🚀 go-pugleaf

Philosophically, I agree with you, Ole, but one can get a long way by just letting RB serve as an interface front end to scripts. 

So far, my project has five buttons (each 18 tall by 28 wide), a timer and a static text field. Four of the buttons just call existing scripts (although I had to add the on run construct to all of them), including two large-scale scripts that Shane wrote (Save with Versions and Build Booklet). 

The fifth script I wrote today to toggle the two characters on either side of the insertion point. 

The timer triggers every 1.25 seconds and it reports in the static text field the class of the current selection. This is the only place so far where I've had to write anything in RB: the script is the only one that returns a value; I check the value to see if it's different from what's displayed in the field and if so, write it in -- if you don't do the check the field flashes. 

I'm sure that in some of these cases the workload could be shared more evenly for perhaps a more efficient result, but with my current understanding of scripting versus Basic, I'm happy enough with the results to date. 

Dave