From: H- 16 <s1ay3r44@...>
Date: 2010-04-11T10:00:39+09:00
Subject: Re: The Ruid Concept, with question

thunk wrote:
> http://trevoke.net/ruids/index.php?topic=5.0
> 
> Pretty much says it.   It takes a part in a set of like classes
> (therefore the swarm).  There are multiple Types but the "standard"
> type makes a few assertions, messages get attached (by the expert) and
> a conclusion gets reached (5 sections / 5 DSLs)
> 
> The "big secret" to making some basic sense of the conclusions is that
> each Ruid has basic "categorization" - done into the Header section of
> the Ruid.
> 
> THEY are simple - so they can be authored using nothing more than a
> "picklist" driven "expert session" which would be key part of a DEMO
> system (and must be Web based).   And was done in WEE and tested and
> so on.
> 
> The SWARM_READER is in charge of making sense of the "Image" made
> after the Ruids contact "Screens".   Screens are about presenting
> information (like a patient record) to the Ruid.   The Ru'id "docks"
> with a "HelperClass" - the HelperClass is something also used by
> Ruleby (the author is happy to report).
> 
> The "HelperClasses" is where a "Ru'id Programmer must spend his/her
> effort.
> 
> =================================
> 

Ok, so what's the entire point of the program? What EXACTLY does it do? 
And can you give us even a LITTLE code. If you can't you can't be 
helped.

P.S. If you haven't noticed I'm just about the only one giving you a 
chance right about now. I wouldn't take that kindness for granted. Nuff 
said...
-- 
Posted via http://www.ruby-forum.com/.