[Panel-devel] KDE4

[Matt Broadstone]

On a less controversial note :)... I have also been kicking (no pun
intended) around with an idea for a new extension (and yes Aaron this
is the idea I was talking about in #plasma). The idea is to provide a
tab bar. Yes plain and simple tabs for kicker/plasma, somewhat more
complex because as opposed to just a simple tab widget, this will
display only the QTabBar at first, and upon selection of a tab it will
popup just that tab. The added feature of it is that the tabs will be
able to be dragged off the tab bar into a torn off tab (think tear off
menu's in a popup widget). First of all I think the widget itself will
find a home many places in KDE simply because it's sexier to have a
tab bar that does good looking popup tabs (a replacement for
KMultiTabBar for instance), but it also might tie in to the idea of
the basket that's been in discussion on this list. What do you all
think?

On 6/21/05, Matt Broadstone <mbroadst at gmail.com> wrote:
> I've been biting my lip on this for a week or so now, but I have
> finally gotten to the point of asking about the purpose for bindings
> in the future of this progress. It's almost as if people have
> forgotten how slow Kicker used to be. All the most recent work done on
> Kicker has basically been to it more efficient, faster. Why exactly do
> we need to add support for these scripting languages to add
> functionality to Kicker? What exactly can't be done in C++ that python
> allows? or does it just allow more ideas that sort of work well? I
> personally used to use gDesklets in gnome and I thought it was a
> pretty bad, it used a whole lot of my memory up (which python ALWAYS
> seems to do in intensive tasks). I know this probably seems like a
> heavy hitting comment against SK, but I'm almost at the point where I
> think SuperKaramba stuff should be used for mockup's, and the really
> useful widgets should be fully brought in as C++ applets?
> 
> KDE is already so bloated, especially with it's own single language,
> why do we need to add more languages? Why do we need to add more
> bloat?
> 
> On 6/21/05, Paul Giannaros <ceruleanblaze at gmail.com> wrote:
> > > > Liquid Weather is probably the most downloaded/used SuperKaramba theme
> > > > out there, and Matt is awesome about working with us on SuperKaramba
> > > > developments.
> > >
> > > ok. let's target that one then. it's also a great candidate for testing the
> > > different form factors: icon on the panel with an extender, full applet on
> > > the desktop.
> >
> > As well as bindings, as it's a pretty much fully Python deal.
> > Bindings is what i'm most interested in. Any thoughts been put forward
> > as to how to handle them? Direct, thin bindings wrapping libplasma for
> > each language? A more abstract method (maybe parsing of header files
> > and providing plugins with the necessary data to each create the
> > bindings or something of the sort) for auto-generation?
> >
> > Cerulean
> > > _______________________________________________
> > > Panel-devel mailing list
> > > Panel-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/panel-devel
> > _______________________________________________
> > Panel-devel mailing list
> > Panel-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/panel-devel
> >
> 
> 
> --
> _____________________
> Matt Broadstone
> Cell: (301) 641-6893
> E-mail: mbroadst at gmail.com
> 


-- 
_____________________
Matt Broadstone
Cell: (301) 641-6893
E-mail: mbroadst at gmail.com