It would be great to add some of the functionality from DBEdit into an
EOModeler replacement. Being able to browse the data via relationships is
very useful. The DBEdit query interface although a little kludgy is still
better than nothing at all. At least you can test fetch specs with it.
The biggest hassle I have always had with EOModeler is having to set the
value type for various Number data types. It's too bad we can't do like
Cayenne does, just use JDBC data types and not have to worry about
prototypes and the like.
I like the visual layout in EOModeler to build relationships, the pane view
is useful for flattened relationships. But most of our work uses the entity
view.
Some type of documentation generator like EOReporter would be pretty useful
On 9/15/05 8:35 AM, "Greg" <ghuland..ramedphotographics.com> wrote:
> Hi,
> I have been looking into writing some plugins for eclipse to take
> advantage of some of the tools already available to eclipse. I have
> started to write a data source that connects into EOF to work with
> BIRT (http://www.eclipse.org/birt/) so that we have a gui report
> creator that we can all leverage in our applications. I hope to have
> the data source completed over the weekend, but I will have to create
> the gui for it as the basic way of creating a query with birt is to
> type an sql statement. So I have decided to create a fetch spec
> builder, with qualifier creator so that it can be done like it is in
> EOModeller. Because there would be a lot of reuse of the ui between
> this and an eomodeller replacement for eclipse, I thought I would
> solicit peoples views of what they would like out of a new
> eomodeller? Do you want the layout to be the same as the current one,
> but just work properly? Or do you want it to be more graphically
> oriented, like how it seems they are doing it with Xcode?
>
> I would really appreciate peoples views and comments.
>
> Regards,
> Greg
This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 08:52:55 EDT