PXAbstractPlugin // When to, when not to

[Thomas Pujolle]

Hi again,

I just want to know, how can I know when I should use a plugin, and
when not to?

For example, I'm building an eLearning framework with some basic
features:
- 3 units with a different theme
- many slides in many units
- some controls to dress all this: previous, next, home, course map
- a tracking system to communicate with a Learning Management System
en remember the user position in the slides.

So far I have only 2, one to manage the views, asset loading,
navigation ... etc.

And one dedicated to the interface with the LMS(Learning Management
System) which is going to send and get information online.

I don't know If I'm very clear.

Can I know some example when the utilization of many plugins was
obvious?

Thank you.

[Laurent Deletelaere]

Hi,

-- translate by Google --
Hello,

This is a very theoretical question, which is difficult to give a simple
answer.
In summary, one plugin is equal to one MVC;

The use of multiple plugins can be felt, when:
� I have parts of application must be completely autonomous;
� when I'm able to easily swap piece application.

But the use of several plugins really takes its meaning with the IOC
engine (PixIOC - who will soon leave), which allows to instantiate and
manipulate the plugins from an XML file.

Very often, it begins developing into one plugin, and when the need
arises we can split (thank you FDT).

I hope I have answered your question somewhat.
I'll try to come in the days of articles that describe the operation of
the MVC + FC and plugins.

-- VO --
Salut,

Voil� une question bien th�orique, dont il est difficile de donner une
r�ponse simple.
En r�sum�, un plugin est �gal � un MVC ;

L'usage de plusieurs plugins peut se faire sentir, lorsque :
� j'ai des parties d'application qui doivent �tre compl�tement autonomes ;
� lors que je dois pouvoir interchanger facilement des morceau
d'application.

Mais l'usage de plusieurs plugins prend vraiment son sens avec le moteur
IOC (PixIOC - qui va bientot sortir), qui permet d'instancier et de
manipuler les plugins depuis un fichier XML.

Tr�s souvent, on commence le d�veloppement dans un seul plugin, et quand
le besoin se fait sentir on peut le fractionner (merci FDT).

J'esp�re avoir un peu r�pondu � ta question.
Je vais essayer de faire dans les jours qui arrivent des articles qui
d�crivent le fonctionnement du MVC+FC et des plugins.

++
Laurent

Le 9/03/11 16:55, Thomas Pujolle a �crit :

> -- Vous recevez ce message, car vous �tes abonn� au groupe Google
> Groupes pixlib. Pour envoyer un message � ce groupe, adressez un e-mail
> � pix...@googlegroups.com. Pour vous d�sabonner de ce groupe, envoyez un
> e-mail � l'adresse pixlib+un...@googlegroups.com. Pour plus
> d'options, consultez la page de ce groupe :
> http://groups.google.com/group/pixlib?hl=fr

[Thomas Pujolle]

Ok!

I'll keep in mind the "completely autonomous" part ;)

Awaiting for more cool articles.
Have a nice day!

On Mar 10, 12:23 pm, Laurent Deletelaere <l.deketela...@gmail.com>
wrote:

> Hi,
>
> -- translate by Google --
> Hello,
>
> This is a very theoretical question, which is difficult to give a simple
> answer.
> In summary, one plugin is equal to one MVC;
>
> The use of multiple plugins can be felt, when:

> I have parts of application must be completely autonomous;

> when I'm able to easily swap piece application.
>
> But the use of several plugins really takes its meaning with the IOC
> engine (PixIOC - who will soon leave), which allows to instantiate and
> manipulate the plugins from an XML file.
>
> Very often, it begins developing into one plugin, and when the need
> arises we can split (thank you FDT).
>
> I hope I have answered your question somewhat.
> I'll try to come in the days of articles that describe the operation of
> the MVC + FC and plugins.
>
> -- VO --
> Salut,
>

> Voil une question bien th orique, dont il est difficile de donner une
> r ponse simple.
> En r sum , un plugin est gal un MVC ;

>
> L'usage de plusieurs plugins peut se faire sentir, lorsque :

> j'ai des parties d'application qui doivent tre compl tement autonomes ;

> lors que je dois pouvoir interchanger facilement des morceau
> d'application.
>
> Mais l'usage de plusieurs plugins prend vraiment son sens avec le moteur
> IOC (PixIOC - qui va bientot sortir), qui permet d'instancier et de
> manipuler les plugins depuis un fichier XML.
>

> Tr s souvent, on commence le d veloppement dans un seul plugin, et quand

> le besoin se fait sentir on peut le fractionner (merci FDT).
>

> J'esp re avoir un peu r pondu ta question.

> Je vais essayer de faire dans les jours qui arrivent des articles qui

> d crivent le fonctionnement du MVC+FC et des plugins.
>
> ++
> Laurent
>
> Le 9/03/11 16:55, Thomas Pujolle a crit :

>
> > Hi again,
>
> > I just want to know, how can I know when I should use a plugin, and
> > when not to?
>
> > For example, I'm building an eLearning framework with some basic
> > features:
> > - 3 units with a different theme
> > - many slides in many units
> > - some controls to dress all this: previous, next, home, course map
> > - a tracking system to communicate with a Learning Management System
> > en remember the user position in the slides.
>
> > So far I have only 2, one to manage the views, asset loading,
> > navigation ... etc.
>
> > And one dedicated to the interface with the LMS(Learning Management
> > System) which is going to send and get information online.
>
> > I don't know If I'm very clear.
>
> > Can I know some example when the utilization of many plugins was
> > obvious?
>
> > Thank you.
>

> > -- Vous recevez ce message, car vous tes abonn au groupe Google
> > Groupes pixlib. Pour envoyer un message ce groupe, adressez un e-mail
> > pix...@googlegroups.com. Pour vous d sabonner de ce groupe, envoyez un
> > e-mail l'adresse pixlib+un...@googlegroups.com. Pour plus