Re: [cssed-devel] New test feature
Brought to you by:
iagorubio
From: Jeremy G. <j....@lo...> - 2004-03-11 19:10:13
|
On Thu, 2004-03-11 at 08:22, Iago Rubio wrote: > Hi all, > > I'm testing a new feature in cssed. > > In non technicall words, this feature will let cssed to be opened one > time, and from this point all other atempts to open a file with it, will > redirect the action to the running instance. > Sounds cool, will give it a try. > This way - as example - if you associate the css file type with cssed, > and you've got one instance of cssed running, the next time you open a > css file from your filebrowser, it will be opened in the cssed instance > you are working. > > Bluefish users know this behaviour. > > This feature is filebrowser independent and also works if you use the > console. > > I've got an initial test done, but I'm not sure if I will put it to work > in a release. > > There're lots of things to do with it, but I'd like to know if it's > interesting. If it's not, I will not work further on it ;) > > You've got an snapshot with this feature enabled here > http://cssed.sourceforge.net/cssed-0.2.0-ipc-11_3_2004.tar.gz > > It have not been tested so far, and It have some improvments to be done > ( as signal handling ), in the case of left it as an option. > > I'm not sure to add it in the release, because there must be a thread > running waiting for actions from other cssed instances. > > I'm afraid of resurce consumption in very low-end systems ( it's tested > in a Pentium 100 with 32 Mb/RAM and it works quite well, but if we > continue to add this kind of features, cssed will not work in this type > of systems ;) > > Any opinions or ideas ? > > If any of you want a technicall description of this feature, just ask > for it ;) but it's based on ipc System-V message queues, so must work in > any *nix system. Just read main.c ( this is test code that will be moved > to a separate file if we decide to use it ). > > * How to test it ? > > Compile the snapshot cd into the /src folder and type: > > ./cssed utils.c& ( as example ) > ./cssed utils.c& > ./cssed utils.c& > > All files must be opened in the first cssed's instance. > > Some debug output will be printed. > > You can also use the following command, in a separate console, to see > what's going on in the background. > > $ watch ipcs -q > > > Feedback please ;) -Jeremy |