From: Randy Kramer <rhkramer@...>
Date: 2005-02-28T23:14:13+09:00
Subject: Re: Thanks, Bugs, and Observations re. KDE Tutorial (was Re: Simple HTML Renderer / Browser?)

On Sunday 27 February 2005 10:46 am, Alexander Kellett wrote:
> concealed at the bottom of
> http://developer.kde.org/language-bindings/ruby/kde3tutorial/p9.html

Ahh, thanks, that's (part of) what I needed! (more below)

> i suppose a tarball with the entire example
> would be really useful for people that just
> like looking at code :) (e.g, me ;))

Yes, that would be helpful, or additionally/alternatively, make it a little 
more obvious in the text that you must also create file p9ui.rc.  I had 
skimmed the text, but even reading it more carefully after knowing I have to 
do that, I'm not sure it would be clear to someone reading it for the first 
time.  Maybe a note at/near the top of the page like, "To run this example 
you must create two files, ... and also for full effect, you must run an 
instance of p8 as well." (starting it first, iirc, or does it matter?)

More comments (as always ;-)

   * I feel like I must apologize again for not having thoroughly studied this 
tutorial, but it seems like the concepts demonstrated here will meet a lot of 
my needs, so I've tentatively moved on to figuring out how to "parse" TWiki 
markup.

   * For the sake of completeness, it seems there is still an error (or 
another EBKAC)--p7 and p8 work fine together as a pair, but p8 and p9 
don't--from p9 I can save bookmarks to p8, but choosing a bookmark in p8 does 
not cause it to be loaded in p9.

   * Which reminds me to thank everyone responsible for these tutorials 
again--they are helpful and demonstrate some useful functionality of the type  
I need!  Part of what I intend is to have a "supervisory" window that knows 
what "pages" are open in any number of "subsidiary" windows.  I'm fairly 
certain the signals and slots mechanism will make that fairly easy to do.  
(Note though that the subsidiary windows will all be independent "instances", 
so a crash or closure of one will not close any of the others.)  

I guess what that part of what I'm trying to say is that not only is the 
tutorial a good way to start learning how to use Korundum and (Ruby)Qt (??), 
it is a good demonstration of some of the power of Qt!

> strange that its so slow. my 2000-ish line
> application (rubberdoc) only takes a second
> or so to start here. widget creation should
> be basically instantaneous. (note, i don't
> have a fast computer)

There is no significant improvement for opening the same program 
(experimenting with p8 and p9) a 2nd time (after closing it).  Also, I tried 
opening the same program a 2nd time when it is already open.  It won't open a 
2nd copy (does this mean the programs are somehow singletons--something else 
for me to learn), but it still takes a significant amount of time (3-4 
seconds) for the "focus" to shift to the already open instance.

Just to try to put the 3 to 6 seconds in context, perhaps some of this is 
because I have a heck of a lot of things loaded (kmail, konsole with 6 
"sessions", epiphany with ~10 tabs, 3 instances of konqueror with a total of 
~35 - 40 tabs, top, samba (etc.), 5 instances of Nedit, 4 instances of gjots) 
and not all that much memory and swap space: 384 KB of RAM (all this MB can 
handle), ~1 GB of swap (often up to half in use, and (aside) I do notice a 
general slowdown when over half of my swap starts being used), and a 500 MHz 
processor.  (But, this is the environment the program will typically run in 
(for me).)

> qt also has a rich text view. subset html.
> not sure if thats useful enough :)
>
> see:
> 	http://doc.trolltech.com/3.3/qtextbrowser.html

That's good to know!

regards,
Randy Kramer