Hello
On Tue, Jan 24, 2006 at 04:03:00PM +0100, Troels Henriksen wrote:
Generally, I think your idea is very cool. A standardized way to start applications (apart from `run-frame-toplevel') would be highly useful.
Thank you.
I do, however, have a request:
Max-Gerd Retzlaff m.retzlaff@gmx.net writes:
Clim Launcher
Together with the Launcher by Dwight Holman there is an additional benefit: The macro can announce the created starter to it. So that if you use it to define the function that fires up your GUI it will automatically displayed in the Clim Launcher.
This functionality should not be wired to a specific launcher program. Instead, McCLIM should maintain an *application-entry-points* alist that maps application names to functions. Thereby, any CLIM-application will be able to retrieve a list of the programs available. This would also open for the possibility of creating alternative launcher programs.
This is perfectly possible. Think of CLIM-LAUNCHER as just what you want + a simplistic standard GUI. The list of applications ist called clim-launcher::*applications* (though it is not an association list right now but a list of application objects (this is part of what Dwight has written)), and the interface function to add and delete applications are currently named ADD-APPLICATION and DELETE-APPLICATION (see the footnote in my other, just sent mail about the names).
I've just seperated both parts: The "backend" has right now got 39 lines of code, and the current GUI consists of 45 lines. To separate the parts is a good idea, and I have just done that in my private directory. Though I would like to have this very simple GUI interface included directly into McCLIM.
This doesn't mean that there cannot be another shiny, flashing "launch bar" that is available via a separate package.
Bye, Max