From: David H. <pro...@ma...> - 2010-07-22 21:24:39
|
Thanks for your reply Dave, On 22-Jul-10, at 2:01 PM, David Avendasora wrote: > In a similar vein, I've thrown around the idea of using a Velocity > EOGenerator template to generate a .d2wmodel file for each entity, > where you could put the basic info (componentName, > displayNameForProperty, formatter, etc) in the user dictionaries. > If it worked well enough I could see having a D2W tab in Properties > area. Looks like we're definitely thinking in a similar direction. See my previous message. > > I mentioned this to David LeBer once. If I remember correctly he > didn't care much for the idea because then you are maintaining some > rules in the EOModel and some in the normal .d2wmodel files, which > could make the development workflow more complicated, or at least > less transparent. David's point probably makes sense. I don't have enough experience with D2W to know if that would fall down in practice or not. Certainly puts a little of the M and V in the same place in the case of my labels in the userInfo idea. I have also been tossing around the idea of default rule files for each Entity in my logic framework. Not sure if this makes sense or not. At the moment I am using the velocity generated stuff to document what I then put into place in the rules. This is somewhat more transparent than not creating the Entity worksheet at all. As I said, I am using the worksheet to help me communicate what is possible to the client. It also helps to have a reference to the specific attribute names etc when you are writing rules. I guess if you could create both the documentation and the rules automatically from different templates, you may not need to worry about its transparency. Incidentally I am now creating both the normal ModelDoc and the "RuleModelDoc" in the same project and folder with no issues. > > I still think it might be a good idea, but I have not yet even > tested to see if it is a workable concept or not. Let me know if I can help. I am so looking forward to WOWODC to discuss these issues face to face for a change! Thanks again, d > > Dave > > > On Jul 22, 2010, at 2:35 PM, David Holt wrote: > >> Hi all, >> >> In an effort to document the design of a D2W application, I have >> come up with a couple of ideas that I think might be useful to the >> community. >> >> Using the EOModelDoc.jar, I have created a new template based on >> Chuck's work that lists an entity's Attributes and Relationships. >> The template currently spits out text formatted so that I can cut >> and paste the output directly into OmniOutliner. The output page >> also has place holders for putting in "Task" information and >> listing the "displayPropertyKeys" for that entity. My idea is that >> you can work with the users to decide which attributes and >> relationships need to be displayed for a given pageConfiguration. >> It might help them visualize what the final result might look >> like. At the very least you will be able to keep track of what >> rules you need to write for a given entity/task combination. >> >> Screenshots from ERMoviesLogic / ERModernMoviesDemo will make it >> more obvious. >> >> This is the EOModelDoc generated Entity page: >> >> <Movie template.jpg> >> >> Which you can then cut and paste into an OmniOutliner document and >> use it as a template for multiple Tasks and/or pageConfigurations >> for this entity: >> >> <Movie Select.jpg> >> >> >> >> And then you can create the corresponding Rules for that Entity >> and Tasks: >> >> <Movie Query.jpg> >> <Movie Display Property Keys Rules.jpg> >> >> Would anyone else find this helpful? If so, do you have any ideas >> for how this workflow could be made more useful to you? >> >> Thanks, >> >> David---------------------------------------------------------------- >> -------------- >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com- >> first_______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > |