Author: linus
Date: 2008-03-20 13:07:08-0700
New Revision: 14196
Added:
trunk/www/gsoc2008/
trunk/www/gsoc2008/eclipse-plugin-handler.html (contents, props changed)
Modified:
trunk/www/googlessoc2008.html
Log:
Added ideas from Christian on the Eclipse-style plugin handler.
Modified: trunk/www/googlessoc2008.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/googlessoc2008.html?view=diff&rev=14196&p1=trunk/www/googlessoc2008.html&p2=trunk/www/googlessoc2008.html&r1=14195&r2=14196
==============================================================================
--- trunk/www/googlessoc2008.html (original)
+++ trunk/www/googlessoc2008.html 2008-03-20 13:07:08-0700
@@ -83,6 +83,11 @@
<li>All modules are built and distributed as Eclipse Plug-ins</li>
<li>Java Web Start</li>
</ul>
+
+ There are also
+ <a href="gsoc2008/eclipse-plugin-handler.html">
+ some other ideas on requirements on the implementation that could be useful.
+ </a>
</p>
<p>
Added: trunk/www/gsoc2008/eclipse-plugin-handler.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/gsoc2008/eclipse-plugin-handler.html?view=auto&rev=14196
==============================================================================
--- (empty file)
+++ trunk/www/gsoc2008/eclipse-plugin-handler.html 2008-03-20 13:07:08-0700
@@ -0,0 +1,71 @@
+<html>
+ <head>
+ <title>More ideas on how to incorporate the Eclipse plug-in handler</title>
+ </head>
+ <body>
+ <div class="h1">
+ <h1>More ideas on how to incorporate the Eclipse plug-in handler</title></h1>
+ <ul>
+ <li>
+It should be a plugin itself, maybe internal in ArgoUML.
+ <ul>
+ <li>
+It will be used in the stand-alone version of Argouml, and
+downloaded by default with the package.
+ </li>
+ <li>
+It shouldn't be downloaded when using the Eclipse framework (or
+at least it should be disabled). In this case, the updater of Eclipse
+should be used.
+ </li>
+ </ul>
+ </li>
+ <li>
+For the reason above, the plugin repository must be compatible with
+the Eclipse updates system.
+ </li>
+ <li>
+It should be able of updating argouml itself.
+ </li>
+ <li>
+It should be strict about the plugins' compatibility with the
+current argouml version.
+ </li>
+ <li>
+It should mimetize the Synaptic UI (or not, but I think that this is
+a great software with a similar focus).
+ </li>
+ <li>
+It should require to accept the plugin licenses before downloading anything.
+ </li>
+ <li>
+It should support Restricted and open repositories, as in Debian.
+Maybe stable and experimental ones too.
+ </li>
+ <li>
+The user should be able to add new repositories, the system
+shouldn't work only with the argouml-downloads one.
+ </li>
+ <li>
+Notify when a new argouml release is not compatible with installed
+plugins (if there are compatible versions of the plugins, download
+them too).
+ </li>
+ <li>
+Atomic installation. If the installation fails, the system mustn't be damaged.
+ </li>
+ <li>
+The UI should have a checkbox "Show only compatible updates".
+Obvious behaviour.
+ </li>
+ <li>
+The UI should have a checkbox "Show all versions of modules".
+Obvious behaviour.
+ </li>
+ <li>
+Search functionality for searching into the plugins database.
+ </li>
+ </ul>
+ </div>
+ </body>
+</html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.