[Eric] outdated “Technical Reports”

Studio - PM studio-pm at hotmail.com
Thu Nov 1 16:17:33 GMT 2018


>  they are very helpful.
   Glad to know it has been of help for you, but here “simple” and specific usefulness was not my only purpose. About this “Tech.Report” works I was much more ambitious and, in this regard, I failed.


My goal was that of proposing and proving a “revolutionary” way of documenting high tech. Tools (as certainly Eric is), based on the principle hereafter exposed, so to hopefully collect a consent and gather a bunch of qualified and aware users now on asking for nothing less that that.


Just for instance now there is another high tech. s/w tool I'd like to process this same way, it's the “MediathekView” [to give it a look you'd need knowing a little German]. Enterprise that revealed simply impossible, as the community there, both designers and users, not only refused to collaborate (just the opposite of Eric's case), but ware scornful, arrogant and offensive: "We are already perfect as we are, no need for any English Tech.Ref.Doc, and if you encounter any difficulty using our product it is simply because you are an idiot, not worth minding".


Anyhow, this the revolutionary principle I had tried to advocate, propose and prove with an actual and massive doc-example:

→ The primary reference for the Tech.Doc is the User, NOT the producer, nor the product in itself.


As a consequence of this fundamental, primary principle there is a whole set of consequent consequences, which would well be matter for a congress producing a final chart, a final Declaration of the Right of Users.

   Not having been capable of convincing any other fellow users of the value of such a cause now, old and tired [sob], I gave up my solitary and vain struggle.

So long.

- P.M.


________________________________
From: Christos Sevastiadis <csevast at auth.gr>
Sent: Thursday, November 1, 2018 7:34 AM
To: Studio-PM at hotmail.com
Cc: Eric at riverbankcomputing.com
Subject: Re: [Eric] outdated “Technical Reports”

Hi,

They are the only reference and help manuals for Eric. They helped me to understand a lot of the Eric's behavior. For sure they need updating, but even like this they are very helpful.

Christos Sevastiadis

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/eric/attachments/20181101/6152faa8/attachment.html>


More information about the Eric mailing list