Well a quick look at haxe at least proved that it's documentation is far
below the OL level.
Also currently I would have to build most of the gui components from
scratch.
(To be honest that's what I had to do with OL also :)
But what it did have was a good language reference (something OL is missing)
And api's clearly state on which target platform an object works.
I feel that OL should have a core api, objects that need a target
platform specific implementation.
These would be implemented with performance on the target platform in mind.
If you then develop components using this api, you would know that they
work on all supported platforms.
This api would be concise and conservative (obvious examples: view,
drawview, Timer (oops that's a camelcase :))
Then you could also have target platform api's if needed.
Say, laszlo components coded with as3
And like it already is, you could write code directly meant for one
target platform.
This would mean cleaning out all the non-crossplatform features from
core objects.
Eg. pixellock or clickregion from view (actually I only assume they are
flash specific)
These could then be brought back using mixins for those who target flash.
Now the components and OL core api are all mixed up.
This adds to confusion.
Basically my point is that instead of writing more backends, I would
like to see more clarity in the laszlo software stack.
And it is my firm belief that with this added clarity and documentation
OL would become more open.
And prosper better in the opensource community.
Because the biggest reason for not contributing is lack of understanding
and insecurity that rises from the previous.
This does not mean that I am opposed to any backend, of course.
- rami
6.2.2010 19:34, Raju Bitter kirjoitti:
Check out what the haXe folks did
Damn! I wasn't aware of this haxe at all.
Looks pretty good on paper.
Architecture has the kind of clarity I wished OL would have.
Has anyone done any comparisons between OL and haxe?
- rami
