From hal9000 at hypermetrics.com Mon Nov 1 00:21:27 2004 From: hal9000 at hypermetrics.com (Hal Fulton) Date: Mon Nov 1 00:21:52 2004 Subject: [FR-devel] Re: Re: Introduction, SciTE lexer (earlier thread) In-Reply-To: <20041031181732.C42C3E4D11@mail03.solnet.ch> References: <417F46BE.4030303@space.ch> <20041031181732.C42C3E4D11@mail03.solnet.ch> Message-ID: <4185C7D7.9070402@hypermetrics.com> Kaspar Schiess wrote: > > I do this for a various reasons, but basically I succumbed finally to the > VIM envy I've been having for a number of months. I will look into > integration possibilities of VIM, since I find its Ruby support to be far > superior to SciTE. > Kaspar, What kind of Ruby support are you referring to? Syntax highlighting and indentation? Or more than that? Hal From eule at space.ch Mon Nov 1 03:56:57 2004 From: eule at space.ch (Kaspar Schiess) Date: Mon Nov 1 03:57:14 2004 Subject: [FR-devel] Re: Re: Re: Introduction, SciTE lexer (earlier thread) References: <20041031181732.C42C3E4D11@mail03.solnet.ch> <4185C7D7.9070402@hypermetrics.com> Message-ID: On 01 Nov 2004, you wrote in gmane.comp.ide.freeride.devel: > What kind of Ruby support are you referring to? Syntax highlighting > and indentation? Or more than that? Just a few random things... - The decision was made on discovering the nice way to specify syntax highlight, folding and autoindent in VIM. And then there is a very large language support (more languages than SciTE, which is very decent too). - You can script VIM by using the Ruby language. - Ruvi could be coming up next. - Folding is correct and has the summarize feature in vi. Sadly, the ctags/VIM combination does not yet do as much as FreeRIDE does towards code inspection. Couldn't the corresponding module be ripped out as a kind of Ruby ctags ? (Just typing this off the top of my head). And last but not least: One should really not compare the two, since VIM's learning curve is way steeper. But once one gets into it, it has a lot of advantages. What do you mean by 'more than that' ? I will be happy to provide you with more information. best regards, kaspar hand manufactured code - www.tua.ch/ruby From g.glueck at gmx.net Mon Nov 1 20:59:23 2004 From: g.glueck at gmx.net (=?iso-8859-1?q?G=FCnter_Gl=FCck?=) Date: Mon Nov 1 20:59:35 2004 Subject: [FR-devel] starting and stopping of plugins on user-demand Message-ID: <200411020259.23861.g.glueck@gmx.net> hi again, now after reviewing the plugin-management code, i've implemented the ability to start and stop plugins any time you want to. (just a few lines of code for now) For now i've added the proc-slots "start" and "stop" to every plugin-slot. Is this okay for you? While playing around with this ability and testing the effects of starting and stopping on demand, i found out a few things: * there are a few basic features missing the ability to unbind keys from the keys-manager the ability to delete a command from a menupane ... i've added these abilities, but i'm sure there are more of this kind missing * only those plugins are save to start and stop on demand which are responsible for their commands, keys, menu-items, ... so if a plugin adds commands, ... in their start-method they have to delete those commands in their stop-method. Also this is a logic restriction it is also possible reason to think about a alternative possibility for registering ui-facets. ( i think about the possibility to register ui-facets by the plugin-configuration-file) what do you think about this? (because i think it would make the life of plugin-developers easier) but for now i have one question: what about the gui for start & stop? i'm thinking about a few gui-alternatives for this topic, but i'm also very thankful of few proposals from you. G?nter Gl?ck (ggl) From curt at hibbs.com Mon Nov 1 21:10:03 2004 From: curt at hibbs.com (Curt Hibbs) Date: Mon Nov 1 21:10:12 2004 Subject: [FR-devel] starting and stopping of plugins on user-demand In-Reply-To: <200411020259.23861.g.glueck@gmx.net> Message-ID: G?nter Gl?ck wrote: > > hi again, > > now after reviewing the plugin-management code, i've implemented > the ability > to start and stop plugins any time you want to. (just a few lines > of code for > now) > > For now i've added the proc-slots "start" and "stop" to every plugin-slot. > Is this okay for you? Sure... that's the way I would have done it. > While playing around with this ability and testing the effects of > starting and > stopping on demand, i found out a few things: > > * there are a few basic features missing > the ability to unbind keys from the keys-manager > the ability to delete a command from a menupane > > ... i've added these abilities, but i'm sure there are more of > this kind > missing You're probably right. > * only those plugins are save to start and stop on demand which are > responsible for their commands, keys, menu-items, ... > so if a plugin adds commands, ... in their start-method they > have to delete > those commands in their stop-method. Also this is a logic > restriction it is > also possible reason to think about a alternative possibility for > registering ui-facets. ( i think about the possibility to > register ui-facets > by the plugin-configuration-file) what do you think about this? > (because i > think it would make the life of plugin-developers easier) As I was reading the beginning of your paragraph, this is precisely what I was thinking, also. It makes sense for plugins to "declare" their UI additions, so that adding and deleting them can be handled automatically by the plugin management code. > but for now i have one question: what about the gui for start & stop? > > i'm thinking about a few gui-alternatives for this topic, but i'm > also very > thankful of few proposals from you. Were you thinking about some kind of popup dialog that would list all plugins, their current state, and a way to change their state (e.g., start, stop, kill)? Curt From g.glueck at gmx.net Mon Nov 1 21:32:21 2004 From: g.glueck at gmx.net (=?iso-8859-1?q?G=FCnter_Gl=FCck?=) Date: Mon Nov 1 21:32:38 2004 Subject: [FR-devel] starting and stopping of plugins on user-demand In-Reply-To: References: Message-ID: <200411020332.21675.g.glueck@gmx.net> On Tuesday 02 November 2004 03:10, Curt Hibbs wrote: > > * only those plugins are save to start and stop on demand which are > > responsible for their commands, keys, menu-items, ... > > so if a plugin adds commands, ... in their start-method they > > have to delete > > those commands in their stop-method. Also this is a logic > > restriction it is > > also possible reason to think about a alternative possibility for > > registering ui-facets. ( i think about the possibility to > > register ui-facets > > by the plugin-configuration-file) what do you think about this? > > (because i > > think it would make the life of plugin-developers easier) > > As I was reading the beginning of your paragraph, this is precisely what I > was thinking, also. It makes sense for plugins to "declare" their UI > additions, so that adding and deleting them can be handled automatically by > the plugin management code. i'm glad to hear your compliance about my thoughts. I think its a topic which should be discussed in near future. > > > but for now i have one question: what about the gui for start & stop? > > > > i'm thinking about a few gui-alternatives for this topic, but i'm > > also very > > thankful of few proposals from you. > > Were you thinking about some kind of popup dialog that would list all > plugins, their current state, and a way to change their state (e.g., start, > stop, kill)? yes. that was exactly my first thought. and if are there no other (better) proposals i'm looking in this direction. But what do you mean with "kill"? isn't start & stop enough? G?nter Gl?ck (ggl) From g.glueck at gmx.net Mon Nov 1 23:24:11 2004 From: g.glueck at gmx.net (=?iso-8859-1?q?G=FCnter_Gl=FCck?=) Date: Mon Nov 1 23:24:22 2004 Subject: [FR-devel] reload plugin-code and configuration on user-demanded-start Message-ID: <200411020524.11395.g.glueck@gmx.net> hi, got a first version of the plugin-manager-gui working. looks minimalistic, but works :-) for now i'm looking for the chance to do a complete "reload" of a plugin. what i mean is to reload the whole code, and the whole plugin.yaml file. so if i'm a plugin-developer i'm very thankful if i have a tool to reload my plugin after changing the plugin-code to see if the new code does what i want. of course this ability comes with a few new problems (what if the plugin has an syntax-error?), but i think those problems are there to resolve them. but now (at 5:16 am - thats usualy my time of confusion :-) i can't really find the piece of code that loads the .rb-file. i'm sure i looked not good enough and it is in front of my eyes but i'm a little confused because of the Configuration class in FreeBASE. so, i would be very thankful about little help. thanks in advance and good night :-) G?nter Gl?ck (ggl) From g.glueck at gmx.net Mon Nov 1 23:46:08 2004 From: g.glueck at gmx.net (=?iso-8859-1?q?G=FCnter_Gl=FCck?=) Date: Mon Nov 1 23:46:19 2004 Subject: [FR-devel] feature-requests at summary-page (rubyforge-site) Message-ID: <200411020546.08987.g.glueck@gmx.net> sorry ... i'm awake :-) i've seen, that there is no feature-requests-link at the summary-page. where is it? ggl From curt at hibbs.com Tue Nov 2 09:20:40 2004 From: curt at hibbs.com (Curt Hibbs) Date: Tue Nov 2 09:20:50 2004 Subject: [FR-devel] starting and stopping of plugins on user-demand In-Reply-To: <200411020332.21675.g.glueck@gmx.net> Message-ID: G?nter Gl?ck wrote: > > > > Were you thinking about some kind of popup dialog that would list all > > plugins, their current state, and a way to change their state > (e.g., start, > > stop, kill)? > > yes. that was exactly my first thought. and if are there no other > (better) > proposals i'm looking in this direction. > But what do you mean with "kill"? isn't start & stop enough? Start and stop are probably enough, I was just writing whatever came into my mind. By kill I simply meant forcing a plugin to stop that wouldn't otherwise respond to the stop request. Curt From curt at hibbs.com Tue Nov 2 09:32:37 2004 From: curt at hibbs.com (Curt Hibbs) Date: Tue Nov 2 09:33:03 2004 Subject: [FR-devel] feature-requests at summary-page (rubyforge-site) In-Reply-To: <200411020546.08987.g.glueck@gmx.net> Message-ID: G?nter Gl?ck wrote: > > sorry ... i'm awake :-) > > i've seen, that there is no feature-requests-link at the summary-page. > where is it? There is now! Thanks for noticing this. There was a RubyForge option that I had to set to get this to appear on the Summary page. Curt From laurent at moldus.org Wed Nov 3 17:22:38 2004 From: laurent at moldus.org (Laurent Julliard) Date: Wed Nov 3 17:22:47 2004 Subject: [FR-devel] reload plugin-code and configuration on user-demanded-start In-Reply-To: <200411020524.11395.g.glueck@gmx.net> References: <200411020524.11395.g.glueck@gmx.net> Message-ID: <41895A2E.6030902@moldus.org> G?nter Gl?ck wrote: > hi, > > got a first version of the plugin-manager-gui working. looks minimalistic, but > works :-) > > for now i'm looking for the chance to do a complete "reload" of a plugin. > what i mean is to reload the whole code, and the whole plugin.yaml file. > so if i'm a plugin-developer i'm very thankful if i have a tool to reload my > plugin after changing the plugin-code to see if the new code does what i > want. > of course this ability comes with a few new problems (what if the plugin has > an syntax-error?), but i think those problems are there to resolve them. > > but now (at 5:16 am - thats usualy my time of confusion :-) i can't really > find the piece of code that loads the .rb-file. i'm sure i looked not good > enough and it is in front of my eyes but i'm a little confused because of the > Configuration class in FreeBASE. > > so, i would be very thankful about little help. > The heart of it is in freebase/lib/freebase/core.rb. Look at the initialize method and then in freebase/lib/freebase/configuration.rb is where the actual loading and starting is taking place. Hope this helps. And congrat's for the great work you are doing. I think all this goes in the right direction. > thanks in advance and good night :-) > > G?nter Gl?ck (ggl) > > _______________________________________________ > Freeride-devel mailing list > Freeride-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/freeride-devel > -- Laurent JULLIARD http://www.moldus.org/~laurent From curt at hibbs.com Tue Nov 9 14:12:03 2004 From: curt at hibbs.com (Curt Hibbs) Date: Tue Nov 9 14:11:56 2004 Subject: [FR-devel] FreeRIDE 0.7.0 is in the One-Click Installer. Message-ID: Laurent, The One-Click installer that I just released contains FreeRIDE 0.7.0 instead of 0.8.0 because the debugger was blowing up on me with 0.8.0. I'll look into this more later (I'm short on time at the moment), but I wanted to make you aware of it. Curt From gilles.filippini at free.fr Sat Nov 20 10:27:48 2004 From: gilles.filippini at free.fr (Gilles Filippini) Date: Sat Nov 20 10:27:24 2004 Subject: [FR-devel] ANNOUNCE: FXScintilla 1.62 Message-ID: <419F6274.7030402@free.fr> I'm pleased to announce the release of FXScintilla 1.62. FXScintilla is an implementation of the Scintilla source code editing component [1] for the FOX GUI toolkit [2]. Changes since the previous release (1.61): - upgraded to Scintilla-1.62 - Fox support defaults to Fox-1.2 - bug fixes FXScintilla homepage: http://www.nongnu.org/fxscintilla/ Downloads: http://savannah.nongnu.org/files/?group=fxscintilla Cheers, _gilles. [1] http://scintilla.org/ [2] http://fox-toolkit.org/ From wxruby at qualitycode.com Fri Nov 26 23:27:06 2004 From: wxruby at qualitycode.com (Kevin Smith) Date: Fri Nov 26 23:26:35 2004 Subject: [FR-devel] Troubles with freeride Message-ID: <41A8021A.3090108@qualitycode.com> Sometime recently, my freeride installation broke. It reverted to the unhelpful behavior of dumping a series of generic error messages upon startup. Last time that happened, it was because fox was not installed properly. I'm on gentoo (arch x86), and I think the problem was caused by my system flipping between fox 1.0 and fox 1.2. I have now corrected that by locking it (at 1.0.49). I uninstalled everything, reinstalled fxscintilla and then fox, and then tried to install fxruby (1.0.25), but it gives a compile error: FXRuby.cpp:64: error: declaration of C function `void st_foreach(st_table*, int (*)(char*, char*, char*), char*)' conflicts with /usr/lib/ruby/1.8/i686-linux/intern.h:249: error: previous declaration `void st_foreach(st_table*, int (*)(), long unsigned int)' here m I also tried to install fxruby 1.2 (ruby) via rubygems, but that gave me an error in extconf.rb: extconf.rb:30:in `find_installed_fox_version': couldn't find FOX header files (RuntimeError) from extconf.rb:155 I am aware of the one-file installer available for linux, but I *really* hate going outside the lovely package management built into my system. Any ideas? Kevin From laurent at moldus.org Sat Nov 27 02:46:26 2004 From: laurent at moldus.org (Laurent Julliard) Date: Sat Nov 27 02:45:46 2004 Subject: [FR-devel] Troubles with freeride In-Reply-To: <41A8021A.3090108@qualitycode.com> References: <41A8021A.3090108@qualitycode.com> Message-ID: <41A830D2.80905@moldus.org> Kevin Smith wrote: > Sometime recently, my freeride installation broke. It reverted to the > unhelpful behavior of dumping a series of generic error messages upon > startup. Last time that happened, it was because fox was not installed > properly. > > I'm on gentoo (arch x86), and I think the problem was caused by my > system flipping between fox 1.0 and fox 1.2. I have now corrected that > by locking it (at 1.0.49). I uninstalled everything, reinstalled > fxscintilla and then fox, and then tried to install fxruby (1.0.25), but > it gives a compile error: > > FXRuby.cpp:64: error: declaration of C function `void > st_foreach(st_table*, int > (*)(char*, char*, char*), char*)' conflicts with > /usr/lib/ruby/1.8/i686-linux/intern.h:249: error: previous declaration > `void > st_foreach(st_table*, int (*)(), long unsigned int)' here > m > > I also tried to install fxruby 1.2 (ruby) via rubygems, but that gave me > an error in extconf.rb: > > extconf.rb:30:in `find_installed_fox_version': couldn't find FOX header > files (RuntimeError) > from extconf.rb:155 > > I am aware of the one-file installer available for linux, but I *really* > hate going outside the lovely package management built into my system. > > Any ideas? Try using fox 1.0.53. This is what we use for the FR installer and we do not have any problem with it. I also strongly encourage you to use the FreeRIDE installer. On Linux it does install everything under /usr/local/FreeRIDE so it doesn't mess up too much with the rest of your pacakging system. Laurent -- Laurent JULLIARD http://www.moldus.org/~laurent From curt at hibbs.com Sat Nov 27 03:15:19 2004 From: curt at hibbs.com (Curt Hibbs) Date: Sat Nov 27 03:14:42 2004 Subject: [FR-devel] [ANN] FreeRIDE 0.9.0 Released! Message-ID: Version 0.9.0 of FreeRIDE has been released and is available for download! For details and downloads, go to: http://freeride.rubyforge.org/ Many bug fixes in this release especially on the Windows platform. There are also some new features: all dock panes can now be dock and undocked, Debugger and Script Runner works better on Win32, debugged process can be run in a console for Windows users to see the process output... Have fun! And, as always, feedback and contributions are welcome. === FreeRIDE Overview === FreeRIDE aims to be a full-featured, first-class IDE on a par with those available for other languages, with all the best-of-breed features that you would expect in a high-end IDE. Some of FreeRIDE's features include: * Multi-file editing * Syntax highlighting * Auto-indenting * Code Folding * Source navigation by module, class, method, etc. * Integrated debugging * Written in Ruby for easy extension Some planned features include: * Full internationalization * High-end refactoring support * Remote pair programming In its current state, FreeRIDE cannot yet be called a real IDE. What is does have is a stable infrastructure with all the working plumbing needed for the hordes of anxious Ruby developers that want to create plugins to extend the functionality of FreeRIDE. The FreeRIDE team will be working on such FreeRIDE plugins that we will individually release to incrementally improve the FreeRIDE system. Periodically we will rollup these added plugins into new releases of FreeRIDE. Even if you have not officially joined the FreeRIDE team you can still create plugins for you own use, share them with others, or send them to us and we will make them available for download from our project wiki. We may even ask for your permission to include them in the FreeRIDE core distribution. Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004 From wxruby at qualitycode.com Sat Nov 27 09:52:47 2004 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Nov 27 09:52:18 2004 Subject: [FR-devel] Troubles with freeride In-Reply-To: <41A830D2.80905@moldus.org> References: <41A8021A.3090108@qualitycode.com> <41A830D2.80905@moldus.org> Message-ID: <41A894BF.2000809@qualitycode.com> Laurent Julliard wrote: > Kevin Smith wrote: > >> I'm on gentoo (arch x86), and I think the problem was caused by my > I also strongly encourage you to use the > FreeRIDE installer. On Linux it does install everything under > /usr/local/FreeRIDE so it doesn't mess up too much with the rest of your > pacakging system. Sadly, the linux installer (0.9.0) isn't working for me either: Choose where to install FreeRIDE [/usr/local] : Installing FreeRIDE. Please wait... tail: cannot open `+61' for reading: No such file or directory gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error exit delayed from previous errors --------------------- MANIFEST --------------------- cat: /usr/local/FreeRIDE/MANIFEST: No such file or directory ---------------------------------------------------- FreeRIDE succesfully installed. Start FreeRIDE with '/usr/local/FreeRIDE/freeride' Kevin From laurent at moldus.org Sat Nov 27 13:29:54 2004 From: laurent at moldus.org (Laurent Julliard) Date: Sat Nov 27 13:29:11 2004 Subject: [FR-devel] Troubles with freeride In-Reply-To: <41A894BF.2000809@qualitycode.com> References: <41A8021A.3090108@qualitycode.com> <41A830D2.80905@moldus.org> <41A894BF.2000809@qualitycode.com> Message-ID: <41A8C7A2.2060600@moldus.org> Kevin Smith wrote: > Laurent Julliard wrote: > >> Kevin Smith wrote: >> >>> I'm on gentoo (arch x86), and I think the problem was caused by my > > >> I also strongly encourage you to use the FreeRIDE installer. On Linux >> it does install everything under /usr/local/FreeRIDE so it doesn't >> mess up too much with the rest of your pacakging system. > > > Sadly, the linux installer (0.9.0) isn't working for me either: > > > > Choose where to install FreeRIDE [/usr/local] : > Installing FreeRIDE. Please wait... > > tail: cannot open `+61' for reading: No such file or directory > > gzip: stdin: not in gzip format > tar: Child returned status 1 > tar: Error exit delayed from previous errors > --------------------- MANIFEST --------------------- > cat: /usr/local/FreeRIDE/MANIFEST: No such file or directory > ---------------------------------------------------- > FreeRIDE succesfully installed. > Start FreeRIDE with '/usr/local/FreeRIDE/freeride' > Can you run the installer with sh -x and send me the output. Thanks! -- Laurent JULLIARD http://www.moldus.org/~laurent From wxruby at qualitycode.com Sat Nov 27 13:57:19 2004 From: wxruby at qualitycode.com (Kevin Smith) Date: Sat Nov 27 13:57:03 2004 Subject: [FR-devel] Troubles with freeride In-Reply-To: <41A8C7A2.2060600@moldus.org> References: <41A8021A.3090108@qualitycode.com> <41A830D2.80905@moldus.org> <41A894BF.2000809@qualitycode.com> <41A8C7A2.2060600@moldus.org> Message-ID: <41A8CE0F.6060107@qualitycode.com> Laurent Julliard wrote: > Can you run the installer with sh -x and send me the output. Looks like my version of tail requires a -n before the +61 Here's the relevant sh -x output: + echo 'Installing FreeRIDE. Please wait...' Installing FreeRIDE. Please wait... + echo '' + tail +61 freeride-linux-installer-0.9.0.sh tail: cannot open `+61' for reading: No such file or directory + tar xz -C /usr/local gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error exit delayed from previous errors + echo '--------------------- MANIFEST ---------------------' --------------------- MANIFEST --------------------- FYI: root@aria download # tail --version tail (coreutils) 5.2.1 Kevin