Re: Unified libraries to allow porting code to other oses
- Posted by jmduro May 25, 2015
- 2598 views
This second way seems promising. I have just one hesitation about some object characteristics. Objects are sometimes identified as id, as {parent, id} (as a widget in another modal window) or as {id, section} (as a panel in the status bar).
Should this additional identification stay in the identification id (atom or sequence) or should it be extracted as a parameter?
I answer my own question:
- id (atom) or {parent, id} (sequence) reference an object
- {id, section} (sequence) doest not reference an object but some part of it (as a panel in a statusbar for example)
So in the syntax of setProperty(object id, sequence Property, object Value), section should not be part of id. But it is neither a property or a value, it remains an extra identification value. Any advice on how to include it in the syntax of the setProperty function?
May be this way: setProperty(object id, object section=0, sequence Property="", object Value=0)
This would permit to use setProperty even with a grid to put text in a cell:
- setProperty(grid, {row, col}, "text", "Cell")
- setProperty(statusbar, panel, "text", "Ready")
- setProperty(button, 0, "text", "Ok")
I don't like this section parameter in second position. May be at the last position would be better.
Regards
Jean-Marc
