World: r3wp

a letter on the screen. Should it be accessible as a gob? Having 
a size, offset, color, etc...

It's probably a stupid idea, but I remember that gobs were intended 
to be used in the thousands on the screen for games and the like.

that depends on what you need it for. in principle you can treat 
a single letter as a gob, by having one char in the text body.

that's true

You mean rendered text characters.

I don't think it's a stupid idea.

Yes, but rendered text cannot be edited.

useful if you need chars flying around the screen, or special typography, 
but rich text should be otherwise able to handle most other cases.

With supporting code, it can, of course it can.

I've been told that it's really hard to create such code.

I'm just thinking that if an application such as ms word is to be 
created then rendered text needs to be edited.

Well, it's not easy, of course, to make an editing system with all 
the features we've come to expect.

Would a character per gob simplify things?

are we talking R2 now?

r2 doesn't have gobs

in R3 that will be part of rich text. due to "bugs" in the rich text 
system, you can in fact already edit rich text in R3, you can just 
not yet move the caret between or select across multiple styles.

only with a single gob, though. if you really need to edit across 
multiple gobs, I don't see why the gob text bodies can't be chained 
together somehow.

Selecting across multiple styles. That's the kicker, isn't it.

In fact, I don't even know how selection works. Is it mezzanine?

It would be a draw block wouldn't it?

One char per gob: that is simple, but maybe you can increase rendering 
speed by creating one gob per section of text which has a consistent 
font-size and style etc.

text behavior is mezzanine

Is it in ctx-text?

It depends on how hard / possible it is to get individual character 
size & position information from gob text strings.

it's in the guie context.

or maybe not... it's mentioned in the text-* files anyway.

the text-* files?

don't you have the R3 GUI source code?

agg_truetype_text.cpp ??

.cpp files are obviously C++ files, not rebol mezzanine code.

rich text editing will probably not be handled at the AGG level.

This is cute.

I control-c'd a bit of rebol source from a web page ... which I wanted 
to edit before I pasted it into the console

Normally I would open up the rebol editor, and paste code into it, 
save it to a disk file and then run it.  And wondering why I always 
need rebol [ ] in the header ...

It just occurred to me ... can i just do this

editor clipboard://

and yes, it works!  I save the file after modification, close the 
editor, and then control-v to paste my code directly into the console 
... no more intermediate files saved!

so saving writes the changes back to the clipboard:// device

of course, do clipboard:// also works without screwing up the console 
history

With R3 you can do clipboard:// even if the code doesn't have a header 
:)

But that editor clipboard:// trick is really cool.

Indeed. I have clipboard shortcuts, but not that one.

Yeah, works for me too on linux. Very good.

btw, I'm working on getting this kind of collision detection code 
working under REBOL  :-) 


in fact, I also want to support rotated shapes, which makes it quite 
a bit more complex to handle generically, but I've done enough research 
on the subject to have a good feel on how to get it to work.


I'm hashing out all the maths to do it, and will integrate this into 
my little game engine.

http://www.metanetsoftware.com/technique/diagrams/tutA_demo.html

I'd also really like to get some easy to use Veronoy region code 
implemented for use in REBOL, they can be quite usefull to simplify 
very advanced search algorythms and graphics apps.

typo... not  Veronoy... Veronoi

Voronoi

yeah... was late (early) for me

I think I just found an interesting way to optimise AGG on R2  :-D 


I'm doing Animation tests with some complex vector & projection math 
(rotating/translating/projecting shapes using floating point math 
exclusively).


using AGG and a non-standard manual management of the window, I'm 
acheiving 0% CPU at 30fps FULL SCREEN (1440x900)

on a crappy 1.5GHz core2 duo.