1. wxEuphoria questions
I'm making lots of progress on the next version of wxEuphoria. As I've
mentioned before, there are some significant changes to the organization of
the code. In particular, the eu code is really only a very thin wrapper
for another fairly thin C/C++ wrapper of wxWidgets.
I've got most of wxedb running under the new library, and most of the
old functionality is working. I've even added a few things, like wxRegEx
support.
Right now, I've got the entire wrapper in a single file, as opposed to the
current structure of having similar classes split into their own files.
The file is basically a bunch of define_c_xxxx, global constants, and one
liner routines with a c_proc/func call. The file is a little over 4000
lines.
Question:
* It's pretty convenient for working with, but would people prefer to
still have everything split out?
Also, later this weekend, I'm hoping to put some code up for people to play
with, if anyone's interested. Jerry, I think you're really going to like
this, because I'm pretty confident that you'll be able to get it up and
going with Ubuntu.
The binaries will be pretty different for the different platforms, too.
The Windows will have everything in one single, giant file (wxWidgets +
wxEuphoria). The linux (and FreeBSD!) distributions will only be the
C/C++ wrapper. It will use a regularly installed version of wxWidgets 2.8.2.
So you can either get it as a package (if available) or build it from
source (without any modifications, just configure/make/make install).
The new structure has a couple of implications for extending the library.
It means that any function not explicitly wrapped won't be available for
use in euphoria apps. On the other hand, the euphoria coder isn't expected
to know anything about C++, unless he wants to add to the wrapper. And
most of the wrapping will be very straightforward. We get to take advantage
of the features of C++, rather than try to emulate them in euphoria.
Matt
2. Re: wxEuphoria questions
Hi
Personally, I'd prefer one large file.
Will the new wxEuphoria be a drop in replacement for the old old one? Or
will there be a lot of re-writing of code using previous versions?
Chris
3. Re: wxEuphoria questions
ChrisBurch2 wrote:
>
> Personally, I'd prefer one large file.
I don't mind one big file, as long as it's well commented... or at least has
headers for the different sections.
4. Re: wxEuphoria questions
- Posted by Matt Lewis <matthewwalkerlewis at gmail.com>
Mar 17, 2007
-
Last edited Mar 18, 2007
ChrisBurch2 wrote:
>
> Hi
>
> Personally, I'd prefer one large file.
>
> Will the new wxEuphoria be a drop in replacement for the old old one? Or
> will there be a lot of re-writing of code using previous versions?
>
It's mostly a drop in replacement. There will be a few things that don't
work exactly the same, mainly because of changes in wxWidgets (we're going
from 2.4.2 to 2.8.2 here). The biggest thing is changing the include
statements.
I also had several places in wxedb (I'm probably going to work on wxIDE
next) where I was making call_member calls from the application, which
won't work anymore.
Matt
5. Re: wxEuphoria questions
- Posted by Jason Gade <jaygade at yahoo.com>
Mar 17, 2007
-
Last edited Mar 18, 2007
Hmm. How large will it be if it is all one file? Larger or smaller than
Win32lib?
I'm still not developing any gui apps, but I do have an opinion for whatever it
is worth: Put all of the major functionality (as in most commonly used) in one
main file, and put lesser used stuff and utility stuff (things that might be
useful outside of wxEuphoria) in separate files.
--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
6. Re: wxEuphoria questions
- Posted by Matt Lewis <matthewwalkerlewis at gmail.com>
Mar 17, 2007
-
Last edited Mar 18, 2007
Jason Gade wrote:
>
> Hmm. How large will it be if it is all one file? Larger or smaller than
> Win32lib?
>
> I'm still not developing any gui apps, but I do have an opinion for whatever
> it is worth: Put all of the major functionality (as in most commonly used) in
> one main file, and put lesser used stuff and utility stuff (things that might
> be useful outside of wxEuphoria) in separate files.
Win32lib.ew is currently about 35K lines (of course, that includes the docs
as well, which I haven't added to wxeu yet). Of course, there are also
other files that win32lib includes for itself, so there is more than that.
I doubt that the wxeuphoria include will approach that size, and we could
easily strip out the documentation for distribution.
Unless someone else chimes in, I think I'll probably leave it all together
for now. It shouldn't be too tough to separate it out later.
Matt
