On 11 Mar 2011, at 14:47, Phil Bull wrote:

> Hi guys,
> 
> On Fri, 2011-03-11 at 09:44 -0500, Shaun McCance wrote:
> [...]
>> Should I remove the 2.x HIG from the gnome-devel-docs releases?
>> Or do you think the information there is still valuable enough
>> to warrant being shipped with 3.0?
> 
> If it is valuable, we can at least update the screenshots.

Just had a quick chat with Allan, and we both agreed that while there is still 
plenty of useful information in there, and we that should leave it in 
gnome-devel-docs, we don't think we should bother updating the screenshots. 
Apart from the fact it's a lot of effort for not much gain (I updated them all 
once before, and it was fairly painful), we think it could be a potential 
source of confusion that we could do without.

It may very well be worth updating the introduction, however, just to clarify 
that while it was written for GNOME 2.x, we expect the majority of it to remain 
useful for GNOME 3.x in the interim (and perhaps pinpoint the bits that 
aren't). I'm happy to do that if people think it's a good idea.

As for where we are with the HIG -- I *may* be able to get something 
rudimentary for you to look at during your hackfest next week, but I can't 
promise anything. If I do, it'll be more about the structure and the plan than 
the actual content, at this stage. I've just started to revisit the discussions 
we had before Christmas to try and pull them into something tangible that we 
can move forward on, but I'd want to at least run it past the other people who 
contributed to that discussion first, before distributing it any further.

Cheeri,
Calum.

-- 
CALUM BENSON, Interaction Designer     Oracle Corporation Ireland Ltd.
mailto:[email protected]         Solaris Desktop Team
http://blogs.sun.com/calum             +353 1 819 9771

Any opinions are personal and not necessarily those of Oracle Corp.

_______________________________________________
usability mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/usability

Reply via email to