Joe made a point in some other mail that REAL might support RBScript
better if it had more users, and that some RBScript evangelism with
examples of use might promote it more. Certainly anyone who reads the
REAL email lists and the frequent complaints about the state of
RBScript would be more likely to avoid it than to embrace it!
RBScript is an incredibly powerful feature of REALbasic. One can make
one's applications as open-architecture as one wishes and allow one's
users to extend applications to address their needs.
Back in 1994, in the early days of web form support, we ported a
highly interactive graphic application to the web and gave a tutorial
on this at WWW4
(http://www.cpsc.ucalgary.ca/~gaines/reports/HM/PortWeb/).
The first port was written as a cgi in an early C++ compiler. A few
years ago we re-wrote it in REALbasic as a web portal to the
interactive app itself, i.e. making the same app available as a local
program with its own interactive interface and as remote server to
web clients. The interaction in both cases is programmed in RBScript.
This has the advantage that end-users can rewrite as much of the
dialog as they like in their native languages.
We had no problems with RBScript until the 2005 release with its
array append crash. We recently moved to 2006 using a workaround to
the crashes causes by REAL's introduction of bugs in the Min and Max
functions in 2006R1, and failure to fix them in that release or the
two subsequent ones. That is very frustrating as we don't want to
have to ask our end users to put workarounds in their amended scripts.
However, RBScript is otherwise still working robustly, and is a very
important feature of REALbasic, well worth using if one wants open
architecture or easily customizable apps.
It would be nice to get other reports of effective use of RBScript on
this list to encourage its use, and to encourage it REAL to give it
the support it merits and to use it as an important marketing feature
of REALbasic.
b.
ps the 2006 version of the app mentioned above is accessible at
http://gigi.cpsc.ucalgary.ca:1500/WGIV.html
I agree with Joe. Developing a community RBScript editor wouldn't be
that difficult (some person/company already has one out there
somewhere), ditto for documentation, but everytime I personally
consider starting such a project, I am discouraged by the likely
futility of it all, given the crashing bugs, the general and
completely baffling neglect on the part of REAL, and (which follows)
the absence of things like PartialRun and decent threading/yielding
behavior that would be needed in most (albeit not all) applications of
RBScript that I've ever had in mind.
My understanding was that Swordfish (I just woke up, so it's possible
that this whole "Swordfish" thing is just a remnant of something I was
dreaming about -- if so, if "Swordfish" is just a figment of my
imagination, then disregard the following) was going to use RBScript.
I don't see how REAL could ever have a web server framework based on
RBScript with crashing bugs, poor threading/yielding, etc., so I had
hoped we would be seeing major progress (or at least *some* progress)
on the RBScript front, but that hasn't happened. As I said, it's
baffling...
-Walter
On 7/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
To me, these bugs are far more important than feature requests such
as separate RBScript documentation and a custom editor, which we
could provide ourselves with a bit of effort. But the
crashing/freezing bugs in RBScript, we can't do anything about. I
would be quite happy if just those were fixed -- and from what I've
heard on this list, so would many others.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
