On Sun, 16 Oct 2005, Aschwin Marsman wrote:
> > tested. Quoting betterdesktop.openSUSE.org: "Over the past year, we
> > have conducted many usability tests on different parts of the KDE and
> > GNOME desktops."
>
> That's not my point, I know they did test on both KDE and GNOME, but I
> can't see ximian as an unbiased entity when you are doing those tests.
Please note, that the test persons were volunteers (not Novell/Ximian
employees)!
> Have they developed improvements for KDE since Novell took them over?
That's not their job - they are supposed to work on GNOME.
> > > Is Novell's desktop future on GNOME?
> >
> > No. Neither GNOME nor KDE are the privileged Novell desktop
> > environment - they both have the same status.
>
> But what about specific installation tooling and new applications: I
> don't hope Novell is creating a Yast specific for GNOME, one for KDE and
> one written in MONO?
Please, don't try to act naive! YaST isn't bound to KDE or GNOME - why
should we reinvent the wheel?
> It could be done off course by using something like an observer like
> pattern: create the functionality (backend) once and have different
> views on it using a GNOME/KDE/... frontend. What are the ideas on this
> for the OpenSUSE project?
>
> As a usability example: I would like to have the ability to make some
> improvements (in my opinion) to e.g. you: When downloading the patches
> and everything went will I don't want to press the Finish button myself,
> I would like a checkbox that gives me the option to specify the
> behaviour I described above. When will development be open for these
> kind of issues, and who will decide if a proposed patch will be included
> or not?
The development is already open - just use Bugzilla to interact with the
YaST developers on this. But please note, that there will be quite some
redevelopment on the YaST2 Packagemanager + YOU for 10.1...
Regards
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
