| Newsgroups |
gmane.comp.windows.eccopro |
| Message-ID |
<[email protected]> |
--------------6BED06E11753C3F8FD6AE33A
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Follow up. This is all intertangled wit many legal suits. I copied this
from Wikipedia and thought it might be of interest:
Lawsuit
Some have claimed that Quattro Pro was the first to use the tabbed
notebook metaphor - but another spreadsheet, Boeing Calc
<https://en.wikipedia.org/wiki/Boeing_Calc>, used tabs to multiple
sheets, and allowed three-dimensional references before Quattro Pro was
on the market. (Boeing Calc was so slow that its multiple sheet
capabilities were barely usable.)^[1]
<https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-boeingcalc-1> ^[2]
<https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-aresluna-2>
Quattro Pro was the subject of a major lawsuit by Lotus against Borland
<https://en.wikipedia.org/wiki/Lotus_v._Borland>. Lotus argued that
Quattro could not copy Lotus 1-2-3 menus (it did copy the menus).
Borland supplied the 1-2-3 menus as an alternative because keystroke
compatibility was needed in order to run macros
<https://en.wikipedia.org/wiki/Macro_(computer_science)> in 1-2-3
worksheets. Borland argued that most cars operate the same, but they are
not necessarily made the same. So, Lotus could not rationally "own" the
way its program behaved. The district court ruled in favor of Lotus, but
the appellate court ruled that the 1-2-3 menus were functional and not
copyrightable. The case went all the way to the U.S. Supreme Court which
split 4 to 4 (Justice Stevens
<https://en.wikipedia.org/wiki/Justice_Stevens> recused himself). This
left the lower court ruling intact, which was a victory for Borland.
However, the broader issue of whether a company can own and protect the
way its program behaves remained unresolved.
By the time the case was resolved, Borland no longer owned Quattro Pro.
Borland sold the spreadsheet to Novell
<https://en.wikipedia.org/wiki/Novell> six months before the final
decision was handed down.
Quattro Pro for Windows
Quattro Pro began as a DOS <https://en.wikipedia.org/wiki/DOS> program
(like Lotus 1-2-3) but with the growing popularity of Windows from
Microsoft, a Windows version of Quattro needed to be written. There was
almost nothing from the DOS code that could be moved to the Windows
project, so the Quattro Pro for Windows (QPW) was written from scratch.
Both the QPW and Paradox <https://en.wikipedia.org/wiki/Borland_Paradox>
for Windows codebases (the latter being another Borland database
application) were based on Borland's internal pilot project with object
oriented UI code for Windows. This project ran simultaneously with the
Borland language group investigating the desirability of a C++
<https://en.wikipedia.org/wiki/C%2B%2B> compiler, and the company
decided to make a bet on C++. However, the C++ compiler was not ready at
first, and OO code for both projects was started in C with OO emulation
through macros. As the Borland Turbo C++ compiler became available
internally the projects converted to using C++.
Charlie Anderson was put in charge of the project and he soon had Istvan
Cseri
<https://en.wikipedia.org/w/index.php?title=Istvan_Cseri&action=edit&redlink=1>,
Weikuo Liaw
<https://en.wikipedia.org/w/index.php?title=Weikuo_Liaw&action=edit&redlink=1>,
Murray Low
<https://en.wikipedia.org/w/index.php?title=Murray_Low&action=edit&redlink=1>,
Steven Boye
<https://en.wikipedia.org/w/index.php?title=Steven_Boye&action=edit&redlink=1>,
Barry Spencer
<https://en.wikipedia.org/w/index.php?title=Barry_Spencer&action=edit&redlink=1>,
Alan Bush, Dave Orton <https://en.wikipedia.org/wiki/Dave_Orton>, Bernie
Vachon
<https://en.wikipedia.org/w/index.php?title=Bernie_Vachon&action=edit&redlink=1>,
Anson Lee
<https://en.wikipedia.org/w/index.php?title=Anson_Lee&action=edit&redlink=1>,
Tod Landis, Gordon Ko and Chuck Batterman
<https://en.wikipedia.org/w/index.php?title=Chuck_Batterman&action=edit&redlink=1>
working on the project. Other engineers joined later. Eventually the
team numbered nearly 20. The object model was inspired by the NeXT
<https://en.wikipedia.org/wiki/NeXT> object model, modified by Mr.
Cseri. Mr. Liaw and Mr. Spencer were in charge of the spreadsheet engine
(written in assembly language) while Mr. Low wrote a large chunk of the UI.
The product was internally codenamed "Thor
<https://en.wikipedia.org/wiki/Thor>" for the Norse god of Thunder. QPW
featured two major innovations. First, it was the first Windows
spreadsheet with multiple pages with cells that could be linked together
seamlessly, a feature from Quattro Pro which QPW extended. Second, it
was the first released Windows program to have an attribute menu
<https://en.wikipedia.org/w/index.php?title=Attribute_menu&action=edit&redlink=1>
(or property pane
<https://en.wikipedia.org/w/index.php?title=Property_pane&action=edit&redlink=1>)
available by right-clicking on the object. Although this idea was first
seen on the Xerox Alto <https://en.wikipedia.org/wiki/Xerox_Alto>, the
idea had not been implemented on a major Windows program. Paradox for
Windows shared this feature, and it was shown off by Phillipe Kahn
<https://en.wikipedia.org/wiki/Phillipe_Kahn> at a Paradox user
conference over a year before QPW was released. Both these ideas became
widespread in the software industry.
QPW was one of the first big applications written in C++ on Windows, and
it pushed the Borland C++ compiler to the limit. One reason why the
Borland C++ Compiler was so good was that it had to compile and link the
massive QPW code base successfully.
The technical risk of the QPW project was immense. The object model was
untried and might not have worked for a spreadsheet. The user interface
(UI) was new (for Windows programs at least). No one knew if the C++
compiler could generate fast enough code. As it turned out, the program
worked. It was fast, it was close in feature set to Lotus 123 and Excel,
and the "right-click for properties" user design was reasonably
understandable.
At one point, it was hoped that QPW and Paradox for Windows would be
able to share a common object model. That proved impossible despite
serious thought and design efforts.
QPW was finally released in September 1992. The Quattro Pro marketing
team had chosen to bundle both Quattro Pro for DOS and Quattro Pro for
Windows in the same box labeled "WIN-DOS" at a price of $495. Customers
and reviewers expecting a pure Windows application responded with
confusion and outrage, believing the product was merely a DOS
application with windowing capabilities. Shortly thereafter QPW was
re-packaged by itself and priced $129, receiving accolades for Borland's
long-delayed pure Windows spreadsheet and its popular price.
Eventually it sold well (after the price was slashed to just $49 a
copy). Work was started immediately on a new version with a brand new
team of engineers led by Joe Ammirato
<https://en.wikipedia.org/w/index.php?title=Joe_Ammirato&action=edit&redlink=1>;
including Bret Gillis
<https://en.wikipedia.org/w/index.php?title=Bret_Gillis&action=edit&redlink=1>
and Peter Weyzen
<https://en.wikipedia.org/w/index.php?title=Peter_Weyzen&action=edit&redlink=1>.
Borland purchased DataPivot
<https://en.wikipedia.org/w/index.php?title=DataPivot&action=edit&redlink=1>
from Brio Technology <https://en.wikipedia.org/wiki/Brio_Technology> to
add a new feature to the program. Colin Glassey came from Brio to help
with the integration of that technology.
After a year and the merging of the old team and the new team, QPW 5 was
released (the reason for the jump in version number had to do with
keeping up with the DOS version as well as it looked good). QPW 5 sold
well also, though the Microsoft Excel
<https://en.wikipedia.org/wiki/Microsoft_Excel> + Word combination was
gaining steam.
Work then started on version 6 (now with Steven Boye
<https://en.wikipedia.org/w/index.php?title=Steven_Boye&action=edit&redlink=1>
as project lead). Midway through the development of version 6 a
strategic decision to work closely with the WordPerfect
<https://en.wikipedia.org/wiki/WordPerfect> word processor was made. It
was a direct attempt to push back at the Microsoft Office one-two punch
of Microsoft Word <https://en.wikipedia.org/wiki/Microsoft_Office_Word>
and Microsoft Excel. The other big issue with Version 6 was the advent
of Windows 95 <https://en.wikipedia.org/wiki/Windows_95>. This was a
significant modification to the Windows operating system with a major
change to user interface guidelines.
In an odd set of events, Novell <https://en.wikipedia.org/wiki/Novell>
purchased both WordPerfect Corporation and the Quattro Pro code base and
team of engineers from Borland. Novell was going to try to be a real
competitor to Microsoft. Although Version 6 was released and some effort
was made to unify the user interface between WordPerfect and QPW, the
effort was far from complete.
In another lawsuit, Novell claims that Microsoft had "deliberately
targeted and destroyed" its WordPerfect and QuattroPro programs to
protect its Windows operating system monopoly. The US Supreme Court
refused to halt the antitrust lawsuit in March 2008.^[4]
<https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-4>
Novell's exit
The release of Windows 95 in August 1995 was the beginning of the end
for Novell and its plans to compete with Microsoft. Not only did
Microsoft release a new operating system, but Microsoft also released
new versions of Word and Excel to accompany it. Sales of Novell
PerfectOffice (and Lotus applications as well) sank to almost nothing
while sales of the Microsoft products were huge.^[/citation needed
<https://en.wikipedia.org/wiki/Wikipedia:Citation_needed>/] Within three
months, Novell announced they were going to sell their applications to
someone (eventually that proved to be Corel
<https://en.wikipedia.org/wiki/Corel>). By mid-1996, Microsoft had 95%
of the market for business applications. As of 2005, Microsoft still
dominates the market for Windows business application
software,^[/citation needed
<https://en.wikipedia.org/wiki/Wikipedia:Citation_needed>/] although
Quattro Pro and WordPerfect, which pre-dated the MS Office 4.2 suite,
are still both updated and s
------------------------------------------------------------------------------------------------------------
On 8/22/2019 4:31 PM, 'Clyde Christofferson' [email protected]
[eccopro] wrote:
> My first copy of ECCO came with the Arabesque name on the manual.
> That was decades ago.
>
> I came across an old email (from 2008) suggesting there had been some
> concern that Netmanage might revoke the license (under which all of us
> are able to use ECCO for free). I have the vaguest recollection from
> those days and earlier. Something fishy was going on in the board
> rooms of big players in the PIM industry, at least thats what many of
> us thought.
>
> ECCO is still as far as I am concerned the best and most versatile
> outliner out there. For years I have used it to build and maintain a
> docketing system tailored to my own needs. Im going to be in great
> distress and a state of mourning if and when it no longer runs on
> available operating systems.
>
> *From:* [email protected] <[email protected]>
> *Sent:* Thursday, August 22, 2019 3:30 PM
> *To:* [email protected]
> *Subject:* [eccopro] Re: Ecco Happy Place / Arabesque
>
>
> Arabesque was the name of the software company that developed and
> marketed Ecco Pro.
>
>
--------------6BED06E11753C3F8FD6AE33A
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
</head>
<body style="background-color: #fff;">
<span style="display:none"> </span>
<!--~-|**|PrettyHtmlStartT|**|-~-->
<div id="ygrp-mlmsg" style="position:relative;">
<div id="ygrp-msg" style="z-index: 1;">
<!--~-|**|PrettyHtmlEndT|**|-~-->
<div id="ygrp-text" >
<p>
<p>Follow up. This is all intertangled wit many legal suits. I
copied this from Wikipedia and thought it might be of interest:</p>
<h2><span class="mw-headline" id="Lawsuit">Lawsuit</span></h2>
<p>Some have claimed that Quattro Pro was the first to use the
tabbed notebook metaphor - but another spreadsheet, <a href="https://en.wikipedia.org/wiki/Boeing_Calc" title="Boeing
Calc">Boeing Calc</a>, used tabs to multiple sheets, and allowed
three-dimensional references before Quattro Pro was on the market.
(Boeing Calc was so slow that its multiple sheet capabilities were
barely usable.)<sup id="cite_ref-boeingcalc_1-1" class="reference"><a href="https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-boeingcalc-1">[1]</a></sup><sup id="cite_ref-aresluna_2-1" class="reference"><a href="https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-aresluna-2">[2]</a></sup>
</p>
<p>Quattro Pro was the subject of a major <a href="https://en.wikipedia.org/wiki/Lotus_v._Borland" class="mw-redirect" title="Lotus v. Borland">lawsuit by Lotus
against Borland</a>. Lotus argued that Quattro could not copy
Lotus 1-2-3 menus (it did copy the menus). Borland supplied the
1-2-3 menus as an alternative because keystroke compatibility was
needed in order to run <a href="https://en.wikipedia.org/wiki/Macro_(computer_science)" title="Macro (computer science)">macros</a> in 1-2-3 worksheets.
Borland argued that most cars operate the same, but they are not
necessarily made the same. So, Lotus could not rationally "own"
the way its program behaved. The district court ruled in favor of
Lotus, but the appellate court ruled that the 1-2-3 menus were
functional and not copyrightable. The case went all the way to the
U.S. Supreme Court which split 4 to 4 (<a href="https://en.wikipedia.org/wiki/Justice_Stevens" class="mw-redirect" title="Justice Stevens">Justice Stevens</a>
recused himself). This left the lower court ruling intact, which
was a victory for Borland. However, the broader issue of whether a
company can own and protect the way its program behaves remained
unresolved.
</p>
<p>By the time the case was resolved, Borland no longer owned
Quattro Pro. Borland sold the spreadsheet to <a href="https://en.wikipedia.org/wiki/Novell" title="Novell">Novell</a>
six months before the final decision was handed down.
</p>
<h2><span class="mw-headline" id="Quattro_Pro_for_Windows">Quattro
Pro for Windows</span></h2>
<p>Quattro Pro began as a <a href="https://en.wikipedia.org/wiki/DOS" title="DOS">DOS</a>
program (like Lotus 1-2-3) but with the growing popularity of
Windows from Microsoft, a Windows version of Quattro needed to be
written. There was almost nothing from the DOS code that could be
moved to the Windows project, so the Quattro Pro for Windows (QPW)
was written from scratch.
</p>
<p>Both the QPW and <a href="https://en.wikipedia.org/wiki/Borland_Paradox" class="mw-redirect" title="Borland Paradox">Paradox</a> for
Windows codebases (the latter being another Borland database
application) were based on Borland's internal pilot project with
object oriented UI code for Windows. This project ran
simultaneously with the Borland language group investigating the
desirability of a <a href="https://en.wikipedia.org/wiki/C%2B%2B" title="C++">C++</a> compiler, and the company decided to make a
bet on C++. However, the C++ compiler was not ready at first, and
OO code for both projects was started in C with OO emulation
through macros. As the Borland Turbo C++ compiler became available
internally the projects converted to using C++.
</p>
<p>Charlie Anderson was put in charge of the project and he soon had
<a href="https://en.wikipedia.org/w/index.php?title=Istvan_Cseri&action=edit&redlink=1" class="new" title="Istvan Cseri (page does not exist)">Istvan
Cseri</a>, <a href="https://en.wikipedia.org/w/index.php?title=Weikuo_Liaw&action=edit&redlink=1" class="new" title="Weikuo Liaw (page does not exist)">Weikuo
Liaw</a>, <a href="https://en.wikipedia.org/w/index.php?title=Murray_Low&action=edit&redlink=1" class="new" title="Murray Low (page does not exist)">Murray Low</a>,
<a href="https://en.wikipedia.org/w/index.php?title=Steven_Boye&action=edit&redlink=1" class="new" title="Steven Boye (page does not exist)">Steven
Boye</a>, <a href="https://en.wikipedia.org/w/index.php?title=Barry_Spencer&action=edit&redlink=1" class="new" title="Barry Spencer (page does not exist)">Barry
Spencer</a>, Alan Bush, <a href="https://en.wikipedia.org/wiki/Dave_Orton" class="mw-redirect" title="Dave Orton">Dave Orton</a>, <a href="https://en.wikipedia.org/w/index.php?title=Bernie_Vachon&action=edit&redlink=1" class="new" title="Bernie Vachon (page does not exist)">Bernie
Vachon</a>, <a href="https://en.wikipedia.org/w/index.php?title=Anson_Lee&action=edit&redlink=1" class="new" title="Anson Lee (page does not exist)">Anson Lee</a>,
Tod Landis, Gordon Ko and <a href="https://en.wikipedia.org/w/index.php?title=Chuck_Batterman&action=edit&redlink=1" class="new" title="Chuck Batterman (page does not exist)">Chuck
Batterman</a> working on the project. Other engineers joined
later. Eventually the team numbered nearly 20. The object model
was inspired by the <a href="https://en.wikipedia.org/wiki/NeXT" title="NeXT">NeXT</a> object model, modified by Mr. Cseri. Mr.
Liaw and Mr. Spencer were in charge of the spreadsheet engine
(written in assembly language) while Mr. Low wrote a large chunk
of the UI.
</p>
<p>The product was internally codenamed "<a href="https://en.wikipedia.org/wiki/Thor" title="Thor">Thor</a>"
for the Norse god of Thunder. QPW featured two major innovations.
First, it was the first Windows spreadsheet with multiple pages
with cells that could be linked together seamlessly, a feature
from Quattro Pro which QPW extended. Second, it was the first
released Windows program to have an <a href="https://en.wikipedia.org/w/index.php?title=Attribute_menu&action=edit&redlink=1" class="new" title="Attribute menu (page does not exist)">attribute
menu</a> (or <a href="https://en.wikipedia.org/w/index.php?title=Property_pane&action=edit&redlink=1" class="new" title="Property pane (page does not exist)">property
pane</a>) available by right-clicking on the object. Although
this idea was first seen on the <a href="https://en.wikipedia.org/wiki/Xerox_Alto" title="Xerox
Alto">Xerox Alto</a>, the idea had not been implemented on a
major Windows program. Paradox for Windows shared this feature,
and it was shown off by <a href="https://en.wikipedia.org/wiki/Phillipe_Kahn" class="mw-redirect" title="Phillipe Kahn">Phillipe Kahn</a> at a
Paradox user conference over a year before QPW was released. Both
these ideas became widespread in the software industry.
</p>
<p>QPW was one of the first big applications written in C++ on
Windows, and it pushed the Borland C++ compiler to the limit. One
reason why the Borland C++ Compiler was so good was that it had to
compile and link the massive QPW code base successfully.
</p>
<p>The technical risk of the QPW project was immense. The object
model was untried and might not have worked for a spreadsheet. The
user interface (UI) was new (for Windows programs at least). No
one knew if the C++ compiler could generate fast enough code. As
it turned out, the program worked. It was fast, it was close in
feature set to Lotus 123 and Excel, and the "right-click for
properties" user design was reasonably understandable.
</p>
<p>At one point, it was hoped that QPW and Paradox for Windows would
be able to share a common object model. That proved impossible
despite serious thought and design efforts.
</p>
<p>QPW was finally released in September 1992. The Quattro Pro
marketing team had chosen to bundle both Quattro Pro for DOS and
Quattro Pro for Windows in the same box labeled "WIN-DOS" at a
price of $495. Customers and reviewers expecting a pure Windows
application responded with confusion and outrage, believing the
product was merely a DOS application with windowing capabilities.
Shortly thereafter QPW was re-packaged by itself and priced $129,
receiving accolades for Borland's long-delayed pure Windows
spreadsheet and its popular price.
</p>
<p>Eventually it sold well (after the price was slashed to just $49
a copy). Work was started immediately on a new version with a
brand new team of engineers led by <a href="https://en.wikipedia.org/w/index.php?title=Joe_Ammirato&action=edit&redlink=1" class="new" title="Joe Ammirato (page does not exist)">Joe
Ammirato</a>; including <a href="https://en.wikipedia.org/w/index.php?title=Bret_Gillis&action=edit&redlink=1" class="new" title="Bret Gillis (page does not exist)">Bret
Gillis</a> and <a href="https://en.wikipedia.org/w/index.php?title=Peter_Weyzen&action=edit&redlink=1" class="new" title="Peter Weyzen (page does not exist)">Peter
Weyzen</a>. Borland purchased <a href="https://en.wikipedia.org/w/index.php?title=DataPivot&action=edit&redlink=1" class="new" title="DataPivot (page does not exist)">DataPivot</a>
from <a href="https://en.wikipedia.org/wiki/Brio_Technology" title="Brio Technology">Brio Technology</a> to add a new feature
to the program. Colin Glassey came from Brio to help with the
integration of that technology.
</p>
<p>After a year and the merging of the old team and the new team,
QPW 5 was released (the reason for the jump in version number had
to do with keeping up with the DOS version as well as it looked
good). QPW 5 sold well also, though the <a href="https://en.wikipedia.org/wiki/Microsoft_Excel" title="Microsoft Excel">Microsoft Excel</a> + Word combination
was gaining steam.
</p>
<p>Work then started on version 6 (now with <a href="https://en.wikipedia.org/w/index.php?title=Steven_Boye&action=edit&redlink=1" class="new" title="Steven Boye (page does not exist)">Steven
Boye</a> as project lead). Midway through the development of
version 6 a strategic decision to work closely with the <a href="https://en.wikipedia.org/wiki/WordPerfect" title="WordPerfect">WordPerfect</a> word processor was made. It
was a direct attempt to push back at the Microsoft Office one-two
punch of <a href="https://en.wikipedia.org/wiki/Microsoft_Office_Word" class="mw-redirect" title="Microsoft Office Word">Microsoft Word</a>
and Microsoft Excel. The other big issue with Version 6 was the
advent of <a href="https://en.wikipedia.org/wiki/Windows_95" title="Windows 95">Windows 95</a>. This was a significant
modification to the Windows operating system with a major change
to user interface guidelines.
</p>
<p>In an odd set of events, <a href="https://en.wikipedia.org/wiki/Novell" title="Novell">Novell</a>
purchased both WordPerfect Corporation and the Quattro Pro code
base and team of engineers from Borland. Novell was going to try
to be a real competitor to Microsoft. Although Version 6 was
released and some effort was made to unify the user interface
between WordPerfect and QPW, the effort was far from complete.
</p>
<p>In another lawsuit, Novell claims that Microsoft had
"deliberately targeted and destroyed" its WordPerfect and
QuattroPro programs to protect its Windows operating system
monopoly. The US Supreme Court refused to halt the antitrust
lawsuit in March 2008.<sup id="cite_ref-4" class="reference"><a href="https://en.wikipedia.org/wiki/Quattro_Pro#cite_note-4">[4]</a></sup>
</p>
<h2><span id="Novell.27s_exit"></span><span class="mw-headline" id="Novell's_exit">Novell's exit</span></h2>
The release of Windows 95 in August 1995 was the beginning of the
end for Novell and its plans to compete with Microsoft. Not only did
Microsoft release a new operating system, but Microsoft also
released new versions of Word and Excel to accompany it. Sales of
Novell PerfectOffice (and Lotus applications as well) sank to almost
nothing while sales of the Microsoft products were huge.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i><a href="https://en.wikipedia.org/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim
needs references to reliable sources. (September 2008)">citation
needed</span></a></i>]</sup> Within three months, Novell
announced they were going to sell their applications to someone
(eventually that proved to be <a href="https://en.wikipedia.org/wiki/Corel" title="Corel">Corel</a>).
By mid-1996, Microsoft had 95% of the market for business
applications. As of 2005, Microsoft still dominates the market for
Windows business application software,<sup class="noprint
Inline-Template Template-Fact" style="white-space:nowrap;">[<i><a href="https://en.wikipedia.org/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim
needs references to reliable sources. (September 2008)">citation
needed</span></a></i>]</sup> although Quattro Pro and
WordPerfect, which pre-dated the MS Office 4.2 suite, are still both
updated and s
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
------------------------------------------------------------------------------------------------------------</div>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 8/22/2019 4:31 PM, 'Clyde
Christofferson' <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> [eccopro] wrote:</div>
<br>
<blockquote type="cite" cite="mid:[email protected]">
<span> </span>
<div id="ygrp-text">
<div class="WordSection1">
<p class="MsoNormal">My first copy of ECCO came with the
Arabesque name on the manual. That was decades ago.<o></o></p>
<p class="MsoNormal"><o> </o></p>
<p class="MsoNormal">I came across an old email (from
2008) suggesting there had been some concern that
Netmanage might revoke the license (under which all of
us are able to use ECCO for free). I have the vaguest
recollection from those days and earlier. Something
fishy was going on in the board rooms of big players in
the PIM industry, at least thats what many of us
thought. <o></o></p>
<p class="MsoNormal"><o> </o></p>
<p class="MsoNormal">ECCO is still as far as I am
concerned the best and most versatile outliner out
there. For years I have used it to build and maintain a
docketing system tailored to my own needs. Im going to
be in great distress and a state of mourning if and when
it no longer runs on available operating systems.<o></o></p>
<p class="MsoNormal"><o> </o></p>
<div>
<div style="border-top:solid #E1E1E1 1.0pt;padding:3.0pt
0in 0in 0in;">
<p class="MsoNormal"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> <br>
<b>Sent:</b> Thursday, August 22, 2019 3:30 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a><br>
<b>Subject:</b> [eccopro] Re: Ecco Happy Place /
Arabesque<o></o></p>
</div>
</div>
<p class="MsoNormal"><o> </o></p>
<p class="MsoNormal"> <o></o></p>
<div id="ygrp-mlmsg">
<div id="ygrp-msg">
<div id="ygrp-text">
<p><br>
Arabesque was the name of the software company
that developed and marketed Ecco Pro. <o></o></p>
</div>
<div>
<p class="MsoNormal"><span style="color:white;"><o></o></span></p>
</div>
</div>
</div>
</div>
</div>
<!-- end group email -->
</blockquote>
</p>
</div>
<!--~-|**|PrettyHtmlStart|**|-~-->
<div style="color: #fff; height: 0;">__._,_.___</div>
<div style="clear:both"> </div>
<div id="fromDMARC" style="margin-top: 10px;">
<hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
Posted by: Raymond Yerkes <[email protected]> <hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
</div>
<div style="clear:both"> </div>
<table cellspacing=4px style="margin-top: 10px; margin-bottom: 10px; color: #2D50FD;">
<tbody>
<tr>
<td style="font-size: 12px; font-family: arial; font-weight: bold; padding: 7px 5px 5px;" >
<a style="text-decoration: none; color: #2D50FD" href="https://groups.yahoo.com/neo/groups/eccopro/conversations/messages/25470;_ylc=X3oDMTJxbWFtc3IzBF9TAzk3MzU5NzE0BGdycElkAzE0Njc1MjAEZ3Jwc3BJZAMxNzA5MzM0OTk3BG1zZ0lkAzI1NDcwBHNlYwNmdHIEc2xrA3JwbHkEc3RpbWUDMTU2NjUwNzg5MA--?act=reply&messageNum=25470">Reply via web post</a>
</td>
<td>•</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;" >
<a href="mailto:[email protected]?subject=Re%3A%20%5Beccopro%5D%20Re%3A%20Ecco%20Happy%20Place%20%2F%20Arabesque" style="text-decoration: none; color: #2D50FD;">
Reply to sender </a>
</td>
<td>•</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;">
<a href="mailto:[email protected]?subject=Re%3A%20%5Beccopro%5D%20Re%3A%20Ecco%20Happy%20Place%20%2F%20Arabesque" style="text-decoration: none; color: #2D50FD">
Reply to group </a>
</td>
<td>•</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;" >
<a href="https://groups.yahoo.com/neo/groups/eccopro/conversations/newtopic;_ylc=X3oDMTJlZGZlNG9yBF9TAzk3MzU5NzE0BGdycElkAzE0Njc1MjAEZ3Jwc3BJZAMxNzA5MzM0OTk3BHNlYwNmdHIEc2xrA250cGMEc3RpbWUDMTU2NjUwNzg5MA--" style="text-decoration: none; color: #2D50FD">Start a New Topic</a>
</td>
<td>•</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;color: #2D50FD;" >
<a href="https://groups.yahoo.com/neo/groups/eccopro/conversations/topics/25467;_ylc=X3oDMTM2YjJvbXJmBF9TAzk3MzU5NzE0BGdycElkAzE0Njc1MjAEZ3Jwc3BJZAMxNzA5MzM0OTk3BG1zZ0lkAzI1NDcwBHNlYwNmdHIEc2xrA3Z0cGMEc3RpbWUDMTU2NjUwNzg5MAR0cGNJZAMyNTQ2Nw--" style="text-decoration: none; color: #2D50FD;">Messages in this topic</a>
(4)
</td>
</tr>
</tbody>
</table>
<!------- Start Nav Bar ------>
<div id="ygrp-grfd" style="font-family: Verdana; font-size: 12px; padding: 15px 0;">
<!-- |**|begin egp html banner|**| -->
To Post a message, send it to: [email protected]<BR>
To Unsubscribe, send a blank message to: [email protected]<BR>
<BR>
Group web-site: <a href="http://groups.yahoo.com/group/eccopro/">http://groups.yahoo.com/group/eccopro/</a><BR>
Files: <a href="http://groups.yahoo.com/group/eccopro/files/">http://groups.yahoo.com/group/eccopro/files/</a>
<!-- |**|end egp html banner|**| -->
</div>
<!-- |**|begin egp html banner|**| -->
<div id="ygrp-vital" style="background-color: #f2f2f2; font-family: Verdana; font-size: 10px; margin-bottom: 10px; padding: 10px;">
<span id="vithd" style="font-weight: bold; color: #333; text-transform: uppercase; "><a href="https://groups.yahoo.com/neo/groups/eccopro/info;_ylc=X3oDMTJlcWtldjlzBF9TAzk3MzU5NzE0BGdycElkAzE0Njc1MjAEZ3Jwc3BJZAMxNzA5MzM0OTk3BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTU2NjUwNzg5MA--" style="text-decoration: none;">Visit Your Group</a></span>
<ul style="list-style-type: none; margin: 0; padding: 0; display: inline;">
</ul>
</div>
<div id="ft" style="font-family: Arial; font-size: 11px; margin-top: 5px; padding: 0 2px 0 0; clear: both;">
<a href="https://groups.yahoo.com/neo;_ylc=X3oDMTJkM3M4b2ttBF9TAzk3NDc2NTkwBGdycElkAzE0Njc1MjAEZ3Jwc3BJZAMxNzA5MzM0OTk3BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNTY2NTA3ODkw" style="float: left;"><img src="http://l.yimg.com/ru/static/images/yg/img/email/new_logo/logo-groups-137x15.png" height="15" width="137" alt="Yahoo! Groups" style="border: 0;"/></a>
<div style="color: #747575; float: right;"> • <a href="https://info.yahoo.com/privacy/us/yahoo/groups/details.html" style="text-decoration: none;">Privacy</a> • <a href="mailto:[email protected]?subject=Unsubscribe" style="text-decoration: none;">Unsubscribe</a> • <a href="https://info.yahoo.com/legal/us/yahoo/utos/terms/" style="text-decoration: none;">Terms of Use</a> </div>
</div>
<br>
<!-- |**|end egp html banner|**| -->
</div> <!-- ygrp-msg -->
<!-- Sponsor -->
<!-- |**|begin egp html banner|**| -->
<div id="ygrp-sponsor" style="width:160px; float:right; clear:none; margin:0 0 25px 0; background: #fff;">
<!-- Start Recommendations -->
<div id="ygrp-reco">
</div>
<!-- End Recommendations -->
</div> <!-- |**|end egp html banner|**| -->
<div style="clear:both; color: #FFF; font-size:1px;">.</div>
</div>
<img src="http://geo.yahoo.com/serv?s=97359714/grpId=1467520/grpspId=1709334997/msgId=25470/stime=1566507890" width="1" height="1"> <br>
<img src="http://y.analytics.yahoo.com/fpc.pl?ywarid=515FB27823A7407E&a=10001310322279&js=no&resp=img" width="1" height="1">
<div style="color: #fff; height: 0;">__,_._,___</div>
<!--~-|**|PrettyHtmlEnd|**|-~-->
</body>
<!--~-|**|PrettyHtmlStart|**|-~-->
<head>
<style type="text/css">
<!--
#ygrp-mkp {
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 10px 0;
padding: 0 10px;
}
#ygrp-mkp hr {
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd {
color: #628c2a;
font-size: 85%;
font-weight: 700;
line-height: 122%;
margin: 10px 0;
}
#ygrp-mkp #ads {
margin-bottom: 10px;
}
#ygrp-mkp .ad {
padding: 0 0;
}
#ygrp-mkp .ad p {
margin: 0;
}
#ygrp-mkp .ad a {
color: #0000ff;
text-decoration: none;
}
#ygrp-sponsor #ygrp-lc {
font-family: Arial;
}
#ygrp-sponsor #ygrp-lc #hd {
margin: 10px 0px;
font-weight: 700;
font-size: 78%;
line-height: 122%;
}
#ygrp-sponsor #ygrp-lc .ad {
margin-bottom: 10px;
padding: 0 0;
}
#actions {
font-family: Verdana;
font-size: 11px;
padding: 10px 0;
}
#activity {
background-color: #e0ecee;
float: left;
font-family: Verdana;
font-size: 10px;
padding: 10px;
}
#activity span {
font-weight: 700;
}
#activity span:first-child {
text-transform: uppercase;
}
#activity span a {
color: #5085b6;
text-decoration: none;
}
#activity span span {
color: #ff7900;
}
#activity span .underline {
text-decoration: underline;
}
.attach {
clear: both;
display: table;
font-family: Arial;
font-size: 12px;
padding: 10px 0;
width: 400px;
}
.attach div a {
text-decoration: none;
}
.attach img {
border: none;
padding-right: 5px;
}
.attach label {
display: block;
margin-bottom: 5px;
}
.attach label a {
text-decoration: none;
}
blockquote {
margin: 0 0 0 4px;
}
.bold {
font-family: Arial;
font-size: 13px;
font-weight: 700;
}
.bold a {
text-decoration: none;
}
dd.last p a {
font-family: Verdana;
font-weight: 700;
}
dd.last p span {
margin-right: 10px;
font-family: Verdana;
font-weight: 700;
}
dd.last p span.yshortcuts {
margin-right: 0;
}
div.attach-table div div a {
text-decoration: none;
}
div.attach-table {
width: 400px;
}
div.file-title a, div.file-title a:active, div.file-title a:hover, div.file-title a:visited {
text-decoration: none;
}
div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited {
text-decoration: none;
}
div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts {
font-family: Verdana;
font-size: 10px;
font-weight: normal;
}
.green {
color: #628c2a;
}
.MsoNormal {
margin: 0 0 0 0;
}
o {
font-size: 0;
}
#photos div {
float: left;
width: 72px;
}
#photos div div {
border: 1px solid #666666;
height: 62px;
overflow: hidden;
width: 62px;
}
#photos div label {
color: #666666;
font-size: 10px;
overflow: hidden;
text-align: center;
white-space: nowrap;
width: 64px;
}
#reco-category {
font-size: 77%;
}
#reco-desc {
font-size: 77%;
}
.replbq {
margin: 4px;
}
#ygrp-actbar div a:first-child {
/* border-right: 0px solid #000;*/
margin-right: 2px;
padding-right: 5px;
}
#ygrp-mlmsg {
font-size: 13px;
font-family: Arial, helvetica,clean, sans-serif;
*font-size: small;
*font: x-small;
}
#ygrp-mlmsg table {
font-size: inherit;
font: 100%;
}
#ygrp-mlmsg select, input, textarea {
font: 99% Arial, Helvetica, clean, sans-serif;
}
#ygrp-mlmsg pre, code {
font:115% monospace;
*font-size:100%;
}
#ygrp-mlmsg * {
line-height: 1.22em;
}
#ygrp-mlmsg #logo {
padding-bottom: 10px;
}
#ygrp-msg p a {
font-family: Verdana;
}
#ygrp-msg p#attach-count span {
color: #1E66AE;
font-weight: 700;
}
#ygrp-reco #reco-head {
color: #ff7900;
font-weight: 700;
}
#ygrp-reco {
margin-bottom: 20px;
padding: 0px;
}
#ygrp-sponsor #ov li a {
font-size: 130%;
text-decoration: none;
}
#ygrp-sponsor #ov li {
font-size: 77%;
list-style-type: square;
padding: 6px 0;
}
#ygrp-sponsor #ov ul {
margin: 0;
padding: 0 0 0 8px;
}
#ygrp-text {
font-family: Georgia;
}
#ygrp-text p {
margin: 0 0 1em 0;
}
#ygrp-text tt {
font-size: 120%;
}
#ygrp-vital ul li:last-child {
border-right: none !important;
}
-->
</style>
</head>
<!--~-|**|PrettyHtmlEnd|**|-~-->
</html>
<!-- end group email -->
--------------6BED06E11753C3F8FD6AE33A--