BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

wxWindows
Goto page 1, 2, 3  Next
 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (Non-Technical)
View previous topic :: View next topic  
Author Message
Rhys Sage
Guest





PostPosted: Sat Oct 11, 2003 9:53 pm    Post subject: wxWindows Reply with quote



Ok. I've heard mention of wxWindows. What is it?

I can see an advantage in using a platform independent programming language
and windows-style libraries that use the same access commands for different
platforms. IE, the main program is written in C++/Pascal/Java/Eiffel/etc
then a .dll is attached that handles all the visual functions so that the
same program (with an appropriate .dll) can be used on Mac, Windows, BeOs
and Linux. Taking a program from Windows to work on Linux would simply be a
matter of transferring the program but uniting it with the correct .dll. I
might be talking out of my hat but I think it's probably possible. Is
wxWindows anything like this?

--
Yours,

Rhys Sage.
www.sageworld.freeserve.co.uk for
code snippets and software downloads.
--
Vini vidi vici
--
(Team Zip)


Back to top
Remy Lebeau (TeamB)
Guest





PostPosted: Sat Oct 11, 2003 11:01 pm    Post subject: Re: wxWindows Reply with quote




"Rhys Sage" <No.Spam@ta> wrote

Quote:
Ok. I've heard mention of wxWindows. What is it?

http://www.wxwindows.org

Quote:
I can see an advantage in using a platform independent programming
language and windows-style libraries that use the same access
commands for different platforms. IE, the main program is written in
C++/Pascal/Java/Eiffel/etc then a .dll is attached that handles all the
visual functions so that the same program (with an appropriate .dll)
can be used on Mac, Windows, BeOs and Linux.

That is a completely different matter. The issue around using wxWindows is
that it allows the same source code to be compiled into a single executable
under different platforms *without* using external modules/dlls befing used.

Quote:
Taking a program from Windows to work on Linux would simply be
a matter of transferring the program but uniting it with the correct .dll.
I might be talking out of my hat but I think it's probably possible.

Possible, but overkill. First off because the library formats are different
under each platform so they have to be loaded in a platform-specific manner,
thus polluting the code. And second, the executables themselves are
different for each platform, so you can't simply compile an executable under
one platform and copy it to another platform and expect it to run. The
executable has to be compiled for the specific platform that it is going to
be run under.


Gambit



Back to top
Ken de Camargo Jr. [*TTFK
Guest





PostPosted: Sun Oct 12, 2003 12:12 am    Post subject: Re: wxWindows Reply with quote



Remy Lebeau (TeamB) wrote:

Quote:
That is a completely different matter. The issue around using
wxWindows is that it allows the same source code to be compiled into
a single executable under different platforms without using external
modules/dlls befing used.

Although you can use it in dynamic libraries too if you want.

--
Ken [*The Team Formerly Known As D]
MoNBH/MDNPEI
http://planeta.terra.com.br/educacao/kencamargo/

Hey! Someone left a tagline here:

Back to top
Digby Millikan
Guest





PostPosted: Sun Oct 12, 2003 4:13 am    Post subject: Re: wxWindows Reply with quote

So does wxWindows not only replace VCL but also WinAPI and other API's?

Digby Millikan
Geolite Mining Systems
http://www.users.on.net/digbym


Back to top
Remy Lebeau (TeamB)
Guest





PostPosted: Sun Oct 12, 2003 4:42 am    Post subject: Re: wxWindows Reply with quote

"Digby Millikan" <digbym (AT) internode (DOT) on.net> wrote

Quote:
So does wxWindows not only replace VCL but also
WinAPI and other API's?

No. Like any other platform framework, it sits on top of the platform's own
API at the lower levels, and just adds layers of abstraction so that your
code doesn't have to deal with the platform APIs directly, but the API
itself still exists, and like the VCL, it provides access to the lower level
objects provided by the platform if you wish to use the API directlty to
manipulate them.

And as for it replacing the VCL, that is still to be seen...


Gambit



Back to top
Digby Millikan
Guest





PostPosted: Sun Oct 12, 2003 12:01 pm    Post subject: Re: wxWindows Reply with quote


"Remy Lebeau (TeamB)" <gambit47.no.spam (AT) no (DOT) spam.yahoo.com> wrote

Quote:


And as for it replacing the VCL, that is still to be seen...


Gambit



Hopefully not! I've just written 85,000 lines of code with VCL.
VCL seems to have reached a satisfactory level of development that there
should be no reason Borland could not continue to have it in their compiler
and also in the IDE, as it needs minimal ongoing maintenance to retain a
system that has taken so long to develop.
The ideal path most users would like to see would be a product where
users have the option of developing code in VCL or wxWindows, or a
combination of both, so users can establish the portability of code
themselves.
Looking forward to hearing the news from Borland!

Regards Digby Millikan
http://www.users.on.net/digbym



Back to top
Ken de Camargo Jr. [*TTFK
Guest





PostPosted: Sun Oct 12, 2003 2:56 pm    Post subject: Re: wxWindows Reply with quote

Digby Millikan wrote:

Quote:
Looking forward to hearing the news from Borland!

It will be a while. And don't hold many expectations.

--
Ken [*The Team Formerly Known As D]
MoNBH/MDNPEI
http://planeta.terra.com.br/educacao/kencamargo/

Hey! Someone left a tagline here:

Back to top
Jeff Weir
Guest





PostPosted: Sun Oct 12, 2003 3:32 pm    Post subject: Re: wxWindows Reply with quote

Digby Millikan wrote:

Quote:
The ideal path most users would like to see would be a product where
users have the option of developing code in VCL or wxWindows, or a
combination of both, so users can establish the portability of code
themselves.


And the compiler that works with the VCL can forget about 100% Standard
C++ langauge conformance, right? No boost, loki, etc. That's what
C++BuilderX is for. Freeze the compiler at version 5.6.x. Update it, but
only when it is required to maintain compatibility with the updated VCL.
This is a reasonable trade-off isn't it?

reagrds,

jeff


Back to top
Ken de Camargo Jr. [*TTFK
Guest





PostPosted: Sun Oct 12, 2003 3:36 pm    Post subject: Re: wxWindows Reply with quote

Jeff Weir wrote:

Quote:
And the compiler that works with the VCL can forget about 100%
Standard C++ langauge conformance, right?

Nope. AFAIK the standard does not ban extensions.

--
Ken [*The Team Formerly Known As D]
MoNBH/MDNPEI
http://planeta.terra.com.br/educacao/kencamargo/

Hey! Someone left a tagline here:

Back to top
Edward Diener
Guest





PostPosted: Sun Oct 12, 2003 3:40 pm    Post subject: Re: wxWindows Reply with quote

Jeff Weir wrote:
Quote:
Digby Millikan wrote:

The ideal path most users would like to see would be a product where
users have the option of developing code in VCL or wxWindows, or a
combination of both, so users can establish the portability of code
themselves.


And the compiler that works with the VCL can forget about 100%
Standard C++ langauge conformance, right? No boost, loki, etc. That's
what C++BuilderX is for. Freeze the compiler at version 5.6.x. Update
it, but only when it is required to maintain compatibility with the
updated VCL. This is a reasonable trade-off isn't it?

There is no reason that Borland couldn't theoretically create a 100%
Standard C++ language compiler and have a compiler switch, to be turned on
for VCL programming, which also accepts VCL extensions and VCL-isms and
still allows 100% Ansi C++ compliance in non-VCL related code.



Back to top
Jeff Weir
Guest





PostPosted: Sun Oct 12, 2003 3:40 pm    Post subject: Re: wxWindows Reply with quote

Ken de Camargo Jr. [*TTFKAD] wrote:

Quote:

Nope. AFAIK the standard does not ban extensions.


My point was VCL compatibilty is more important than cross
platform/compiler portability - sorry to have confused the issue.

regards,

jeff


Back to top
Jeff Weir
Guest





PostPosted: Sun Oct 12, 2003 3:46 pm    Post subject: Re: wxWindows Reply with quote

Edward Diener wrote:

Quote:

There is no reason that Borland couldn't theoretically create a 100%
Standard C++ language compiler and have a compiler switch, to be turned on
for VCL programming, which also accepts VCL extensions and VCL-isms and
still allows 100% Ansi C++ compliance in non-VCL related code.


Of course that is true. But, just in case they think that it's is more
trouble than it's worth I am happy with the current language support. I
just want to keep using C++ and the VCL.

regards,

jeff



Back to top
Remy Lebeau (TeamB)
Guest





PostPosted: Sun Oct 12, 2003 9:38 pm    Post subject: Re: wxWindows Reply with quote

"Digby Millikan" <digbym (AT) internode (DOT) on.net> wrote


Quote:
Hopefully not! I've just written 85,000 lines of code with VCL.

My company's primary product contains over 2 million lines of code and over
50 forms.

Quote:
VCL seems to have reached a satisfactory level of development
that there should be no reason Borland could not continue to have
it in their compiler and also in the IDE

It has already been proven that BCB6's VCL can be used in CBX, it just can't
be visually designed because there are no VCL editors in CBX at this time.

Quote:
as it needs minimal ongoing maintenance to retain a system that
has taken so long to develop.

Except for the fact that the VCL is primarily maintained by the Delphi
development group, not the C++ group. Certain reorganizations at Borland
causes the two groups to go their separate ways, essentially telling the C++
group that if they want to continue providing support for the VCL, they
would have to do it themselves. At least that is how I heard it. And then
with the introduction of CBX, there was a decision to be made - 1) maintain
the Pascal VCL as-is, 2) re-write the Pascal VCL in C++ but otherwise keep
it the same, or 3) make a new library from scratch to take advantage of the
C++ language and its features. There were early experiments done with #2,
and from what I had heard awhile back, there was some success with it.
Later on, when I heard that #3 was being persued instead, I was just as
surprised as everyone else to hear it. Why they did not continue to persue
#2, I do not know even to this day.


Gambit



Back to top
AlisdairM
Guest





PostPosted: Sun Oct 12, 2003 11:36 pm    Post subject: Re: wxWindows Reply with quote

"Remy Lebeau (TeamB)" <gambit47.no.spam (AT) no (DOT) spam.yahoo.com> wrote in
news:3f89cc34$1 (AT) newsgroups (DOT) borland.com:

Quote:
My company's primary product contains over 2 million lines of code and
over 50 forms.

<quickly scans source tree>
Close to 500 forms in ours, although only 1 million lines of code.

Pointlessly competitive? Who, me? <g>

AlisdairM

Back to top
Remy Lebeau (TeamB)
Guest





PostPosted: Sun Oct 12, 2003 11:47 pm    Post subject: Re: wxWindows Reply with quote


"AlisdairM" <alisdair.meredith (AT) uk (DOT) renaultf1.com> wrote


Quote:
Close to 500 forms in ours

Ouch


Gambit



Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (Non-Technical) All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.