I like.
On Mar 20, 2008, at 4:03 AM, David Avendasora wrote:
> Hi all,
>
> I just had an idea of something that I think would be useful, but it
> is a substantial shift in the normal Class <-> Entity Modeler
> editing workflow.
>
> What if instead of simply seeing that the .eomodeld file in the
> "Related" list in the bottom left corner of the WOLips perspective,
> the actual Entity Properties pane came up for the Entity.java file
> currently active in the java editor?
>
> There's no need to see the outline or the list of entities as the
> WOPackageExplorer would somewhat replace that.
>
> This would be greatly streamline changing properties, adding fetch
> specifications, etc, without actually switching perspectives and
> opening Entity Modeler as a whole. It would really solidify the
> relationship between a entity's .java files and the model itself
> because a switch in perspectives (both Eclipse and actual) would no
> longer be required between java and model editing.
>
> You would only need to open the full Entity Modeler if you were
> adding attributes or relationships, but even those could be done
> here too by simply adding an Entity Modeler toolbar with all the
> requisite buttons to that pane as well.
>
> It would be very rare that you'd need to actually open the model
> file in the full Entity Modeler application, and at that point maybe
> you could just go open it out of the Resources directory, or have a
> button on the new pane that will open the full Entity Modeler
> perspective.
>
> What does everyone think?
>
> Dave
>
--Practical 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 : Thu Mar 20 2008 - 13:31:10 EDT