This is possibly because if you don't "reload" the entity after making
changes in an external editor, Forge doesn't know the file has changed, and
rewrites the same contents... probably something to fix.
That's my guess as to what they are referring to. Good point though.
~Lincoln
On Mon, Oct 24, 2011 at 1:02 AM, Jason Porter <lightguard.jp(a)gmail.com>wrote:
I'm a little confused by this thinking. Forge will work with
whatever you
have there. Generated or not. It isn't going to overwrite anything you put
in there, maybe they were using an old version?
Sent from my iPhone
On Oct 23, 2011, at 22:50, Richard Kennard <richard(a)kennardconsulting.com>
wrote:
> Hi guys,
>
> There's a nice looking presentation up at...
>
>
http://www.slideshare.net/jbaruch/pure-java-rad-and-scaffolding-tools-race
>
> ...that slightly 'dings' Seam Forge for not being 'continuous'
(slide
43). I asked the authors what they meant by this. They said:
>
> "The reason we stated SeamForge scaffolding as one-time is not because of
Metawidget, but because of the fact that generated code inside the entities
is
> not separated from user-created one. e.g. - I generated Person entity,
then changed stuff and added some stuff to it, and SeamForge's entities
editing
> feature is not usable for me anymore (Metawidget's forms rendering will
still work, of course). Just for the contrast, Spring Roo separated the
> user-generated content from auto-generated content by using Inter-type
declarations. I can edit my entities the way I like and Roo can mess with
its ITDs
> the way it likes"
>
> Just some food for thought?
>
> Richard.
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev