Ivan,
Sure: for relationships, we do one-to-one (they expand in-place) and many-to-one (a
dropdown) and one-to-many (a table with a row at the bottom where you
can add more) and many-to-many (a table with a dropdown at the bottom where you can add
more).
Another nice demo might be to generate a regular JSF app, talk about the scaffold, then go
back into Forge and add RichFaces to the project and re-generate
the scaffold. You should see new controls appear, such as date pickers and color pickers
and spinners.
Regards,
Richard.
On 1/03/2012 9:26 AM, Ivan St. Ivanov wrote:
Hey Richard!
Slides maybe yes. But recording, well, it will be in Bulgarian ;-)
Could you give me a hint for something more interesting to show in the Metawidget area
besides the usual id, name, address and one-to-many fields?
Cheers,
Ivan
On Thu, Mar 1, 2012 at 12:20 AM, Richard Kennard <richard(a)kennardconsulting.com
<mailto:richard@kennardconsulting.com>> wrote:
Ivan,
That sounds terrific.
If you could document some of this stuff (make your slides available, write some
slide notes, record your presentation etc.) I'd be happy to
re-present it
at the Sydney JUG?
Regards,
Richard.
On 1/03/2012 7:25 AM, Ivan St. Ivanov wrote:
> Hi everyone,
>
> Now with Forge already final, it's time for us to advertise it to our local
JUGs. I would take the opportunity to talk about it in the Bulgarian JUG
> (somewhere in April though :-(). Here is what I plan to show:
>
> 1) General rant about Forge: what it is good for and how it differs from maven
archetypes and Spring Roo (no religious stuff, I'm a Spring fan BTW)
> 2) Developing a Java EE application with scaffolding: here I would show
something more complex than the conference sample app that Lincoln already
> presented on the Java2Days conference in Sofia last year. Here I would like to
talk about some of the not so common features of the metawidget
> plugin. Any ideas? Of course also some Arquillian and OpenShift.
> 3) After a short break I would continue with a different type of application
that you could implement with Forge. Looking at the plugins, maybe it
could
> be the OSGi stuff.
> 4) Next: developing a plugin. Create a sample plugin, explanation of the
different settings: command, options, usage of the shell prompt, the
> environment, the configuration API, etc.
> 5) Finally: the get involved section
>
> What do you think? Should I add something else or drop anything?
>
> Cheers,
> Ivan
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org <mailto:forge-dev@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