[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-patch-tracker] [patch #8787] Octave Forge: Improve package overv
[Octave-patch-tracker] [patch #8787] Octave Forge: Improve package overview page
Tue, 09 Feb 2016 02:40:16 +0000
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.6.0
Follow-up Comment #21, patch #8787 (project octave):
> Reading them on the fly is a good idea unless you want to make the
packages.php page completely static.
> Instead of a (new) json file we could simply copy the package's DESCRIPTION
file and parse it. Again, this will make it easier for us to make changes
later. For example, we could decide to show more information on packages.php.
Won't that make the site even slower? As it is, it only needs to include the
files straight from the content, but having to actually parse these.
The reason to use json instead of the DESCRIPTION is that I wouldn't like to
write a parser for the DESCRIPTION file in php while a json writer in Octave
would be much simpler (well, for the very limited needs we have that is).
There's also the green side of it, we don't really need to do this, it's just
a waste of power. If we have the code that generates the page on the fly for
the users, and the content doesn't change that frequently, why not generate
that content ourselves once and make it static.
Note that release process is a script that just moves files around on the web
server. It'd be perfectly fine to have a script there that regenerates the
packages page, which is called by the release script.
Reply to this item at:
Message sent via/by Savannah