Qt vs. FOX vs. ? (was Help on installing ruby-qt on windowsXP)

I assume that the Ruby extension for Qt will support version 3 someday. I
just don’t want to put in the effort to learn Qt if at some point I’m going
to have to pay $1550 to upgrade. Of course I could develop under Linux to
avoid this problem, but I want the things I develop to be usable by people
running under Windows too.

I get the impression that Qt is a somewhat better GUI toolkit that others.
I also get the impression that FOX is the next best choice. I’m leaning
toward spending my time learning FOX unless someone wants to explain to me
why I should use Qt instead or why I should consider some other GUI toolkit
that has Ruby support.

···

-----Original Message-----
From: Pierre Brengard [mailto:pbrengard@bct-technology.com]
Sent: Tuesday, September 17, 2002 4:19 AM
To: ruby-talk@ruby-lang.org
Subject: Re: Help on installing ruby-qt on windowsXP

I’m curious why you’ve decided to try the
non-commercial version for Windows.
I was looking into that last week and
decided to try FOX instead because

  1. the non-commerical version is Qt version 2.3, not
    version 3 (unless you just download a 30-day evaluation
  2. getting the Windows commercial version in order to get
    version 3 support is prohibitively expensive! - $1550

but, the Ruby extension for Qt 3 does not exist yet !
So, no regret.


WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.


I get the impression that Qt is a somewhat better GUI toolkit that others.
I also get the impression that FOX is the next best choice. I’m leaning
toward spending my time learning FOX unless someone wants to explain to me
why I should use Qt instead or why I should consider some other GUI toolkit
that has Ruby support.

I also wonder what GUI is the best under windows.
I’ve seen all of them crashing :-/

For linux gtk is good…

Gergo
±[Kontra, Gergely @ Budapest University of Technology and Economics]-+

    Email: kgergely@mcl.hu,  kgergely@turul.eet.bme.hu          |

URL: turul.eet.bme.hu/~kgergely Mobile: (+36 20) 356 9656 |
±------“Olyan langesz vagyok, hogy poroltoval kellene jarnom!”-------+
.
Magyar php mirror es magyar php dokumentacio: http://hu.php.net

Isn’t somebody on this list porting the Perl/TK text to Ruby/TK? I
remember somebody asking if this was in the works, if not, they were
going to take up this task.

Also, since we are on the subject, how does Ruby/Fox compare with
Ruby/TK? I understand TK has a ten year head start and thousands of
pages of English text behind it. How useable for productin work has
Ruby/FOX become?

//ed

“Edward Wilson” web2ed@yahoo.com wrote in message
news:5174eed0.0209171130.12081aa9@posting.google.com

Isn’t somebody on this list porting the Perl/TK text to Ruby/TK? I
remember somebody asking if this was in the works, if not, they were
going to take up this task.

Also, since we are on the subject, how does Ruby/Fox compare with
Ruby/TK? I understand TK has a ten year head start and thousands of
pages of English text behind it. How useable for productin work has
Ruby/FOX become?

The latest releases of FxRuby has improved stability significantly - get the
1.6.7 install for Windows.
The scintilla test application crashes within seconds but almost all other
sample applications appears stable. I also got the TextEdit application
crashing when I edited one of the files implementing it (didn’t save it…)
but couldn’t reproduce.

The test apps now say something like Sorry you need SOAP4R instead of just
terminating, when you miss that piece of software.

I like the way FxRuby easily synchronizes multiple controls due to the
bidirectional connections.
Haven’t done any real FxRuby programming though - just investigating.

I also looked at the UFO OpenGL based GUI library for SDL (no Ruby
binding) - it is a completely bloated toolkit not delivering very much
although the concept as such looked interesting.

Other interesting news: The Mono project has decided to drop GTK and
implement WinForms on top of either Win32 native, or Wine on Linux (adding
GUI facilities to Wine along the way).

It therefore seems like WinForms could end up becoming a relevant cross
platform GUI toolkit. While this is still vaporware, Mono has proven that
they can grow functionality very quickly.

In this light a Ruby interface to MS .NET Winforms as well as Mono Winforms
would be an interesting project.

Mikkel

MikkelFJ wrote:

The latest releases of FxRuby has improved stability significantly - get the
1.6.7 install for Windows.
The scintilla test application crashes within seconds but almost all other
sample applications appears stable.

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I also
know, for example, that the FreeRIDE group is relying heavily on the
Scintilla widget and it seems to be working OK.

I also got the TextEdit application crashing when I edited one of the
files implementing it (didn’t save it…) but couldn’t reproduce.

OK. If you do hit on a way to reproduce it, let me know.

The latest releases of FxRuby has improved stability significantly - get
the
1.6.7 install for Windows.
The scintilla test application crashes within seconds but almost all other
sample applications appears stable. I also got the TextEdit application

On Windows ME, Ruby 1.6.7-4 install, scintilla-test.rbw will crash if
i doubleclick to run. Running by ‘ruby scintilla-test.rbw’ in a DOS box is
ok.

If i comment some lines with ‘puts’ e.g.

@scintilla.connect(SEL_COMMAND) do |sender, sel, scn|
puts “received SCNotification:”
#~puts " scn.nmhdr.idFrom = #{scn.nmhdr.idFrom}"

end

runs fine if double-clicked.

[]'s
Guaracy

···

----- Original Message -----
From: “MikkelFJ” mikkelfj-anti-spam@bigfoot.com

HP: www.guaracy.cjb.net

Lyle Johnson wrote:

MikkelFJ wrote:

The latest releases of FxRuby has improved stability
significantly - get the
1.6.7 install for Windows.
The scintilla test application crashes within seconds but
almost all other
sample applications appears stable.

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I also
know, for example, that the FreeRIDE group is relying heavily on the
Scintilla widget and it seems to be working OK.

I can confirm that the FreeRIDE is making very heavy use of FXRuby’s
FXScintilla component and we are not running into any problems like this
with it.

Curt

···

I also got the TextEdit application crashing when I edited one of the
files implementing it (didn’t save it…) but couldn’t reproduce.

OK. If you do hit on a way to reproduce it, let me know.

“Lyle Johnson” lyle@users.sourceforge.net wrote in message
news:3D87AC9E.2020007@users.sourceforge.net

MikkelFJ wrote:

The latest releases of FxRuby has improved stability significantly - get
the

1.6.7 install for Windows.
The scintilla test application crashes within seconds but almost all
other

sample applications appears stable.

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I also
know, for example, that the FreeRIDE group is relying heavily on the
Scintilla widget and it seems to be working OK.

Well - I tried opening scintilla-test.rbw in RubyWin
It had this annoying feature that focus kept going back to RubyWin, so I
couldn’t really test.
Then I closed RubyWin and surprisingly the Scintilla-test application stayed
open.
This time the application remained stable.
However, I was unable to terminate the application using close window or
quit in the menu.
So I suspect it is a close event going wild in the scintilla-test
application in the 1.6.7 distribution.
(Could also be influenced by RubyWin using Scintilla, so another Scintilla
version might have been loaded).
(To avoid confusion: the crash scenario was simply the application
terminating after a few keystrokes entered, when started standalone
doubleclicking on the .rbw file in Windows XP, SP1).

I have used the Scintilla based Scite editor on Windows for over a year in
various versions, and it has always been rock solid. The scintilla-test app
were also stable in version 1.6.6 as I recall.

I also got the TextEdit application crashing when I edited one of the
files implementing it (didn’t save it…) but couldn’t reproduce.

OK. If you do hit on a way to reproduce it, let me know.

BTW: The crash was a serious one like "instruction could not be read"
messagebox or similar. The scenario was simple: type type enter type type
enter randomly a few times then open commands.rb and repeat editing randomly
inside file. Crash within 10 seconds.

Mikkel

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I also
know, for example, that the FreeRIDE group is relying heavily on the
Scintilla widget and it seems to be working OK.

Yes, using 1.7.2-4 Windows install - running on WinXP

running scintilla.rbw (by double clicking) crashes within a second of
selecting the main app window.

Changing the extension to scintilla.rb and it works happily, though
spewing out a ton of trace.

Rob

Guaracy Monteiro wrote:

On Windows ME, Ruby 1.6.7-4 install, scintilla-test.rbw will crash if
i doubleclick to run. Running by ‘ruby scintilla-test.rbw’ in a DOS box is
ok.

If i comment some lines with ‘puts’ e.g.

@scintilla.connect(SEL_COMMAND) do |sender, sel, scn|
puts “received SCNotification:”
#~puts " scn.nmhdr.idFrom = #{scn.nmhdr.idFrom}"

end

runs fine if double-clicked.

Guaracy,

Thanks for confirming my suspicions. It sounds like doing a “puts” from
the non-console version of Ruby is a recipe for doom. I’ll just take
those statements out for the next release (they were really just
debugging aids anyways).

Lyle

Yes, using 1.7.2-4 Windows install - running on WinXP

running scintilla.rbw (by double clicking) crashes within a second of
selecting the main app window.

Changing the extension to scintilla.rb and it works happily, though
spewing out a ton of trace.

make that “scintilla-test.rbw” and “scintilla-test.rb”

in the samples/FXRuby directory.

rob

Robert McGovern wrote:

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I
also know, for example, that the FreeRIDE group is relying heavily on
the Scintilla widget and it seems to be working OK.

Yes, using 1.7.2-4 Windows install - running on WinXP

running scintilla.rbw (by double clicking) crashes within a second of
selecting the main app window.

Changing the extension to scintilla.rb and it works happily, though
spewing out a ton of trace.

The same thing also applies to table.rbw

As .rbw it will crash if you select a few widgets (Select a cell and
drag). Change it to .rb and it works perfectly.

Rob

Also the same behaviour for 1.7.2-1 Windows under Win2k

-mark.

···

At 04:10 AM 9/19/2002 +0900, you wrote:

If anyone else is reading this thread, is the Scintilla test program
crashing for anyone besides Mikkel? I can’t reproduce this crash. I also
know, for example, that the FreeRIDE group is relying heavily on the
Scintilla widget and it seems to be working OK.

Yes, using 1.7.2-4 Windows install - running on WinXP

running scintilla.rbw (by double clicking) crashes within a second of
selecting the main app window.

Changing the extension to scintilla.rb and it works happily, though
spewing out a ton of trace.

Robert McGovern wrote:

running scintilla.rbw (by double clicking) crashes within a second of
selecting the main app window.

Changing the extension to scintilla.rb and it works happily, though
spewing out a ton of trace.

OK. It sounds like the common threads among these cases are that:

  1. You only see it crash when it’s running the
    non-console version of the Ruby interpreter
    (i.e. the one that’s invoked when you double-click
    a *.rbw file); and,

  2. It only crashes for those example programs that
    attempt to print stuff to the standard output
    (both the scintilla-test.rbw and table.rbw examples
    do this).

Can you confirm for me that if you simply comment-out or remove the
various “puts” statements in these examples (the *.rbw versions) that
they will then run without crashing? I have the feeling that what we’re
seeing is that if you try to do a “puts” in the non-console version of
Ruby that it will crash.

TIA,

Lyle

Thanks for confirming my suspicions. It sounds like doing a “puts” from
the non-console version of Ruby is a recipe for doom. I’ll just take
those statements out for the next release (they were really just
debugging aids anyways).

BTW: but ruby shouldn’t crash from a puts statement, I think…

Gergo
±[Kontra, Gergely @ Budapest University of Technology and Economics]-+

    Email: kgergely@mcl.hu,  kgergely@turul.eet.bme.hu          |

URL: turul.eet.bme.hu/~kgergely Mobile: (+36 20) 356 9656 |
±------“Olyan langesz vagyok, hogy poroltoval kellene jarnom!”-------+
.
Magyar php mirror es magyar php dokumentacio: http://hu.php.net

Yep. “Select All” will do it on the .rbw version for me.

Not quite perfectly from this end for the .rb version. Doing a resize
(row=7 col=7 or less) causes a crash. Is that a FXTable problem? The
table.rb code seems to be ok.

-mark.

···

At 04:30 AM 9/19/2002 +0900, Robert wrote:

The same thing also applies to table.rbw
As .rbw it will crash if you select a few widgets (Select a cell and
drag). Change it to .rb and it works perfectly.