Re: Ok to redirect http://developer.gnome.org/doc/API/2.0/ to GNOME Library?

[Tim Janik <timj gtk org>]

On Tue, 14 Aug 2007, Olav Vitters wrote:

> GTK+ is the main user of the developer API reference with links from:
>  http://www.gtk.org/api/
>
> I want to redirect:
>  http://developer.gnome.org/doc/API/2.0/
> to:
>  http://library.gnome.org/developer/
>
> See for instance the GTK+ API reference on:
>  http://library.gnome.org/developers/gtk/2.11/
>
> Note: GNOME Library currently finds new tarballs every night. At one
> point this will start after install-module runs (low priority right
> now).
>
> If nobody objects within a week I'll make this change.

i'm currently uploading the glib/atk/pango/gtk+ docs to
  http://developer.gnome.org/doc/API/2.0/
manually and have a couple issues/questions before the move:
- the above link http://library.gnome.org/developer/ doesn't actually work
- the front page links to http://library.gnome.org/devel/ which is
  a directory listing
- i was going to say something about the new reference API titles page,
  but can't currently browse/verify it due to the directory listings...
  - the API overview here: http://developer.gnome.org/doc/API/
    is ordered by dependencies, this ordering needs to be preserved
  - the module names/titles shouldn't be marked in red (red is
    far too intrusive for normal text it allmost looks like error
    messages)
  - links should be clearly identifiable as links like on the
    current pages (blue with underline)
- the most requested documentation feature at linuxtag was to make
  our docs searchable, http://developer.gnome.org/doc/API/ has
  a site specific google search entry now. this functionality
  needs to be preserved.
- i personally find the grey background image star on
    http://library.gnome.org/developers/gtk/2.11/
  fairly irritating when reading the index. i'd prefer
  the index text to not change contrast by removing
  the grey star from the areas which display actual
  code (i.e. below the "GTK+ Reference Manual" block)
- currently, new trunk based docs can be put up (fixed) immediately
  by doing a new upload (a 24h lag due to automated builds would be
  acceptable here though). you say you're building docs nightly
  from release tarballs only?
  how can we get trunk based docs up then?

> --
> Regards,
> Olav

---
ciaoTJ