This is for archetypes, I'm not sure if it is exactly the same for atct
but it probaly is:
put the template in your product skin and assign it as the default_view
and immediate_view in the class definition.
Another option is to do nothing in the class definition and, e.g., if
your portal_type is named MyPortalType create a template named
myportaltype_view.pt and inside that define the macros "body" and
"folderlisting" and archetypes will use those to show the body and the
folder listing of your object instead of the default ones.
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
<a href="http://ads.osdn.com/?ad_idv28&alloc_id845&op=click">http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________
Plone-Users mailing list
[hidden email] https://lists.sourceforge.net/lists/listinfo/plone-users
If you're really only talking about a view of a folder, the method
prescribed in that tutorial is probably the best idea, letting you use the
"display" menu to choose which folders have the contents' view. Note,
however, that such aggregation is a bit tricky, unless you also restrict
the types in the folder, as the above how-to does, since you don't know
how to display every content type (i.e. not every type has a "getText"
accessor to get the body text).
You can use a skin product (see DIYPloneSkin tutorial) and set up the new
template in the Install.py, meaning no ZMI interaction. Probably best
Alternatively, you can derive a content type from ATFolder (see
RichDocument tutorial) and set:
default_view = 'my_view'
suppl_views = ()
on the class, where my_view is the template. This will make this template
the view of the folder.