My 2 cents... I have personally been a little disappointed that /view is getting all the RT attention. This is simply because my problems are better solved with /command and who knows when that will be ready. I also wish that /core was updated as quickly as /view with new features and bug fixes. I am actively working on my own /command extensions for Win32 by using a tcp port for communication between Rebol and an EXE that will carry out commands for Rebol. I will likely make this extension public once I'm comfortable with it. I didn't want to do this but since RT is not forthcoming with a /command deadline (and additionally my request for getting a copy of /command has been ignored), I can't wait for something indeterminate. I am also working on using Rebol in web server mode so I can use a browser for UI, even though my app is running locally. I am only using the web server to get the browser interface (so that I can use form input - otherwise file display would be enough). My hope is that under Win32 you can double-click my app icon and it will load Rebol and my special EXE, pop open the default browser to the application's home page, and away you go, with most pages being rebol scripts. I have been very tempted to really rely on /view but haven't for these main reasons: 1) My company has a dictum that all new UI work be browser-based 2) I have found View to be quirky in that certain Win32 niceties aren't available (like cursor blinking, ctrl-shift selecting...) 3) Browsers currently have a richer set of possibilities including video, audio, etc. But I may be a /view convert at some point. Rodney Snell -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 13, 2000 3:55 PM To: [EMAIL PROTECTED] Subject: [REBOL] /view and the Web Re:(6) ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 14, 2000 8:20 AM Subject: [REBOL] /view and the Web Re:(5) > No. I am thinking of the possibility of creating interactive Web pages using > /view . view contains core so it works in cgi so you can do the usual server side stuff. But another method to explore if you don't want to do cgi, using browse/only function with local files dynamically created in view, but I think this is fairly limited in the interative stakes. You can set up a kiosk mode browser, add a refresh tag, and have /view doing things in the backgound. (works for IE other browsers may or may not still support it) browse/only "-k pathtofile.html" Like I said, this is limited, but I don't think anyone has fully explored the possibilities. Cheers, Allen K PS. I have been using /view long enough for a paradigm shift. I don't try and fit /view into the web, I now see the web as a live content plugin for my view pages..
