Re: Fiji Update Site: Dependencies
Posted by
Alexandre Dufour on
Jan 31, 2013; 5:17pm
URL: http://imagej.273.s1.nabble.com/Fiji-Update-Site-Dependencies-tp5001614p5001626.html
Hi Johannes, Curtis
On 31 janv. 2013, at 16:47, Johannes Schindelin wrote:
Thanks for the pointers. in fact I realize I already knew about the updater, since Icy has had the exact same system from day 1 (we just subjectively borrowed the term "repository" from the linux world rather that the Eclipse-centric "update site").
I probably just got confused by the discussion about packing icons etc. in the right place/folder, wrongly assuming that the "update sites" actually led to full html pages online where the plugin icons would appear, like what we did with the Icy website (and I would have liked to see how it worked if that was the case).
In our case, icons are submitted via the site's Content Management System (which feeds the "official" repository), separately from the jar, because it offered several advantages: 1) the web site automatically generates the plug-in web page online; 2) the various media and metadata published online alongside the jar can be displayed in-app either via the plugin browser, or via our new "spotlight"-like all-in-one search bar (inspired from IJ2's search bar which we extended to do live plugin browsing/dowloading/running from the keyboard). I guess we could also adapt the system if you guys want to use the same distribution system, and even make this work for plain ImageJ.
Btw, seeing the screen captures on said pointers, does Fiji still need to be restarted when downloading/updating plugins? I thought I understood from a recent meeting this was solved (it took us hard effort to solve the problem and avoid restarting for every new plugin install/update).
Alexandre
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html