AccountWizard - LIB
DirectorySeviesUI - LIB
Eudora - EXE (of course)
EudoraOldIcons - DLL
EudoraEes - DLL
EulMap - LIB
EuLang - DLL
Imap - DLL
NSImport - DLL
OEImport - DLL
OLImport - DLL
OpenSSL - (not sure. Pete is working on this one. Looks like a LIB)
OT501 - Lib (! Not what I would have wished for.)
QCSocket - DLL
QCUtils - DLL
SearchEngiine - LIB
QCSLL - N/A, not present.
These are the libraries present in the code. A project can end with up
with another name if so configured, but it's not normally done.
What worries me is that I seem to keep hear mentions of other DLLs,
which are clearly not system DLLs but integral parts of Eudora.
Unless there's a magic drawer in the hosted code I haven't looked in, and I
blankly admit that this might very well be the case, I can't find the DLLs.
They must be part of a working installation though. If not the app simply
wouldn't work.
Nonetheless, I can't find this DLL in neither the codebase or the Eudora
client I have installed myself(!)
On Thursday, October 4, 2018, sbrothy@gmail.com wrote:
When the project opens it opens like this:
AccountWizard - LIB
DirectorySeviesUI - LIB
Eudora - EXE (of course)
EudoraOldIcons - DLL
EudoraEes - DLL
EulMap - LIB
EuLang - DLL
Imap - DLL
NSImport - DLL
OEImport - DLL
OLImport - DLL
OpenSSL - (not sure. Pete is working on this one. Looks like a LIB)
OT501 - Lib (! Not what I would have wished for.)
QCSocket - DLL
QCUtils - DLL
SearchEngiine - LIB
QCSLL - N/A, not present.
These are the libraries present in the code. A project can end with up
with another name if so configured, but it's not normally done.
What worries me is that I seem to keep hear mentions of other DLLs,
which are clearly not system DLLs but integral parts of Eudora.
Unless there's a magic drawer in the hosted code I haven't looked in, and I
blankly admit that this might very well be the case, I can't find the DLLs.
They must be part of a working installation though. If not the app simply
wouldn't work.
Nonetheless, I can't find this DLL in neither the codebase or the Eudora
client I have installed myself(!)
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see where
it comes from.
This was what I was after, a list of exported functions from that DLL. I
cannot find the include file "ssce.h" though, supposedly part of the Eudora
project itself. and I've searched my entire HDD:
Microsoft (R) COFF/PE Dumper Version 14.15.26726.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file SPELL32.DLL
File Type: DLL
Section contains the following exports for SSCE4232.dll
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see where
it comes from.
I see there's at some HUNSPELL API functions with the exact same names. If
they do the exact same thing though, I'm not sure.
Here comes another dumb question. I guess I'll have to replace the spell
dialog with MFC to start with, but where is this dialog in the application?
I've searched and failed to find it. I tried the help but that doesn't work
in my copy here. Depending on how complicated it I migt just need a picture
of it.
This was what I was after, a list of exported functions from that DLL. I
cannot find the include file "ssce.h" though, supposedly part of the Eudora
project itself. and I've searched my entire HDD:
Microsoft (R) COFF/PE Dumper Version 14.15.26726.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file SPELL32.DLL
File Type: DLL
Section contains the following exports for SSCE4232.dll
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see where
it comes from.
I see there's at some HUNSPELL API functions with the exact same names. If
they do the exact same thing though, I'm not sure.
Here comes another dumb question. I guess I'll have to replace the spell
dialog with MFC to start with, but where is this dialog in the application?
I've searched and failed to find it. I tried the help but that doesn't work
in my copy here. Depending on how complicated it I migt just need a picture
of it.
This was what I was after, a list of exported functions from that DLL. I
cannot find the include file "ssce.h" though, supposedly part of the Eudora
project itself. and I've searched my entire HDD:
Microsoft (R) COFF/PE Dumper Version 14.15.26726.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file SPELL32.DLL
File Type: DLL
Section contains the following exports for SSCE4232.dll
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see
where
it comes from.
I have the code for it ofcourse, but I'd like to see it, and the project
doesn compile.
On Fri, Oct 5, 2018 at 1:45 PM sbrothy@gmail.com wrote:
I see there's at some HUNSPELL API functions with the exact same names. If
they do the exact same thing though, I'm not sure.
Here comes another dumb question. I guess I'll have to replace the spell
dialog with MFC to start with, but where is this dialog in the application?
I've searched and failed to find it. I tried the help but that doesn't work
in my copy here. Depending on how complicated it I migt just need a picture
of it.
Regards.
On Fri, Oct 5, 2018 at 1:39 PM sbrothy@gmail.com wrote:
This was what I was after, a list of exported functions from that DLL. I
cannot find the include file "ssce.h" though, supposedly part of the Eudora
project itself. and I've searched my entire HDD:
Microsoft (R) COFF/PE Dumper Version 14.15.26726.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file SPELL32.DLL
File Type: DLL
Section contains the following exports for SSCE4232.dll
00000000 characteristics
32875701 time date stamp Mon Nov 11 17:40:33 1996
0.00 version
1 ordinal base
59 number of functions
59 number of names
On Fri, Oct 5, 2018 at 1:24 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see
where
it comes from.
Sorry for wasting your time.
Regards.
On Fri, Oct 5, 2018 at 1:21 PM Pete Maclean
petemaclean@users.sourceforge.net %0Dpetemaclean@users.sourceforge.net
wrote:
I am a bit puzzled as to why you would ask about this when you surely can
determine the answer for yourself. Nevertheless I am happy to oblige.
The original name of the DLL, as supplied by Wintertree Software, is
SSCE4232.DLL. In the Eudora context, it was renamed to SPELL32.DLL.
I find it endlessly strange that you are unable to find files that I have no trouble finding. In this case, spellpaige.h and spellpaige.cpp, which I will send to you by email.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm as mystified as you, if not more. But when I open a project and see
files being part of the project I expect them to open when I double-click
them. I can find some files called "spellpaige.h.i" and "spellpaige.cpp.i"
but these are binary.
I find it endlessly strange that you are unable to find files that I have
no trouble finding. In this case, spellpaige.h and spellpaige.cpp, which I
will send to you by email.
Ah, your message hints at why we see things differently. Apparently when you refer to a file as "missing" you mean only that it is not present in the current Hermes project. When I look for a file I look in both the Hermes project and in the original Eudora files.
spellpaige.h and spellpaige.cpp are there in the Eudora sources (under "Eudora71\Eudora") and were also in the original Hermes sources but were removed from the latter since it is not clear that we can use them. The trouble is that they were removed by Jeff Prickett who mercilessly tore out lots of files without removing or cleaning up references to those files. (I fear he may have done more harm than good in this respect.)
The fact that the Paige library sources were included in the open-sourcing could, I suppose, be seen as a tacit hint that we would be okay using them. I would not, however, be party to doing that without obtaining very confident legal advice.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah. So it's a giant misunderstanding on my part! I hope you'll admit that
it's a little weird referring to the project as Hermes when it is in fact
called Eudora.
What's even weirder, is that Windows didn't find anything when I made an
explicit search. But I've experienced something similar on Windows before.
I suspect that if I'd downloadet the project on my Linux box I would have
found it immediately.
Now we have an explanation though. Wonderful. This will hopefully stop my
stupid questions and the waste of your time.
Ah, your message hints at why we see things differently. Apparently when
you refer to a file as "missing" you mean only that it is not present in
the current Hermes project. When I look for a file I look in both the
Hermes project and in the original Eudora files.
spellpaige.h and spellpaige.cpp are there in the Eudora sources (under
"Eudora71\Eudora") and were also in the original Hermes sources but were
removed from the latter since it is not clear that we can use them. The
trouble is that they were removed by Jeff Prickett who mercilessly tore out
lots of files without removing or cleaning up references to those files. (I
fear he may have done more harm than good in this respect.)
The fact that the Paige library sources were included in the open-sourcing
could, I suppose, be seen as a tacit hint that we would be okay using them.
I would not, however, be party to doing that without obtaining very
confident legal advice.
Ah, your message hints at why we see things differently. Apparently
when you refer to a file as "missing" you mean only that it is not
present in the current Hermes project. When I look for a file I look
in both the Hermes project and in the original Eudora files.
spellpaige.h and spellpaige.cpp are there in the Eudora sources
(under "Eudora71\Eudora") and were also in the original Hermes
sources but were removed from the latter since it is not clear that
we can use them. The trouble is that they were removed by Jeff
Prickett who mercilessly tore out lots of files without removing or
cleaning up references to those files. (I fear he may have done more
harm than good in this respect.)
The fact that the Paige library sources were included in the
open-sourcing could, I suppose, be seen as a tacit hint that we
would be okay using them. I would not, however, be party to doing
that without obtaining very confident legal advice.
We are definitely OK to use Paige. First of all, the usual Paige
licencing agreement was that the source of whatever version you
bought was yours to use and share. Second, DataPak has gone under
and left no corporate successor; the copyright is in much the same
lacuna as Symbolics Genera.
I've spoken to Manuel Lauro in regards to this; he's a good IP lawyer
and I trust him. I wholly support using the Paige code because it is
lightweight and secure, but we could, I suppose, use another
rich-text control...
AFAIR, both MFC and WxWidgets has richeditctrls. SpellPaige may be
superior, I haven't seen it yet. If at some time we're gonna migrate to
WxWidgets I dunno if SpellPaige can follow. But I'm definitely of the
opinion that we shouldn't throw tested and tried code out the window
without a good reason.
Ah, your message hints at why we see things differently. Apparently
when you refer to a file as "missing" you mean only that it is not
present in the current Hermes project. When I look for a file I look
in both the Hermes project and in the original Eudora files.
spellpaige.h and spellpaige.cpp are there in the Eudora sources
(under "Eudora71\Eudora") and were also in the original Hermes
sources but were removed from the latter since it is not clear that
we can use them. The trouble is that they were removed by Jeff
Prickett who mercilessly tore out lots of files without removing or
cleaning up references to those files. (I fear he may have done more
harm than good in this respect.)
The fact that the Paige library sources were included in the
open-sourcing could, I suppose, be seen as a tacit hint that we
would be okay using them. I would not, however, be party to doing
that without obtaining very confident legal advice.
We are definitely OK to use Paige. First of all, the usual Paige
licencing agreement was that the source of whatever version you
bought was yours to use and share. Second, DataPak has gone under
and left no corporate successor; the copyright is in much the same
lacuna as Symbolics Genera.
I've spoken to Manuel Lauro in regards to this; he's a good IP lawyer
and I trust him. I wholly support using the Paige code because it is
lightweight and secure, but we could, I suppose, use another
rich-text control...
That is most excellent. If nobody objects, I will reinstate the Paige files into the Hermes solution and see if it builds. I too have concerns about Paige's interaction with WxWidgets but we can see about that later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On Thursday, October 4, 2018, sbrothy@gmail.com wrote:
What worries me is that I seem to keep hear mentions of other DLLs,
which are clearly not system DLLs but integral parts of Eudora.
Unless there's a magic drawer in the hosted code I haven't looked in, and I
blankly admit that this might very well be the case, I can't find the DLLs.
They must be part of a working installation though. If not the app simply
wouldn't work.
Nonetheless, I can't find this DLL in neither the codebase or the Eudora
client I have installed myself(!)
--
Søren Bro Thygesen
The name of the spellchecker DLL should be something along the lines of:
scee5230.dll or
scce5232.dll
Anyone?
Regards
On Friday, October 5, 2018, Soren Bro sbrothy@users.sourceforge.net wrote:
--
Søren Bro Thygesen
I am a bit puzzled as to why you would ask about this when you surely can determine the answer for yourself. Nevertheless I am happy to oblige.
The original name of the DLL, as supplied by Wintertree Software, is SSCE4232.DLL. In the Eudora context, it was renamed to SPELL32.DLL.
Ah yes. Sorry. I got confused there. There seems to be several copies of
this DLL with varying names. I'll go through the config again to see where
it comes from.
Sorry for wasting your time.
Regards.
On Fri, Oct 5, 2018 at 1:21 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
This was what I was after, a list of exported functions from that DLL. I
cannot find the include file "ssce.h" though, supposedly part of the Eudora
project itself. and I've searched my entire HDD:
Microsoft (R) COFF/PE Dumper Version 14.15.26726.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file SPELL32.DLL
File Type: DLL
Section contains the following exports for SSCE4232.dll
Summary
On Fri, Oct 5, 2018 at 1:24 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
I see there's at some HUNSPELL API functions with the exact same names. If
they do the exact same thing though, I'm not sure.
Here comes another dumb question. I guess I'll have to replace the spell
dialog with MFC to start with, but where is this dialog in the application?
I've searched and failed to find it. I tried the help but that doesn't work
in my copy here. Depending on how complicated it I migt just need a picture
of it.
Regards.
On Fri, Oct 5, 2018 at 1:39 PM sbrothy@gmail.com wrote:
I have the code for it ofcourse, but I'd like to see it, and the project
doesn compile.
On Fri, Oct 5, 2018 at 1:45 PM sbrothy@gmail.com wrote:
Oh wait. This dialog isn't Sringray. Mea Culpa. I'd still like to see it
though.
Regards.
On Fri, Oct 5, 2018 at 1:47 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
It is in "Eudora71\Eudora\SpellDialog.cpp". I will send you an example by email.
Yes, I've found them. There are several. Unfortunately I cant' find neither
"ssce.h" nor spellpaige.h/.cpp.
Regards.
On Fri, Oct 5, 2018 at 2:03 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
I find it endlessly strange that you are unable to find files that I have no trouble finding. In this case, spellpaige.h and spellpaige.cpp, which I will send to you by email.
I'm as mystified as you, if not more. But when I open a project and see
files being part of the project I expect them to open when I double-click
them. I can find some files called "spellpaige.h.i" and "spellpaige.cpp.i"
but these are binary.
Am I fetching something different than you?
I do this from the CMD command line:
I'm then asked for as password, which I give and then it starts downloading
what is presumably everything.
But still, bits and pieces are missing which obviously, you have no trouble
finding?`
Regards.
On Fri, Oct 5, 2018 at 2:31 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
Ah, your message hints at why we see things differently. Apparently when you refer to a file as "missing" you mean only that it is not present in the current Hermes project. When I look for a file I look in both the Hermes project and in the original Eudora files.
spellpaige.h and spellpaige.cpp are there in the Eudora sources (under "Eudora71\Eudora") and were also in the original Hermes sources but were removed from the latter since it is not clear that we can use them. The trouble is that they were removed by Jeff Prickett who mercilessly tore out lots of files without removing or cleaning up references to those files. (I fear he may have done more harm than good in this respect.)
The fact that the Paige library sources were included in the open-sourcing could, I suppose, be seen as a tacit hint that we would be okay using them. I would not, however, be party to doing that without obtaining very confident legal advice.
Ah. So it's a giant misunderstanding on my part! I hope you'll admit that
it's a little weird referring to the project as Hermes when it is in fact
called Eudora.
What's even weirder, is that Windows didn't find anything when I made an
explicit search. But I've experienced something similar on Windows before.
I suspect that if I'd downloadet the project on my Linux box I would have
found it immediately.
Now we have an explanation though. Wonderful. This will hopefully stop my
stupid questions and the waste of your time.
Regards
On Friday, October 5, 2018, Pete Maclean petemaclean@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
Please do not be too concerned about wasting my time.
Between the lines:
The stupid questions OTOH we could do without.
:)
On Friday, October 5, 2018, Pete Maclean petemaclean@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
At 02:14 PM 10/5/2018, you wrote:
We are definitely OK to use Paige. First of all, the usual Paige
licencing agreement was that the source of whatever version you
bought was yours to use and share. Second, DataPak has gone under
and left no corporate successor; the copyright is in much the same
lacuna as Symbolics Genera.
I've spoken to Manuel Lauro in regards to this; he's a good IP lawyer
and I trust him. I wholly support using the Paige code because it is
lightweight and secure, but we could, I suppose, use another
rich-text control...
(AFK)
AFAIR, both MFC and WxWidgets has richeditctrls. SpellPaige may be
superior, I haven't seen it yet. If at some time we're gonna migrate to
WxWidgets I dunno if SpellPaige can follow. But I'm definitely of the
opinion that we shouldn't throw tested and tried code out the window
without a good reason.
Regards
On Saturday, October 6, 2018, Ted Matavka nmatavka@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
That is most excellent. If nobody objects, I will reinstate the Paige files into the Hermes solution and see if it builds. I too have concerns about Paige's interaction with WxWidgets but we can see about that later.