Tiny Core Extensions > TCE Q&A Forum

Creating submenus in TC2.0RC4

<< < (2/4) > >>

roberts:
It would be nice to have such a specification for menus.

However, we have hundreds, namely 532 existing tces and 504 existing tcz, already with the JWM XML menu specification. All these extensions for v2.0 and v2.0 is not even final yet!

It would be quite an undertaking to unpack, adjust, and repack all those extensions for the new menu specification.

Plus it would mean a delay to release 2.0 final. 
If it were to be considered, a major change, such as v2.0 would be the time for such a change.

bmarkus:
Hi,

there is www.freedesktop.org :


--- Quote ---freedesktop.org is open source / open discussion software projects working on interoperability and shared technology for X Window System desktops. The most famous X desktops are GNOME and KDE, but developers working on any Linux/UNIX GUI technology are welcome to participate.

freedesktop.org is building a base platform for desktop software on Linux and UNIX. The elements of this platform have become the backend for higher-level application-visible APIs such as Qt, GTK+, XUL, VCL, WINE, GNOME, and KDE. The base platform is both software and standards.
--- End quote ---

One of their standard is for menus:

http://www.freedesktop.org/wiki/Specifications/menu-spec

It is followed by KDE, xfce and others but not by JWM :(

My script to manage the menu in JWM now works. After some testing I will publish in a separate topic to discuss. For sure other WM's can be supported too.

But the best would be to use freedesktop structure and then convert it to the appropriate native format of the used WM.

BTW, which other WM's must be considered with TC 2.0?

roberts:
And not flwm, or many of the other "small is beautiful" window managers.
Besides to implement would likely add much bulk compared to existing busybox's awk applet currently being used.

bmarkus:

--- Quote from: roberts on June 06, 2009, 01:57:48 AM ---And not flwm, or many of the other "small is beautiful" window managers.
Besides to implement would likely add much bulk compared to existing busybox's awk applet currently being used.

--- End quote ---

It's clear. On the other hand it means that all tiny WM has its own menu definition method. An extension maker can't support all when creating tce/tcz, the OS has to offer a mechanism.

What happenes if a WM installed fom tce/tcz after the extensiion installed, who will create the menu defs for already installed apps?

roberts:
The default mode for TC is that apps (extenions) are either mounted or loaded upon boot from tce directory, therefore the menu for such is dynamically generated. I already have dynamic menu via standardized calls to interface files supporting TC extension menus for flwm and hackedbox. I believe winmdow maker is also now available. If you choose any of these alternate window managers you still have your application extension menu. That was a major improvement for v2.0.

If you choose to use persistent local, then by your choice you have decided not to be dynamic.So YMMV. I don't promote persistence and have been promoting pristine boot with dynamic extensions for over five years now..

Navigation

[0] Message Index

[#] Next page

[*] Previous page