World: r3wp

The improvements have been to lower-level parts of R3. The work on 
the GUI made it abundantly clear that the lower levels needed some 
work. We've been doing that work. Part of that is the parse imoprovements 
that we're working on right now, which will help with improving the 
VID dialects.

load-gui 



; area-tc stylized gob -custom widget-

areatc-obj: context [


	stylize [
	
		 area-tc: box [
		
			about: "Area displaying in color keywords in text"
			
			facets: [
				size: 400x400
				max-size: 2000x2000
			]
			options: [
				size: [pair!]
			]
			faced: [ 
			]
		; internal face funcition:
		
		; empty draw block ...
			draw: [ fill-pen red text 20x20 [  "test" ] ]
			
		; events handler
			actors: [
		
			]	
		 ] ; fin area-tc style
	] ; end stylize
]; end areatc-obj
view [
    area-tc
]


 to draw in the end a black text over a background default colored 
 with a shape and color i didn't choosed that's not not not cool at 
 all  too much code for a useless thing and a wrong result.

Carl has some new ideas that will help fix the resize model, and 
we will be working on those when work on the GUI resumes.

yeah around 2012  and meanwhile I wait ... pfff ok since carl is 
actually working on parse to make it more friendly to idiots like 
me I will say i will wait.

Hew, I've been waiting for the parse enhancements for 5 years, or 
more recently since November. You won't have to wait that long.

Hew -> Hey

I'm frustrated max ... i saw carl working on parse i wanted to take 
that opportinuty to start adapting area-tc to r3  and VID just is 
unfinished not even exploitable to do a starting of a begining of 
a test work ....  i though text instruction as been reformed last 
time carl working on GUI  and that we could use thing like text pos 
[ color1 "string1" color2 "string2" color3 '"string3" etc ...]

but in fact that's the same old draw we had in R2 ...

The Unicode enhancements haven't made it to the GUI yet. We haven't 
been working on the GUI since spring.

hum apparently the sting arguments in text draw is able to "rejoin" 
strings given in a block and you can't give strings to text instruction 
without embeding them to a black

It took a while to even propagate the Unicode and moduule changes 
across the core, let alone the GUI.

yeah ... i believed what people told me you can almost use Vid to 
do area-tc  thing is it's not the case at all ...

Oh, which people? Never mind, it doesn't matter.

button "Close" [quit] that doesn't work neither ?

what i have to do then button "Close" with [actor: [ on-lick: [quit]] 
] ?

ho it's button "close" do [quit]

button "close" quit

ok an just to unview the window  how can i do ?

unview self works ?

I don't recall. Henrik?

we where not talking about VID... just the gob... and did tell you 
that unicode was not yet part of the GUI  :-)

Yead, VID is supposed to make gobs easier to use. Working with gobs 
directly will be verbose and tricky.

yeah but what is the relation betwin the unicode and the fact that 
text instruction draws a text in black when i request it to be red 
?

brianH that's  like every object it's easier only if you know  how 
to fill the proper fields of the object

I expect that the syntax was off.

Howerver when you don't know what you can put and what you can skip 
you end with a ugly code full of useless things

but i like the draw  block in gobs it's more easy to define them 
than being forced to pass by effect object

and the path to acces them is lighter too ...

actually VID is pretty unstable in R3 ... it's not hard to make the 
VM gets a hardcrash ...

The overall design is good, but it needs some changes and debugging 
:(

I mean the design of the gob system and infrastructure, not the dialect.

hum is there an anamonitor for R3 ?

hum i can't tell you what a gob looks like i don't know how to access 
them

system/view ?

No anamonitor for R3 yet. system/view will be going away when the 
VID is modularized.

vid will not be a default thing anymore ?

The plan is now to do a /Core and /View, with /Core coming out first.

anyway VID in R3  couldn't handle properly an anamonitor like script 
so ...

Even when /View comes out, VID will be in one or more modules.

brianh  i know htat what i read on the blog too but i though vid 
would be integrated by default in the VM ... a module is like it's 
external and you don't have it by default

to make it native like ?

There are internal modules, and some of them will wrap natives.

what will be concretly the interrest of having VID as module ? will 
it allow the community to enhance Vid without ringing carl's bell 
around every time ?

Yes.

Plus, modules are useful for organization. Work on VID had to stop 
because the process of organizing it failed, needing modules.

i'm currious to see that ...

Too much code, too much to keep track of. So, Carl took a break to 
start the module system and I finished it.

ok

i want a way to handle fonts the proper way on all os's and with 
draw . i want a given font to be able to speak with me or the VM 
and draw/text to auto adapt the rendering to it. (if i have to simulate 
a fake cursor i will need to know what is the real pixel size of 
each of the chars in my line;;;)

and i want so the fonts given to be rendered the same way on any 
os

That would be nice :)