Post Reply 
newRPL: [UPDATED April 27-2017] Firmware for testing available for download
02-27-2017, 04:17 PM
Post: #571
RE: newRPL: [UPDATED February 21-2017] Firmware for testing available for download
(02-27-2017 03:56 AM)Francois Lanciault Wrote:  It's ok for flag indicators. But will it be the same for graphics ? In standard RPL you can see your graphics primitive (lines, circles, etc) appear on screen as the program runs.

I'm still working out the details of how a newRPL program will interface with humans. You won't be able to draw to screen just like that. You'll draw to a PLOT object, which then you can render to various targets: PICT, a GROB, SVG file on SD card, etc.
In order to interact, there will be some sort of forms, probably defined by a main text file with tags that include objects in variables (we discussed this in another thread). For example, you could have the main text being just the tag of a variable containing a PLOT object. When the user activates the form, the PLOT will be displayed (with all bells and whistles, scroll, zoom, etc). A program can dynamically update that PLOT, when the program ends the form will update the display.
Instead of a program drawings to the screen and using FREEZE or similar commands, you'll create an application that creates graphics to be displayed in a form with which the user will interact. Since it will be event-driven, you'll have separate routines to react to the user input, updating graphics, etc.
I'm still putting together the concepts, as soon as it's implemented you'll see. I'm not planning to create anything complex, the idea is that it should be very simple for an application to to get input from the user, do calculations and issue a report containing text mixed with graphics.
The report will ideally be able to be exported in HTML format with all the graphics, so you can put it on an SD card and open it in a browser, or copy/paste into your favorite rich document editor.
And if you still decide to go the traditional way of just drawing, you'll draw to a PLOT file, and call a PLOT viewer at the end of your program.

(02-27-2017 03:56 AM)Francois Lanciault Wrote:  Also, speaking of "WAIT" can you explain the behaviour under newRPL (or point me to some documentation) . It seems to return a string containing the last key pressed. I don't recall it did that in standard RPL.
François

It used to return a key code, very hard to remember. Now the key code is a string, which is much easier to visualize.
The string is identical in format as the ASNKEY command (discussed not long ago in this thread):
Format:
"KEY.SHIFT.MODIFIER"
KEY = "A thru Z, 0 thru 9, * - + . or UP/DN/LF/RT, BK for backspace, EN for enter
SHIFT = L, LH,R, RH,A, AH,OH,ALH,ARH (L=left shift, LH=left shift hold, A=Alpha, OH=On-hold). Notice that On can only be defined with a hold plane.
MODIFIER = D,U,P,R,L,T (D=key down, U=key released, P=pressed, R=repeat, L=long press, T=long repeat, no modifier means the standard P (pressed) event)

Examples:
"7.L" = Left-shift 7
"7.LH" = Left-shift-hold 7
"7..D" = Action executed on key-down event for unshifted key number 7
"7..U" = Action executed on key-up event
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: newRPL: [UPDATED February 21-2017] Firmware for testing available for download - Claudio L. - 02-27-2017 04:17 PM



User(s) browsing this thread: 4 Guest(s)