alwaysBuffer not set...
Wouter
wouter.abraham at pi.be
Wed Jul 21 02:59:25 EDT 2004
> alwaysBuffer not set...
> Richard Gaskin ambassador at fourthworld.com
> Tue Jul 20 16:13:47 EDT 2004
>
> * Previous message: alwaysBuffer not set...
> * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
> Wouter wrote:
--big snip
> > If this is at engine level then the engine itself is making a
> difference
> > between the MC IDE and the RR IDE. And this could cause slippy-ness.
> > Also implicating separated or singlesided engine improvement. ???
>
> No, you can verify this by using the same engine in both environments.
> Any differences between the two are specific to the IDEs.
That is exactly what I did.
And because of this difference I supposed the templates (where the
default alwaysBuffer of the templateStack is lodged) were not hidden in
the engine itself. And this made me wonder why you called this <the
opportunity to improve *the engine itself*>
So I seem not to be grasping the point.
I look at MC and RR as stacks interacting with an engine (and from a
low level point of view :-).
But because of things said on the lists the impression is growing that
what is called the engine, is something composed of stacks and the
engine. Where are the borders between the IDE, stacks and the engine?
-- snip
> I'm not sure any Rev behaviors are undocumented. You'd have the check
> the Rev docs. My role here is just to support the MC IDE maintenance
> and development, honoring the community's preference that its value as
> a
> closer-to-the-engine alternative be maintained.
And you are doing a great job.
(and I still prefer MC over RR)
>
> --
> Richard Gaskin
> Fourth World Media Corporation
Greetings,
Wouter
More information about the metacard
mailing list