On 08.12.2007, at 19:38, Reinout van Rees wrote:
Martin Aspeli wrote:
i'm also not sure how to treat static portlets conceptually. i.e.
as pages (that just 'happen to be displayed in a column') or as
non- content. this raises further questions, i.e. how to treat
their content when searching a site?
The way plone.portlet.static works (i.e. what I'd advocate for 3.1)
is that they have nothing to do with content at all. They are just
portlets that when edited give you a Kupu area to enter text. That
text is rendered inside the portlet column.
(/me isn't framework, so just a quick chip-in)
The static text portlet is great for adding buttons and what have
you to the sidebar. See http://vanrees.org : linked-in button,
hacker's diet.
So: no content, just "stuff".
yes, i agree. the usecase i had in mind can be satisfied with content
reference portlets in which case their content doesn't need to be
indexed, either, since their targets already are.
cheers,
tom
Reinout
--
Reinout van Rees - Programmer at http://zestsoftware.nl/
http://vanrees.org/weblog/ reinout @ vanrees.org
"Information overload isn't the problem. If it was, you'd
walk into a library and die." (David Allen)
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
