World: r3wp

But if you use HW to do anti-aliasing and filtering, things can look 
differently.

the coordinate systems don't have the same precision on all cards.

very basic settings
 = better use SW rendering? :-)

AFAIK 2D on openGL is just the fact of using a flat camera (orthogonal 
perspective) with a camera looking straight down.

what can happen is that between polygons, some edges will have seams 
on some cards and be very clean on other better cards

in an application I use, there is an artifact where the perspective 
of the camera offsets coordinates in the y of *some* polygons  .... 
very strange bug...

When using a Mac, you look at an OpenGL output. If you use the zoom 
function, there is a key combination to put anti-alias on/off. If 
it's off, you see the correct pixels, as there is in the drawing 
(bitmap). But you're right, if you put in anti-aliasing and other 
effects, it can look different on different hardware.

that sucks, no? :-) I thought that  standard is standard :-)

They should submit it to W3C :-)

very basic settings

  means no fancy shader stuff and simple texture use... like geomol 
  says, no filtering, no AA... but that also means blistering fast 
  gfx.

Who cares of blistering fast GFX apart from games, when you can't 
have the same anti-aliased font output on your form? :-)

some details like the coordinate precision and various occlusion 
optimisations, being done differently can affect the output... like 
if you superimpose two polygons with the exact coordinates... some 
cards will remove one of the polys... others (most) will cause pixels 
to shift from one poly to the other everytime you refresh... causing 
a very annoying shimering.

well, noting that all OGL antialising is about 2000 times prettier 
than AGG's  I don't mind  ;-)

It is? :-) I thought, AGG did a pretty good job.

but you won't be able to notice the difference in things like form.

http://www.antigrain.com/screenshots/compare_to_xara.gif

I've never seen a single font which didn't have at least a single 
letter which was grossely mis-AAed.  often its the s, the o, or the 
e..... they stick out in every word and its annoying.

it depends on the aa filter & sizeyou decide to chose.

Poor looking fonts in R3 are because the AA settings used in R3 are 
not correct. This requires intervention by Cyphre as those settings 
are not exposed in DRAW yet.

I took the image from: http://www.antigrain.com/screenshots/index.html

graphics are effectively very clean.

thin fonts really look bad in R2.

Anyway - good times ahead, once Host code is released ... the question 
is - when it is going to happen :-)

in any case, when you build a GUI with OGL, you build in such a way 
that everything scales, cause its sooo easy to do... its in fact 
free... like AGG.  so the fact that a GUI isn't exactly pixel perfect 
is secondary... since often you don't even have the same fonts on 
various OSes  ;-)

I prefere GUI to be pixel perfect.

That's also the reason why I'm not a fun of scalable GUIs.

And because "you don't even have the same fonts on various OSes", 
I like that in Flash you can embed own font glyphs.

And as Pekr mentioned Flash HW acceleration - it really sucks. In 
most cases you have to turn it off because it slows things down. 
You must design the app to be fine with HW, but nobody knows how. 
At least nobody is able to answer my questions on Adobe forums (and 
OSFlash as well).

true type and the ttf lib are pretty much on all OS nowadays... its 
just a question of having the right to distribute a font with your 
apps... which in theory is the same issue with flash I would guess.

on all
 should read "compiled for"

there is a big difference in how flash and AGG render their stuff.... 
it seems to me that AGG is actually more scalable in sheer quantity 
of strokes, whereas flash seems to be much better at handling textures 
and bigger screens... have you noticed the same reactions... having 
much more in depth knowledge of flash, I'm curious as to your observations....

The problem with TTF is, that in most cases the fonts are copyrighted, 
so zou cannot give them with the app. You can embed glyphs you need 
into Flash, but the the font is not TTF anymore so nobody can use 
it in other apps.

ah yess I see the nuance.  so font authors are wary of allowing re-distributable 
licenses?

I don't know AGG well so I'am not able to compare these. AGG can 
use same rasterization as Flash (which is more optimized for speed 
I guess). At least that's what Cyphre told me.

Cyphre has thought that we might switch to "compound rasterizer" 
of AGG, which would be more similar to Flash. But we might be slightly 
off-topic here :-)

I wish all those decisions where available to the programmers... 
often I have been bitten by these decisions in REBOL...  I plan to 
allow as much control to the Low-level stuff as possible with my 
OGL extension, even with the toolsets I'll build using it, I still 
want to allow the capacity to edit quality & quantity based-decisions, 
probably by providing a standard gfx setup requestor available to 
all applications of rogle.

this way developpers won't have to build their own, its going to 
be built-in and not require a "restart" of the application.

Q: anyone tried playing around with vector! datatype in extensions?

not yet ...

I haven't either

I may look at vectors in extension later to produce some sound streams, 
but have no time right now

for 3D they might be the perfect datasets for transformation matrixes 
and stuff like that...

Sound streams ... Rebolek - vectors are one thing, but sound subsystem 
is another one. Is there sound in R3 View at all?

Someone requested multi-dimension vectors or something like that 
some time ago. Is that already implemented? Would it be usefull?

with extensions we can possibly use other timers, precise timers, 
and include that in the C code.  so if you open the sound ports in 
the extension and do the timing there... it could work... but its 
blocking right now... no async... so no real way to mix sound with 
other events... until async extension model is shared.

Pekr no sound yet, but can be written using extensions probalby. 
I was thinking more in twerms of creating the soundstream for later 
use than actually playing it from R3 (at least right now, as a first 
step)

Max - this is interesting - I wonder where is the main event loop? 
Core dll, or Host code? I think host, so yes, it is replaceable. 
I still try to push Carl to switch to multimedia timers - would work 
much better.... I have good article on that, and Carl liked it.

yes I read the article...

in theory, you could replace the main loop if you want, if we have 
callbacks in extensions, the main loop can be handled from an extension. 
although its not like having it close to the core, where it can be 
smarter...


but if a callback can see if some events are waiting on a list of 
event ports (something like event: wait [ port 0] ), then we could 
use whatever timer/window events and fire from there....  the rogle 
extension includes GLut which already has its own (precise?) timer 
internally, but it can't trigger rebol code *yet*. so right now I 
have to handle all events in the C side :-(

Where's the event port? Core or Host?