<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MOD Compatibility Engineâ„¢</title>
	<atom:link href="http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/</link>
	<description>Your premium source for custom modification services for phpBB</description>
	<lastBuildDate>Wed, 11 Jan 2012 20:39:04 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dave.rathbun</title>
		<link>http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/comment-page-1/#comment-462</link>
		<dc:creator>dave.rathbun</dc:creator>
		<pubDate>Wed, 08 Nov 2006 00:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpbbdoctor.com/blog/?p=27#comment-462</guid>
		<description>But you&#039;re looking at a different issue. :-)

If you have subforums with code replicated / repeated in other areas, that&#039;s one issue. If you have a MOD that installs a &quot;tooltip&quot; for the topic that&#039;s another MOD. Unless that MOD is written to be compatible with subforums, it won&#039;t be. That&#039;s not what the MOD-CE is designed to do.

What it is designed to do - at it&#039;s most basic level - is determine if two (or more) MODs can be installed without conflicts. It doesn&#039;t attempt to - nor will it ever attempt to - see if two MODs will function together, that would be nearly impossible.

For example, consider the following two mythical MODs. One opens index.php, finds a specific line (let&#039;s say line &quot;300&quot; because it doesn&#039;t really matter what it is) and before that line adds this code:
&lt;pre&gt;$myvar = FALSE;&lt;/pre&gt;
Next, MOD #2 also finds line 300 and before it adds this:
&lt;pre&gt;$myvar = TRUE;&lt;/pre&gt;
Now clearly these two MODs will conflict functionally, but they can both be installed at the same time. Whichever MOD is installed last will &quot;win&quot; as to which value is set to $myvar.

The purpose of the MOD CE as I plan to deliver it is to find a set of MOD and determine if they conflict with their installation instructions. There are rules that I have determined and coded that say exactly what a conflict was, in short it&#039;s based on detecting replace operations that update overlapping blocks of code (where a &quot;block of code&quot; could simply be one line.)

In other words, there&#039;s no way that I can see - short of writing some sort of code parsing engine that actually understands what the code is doing - to detect and react to the situation you describe.</description>
		<content:encoded><![CDATA[<p>But you&#8217;re looking at a different issue. <img src='http://www.phpbbdoctor.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>If you have subforums with code replicated / repeated in other areas, that&#8217;s one issue. If you have a MOD that installs a &#8220;tooltip&#8221; for the topic that&#8217;s another MOD. Unless that MOD is written to be compatible with subforums, it won&#8217;t be. That&#8217;s not what the MOD-CE is designed to do.</p>
<p>What it is designed to do &#8211; at it&#8217;s most basic level &#8211; is determine if two (or more) MODs can be installed without conflicts. It doesn&#8217;t attempt to &#8211; nor will it ever attempt to &#8211; see if two MODs will function together, that would be nearly impossible.</p>
<p>For example, consider the following two mythical MODs. One opens index.php, finds a specific line (let&#8217;s say line &#8220;300&#8243; because it doesn&#8217;t really matter what it is) and before that line adds this code:</p>
<pre>$myvar = FALSE;</pre>
<p>Next, MOD #2 also finds line 300 and before it adds this:</p>
<pre>$myvar = TRUE;</pre>
<p>Now clearly these two MODs will conflict functionally, but they can both be installed at the same time. Whichever MOD is installed last will &#8220;win&#8221; as to which value is set to $myvar.</p>
<p>The purpose of the MOD CE as I plan to deliver it is to find a set of MOD and determine if they conflict with their installation instructions. There are rules that I have determined and coded that say exactly what a conflict was, in short it&#8217;s based on detecting replace operations that update overlapping blocks of code (where a &#8220;block of code&#8221; could simply be one line.)</p>
<p>In other words, there&#8217;s no way that I can see &#8211; short of writing some sort of code parsing engine that actually understands what the code is doing &#8211; to detect and react to the situation you describe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: damnian</title>
		<link>http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/comment-page-1/#comment-455</link>
		<dc:creator>damnian</dc:creator>
		<pubDate>Tue, 07 Nov 2006 18:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpbbdoctor.com/blog/?p=27#comment-455</guid>
		<description>Yes, I certainly meant &quot;repeated&quot;. However, replication isn&#039;t always limited to a single file.

Guess what, I also have a subforums MOD of my own, and it has major portions of index.php replicated in viewforum.php. Now, try adding the last topic tooltip to the forum list - and you&#039;ve missed the subforums...

I realize that subforums are an extreme (this is probably the reason for CH to eventually become a phpBB2 fork), but more common examples can be thought of, the Attachment MOD being a good starting point ;).</description>
		<content:encoded><![CDATA[<p>Yes, I certainly meant &#8220;repeated&#8221;. However, replication isn&#8217;t always limited to a single file.</p>
<p>Guess what, I also have a subforums MOD of my own, and it has major portions of index.php replicated in viewforum.php. Now, try adding the last topic tooltip to the forum list &#8211; and you&#8217;ve missed the subforums&#8230;</p>
<p>I realize that subforums are an extreme (this is probably the reason for CH to eventually become a phpBB2 fork), but more common examples can be thought of, the Attachment MOD being a good starting point <img src='http://www.phpbbdoctor.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave.rathbun</title>
		<link>http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/comment-page-1/#comment-452</link>
		<dc:creator>dave.rathbun</dc:creator>
		<pubDate>Tue, 07 Nov 2006 14:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpbbdoctor.com/blog/?p=27#comment-452</guid>
		<description>I certainly agree that there will be things that fall through. However, I am not following your example. When you say &quot;replicated&quot; that means to me &quot;repeated&quot;, as in there is some code that is repeated along the way. And since you mentioned subforums I think I see where you are going... as there are lines of code within the (for example) simple subforums MOD for index.php that are the same as code from the regular index.php. I have two ways to address this.

First, I have my own subforums MOD that is similar in functionality but substantially different in code from the subforums MOD released at phpBB. I intend to offer (here at this site) very few MODs that are not written (or rewritten) here. I don&#039;t plan to rewrite the attachment MOD, for example. ;-) But by doing that, and by keeping this process in mind while writing those MODs, some of these issues can be addressed.

But the real solution to this is that the MOD CE doesn&#039;t go by FIND commands, but by the results of the FIND commands. When a MOD is added into the MOD Manager (which is the source data for this system) each FIND is tagged based on the core code from an unchanged phpBB board (current version). The results of that process drive the compatibility check.

In other words, the MOD CE does not attempt to install every MOD that is selected, it anticipates what would happen and records conflicts (or at least &lt;em&gt;potential &lt;/em&gt;conflicts) based on that process. So it&#039;s a bit different approach than what I think you were envisioning.

Thanks for your comment. It&#039;s refreshing to see one actual comment mixed in with the 30+ spam comments that my spam-catcher is processing. :-)</description>
		<content:encoded><![CDATA[<p>I certainly agree that there will be things that fall through. However, I am not following your example. When you say &#8220;replicated&#8221; that means to me &#8220;repeated&#8221;, as in there is some code that is repeated along the way. And since you mentioned subforums I think I see where you are going&#8230; as there are lines of code within the (for example) simple subforums MOD for index.php that are the same as code from the regular index.php. I have two ways to address this.</p>
<p>First, I have my own subforums MOD that is similar in functionality but substantially different in code from the subforums MOD released at phpBB. I intend to offer (here at this site) very few MODs that are not written (or rewritten) here. I don&#8217;t plan to rewrite the attachment MOD, for example. <img src='http://www.phpbbdoctor.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  But by doing that, and by keeping this process in mind while writing those MODs, some of these issues can be addressed.</p>
<p>But the real solution to this is that the MOD CE doesn&#8217;t go by FIND commands, but by the results of the FIND commands. When a MOD is added into the MOD Manager (which is the source data for this system) each FIND is tagged based on the core code from an unchanged phpBB board (current version). The results of that process drive the compatibility check.</p>
<p>In other words, the MOD CE does not attempt to install every MOD that is selected, it anticipates what would happen and records conflicts (or at least <em>potential </em>conflicts) based on that process. So it&#8217;s a bit different approach than what I think you were envisioning.</p>
<p>Thanks for your comment. It&#8217;s refreshing to see one actual comment mixed in with the 30+ spam comments that my spam-catcher is processing. <img src='http://www.phpbbdoctor.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: damnian</title>
		<link>http://www.phpbbdoctor.com/blog/2006/11/02/mod-compatibility-engine%e2%84%a2/comment-page-1/#comment-423</link>
		<dc:creator>damnian</dc:creator>
		<pubDate>Sun, 05 Nov 2006 01:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpbbdoctor.com/blog/?p=27#comment-423</guid>
		<description>This sounds very promising.

However, there will also be false negatives. When a piece of code is replicated by MOD A (e.g. a subforums MOD), you won&#039;t be able to identify MOD B (e.g. a tooltip MOD) missing it.</description>
		<content:encoded><![CDATA[<p>This sounds very promising.</p>
<p>However, there will also be false negatives. When a piece of code is replicated by MOD A (e.g. a subforums MOD), you won&#8217;t be able to identify MOD B (e.g. a tooltip MOD) missing it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

