From: Thomas L. <ta...@ec...> - 2001-04-21 15:33:05
|
I'm wondering whether to replace AppMenu with a general-purpose AppInfo.xml file. Menu items would be part of it, but we could add other stuff like: - A tooltip for the application. - About... stuff (Name, Version, Author, Copyright, etc). This means all programs will get a consistent info box, and allows applications to be automatically indexed if the need arises... - May-be-run-as-an-applet flag (and lose AppletRun). Applets normally need an AppRun anyway (and Stephen Watson's applets just symlink AppletRun anyway!). - Anything else we think of later ;-) Happily, we wouldn't even have to change much code, as the current system just caches the tree structure of the XML! Thoughts? -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Stephen W. <wa...@ul...> - 2001-04-23 11:25:52
|
In message <200...@ev...> Thomas Leonard <ta...@ec...> scribbled: > I'm wondering whether to replace AppMenu with a general-purpose > AppInfo.xml file. Menu items would be part of it, but we could add other > stuff like: > > - A tooltip for the application. > > - About... stuff (Name, Version, Author, Copyright, etc). > This means all programs will get a consistent info box, and allows > applications to be automatically indexed if the need arises... Both good ideas. > - May-be-run-as-an-applet flag (and lose AppletRun). Applets normally need > an AppRun anyway (and Stephen Watson's applets just symlink AppletRun > anyway!). We would need to make sure that AppRun can distinguish between an XID for an applet and a wholly numeric filename for a program. > > - Anything else we think of later ;-) > > Happily, we wouldn't even have to change much code, as the current system > just caches the tree structure of the XML! > > Thoughts? Have we enough common code yet in the filer and various apps to make a library worthwhile? -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Thomas L. <ta...@ec...> - 2001-04-23 16:15:40
|
On Mon, Apr 23, 2001 at 12:22:23PM +0100, Stephen Watson wrote: [...] > Have we enough common code yet in the filer and various apps to make a > library worthwhile? One thing that would be useful... installing some python modules with rox-base. We could have Choices, Savebox and Options included, which would cut down the size of some applications. It would mainly be useful for python programs, but would also make it really easy to add a couple of python scripts to replace the old gui utils... Slight problem though: where do we put them? The default python search path only includes /usr/local/... (guess it depends where you installed it) which isn't very helpful, so we'd have to add more directories to it... (~/lib/rox-base, /usr/local/lib/rox-base, ... like Choices?) -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Diego Z. <za...@ce...> - 2001-04-24 22:17:39
|
ta...@ec... said: > One thing that would be useful... installing some python modules with > rox-base. We could have Choices, Savebox and Options included, which > would cut down the size of some applications. I've been meaning to write Perl modules (sorry, I don't grok Python) for handling Choices for some time. Maybe I'll get around to it someday, that would make things easier for Perl programs. > Slight problem though: where do we put them? The default python search > path only includes /usr/local/... (guess it depends where you > installed it) which isn't very helpful, so we'd have to add more > directories to it... (~/lib/rox-base, /usr/local/lib/rox-base, ... > like Choices?) You could put them in some rox directory (/usr/local/rox/lib?) and have any AppRun scripts that need them set the PYTHONPATH directory appropriately... Hm... I see a chicken-and-egg problem somewhere in there (need the modules to figure out the paths, need the path to find the modules). Will keep thinking about it (in my copious free time). --Diego |
From: Thomas L. <ta...@ec...> - 2001-04-26 09:49:22
|
On Tue, Apr 24, 2001 at 05:17:36PM -0500, Diego Zamboni wrote: > > ta...@ec... said: > > One thing that would be useful... installing some python modules with > > rox-base. We could have Choices, Savebox and Options included, which > > would cut down the size of some applications. > > I've been meaning to write Perl modules (sorry, I don't grok Python) for > handling Choices for some time. Maybe I'll get around to it someday, that > would make things easier for Perl programs. > > > Slight problem though: where do we put them? The default python search > > path only includes /usr/local/... (guess it depends where you > > installed it) which isn't very helpful, so we'd have to add more > > directories to it... (~/lib/rox-base, /usr/local/lib/rox-base, ... > > like Choices?) > > You could put them in some rox directory (/usr/local/rox/lib?) and have any > AppRun scripts that need them set the PYTHONPATH directory appropriately... > Hm... I see a chicken-and-egg problem somewhere in there (need the modules to > figure out the paths, need the path to find the modules). Will keep thinking > about it (in my copious free time). OK, how about something like Choices, but simpler (read-only). LIBDIRPATH is a list of directories to search for shared code, and defaults to: ~/lib:/usr/local/lib:/usr/lib You could then install the shared code using rox-base into any of those directories, in a subdirectory called 'rox-base'. 'rox-base' would be like an application directory, with subdirectories 'python', 'perl', etc. It could (optionally) also have Help (library documentation), .DirIcon and even AppRun (display the version number and a brief summary?). Python programs would search for rox-base and then add rox-base/python to their search path. Of course, this could be extended to C libraries later... (but that'll have it's own headaches ;-) Comments? -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Thomas L. <ta...@ec...> - 2001-04-29 16:44:58
|
On Thu, Apr 26, 2001 at 10:48:43AM +0100, Thomas Leonard wrote: [ shared libraries ] > OK, how about something like Choices, but simpler (read-only). > LIBDIRPATH is a list of directories to search for shared code, and > defaults to: > ~/lib:/usr/local/lib:/usr/lib > > You could then install the shared code using rox-base into any of those > directories, in a subdirectory called 'rox-base'. > > 'rox-base' would be like an application directory, with subdirectories > 'python', 'perl', etc. It could (optionally) also have Help (library > documentation), .DirIcon and even AppRun (display the version number and a > brief summary?). > Python programs would search for rox-base and then add rox-base/python to > their search path. Right, I've created a new module in CVS, 'ROX-Lib'. Check that out into ~/lib and it's installed :-) CVS Archive now uses it (this needs testing!). ROX-Lib currently only contains python modules: choices Lets you load and save user choices easily SaveBox Does drag-and-drop saving MultipleChoice Gives you a dialog box with any number of buttons All need testing... Modules for other languages can be added here too (PERL?). -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Stephen W. <wa...@ul...> - 2001-04-25 08:44:43
|
In message <200...@ev...> Thomas Leonard <ta...@ec...> scribbled: > On Mon, Apr 23, 2001 at 12:22:23PM +0100, Stephen Watson wrote: > > [...] > > Have we enough common code yet in the filer and various apps to make a > > library worthwhile? > > One thing that would be useful... installing some python modules with > rox-base. We could have Choices, Savebox and Options included, which would > cut down the size of some applications. I've put a python InfoWin widget at <URL:http://www.kerofin.demon.co.uk/rox/> (don't download the current Clock or Load archives, they have broken links in them!). -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Stephen W. <wa...@ul...> - 2001-04-25 10:16:19
|
In message <3dc...@wa...> Stephen Watson <wa...@ul...> scribbled: > (don't download the current Clock or Load archives, they have broken links > in them!). Actually that's a lie. SparkFS gets confused by symlinks in tar archives, poor thing. They are OK. -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Thomas L. <ta...@ec...> - 2001-04-25 13:29:15
|
On Sat, Apr 21, 2001 at 04:32:31PM +0100, Thomas Leonard wrote: > I'm wondering whether to replace AppMenu with a general-purpose > AppInfo.xml file. Menu items would be part of it, but we could add other > stuff like: > > - A tooltip for the application. OK, this is working now. Put a <Summary> tag in AppInfo.xml to get a tooltip on your application, eg: <?xml version="1.0"?> <AppInfo> <Summary>Create or read archive files. Such files usually have names ending in .gz, .tar, .tgz, .bz2 or .zip.</Summary> <AppMenu> ... </AppMenu> </AppInfo> The old AppMenu files are still supported (for backwards compatibility). -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |