Re: [Wxdsgn-devs] plugin merge

[Esteban A. B. <nab...@ya...>]

--- Malcolm Nealon <m.n...@wa...> escribió:
> I open (what I suppose is the correct project) 
> wxdevcpp\source\plugins\wxdsgn\wxdevcpp.dpr
> 
> This seems to be the devcpp IDE with a few added
> files, (wxdevcpp.exe) 
> In my ignorance, I thought that this would be a
> project containing two 
> sub-projects (the IDE and the designer  plugin).
> So assuming that I have to build two projects I
> closed the dpr, and 
> opened wxdsgn.dpk (believing that this is the
> plugin)

Ok, I'll try to clarify. The new layout of the project
goes like this:

There are 3 important project files now: the first one
you used (wxdevcpp\source\plugins\wxdsgn\wxdevcpp.dpr)
simulates a full wxDev-Cpp IDE, or in other words,
vanilla dev-cpp + wxdsgn designer statically linked.
This version is meant to be used during development,
since it makes it easier to debug, test, etc. But the
intention is to never distribute binaries generated
with this project file. 

Next, wxdsgn.dpk generates the wxdsgn designer as a
runtime linkable plugin. It shares the designer
sources, so if you modify something in the other
development version, those changes get to the binary
.bpl file that wxdsgn.dpk generates when you compile.

Finally, under wxdevcpp\source, devcpp.dpr should be
used to build the IDE binary release, and this is
vanilla dev-cpp, with the ability to load .bpl or .dll
plugins at runtime, again, it shares sources with
wxdevcpp.bpr (in a meaningful way of course, so for
example, devcpp.dpr does not use any files from the
wxDesigner "wxdsgn"). We are supposed to build the
executable using this version, and pack it along with
the wxdsgn plugin, so we can keep a distribution that
works like the current one does. 

The difference is that the user will have the option
to uninstall the wxdsgn component if they want to, or
even upgrade it individually without touching the IDE
at some point. Also, at some point the people at the
original DevCpp project could synch with us and
distrubute the Vanilla IDE with plugin capabilities,
and some users could add the wxdsgn pack, so there is
effectivelly only one version of dev-cpp "in the
wild", and not two like now.


> Now when I try to compile I get a dialog stating
> that I should do the 
> following:
> 
> Add Jcl.
> 
> Add JvCoreD6R.
> 
> Remove JvVCL5Utils, JvWin32, JvComponentBase,
> JvAppIniStorage, 
...
> I am guessing that this is due to my choice of
> JCL/JVCL and that y'all 
> don't get this.  So assuming that I am correct in
> this, which version of 
> jcl/jvcl should I install, or how else can this be
> solved?

Ok, right now I can't help you there, but I guess you
are correct in that it has something to do with the
JCL/JVCL versions you used. As I told you, Tony
mentioned something about trying to use the latest
versions, but I can't confirm wich ones have he used
at the end. In any case, it is still pending the need
to upload to sourceforge or other site the whole
package with all the CompUsed_WX stuff, to avoid this
kind of problems.




      ____________________________________________________________________________________
¡Capacidad ilimitada de almacenamiento en tu correo!
No te preocupes más por el espacio de tu cuenta con Correo Yahoo!:                      
http://correo.espanol.yahoo.com/