16 Apr
2006
16 Apr
'06
10:32 a.m.
Ok, doesn't seem to work, but let me explain what
I'm doing. I'm
writing a component meant to be hosted in Pier, the component has
several settings it needs, and I was using class side descriptions to
provide the "settings" interface that Pier offers on any component.
Yes, this is the usual procedure.
However, looking at PRSettingsComponent, I see that
it's not asking
the
instance for it's description, it's asking the class directly,
bypassing
any overrides I may have attempted on the instance side. Is that the
intention?
Oups, this seems to be a bug. I fixed it and will publish my changes
as soon as I have a propre internet connectionn again.
Am I writing components wrong? Should I be
subclassing
something in Pier rather than my own WAComponent subclass?
No nothing wrong from your side. You could also subclass PRStructure
(as the model) and define the settings on there (to make editing
work). Then you could also define views and other commands.
The Magritte tutorial is great btw, is there something
similar for
Pier?
No, not yet, only the SmallWiki paper from WikiSymposium that is
still valid for a big part (minus the name).
Now that Pier seems somewhat stable, I'm starting
to explore it more
as an application container with configurable widgets, digging it so
far, just need to get a few things done so I grok the do's and
dont's a
little better. Great work though, keep it up!
Thanks a lot!
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch