Re: [Amsn-devel] new and gooey

[Harry V. <htv...@zo...>]

Op zondag 30 oktober 2005 20:19, schreef GrdScarabe:
> >>+-------------------------------------+
> >>
> >>|            Plugins                  |
> >>|   (UIs / Protocols / Extensions)    |
> >>
> >>+-------------------------------------+
> >>           v  Events  ^^^
> >>+-------------------------------------+
> >>
> >>|            Core                     |
> >>|   (Event dispatching system)        |
> >>
> >>+-------------------------------------+
> >
> > I would be quite interested in working on the Core part as I have
> > experience working with the current plugin system and have some ideas on
> > how to adapt it to work with "Core" plugins and "user" plugins.
> >
> > One more thing that would be have to be done is to create global and
> > per-user plugins. Global plugins are ones that get loaded on amsn start
> > and user plugins are those that get loader on user login.
>
> +-------------------+------------------+
>
> |  Globals Plugins  | per user Plugins |
> | (UIs / Protocols) |  (Extensions)    |
>
> +-------------------+------------------+
>              v  Events  ^^^
> +--------------------------------------+
>
> |             Core                     |
> |    (Event dispatching system)        |
>
> +--------------------------------------+
>
> Do you mean something like that ? Or do you think the protocols and the
> GUI parts can be considered as per-user-plugins too ?
I think Karol was very right in speaking of Core/user and Global/per-user as 
separate concepts. GUI parts and even protocols can be per-user. Think of 
having different GUI's (one user may prefer another GUI than another). Also a 
developer may want to use an 'unstable' protocol plugin for testing, while 
other users may want the default, stable protocol plugin.

>
> If we consider that scheme, then some "plugins" must have priority on
> the others to treat the events, no ? Do you think a prioity list is
> enough to deal with that matter ?
Good idea, although I would say 'dependency list' rather than 'priority list'. 
This will also eliminate the need of distinguishing between Core- and 
User-plugins. Also, it is good to make Plugin-categories. This way you can, 
for example, make a GUI-plugin depend on the Protocol group, so it will work 
with either a MSNP9 plugin, or MSNP11, or Jabber, or whatever....
(Please note that per-user plugins can depend on global ones, but global 
plugins cannot depend on per-user ones, because that would break aMSN 
startup.)

Within a group there should also be a way to set 'conflicts' (like MSNP9 
conflicts with MSNP11, but using any of them together with a Jabber plugin 
should be possible). But this is quite complex, I haven't a real good idea 
yet.

>
> I would be interested on working on the core too ... if you are ok to
> "mentor" me ! I have some experience in TCL, but not that much on Tk.
>
> GrdScarabe
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Amsn-devel mailing list
> Ams...@li...
> https://lists.sourceforge.net/lists/listinfo/amsn-devel