And I'm looking for ideas for how I can make this as simple as possible for the content editors.
The best I can come up with so far is to have a rich text box and rely on the user to enter bullet lists, and then indent the list for parents and again for grand parents.One problem with this approach is that the CSS styling needs the LI text to be wrapped in DIV's which creates an extra step for the editors.
However I think a table is more appropriate for this solution than a CSS/UL type solution but I'm trying to think of a simple way for the editors to enter this data.
I would have to agree with Rich's idea here. While it may take longer for the initial data entry, I think you'll find that this appraoch will be endlessly more flexible down the road. What if you want to display portions of a particular pedigree tree? Will you have to duplicate portions of a given existing tree to do that? What if you want to perform a search on names? You can be much more "choosey" if you made each pedigree a node and utilize the already existing paret/child grandparent/parent structure that XML provides. If you are mostly worried about the output of this from a programatic standpoint, let us know and perhaps we can help.
Rich solution is fine, but if you have lot's of data it can lead to duplication - same dogs have similar parents ...
You can try solution where all dogs some to ine folder and you setup contentpicker to his parents. Then you can generate tree recursion in xslt, and have not duplicate entry. But solution is depend on your needs...
Thanks for the ideas. The tree is for trophy stags and will only feature the best animals so we don't want to keep a full tree (thousands of deer) - this is handled in other specialised farm software.
I've experimented with adding an HTML tree template to the rich text area. I'll take this idea and Rich's to the client and see if they have a preference.
Any ideas for pedigree tree?
Hi,
I'm attempting to create a Pedigree tree i.e. something similar to:
http://fu2k.org/alex/css/cssjunk/pedigree/PedigreeList
And I'm looking for ideas for how I can make this as simple as possible for the content editors.
The best I can come up with so far is to have a rich text box and rely on the user to enter bullet lists, and then indent the list for parents and again for grand parents.One problem with this approach is that the CSS styling needs the LI text to be wrapped in DIV's which creates an extra step for the editors.
However I think a table is more appropriate for this solution than a CSS/UL type solution but I'm trying to think of a simple way for the editors to enter this data.
Any ideas?
Thanks
Paul
Why not have a separate nodes with doc type of 'Name'?
Name
-Name
-Name
-Name
-Name
-Name
-Name
Name
-Name
-Name
-Name
-Name
-Name
-Name
Rich
Hi Rich,
Thanks for the suggestion. My preference was to have it all contained within one node purely from a data entry point of view.
The information is mostly hand-written at the moment so there is going to be quite a lot of data-entry.
Paul
Hi Paul,
I would have to agree with Rich's idea here. While it may take longer for the initial data entry, I think you'll find that this appraoch will be endlessly more flexible down the road. What if you want to display portions of a particular pedigree tree? Will you have to duplicate portions of a given existing tree to do that? What if you want to perform a search on names? You can be much more "choosey" if you made each pedigree a node and utilize the already existing paret/child grandparent/parent structure that XML provides. If you are mostly worried about the output of this from a programatic standpoint, let us know and perhaps we can help.
Thanks,
Nik
Rich solution is fine, but if you have lot's of data it can lead to duplication - same dogs have similar parents ...
You can try solution where all dogs some to ine folder and you setup contentpicker to his parents. Then you can generate tree recursion in xslt, and have not duplicate entry. But solution is depend on your needs...
Petr
Hi,
Thanks for the ideas. The tree is for trophy stags and will only feature the best animals so we don't want to keep a full tree (thousands of deer) - this is handled in other specialised farm software.
I've experimented with adding an HTML tree template to the rich text area. I'll take this idea and Rich's to the client and see if they have a preference.
Thanks
Paul
is working on a reply...