World: r3wp

the build system will allow that, but the question is if the source 
will be published like that. I hope it will, but I would not rule 
out that many styles will depend on eachother in the future.

so taking apart the R3 GUI WRT styles may not work as well.

I would regard such design being - fundamental. I like that RebGUI 
because of that - one widget, one file, easy as that. There is too 
much fuss about inheritance, having some base, upon which other styles 
are based - that is an utopia, and I don't know, while we still keep 
to that. That does not save any signicant memory, and I doubt that 
by changing one parameter to some base style, you want to have all 
childs influenced. That is nice example of inheritance, but completly 
misses practical usability imo :-)

But - I think that we can't change it in recent stage of development, 
so just regards it being my typical rant :-)

It's not utopia, it saves you from writing the same code over and 
over again.

yes, but there is no clear boundary for the style - it is "scattered 
around" ....

same code = pre-rebol ??

Pekr, actually not. On a style level, the style itself is contained 
within one file. It's been like that since Carl's first prototype 
and it stays that way, but a table may contain a variety of different 
styles, such as fields for editable input, but you really don't want 
field to be in the same source file as for table.

so some styles will have dependencies

OK, so it is source-code organisation vs the functionality. That 
is acceptable to me. So simply put - while you might copy table-widget 
around, it might not work, if dependable upon other styles (table 
is compound of multiple styles), which you don't copy/include too 
....

Yes, styles have dependencies. For example TOGGLE is based on BUTTON.

yes, but working a failsafe mechanism into table that makes it slightly 
less functional if a field is not there... I'm not sure that's a 
good idea. It's better to dictate dependencies and follow them. What 
if you decide to derive table? You might get different R3 GUIs that 
work differently. It's now starting to make me think that it's a 
bad idea to allow removal of certain styles. :-)

what about having another field in the style, called 'depends-upon: 
[other styles here] .... then, upon such flags, you might be able 
to kind of automate it ...

look, that's not something absolutly needed, but would be nice, if 
R3 becomes popular, and we have hundreds of styles around to choose 
from :-))

don't prematurely optimize

what sort of completion are we at now ?  10, 50, 70, 90 % ?

Pekr, no absolutely not. That is too error prone.

Are we going to be loading the gui from file storage?

completion: don't know about any particular percentage.

file storage: right now yes, but later it probably will be integrated.

does the latest r3gui work in the released hostkit, or only with 
the version you gave us saturday?

is there a way we can get the r3-gui not compressed?  I'm getting 
strange handler errors which cause rebol to halt whever I try to 
open another window not from r3 gui.

I don't care if it 30MB in size.   I could help you with the debugging, 
but right now its very tedious to do.

I'm preparing a different build script, so it will appear uncompressed. 
Should be up within a day or so.

cool


also, is there a way to link an arbitrary gob within the gui defintion?

I'd like to show an animated 3D teapot within r3gui  :-)

seems using view/as-is when r3-gui is loaded prevents r3-gui from 
doing its stuff... it craps out with a handler-related error...

(this is on a window not using r3-gui, btw)

hmmm... I'm not sure yet. the closest thing is probably IMAGE or 
DRAW faces.

view is probably broken with non-standard windows. I made a few changes 
in it to make it work properly, but it could use a rewrite.

it could be nice to add a simple style called gob, which just uses 
a gob! as its setup data


basically, it would be a static gob, which only displays itself, 
doesn't resize or just doesn't respond to the resize re/actors.


this would allow integration of different graphics tools which weren't 
setup using r3gui.

just a thought.

I'll pass this on (if it's not already in there)

thxs


are the online docs usable for style definition or has it changed 
so much that there's no point in trying to make a custom style right 
now?

new build is up with uncompressed source:

http://rebol.hmkdesign.dk/files/r3/gui/r3-gui.r3

oh cool!

please download to local disk

style building has only changed with regards to resizing (which I 
haven't entirely figured out yet), but otherwise remains the same, 
so feel free to build some styles.

later, Cyphre will come up with some modifications to draw blocks 
for styles, so we can use positional keywords that work together 
with the box model, so it becomes easier to create draw blocks.

ah there is a box style I can easily use.

thanxs for all.

ok, cool

hum... using stylize doesn't seem to add to the global style sheet... 
is there a function to call first to setup or assign to a specific 
stylesheet?

such as to replicate stylize/master   in R2..

it should do that. it's a bug if it doesn't.

DOH!.... it would help if i used stylize  BEFORE  I use view   ;-)

seems to work now.  :-)

ok :-)

btw, I'm working on fixing the as-is event handler issue I found 
earlier...

is it normal that (out of the box) there is nothing happening to 
controls when I press on the mouse?

if you don't add any reactors, then I think so, yes.

you mean.. buttons don't click (visually) unless I add an action 
to them?

cause right now, the gui looks totally dead a part for the fact that 
it resizes (though its late by one window resize event.)