Look at my LzCursor implementation I sent out for review. We need to
figure out how to enforce singleton-ness, but it is a pattern for
creating a class whose implementation is down in the kernel (and not
necessarily a class).
On Mar 23, 2008, at 17:54, "Henry Minsky" <[EMAIL PROTECTED]>
wrote:
You mean having a separate sprite-like runtime-specific class or
object that LzModeManager would refer to?
On Sun, Mar 23, 2008 at 5:35 PM, Max Carlson <[EMAIL PROTECTED]>
wrote:
I'd recommend making the platform-specific bits part of the kernel
APIs,
using the pattern we have now for views. It would be good to merge
the existing platform/runtime/... bits into the kernel also...
Henry Minsky wrote:
>
>
>
> I guess in order to make platform-specific extensions in
separate
> files, I ought to make a base abstract subclass, and then
> have each runtime declare the actual LzModeManager class in its
> platform/runtime/... directory ?
>
>
> I mean make an abstract base class, like LzModeManagerBase, and then
> have the platform-specific subclasses actually
> define lzModeManager in the various platform/runtime/...
directories.. .
>
>
>
> --
> Henry Minsky
> Software Architect
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>
>
>
> --
> Henry Minsky
> Software Architect
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
--
Regards,
Max Carlson
OpenLaszlo.org
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
