I want to be able to create content and then attach sub-content to it. For example, if tasks were the content, it would look like the following: go shopping get bananas get bread pick up cleaning get shirt get pants clean house clean kitchen clean mixer clean clean sink clean bedroom I don't want to have the overhead of creating and sifting through folders as you navigate the hierarchy. In order to do this, I need the ability to have content that has folderish properties allowing sub content. Is there a product out there that has similar characteristics? If I were to build this, what tools within plone would I use?
+-------[ Greg Gehrich ]---------------------- | I want to be able to create content and then attach sub-content to it. | For example, if tasks were the content, it would look like the following: | | go shopping | get bananas | get bread | pick up cleaning | get shirt | get pants | clean house | clean kitchen | clean mixer | clean clean sink | clean bedroom | | I don't want to have the overhead of creating and sifting through | folders as you navigate the hierarchy. In order to do this, I need the | ability to have content that has folderish properties allowing sub content. You could set a property on your item that points to the sub-items. If the list is ordered, you'd need to obviously also add some ordering information. Or subclass an existing document type and add the same type of thing. -- Andrew Milton akm@theinternet.com.au
Is anyone aware of a UI that displays their content as nested within Zope? Andrew Milton wrote:
+-------[ Greg Gehrich ]---------------------- | I want to be able to create content and then attach sub-content to it. | For example, if tasks were the content, it would look like the following: | | go shopping | get bananas | get bread | pick up cleaning | get shirt | get pants | clean house | clean kitchen | clean mixer | clean clean sink | clean bedroom | | I don't want to have the overhead of creating and sifting through | folders as you navigate the hierarchy. In order to do this, I need the | ability to have content that has folderish properties allowing sub content.
You could set a property on your item that points to the sub-items. If the list is ordered, you'd need to obviously also add some ordering information.
Or subclass an existing document type and add the same type of thing.
There is a product called ZopeTree google for it robert Gregory Gehrich wrote:
Is anyone aware of a UI that displays their content as nested within Zope?
Andrew Milton wrote:
+-------[ Greg Gehrich ]---------------------- | I want to be able to create content and then attach sub-content to it. | For example, if tasks were the content, it would look like the following: | | go shopping | get bananas | get bread | pick up cleaning | get shirt | get pants | clean house | clean kitchen | clean mixer | clean clean sink | clean bedroom | | I don't want to have the overhead of creating and sifting through | folders as you navigate the hierarchy. In order to do this, I need the | ability to have content that has folderish properties allowing sub content.
You could set a property on your item that points to the sub-items. If the list is ordered, you'd need to obviously also add some ordering information.
Or subclass an existing document type and add the same type of thing.
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Greg Gehrich wrote:
I want to be able to create content and then attach sub-content to it. For example, if tasks were the content, it would look like the following:
go shopping get bananas get bread pick up cleaning get shirt get pants clean house clean kitchen clean mixer clean clean sink clean bedroom
I don't want to have the overhead of creating and sifting through folders as you navigate the hierarchy. In order to do this, I need the ability to have content that has folderish properties allowing sub content.
What overhead is this? I'd do this as nested ordered folders and use the ZMI to manage it all, unless there are other hidden requirements here... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
The overhead the user has to incur to create subtasks. If folders are used to create the hierarchy, the user must first create a folder to hold the subtasks for "Pick up cleaning" and then enter the two subtasks. I'd rather just directly create a subtask because that eliminates the step to create a folder. Viewing will also be cleaner because you never the a folder obscuring the subtasks. Chris Withers wrote:
Greg Gehrich wrote:
I want to be able to create content and then attach sub-content to it. For example, if tasks were the content, it would look like the following:
go shopping get bananas get bread pick up cleaning get shirt get pants clean house clean kitchen clean mixer clean clean sink clean bedroom
I don't want to have the overhead of creating and sifting through folders as you navigate the hierarchy. In order to do this, I need the ability to have content that has folderish properties allowing sub content.
What overhead is this?
I'd do this as nested ordered folders and use the ZMI to manage it all, unless there are other hidden requirements here...
Chris
Greg Gehrich wrote:
I want to be able to create content and then attach sub-content to it. For example, if tasks were the content, it would look like the following:
go shopping get bananas get bread pick up cleaning get shirt get pants clean house clean kitchen clean mixer clean clean sink clean bedroom
I don't want to have the overhead of creating and sifting through folders as you navigate the hierarchy. In order to do this, I need the ability to have content that has folderish properties allowing sub content.
What overhead is this?
I'd do this as nested ordered folders and use the ZMI to manage it all, unless there are other hidden requirements here...
Chris
I'm also not clear about what you want to do. Are you talking about creating content or viewing it? Or both? I *think* what you are talking about is what is called 'mixed content elements' in XML: an element can contain both text and other elements. If so, this is handled seamlessly in xml/sgml editors (Epic, FrameMaker, maybe Openoffice) and tools associated with them for creating web content, but there are no straightforward ways of dealing with this in Zope. Plone's default folders (still folders) are mixed-content elements. The Archetypes product for CMF/Plone works, but is ridiculously complex and buggy. The Silva content management framework may be what you want, but you have to want what Silva delivers. XMLparser is a proof of concept, not a usable tool. To deal with this type of content effectively you may need to look elsewhere - check out the Apache Lenya and Forrest projects for example, or the tools building up around IBM's DITA. Or you'll need a Zope expert (Chris, for example) to build it for you to meet your particular needs. In theory, Zope should be great for creating task-focused online documents. In practice it can be great at rendering them, but there are no useful open-source tools to move content from productive authoring/editing environments (Epic/FrameMaker with docBook or DITA XML schemas/DTDs) into the Zope 'publishing' environment. Unless you guys know different... -- Mark Barratt Text Matters Information design: we help explain things using language | design | systems | process improvement ______________________________________________________ phone +44 (0)118 986 8313 email markb@textmatters.com web http://www.textmatters.com
Greg Gehrich wrote:
The overhead the user has to incur to create subtasks.
What overhead is this?
If folders are used to create the hierarchy, the user must first create a folder to hold the subtasks for "Pick up cleaning" and then enter the two subtasks.
How would they do it otherwise?
I'd rather just directly create a subtask because that eliminates the step to create a folder.
Well, if they directly create a subtask, where do they put it?
Viewing will also be cleaner because you never the a folder obscuring the subtasks.
How does a folder obscure the subtask? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
What I would like is something more like the newsreader I use now (Thunderbird). Users create items in a nested hierarchy without having to create folders to store subitems. I can view the hierarchy and decide where I want to jump in and open up the detail or easily add detail at the appropriate nesting level (through a reply). Chris Withers wrote:
Greg Gehrich wrote:
The overhead the user has to incur to create subtasks.
What overhead is this?
If folders are used to create the hierarchy, the user must first create a folder to hold the subtasks for "Pick up cleaning" and then enter the two subtasks.
How would they do it otherwise?
I'd rather just directly create a subtask because that eliminates the step to create a folder.
Well, if they directly create a subtask, where do they put it?
Viewing will also be cleaner because you never the a folder obscuring the subtasks.
How does a folder obscure the subtask?
Chris
Greg Gehrich wrote:
What I would like is something more like the newsreader I use now (Thunderbird). Users create items in a nested hierarchy without having to create folders to store subitems. I can view the hierarchy and decide where I want to jump in and open up the detail or easily add detail at the appropriate nesting level (through a reply).
Create a folder-like type that implements your task item, and can contain other task items. The users will never know that the task item is really a folder: why should they care? Create a view that displays a tree of your items. You have exactly what you want. PJDM -- Peter Mayne Spherion Technology Solutions Canberra, ACT, Australia "Learning to cry for fun and profit" - Sisters of Mercy
Greg Gehrich wrote:
What I would like is something more like the newsreader I use now (Thunderbird). Users create items in a nested hierarchy without having to create folders to store subitems. I can view the hierarchy and decide where I want to jump in and open up the detail or easily add detail at the appropriate nesting level (through a reply).
I don't see anything in what you've said that makes using Zope Folder objects as you items, storing info using Properties. It seems you're arguing about UI, so build the UI you want :-) Or, if you've got budget, pay someone else t obuild it for you! cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (8)
-
Andrew Milton -
Chris Withers -
Dieter Maurer -
Greg Gehrich -
Gregory Gehrich
-
Mark Barratt -
Peter Mayne -
robert