Dave Watts wrote: > So if there's an organizational shuffle of roles, I'd have to rewrite > my XML schema? Because that sort of thing happens all the time, and a > rigid hierarchy simply won't be able to match that without frequent > changes.
I thought of that, which is why I suggested using something like level1, level2, and putting the actual title as a parameter. There are drawbacks to that approach, of course, as you and Steven pointed out. The thing that's missing, so far, is the structure--who reports to whom, whether it's a direct report or dotted-line, what the hierarchy is. You have to have that information to have a usable org chart. Steven is right--you shouldn't have to change your classes when your organization changes. The only way I see to do that is to include hierarchical information in the XML, and let your code handle the display. Cordially, Kerry Thompson _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
