https://wiki.kram.nz/index.php?action=history&feed=atom&title=SE401%3A33%3APlugin_Analysis 2026-04-30T02:50:56Z Revision history for this page on the wiki MediaWiki 1.45.3 https://wiki.kram.nz/index.php?title=SE401:33:Plugin_Analysis&diff=74&oldid=prev 2008-02-15T20:03:56Z

<p>New page: ==&lt;font color=#00267c&gt;Initial Thoughts&lt;/font&gt;== Before we began looking on how to develop a plug-in interface we thought it would be quite simple. It would require an interface (or equiva...</p> <p><b>New page</b></p><div>==&lt;font color=#00267c&gt;Initial Thoughts&lt;/font&gt;==<br /> Before we began looking on how to develop a plug-in interface we thought it would be quite simple.<br /> <br /> It would require an interface (or equivalent in .net/VB) with predefined methods like:<br /> :*Variables to describe name/functionality, input type(s) needed etc.<br /> ::*This raises problems, how do you deal with plug-ins that require more than 1 data input?<br /> :::*Could be resolved by creating applications to merge data into 1 source.<br /> :::*This wont work if the data sources are incompatible - might be easier if we make the plugin take an array of data sources.<br /> :*Function(s) that process input data.<br /> :*Function to output source code.<br /> :*How to display a static version of the content in the editor.<br /> :*Need to create a way to scan a directory for installed plug-ins.<br /> :*As the tool is for users with low computer skills we probably don&#039;t want them to be going off to sites and downloading/installing content themselves. It would be preferable to make this part of the tool - could do this similar to the bit torrent Client Azureus&#039; approach - downloads a list of plug-ins from the site, and can tick the plug-ins you would like to install and press download. They are automatically installed and activated upon restart.<br /> ::*This brings more issues - who wants to restart the application after downloading a new plug-in - we should find out if its possible to develop a hot pluggable tool (? is this the right term - start plug-ins while tool is running).<br /> :*We would need to create a method of checking for plug-in updates so users do not need to manually check.<br /> ::*Added to user stories - See Plug-in specific stories<br /> <br /> <br /> ==&lt;font color=#00267c&gt;Research&lt;/font&gt;==<br /> MSDN site makes it sound very easy to create a plug-in framework - they even have a guide on how to do it&lt;br&gt;<br /> [http://msdn2.microsoft.com/en-us/library/ms972962.aspx MSDN Creating a Plug-In Framework]<br /> :Note: Also has guides on making GUI&#039;s<br /> This doesn&#039;t address making hot pluggable tools, but Java can do it so surely .net does...?<br /> :*Brief read over the MSDN guide would suggest it doesn&#039;t as you need to modify a .config file before the plug-in can be used, we will need to automate this for the user. Restarting the application is not a huge deal though - more of a user convenience.<br /> <br /> <br /> ==&lt;font color=#00267c&gt;Final Thoughts&lt;/font&gt;==<br /> :*We will initially build the framework without plug-ins (functionality will be part of the framework).<br /> :*As this is an XP project we can choose to add plug-ins at any stage.<br /> ::*Will involve a bit of refactoring but should not cause any major problems (maybe 1 iterations worth).<br /> :*Will discuss with Gill and see if she agrees.<br /> <br /> <br /> <br /> [[SE401:33:Mashup_Creation_Tool|◄ Back]]</div>

Mark