Re: [Wxdevide-devs] doc manager and notebook

[Nuklear Z. <nuk...@gm...>]

no what i meant was that we keep the delphi ide for now and focus on the
form designer in c++. between the two in the end, the form designer has more
end user value since it will be a true WYSIWYG. the ide can have some other
features and some that work better but it is pretty good right now and will
not have AS dramatic results. (especially for a longer period of time) so we
put off the plugin framework for the time being and the c++ ide and write
the c++ form designer to be useable with the plugin system in the future.
hence the api layer.

Nuklear

On Wed, Mar 31, 2010 at 3:17 PM, Tony Reina <re...@al...> wrote:

>
> the basic idea for the interfacing code for the form designer (connecting
>> it to the gui) is basically like what scintilla does. the form designer is
>> its own module, it can have a modular structure too. then the parts that
>> need either user input, config read/write and whatever else are routed to an
>> interfacing api. then we use that api with a standalone executable directly
>> (the gui uses it natively) as long as we do it right we only need to build a
>> wrapper api for that to connect the form designer into the plugin system for
>> wxDevIDE. that also allows the form designer to be used in other projects
>> too like if Code::Blocks users wanted to use it. hopefully y'all understood
>> what i'm trying to say. that should kinda kill several birds with one stone.
>>
>>
>>
> So are you saying that we keep the Delphi plugin of the form designer (for
> now) and just allow it to hook into wxDevIDE? I was hoping that we would at
> least eventually migrate the form designer to wxWidgets/C++ so that it is a
> true WYSIWYG cross-platform version.
>
> -Tony
>
>