Quirino Zagarese wrote:
Thank you very much Max :-)
Sure!
p.s. I kept on making tests on the visual IDE, but there are some issues that stopped me. You use lzx code as a dataset, but that way, when I click on an element to edit it, I only get a reference to the attributes which are specified in the code, not all the ones available for that component. Do you think there's a way to go over this limit while keeping the lzx-dataset approach?
Yes, that's a limitation. I like the dataset approach because it works on the actual source of the file. We'll need some way to read the available attributes (and methods) from the class. This is trickier than it sounds, because some of these may be inherited - also it's difficult to tell the difference between a regular property and a method at runtime.
Ideally, classes could expose public methods and attributes explicitly - with a priority so the 'important' once appear higher in the list. This would require some compiler work...
For now, it might be best to expose everything that's available on the class at runtime.
-- Regards, Max Carlson OpenLaszlo.org
