From: Roland, R. M <rmr...@in...> - 2003-06-23 21:23:56
|
I tried to send this a few days ago, but it didn't go through. So = here's attempt number 2. >> In fact, it looks like a single element can not >> only have multiple children, but possily multiple parents(?) >> [getParents()]. >No, they can only have one parent (although their parent may have a >parent). This is just a misleading function name. Perhaps getAncestors() and getDescendants() or something >> This leads me to suggest that maybe fatcat could have >> some predefined categories (Images, Links, etc), then a module can = create >> its own children of those >Interesting thought. We will talk more about this. Sounds good. Let me know what your thoughts are on this. >> In this setup, an important function would be the >> 'getAllElements(category)' >> One question about this. When returning elements belonging to a = category, >> do you return elements belonging to a parent of that cagtegory? = (Perhaps a >> parameter switch [getAllElements(category,returnParentElements)]). = This >> way if I want to add an image to a Pagemaster page, I get not only >> Image>Pagemaster elements, but generic Image elements as well. >Originally I was going to do this but it seemed like a lot of data that >not many people would use. We can look at allowing this through better >interface however. Thanks. As I said, maybe just an optional parameter that when supplied = returns the elements of parent categories as well. >PageMaster was written with our university users in mind. Because few = of >them know HTML, it was easier to split the material into sections to = make >its appearance more pleasing. What I would suggest is the option to = have >an expert mode. Excellent idea, just a change of interface and some small tweaks. I'd = be willing to work on this if I knew what Adam's plans are regarding his = rewrite. >> 4) Expand the size of the input window and allow a page to be a = single >> entity (ie no sections). >Not sure how Adam will wish to treat this. It would be nice however if = the >user could set their window size to increase the width of the text = area. Yeah, that'd be nice, but that's another option to have to save in the = DB, and there's currently no pagemaster_options table so that might not = be worth the difficulty. >> 6) When editing a page, clicking on the image button will bring up a = small >> window (similar to the help windows) with the 'Add Image' interface. >> Perhaps a button "Add Internal Image" and "Add External Image". >Possible, but would require some javascript programming (which I am not >great at). Also there would need to be an alternate interface for those >who don't run javascript. I agree. Man I hate Javascript ... or more accurately, its splintered = support and yet growing importance and use. >> 8) The uploading of the images could be handled by the document = manager. >Depending on the module, that could be kind of a pain switching in and = out >of modules. Let me get back to you on that. Thanks again for the feedback, Ryan Roland Application Developer Information Technology Department Division of Recreational Sports Indiana University rmr...@in... Office: 812.855.9617 Cell: 812.320.0032 Thanks, Ryan Roland Application Developer Information Technology Department Division of Recreational Sports Indiana University rmr...@in... Office: 812.855.9617 Cell: 812.320.0032 |