You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Oliver Lietz <ap...@oliverlietz.de> on 2010/10/18 19:11:58 UTC
dynamic user interfaces
hello all,
I'm trying to build a dynamic user interface from components (panels, lists,
trees, editors, forms, etc.) and assemble parts of it with dependency
injection.
In my first attempt last year with JavaFX I used Blueprint and bind/unbind for
attaching/detaching interface parts (modules).
Now I'm going for Vaadin and multi user which makes it a little more
complicated. Components and some services have to be bound to session/user.
I'm unsure which way to go, which implementation to "misuse". Managed
services? Component factories? Any hints?
tia,
O.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: dynamic user interfaces
Posted by Christopher Brind <br...@brindy.org.uk>.
Actually, you can do that with my version, but I suggest we discuss this on
the Vaadin-OSGi google group, as it's not related to Felix really.
Cheers,
Chris
On 25 October 2010 21:37, Oliver Lietz <ap...@oliverlietz.de> wrote:
> Am Monday 18 October 2010 schrieb Christopher Brind:
> > Hi Oliver,
> >
> > This isn't directly Felix related, a few of us have started a Google
> Group
> > to discuss Vaadin and OSGi, so you might be better off starting there. :)
> >
> > http://groups.google.com/group/vaadin-osgi/members
> >
> > I'll mail you off-list with a few hints to start with.
>
> hey Chris,
>
> I already found all these approaches and your project on github. In your
> example application all components are strongly coupled to your application
> -
> that's exactly what I want to avoid. I've something more similar to
> Petter's
> application in mind, preferable more fine-grained (components instead of
> complete modules):
>
> http://vaadin.com/wiki/-/wiki/Main/Creating%20a%20Modular%20Vaadin%20Application%20with%20OSGi
> Letting the application decide, which and where it adds modules and
> components
> and assembling of modules with DI from components.
>
> regards,
> O.
>
>
Re: dynamic user interfaces
Posted by Oliver Lietz <ap...@oliverlietz.de>.
Am Monday 18 October 2010 schrieb Christopher Brind:
> Hi Oliver,
>
> This isn't directly Felix related, a few of us have started a Google Group
> to discuss Vaadin and OSGi, so you might be better off starting there. :)
>
> http://groups.google.com/group/vaadin-osgi/members
>
> I'll mail you off-list with a few hints to start with.
hey Chris,
I already found all these approaches and your project on github. In your
example application all components are strongly coupled to your application -
that's exactly what I want to avoid. I've something more similar to Petter's
application in mind, preferable more fine-grained (components instead of
complete modules):
http://vaadin.com/wiki/-/wiki/Main/Creating%20a%20Modular%20Vaadin%20Application%20with%20OSGi
Letting the application decide, which and where it adds modules and components
and assembling of modules with DI from components.
regards,
O.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: dynamic user interfaces
Posted by LongkerDandy <lo...@gmail.com>.
I'm also using Vaadin with OSGi.
For now, I have something like this:
1. Vaadin servlet mapping bundle for "/VAADIN"
2. Vaadin themes and widgeset bundle as a fragment.
3. You Vaadin main interface
4. Some Vaadin plugin service also act as a component factory.
The only thing I have is that the Vaadin plugin component can't put his
themes into the main site.
I'm not fixing it, but I guess you can do some trick when vaadin servlet
trying to get the css files.
And thanks for Chris's group info.
Regards
LongkerDandy
On Tue, Oct 19, 2010 at 3:16 AM, Christopher Brind <br...@brindy.org.uk>wrote:
> Hi Oliver,
>
> This isn't directly Felix related, a few of us have started a Google Group
> to discuss Vaadin and OSGi, so you might be better off starting there. :)
>
> http://groups.google.com/group/vaadin-osgi/members
>
> I'll mail you off-list with a few hints to start with.
>
> Cheers,
> Chris
>
>
>
>
> On 18 October 2010 18:11, Oliver Lietz <ap...@oliverlietz.de> wrote:
>
> > hello all,
> >
> > I'm trying to build a dynamic user interface from components (panels,
> > lists,
> > trees, editors, forms, etc.) and assemble parts of it with dependency
> > injection.
> > In my first attempt last year with JavaFX I used Blueprint and
> bind/unbind
> > for
> > attaching/detaching interface parts (modules).
> > Now I'm going for Vaadin and multi user which makes it a little more
> > complicated. Components and some services have to be bound to
> session/user.
> > I'm unsure which way to go, which implementation to "misuse". Managed
> > services? Component factories? Any hints?
> >
> > tia,
> > O.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
Re: dynamic user interfaces
Posted by Christopher Brind <br...@brindy.org.uk>.
Hi Oliver,
This isn't directly Felix related, a few of us have started a Google Group
to discuss Vaadin and OSGi, so you might be better off starting there. :)
http://groups.google.com/group/vaadin-osgi/members
I'll mail you off-list with a few hints to start with.
Cheers,
Chris
On 18 October 2010 18:11, Oliver Lietz <ap...@oliverlietz.de> wrote:
> hello all,
>
> I'm trying to build a dynamic user interface from components (panels,
> lists,
> trees, editors, forms, etc.) and assemble parts of it with dependency
> injection.
> In my first attempt last year with JavaFX I used Blueprint and bind/unbind
> for
> attaching/detaching interface parts (modules).
> Now I'm going for Vaadin and multi user which makes it a little more
> complicated. Components and some services have to be bound to session/user.
> I'm unsure which way to go, which implementation to "misuse". Managed
> services? Component factories? Any hints?
>
> tia,
> O.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>