On November 4, 2005 05:19 pm, Neil Hodgson wrote: > I think it is actually possible to add a new platform without > changing Platform.h but it may be more work. Palette could cause > trouble but it is rare for people to care much about paletted displays > any more.
I "think" I managed to get away with making sure Platform.h had a "#define PLAT_QT 0" and lower down, a "#if defined(QT)". Also theres that ifdef PLAT_WX (int ascent) in the Font class, maybe it should be a method? > Neil > I started the Qt4 port based on the old QScintilla qt3 port, but its horribly inflexible :( I hope to come up with something thats easy to use, yet allows full use of every Scintilla feature. That Scintilla.iface file will help alot ;) I'm thinking of going with a three layer design, the base QScintilla class will provide a minimal Qt interface to scintilla, and ontop of that a subclass thats generated from the iface file, and last, the final bits that can't be generated :) Now, noone will mind if I use the scite lexer description files right? ;) I'm also a little concerned that scintilla forces use of xpm's, it may be possible to have Qt4 convert its QIcon/QPixmap's to an xpm, but it seems like an extra step that needent be taken.. And Im confused about the little bit of unicode code in the Platform class.. Qt natively supports unicode via its QString's, I'm just not sure how they all fit together. -- Thomas Fjellstrom _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
