Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

wysiwyg?

(1/4) > >>

DJMaze:
What about a implementation of WYSIWYG?
Let's say you build a window in wxWidgets, C::B loads the library (already loaded anyway) and creates the window based on the window position, size and settings.

Not so sophisticated as MSVC or BCB but more like a simple preview or make it just as sophisticated by using a new file type '.wxd' (wxWidgets Designer) and '.fld' (FLTK Designer) and the designer file contains the position and size data.

takeshimiya:

--- Quote from: DJMaze on March 17, 2006, 05:48:48 am ---What about a implementation of WYSIWYG?
Let's say you build a window in wxWidgets, C::B loads the library (already loaded anyway) and creates the window based on the window position, size and settings.

Not so sophisticated as MSVC or BCB but more like a simple preview or make it just as sophisticated by using a new file type '.wxd' (wxWidgets Designer) and '.fld' (FLTK Designer) and the designer file contains the position and size data.

--- End quote ---

I'm not sure I understand what you want to do, but I wonder, that's what wxSmith does (for wxWidgets), isn't?
And for FLTK, that's what fluid does.

Or you're talking not about a RAD but something different, not ever done before on any existing app?

DJMaze:
yes, similar to fluid and wxSmith but then integrated inside C::B as wysiwyg plugins or something.

fluid and wxSmith are form designers only but, as somesort of plugin inside C::B you have the power of both (code editor and form designer). This way you can increase development speed just like RAD but do not make it a full RAD since that will limit flexibility.

I was more thinking about a structure like Borland's VCL. You compile widgets into a library and C::B loads these libraries. Then you can drop widgets on a form like in fluid and wxSmith and the code designer puts the needed C++ code inside the .cxx file.

That way you can rapidly design a form inside C::B but without loosing control.

RAD Example:
say in fluid you design a window with buttons, select box and richedit. After that you must select the menu option to write the code to a file so you can alter it.

C::B Example:
you design a window with buttons, select box and richedit and while you're dropping the widgets on the form C::B instantly writes the equivelant code into the .c and .h files.

1. The menu has a new option "new window" that starts a wizard to select what kind of window you want (fluid, wxWidgets, etc.) and how you want the filename.
2. Click OK and C::B writes a filename.cxx and filename.h and then opens the files and a form designer
3. (Lets say below the menu)  a tabs section pops up which contains widgets.
4. select a widget and drop it on the form designer
5. when dropped C::B writes the needed code in the .c and .h files
6. modify the .c and .h files yourself to get the effect you want.

A real RAD/wysiwyg needs another file, as i explained above, so that it doesn't have to read your .c and .h files to figure out what you realy want.

I hope i made myself clear about the difference between fluid/wxSmith and a system inside C::B

thomas:

--- Quote ---fluid and wxSmith are form designers only but, as somesort of plugin inside C::B you have the power of both (code editor and form designer). This way you can increase development speed just like RAD but do not make it a full RAD since that will limit flexibility.

I was more thinking about a structure like Borland's VCL. You compile widgets into a library and C::B loads these libraries. Then you can drop widgets on a form like in fluid and wxSmith and the code designer puts the needed C++ code inside the .cxx file.

That way you can rapidly design a form inside C::B but without loosing control.
--- End quote ---
I begin to wonder if you have ever actually used Fluid (or wxSmith). This is exactly how it works...

DJMaze:

--- Quote from: thomas on March 17, 2006, 06:16:56 pm ---I begin to wonder if you have ever actually used Fluid (or wxSmith). This is exactly how it works...

--- End quote ---

OK i think you didn't get it. In fluid you can design forms but after that you must call in the menu "File" -> "write code"
The issue here is, after you wrote the code and modify it but think "hmm i need another widget on the form" you're screwed since you call "File" -> "write code" again and all your changes are lost, unless you run a merger app or something.

Instead, thru C::B you can instantly add a new widget to a form without loosing changes AND you can modify the code instantly.

For example you have a new form and write code to the .c file to take certain actions on the form.
After that you add a button widget and write additional code for the widget.
Then you add another button and write code for it.

Did you ever use Borland C++ Builder/Delphi/Kylix or MS VC++ Studio ?

NOTE: i use FLTK 2

Navigation

[0] Message Index

[#] Next page