Quoting Quentin Mathé <[EMAIL PROTECTED]>: > Le 3 mars 06 à 18:22, Sa�o Kiselkov a écrit : > > > If you want to, please, commit it to Etoile SVN, but I don't have > > SVN write > > access, so please take care of that then too ;-) Thanks :-) > > I have committed EtoileMenuServer in Etoile/Services/Private/ > MenuServer, though it's not part of the build process right now. I > haven't make any changes right now outside adding a README (the one > you packaged in parent directory) and a ChangeLog.
Ok, cool. > It seems Nicolas has set up an account for you� Feel free to commit > updates in the repository. Just take care to update the related > ChangeLog. > > >> We should discuss how these various pieces WildMenus bundle, > >> EtoileMenuServer and ServicesBarKit (StatusBar framework) are going > >> to interact with each other precisely, and where they would be > >> located in the repository (because I suppose WildMenus in a not > >> bundle anymore). > > > > EtoileMenuServer is a separate app, so it doesn't really interact > > with anything > > in EtoileMenus (the modified WildMenus thing) at all. EtoileMenus > > replaces > > WildMenus - it doesn't make any sence having both loaded at the > > same time. > > That's why I have committed EtoileMenuServer but not yet the updated > WildMenus part. When I quit the menu server, EtoileMenus is still > functionnal, that's nice and just matching WildMenus behavior. > I'm planning to update WildMenus with EtoileMenus content. I'm > currently reporting the changes you have done in a ChangeLog, your > refactoring being rather major. Then I'm going to commit it. > In your code, #import and #include are strangely mixed, may I remove > every #include directives ? Perhaps having EtoileMenus and WildMenus separate would be better - I'd consider EtoileMenus to be a different bundle from WildMenus, because of the ammount of changes I've done inside. Let's say I "forked" it, rather then just refactored. The reason why #import and #include are mixed is because the WildMenus author used #include and I use #import. I agree that changing it all to #import would be better. But before doing anything with that code, please be sure to check for a new version at http://altair.dcs.elf.stuba.sk/~diablos/menubar - I'm constantly improving the implementation and uploading new bundles. The timestamp of the latest upload is visible on the site, so you can easily compare with your present download. The latest version *(uploaded 4. Mar, Sat ~9AM - right now when I'm writing you this mail message) addresses quite a lot of issues... > >>> Oh and one more thing: unlike Apple, this menusystem *will* have > >>> tear-off menus > >>> - we won't be making the same mistake as Apple. > >> > >> Nice. > > > > Damn I'm great! :-D > > Yeah :-) > > � but well this tear-off feature has a minor bug in my test ;-) More > precisely, when I start an application with a menu already torn-off > on a previous use (where traditionnal vertical menu was enabled), the > tear-off menu appears partially behind the menu bar� When I click on > its related menu item in the menu bar, every menus disappear, only > the menu server remains visible (and the menu I just clicked on). > > Quentin. > > -- > Quentin Mathé Yes, the latest update fixes this issue as well. -- Saso _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
