Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

e8johan (605347)

e8johan
  (email not shown publicly)
http://www.digitalfanatics.org/e8johan

I'm a programmer and a hardware designer.

Journal of e8johan (605347)

Back Again

Tuesday April 20 2004, @07:11AM
User Journal

I don't know if anyone ever reads this journal. /. just doesn't seem to be that kind of place. I'm just writing to announce that Gt is on track and partly working. Signals and slots are there and the basic framework exists - now there are two things left polishing the framework and wrapping GTK+. Sounds like fun!

Ah, the link is: http://www.digitalfanatics.org/projects/gt.

Update: Gt, Qt and hacking away

Friday September 19 2003, @05:14AM
User Journal

Ok, it was a while since I entered something into my journal (I think that the new verb is "blogged"). This is just a small update.

Gt has a moc, it works, but the exception handing (and thus the error feedback) is not good. It will be available from http://www.digitalfanatics.org/projects/gt/.

I've written (or rather, am writing) a Qt tutorial. I've had good feedback from it, please check it out at http://www.digitalfanatics.org/projects/qt_tutorial/.

Finally I'm working on my first large open source project. It is fractal related. I want to enter a competition with it, but as soon as I've submitted the first version I may (and will) publish the source. It, too, will be available from http://www.digitalfanatics.org.

Gt will need a moc

Wednesday February 05 2003, @09:08AM
User Journal

After thinking alot about how to manage signals and slots in Gt I have decided to redo the project, but in a more Qt-like way.

The following issues have come up:

  • A moc makes things easier and better looking.
  • A moc can easily be implemented in Perl.
  • A moc makes it easier to wrap GTK into Gt.

I intend to write a moc-like tool (with support for signals and slots) producing code with the same functionality as Qt's moc. This moc will be freely available and GPL'ed without any restrictions on the resulting files.

The moc will be easy to build if the following conditions are met:

  • One mocable class per file.
  • Nice types, i.e. the same restrictions as in Qt's moc.

I wonder if there are any legal risks in doing this. Trolltech might be pissed... :)

Gt Again

Tuesday November 19 2002, @04:51AM
User Journal

I've gotten some more time to fiddle with GObject/GWidget and to try getting the signal/slot mechanism to work properly.

Now it seems to work, you can test connections and actually call 'em. The pointer can be of another class, e.g. a GObject pointer can dispatch signals in a GWidget object without knowing of them.

It seems to be possible to automatically generate code that works with this. I've tried with the Bin, Container and Button classes and got it to work without too much tweaking.

Gt Update

Wednesday November 06 2002, @11:10AM
User Journal
The basic parsing and automatic wrapping of GTK+ into C++ classes is ready for use. I've begun a rewrite of the basic Gt classes.

I begun this project by wrapping parts of GTK+ into Gt and designed a class hierarcy around this that gave me signals, slots and events. In order to get the GTK+ to Gt wrapping to work better, I've decided to rewrite these classes.

What do I offer? I have a GObject with safe pointers, automatic deletion of children, etc. Also, a handmade Gt widget serving as the base of the entire GTK+ class hierarcy.

The only main hurdles left are these:
  1. Get the basic classes to work perfectly (GObject, GSafePtr and GWidget).
  2. Get the automatic wrapping to work 100% (all GTK+ widgets will work without patching).
  3. Write a GPainter wrapper for GDK to make the porting of Qt/KDE widgets easy.
Then there is just one point left: get people to use it!