[ANN] aeditor 1.0 released

ruby-talk
1

screenshots:
http://aeditor.rubyforge.org/wiki/wiki.pl?MainThemes

download:
http://rubyforge.org/frs/download.php/921/aeditor-1.0.tar.gz

dependency#1, iterator:
http://rubyforge.org/frs/download.php/703/iterator-0.8.tar.gz

dependency#2, fxruby
http://fxruby.sourceforge.net/
If you are on a windows box it may be possible that fxruby already
are installed.

on windows there are font problems.. you can make me happy if you can
make solve this problem. Thanks in advance.

I have attached my ~/.aeditor file, which may be interesting to you.

···

--
Simon Strandgaard

mode :ruby do |m|
  m.tabsize = 2
  m.file_suffixes = %w(rb)
  m.lexer = :ruby
  m.cursor_through_tabs = true
end

mode :c do |m|
  m.tabsize = 4
  m.file_suffixes = %w(c cpp cxx cc h hpp hxx hh)
  m.cursor_through_tabs = false
end

theme_blue = {
  :ivar1 => [[55, 75, 215], [40, 50, 120]],
  :mcomment_tab => [[30, 30, 120], [0, 0, 0]],
  :endoffile_tab => [[83, 83, 97], [0, 0, 0]],
  :string1 => [[65, 85, 225], [0, 0, 0]],
  :ident => [[55, 75, 215], [90, 80, 80]],
  :string => [[65, 85, 225], [30, 80, 0]],
  :keyword => [[60, 80, 220], [0, 0, 0]],
  :any => [[60, 80, 220], [30, 40, 20]],
  :ivar => [[60, 80, 200], [0, 0, 0]],
  :tab => [[30, 70, 190], [30, 40, 20]],
  :regexp => [[30, 80, 0], [165, 185, 25]],
  :space => [[60, 80, 220], [30, 40, 20]],
  :gvar => [[160, 180, 100], [90, 0, 0]],
  :heredoc => [[80, 60, 220], [30, 40, 20]],
  :regexp1 => [[60, 80, 180], [165, 185, 25]],
  :out => [[60, 60, 60], [180, 100, 100]],
  :dot => [[60, 80, 205], [0, 0, 0]],
  :symbol => [[30, 80, 220], [90, 80, 80]],
  :comment => [[60, 80, 120], [0, 0, 0]],
  :heredoc_tab => [[30, 70, 190], [30, 40, 20]],
  :punct => [[30, 80, 220], [120, 120, 120]],
  :empty => [[30, 30, 100], [0, 0, 0]],
  :dot1 => [[60, 80, 220], [0, 0, 0]],
  :mcomment => [[60, 80, 120], [0, 0, 0]],
  :endoffile => [[100, 100, 100], [0, 0, 0]],
  :number => [[65, 85, 225], [30, 80, 0]]
}

theme_gvim = {
  :ivar1 => [[55, 75, 215], [40, 50, 120]],
  :mcomment_tab => [[197, 197, 197], [231, 231, 231]],
  :endoffile_tab => [[209, 209, 209], [209, 209, 209]],
  :string1 => [[231, 231, 231], [0, 138, 142]],
  :ident => [[231, 231, 231], [0, 138, 142]],
  :string => [[231, 231, 231], [97, 101, 97]],
  :keyword => [[231, 231, 231], [158, 32, 239]],
  :any => [[231, 231, 231], [30, 40, 20]],
  :ivar => [[231, 231, 231], [0, 138, 142]],
  :tab => [[231, 231, 231], [231, 231, 231]],
  :regexp => [[30, 80, 0], [165, 185, 25]],
  :space => [[231, 231, 231], [30, 40, 20]],
  :gvar => [[160, 180, 100], [90, 0, 0]],
  :heredoc => [[231, 231, 231], [97, 101, 97]],
  :regexp1 => [[60, 80, 180], [165, 185, 25]],
  :out => [[60, 60, 60], [180, 100, 100]],
  :dot => [[231, 231, 231], [0, 0, 0]],
  :symbol => [[231, 231, 231], [0, 138, 142]],
  :comment => [[231, 231, 231], [0, 0, 255]],
  :heredoc_tab => [[209, 209, 209], [207, 211, 207]],
  :punct => [[231, 231, 231], [0, 0, 0]],
  :empty => [[30, 30, 100], [0, 0, 0]],
  :dot1 => [[60, 80, 220], [0, 0, 0]],
  :mcomment => [[231, 231, 231], [0, 0, 255]],
  :endoffile => [[231, 231, 231], [0, 0, 255]],
  :number => [[231, 231, 231], [97, 101, 97]]
}

def theme_import(theme_hash, name=nil)
  name ||= :imported
  theme name do |t|
    theme_hash.each do |key, (bg, fg)|
      t.set_rgb_pair key, bg, fg
    end
  end
end

theme_import(theme_blue, 'blue')
theme_import(theme_gvim, 'gvim')

puts "done loading config file"

2

Aeditor is a text editor with syntax highlighting?

  Sean O'Dell

···

On Sunday 04 July 2004 17:13, Simon Strandgaard wrote:

3

Hi,

At Mon, 5 Jul 2004 09:13:32 +0900,
Simon Strandgaard wrote in [ruby-talk:105240]:

mode :ruby do |m|
  m.tabsize = 2

Just a question; does this change tabstop size? Can it change
indent size regardless of tabstop?

···

--
Nobu Nakada

4

on windows there are font problems.. you can make me happy if you can
make solve this problem. Thanks in advance.

Making you happy:
@font.create is not executed before onCanvasPrepare, and the font thusly
accessed is invalid, causing segmentation fault. Solution proposed:

def create
  read_registry
  super # this is where it looses control
  @font_created = true
  @font.create
  @back_buffer.create
  @canvas.setFocus
  update_title
end

and then a

return unless @font_created

in onCanvasPrepare (at the very start). Problems with this solution are:
a race condition exists. You would have to do that with a semaphore or
other.

The speed of the whole editor seems to be very slow under windows with
Fox. Can I ask you again to the exact reason why another fully evolved
editor like SciTE will not do ?

best regards,

kaspar

semantics & semiotics
code manufacture

www.tua.ch/ruby

5

screenshots:
http://aeditor.rubyforge.org/wiki/wiki.pl?MainThemes

I hope I have fixed the font issues, so that it now works
on windows.

download:
http://rubyforge.org/frs/download.php/936/aeditor-1.1.tar.gz

I have also added a fontdialog.. so you can choose your
own font.

If you give it a shot, then please tell me how it works out.
I am especially curious to if it works on windows.
Ideas for improvements are very welcome.. If you manage
to make a nicer theme then please share the colors.
If something sux or is unacceptable slow, then please
also contact me.

I hope I havn't dissapointed anyone.

···

On Monday 05 July 2004 02:13, Simon Strandgaard wrote:

dependency#1, iterator:
http://rubyforge.org/frs/download.php/703/iterator-0.8.tar.gz

dependency#2, fxruby
http://fxruby.sourceforge.net/
If you are on a windows box it may be possible that fxruby already
are installed.

on windows there are font problems.. you can make me happy if you can
make solve this problem. Thanks in advance.

I have attached my ~/.aeditor file, which may be interesting to you.

--
Simon Strandgaard

mode :ruby do |m|
  m.tabsize = 2
  m.file_suffixes = %w(rb)
  m.lexer = :ruby
  m.cursor_through_tabs = true
end

mode :c do |m|
  m.tabsize = 4
  m.file_suffixes = %w(c cpp cxx cc h hpp hxx hh)
  m.cursor_through_tabs = false
end

theme_blue = {

  :ivar1 => [[55, 75, 215], [40, 50, 120]],
  :mcomment_tab => [[30, 30, 120], [0, 0, 0]],
  :endoffile_tab => [[83, 83, 97], [0, 0, 0]],
  :string1 => [[65, 85, 225], [0, 0, 0]],
  :ident => [[55, 75, 215], [90, 80, 80]],
  :string => [[65, 85, 225], [30, 80, 0]],
  :keyword => [[60, 80, 220], [0, 0, 0]],
  :any => [[60, 80, 220], [30, 40, 20]],
  :ivar => [[60, 80, 200], [0, 0, 0]],
  :tab => [[30, 70, 190], [30, 40, 20]],
  :regexp => [[30, 80, 0], [165, 185, 25]],
  :space => [[60, 80, 220], [30, 40, 20]],
  :gvar => [[160, 180, 100], [90, 0, 0]],
  :heredoc => [[80, 60, 220], [30, 40, 20]],
  :regexp1 => [[60, 80, 180], [165, 185, 25]],
  :out => [[60, 60, 60], [180, 100, 100]],
  :dot => [[60, 80, 205], [0, 0, 0]],
  :symbol => [[30, 80, 220], [90, 80, 80]],
  :comment => [[60, 80, 120], [0, 0, 0]],
  :heredoc_tab => [[30, 70, 190], [30, 40, 20]],
  :punct => [[30, 80, 220], [120, 120, 120]],
  :empty => [[30, 30, 100], [0, 0, 0]],
  :dot1 => [[60, 80, 220], [0, 0, 0]],
  :mcomment => [[60, 80, 120], [0, 0, 0]],
  :endoffile => [[100, 100, 100], [0, 0, 0]],
  :number => [[65, 85, 225], [30, 80, 0]]

}

theme_gvim = {

  :ivar1 => [[55, 75, 215], [40, 50, 120]],
  :mcomment_tab => [[197, 197, 197], [231, 231, 231]],
  :endoffile_tab => [[209, 209, 209], [209, 209, 209]],
  :string1 => [[231, 231, 231], [0, 138, 142]],
  :ident => [[231, 231, 231], [0, 138, 142]],
  :string => [[231, 231, 231], [97, 101, 97]],
  :keyword => [[231, 231, 231], [158, 32, 239]],
  :any => [[231, 231, 231], [30, 40, 20]],
  :ivar => [[231, 231, 231], [0, 138, 142]],
  :tab => [[231, 231, 231], [231, 231, 231]],
  :regexp => [[30, 80, 0], [165, 185, 25]],
  :space => [[231, 231, 231], [30, 40, 20]],
  :gvar => [[160, 180, 100], [90, 0, 0]],
  :heredoc => [[231, 231, 231], [97, 101, 97]],
  :regexp1 => [[60, 80, 180], [165, 185, 25]],
  :out => [[60, 60, 60], [180, 100, 100]],
  :dot => [[231, 231, 231], [0, 0, 0]],
  :symbol => [[231, 231, 231], [0, 138, 142]],
  :comment => [[231, 231, 231], [0, 0, 255]],
  :heredoc_tab => [[209, 209, 209], [207, 211, 207]],
  :punct => [[231, 231, 231], [0, 0, 0]],
  :empty => [[30, 30, 100], [0, 0, 0]],
  :dot1 => [[60, 80, 220], [0, 0, 0]],
  :mcomment => [[231, 231, 231], [0, 0, 255]],
  :endoffile => [[231, 231, 231], [0, 0, 255]],
  :number => [[231, 231, 231], [97, 101, 97]]

}

def theme_import(theme_hash, name=nil)
  name ||= :imported
  theme name do |t|
    theme_hash.each do |key, (bg, fg)|
      t.set_rgb_pair key, bg, fg
    end
  end
end

theme_import(theme_blue, 'blue')
theme_import(theme_gvim, 'gvim')

puts "done loading config file"

6

yes.. I forgot to mention that.. I am a little tired.

features:
syntax coloring.. (2 lexers at the moment: ruby, plaintext).
its able to do recognize heredocs spanning over multiple lines,
also multiline comments.. and correctly deal with the __END__ tag.

bookmarks.. F8=inserts/removes anonymonus bookmark.
F9=jumps to next anonymous bookmark.

swaplines.. Shift-Up, moves the current line up.
Shift-Down, moves the current line down.

indent/unindent.. Shift-Left unindents, Shift-Right indents.

selections.. F5=enable/disable selection mode, F6=paste, F7=cut.

search/replace.

multiple buffers.

sideways scrolling are fairly ok.

autoindent.

maybe there are more features?

···

On Monday 05 July 2004 02:19, Sean O'Dell wrote:

On Sunday 04 July 2004 17:13, Simon Strandgaard wrote:

Aeditor is a text editor with syntax highlighting?

--
Simon Strandgaard

7

no.. sorry, not at the moment.

I did some experiements with the old aeditor. I will add it to the todo list.

it uses strategy pattern for editing strategies.
It has ThrougTabs, Tabs, VirtualSpace and Normal.
I guess it could be implemented by adding an extra strategy.

···

On Monday 05 July 2004 02:45, nobu.nokada@softhome.net wrote:

At Mon, 5 Jul 2004 09:13:32 +0900,
Simon Strandgaard wrote in [ruby-talk:105240]:
> mode :ruby do |m|
> m.tabsize = 2

Just a question; does this change tabstop size? Can it change
indent size regardless of tabstop?

--
Simon Strandgaard

8

Making you happy:
@font.create is not executed before onCanvasPrepare, and the font thusly
accessed is invalid, causing segmentation fault. Solution proposed:

well, it's strange anyway that on linux this does work :confused:

The speed of the whole editor seems to be very slow under windows with
Fox. Can I ask you again to the exact reason why another fully evolved
editor like SciTE will not do ?

I believe the author actually does not only wants to build an editor.
He's even writing an opponent to the Scintilla library,
see this:
http://aeditor.rubyforge.org/faq.html

···

il Mon, 5 Jul 2004 23:40:53 +0900, Kaspar Schiess <eule@space.ch> ha scritto::

9

> on windows there are font problems.. you can make me happy if you can
> make solve this problem. Thanks in advance.

Making you happy:
@font.create is not executed before onCanvasPrepare, and the font thusly
accessed is invalid, causing segmentation fault. Solution proposed:

Wonderful!

def create
  read_registry
  super # this is where it looses control
  @font_created = true
  @font.create
  @back_buffer.create
  @canvas.setFocus
  update_title
end

and then a

return unless @font_created

I had assumed that #create was invoked before anything else.
but not realized this could be a problem.. (even though I have tried on 2 of
my friends windows boxes.. changing random things in the code).

in onCanvasPrepare (at the very start). Problems with this solution are:
a race condition exists. You would have to do that with a semaphore or
other.

I will browse fox's souce code to investigate this further.

The speed of the whole editor seems to be very slow under windows with
Fox.

how slow? there is outputed timing information to the console.
may I ask about details.

one time when I tried on windows I had really poor performance.
it took 10 seconds to render one frame. On my 700MHz linux box it
takes 0.05 seconds to lex+render one frame.

I have no explanaition if the slowdown is greater than 1 second.

Suggestions how to track it down are appreciated.

Can I ask you again to the exact reason why another fully evolved
editor like SciTE will not do ?

Im obsessed by ruby. I want to be able to write plugins in Ruby.
I want to be able to do changes in the editor core via plugins.
It is not possible with Scintilla to have so much freedom in the
plugins. What I want is maybe emacs ala ruby?

At some point it could be interesting to integrate my editor widget into
freeride, and see what happens.

best regards,

kaspar

Thanks Kaspar for making me happy :slight_smile:

···

On Monday 05 July 2004 16:40, Kaspar Schiess wrote:

--
Simon Strandgaard

10

I will not argue the merits of (potentially) reinventing the wheel
here. But as for the speed issue, bear in mind that SciTE is compiled
C++ code, and Simon's editor is written in Ruby. If AEditor was
written directly in C++, I think it's safe to say you'd see
performance much more comparable to SciTE's.

···

On Mon, 5 Jul 2004 23:40:53 +0900, Kaspar Schiess <eule@space.ch> wrote:

The speed of the whole editor seems to be very slow under windows with
Fox. Can I ask you again to the exact reason why another fully evolved
editor like SciTE will not do?

11

Simon Strandgaard wrote:

If you give it a shot, then please tell me how it works out.
I am especially curious to if it works on windows.
Ideas for improvements are very welcome.. If you manage
to make a nicer theme then please share the colors.
If something sux or is unacceptable slow, then please
also contact me.

Thank you for your effort, sorry for not answering. I have tried this
version, but there seems to be another issue here (see attached file).
Can anyone confirm this on windows ? I don't know what that is since I
haven't had the time to trace this...

btw: ruby 1.8.1 (2003-12-25) [i386-mingw32]

best regards,
kaspar

semantics & semiotics
code manufacture

www.tua.ch/ruby

run.txt (7.02 KB)

12

gabriele renzi wrote:

He's even writing an opponent to the Scintilla library,

Ah. Opponent-based software. Yes, I think I seen some of that lately.

:slight_smile:

James, teasing.

13

Hello Simon,

Can I ask you again to the exact reason why another fully evolved
editor like SciTE will not do ?

Im obsessed by ruby. I want to be able to write plugins in Ruby.
I want to be able to do changes in the editor core via plugins.
It is not possible with Scintilla to have so much freedom in the
plugins. What I want is maybe emacs ala ruby?

emacs has about 100.000 lines of C code to avoid the slowness of
elisp. This are not inside files like buffer.c and do not belong to
the lisp interpreter core.

···

--
Best regards, emailto: scholz at scriptolutions dot com
Lothar Scholz http://www.ruby-ide.com
CTO Scriptolutions Ruby, PHP, Python IDE 's

14

Simon Strandgaard wrote:

> Can I ask you again to the exact reason why another fully evolved
> editor like SciTE will not do ?

Im obsessed by ruby. I want to be able to write plugins in Ruby.
I want to be able to do changes in the editor core via plugins.
It is not possible with Scintilla to have so much freedom in the
plugins. What I want is maybe emacs ala ruby?

At some point it could be interesting to integrate my editor widget into
freeride, and see what happens.

It would, indeed, be interesting to see an aeditor freeride plugin. One of
the goals of freeride is to be an IDE written in ruby. Obviously, aeditor
fits right into that mold! If you decide to give it a go, we (the freeride
developers) will be happy to answer your questions and provide whatever
assistance we can.

You mentioned that you want to have editor plugins. Do you have this
already? The reason I ask is because freeride is entirely plugin based. Its
plugin management is handled by a completely independent piece of code we
call FreeBASE (pun intended) which handles plug loading, dependencies, and
inter-plugin communications.

Someday we are going to make a separate RubyForge project for FreeBASE to
make it more visible and accessible.

If you don't already have a plugin system, then you should consider
FreeBASE. Doing so would not only save you a lot of time, but would make
integration into FreeRIDE much easier.

Curt

15

I think I have added your suggested idea.. however I don't know if it changes
anything on windows, and thus would like to hear if the new code works for
you (or for others windows users).

The new 'viewfox.rb' file are located here
http://rubyforge.org/cgi-bin/viewcvs/cgi/viewcvs.cgi/projects/experimental/buffer/source/viewfox.rb?rev=1.3&cvsroot=aeditor&content-type=text/vnd.viewcvs-markup

Tell me if replacing the old 'viewfox.rb' file with the new, changes anything?

Thanks in advance

···

On Monday 05 July 2004 17:46, Simon Strandgaard wrote:

On Monday 05 July 2004 16:40, Kaspar Schiess wrote:
> > on windows there are font problems.. you can make me happy if you can
> > make solve this problem. Thanks in advance.
>
> Making you happy:
> @font.create is not executed before onCanvasPrepare, and the font thusly
> accessed is invalid, causing segmentation fault. Solution proposed:

Wonderful!

--
Simon Strandgaard

16

I had a chat session with Robert Klemme, who experienced almost the same,
but Robert unfortunatly had to go.. so we never hunted it down.

It seems to be an endless recursion. The backtrace doesn't reveal how
it happened, thus I have made a small change so we can get a look at
the full backtrace.

please fetch this version of 'viewfox.rb' and try again, and afterwards
mail me the '__backtrace__' file.
http://rubyforge.org/cgi-bin/viewcvs/cgi/viewcvs.cgi/projects/experimental/buffer/source/viewfox.rb?rev=1.9&cvsroot=aeditor&content-type=text/vnd.viewcvs-markup

This will hopefully reveal where the recursion begins.

Another issue, in line#2 of the output it says
cannot read, No such file or directory - D:/temp/aeditor-1.1/err.txt
I guess this is because the program is invoked with a non-existing file.
I am curious to what happens if you invoke the program with an existing file?
c:\> editor autoexec.bat

Also if you don't supply any arguments to the editor when you start it.. what
happens then?
c:\> editor

Do you have ideas how to hunt down this recursion?

Thanks for valuable info.. I am grateful

···

On Tuesday 06 July 2004 23:36, Kaspar Schiess wrote:

Thank you for your effort, sorry for not answering. I have tried this
version, but there seems to be another issue here (see attached file).
Can anyone confirm this on windows ? I don't know what that is since I
haven't had the time to trace this...

btw: ruby 1.8.1 (2003-12-25) [i386-mingw32]

--
Simon Strandgaard

17

wew.. thats many lines, my project has ~3400 lines of source code
and ~2000 lines of testcode at the moment.

my old editor had many more lines and could do some other things:
folding, undo/redo/macros. It had much more testcode.. I have become
a better tester since that time, and writes simpler tests.
I believe the new editor is somewhat better tested than the old.

my current intent is to keep it small and only use ruby. In the past
I had an idea about writing the frontend in C++, to obtain speed.
I think the speed of the current ruby implementation are acceptable.
No need for C++.

when I get back from my 3 week vacation in the us, I will focus on
only blitting the dirty areas to the display.. and only do lexing of the
current line (lexing really takes long time).

I hope that I can release an editor package, that works on windows before
saturday, where I go on vacation.

any kind of patches are warmly welcome (hint) :slight_smile:

···

On Monday 05 July 2004 18:06, Lothar Scholz wrote:

Hello Simon,

>> Can I ask you again to the exact reason why another fully evolved
>> editor like SciTE will not do ?

> Im obsessed by ruby. I want to be able to write plugins in Ruby.
> I want to be able to do changes in the editor core via plugins.
> It is not possible with Scintilla to have so much freedom in the
> plugins. What I want is maybe emacs ala ruby?

emacs has about 100.000 lines of C code to avoid the slowness of
elisp. This are not inside files like buffer.c and do not belong to
the lisp interpreter core.

--
Simon Strandgaard

18

Simon Strandgaard wrote:
> > Can I ask you again to the exact reason why another fully evolved
> > editor like SciTE will not do ?
>
> Im obsessed by ruby. I want to be able to write plugins in Ruby.
> I want to be able to do changes in the editor core via plugins.
> It is not possible with Scintilla to have so much freedom in the
> plugins. What I want is maybe emacs ala ruby?
>
> At some point it could be interesting to integrate my editor widget into
> freeride, and see what happens.

It would, indeed, be interesting to see an aeditor freeride plugin. One of
the goals of freeride is to be an IDE written in ruby. Obviously, aeditor
fits right into that mold! If you decide to give it a go, we (the freeride
developers) will be happy to answer your questions and provide whatever
assistance we can.

I need to enhance the editor sligthly more, before I give it a shot.
Here is a very optimiztic plan, in no paticular order:
I will first experiment with supporting different encodings, such as
unicode, big5, sjis.. etc.
I will port my old undo/redo/macro system to the new editor.
I will add line folding (my old editor had arbitary folding).

You mentioned that you want to have editor plugins. Do you have this
already? The reason I ask is because freeride is entirely plugin based. Its
plugin management is handled by a completely independent piece of code we
call FreeBASE (pun intended) which handles plug loading, dependencies, and
inter-plugin communications.

no, I don't have any plugins yet.
I have looked at your plugin system earlier, and found it interesting.

Someday we are going to make a separate RubyForge project for FreeBASE to
make it more visible and accessible.

If I understand you correct, freebase is a standalone plugin architecture ?

If you don't already have a plugin system, then you should consider
FreeBASE. Doing so would not only save you a lot of time, but would make
integration into FreeRIDE much easier.

I have considered it, but not come to any conclusion.

The kind of plugins I imagine, which will need to interact with the lower
layers of editor could be:
coverage/profiling.. will have to color each line, and keep track of
profiling information per line.
cvs-annotate.. will have to keep track of version-numbers per line.
abstract-syntax-tree.. pointers between the model and the ast.
custom editing modes.. which has control of cursor movement.
These things have to dig deep into the model.

There are probably many more possible plugins.

···

On Monday 05 July 2004 19:07, Curt Hibbs wrote:

--
Simon Strandgaard

19

Today Robert Klemme got it hunted down.. the recursion no longer happens.
You will need to fetch the CVS version of 'viewfox.rb' and replace it with the
old one, installed on your computer.
http://rubyforge.org/cgi-bin/viewcvs/cgi/viewcvs.cgi/*checkout*/projects/experimental/buffer/source/viewfox.rb?rev=HEAD&cvsroot=aeditor&content-type=text/plain

now the editor should startup on windows.

If you experience abnormal behavier, then please report back, what happened,
what did you do before it happened... (maybe you also know whats went wrong).

what monospaced font should aeditor default to on windows?

please mail me some screenshots, weather or not you manage to get it working
on windows. My mind only find rest when I can see it is actually working.

Thanks to: you, riffraff, batsman, botp, dr_bob, for putting huge efforts into
getting this program working.

···

On Wednesday 07 July 2004 00:59, Simon Strandgaard wrote:

On Tuesday 06 July 2004 23:36, Kaspar Schiess wrote:
> Thank you for your effort, sorry for not answering. I have tried this
> version, but there seems to be another issue here (see attached file).
> Can anyone confirm this on windows ? I don't know what that is since I
> haven't had the time to trace this...
>
> btw: ruby 1.8.1 (2003-12-25) [i386-mingw32]

I had a chat session with Robert Klemme, who experienced almost the same,
but Robert unfortunatly had to go.. so we never hunted it down.

--
Simon Strandgaard

20

if we just had a ruby ->c++/ObjectiveC translator..

···

il Tue, 6 Jul 2004 01:21:40 +0900, Simon Strandgaard <neoneye@adslhome.dk> ha scritto::

my current intent is to keep it small and only use ruby. In the past
I had an idea about writing the frontend in C++, to obtain speed.
I think the speed of the current ruby implementation are acceptable.
No need for C++.