I think those are there so DHTML apps wouldn't autoinclude a bunch of
code that fails when someone accidentally includes one of those
components. Instead of some mysterious runtime error, the class won't
be included - making for a much more straightforward debugging experience.
It seems like what we really want is to be able to signal a compiler
error when trying to include one of these components in DHTML...
Failing that, we could eliminate the condition in the components and ask
developers to put conditions in their own apps when they want
cross-runtime support. We will likely need to add if ($dhtml) { warn }
else { ... } clauses to most methods.
P T Withington wrote:
[exec] extensions/av/mediastream.lzx:13:9: Compile may fail due to conditional
class definitions in <switch>
[exec] extensions/av/rtmpconnection.lzx:12:11: Compile may fail due to
conditional class definitions in <switch>
[exec] extensions/av/videoview.lzx:13:9: Compile may fail due to conditional
class definitions in <switch>
--
Regards,
Max Carlson
OpenLaszlo.org
