Am 2013-04-15 08:12, schrieb Renk Thorsten:
>> Using getprop on the one hand does not allow getting a property
>> converted to a given type and on the other hand is tedious to use
>> for more than one property, as one has to assemble the according
>> property paths (which is definitely less effici
> If you just want a quick and dirty way to read one property, we have
> getprop / setprop - for any other use, you should be doing what the API
> already supported; getting a props.Node object for the leaf, and then
> manipulating it with no further string/path handling.
> Using getprop on
Am 2013-04-14 14:30, schrieb James Turner:
>> Extend Nasal property methods to support relative paths.
>>
>> All methods exposed to the Nasal props module now accept an
>> optional first parameter refering to another node by a relative
>> path.
>
> I'm a bit torn on this change; making APIs mor
3 matches
Mail list logo
