Re: request to federico

[Tom Vogt <tom lemuria org>]

sorry for the delay, I'm busy working on one of my private projects
(http://www.lemuria.org/SpellMaster/ if anyone interested in play-by-email
games is interested to join the testing crowd :) ).


Federico Mena Quintero <federico@nuclecu.unam.mx> wrote:
> The GNOME User Interface Guidelines document is concerned about:
> 
> 	- User interface design issues -- look & feel.
> 
> 	- Standard behavior for user interface elements.

where is the hard border here? e.g. it is generally considered a good idea
to request an app should not pop up a window larger than the screen or other
such things, while  strictly speaking this is between the app and the window
manager with gnome nowhere involved.

is there a hard line or do we state that "hints" and proposals such as this
are within scope, but full details or implementation issues are not?


> 	- Information for programmers on how to actually implement the
>           functionality and behaviors specified in the document.
> 
> 	- General information for developers, such as how to make sure
>           applications internationalize well, how to integrate
>           documentation into the GNOME documentation framework, etc.

depending on the sheer volume - would it maybe make sense to move this to a
seperate, all-gnome "how do I write a gnome application" guide?



> Actually, quite a bit of the RSG should go into the User Interface
> Guidelines as soon as I am out of packaging hell.  I am sorry for not
> having put more work into the UI Guidelines yet, but I have been very
> busy building packages for the GNOME release.

no problem, busy myself, otherwise you would have received a dozen patches
already.:)



> I do not think announcing this on Fresmeat.net or Slashdot.org is a
> good idea, for reasons I already expounded to Mr. Kaminsky on a
> private mail.

looks like that topic is resolved. so we have one official guide in cvs,
period.


> >  also, how are changes to the cvs version working?  you mentioned
> >  patches and that a docbook version exists. where should the patches
> >  be done from, the txt version, sgml or docbook?
> 
> The final patches should be taken against the sgml files on cvs.
time to learn sgml...

> Please note that these are the final patches that will go into the UI
> Guidelines document; don't waste your time posting docbook markup on
> this list when plain text will do :-)
maybe someone can volunteer to translate plain text proposals into
ready-made patches to relieve you of some work. I would, but I don't know
sgml:(


-- 
Those who do not understand Unix are condemned to reinvent it, poorly.
		-- Henry Spencer