Hi folks, As a budding user of RBScript I would love to see these implemented, particularly the documentation. Having this info buried in the Language Reference on page 527 (actually this is info on the RBScript Control) is not the easiest place to find. Even then the information that an end-user would be after seems to start on page 532 or thereabouts.
I cannot comment on the broken exception handling as I have not played with this yet. If I might ask, how is it broken and are there workarounds? Regards Robin > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:realbasic-nug- > [EMAIL PROTECTED] On Behalf Of Brendan Murphy > Sent: 15 July 2006 09:17 > To: RB NUG Group > Cc: Geoff Perlman > Subject: RBScript > > Here is an open letter to RS. > > I would like some serious attention paid to RBScript in the next > release. There are certain bugs that need to be fixed ASAP and > there are certain enhancements that you should consider. > > First, exception handling is broken and must be fixed ASAP. > Example feedback report "sbuwicsb". > > RBScript is a very important feature for us and I would like to > see it be made a first class citizen in the RB universe. Here are > a few suggestions to make is a first rate feature. > > - Create a separate PDF that describes RBScript in all its gory > details that we can distribute with our programs so that our > customers can have a base reference to read. This should be > written with our end customer in mind and not the primary > developer of the program. So it should do a lot of hand holding so > to speak (i.e., be a mini-user guide for RB in some respects). If > you don't have the personnel bandwidth, then you should contract > this work out to one of the old timers on the NUG to write the > bulk of such a document for a fee. This document would be a > significant addition to the RB documentation set. > > The PDF can be release independent of the next release, so I would > like this item done ASAP. > > - I would like to see an RBScript editor control implemented. That > way we the developer can implement an editor for our end users as > appropriate. This would be like the EditField in that it would be > based on your own internal editor. Here are the some basic > requirements for creating such a control. > > - color code the syntax like the RB IDE > - automatic indentation of the code like the RB IDE > - code completion based on the context object methods like the RB IDE > > We obviously don't need break point support or anything like that, > just basic editing for our end customers so the end customer can > have the same experience we do with the IDE every day. > > - Implement multiple context object. See Feedback report > "rmfdkyqu". With the ability to assign multiple context objects, > we can manage our software support for RBScript in ways that will > make RBScript a joy to implement. > > With these changes I am suggesting we will have a superior > experience with RBScript and so will our end customers. > > RBscript is a really significant feature and has a potential for > great innovations. > > _______________________________________________ > 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>
