Re: EverEcco template updater

Ecco-ites ...

EE's feature set is richer than we know.  Discovery is on-going.  Tests are confirming EE has made Ecco more or less bullet proof when you stay on a prescribed path of 'operational behavior'.  I am building this behavior pattern' into the EverEcco template as best I can.  The template is designed to guide the user sufficiently so that if he/she makes 10 entries per day,  a single Ecco file will last 20 years before  becoming truly full.  

Simply put: Ecco has internal "old school' 16 bit memory registers that create bottlenecks and will never go away.  Heck, the graphics engine in Ecco is only 8 bit.  I learned this the hard way making new icons. The fact you can make icons but have to work in an Indexed 256 or less color scheme is another "non-detailed EE feature".   

So there is some ancient code inside Ecco.   But MyPhoneExplorer and Multi-View extend Ecco to the Internet, and EE gives us memory work-arounds, programability, and database and spreadsheet features.   EverEcco's goal - both as a template and as a documentation project - is to tie-together and exploit the sum-total of 25 years of individual and group effort. 

But even Slang didn't work in a vacuum.  He'd make changes to EE, post them and get feedback.  And that was when the Yahoo forums were barely good enough to allow that sort of 2-way interaction.  Now with "Yahoo Neo", hitting 'send' is like casting-off a message in a bottle.  I am not supposed to be stranded on an island.  Because of the 'everflow' structure, if a post is not answered within a day or two continuity is lost.  Because of the abismal Search tools and no way to do Headlines or Sticky Notes, there's no good way to build topics for group discourse.

Just how bad is this for a group of people that at-heart are coders, developers and creative types?
Would you give Yahoo Neo a D+ as development tool?


Meisters, Ecco-ites, eta all ...

At this point and moving forward I really need your help.  Please consider this a plea for input on how to continue. 

I want to publish the "Ecco Memory Manifesto" but it makes no sense to do a big write up - tease it here on the 'everflow', post it in the Files section, and get parts of it wrong.  How confusing would that be?    What is needed is a place to post a "beta" of the Manifesto (what I think I know) and have you guys who've actually been under the hood "have at it'.  I can say with confidence that portions are correct but it is not  100%.  The goal is the create "definitive documentation" .

Friedhelm, you've gotten data in and out of Ecco in ways formerly thought impossible and your installer and ticket system keep a portion of the Ecco community up and running smoothly.  YSWT,  I cannot think of my tests and conclusions as publishable until they get your attention and some red lines or a Gold star.  And if Slang were around enough to proof read and explain a couple details before publishing, that would be perfect.  Naming names is always dangerous, but it seems r634718 - you are doing GTD in a way that would make David Allen envious.  JS, you seem to speak LUA more fluently than I speak English.    Alien Films - you are a professional at keeping track of bits and pieces.  In the recent past,  A. Schepers, R Brandes, Pastor Don and a host of others have added to the knowledge base.  Going back further many more names come up.  

To wrap - I sure as heck would like to acknowledge and have the blessings from everyone who's had input on making Ecco such a cool tool.   I am utilizing your output and knowledge to create the EverEcco template.  If I could throw this thing back into the proverbial ring and let "all who have come before" tweak this thing up, the Ecco community would have a "software tool offering" - thanks to virtual computing  technology - that would serve the  Polymath People of the Planet well until 2067 (the date when Ecco apparently implodes?).

I'll keep typing as I learn more.  And hoping for feedback on the "community build" aspect of this project. 

If you want to go off-line or email to yak it up, that works.
four one four  seven seven one seven eight nine eight.
You will hear a pre-tongue cancer me saying something like "EarMark Productions phone answering machine..."   (my wife tells me I don't sound that much different now)  
Or you can email at M as in Mad, D as in Dog, H as in Helen at EarMark dot net. 
(three initials before the @)

-Mark