Yep, that's much more like it. Definitely the visual layout could be
improved with the display of those icons on the right (then should be
the same width, or aligned better, or something), however I think the
concept is much better. The usual 'site logo' in the top left makes
sense, and the associations with GTK and Perl are really clear from
what's there on the right hand side.
Yaakov Nemoy wrote:
Hmmm....
2006/8/2, John Pye <[EMAIL PROTECTED]>:
Hi again,
I think more that anything, the thing that's irking me here is the fact
that we've got these icons in the "website logo" position on the page.
When you put *an* icon there, you're saying graphically that "this is
the site of X". To a certain degree, if we see ourselves a sub-project
of GNOME, then that would be OK -- lots of GNOME projects take on the
GNOME icon. But I don't think that this "works" in the case of the
python icon. And further: to have have *two* icons in this special
position on the page creates confusion, as I already argued.
Perhaps another approach would be to have them in a panel down one side,
with some short text explaining each one: that PyGTK can be used to
develop applications for the GNOME environment or any other applications
that support the GTK+ toolkit, for applications that you write in the
Python language.
5 seconds of googling came up with this:
http://gtk2-perl.sourceforge.net/
I get the feeling they consider themselves part of the Gnome project.
But they clearly put their other parts down the side using the
original icons, which IMHO clash horribly.
John: Is this what you had in mind?
Yaakov
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
--
John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia
http://pye.dyndns.org/
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
