On 4/8/07, Quentin Mathé <[EMAIL PROTECTED]> wrote:
Le 7 avr. 07 à 21:40, Yen-Ju Chen a écrit :
> Hi,
>
> I am thinking to write some small menulets for various tasks.
> Then I realize that the headers I need is in MenuServer,
> specifically EtoileMenulet.h and MenuBarHeight.h.
> Therefore, I have to copy them into each of my menulets.
> It would be easier to have a copy of them in ServerBarKit
> so that I can just link to ServerBarKit.
> But both of them are under GPL while ServerBarKit is under LGPL.
> Is it O.K. to copy them into ServerBarKit and change the license to
> LGPL ? Saso ?
It's ok to put these headers in ServicesBarKit (if Saso say yes to
the license change), now I'm not sure we should keep them public in
future, I mean it's probably better to enforce the use of
ServicesBarKit API which is far less minimalistic. About that too, it
could be better to rename ServicesBarKit to a better name like
MenuletKit… (or ServletKit ;-) We could also strip Kit suffix out
from the name since this framework will consist of only two main
classes. What do you think?
It depends on the plan for ServicesBarKit.
First, people can use it to write menulet.
There is no problem at all.
Second is the organization of menulets,
we can have three options:
1. let menu server organize it, including drag-and-drop.
2. we can have a single "service space" attach to menu server
and all the menulets are subview of this "service space",
like what EtoileWildMenu does with menus.
So this "service space" are responsible for menulets organization
and menu server only need to put "service space" on it.
3. We can even make this "service space" an application
so that it will not share events with menu server.
It might be handy in some cases.
We just need to make this "service space" the same background as
menu server.
While option 1 seems to be easier, option 2 or 3 may be a better
choice for future.
My current plan is to have a volume menulet and probably another menulet
for service menu as you tried before.
Yen-Ju
Cheers,
Quentin.
_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss
_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss
