On Dec 2, 2009, at 7:19 AM, Mike Schrag wrote:
> i have never found digram views of database to be useful ... every
> time i see a "real" database diagram, it's always a jumbled mess.
That has been my experience too. If the database is complex enough to
need a diagram, it is too complex for a diagram.
> I prefer just navigating the eomodels in entity modeler.
EOModelDoc can also produce some useful views in HTML where you can
see more at once.
Chuck
>
> On Dec 2, 2009, at 10:12 AM, Robert Huber..7r wrote:
>
>> Hi Anjo
>>
>> Thanks for the idea, but I think it's not very realistic for me.
>> But how do developers live without a diagram view, I am really
>> wondering.
>>
>> Best regards, Robert
>>
>> On 02.12.2009, at 15:57, Anjo Krank wrote:
>>
>>> You could write a simple EOModel->GraphViz WOApp. Shouldn't be too
>>> hard and it spares you the layout problem. Make a page where you
>>> can select the entities in question or whatever.
>>>
>>> This one for example looks mostly like an ER diagram:
>>>
>>> http://www.graphviz.org/Gallery/directed/datastruct.html
>>>
>>> Cheers, Anjo
>>>
>>> Am 02.12.2009 um 15:50 schrieb David Avendasora:
>>>
>>>> Hmm.
>>>>
>>>> You are right. Unfortunately I don't see a diagram view being
>>>> added to Entity Modeler, unless you write it, or pay someone to.
>>>> You could always contact Omni and see if there is a way to get at
>>>> the parsing rules that OmniGraffle uses so you could modify them
>>>> to do what you want.
>>>>
>>>> Dave
>>>>
>>>> On Dec 2, 2009, at 9:40 AM, Robert Huber..7r wrote:
>>>>
>>>>> Dave
>>>>>
>>>>> Thanks for the tip, I don't see the OmniGraffle the right tool
>>>>> for the job. The diagram is not very readable, as for example
>>>>> there is no clear separation between the attributes and
>>>>> realtionship names, the relationship names are not drawn on the
>>>>> relationship as in EOModeler, and no info about the attribute
>>>>> itself in the diagram, just the name, in general, it's a
>>>>> shrinked down display of what EOModeler offers. I mean, it's at
>>>>> least something, but in my opinion not really a replacement for
>>>>> the missing diagram view, and of course, completely out of the
>>>>> Entity Modeler's context.
>>>>>
>>>>> Thanks and best regards, Robert
>>>>>
>>>>>
>>>>>
>>>>> On 02.12.2009, at 15:18, David Avendasora wrote:
>>>>>
>>>>>> OmniGraffle (http://www.omnigroup.com/applications/
>>>>>> omnigraffle/) will do it. Just open the .eomodled file with it
>>>>>> and it will automatically turn it into a diagram. Sweeeeeeeet.
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>>
>>>>>> On Dec 2, 2009, at 9:08 AM, Robert Huber..7r wrote:
>>>>>>
>>>>>>> Hi All
>>>>>>>
>>>>>>> I am using the Entity Modeler (in Eclipse) for the design of
>>>>>>> the database part of our projects. As we absolutely need to
>>>>>>> print out in diagram view the entity model, we keep a Mac with
>>>>>>> Mac OS X 10.4 and the EOModeler, just to (open and) print the
>>>>>>> diagram.
>>>>>>> Now I made in the Entity Modeler 2 subclasses from an entity
>>>>>>> (with the menu Subclass Entity) and as a consequence, can't
>>>>>>> open the model in the EOModeler any more. I checked everything
>>>>>>> to make sure there is no error somewhere and think everything
>>>>>>> is ok, but I get the error message:
>>>>>>>
>>>>>>> Alert
>>>>>>>
>>>>>>> An error occurred while opening "/Users/robert/Desktop/
>>>>>>> Hades.eomodeld".
>>>>>>>
>>>>>>> Exception: NSInvalidArgumentException
>>>>>>> Reason: Unable to read /Users/robert/Desktop/Hades.eomodeld/
>>>>>>> index.eomodeld
>>>>>>>
>>>>>>> I really hope this can be corrected, so we still can open the
>>>>>>> model in the EOModeler.
>>>>>>> Can anyone from the WOLips team comment please, when there
>>>>>>> will be a diagram view in Entity Modeler available? I very
>>>>>>> very much hope there will be one some time, as we have no idea
>>>>>>> how to discuss and review the model without a printout on
>>>>>>> paper (ca. 2 x 3 meter in size for the big models). It's the
>>>>>>> only view which allows to verify the model (some of them with
>>>>>>> more than 100 entities) in a team of developers.
>>>>>>> How are others handling this situation? I would love to know?
>>>>>>> Of course we would love to abandon the EOModeler, but we can't
>>>>>>> because of the reason described above.
>>>>>>>
>>>>>>> Thansk and best regards, Robert
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _/ _/ _/ _/ _/ r. huber
>>>>>>> _/
>>>>>>> _/ _/ _/ 7r gmbh
>>>>>>> _/ _/ _/ alpenstrasse 93
>>>>>>> _/ _// ch-8200 schaffhausen
>>>>>>> _/ _/
>>>>>>> _/ _/ tel. +41 52 624 81 15 www.seven-r.ch
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> David Avendasora
>>>>>> Senior Software Engineer
>>>>>> K12, Inc.
>>>>>>
>>>>>> *****
>>>>>> WebObjects Documentation Wiki : http://wiki.objectstyle.org/confluence/display/WO/
>>>>>> *****
>>>>>> WebObjects API: http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/index.html
>>>>>> *****
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _/ _/ _/ _/ _/ r. huber
>>>>> _/
>>>>> _/ _/ _/ 7r gmbh
>>>>> _/ _/ _/ alpenstrasse 93
>>>>> _/ _// ch-8200 schaffhausen
>>>>> _/ _/
>>>>> _/ _/ tel. +41 52 624 81 15 www.seven-r.ch
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> David Avendasora
>>>> Senior Software Engineer
>>>> K12, Inc.
>>>>
>>>> *****
>>>> WebObjects Documentation Wiki : http://wiki.objectstyle.org/confluence/display/WO/
>>>> *****
>>>> WebObjects API: http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/index.html
>>>> *****
>>>>
>>>
>>>
>>
>>
>>
>> _/ _/ _/ _/ _/ r. huber
>> _/
>> _/ _/ _/ 7r gmbh
>> _/ _/ _/ alpenstrasse 93
>> _/ _// ch-8200 schaffhausen
>> _/ _/
>> _/ _/ tel. +41 52 624 81 15 www.seven-r.ch
>>
>>
>>
>
>
-- Chuck Hill Senior Consultant / VP DevelopmentPractical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Wed Dec 02 2009 - 13:07:04 EST