[haXe] arctic

[Asger Ottar Alstrup]

> I really love enums, and I think they are great to quickly describe UI
> like you are doing in Arctic, but I think that you should only use them
> as shortcuts to create a class hierarchy. It's very important IMHO to be
> able to retrieve the actual classes instances created in the backround.
>

I can understand that it is useful to access the objects in some situations,
but Arctic is not supposed to do everything. Instead, Arctic is supposed to
be nice and small. If you want objects, use Flash Components, ASwing or
ActionScript.

Notice that the CustomBlock allows you to put anything you like into an
arctic GUI, including any of the above object-based systems.
When the Id stuff is done (hopefully Monday), I'll also add a way to get to
the raw MovieClip of each block. That means that you have an escape
mechanism to get the raw generated objects, so you are not left out should
Arctic not provide exactly what you need.

So, for now, I will proceed with the enum-only approach, and see how far
that takes us. It might be that objects will sneak in on us before we know
it, but so far, I think it looks as if we can keep them out for quite some
time.

Regards,
Asger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.motion-twin.com/pipermail/haxe/attachments/20061103/8f1cd2a1/attachment.htm