AltME groups: search
Help · search scripts · search articles · search mailing listresults summary
world | hits |
r4wp | 64 |
r3wp | 1992 |
total: | 2056 |
results window for this page: [start: 1 end: 100]
world-name: r4wp
Group: #Red ... Red language group [web-public] | ||
DocKimbel: 25-Feb-2012 | I need to add support for Syllable, I have the right doc from Kaj for that, so no problem. For Darwin, I would need the right stack layout description on starting a new process, I haven't found yet a recent and official description for that, just a lost page in google's cache from 2009: http://webcache.googleusercontent.com/search?q=cache:4zQ0NwtOKdsJ:blogs.embarcadero.com/eboling/2009/10/13/5620+MacOSX+stack+layout+on+start&cd=4&hl=fr&ct=clnk&gl=fr | |
Andreas: 25-Feb-2012 | from that doc, the osx stack layout looks identical to linux/elf | |
DocKimbel: 25-Feb-2012 | identical from the main() POV, but I'm not sure that's the right kernel stack layout before libc is initialized. | |
Andreas: 25-Feb-2012 | in that doc, it's not describing the stack for main() but the stack layout as setup for the entry point ("_start") | |
Henrik: 30-Nov-2012 | Now after observing development of several GUI systems, there are always some particular things I find wrong with them: They were designed with small details in mind rather than the big picture. This means that when a developer uses a GUI system, he'll find that some things are easy, while others are very hard. For example, none of our GUI systems are particularly designer friendly, meaning that building a skin requires a programmer with artistic skills. There are not many of those around and that's a real problem. Saphirion's R3 GUI was derived from Carl's work in a way, where several parts were rewritten, because they didn't scale enough for real-world GUIs. The rest of the work has been about beefing up the R3 GUI to handle what is needed. Development often seems to go in isolated sections: Building styles, building a layout engine, event handling, skin system, animation or whatever, without a properly coherent view on the whole thing. We talk about how we have a really nice feature, but that feature may not mean much, if it's not functioning in a coherent way with the rest. If I were to restart VID Ext Kit as a new GUI system, I would rewrite it top down: Start with an application with the simplest, purest GUI description and write the GUI system down from there. I would recommend that a GUI system for Red needs to be written like that, starting as early as possible and let it grow downwards instead of upwards with a real application in mind rather than some neat demos. | |
Henrik: 11-Jan-2013 | Not sure how it works in PDF, but I wrote a VID/Postscript converter, using the layout engine of VID to "typeset" in postscript. Maybe this is the way to go for a PDF typesetter. | |
DocKimbel: 14-Mar-2013 | I've found out an annoying bug in the way the interpreter sets the stacks layout for function/native calls with refinements presented in arbitrary order, it results in assigning the wrong arguments to refinements in some cases (caught by 3 unit tests only). I've worked most of the day on changing the way function/native calls are handled by the interpreter to get it right in all cases this time. I hope to finish it for tomorrow. | |
Pekr: 16-May-2013 | btw - I was able to add the button: button: java-new [ java.awt.Button "Test" ] java-do [frame/add button] .... but then label does not display :-) The layout manager probably needs different technique to work with. Btw isn't AWT really old, something like 1995? :-) | |
DocKimbel: 30-Jun-2013 | Damn, Github once again changed their layout...What was wrong with the old one?? It really looks like they change it for just the sake of change... | |
DocKimbel: 30-Jun-2013 | Thanks. The right position for the menu is a bit annoying, but I guess we'll get used to it...Still I prefer the previous layout. | |
Group: Announce ... Announcements only - use Ann-reply to chat [web-public] | ||
Jerry: 6-May-2012 | My REBOL book is going to be published in July. I've almost done the writing. The publisher is BroadView (in China). The first edition will be 10K copies. has designed the book cover, and layout some of the content | |
NickA: 26-Mar-2013 | Nice layout, btw. | |
Robert: 14-Jul-2013 | We did a new Saphir / R3 Andoid release. Changes: -fixed input text renderin bug -reworked misc internal threads synchronisation issues to fix possible dead locks -added ACTIVE, INACTIVE events -added horizontal native scrolling for layouts wider than screen -fixed screen rotation -updated demo script (just type DEMO in the console) -fixed BROWSE bug -added .r3 suffix to be able open this type of R3 scripts automatically -other smaller internal fixes If you want to test it on your phone just run the console and type: do http://development.saphirion.com/experimental/demo.r ATTENTION: We changed the directory layout a bit. You find the Andoid release here: http://development.saphirion.com/experimental/builds/android We added other platforms as well: http://development.saphirion.com/experimental/builds/ And the root is still: http://development.saphirion.com/experimental/ Next Wednesday I will give a short talk about our porting efforts here via Web-Cast: http://www.vksi.de/sneak-preview/17072013-android-qs.htm (German) | |
Robert: 14-Jul-2013 | In conjunction we did a new R3-GUI release as well. added DETAB flag support fixed TEXT-AREA issues fixed TEXT init-size handling fixed SIZE-TXT bug built new R3GUI release (version 4897) delete "experimental" layout-sizing-independent.r3 improve rouding move docs/r3-gui/ to documentation/r3/r3-gui/ remove documentation/r3/r3-gui/license/ directory containing obsolete license Copyright notice update license update typo fixed Rounding correction improved rotate event handling improved drag handling code (removed duplicate gui-events/drag reference) improved android text input handling fixed progress resizing improved text-able cell font handling fonts are antialiased by default on android now http://development.saphirion.com/resources/r3-gui.r | |
Group: Ann-Reply ... Reply to Announce group [web-public] | ||
Jerry: 28-Aug-2012 | Every pages is carefully drawed and layouted. To make the English Edition of it, I have to re-layout every page. Since English Sentence is shorter than it's Chinese one in most of the cases, I will need to re-layout everypage. the aspect should be change from 4:3 to 16:9 or 16:10. This will take some time for me to prepare. | |
Group: Rebol School ... REBOL School [web-public] | ||
caelum: 22-Apr-2012 | Is it possible to change the background color of the view led? Or are the only states available 'true' and 'false' which are green and red? I want different background colors for 'true' and 'false' states. view center-face layout [ across l1: led label "State" state: field btn "Change led state" [ either l1/data [ l1/data: false state/text: "False" ][ l1/data: true l1/data: true state/text: "True" ] show [l1 state] ] ] | |
Henrik: 22-Apr-2012 | you can also do this: view layout [led with [colors: [<your colors here>]]] | |
GiuseppeC: 6-May-2012 | where I am wrong ? I have an object called news news/tittle: "Something" news/data: 06-may-2012 I want to display these data using VID view layout [ h2 news/tittle h2 news/date ] news/tittle is displayed news/date is not Where I am wrong ? | |
Henrik: 6-May-2012 | First, assign words to your texts: view layout [ t1: h2 t2: h2 ] Then create a function to update the content: update-texts: func [tt1 tt2] [ t1/text: tt1 ; not sure that SET-FACE works here. t2/text: tt2 show [t1 t2] ] Then use the function where you need it. | |
Endo: 7-May-2012 | Or give a name to your window: view lay: layout [...] and call "show lay" when you make changes. This will refresh the whole widgets in the window. It's better to refresh what you've updated, not the whole window, as it is much more slower. But when you are testing it is easier. | |
GiuseppeC: 7-May-2012 | Henrik, I am experimenting with your code. Here is my code: view layout [ testo-id: h2 ] update-window: func [ttesto-id] [ testo-id/text: to-string ttesto-id show [testo-id] ] I have the following error: Error: Invalid path value: text | |
james_nak: 7-May-2012 | update-window: func [ttesto-id] [ testo-id/text: to-string ttesto-id show testo-id ] view layout [ testo-id: h2 "hello" [] button {test} [update-window {world}] ] | |
Endo: 8-May-2012 | layout [x: text "test"] ;update x/text with a long text x/line-list: none show x | |
james_nak: 9-May-2012 | Giuseppe, you can experiment by creating your gui code as a block and then "do" it. Then view it. a: [layout [button "hi" [print "hello"]]] b: do a view b | |
Henrik: 10-May-2012 | Perhaps it helps to learn about the mechanisms: There are several ways to generate a dynamic UI: The LAYOUT function works by creating an object tree, a tree of faces that are simply ordinary objects. When passing this to the VIEW function, a layout is displayed. The layout function is part of VID and is as such a high level function. VIEW is a low level function to interpret the face tree. The face tree consists of objects that contain other objects through the FACE/PANE word. If the FACE/PANE contains an object, that object is a single face, that is displayed inside the parent face. If the PANE contains a block, that block may contain multiple objects that are simply multiple faces. As such, a typical window is a face with a FACE/PANE that is a block that contains other objects. Graphically, the face is represented by a region on the screen that has the size and offset, possibly an effect, such as coloring, blur or mirroring or a text attached to it, and image or other faces that are only visible inside that region. A window is also a face. To navigate to the parent face from a face, use the FACE&/PARENT-FACE word. Note that FACE/PARENT-FACE is many times not set by VID, which is sometimes problematic. You can manipulate the face tree by adding removing objects dynamically and calling the SHOW function. You can also change values in existing face objects in the tree, such as for resizing or moving the faces and then calling SHOW again. You can also build a face tree entirely by hand, and this is usually the starting point for different layout engines, such as RebGUI, that simply build face trees in their own way. The prototype face is FACE, which is a minimum requirement face for the View engine. The prototype face for a VID face, which contains a few more words, is SYSTEM/VIEW/VID/VID-FACE, which is the minimum requirement face for VID. One condition for the face tree is to not use the same object in multiple locations. The VIEW or SHOW function will return an error if that is the case. A simpler way is also to generate a new face tree every time you want to change the layout. Although this is slightly more computationally heavy, it allows you to manipulate the block that was passed to the LAYOUT function instead of manipulating the face tree directly. This technique is best used, when the face tree changes dramatically by each manipulation. Another important concept is the DRAW engine which is a separate entity in REBOL2. It can be called to draw on an image bitmap, using the DRAW function or as in effect for a face object, by adding a parameter in the VID dialect block or by changing the FACE/EFFECT word. DRAW is used by calling a dialect. if you just want to use fields, buttons and simple user interface designs, you may not need to use DRAW. | |
GiuseppeC: 10-May-2012 | A question: I create a layout wiich has two button. I whish to add more buttons dynamically updating the layout. How could I do this ? | |
Henrik: 10-May-2012 | You can do this by adding the buttons to a panel and update the contents of this panel. view/new layout [p: panel 500x500 []] ; start with an empty panel. note that VID does not support scrolling panels out-of-the-box. For this you need the VID Extension Kit. append p/pane make get-style 'button [] ; you will need to adjust for offset here, otherwise the new phase will be placed on top of the old one. do in last p/pane 'init ; you will need to initialize the face, which is the FACE/INIT block that resides in the face style definition. once the init block has been run, the face will set itself up and then you can show it show p This is just a simple version of what can be done. To clear it again: clear p show p If you want to do more than this, I think you need to use the VID Extension Kit, because you will be spending a lot of time managing scrollbars and panels. It has styles that are meant for this purpose. | |
Endo: 10-May-2012 | I wrote another simple example as a one-liner, not useful in a real-world app. but gives an idea: view f: layout/size [btn "add" [append f/pane layout/tight/offset [backcolor random white btn random "abcdef"] 50x50 + random 300x300 show f]] 400x400 | |
Endo: 10-May-2012 | It actually adds new faces to the main face's pane, not the new styles. So, not a useful example. ;no need to backcolor.. shorter: view f: layout/size [btn "add" [append f/pane layout/tight/offset [btn random "abcdef"] 50x50 + random 300x300 show f]] 400x400 | |
caelum: 27-May-2012 | A view question. Can the name of a button be changed after it has been created? view layout [button "Text in Button"] I want to change "Text in Button" to "New Text in Button" and redisplay it. I have not come across this anywhere so far? | |
Sunanda: 27-May-2012 | Here's one way: view layout [b: button "Text in Button" [face/text: "Changed!" show face]] Though it'd usually be better to assign the button to a word, so you can change the text at other points in your script too: view layout [ but1: button "Text in Button" but2: button "Press me" [but1/text: "Changed!" show but1] ] | |
Evgeniy Philippov: 10-Jun-2012 | REBOL [Title: "rtext.r"] view layout [treepane: tree contentpane: textarea] 400x400 | |
Henrik: 29-Jun-2012 | You can do that, although that requires you to re-layout the pane. I don't know the code behind the panel, so that may or may not be the best way to do it. It's not the fastest way though. You can manually add a face object to the pane block, but you will then have to calculate its offset, initialize it by hand and resize the parent panel to fit the new face. | |
Henrik: 29-Jun-2012 | But remember that the panel block as described with [across space 0x0 label "_" ... etc. is only a description. Adding something to that block will not affect your current layout. The LAYOUT function parses the block into a tree of objects (faces), which then can be displayed with VIEW. | |
Henrik: 29-Jun-2012 | So, you either re-build that layout, or you manipulate the face object tree directly. | |
Arnold: 29-Jun-2012 | main: layout block view main ...function or other action for computing what block should become... main: layout block ;set it again unview/all view main | |
Henrik: 29-Jun-2012 | try this interactive test: view layout [p: panel [button]] escape to console and type: p/pane: get in layout/tight [field 100] 'pane show p | |
Henrik: 30-Jun-2012 | You can copy the font object with something like this: label "boo" with [font: make font []] There are other ways to trigger copying the font object during the layout process, but I can't exactly remember how, right now. | |
Arnold: 30-Jun-2012 | If I could switch it from a text to a label it would be nice. As yet I have this puzzling experience: REBOL [] high-on: high-on-odd: false swap-even: func [/local n] [ either high-on [for n 2 8 2 [ panel-rechts/pane/:n/font/color: 'white] high-on: false ][ for n 1 7 2 [ panel-rechts/pane/:n/font/color: 'black] high-on: true ] show panel-rechts] swap-odd: func [/local n] [ either high-on-odd [for n 1 7 2 [panel-rechts/pane/:n/font/color: 'white panel-rechts/pane/:n/style: 'lbl-h-la-white] high-on-odd: false ][for n 1 7 2 [panel-rechts/pane/:n/font/color: 'black panel-rechts/pane/:n/style: 'lbl-h-la-normal] high-on-odd: true] show panel-rechts] spiegel-styles: stylize [ lbl-h-la-normal: text left middle 40x100 lbl-h-la-white: label left middle 40x100] view layout [styles spiegel-styles across panel-rechts: panel [below space 0x0 lbl-h-la-white "_" lbl-h-la-white "_" lbl-h-la-normal "_" lbl-h-la-normal "_" lbl-h-la-normal "_" lbl-h-la-normal "_" lbl-h-la-normal "_" lbl-h-la-normal "_"] return button "Even" [swap-even] button "Odd" [swap-odd] button "Debug" [print dump-face panel-rechts print panel-rechts/pane/1/font/color print panel-rechts/pane/1/color print panel-rechts/pane/1/style] ] Where the first two labels change when button Odd is clicked. and then stay unchanged and the debug button shows the changes as expected (by me) | |
Henrik: 30-Jun-2012 | You can't simply switch the style by putting a new word in the STYLE facet. Each style is a prototype object with very different code to manage its internals. Generating a style using layout therefore involves getting a face from the style library, performing a set of operations on it for correct size and offset and run its initialization procedure. Only then is it inserted at the right localtion in the pane of the parent panel. | |
ChristianE: 4-Jul-2012 | view layout [ radio-line of 'a "Check this out" radio-line of 'a "or this" pad 8 radio-line of 'b "Or Check this out" radio-line of 'b "or this" radio-line of 'b "or that" ] | |
Arnold: 4-Jul-2012 | Something like this cost me only a couple of hours trial and err (mostly err) for there was no proper example to copy and it didn't work out of the box without the initialisations. main: layout [ a: radio on 'things lbl-a: "A" b: radio of 'things lbl-b: "B" etc] a/data: true b/data: false view main | |
Maxim: 4-Jul-2012 | ex: view layout [ panel [across radio radio radio on] panel [across radio on radio radio] ] | |
Maxim: 4-Jul-2012 | here is a simple way to get the code for a face within the layout function ( I found it the easiest to remember): view layout [ across text "1" my-radio: radio on do [probe my-radio] text "2" radio ] the advantage of this system is that you get the actual face with any facets setup as they really are in your gui. this is often the easiest way to identify just where and how a specific facet affects a face... probe it without your change, and then run it again, with your change... comparing both probes in a diff or merge tool. | |
ChristianE: 4-Jul-2012 | get-radio-buttons: does [ reduce [ get-face option-1 get-face option-2 get-face option-3 ] ] reset-radio-buttons: does [ clear-face option-1 clear-face option-2 clear-face option-3 ] view layout [ option-1: radio-line "Option 1" of 'options [probe get-radio-buttons] option-2: radio-line "Option 2" of 'options [probe get-radio-buttons] option-3: radio-line "Option 3" of 'options [probe get-radio-buttons] btn "reset radios" [reset-radio-buttons] ] | |
Arnold: 7-Jul-2012 | Hi Chris! Thank you. I consulted this site also. But there is better news to this! In stead of the words on and of you have to use the words true and false and the problems are solved! Didn't even have to initialize the /data fields between creating the layout and calling it in action with view. Not documented but stil possible. (Like it is also undocumented on the REBOL site that you can have a checkbox followed by an action block.And this is also possible on text-labels making them clickable and have an mouse-over effect.) | |
Maxim: 5-Sep-2012 | a one liner: until [ view layout [fld: field] not empty? fld/text ] | |
Maxim: 5-Sep-2012 | here, the field's action compares the field when pressing tab/enter, and will close the window when its not empty. until [view layout [fld: field [unless empty? face/text [unview]]] not empty? fld/text] | |
GrahamC: 5-Sep-2012 | you get that vid error because you are referring to it before the layout function has run. | |
Sunanda: 31-Oct-2012 | Why can't a button hide itself? Looks like /SHOW? is always set TRUE on exit from an action facet: view layout [b: button "hide me" [hide b print b/show?]] (esc) print b/show? ;; expect FALSE if button clicked, but always get TRUE My ungainly work-around is to move the button well out of the visible area: view layout [b: button "hide me" [b/offset: -100x-100 - abs b/offset show b]] (the abs and -100s allow me to reverse the action to put it back where it was) | |
MaxV: 31-Oct-2012 | A button can remove itself: lokk here: a: layout [b: button [remove find a/pane b show a]] view a | |
Sunanda: 2-Nov-2012 | Another question ... I'vd like a field action facet to be triggered on field exit. But I can find two cases (under windows) when it isn't: 1. ctrl+tab out of the field, rather than tab 2. right click another face, eg a button view layout [field 100x100 [print "field was exited"] button "click me" [print 'left] [print 'right]] Any ideas for making the field action trigger in all cases? Please! (Right now my workaround is to do a bulk check on all fields when the user clicks a main action button like SAVE, but that means they may see multiple field-exit messages all at once, and later than they'd expected). | |
Geomol: 20-Dec-2012 | img: make image! 88x88 img/alpha: 255 draw img [ pen none fill-pen linear 0x0 0.0 88.0 90.0 1.0 1.0 0.0.0 16.16.16 32.32.32 box 0x0 88x88 14.0 fill-pen linear 5x5 0.0 78.0 90.0 1.0 1.0 102.102.102 10.10.10 10.10.10 10.10.10 0.0.0 box 5x5 83x83 14.0 ] view layout [ image img ] | |
Cyphre: 20-Dec-2012 | Henrik, I don't know how hard is to add gradient on line but you can 'emulate' it using textures. See this R2 example: g: draw 100x10 [pen none fill-pen linear 0x0 0 100 0 1 1 red green blue yellow box 0x0 100x10] view layout [origin 0 box 300x300 black effect [draw [pen g spline 0x0 100x100 200x30 300x300 16]]] | |
Bo: 20-Dec-2012 | But it was all done in a 'layout block. :-) | |
Geomol: 21-Dec-2012 | sz: 200x400 img: make image! sz img/alpha: 255 draw img compose [ pen none fill-pen linear (as-pair 0 sz/y / 2) -50.5 70.5 90.0 1.0 1.0 45.45.47 9.9.11 108.113.117 circle (as-pair sz/x - 115 sz/y / 2) 70.5 fill-pen 1.0.5 circle (as-pair sz/x - 115 sz/y / 2) 68.5 reset-matrix fill-pen linear (as-pair sz/x - 115 sz/y / 2) -60.5 30.5 45.0 1.0 1.0 161.164.169 161.164.169 89.94.100 box (as-pair sz/x - 115 - 26 sz/y / 2 - 26) (as-pair sz/x - 115 + 26 sz/y / 2 + 26) 10.0 fill-pen 1.0.5 box (as-pair sz/x - 115 - 22 sz/y / 2 - 22) (as-pair sz/x - 115 + 22 sz/y / 2 + 22) 6.0 reset-matrix fill-pen linear (as-pair 0 sz/y / 2 - 26) -50.5 100.5 90.0 1.0 1.0 1.0.5.255 200.214.226.224 200.214.226.128 shape [ move 154x200 arc 16x200 68.0 68.0 arc 154x200 -149.0 68.0 ] ] view layout [ backdrop 1.0.5 image img ] | |
Steeve: 21-Dec-2012 | I don't rememeber who did the neon effect, but here it is. font-C: make face/font [style: [ bold ] size: 64] neon: "REBOL BAR" coord: 30x15 inc: 0.25.25 draw-block: compose [ line-join round font font-c pen (inc * 1 + 255.0.0.230) line-width 11 text vectorial coord neon pen (inc * 2 + 255.0.0.205) line-width 9 text vectorial coord neon pen (inc * 3 + 255.0.0.180) line-width 8 text vectorial coord neon pen (inc * 4 + 255.0.0.155) line-width 7 text vectorial coord neon pen (inc * 5 + 255.0.0.130) line-width 6 text vectorial coord neon pen (inc * 6 + 255.0.0.105) line-width 5 text vectorial coord neon pen (inc * 7 + 255.0.0.80) line-width 4 text vectorial coord neon pen (inc * 8 + 255.0.0.55) line-width 3 text vectorial coord neon pen (inc * 9 + 255.0.0.30) line-width 2 text vectorial coord neon pen (inc * 10 + 255.0.0.5) line-width 1 text vectorial coord neon ] view/title layout [ box black 450x200 effect [ draw draw-block ] ] "NEON" | |
GrahamC: 27-Feb-2013 | #include %gfx-colors.r #include %gfx-funcs.r #include %view-funcs.r #include %view-vid.r #include %view-edit.r #include %view-feel.r #include %view-images.r #include %view-styles.r #include %view-request.r ;-- Must be done prior to loading anything that requires fonts on Linux. layout [text "imanXwin kludge"] ;-throw this one away soon-- okay? open-events | |
caelum: 28-Feb-2013 | Same as yours only with prot-setnet.r added. #include %gfx-colors.r #include %gfx-funcs.r #include %view-funcs.r #include %view-vid.r #include %view-edit.r #include %view-feel.r #include %view-images.r #include %view-styles.r #include %view-request.r #include %prot-setnet.r ;-- Must be done prior to loading anything that requires fonts on Linux. layout [text "imanXwin kludge"] ;-throw this one away soon-- okay? open-events | |
Group: !Syllable ... Syllable free operating system family [web-public] | ||
Kaj: 11-May-2012 | I got some of the examples of the Edje layout engine to work | |
Group: #Red Docs ... How should Red be documented [web-public] | ||
Gregg: 4-Dec-2012 | What I like about http://clojuredocs.org/quickref/ClojureCore, compared to the rebol dict page and senha API page, is: - No need to expand or collapse the TOC on the left. You can see two top-level headings. - Single scrolling page you can scan. And I do like the visible scrolling in this case. - Summary doc string visible for each item. Again, good for scanning. - Having the number of examples listed is nice, and shows what needs examples. - It's a clean, effective layout to my eye, providing useful detail before drilling down. | |
Gregg: 4-Dec-2012 | Just looked at http://clojuredocs.org/clojure_core, and it is *not* a useful layout IMO. | |
Group: !REBOL3 ... General discussion about REBOL 3 [web-public] | ||
Scot: 28-Feb-2013 | The approach needs to provide tools so easy you can layout an app as easily as making a powerpoint presentation, but with the power underneath to do absolutely anything. | |
Group: !R3 Building and Porting ... [web-public] | ||
AdrianS: 4-Feb-2013 | Just so happens that I have a CB project file for the official source layout, if you want it. There's also a little change to make-make.r that you'll need t make for which he's made a pull request. https://github.com/rebol/r3/pull/77 |
world-name: r3wp
Group: Script Library ... REBOL.org: Script library and Mailing list archive [web-public] | ||
Sunanda: 19-Jan-2005 | Please mock up an example -- you could do it in View layout -- that'd make the discussion more concrete. | |
Group: I'm new ... Ask any question, and a helpful person will try to answer. [web-public] | ||
DideC: 10-Mar-2005 | ctx: context bind [ chars: charset [ #"A" - #"Z" #"a" - #"z" #"0" - #"9" #"-" #"_"] non-chars: complement chars set 'copy-word has [start end end-rule car-pos] [ if any [not focal-face not caret] [exit] car-pos: index? caret end-rule: copy [] parse/all head caret [ any [ start: some chars end: ( if all [car-pos >= index? start car-pos <= index? end] [end-rule: 'break] ) end-rule | some non-chars (start: end: none) ] ] if all [start end] [write clipboard:// probe copy/part start end] ] ] in system/view 'focal-face view layout [ area "This is some text to test" text "To copy the word under the cursor : hit CTRL+K or press the button bellow" button "Copy word" #"^K" [copy-word] ] | |
Henrik: 10-Mar-2005 | is it possible to use an object variable for a VID item, such as obj: make object! [t: none] where I would like view layout [obj/t: button "hello"] in some way? it doesn't work... | |
Anton: 10-Mar-2005 | o: context [var: none] layout [button with [o/var: self]] o/var/type ;== face o/var/style ;== button | |
Anton: 10-Mar-2005 | For example, don't do this: text: context [var: none] layout [button with [text/var: self]] ** Script Error: Cannot use path on none! value ** Where: forever ** Near: text/var: self | |
Anton: 10-Mar-2005 | The most elegant solution would be to patch layout so it accepts set-paths. | |
Allen: 30-Apr-2005 | blocks are also great for composing in, e.g creating a dynamic layout block to pass to the layout function or draw | |
Alberto: 9-Jun-2005 | view layout [ across lbl "field 1" f1: field return lbl "field 2" f2: field return btn "hide f2" [hide f2] ] | |
Bobik: 4-Oct-2005 | Could you help me anybody? I have a simple sequences of commands: view layout [label "hello"] tx: request-text "something" ... I need invoke request-text immediately after main window showed - not after the main window is closed... | |
Bobik: 4-Oct-2005 | So if i use view layout [.....] it is as some as if i use: view/new layout [....] do-events ? | |
Bobik: 5-Oct-2005 | I can not understand behaviour of my example: If i have a script1.r: view layout [ ... btn "script2" [ do %script2.r print 123 ] ] ... and sript2.r has: view layout [.....] I expected that <print 123> will not execute because script2 has view layout... (no view/new layout [...]) | |
Pekr: 6-Oct-2005 | it does not seem to work: view layout [btn "So what?" [inform layout [text "So what?"]]] | |
Bobik: 6-Oct-2005 | so how can i get layout of requester(f.e. request-text) to do it ?> insert tail system/view/sreen-face/pane/1/pane <what?> | |
Anton: 29-Oct-2005 | LAYOUT calls GROW-FACETS which handles some types and collects others in blocks to let NEW/MULTI handle them (where NEW is the face which is being created.) See the code here: print mold get in svv 'grow-facets | |
BrianH: 5-Apr-2006 | Plus the user interface loks a little off because it is written for an older version of WinCE, and the title bar didn't match the standard layout even then. | |
BrianH: 5-Apr-2006 | I haven't tried it on the smartphone layout, but I would be shocked if it worked. :) | |
Group: CGI ... web server issues [web-public] | ||
Anton: 4-Jul-2005 | view layout [b: box 200x100 navy image help.gif feel [engage: func [face action event][if find [over down] action [b/text: mold pick face/image event/offset show b]]]] | |
Group: Web ... Everything web development related [web-public] | ||
Maxim: 12-Jan-2005 | you can basically have the artist doing the pics and layout, and a developper doing the code part... | |
eFishAnt: 22-Jan-2005 | so can you speak a REBOL script into here? Oops forgot, not Messenger where do [ view/new layout [ box ] ] can be done... | |
Carl: 22-Jan-2005 | view layout [image percent photo.JP button "quit "[quit ] ] | |
Pekr: 30-Jan-2005 | One question though. Both class and id are used mostly to describe layout. I mean - Gabriele's temple uses class and id to identify what/how data should be filled in, but it may not be in correspondence with design. I should note, that Temple design is how I imagine templating system should work. When you work in trio-mode - user (entering data into app), programmer and designer (which can't program), most template systems are not acceptable, as they break the ability to see the design work result, unless loaded into production environment, and that is not acceptable in my situation ... | |
yeksoon: 30-Jan-2005 | on Gab's Temple. pre-defining the 'id' is a way for developers and designer to communicate and agree on certain stuffs. That is how the separation of work is being done. Developer will code with 'address' in mind in their business logic..and designer just design the layout and only need to put in id 'address'. | |
Sunanda: 31-Jan-2005 | Divs are ultimately more flexible than tables. Tables have their place -- for the display of tabular data as they were intended. For page layout and markup, DIVs are ultimately less boxy. They also, usually, produce data flow that is more friendly than tables for people using accessibility aids. | |
yeksoon: 3-Feb-2005 | I have a problem with some layout. Trying to align an output of 'processingtime' and some 'footer' on the same line.. but I always end up wiht the footer a line below. The left-right alignment is correct though. --- .footer { text-align: right; font:10px verdana, arial, helvetica, sans-serif; color: #666; background: transparent; } .processingtime { text-align: left; font:10px verdana, arial, helvetica, sans-serif; color: #666; background: transparent; } -- -- <div class="processingtime">some processing time</div> <div class="footer">some trademarks stuffs</div> -- | |
Group: Cookbook ... For http://www.rebol.net/cookbook/requests.html [web-public] | ||
DideC: 8-Jul-2005 | main: layout [ space 2 origin 4 across style pane-tog tog of 'panels ; Just to avoid puting {of 'panels} in each tog lines below pane1-tab: pane-tog 100x30 "Pane 1" [show-pane pane1] pane2-tab: pane-tog 100x30 "Pane 2" [show-pane pane2] pane3-tab: pane-tog 100x30 "Pane 3" [show-pane pane3] return content-pane: box 300x200 return btn white "Save" ; Save and Apply are used here for decorative purposes btn orange "Apply" btn sky "Close" [unview] ] | |
DideC: 8-Jul-2005 | pane1: layout/offset [ across text "Setting 1" field return text "Setting 2" field ] 0x0 ... | |
DideC: 8-Jul-2005 | The note talk about layout/TIGHT, but you did not use it before !!!! | |
Henrik: 8-Jul-2005 | hmm... this will mean that the layout/offset is not the same as contents-pane/pane/offset | |
Group: Rebol/Flash dialect ... content related to Rebol/Flash dialect [web-public] | ||
Oldes: 8-Oct-2007 | Rebol/Flash dialect (RSWF) version 2.5.0 is available! compressed: http://box.lebeda.ws/~hmm/rswf/rswf_latest.r(89kB) uncompressed: http://box.lebeda.ws/~hmm/rswf/rswf_2.5.0.r(331kB) as colorized HTML: http://box.lebeda.ws/~hmm/rswf/rswf_2.5.0.html (885kB) What's new: - New swf-parser included which replaces old exam-swf function (useful for importing foreign SWF files) - Added implementation of Class definitions for SWF versions 6 and higher (I have to create some examples) - Added new 'trace function into actions (which can be use to compile swf files with or without trace calls easily) - 'require and 'include now accepts block of files or urls (I should modify my rswf code colorizer to show included files as well) Here is also new example how to include first of GUI elements: http://box.lebeda.ws/~hmm/rswf/example/swf8-cliphandler In the future I would like to create something like mini Layout dialect which will be used for better positioning of the new GUIs I'm working on. | |
Oldes: 10-Oct-2007 | Version 2.6.0 available.... now with first version of LAYOUT... (only buttons available now) http://box.lebeda.ws/~hmm/rswf/example/swf8-layout-buttons | |
Oldes: 19-Oct-2007 | Version 2.8.0 available.... - Updated layouter (now with new 'Field, 'Password and 'Area GUIs) http://box.lebeda.ws/~hmm/rswf/rswf_latest.r http://box.lebeda.ws/~hmm/rswf/rswf_2.8.0.r New example script: http://box.lebeda.ws/~hmm/rswf/example/swf8-layout-fields | |
Oldes: 24-Oct-2007 | Version 2.9.0 ... now with Calendar GUI and fixed one nasty bug in 'IF compilation after 'EITHER rule http://box.lebeda.ws/~hmm/rswf/example/swf8-layout-calendar | |
Oldes: 25-Oct-2007 | It is possible to create drag'n'drop editor in the dialect as well.. but first I have other goals. And maybe one day you will be able to create layout from Rebol VID too. | |
Terry: 16-Nov-2007 | To give you an example.. this.. <?xml version="1.0" encoding="utf-8"?> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"layout="absolute"> <mx:Panel title="My Application" width="200" height="300" x="0" y="0"> <mx:Label text="Welcome to Flex!" mouseDownEffect="WipeRight" height="45"/> </mx:Panel> <mx:PopUpButton x="483" y="20" label="PopUpButton"/> <mx:Accordion x="441" y="50" width="200" height="200"> <mx:Canvas label="Accordion Pane 1" width="100%" height="100%"> </mx:Canvas> <mx:Canvas label="asdf" width="100%" height="100%"> </mx:Canvas> <mx:Canvas label="asdf" width="100%" height="100%"> </mx:Canvas> <mx:Canvas label="adsf" width="100%" height="100%"> </mx:Canvas> </mx:Accordion> <mx:CheckBox x="441" y="258" label="Checkbox"/> <mx:DateChooser x="238.5" y="31"/> </mx:Application> | |
Group: Plugin-2 ... Browser Plugins [web-public] | ||
BrianH: 5-May-2006 | For that matter, is it possible to specify the size of the client area relative to the page size, have it resize with the page, and have the REBOL layout inside handle the resize as if a View window had been resized by the user? | |
Group: !Cheyenne ... Discussions about the Cheyenne Web Server [web-public] | ||
Maxim: 22-Feb-2007 | I put 0% of time on site layout, once its done. I just edit content and make the page. its like editing make doc, but in html format... also, the tags are not standard html type tags they nest directely <p! text <b! is bold <i! and italic>>> |
1 / 2056 | [1] | 2 | 3 | 4 | 5 | ... | 17 | 18 | 19 | 20 | 21 |