From: Thomas L. <ta...@le...> - 2000-09-02 17:46:04
|
It's been pointed out to me that ROX-Session is rather out-of-date! I've make lots of changes and committed the new version to CVS. It should be much simpler to install - just compile it and run and it should offer to write your .xsession file for you. Could someone with CVS check that it works and creates sensible files? Take care of your old .xsession files, just in case! Let me know if it works, particularly on 'odd' systems... Thanks, Thomas Leonard -- tal197 at users.sourceforge.net The ROX desktop (free/GPL) : http://rox.sourceforge.net |
From: Stephen W. <wa...@ul...> - 2000-11-03 11:35:34
|
ROX-Session 0.1.9 on Solaris 7 fails when running MakeDefault.sh Script started on Fri 03 Nov 2000 11:25:30 GMT laurel:~/Apps ROX-Session/AppRun /home/stephen/Apps/ROX-Session/MakeDefault.sh: test: argument expected laurel:~/Apps sh -x ROX-Session/MakeDefault.sh + cd + [ -L .xsession ] ROX-Session/MakeDefault.sh: test: argument expected laurel:~/Apps ls -l /bin/sh /usr/local/bin/bash -r-xr-xr-x 3 bin root 91668 Oct 6 1998 /bin/sh -rwxr-xr-x 1 root other 2558160 Nov 9 1999 /usr/local/bin/bash In other words MakeDefault.sh is expecting /bin/sh to be a link to bash. -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Thomas A L. <ta...@ec...> - 2000-11-14 16:24:48
|
On Fri, 3 Nov 2000, Stephen Watson wrote: > ROX-Session 0.1.9 on Solaris 7 fails when running MakeDefault.sh [...] > In other words MakeDefault.sh is expecting /bin/sh to be a link to bash. Try the latest CVS version; I think Bernard has already fixed this... Thomas Leonard -- ta...@ec... |
From: Thomas L. <ta...@le...> - 2000-11-25 11:34:50
|
Since the last version was rather buggy, it's probably time for a new release! Could people check that the cvs snapshot of ROX-Session is OK? If so, I'll release 0.1.10 next week. Thomas Leonard -- tal197 at users.sourceforge.net The ROX desktop (free/GPL) : http://rox.sourceforge.net |
From: Andy P. <squ...@uk...> - 2000-11-26 12:03:51
|
Thomas Leonard wrote: > > Since the last version was rather buggy, it's probably time for a new > release! > > Could people check that the cvs snapshot of ROX-Session is OK? If so, I'll > release 0.1.10 next week. Unless I'm missing something, it won't compile out of CVS using the documented method (the AppRun script) - I had to go into the src/ directory and run autoconf first, as the configure script was missing. I'll issue an RPM once 0.1.10 is out. -- Andy Piper - Fareham, Hampshire (UK) - ICQ #86489434 and...@fr... | an...@un... * OpenUT for Linux | http://openut.sourceforge.net * Unreal Tournament News | http://www.unrealtournament.org |
From: Thomas A L. <ta...@ec...> - 2000-11-27 14:47:37
|
On Sun, 26 Nov 2000, Andy Piper wrote: > Thomas Leonard wrote: > > > > Since the last version was rather buggy, it's probably time for a new > > release! > > > > Could people check that the cvs snapshot of ROX-Session is OK? If so, I'll > > release 0.1.10 next week. > > Unless I'm missing something, it won't compile out of CVS using the > documented method (the AppRun script) - I had to go into the src/ > directory and run autoconf first, as the configure script was missing. The snapshot should have it created for you. It's not in the main repository since the file is autogenerated... > I'll issue an RPM once 0.1.10 is out. Thanks. Are you planning to include some default files for the panel? Eg: /usr/share/Choices/ROX-Filer/pan_Default Probably just needs: - the user's home directory, - a logout button, - /usr/apps, - / I wonder if we can get the post-install to add everything in /mnt? Thomas Leonard -- ta...@ec... |
From: Andy P. <squ...@uk...> - 2000-11-27 19:21:20
|
Thomas A Leonard wrote: > > On Sun, 26 Nov 2000, Andy Piper wrote: > > > Unless I'm missing something, it won't compile out of CVS using the > > documented method (the AppRun script) - I had to go into the src/ > > directory and run autoconf first, as the configure script was missing. > > The snapshot should have it created for you. It's not in the main > repository since the file is autogenerated... I'm *sure* I'm being thick here - but where from? Couldn't see any snapshots, so I took stuff straight out of CVS, and it wouldn't build :-( although it was a simple matter to run autoconf myself. > > I'll issue an RPM once 0.1.10 is out. > > Thanks. Are you planning to include some default files for the panel? Could do! > I wonder if we can get the post-install to add everything in /mnt? We could - but is that a good idea? Well, actually, I can't think of any circumstances where it would be a Bad Thing, so I'll wait to see if anyone else can come up with a reason 8-) -- Andy Piper - Fareham, Hampshire (UK) - ICQ #86489434 and...@fr... | an...@un... * OpenUT for Linux | http://openut.sourceforge.net * Unreal Tournament News | http://www.unrealtournament.org |
From: Stephen W. <wa...@ul...> - 2000-11-29 08:36:01
|
In message <3A2...@uk...> Andy Piper <squ...@uk...> scribbled: > Thomas A Leonard wrote: > > I wonder if we can get the post-install to add everything in /mnt? > > We could - but is that a good idea? Well, actually, I can't think of > any circumstances where it would be a Bad Thing, so I'll wait to see > if anyone else can come up with a reason 8-) What were you planning to put in /mnt? Under Solaris it is an ordinary directory, the traditional mount point for anything that doesn't have its own mount point. -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Andy P. <squ...@uk...> - 2000-11-29 19:51:35
|
Stephen Watson wrote: > > In message <3A2...@uk...> > Andy Piper <squ...@uk...> scribbled: > > > Thomas A Leonard wrote: > > > I wonder if we can get the post-install to add everything in /mnt? > > > > We could - but is that a good idea? Well, actually, I can't think of > > any circumstances where it would be a Bad Thing, so I'll wait to see > > if anyone else can come up with a reason 8-) > > What were you planning to put in /mnt? Under Solaris it is an ordinary > directory, the traditional mount point for anything that doesn't have its own > mount point. Possibly some confusion here - we're not proposing to put anything *in* /mnt, but Thomas was suggesting that any directories under /mnt should be added to the panel as part of the RPM post-install stage... on my Linux system for example, that would be /mnt/cdrom, /mnt/floppy, /mnt/win (for my Windows partition), and others. So, in theory it would add the user's drives to the icon bar / panel. The reason I posed the "good idea?" question was exactly the sort of thing you've pointed out... people may mount filing systems on /mnt itself, or elsewhere entirely. So it's a little hard to gauge what we should do! -- Andy Piper - Fareham, Hampshire (UK) - ICQ #86489434 and...@fr... | an...@un... * OpenUT for Linux | http://openut.sourceforge.net * Unreal Tournament News | http://www.unrealtournament.org |
From: Tim W. <tw...@re...> - 2000-11-29 23:12:12
|
On Wed, Nov 29, 2000 at 07:51:14PM +0000, Andy Piper wrote: > Possibly some confusion here - we're not proposing to put anything > *in* /mnt, but Thomas was suggesting that any directories under /mnt > should be added to the panel as part of the RPM post-install stage... Scanning /etc/fstab seems like a cleaner way of doing this, and won't cause trouble with automounters. Tim. */ |
From: Stephen W. <wa...@ul...> - 2000-11-30 14:58:16
|
In message <200...@re...> Tim Waugh <tw...@re...> scribbled: > On Wed, Nov 29, 2000 at 07:51:14PM +0000, Andy Piper wrote: > > > Possibly some confusion here - we're not proposing to put anything > > *in* /mnt, but Thomas was suggesting that any directories under /mnt > > should be added to the panel as part of the RPM post-install stage... > > Scanning /etc/fstab seems like a cleaner way of doing this, and won't > cause trouble with automounters. Sometimes known as /etc/vfstab -- Stephen Watson wa...@ul... Ultra Electronics Magnetics Division, Hednesford. |
From: Thomas A L. <ta...@ec...> - 2000-12-01 12:42:26
|
On Mon, 27 Nov 2000, Andy Piper wrote: > Thomas A Leonard wrote: [ ROX-Session ] > > Thanks. Are you planning to include some default files for the panel? > > Could do! Thinking about this a bit more, it might be better to get the filer to autogenerate pan_default as a special case, rather than putting it in the ROX-Session RPM. The advantage is, people using the tarball get a sensible default too... Thomas Leonard -- ta...@ec... |
From: Andy P. <squ...@uk...> - 2000-12-03 20:58:31
|
Thomas A Leonard wrote: > Thinking about this a bit more, it might be better to get the filer to > autogenerate pan_default as a special case, rather than putting it in the > ROX-Session RPM. > > The advantage is, people using the tarball get a sensible default too... So, are you saying that will that go into 0.1.30? (or 1.0.0-pre4-test10? ;-) -- Andy Piper - Fareham, Hampshire (UK) - ICQ #86489434 and...@fr... | an...@un... * OpenUT for Linux | http://openut.sourceforge.net * Unreal Tournament News | http://www.unrealtournament.org |
From: Thomas A L. <ta...@ec...> - 2000-12-04 18:19:16
|
On Sun, 3 Dec 2000, Andy Piper wrote: > Thomas A Leonard wrote: > > Thinking about this a bit more, it might be better to get the filer to > > autogenerate pan_default as a special case, rather than putting it in the > > ROX-Session RPM. > > > > The advantage is, people using the tarball get a sensible default too... > > So, are you saying that will that go into 0.1.30? (or > 1.0.0-pre4-test10? ;-) OK, OK, time for a release! I've made the filer put Home and Apps on new panels instead of leaving them blank. (Apps is the directory containing ROX-Filer). If this works it'll be 0.1.30 and then we'll do 1.0.0 quickly before anyone has a chance to report any bugs ;-) Test it! Thomas Leonard -- ta...@ec... |
From: Thomas L. <ta...@ec...> - 2001-03-23 15:58:46
|
Minor update to ROX-Session: When the window manager quits, the choice box defaults to the last used command (so it's easy to restart the same program). If no-one has any problems with this version, I'll make a new release in a couple of days... -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Thomas L. <ta...@ec...> - 2002-01-29 17:29:27
|
I'm planning to do a new ROX-Session release tomorrow, as the current version is rather out-of-date. There are no major changes, just a couple of new window mangers on the default list, use of AppInfo.xml instead of AppMenu (which ROX-Filer no longer supports) and an updated AppRun and configure.in (same changes as were made to the filer quite a while ago). It also no longer sets LD_LIBRARY_PATH to ~/lib. Very few people will have Gtk+ installed there, and it slows everything down. I backed out all the session management stuff after realising XSMP doesn't do what I want. There was some vague enthusiasm on the xdg list for a new protocol, so I may investigate that in the future. Anyway, please test the CVS snaphot: http://rox.sourceforge.net/snapshots/ -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... |
From: Thomas L. <ta...@ec...> - 2002-09-12 10:43:34
|
I'm planning to do another ROX-Session release soon. Changes are: - Window manager can be a full command (not just a program name). - If lots of errors are displayed then it switches to the log window format automatically. - The log window has a much larger history. - Log messages get a timestamp added (if it's more that 1 minute since the last timestamp). - Errors from ROX-Session itself (eg, font errors) aren't logged (this could cause deadlock). CVS snapshots are up-to-date: http://rox.sourceforge.net/snapshots/ Testing and translations welcome... -- Thomas Leonard http://rox.sourceforge.net ta...@ec... ta...@us... GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Tony H. <h...@re...> - 2006-10-17 12:37:08
|
I'm still using a patched version of ROX-Session 0.26 because when I first tried the Python version I found that many of the session options weren't implemented. What's the status of these now? I'm thinking it's about time I upgraded. I've got an idea for an improvement if it hasn't been done already. When looking at the message log it can be difficult to tell which messages are coming from which application. Can ROX-Session sort out what's coming from where (perhaps needing ROX-Filer's cooperation for stuff launched from there instead of directly by ROX-Session) and prefix the messages with the pid or something? -- TH * http://www.realh.co.uk |
From: Jonatan L. <li...@ky...> - 2006-10-17 12:53:22
|
Tony Houghton wrote: > I'm still using a patched version of ROX-Session 0.26 because when I > first tried the Python version I found that many of the session options > weren't implemented. What's the status of these now? I'm thinking it's > about time I upgraded. BTW, what was the purpose of porting it to python? Now I always need python running, and it's huge. Right now it takes 20MB mem here, only to run a simple session manager that actually does nothing but monitoring the windowmanager and rox-filer, and handling settings requests through dbus... I think ROX-Session should be ported back to sweet lightweight C, or integrated into ROX-Filer. =) -- /Jonatan -=( http://kymatica.com )=- |
From: Jim R. <i....@ji...> - 2006-10-17 13:21:41
|
Jonatan Liljedahl <li...@ky...> wrote: > I think ROX-Session should be ported back to sweet lightweight C, or > integrated into ROX-Filer. =) I vote for integration with ROX-Filer. It would be nice to have a clean way to start up and shut down all ROX panels at once, especially in an environment such as compiz or beryl where the "window manager" doesn't include *any* session management whatsoever. This way I could use my rox panel with its new fancy integrated "logout" function as the thing I exec on the last line of my .xinitrc -- Jim Ramsay "Me fail English? That's unpossible!" |
From: Ken H. <ke...@ha...> - 2006-10-17 13:34:31
|
Jim Ramsay wrote: > Jonatan Liljedahl <li...@ky...> wrote: >> I think ROX-Session should be ported back to sweet lightweight C, or >> integrated into ROX-Filer. =) > > I vote for integration with ROX-Filer. It would be nice to have a > clean way to start up and shut down all ROX panels at once, especially > in an environment such as compiz or beryl where the "window manager" > doesn't include *any* session management whatsoever. > > This way I could use my rox panel with its new fancy integrated > "logout" function as the thing I exec on the last line of my .xinitrc Does this mean you're NOT using ROX-Session now? It does that you know. For me, I like it fine the way it is. 20MB out of 1.5GB is not much to worry about :). And since I'm running several other python utilities, most of that 20MB is shared with something else, or swapped out when not in use. Unless anyone is interested in porting stuff to D? |
From: Thomas L. <ta...@gm...> - 2006-10-17 17:55:02
|
On 10/17/06, Ken Hayber <ke...@ha...> wrote: > Jim Ramsay wrote: > > Jonatan Liljedahl <li...@ky...> wrote: > >> I think ROX-Session should be ported back to sweet lightweight C, or > >> integrated into ROX-Filer. =) The trouble with the C version was that it would crash on startup every time you upgraded D-BUS, and getting it to support all the versions was very difficult. Python makes it easier to support several APIs, and if it fails you get a stack trace box (from which you can launch Edit, fix the problem, and log in again!). > For me, I like it fine the way it is. 20MB out of 1.5GB is not much to > worry about :). And since I'm running several other python utilities, > most of that 20MB is shared with something else, or swapped out when not > in use. gexmap[1] reports the "Effective Resident" as 8 Mb here. I think the problem is mostly with pygtk. Running 'python', it starts at 1.5 Mb, going to 4.4 Mb as soon as you 'import gtk'. > Unless anyone is interested in porting stuff to D? How complete is the gcc backend now? It needs to be portable. I'm quite tempted to provide a D compiler through Zero Install and add it to the build deps in the interface. We'd need to try it on something less core than ROX-Session first, though ;-) [1] http://www.berthels.co.uk/exmap/ -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |
From: Ken H. <ke...@ha...> - 2006-10-18 01:04:21
|
Thomas Leonard wrote: > On 10/17/06, Ken Hayber <ke...@ha...> wrote: >> Jim Ramsay wrote: >>> Jonatan Liljedahl <li...@ky...> wrote: >>>> I think ROX-Session should be ported back to sweet lightweight C, or >>>> integrated into ROX-Filer. =) <snip> > >> Unless anyone is interested in porting stuff to D? > > How complete is the gcc backend now? It needs to be portable. I'm > quite tempted to provide a D compiler through Zero Install and add it > to the build deps in the interface. We'd need to try it on something > less core than ROX-Session first, though ;-) Well, I'm happily surprised that I wasn't lol'ed for the suggestion. Gentoo doesn't have an ebuild yet (but I think there is a portage overlay with one, possibly in break-my-gentoo). I had started to do my own build at one point and never finished it. So far all I've done is play with the Windows version at work. http://dgcc.sourceforge.net has several binaries and source available for download - current as of July, 2006, v0.19 |
From: Tony H. <h...@re...> - 2006-10-17 19:11:59
|
In <cd5...@ma...>, Thomas Leonard wrote: > On 10/17/06, Ken Hayber <ke...@ha...> wrote: > > Jim Ramsay wrote: > > > Jonatan Liljedahl <li...@ky...> wrote: > > >> I think ROX-Session should be ported back to sweet lightweight C, or > > >> integrated into ROX-Filer. =) > > The trouble with the C version was that it would crash on startup > every time you upgraded D-BUS, and getting it to support all the > versions was very difficult. The D-BUS API has pretty much stabilised now. -- TH * http://www.realh.co.uk |
From: Guido S. <__g...@we...> - 2006-10-17 23:03:54
|
On Tue, 17 Oct 2006 20:11:49 +0100 Tony Houghton <h...@re...> wrote: > In <cd5...@ma...>, Thomas Leonard wrote: > > > On 10/17/06, Ken Hayber <ke...@ha...> wrote: > > > Jim Ramsay wrote: > > > > Jonatan Liljedahl <li...@ky...> wrote: > > > >> I think ROX-Session should be ported back to sweet lightweight C, or > > > >> integrated into ROX-Filer. =) > > > > The trouble with the C version was that it would crash on startup > > every time you upgraded D-BUS, and getting it to support all the > > versions was very difficult. > > The D-BUS API has pretty much stabilised now. Why dbus messaging was used for X property change notification in the first place, when the X server protocol provides for a messaging system already, would be another matter to discuss ;-) Guido |