World: r3wp

Just posted this to my blog http://swt1962.spaces.live.com;-)

BTW SteveT, the CLR doesn't interpret its bytecodes, ever - it compiles 
them to native code and then executes the native code. Interpretation 
isn't what makes .NET and C# slow.

Carl once told me that he has found the best REBOL programmers to 
be former assembly language programmers.

Henrik: if you know the size, preallocate. if you don't, in my experience 
it's preallocation that degrades performance. but... don't listen 
to me, just time your code. :)

Sunanda: parse works with comma delimited if there is a comma in 
the fields, as long as the fields are delimited by " when this happens.

>> parse/all {one,two,"three with a , inside",four} ","
== ["one" "two" "three with a , inside" "four"]

Thanks Gabriele -- that may work for SteveT.

However, there are some anomalies in the way parse handles RFC4180 
formatted CSV files. Particularly if there are embedded double quotes 
in a field.


For my purposes, I find tab delimited files are better -- though 
still not always perfect:

    >> x: parse/all {"a"^- ","","} to-string tab

    == ["a" { ","","}]   ;; 2nd field should be {,",}  -- result is close 
    enough that it can be tidied into that
 
   >> y: parse/all {"a", ","","} ","
    == ["a" { "} "" ""]    ;; 2nd field mashed irrecoverable!

the best solution is always to create your own rule, that fits your 
source files perfectly. the built in one helps in simple cases, but 
gets in the way more often than not (imho). it's handy for new users 
though, because they can parse cvs right away, and worry about the 
details only later on when they've learnt parse better :)

Hi Gabriele, that's a good point, I've read the above articles about 
parse and there's an awful lot to learn to use it effectivly in REBOL.

Hi Henrik, yes I know it can be done and you can create your own 
styles or extensions, but new 'Winows' programmers will be very put 
off by that. they shouldn't have to override the VID to do expected 
things liek I mentioned.

exactly. this problem will go away in VID3 for R3. VID is very sparse 
with features like this and you've hit that wall now, a wall I've 
been climbing for years by doing things like LIST-VIEW and vid-field.r. 
:-)

;-)

a problem is that a lot of these internals are not documented and 
so they are very hard to figure out. I think it's safe to say this 
is the biggest sore point about REBOL, one we're anxious to not only 
fix but to turn completely around on and become a leader with.

I know some of my old colleagues would have a tick list before they 
would attempt any language/system and i think VID fails badly there. 
I can cope with it cos I'm so into Rebol, but I know others would 
find say Python with vxWidgets would tick more of their boxes!  Sorry 
for swearing (Python) ;-)

your points are perfectly valid :-)

BTW Henrik - when do you sleep ?

i thought I was bad!

I'm usually a night owl. I went to bed at 3 am and I got up at 11 
am.

which is almost an hour ago here

You in Denmark ??

yes

Are a lot of the other guys in the US? It's interesting to see where 
were all spread - hink Ashley is anitpadean Tes?

I think we're mostly US and European, but we have a few easterners 
as well.

Cool, is Ashley re-working rebGUI for VID 3 or will it be redundant. 
I've never bean totally happy with a third party widgets (like Python 
+ vxWidgets) or Java + Mattisse etc

The accessors to the widgets need to be developed by the language 
developers normally IMO

I had a go with Ruby and vxWidgerts - it really put me off

I'm not sure RebGUI will be available for R3, but he knows that better 
than me. I've never used RebGUI much. :-)

No I've downloaded it but put it to one-side, too much to learn at 
the moment.

Can a style include events?

yes, you can manipulate the events for a style with the FEEL object.

Right so I could create  styles to override the field and include 
params for number of chars to allow or convert to upper and perhaps 
use parse to restrict to numbers ?

Yes, you can trap and handle in your own way all of the events a 
field style can receive.

Thanks Henrik , I'll have a go with that today.

print mold svv/vid-styles/field/feel

You can see the engage function is where most of the event handling 
is.

You can redefine the engage yourself like this:
layout [
	style my-field field feel [
		engage: func [face action event][
			..
		]
	]
]

that's basically what vid-field.r does. it takes the existing FIELD 
style and changes its FEEL object to contain more options for better 
text handling.

Anton's made a version that has undo/redo, right?

You can copy the code from the default engage function, but you will 
fall into a trap; some of the words used in the default engage handler 
are bound to specific contexts. Your code will bind all the words 
in your context or global context. I'm talking about the words focal-face 
(which is in system/view), unlight-text, highlight-start, highlight-end 
and edit-text (which are in ctx-text).

So you should bind your code first to system/view, then to ctx-text, 
before making the function:

style my-field field feel [
	engage: func [face action event] bind bind [

		; your code which uses focal-face, unlight-text etc...

	] system/view ctx-text
]

Ok, just found some mention of ctx-text in the docs.

Henrik, unlimited undo/redo.

probably a good idea to learn about bindings first to know what it 
means :-)

My edit-panel style is actually based on PANEL style, but pretty 
much supplants AREA, if you're happy with monospace font. (I haven't 
supported a single-line FIELD-like style, but could be easily done 
I expect.)

See the Editors group to try out the edit-panel style.

One other funcionality I'm missing is to be able to set the tab order 
! They won't always be the presented order.
And wether CR should act a sTAB or not.

Aha... the built-in tab-cycling system is simplistic. I made my own 
but it still goes in pane order.

whether CR can act as tab can be determined with a face flag.

Ok thanks, Tab order might be cobbled by enlosing field in two or 
more vertical panels. Sorry missed the flag for CR.

layout [f: field] probe f/flags ; == [field return tabbed on-unfocus 
input]
view layout [f: field with [deflag-face self return]]