[lug] The deal with applets / notifications / panels / indicators / systray.....

Bruce Long qstream at gmail.com
Mon Feb 6 01:13:41 MST 2012


>
>
> Actually, I'm recommending against building a framework instead of
> solving the problem.  If a framework emerges, so be it.  If, as you
> solve the problem, a pre-existing framework fits the bill, go for it.
> However, trying to solve a problem by creating a framework is usually
> a mistake.
>
>
Normally I couldn't agree more. However, the problem I am trying to solve
is that I don't like *any* existing framework. In fact, I hate them. Even
Linux
can be improved a lot. And that's not mentioning Gnome and KDE (or worse,
Gnome 3 or Unity!)

<rant on>  :)
The original poster mentioned some of the problems.
Linus Torvalds complained
that Linux was becoming bloated. Every new capability we want either
requires another
level of indirection or I have to choose a special app instead of OS-wide
support. It's too complex.
Why do we need to refit every app whenever Gnome or Ubuntu changes
something? I
should be able to specify what word-processing logic is ONCE. And someone
else can
design a UI then I should be able to get native code that lets me do
word-processing and
everything else I want to do using that UI. And without a layer of
indirection or having to
submit to a universal standard. It's absurd to have an app repo for every
version of Ubuntu.
AND for every other version of every other distro + Mac + iPhone + Android
+ XBox + Legacy 0$.

In the open source world, if you have a complaint, the battle cry is "fix
it yourself." So that's what I'm doing.
<rant off>


> > Proteus was a pain to create. If there had been a better solution I would
> > have gone with it.
>
> I don't actually know how you know it is a good solution for your
> problem.
>

I started with a design that was in the right direction then evolved it
toward what I wanted.
As I ran into problems for which I couldn't find suitable theory I read
books on the relevant
mathematics then created the theory I needed. My methodology is this: when
I realize there
is some functionality that I want but which my current design does not
provide, I generalize
and simplify. My first draft was 5x more code than my current version.

But, I didn't say I knew it was a good solution. Just that none of the
existing solutions provided
what I needed.

Now I do know that it's a good solution because it's beginning to work!

Cheers!

Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20120206/ce0b396a/attachment.html>


More information about the LUG mailing list