r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!RebGUI] A lightweight alternative to VID

sqlab
31-Jul-2009
[8211]
Windows XP with 1366 x 768


After start of tour.r the upper border is outside the screen and 
the status line not visible.

After moving the window down with the cursor keys, the status line 
gets visible.

After moving  the cursor to the upper edge with every click there 
the main windows moves down a step.
Ashley
31-Jul-2009
[8212x2]
changed from single color web like look to some W9x look, was there 
any reason?
 ... commercial reality ;)
where would I have changed the font?
 ... ctx-rebgui/effects/font
request-char somehow misbehaves here
 ... bug, noted
fonts must be handled differently in w7s

 ... I don't have access to W7 at home, but will check this Monday 
 at work
where do I set my UI options?

 Design time with ctx-rebgui/effects, /colors /behaviors and /sizes

 Adding request-ui back so you can alter these values from a GUI is 
 trivial ... what I've removed is the rebind logic that enabled you 
 to dynamically change values (i.e. you would have to re-do %rebgui.r 
 to see any UI changes take effect ... not very practical for an SDK 
 app)
they look like W9x

 ... the color scheme (with the colors/page change noted above) is 
 taken straight from W7
don't like gradiented buttons/tab
 ... based on W7 and Mac
I thought Ashley wanted to go more web way, not desktop app way

 ... I've actually gone for something halfway (simpler than OS, more 
 complex than Web)
is it using a smaller font?

 ... 12pt by default as always (maybe W7 renders it differently than 
 XP?)
everything seems much smaller
 ... bigger screen? ;)
I would welcome tour.r would fit 1280x800 notebook

 ... RC1 is about getting the basic functionality right, %tour.r and 
 %RebDOC.r will both be made to run 1024x768
used to fit
 ... they havn't been reworked yet
Windows XP with 1366 x 768 ...
 ... will be fixed with above
Build 201 uploaded
- Added request-error
- Enhanced request-verify
- Added set-enable
- Added set-disable
- Added layout disable option
- Enhanced led widget
- Enhanced radio-group

Example disable/enable usage

display "test" [
	f: area "Blah" disable
	button "Enable" [set-enable f]
	button "Disable" [set-disable f]
]
do-events
sqlab
31-Jul-2009
[8214]
sorry. I was not detailed enough,

the status line is not visible in the first place, although the lower 
border is inside the screen.

It's not possible to move the window with cursor keys, as it always 
snaps back.

It's not possble to resize the window by catching the upper edge 
with the mouse, as it always snaps down.
I hope I am clearer now.
Henrik
31-Jul-2009
[8215]
where can I download this again? sorry for not keeping up. :-)
Pekr
31-Jul-2009
[8216]
Could drop-downs be closed by clicking outside of them? Only ESC 
is possible right now ...
Graham
31-Jul-2009
[8217x2]
Henrik .. just do a google search for rebgui codeplex
I found this in my code:


#if [linux][
    set-fonts/name "helvetica"
    set-fonts/size 12
]
Henrik
31-Jul-2009
[8219]
thanks, got it
Ashley
1-Aug-2009
[8220]
Build 202 uploaded ( https://rebgui.svn.codeplex.com/svn/)
- Fixed password
- Added icon to tour.r
- Resized tour.r to fit smaller screens

- Reworked layout and display functions to remove duplicate show 
and do-events calls
- Removed do-events from tour.r and RebDOC.r


The layout/display change (apart from correcting numerous rendering 
anomolies and improving layout speed) may have caused other unforseen 
side-effects. At the very least it changes RebGUI in the following 
manner; previously you would write:

	display "A" [...]
	print "A"
	do-events

and get "A"  printed to the console. Now you write:

	display "A" [...]
	print "A"


and only get "A" printed to the console once the display has been 
closed. This now lets you write code like:

	display "A" [ ;do some stuff to set result]
	process result and display "B" or "C" based on result

This change is still experimental so let me know what you think.


Also, who actually uses tool-tips??? I've been debating whether to 
fix them so they work properly, or just remove them entirely. Thoughts?
Graham
1-Aug-2009
[8221]
I'd like to use them one day .. but never have got around to doing 
so.
Pekr
1-Aug-2009
[8222x2]
never used tooltips, but sometimes with another apps I welcome them, 
to find description for icons ....
One note to drop-list. Apart from the fact, that it can be closed 
only by pressing ESC, it does a little bit weird thing - it remembers 
its last mouse-over element. So mouse-over some drop-list item, then 
go-away from it, then press ESC. The value of drop-list changes to 
that last remembered mouse-over one ...
Ashley
1-Aug-2009
[8224]
Yep, I need to rework the popup logic (drop-lists, edit-lists, menus) 
a bit. There was/is a lot of code to work around non-existant view 
bugs (which were present pre View 1.3). Most of the weird exceptions 
are now caused by the little-used tool-tip code! ;)
Graham
1-Aug-2009
[8225x4]
Just wondering if when there are major changes, if they can be uploaded 
to a different branch for testing before being committed to the main 
trunk.
Sounds like display is now always modal??
That's a major change .. like changing from view/new to view
Doesn't this break lots of things?
marek
1-Aug-2009
[8229x3]
I am just trying new RebGUI and like it a lot. There is one, at least, 
big problem with disable.
Sorry for breaking my message. Hopeffuly changed settings will work 
now.
>> display "" [panel data [button] disable panel data [button] disable] 
  ;;== it only disables second panel and first can't be disabled 
even later in code
Ashley
1-Aug-2009
[8232x2]
Sounds like display is now always modal?

 ... I thought modal is when only the active dialog/popup can accept 
 user input? That's still the case, try the follwing:

	display "Test" [
		area
		button "A" [display "A" [button]]
		button "B" [alert "B"]
	]


Press "A" and type some text into the area, then close "A" and try 
the same thing with "B".
Marek, good pickup ... I'll add that to the list of fixes.
marek
1-Aug-2009
[8234]
Another discovery. One can only select one table at a time. This 
is more serious problem, me thinks. The previous one seems to work 
later, but directtly from display.
And it seems tha I can send more than 1 line at the time now.
marek
2-Aug-2009
[8235]
It must be my poor accent. Not all panels or widgets inside of them 
can be disabled in layout. Later, when program is run seems to be 
no problem.

There is another little problem with tables. When last column is 
right justified with no scroller there is small gap between text 
and edge of table. when scoller kicks in
there is no gap at all.

Finally let me have little wish. Would it be possible for table to 
have 'no-sort option? Would it be usefull to anybody else?
Graham
2-Aug-2009
[8236]
I'd rather have fixed sort so you can choose which column to sort 
on, and not let it change .. as an option.  similar I guess to your 
wish?
marek
2-Aug-2009
[8237x2]
If hidden column can be one to be sorted we both will be happy.  
So it should work this way too.
I was just testing tables by

>> display "" [table options ["A" left 1.0] data [1 2] table options 
["B" left 1.0] data [3 4]]

1. Only one table can be selected from as I already discovered before

2. When any table is selected from pressing <TAB> causes this ERROR
** Internal Error: Stack overflow
** Where: group?
** Near: all [
    in face 'group 
    get in face 'group
]
Graham
2-Aug-2009
[8239x2]
oh no ... stack overflow returns :(
Note, that you can "hide" a column like this

options [ "Hidden" left .001 "Visible" left  .99 ]
marek
2-Aug-2009
[8241]
Any reason why not go:-

>> options ["" left 0.0 "Visible" left 1.0]  ;; seems to work as 
well
Graham
2-Aug-2009
[8242]
oh? didn't know could use 0.0 !
marek
2-Aug-2009
[8243]
Another possible problem, with button widget.

>> display "" [b1: button 0x0 b2: button 0 b3: button 10 button "sizes?" 
[print [b1/size b2/size b3/size]]]
Using older versions sizes are 0x0 0x20 40x40.
Version 202 comes up with 20x0 20x20 52x20.

When box widget is tested in the same way results are the same. Hope 
it will help.
Ashley
3-Aug-2009
[8244]
Build 203
- Better icons for alert, help, info & stop
- Removed tool-tip widget and supporting code
- Added ctx-rebgui/on-error object
- request-error: added icon
- request-password: added icon
- request-password: added cancel button
- request-value: added icon
- request-verify: added icon
- request-progress: added icon
- display: added no-wait option to fix request-progress
- Table: fixed resizing artifacts
- Table: added 'no-sort option
- Table: added 'no-resize option
- Table: added 'fixed-sort option
- Fixed layout/only (it ignored disable)
- Removed %images dir
- updated tour.r and RebDOC.r
Pekr
3-Aug-2009
[8245x4]
so tooltip was removed even for icons?
aren't LEDs a little bit too big?
- opening menu while not closing previous one is allowed - a bug 
imo ... I expect those things fixed with preannounced changes to 
pop-up layer?
- grouping/scroll-pannel - few pixels missing on lower scroller?
Ashley
3-Aug-2009
[8249]
This should address the table and disable issues raised above. WRT 
other issues:

stack overflow return
 ... could not duplicate this.
One can only select one table at a time

 ... select = focus, and yes, as focus shifts so to does the "selected" 
 row
And it seems tha I can send more than 1 line at the time now

 ... not sure I understand what the issue is here.Are we saying 'multi 
 is always on now?
hidden column

 ...I plan to properly support hidden columns ... if column width 
 is zero the face iterator will not create a face and it will not 
 otherwise be treated as a "column"
button widths

 ... the width sizing algorithm changed for button, label, heading, 
 etc (basically anything that appears on a single line)

 - previously you had to use -1 (or larger widths) to accomodate larger 
 text as the width was fixed

 - now it is fixed to the greater of it's specified width and it's 
 natural text width; and -1 sizes to the maximum of text width and 
 a line

 - there is no checking for button height (as it is assumed you would 
 either leave it at default 5 or have it larger
Pekr
3-Aug-2009
[8250x3]
lower=bottom
- title-group and image RebDoc section depend upon images from /images 
directory, which are now deleted hence not available anymore ....
- scrollbars are behing a little weirdly. When you press mouse button 
down, and you go away from scrollbar (or not), the content starts 
scrolling even before the scroller is visually moved. Nicely visible 
with RebDoc for e.g.
marek
3-Aug-2009
[8253x5]
About my previous musing...

stack overflow return

 ... This is my fault as I  put ctx-rebgui/behaviors/tabbed: [... 
 (no table in)] in my little program. Need another safe way to do 
 that.
one can only select one table at a time
 ... not tabbable table is the only way
hidden column
 ... will use 0.01
button width

 ... basically when one specify [button 100] one get old [button 103] 
 but that's ok if we know it.
More about stack overflow and tables.

When taking 'table from ctx/behaviors/tabbed it still works any extra 
tabbable widget like so

>> [table options ["A" left 1.0] data [1] table options ["B" left 
1.0] data [1] button]

but selecting from one table deselects the other. All tables selection 
was possible with previous incarnation of RebGUI. I hope somebody 
else was using this feature so it's not only me using before and 
wanting it.
I hope I nailed down my table problem now.

It seems that one can select from all text-lists on display, but 
only one table is selected from - selecting next one deselects previous 
one. Tabbded on not is not the problem.


Drop-list and edit-list cannot be closed by clicking elswhere but 
this is still to be fixed, isn'i it.
>> display "" [b1: button 5 "Short" b2: button 5 "Very Very long" 
button [print [b1/size b2/size]]]
42x20 93x20


Is this as intended? One more disadventage is no multiples of 4; 
hard to align your widgets.
I'm wrong in previous post. Please desregard it. There is no problem 
there.
marek
4-Aug-2009
[8258]
Another little observation.

This works correctly:-

>>display "" [p1: panel data [a1: area] button [set-disable a1] button 
[set-enable a1]]

This does not:-

>> display "" [p1: panel data [area] button [set-disable p1/pane/1] 
button [set-enable p1/pane/1]]  ;;  disable every time, enable never
Ashley
5-Aug-2009
[8259x2]
title-group and image RebDoc section depend upon image ...
 Fixed in next build
scrollbars are behing a little weirdly
 ... noted

basically when one specify [button 100] one get old [button 103] 
but that's ok if we know it
 ... ah, I understand the issue now. Fixed in next build.

I hope somebody else was using this feature so it's not only me using 
before and wanting it.

 ... don't worry, I think the issue is that table needs to differentiate 
 between a selected row and a row that has focus. This was not an 
 issue in previous versions as table was not a tabbable widget. Will 
 be fixed in a future build.

Drop-list and edit-list cannot be closed by clicking elswhere but 
this is still to be fixed, isn'i it.
 ... on the list to fix
Another little observation.

 ... that's an interesting bug and I have no idea at this stage why 
 the 2nd case doesn't work. Needs further investigation.


Good work marek (and others) ... we're slowly but surely ironing 
out the issues.
A small example of using the new request-error function to handle 
errors in a user-friendly fashion:

	do %rebgui.r
	if error? set/any 'err try [
		display "Main" [
			button 100x50 "Sub" [
				display "Sub" [button 50x25 "Error" [1 / 0]]
			]
		]
	]  [request-error err]