r3gui docs
Started by Richard on 1-Mar-2014/11:39:52-8:00
Richard — 1-Mar-2014/11:39:52-8:00
http://re-bol.com/saphirion-r3guidocs.zip
-------------------------------------------
In this link the documents contain black squares where the doc info shoud be?
regards
Richard
Nick — 1-Mar-2014/13:42:16-8:00
Everything is in those HTML docs, but it looks like it would've been nice to download their CSS files along with the HTML files.
To read the HTML temporarily, you can highlight the blackened code with your mouse to see it, or permanently edit a copy of the files to remove all the class="<..>" identifiers in the HTML (best yet, when their site comes back online, backup their docs with the CSS and all :)
Nick — 2-Mar-2014/6:14-8:00
R E B O L []
x: read %./
foreach file x [
if %.htm = suffix? file [
content: read file
parse/all content [any [
to { class="} begin: thru {"} ending: (
remove/part begin ((index? ending) - (index? begin))) :begin
]]
write to-file join first parse file "." "-cleaned.html" content
]
]
print "done" halt
Richard — 3-Mar-2014/5:44:54-8:00
Still confused with all Rebol versions.
When i try this example:
R E B O L []
do %r3-gui.r3
view [
text "Example window."
button "Close" close
]
I get: Gui error: cannot parse the gui dialect at close
The rebol program used is: r3-view.exe
rebol 3.0 [alpha test] version 2.101.0.3.1 (windows7)
What is the problem?
regards
Richard
Nick — 3-Mar-2014/11:33:39-8:00
In Saphirion's version of R3-GUI, actors are required to respond to an event. You can use 'on-action to respond to the most common widget events:
do %r3-gui.r3
view gui: [
text "Example window."
button "Close" on-action [unview unview]
]
Richard — 4-Mar-2014/8:54:42-8:00
With on action, the button reacts on left clicks. How can you detect right clicks, double clicks....?
To begin with rebol, what would you suggest? Rebol2 or Rebol3??
Richard
Nick — 4-Mar-2014/9:22:58-8:00
That's all documented here:
http://development.saphirion.com/rebol/r3gui/actors/index.shtml
You have these, and other more generic actors:
on-make-when face is first created to initialize special values
on-click-when mouse button clicked on face
on-drag-when dragging inside a face
on-drag-over-when dragging and are over a target face
on-drop-when drag has stopped or when a file is dropped
on-focus-when we have been given or are losing focus
on-get-to fetch state values
on-set-when state values are set
on-clear-when the state values are cleared
on-key-when key has been pressed (for our focus)
on-move-when mouse has moved
on-over-when mouse passes over or away
on-reset-when reset is needed
on-resize-when size values have changed
on-update-when face contents have changed
on-draw-when system starts to draw the face (create DRAW block)
on-scroll-when scrolling is needed
on-scroll-event-when the mouse wheel is used
on-init-when face and its parent pane are ready (including initial sizing)
on-attach-when a face is attached from another face
on-attached-when a face is triggered in the attach reaction chain
To get more info about the type of click:
on-click: [
probe arg/type
]
I've always suggested getting started with Rebol using R2, only because it's more mature. There are currently many more tools, many years of code examples, and hundreds of thousands of support questions answered in the mailing list and altme archives at rebol.org. By learning R2, you can use all the main desktop OS platforms, and moving to R3 is fairly trivial once you really get to know Rebol. When Red becomes a bit more mature, you'll also have all the basics down.
Nick — 4-Mar-2014/18:36:52-8:00
The most compelling reasons to use R3 right now for you're learning Rebol: Unicode and Android support.
Reply