19 Apr
2007
19 Apr
'07
5:38 p.m.
I found the problem I got. My object MyNavigationWidget is child of
PRBoxWidget so according to the new design I had to add the both class
method: #defaultCssClass and #defaultCssName.
Maybe the PRBoxWidget should have dumb defaults for description or a
'shouldbeimplement'?
--
Martial Boniou
Lukas Renggli a écrit :
| > | > As a newbie in Magritte, I don't understand well how the new
| > widgets
| > | > work in Pier. For my personal web site I'm programming in Pier, I
| > | > created a PRBoxWidget instance to encapsulate other widgets.
| > |
| > | widgets are essentially just Seaside components, but instead of
| > | #renderContentOn: you override #renderWidgetOn:. They also provide a
| > | settings command so that administrators can configure them from the
| > | web. It is also possible to plug in any Seaside component, e.g. the
| > | Sushi Store, but these are not configurable from the web.
| >
| > I had understood this yet, so It is probably something else.
| > I tried to edit environment and add a '+tools+<br/>' to add my own
| > widget in pier. And when I click on the link to create a new
| > Component,
| > I get a DNU.
| >
| > I attached the debug message.
|
| I know this problem, it occurred to me a few hours ago as well and I
| fixed it, but did not commit yet. Pier-Seaside-lr.158 probably fixes
| your problem.
|
| Cheers,
| Lukas
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
|
|
| _______________________________________________
| SmallWiki, Magritte, Pier and Related Tools ...
| https://www.iam.unibe.ch/mailman/listinfo/smallwiki