12 Feb
2010
12 Feb
'10
1:38 p.m.
I had a look at PRValueLink and indeed this could be a better starting point to implement
what I want. And it is the first time I saw how pragmas are used and what they are good
for. It is something like pool dictionaries I'm always ignoring.
I have problems understanding the rationale behind the usage of pragmas here. PRLink
parses to instances of subclasses that are valid references for the string inside the link
(PRValueLink for "value"). Why does PRValueLink not the same? Everything after
value: could look up subclasses of PRValueLink that deal with the specified behaviour, no?
So I could subclass the PRValueLink instead of putting extensions on it that use pragmas.
Somehow I don't get it. But probably I'm just missing something important.
thanks in advance,
Norbert
On 12.02.2010, at 11:03, Lukas Renggli wrote:
Well, there is
state because I'm after forms.
I guess you could still look after value links, together with a
component that is partially rendered using this technique.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki