Hi Jason, Perhaps the best approach to answer your queries with regards to REBOL IOS is to actually request an evaluation copy.
http://rebol.com/express-form.html One of the things I like about IOS is how "light" it is compare to competitors products. Light in size and memory demands but not in extensibility. YekSoon At 10:53 PM 3/17/2002 -0500, you wrote: >Hi Gregg > >Thanks. Yes your description helps. > >I just went to check on rebol.com and delighted to discover they have a new >links to IOS articles >http://www.linuxfocus.org/English/March2002/article230.shtml > >and > >http://www.newarchitectmag.com/documents/s=2457/new1015630100801/index.html > >..at last some new press coverage. Spring must be here :-) > >Funny RT didn't post an announce to the list, or did I miss something? > > > I can publish things via IOS to a server. I can then go anywhere in the > > world and fire up the IOS/Link client on a clean machine, and everything > > I've published (or that anyone else has published on the server) is > > automatically sync'd. Now, lots of people on this list will undoubtedly > > think "Yeah, so what. I know of n other systems that do that too." The >thing > > that makes IOS great, to me, is how simply, easily, and reliably it all > > works. > >ok: A. synchronize distributed data easily > >That something we all want the smallest possible headache to do? > >Please can you clarify what "firing up" IOS/Link client on a clean machine >involves. >What is the cost per link client? >How easy to customize the look of the client? > > > IOS doesn't provide everything you might ever want, but it's easy to >extend. > > For one project I'm working on, we're using a remote Rugby server along >with > > IOS to provide facilities that I don't yet know how to provide via IOS. > >aha.. > > > I built the original app under /View, we installed IOS, published the > > scripts, and it ran under IOS without any changes. IOS becomes a simple > > deployment mechanism. I can have the Conference reblet fired up, and have > > people looking at the app. As they make suggestions, I can tweak it on the > > fly, re-publish it, and they can run it again to see the changes. If I >need > > to roll back to a previous version, IOS maintains a history of published > > versions for me automatically. > >You mean you are tweaking your own /View scripts which are now distributed >and synchonrized [published] via IOS ? >The history function sounds nice, like the cool 'versions' thing in Zope. > >Is 'publish' on a demand-basis? >If clients are on-line 24/7 like DSL how quickly are updates propagated? >Is this architecture like DNS? > >Does IOS care what your Viewlets are? >Can non-Rebol/Link clients also access them [in non published mode] ? > >Where is this stuff explained? >Are there docs? > >cheers >./Jason -- Attached file included as plaintext by Listar -- --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.336 / Virus Database: 188 - Release Date: 3/11/2002 -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
