One thing to be careful of is that making LzNode derive from LzDataElement would impose more restrictions on our ability to optimize LzDataElement by decorating the native XML data element types.
Another way to get (almost) the same effect would be to adopt Oliver's DOM APIs for LzNode -- the ones in incubator/domapi.js. Not sure how this resonates with DHTML, though... One way to resolve the cheasyMultipleInheritance problem would be to create a trait that implements the parts of LzNode that LzDataset wants, and have both LzNode and LzDataset derive from that trait. On May 18, 2006, at 12:50 PM, P T Withington wrote: > This has been proposed several times. I think one fear is that it > adds yet more weight to LzNode. But both Jim and Adam have > discussed it in the past. Perhaps now is the time to bite the > bullet. Or, perhaps we make LzDataElement a trait? > > On 2006-05-18, at 14:03 EDT, Henry Minsky wrote: > >> Or rather, maybe LzNode should inherit from LzDataElement? >> >> >> >> On 5/18/06, Henry Minsky <[EMAIL PROTECTED]> wrote: >>> >>> >>> What would be wrong with just having LzDataset inherit from >>> LzDataElement? >>> >>> >>> >>> >>> -- >>> Henry Minsky >>> Software Architect >>> [EMAIL PROTECTED] >>> >>> >> >> >> -- >> Henry Minsky >> Software Architect >> [EMAIL PROTECTED] >> _______________________________________________ >> Laszlo-dev mailing list >> [email protected] >> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
