Nice work! I appreciate your efforts towards a per-package release system. The layout is nice and the only thing that I think is wrong is the title of the page, which I guess should be "Octave package: Image" and not "Function Referene: image". The new layout works fine as is, in my opinion. I like the coloured boxes.
I have some suggestions (see it as a wishlist or starting point for discussion!) *does the package name has to be repeated in the yellow box as well as on the top of the page? *can the green box display the latest version number, and have a smaller text below with a link to older releases? (if there are is such functionality). If there is something broken in a package version, I think users will appreciate being able to easily find an older version. *is it desirable/possible to have links to external packaging of the octave packages? Like pointers to debian package, macports etc. C.f. http://www.macports.org/ports.php?by=name&substr=octave-image and http://packages.debian.org/sv/source/lenny/octave-image *should there be a link to bugs for the package? For now, it can lead to the bugs page http://octave.sourceforge.net/bugs.html but there will maybe be a bug tracking system for the octave packages in the future. *should we include a pointer to the repository? something like http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/image/ paul 17 okt 2009 kl. 23.58 skrev Søren Hauberg: > Hi All > > For waaay too long I've been working on changing the release system. > Well, "working" isn't really the right word as I haven't actually done > much work due to lack of time. > > To those that don't remember, the reason why we don't allow individual > package maintainers to release their packages when it suits them, is > that the HTML generation is from the old monolithic days. This means > that the current system needs to generate the HTML pages for _all_ > packages at once. > > Carlo and myself have been working on changing this, such that HTML > pages can be generated for individual packages. The code for this is > available in the 'generate_html' package. > > For a long time essential parts of this code has been incomplete, but > I've recently been taking a stab at this once more. You can check out > the results at > > http://octave.sf.net/test > > This test site is only showing three packages (the ones I happened to > have installed). It is also missing a bunch of stuff: > > * Doxygen documentation. > * The Octave manual. > * The help texts of all functions that come with core Octave. > > Do you have any comments on this page? I've made some changes here and > there to simplify the HTML generation; I hope I haven't changed anything > that people cared about (if so, speak up). > > Søren > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Octave-dev mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/octave-dev ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
