Malcolm,
On 2005 Jan 25 , at 17.49, Malcolm J. Currie wrote:
>> Malcolm: I'm currently generating the `recent commits' page into
>> cvs.starlink.ac.uk/~nxg/. Are you planning any location in the new
>> web
>> order for such static/generated web pages?
>
> If we have master sources of information, it is preferable to use those
> for dynamic pages, than keep a separate HTML list that will become out
> of date.
I'm suggesting having the master source of information about code
`owners' be in the component.xml file, right alongside the code. This
seems natural and straightforwardly maintainable.
Since Steve's nightly build automatically assembles these into
componentset.xml at the top of the tree, they're also readily
accessible. I've quickly set up another cron job to regenerate
componentset.html nightly, and leave it at
<http://cvs.starlink.ac.uk/~nxg/componentset.html>. For example.
The contents of the component.xml files could be extended very easily,
for example to include supported status and copyright owner.
I suggested a static web page only for the remainder of that package
table which isn't in CVS and isn't supported -- things like TEX, EMACS,
EMAIL -- for historical interest only. If, that is, we don't just junk
any record of those packages which we're really not responsible for at
all, and haven't been since Starlink stopped having a sysadmin role.
> Something that maintains a page listing the software items including
> contacts and e-mail addresses, like [log in to unmask], is needed for
> users. I'd like to divide it into groups: classic applications and
> libraries, and likewise for Java. Most users will look at the
> applications first.
That's the general idea.
> I'm still playing around with some tools to determine what's useable.
> Hitherto it's the lack of documentation that's made them harder to use
> than actually coding the CSS manually. I'm awaiting some books
> including a CSS Cookbook.
I find the CSS1 standard very useful, <http://www.w3.org/TR/CSS1>, and
css/edge <http://www.meyerweb.com/eric/css/> is full of the quite
remarkable things that are possible with CSS.
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|