[Panel-devel] Kickoff / KDE 4

[Siraj Razique]

Hi.
Raptor is the Chosen solution to put an end the Menu war and shouldn't be
reason for dispute.
I see that it's starting again, which shouldn't happen ,

 and Hein Raptor team is well aware of all the usability research and We
have been in touch with Celeste.
 If some one is porting Kickoff please take some time to look at Raptor
goals and Try to write reusable code it will help both projects we.

by the way,  good luck with the port

Raptor will continue,

And I urge the team to think in ways of uniting and progressing.and code is
there to be improved not to be trashed.

and for the usability people, we will come to you! (when it's ready)
we WILL NOT  release without your valuable comments.

the idea is to make the GUI XML based + SVG themeing (again xml). we don't
want to recompile the menu for each point the usability team will make. once
we have the XML gui working We will have the option of testing the usability
features real time and adjust quickly
.
There are many such plans to make the Menu really dynamic at runtime.

So I request the Kickoff porting team lead by Knight to come up with the
final set of notes, Please try to remind your selfs why We need plasma and
why we need to trash away Kicker code + Kdesktop code. too many unfinished
improper frame works appended one on top of the other .We don't want this in
plasma. if we are building a menu we need a common collaborative framework
not two solution that leads to dead ends. Having two GUI options is
fantastic  for the end users I would prefer to have 100's of them ;-) . but
it's terrible to have 100 different frameworks that dose the same thing.

Bye


On 9/25/07, Aaron J. Seigo <aseigo at kde.org> wrote:
>
> On Tuesday 25 September 2007, Eike Hein wrote:
>
> to avoid unnecessary flame-fanning:
>
> > when hard work is being passed over,
>
> it isn't being passed over. there is nothing to pass over at the moment.
> it's
> a work in progress. when it is ready then it will be offered as an option
> at
> a *minimum* and will be examined for use in default set ups. but until it
> is
> ready, there is no possibility to do so. hope that explains things better.
>
>
> > but one way to
> > avoid that happening is for those who do the work to
> > talk to the rest of the project to make sure a design
> > is workable and agreed upon, and I don't think that
> > has happened here from what I've seen.
>
> the raptor developers have been talking to artists and other developers,
> including myself, for quite some time now. there has been communication,
> though the raptor team has chosen to run with their own UI theories rather
>
> than go to the OpenUsability folks. this is completely their right, and
> we'll
> see how it shakes out in the end. experimentation is good and all that.
> but
> yes, they have been communicative. just in their own way.
>
> relaly, it seems that it has mostly been people outside of the raptor and
> kickoff teams that have been helping confuse the situation =)
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Trolltech
>
> _______________________________________________
> Panel-devel mailing list
> Panel-devel at kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
>
>


-- 
Sj
.----
Work Email : sirajr at gmail.com
Official Email: siraj at kdemail.net
Website : http://www.kbfx.org
phone : +94114927829
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20070925/41b85a0c/attachment.html