On Wed, 09 Jan 2002 09:39:58 +0100, Carsten Strotmann wrote: >over the last weeks I made some brainsorming about this project, what I >want this RAD-Tool to be. Before you start flaming me, please consider >that these are just suggestions for a discussion. Of couse. >I know that it is not >easy or that it is maybe impossible to meet all this goals:
>1) a name: how about OpenGUI or OpenDialog? OpenGUI project already exists. OpenDialog - Sibyl not only dialog building system. Also we can use original name Visual Pascal Development Enviroment (VPDE). But name is not main goal. >2) Architecture and concept: Delphi is now about one decade old, and so >is the delphi two-way-RAD idea. Maybe the world of RAD tools is advanced >in the last ten years. I find the concept of the "libglade" project >http://developer.gnome.org/doc/API/libglade/libglade.html) very >interesting, having the GUI encoded in XML Language wich is parsed at >runtime. In such a RAD Tool one don't need to re-compile after a gui >change, and non-programmers can help building the gui, or the user can >change the gui to suit her/his needs. I would like to see that we build >a more modern RAD Tools with Pascal bindings (with a delphi import >module) rather that a one-to-one Delphi clone. First af all, scripting IDE (like tcl/tk) too slow and in most cases ugly. But yes, we can try make not visual part, but controls only and allow user move these controls to any place. >3) target platform/compiler: as I wrote in a previous post, I would like >the tool to be platform and compiler independent. That includes the >available OS/2 Pascal Compiler (gnu, virtual pascal, freepascal), but >also other pascal-like languages like modula2, modula3 (I work with SRC >Modula3 on OS/2), oberon, XDS and others. And if this is possible, >bindings for other languages like ReXX are not that far away. We can't make this at current moment. Sibyl very closed to Speed Pascal . But it possible. >4) GUI Toolkit: We should discuss if we like to use a GUI toolkit or if >the RAD Tools uses plain OS/2 API. The use of a toolkit helps in terms >of platform independance, but may hide some "loved" OS/2 Features. My >opinion is to use a basic toolkit for platform independance with >optional "OS/2 only" extensions. So the programmer can decide if he goes >cross-plattform or if he likes to squeeze the last trick out of OS/2. >Suggestions are WxWindows/2 (not finished), V, XPCOM (Heavyweight), >GTK/2 (no PM GUI today). At current time used SPCC. >5) Speed: would be nice if the compiled GUI Applications will run well >on a 486/100 32 MB. For the RAD Tools I would see a target machine of a >P2 266 64 MB. Don't forget the people that don't use the latest hardware :-) May be. >I hope I'm not on the wrong track, because it seems that there is >already some code and people working on this project. Can anybody give >me the status if there is already a (maybe) written concept for this >project? At current time we have source code of Sibyl RTL, SPCC & VPDE. Full clone of Sibyl 3 Fix 4 (Not all sources synhronized yet). PS: I think, eclipse (?) project is uniIDE. I think we must: First of all, make full clone of Sibyl. Second, replace binary resources by ascii representation (for RC). Third, Make other things. PPS: I'm not interesting in non-OS/2 RAD. PPPS: I think WPS is more great RAD. Just required some classes, for example for make/project. ----------- To unsubscribe yourself from this list, send the following message to [EMAIL PROTECTED] unsubscribe sibyl end
