Creating/Extending modules

[vieira]

Hi, has anyone had the experience of creating a new module, or
extending an existing one (in this case, the swingvm)?

For example, if we wanted to change some of the base view components,
such has menu, class bar, calendar, etc... we could change swingvm,
but it's not a good option. How can swingvm be extended (without
creating a new module by copy&paste and change it) and how can we use
this new created module?

Thanks,
Carlos V.

[Eitan Suez]

there's a notion of a view mechanism (see the interface by
the same name). SwingViewMechanism
is one implementation. implementations of the ViewMechanism
interface are essentially a registry of what components are used
for different parts of the user interface (object views, list views,
atomic editors, renderers, etc..). what view mechanism is in
play for a specific app can be altered by revising the
spring bean defined in src/applicationContext.xml with the id of
"view-mechanism."

/ eitan

> --
> You received this message because you are subscribed to the Google Groups "jmatter" group.
> To post to this group, send email to jma...@googlegroups.com.
> To unsubscribe from this group, send email to jmatter+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jmatter?hl=en.
>
>

[Carlos Vieira]

Hi Eitan... many thanks!

Now it's pretty much clear the great modularity and extensibility of the framework ;)

Regards,
Carlos V.

[Eitan Suez]

On Wed, Aug 4, 2010 at 5:27 AM, Carlos Vieira <carlos...@gmail.com> wrote:
> Hi Eitan... many thanks!
>
you're welcome.

> Now it's pretty much clear the great modularity and extensibility of the
> framework ;)
>

i wouldn't go that far. :-) but i did try to make the system somewhat
modular.

thanks,
/ eitan