Technically, this is mostly for Pete and my eyes, but I'll put it in this
thread, so others can follow the process.
As I said before the MDI sample (showing how to implement the Multi
Document Interface) from the wxWidgets download looks like a good starting
point. We could use a WYSIWYG tool, like wxSmith or wxFormBuilder, but I'd
prefer to start without. The KISS principle.
I'll start by cleaning up this project. Putting the various classes in
their own headers/source files, and what else I can think of to make it
prettier.
Actually, I'd like to start from the complete beginning. Downloading the
cross-platform wxWidgets source code and compiling it myself. Following the
instructions in the attached install.txt document under "The Expert Case".
I'd like the finished program to be configure/make oriented, with
build-targets for the various platforms we want to support, and not tying
us to a particular IDE.
So far it seems like it still doesn't want anything to do with STL. I'm
still not sure how important this is to us. It can probably be configured
to accept it, but I'm going vanilla right now. Anyway, Boost provides
various container types as well, so we will not be lacking in those.
Yes. I would think so too. It may just be a switch we need to flip. How
pervasive is STL in the current code? A std::vector here and there, or is
it used extensively?
As I said, boost provides most, if not all, of the same functionality as
STL. So, a downright showstopper is may be a little strong. Some extra
work, definitely, but that's hardly a surprise. :)
Use of wchar_t is an absolute requirement in Windows but not a good choice for Linux. I don't know about MacOS; I have done a little development for Macs but that was so long ago that Unicode was not a consideration.
I have been aware all along that this would be a dicey issue for us although until recently I figured it was one we could deal with much later on. I will give it some serious thought.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No. I realise he sounds as if he's learning while writing it down. All I
was concerned about was that wchar_t is present on all the platforms we
plan to support. And from his feeble fumblings, it sounds as if they are.
Don't take that link too seriously. It was just meant as an assurance that
wchar_t is indeed available on all plarforms.
I found wxcrafter to be a program that wasn't free, but I found the
following package in my repository anyway:
wxcrafter-standalone - GUI RAD Tool for wxwidgets.
This might help. This WYSIWYG tool is probably one of the best and most
used. Even better than wxSmith and wxFormBuilder. I realise it's a matter
of taste and so forth, but one of the IDEs (codelite? Code::Blocks, has an
integrated Create->Project menu where this program is integral). Finding it
for free kinda surprised me.
No. I realise he sounds as if he's learning while writing it down. All I
was concerned about was that wchar_t is present on all the platforms we
plan to support. And from his feeble fumblings, it sounds as if they are.
Don't take that link too seriously. It was just meant as an assurance that
wchar_t is indeed available on all plarforms.
Just wondering whether or not IF YOU COULD contact Steve Dorner (the original Eudora programmer) would anything he told you be of any benefit OR can you guys all figure things out w/o his help?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just wondering whether or not IF YOU COULD contact Steve Dorner (the
original Eudora programmer) would anything he told you be of any benefit OR
can you guys all figure things out w/o his help?
Yes, Steve is the original "Eudora/Windows perpetrator" :-)
I just thought I would ask the question. He's on linkedin, so you could try contacting him there....should the need ever arise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed. Thank you very much for the pointer. I'm sure we'll disturb him
down the road. But not unless we have something concrete to ask about. I'm
sure he's busy doing something else by now. He's probably not interested in
essentially doing the same thing over again. So let's label him as a last
resort goto.
Yes, Steve is the original "Eudora/Windows perpetrator" :-)
I just thought I would ask the question. He's on linkedin, so you could
try contacting him there....should the need ever arise.
Well, we're pretty good on our own, with the danger of sounding arrogant.
He developed the Windows version right?
Steve Dorner is who originally wrote Eudora for the Mac single-handedly
all those years ago. From something I read the other day, he really was
not interested in the Windows version and it was written by a bunch of
other people at Qualcomm. So he would probably not be much use for
details. Also, he has cancer so has other things on his mind.
Well, we're pretty good on our own, with the danger of sounding
arrogant. He developed the Windows version right?
Steve developed, as far as I know, the Mac version.
Steve Dorner is who originally wrote Eudora for the Mac
single-handedly all those years ago. From something I read the other
day, he really was not interested in the Windows version and it was
written by a bunch of other people at Qualcomm. So he would probably
not be much use for details.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Also, he has cancer so has other things on his mind.
OK. I finally got the wxWidgets MDI sample to compile (Still without a
precompiled header though, which kinda irritates me). And yes, it's a good
starting point. See attached picture.
Well, we're pretty good on our own, with the danger of sounding
arrogant. He developed the Windows version right?
Steve developed, as far as I know, the Mac version.
Steve Dorner is who originally wrote Eudora for the Mac
single-handedly all those years ago. From something I read the other
day, he really was not interested in the Windows version and it was
written by a bunch of other people at Qualcomm. So he would probably
not be much use for details.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Also, he has cancer so has other things on his mind.
OK. I finally got the wxWidgets MDI sample to compile (Still without a
precompiled header though, which kinda irritates me). And yes, it's a good
starting point. See attached picture.
Well, we're pretty good on our own, with the danger of sounding
arrogant. He developed the Windows version right?
Steve developed, as far as I know, the Mac version.
Steve Dorner is who originally wrote Eudora for the Mac
single-handedly all those years ago. From something I read the other
day, he really was not interested in the Windows version and it was
written by a bunch of other people at Qualcomm. So he would probably
not be much use for details.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Also, he has cancer so has other things on his mind.
I'm importing it into codelite nonetheless though. We can put it back in
autohell when we want. The project also needs to be logically split up;
working on that. As it is, it's just two big files. Header and source. A
mess.
OK. I finally got the wxWidgets MDI sample to compile (Still without a
precompiled header though, which kinda irritates me). And yes, it's a good
starting point. See attached picture.
Well, we're pretty good on our own, with the danger of sounding
arrogant. He developed the Windows version right?
Steve developed, as far as I know, the Mac version.
Steve Dorner is who originally wrote Eudora for the Mac
single-handedly all those years ago. From something I read the other
day, he really was not interested in the Windows version and it was
written by a bunch of other people at Qualcomm. So he would probably
not be much use for details.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Also, he has cancer so has other things on his mind.
I'm importing it into codelite nonetheless though. We can put it back in
autohell when we want. The project also needs to be logically split up;
working on that. As it is, it's just two big files. Header and source. A
mess.
Regards.
On Fri, Sep 21, 2018 at 7:36 PM sbrothy@gmail.com wrote:
And even better. It uses the "autohell" tools. :)
Regards.
On Fri, Sep 21, 2018 at 7:35 PM sbrothy@gmail.com wrote:
OK. I finally got the wxWidgets MDI sample to compile (Still without a
precompiled header though, which kinda irritates me). And yes, it's a good
starting point. See attached picture.
Well, we're pretty good on our own, with the danger of sounding
arrogant. He developed the Windows version right?
Steve developed, as far as I know, the Mac version.
Steve Dorner is who originally wrote Eudora for the Mac
single-handedly all those years ago. From something I read the other
day, he really was not interested in the Windows version and it was
written by a bunch of other people at Qualcomm. So he would probably
not be much use for details.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Also, he has cancer so has other things on his mind.
Just wondering whether or not IF YOU COULD contact Steve Dorner (the
original Eudora programmer) would anything he told you be of any benefit OR
can you guys all figure things out w/o his help?
Technically, this is mostly for Pete and my eyes, but I'll put it in this
thread, so others can follow the process.
As I said before the MDI sample (showing how to implement the Multi
Document Interface) from the wxWidgets download looks like a good starting
point. We could use a WYSIWYG tool, like wxSmith or wxFormBuilder, but I'd
prefer to start without. The KISS principle.
I'll start by cleaning up this project. Putting the various classes in
their own headers/source files, and what else I can think of to make it
prettier.
Actually, I'd like to start from the complete beginning. Downloading the
cross-platform wxWidgets source code and compiling it myself. Following the
instructions in the attached install.txt document under "The Expert Case".
I'd like the finished program to be configure/make oriented, with
build-targets for the various platforms we want to support, and not tying
us to a particular IDE.
So far it seems like it still doesn't want anything to do with STL. I'm
still not sure how important this is to us. It can probably be configured
to accept it, but I'm going vanilla right now. Anyway, Boost provides
various container types as well, so we will not be lacking in those.
Regards.
If it truly cannot coexist with STL then I would say that is a show-stopper. But surely it must be compatible?
Yes. I would think so too. It may just be a switch we need to flip. How
pervasive is STL in the current code? A std::vector here and there, or is
it used extensively?
As I said, boost provides most, if not all, of the same functionality as
STL. So, a downright showstopper is may be a little strong. Some extra
work, definitely, but that's hardly a surprise. :)
Regards
On Monday, September 17, 2018, Pete Maclean petemaclean@users. sourceforge.net wrote:
--
Søren Bro Thygesen
Yeah. It's just a switch, see:
https://www.wxwidgets.org/docs/faq/general/#stl
Don't worry too much about that.
Regards
On Monday, September 17, 2018, Pete Maclean petemaclean@users.sourceforge.net wrote:
--
Søren Bro Thygesen
When using UNICODE on WxWidgets we're talking wchar_t. This is acceptable
across all the relevant platforms right?
And if not, we can typedef or #define us out of any problems, right?
Regards
On Monday, September 17, 2018, Pete Maclean petemaclean@users.sourceforge.net wrote:
--
Søren Bro Thygesen
I really don't know what else it would be. TCHAR is Windows specific isn't
it?
Regards
On Monday, September 17, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
My questions are mostly rhetorical. Just thinking out loud.....
Regards
On Monday, September 17, 2018, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
(AFK)
And yes. I'm not home.
Regards
On Monday, September 17, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
Use of wchar_t is an absolute requirement in Windows but not a good choice for Linux. I don't know about MacOS; I have done a little development for Macs but that was so long ago that Unicode was not a consideration.
I have been aware all along that this would be a dicey issue for us although until recently I figured it was one we could deal with much later on. I will give it some serious thought.
Nah. wchar_t shouldn't be a problem on any of the platforms. For instance:
http://www.firstobject.com/wchar_t-string-on-linux-osx-windows.htm
Yes, we might run into a couple of specific (fixable) problems, but as a
whole we should be OK.
Especially if we use boost.
I know I've been trying to sell boost pretty hard. But I have good reason.
This library is superior to anything else I've found in that genre.
Regards.
On Mon, Sep 17, 2018 at 4:01 PM sbrothy@gmail.com wrote:
For instance, a more or less random pick:
Array https://www.boost.org/doc/libs/1_68_0/libs/array/
STL compliant container wrapper for arrays of constant size.
Author(s)Nicolai JosuttisFirst Release1.17.0StandardTR1CategoriesContainers
https://www.boost.org/doc/libs/1_68_0/?view=category_containers ----
https://www.boost.org/doc/libs/1_68_0/
Regards.
On Mon, Sep 17, 2018 at 8:39 PM sbrothy@gmail.com wrote:
I think whoever wrote that piece (http://www.firstobject.com/wchar_t-string-on-linux-osx-windows.htm) is none too clear about the matter.
No. I realise he sounds as if he's learning while writing it down. All I
was concerned about was that wchar_t is present on all the platforms we
plan to support. And from his feeble fumblings, it sounds as if they are.
Don't take that link too seriously. It was just meant as an assurance that
wchar_t is indeed available on all plarforms.
Regards.
On Mon, Sep 17, 2018 at 8:53 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
I found wxcrafter to be a program that wasn't free, but I found the
following package in my repository anyway:
wxcrafter-standalone - GUI RAD Tool for wxwidgets.
This might help. This WYSIWYG tool is probably one of the best and most
used. Even better than wxSmith and wxFormBuilder. I realise it's a matter
of taste and so forth, but one of the IDEs (codelite? Code::Blocks, has an
integrated Create->Project menu where this program is integral). Finding it
for free kinda surprised me.
Regards.
On Mon, Sep 17, 2018 at 9:03 PM sbrothy@gmail.com wrote:
Just wondering whether or not IF YOU COULD contact Steve Dorner (the original Eudora programmer) would anything he told you be of any benefit OR can you guys all figure things out w/o his help?
(AFK)
Well, we're pretty good on our own, with the danger of sounding arrogant.
He developed the Windows version right?
He might be nice to have at hand for asking how the original program was /
is supposed to work.
I'm not stupid enough to refuse any help we can get. I'm just not sure
we're quite there where his knowledge will be of help.
Regards
On Monday, September 17, 2018, Walt Stagner wstagner@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
Yes, Steve is the original "Eudora/Windows perpetrator" :-)
I just thought I would ask the question. He's on linkedin, so you could try contacting him there....should the need ever arise.
Indeed. Thank you very much for the pointer. I'm sure we'll disturb him
down the road. But not unless we have something concrete to ask about. I'm
sure he's busy doing something else by now. He's probably not interested in
essentially doing the same thing over again. So let's label him as a last
resort goto.
Regards.
On Mon, Sep 17, 2018 at 7:20 PM Walt Stagner wstagner@users.sourceforge.net
wrote:
On 18/09/18 2:46 , Soren Bro wrote:
David
At 11:42 PM 9/17/2018, you wrote:
Steve developed, as far as I know, the Mac version.
No, he would not. On the other hand, Jeff Beckley would most
probably be considered the top authority on Eudora/Win, and that's
the codebase we're using even for the Mac version, so I would try
contacting him.
Very true.
OK. I finally got the wxWidgets MDI sample to compile (Still without a
precompiled header though, which kinda irritates me). And yes, it's a good
starting point. See attached picture.
Regards.
On Thu, Sep 20, 2018 at 12:41 AM Ted Matavka nmatavka@users.sourceforge.net
wrote:
And even better. It uses the "autohell" tools. :)
Regards.
On Fri, Sep 21, 2018 at 7:35 PM sbrothy@gmail.com wrote:
I'm importing it into codelite nonetheless though. We can put it back in
autohell when we want. The project also needs to be logically split up;
working on that. As it is, it's just two big files. Header and source. A
mess.
Regards.
On Fri, Sep 21, 2018 at 7:36 PM sbrothy@gmail.com wrote:
If I've been talking about exceptions - and I may very well have - the same
document has something to say on that issue too:
How to use C++ exceptions with wxWidgets?
---- https://www.wxwidgets.org/docs/faq/general/#exceptions
This makes exceptions a little moot. But how else deal with a window that
doesn't create? A simple message?
Regards.
On Fri, Sep 21, 2018 at 9:35 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
Back home.
Can we have him on hold? I'm sure an issue will turn up where his knowledge
will be of help.
Regards.
On Mon, Sep 17, 2018 at 6:35 PM Walt Stagner wstagner@users.sourceforge.net
wrote: