webical-developers

[Webical-developers] Plugin development

[Ivo v. D. <ivo...@gm...>]

Hello,

In order to get the plugin framework somewhat stable and complete I've
started reviewing and expanded it. I'll do this in two steps: first the
backend and then the frontend. I've decided to do this by developing some
plugins in parallel to get the requirements clear in a practical way. For
the the backend plugin I've already started on a caldav provider, I'll
decide on the frontend plugin later (thinking off a google maps plugin).
While working on the plugin a couple of issues/missing features already
popped up together with some infrastructure needs to make development
easier. I'll list them here for now.

Infrastructure needs:

- A maven repository to deploy webical classes to. This enables plugin
developers to add webical as a compile time dependency.
- A webdav location (or just web with some other form of upload) to deploy
the plugin manifest xsd. This makes it possible to reference the xsd online.
- Nigthly builds that can be deployed to the maven repository (through
continuum?).
- An svn restructuring to accommodate the plugins developed in-house. This
could be done as a separate project or by dividing trunk in /webical and
/plugins.
- (Optional) A location to upload (nigtly) builds for the plugins.


Webical enhancements:

- Extension the pom so that a jar is created with the classes to upload to
the maven repository.
- The possibility to include jar archives in the plugin:
   - Extend the manifest xsd.
   - Extend the plugin classloader.
- Add dependency information in the framework
   - Add a version number in the web.xml or
applicationContext.xml(generated by maven)
   - Add a compatible-webical-version in the manifest xsd
   - Extend the Plugin registration system to check for the version numbers
and only enable the plugin on a match.

Possible desired enhancements:

- Add a search method to the EventDao and manager to enable search on the
calendars.
- Extract the synchronization logic from the provider specific details so it
can be reused by plugins (a google calendar provider for example).
- Plugin framework enhancements:
   - Add additional possibilities to describe the plugin:
      - An version number (required)
      - A description (required)
      - A static html page to display additional information like licenses,
developers and that sort of thing)
   - Add configuration options
      - Global settings. Give the opportunity to supply a configuration
page. The configurations are stored in the database.
      - User settings. Give the opportunity to supply a per-user
configuration page. These configurations are stored in the database as well.
   - Divide the configuration page in steps where the plugin configuration
has a separate tab.
   - Add a list of plugins with the state (plus reason why they are not
enabled), info and a link to the optional info and configuration page.
      - Debug info can also be added. I'm thinking of a page that shows the
registered classes, jars, resource directories, backend providers
used/offered extension points, etc.

There are probably a lot more features that can be thought off, so I'll
start a topic to list these and let it serve as a base for additional
requests and discussions.

Regards,
Ivo

-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Plugin development

[Zoran K. <zo...@fu...>]

Good news! Can you post a link to the topic?

How about adding some of the smaller items to the trackers?

Do you have any caldav server in mind? I think that RSCDS should be pretty
okay. You can also apt-get install it:
http://rscds.sourceforge.net/
(PHP based though, but that really shouldn't matter)

Best,
Zoran

Ivo van Dongen wrote:
> Hello,
> 
> In order to get the plugin framework somewhat stable and complete I've 
> started reviewing and expanded it. I'll do this in two steps: first the 
> backend and then the frontend. I've decided to do this by developing 
> some plugins in parallel to get the requirements clear in a practical 
> way. For the the backend plugin I've already started on a caldav 
> provider, I'll decide on the frontend plugin later (thinking off a 
> google maps plugin).
> While working on the plugin a couple of issues/missing features already 
> popped up together with some infrastructure needs to make development 
> easier. I'll list them here for now.
> 
> Infrastructure needs:
> 
> - A maven repository to deploy webical classes to. This enables plugin 
> developers to add webical as a compile time dependency.
> - A webdav location (or just web with some other form of upload) to 
> deploy the plugin manifest xsd. This makes it possible to reference the 
> xsd online.
> - Nigthly builds that can be deployed to the maven repository (through 
> continuum?).
> - An svn restructuring to accommodate the plugins developed in-house. 
> This could be done as a separate project or by dividing trunk in 
> /webical and /plugins.
> - (Optional) A location to upload (nigtly) builds for the plugins.
> 
> 
> Webical enhancements:
> 
> - Extension the pom so that a jar is created with the classes to upload 
> to the maven repository.
> - The possibility to include jar archives in the plugin:
>    - Extend the manifest xsd.
>    - Extend the plugin classloader.
> - Add dependency information in the framework
>    - Add a version number in the web.xml or applicationContext.xml 
> (generated by maven)
>    - Add a compatible-webical-version in the manifest xsd
>    - Extend the Plugin registration system to check for the version 
> numbers and only enable the plugin on a match.
> 
> Possible desired enhancements:
> 
> - Add a search method to the EventDao and manager to enable search on 
> the calendars.
> - Extract the synchronization logic from the provider specific details 
> so it can be reused by plugins (a google calendar provider for example).
> - Plugin framework enhancements:
>    - Add additional possibilities to describe the plugin:
>       - An version number (required)
>       - A description (required)
>       - A static html page to display additional information like 
> licenses, developers and that sort of thing)
>    - Add configuration options
>       - Global settings. Give the opportunity to supply a configuration 
> page. The configurations are stored in the database.
>       - User settings. Give the opportunity to supply a per-user 
> configuration page. These configurations are stored in the database as 
> well.
>    - Divide the configuration page in steps where the plugin 
> configuration has a separate tab.
>    - Add a list of plugins with the state (plus reason why they are not 
> enabled), info and a link to the optional info and configuration page.
>       - Debug info can also be added. I'm thinking of a page that shows 
> the registered classes, jars, resource directories, backend providers 
> used/offered extension points, etc.
> 
> There are probably a lot more features that can be thought off, so I'll 
> start a topic to list these and let it serve as a base for additional 
> requests and discussions.
> 
> Regards,
> Ivo
> 
> -- 
> Ivo van Dongen
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers


-- 
Zoran Kovacevic
Func. Internet Integration
W http://www.func.nl
M +31 6 48104284
T +31 20 4230000
F +31 20 4223500
GPG http://www.func.nl/keys/z.k...@fu...

Re: [Webical-developers] Plugin development

[Ivo v. D. <ivo...@gm...>]

On 9/24/07, Zoran Kovacevic <zo...@fu...> wrote:
>
> Good news! Can you post a link to the topic?


http://www.webical.org/twiki/bin/view/Main/PluginFrameworkEnhancement

How about adding some of the smaller items to the trackers?


I'll see if  I can group them together a bit.

Do you have any caldav server in mind? I think that RSCDS should be pretty
> okay. You can also apt-get install it:
> http://rscds.sourceforge.net/
> (PHP based though, but that really shouldn't matter)


Well, I'm using chandler at the moment for testing. Works quite good, but
the standard logging and error reporting is almost nonexistent.

Best,
> Zoran
>
> Ivo van Dongen wrote:
> > Hello,
> >
> > In order to get the plugin framework somewhat stable and complete I've
> > started reviewing and expanded it. I'll do this in two steps: first the
> > backend and then the frontend. I've decided to do this by developing
> > some plugins in parallel to get the requirements clear in a practical
> > way. For the the backend plugin I've already started on a caldav
> > provider, I'll decide on the frontend plugin later (thinking off a
> > google maps plugin).
> > While working on the plugin a couple of issues/missing features already
> > popped up together with some infrastructure needs to make development
> > easier. I'll list them here for now.
> >
> > Infrastructure needs:
> >
> > - A maven repository to deploy webical classes to. This enables plugin
> > developers to add webical as a compile time dependency.
> > - A webdav location (or just web with some other form of upload) to
> > deploy the plugin manifest xsd. This makes it possible to reference the
> > xsd online.
> > - Nigthly builds that can be deployed to the maven repository (through
> > continuum?).
> > - An svn restructuring to accommodate the plugins developed in-house.
> > This could be done as a separate project or by dividing trunk in
> > /webical and /plugins.
> > - (Optional) A location to upload (nigtly) builds for the plugins.
> >
> >
> > Webical enhancements:
> >
> > - Extension the pom so that a jar is created with the classes to upload
> > to the maven repository.
> > - The possibility to include jar archives in the plugin:
> >    - Extend the manifest xsd.
> >    - Extend the plugin classloader.
> > - Add dependency information in the framework
> >    - Add a version number in the web.xml or applicationContext.xml
> > (generated by maven)
> >    - Add a compatible-webical-version in the manifest xsd
> >    - Extend the Plugin registration system to check for the version
> > numbers and only enable the plugin on a match.
> >
> > Possible desired enhancements:
> >
> > - Add a search method to the EventDao and manager to enable search on
> > the calendars.
> > - Extract the synchronization logic from the provider specific details
> > so it can be reused by plugins (a google calendar provider for example).
> > - Plugin framework enhancements:
> >    - Add additional possibilities to describe the plugin:
> >       - An version number (required)
> >       - A description (required)
> >       - A static html page to display additional information like
> > licenses, developers and that sort of thing)
> >    - Add configuration options
> >       - Global settings. Give the opportunity to supply a configuration
> > page. The configurations are stored in the database.
> >       - User settings. Give the opportunity to supply a per-user
> > configuration page. These configurations are stored in the database as
> > well.
> >    - Divide the configuration page in steps where the plugin
> > configuration has a separate tab.
> >    - Add a list of plugins with the state (plus reason why they are not
> > enabled), info and a link to the optional info and configuration page.
> >       - Debug info can also be added. I'm thinking of a page that shows
> > the registered classes, jars, resource directories, backend providers
> > used/offered extension points, etc.
> >
> > There are probably a lot more features that can be thought off, so I'll
> > start a topic to list these and let it serve as a base for additional
> > requests and discussions.
> >
> > Regards,
> > Ivo
> >
> > --
> > Ivo van Dongen
> > Func. Internet Integration
> > W http://www.func.nl
> > T +31 20 4230000
> > F +31 20 4223500
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Webical-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webical-developers
>
>
> --
> Zoran Kovacevic
> Func. Internet Integration
> W http://www.func.nl
> M +31 6 48104284
> T +31 20 4230000
> F +31 20 4223500
> GPG http://www.func.nl/keys/z.k...@fu...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Plugin development

[Ivo v. D. <ivo...@gm...>]

Btw. What do you think off the infrastrucure needs. Is it possible to set
this up on the webical.org server?

On 9/24/07, Zoran Kovacevic <zo...@fu...> wrote:
>
> Good news! Can you post a link to the topic?
>
> How about adding some of the smaller items to the trackers?
>
> Do you have any caldav server in mind? I think that RSCDS should be pretty
> okay. You can also apt-get install it:
> http://rscds.sourceforge.net/
> (PHP based though, but that really shouldn't matter)
>
> Best,
> Zoran
>
> Ivo van Dongen wrote:
> > Hello,
> >
> > In order to get the plugin framework somewhat stable and complete I've
> > started reviewing and expanded it. I'll do this in two steps: first the
> > backend and then the frontend. I've decided to do this by developing
> > some plugins in parallel to get the requirements clear in a practical
> > way. For the the backend plugin I've already started on a caldav
> > provider, I'll decide on the frontend plugin later (thinking off a
> > google maps plugin).
> > While working on the plugin a couple of issues/missing features already
> > popped up together with some infrastructure needs to make development
> > easier. I'll list them here for now.
> >
> > Infrastructure needs:
> >
> > - A maven repository to deploy webical classes to. This enables plugin
> > developers to add webical as a compile time dependency.
> > - A webdav location (or just web with some other form of upload) to
> > deploy the plugin manifest xsd. This makes it possible to reference the
> > xsd online.
> > - Nigthly builds that can be deployed to the maven repository (through
> > continuum?).
> > - An svn restructuring to accommodate the plugins developed in-house.
> > This could be done as a separate project or by dividing trunk in
> > /webical and /plugins.
> > - (Optional) A location to upload (nigtly) builds for the plugins.
> >
> >
> > Webical enhancements:
> >
> > - Extension the pom so that a jar is created with the classes to upload
> > to the maven repository.
> > - The possibility to include jar archives in the plugin:
> >    - Extend the manifest xsd.
> >    - Extend the plugin classloader.
> > - Add dependency information in the framework
> >    - Add a version number in the web.xml or applicationContext.xml
> > (generated by maven)
> >    - Add a compatible-webical-version in the manifest xsd
> >    - Extend the Plugin registration system to check for the version
> > numbers and only enable the plugin on a match.
> >
> > Possible desired enhancements:
> >
> > - Add a search method to the EventDao and manager to enable search on
> > the calendars.
> > - Extract the synchronization logic from the provider specific details
> > so it can be reused by plugins (a google calendar provider for example).
> > - Plugin framework enhancements:
> >    - Add additional possibilities to describe the plugin:
> >       - An version number (required)
> >       - A description (required)
> >       - A static html page to display additional information like
> > licenses, developers and that sort of thing)
> >    - Add configuration options
> >       - Global settings. Give the opportunity to supply a configuration
> > page. The configurations are stored in the database.
> >       - User settings. Give the opportunity to supply a per-user
> > configuration page. These configurations are stored in the database as
> > well.
> >    - Divide the configuration page in steps where the plugin
> > configuration has a separate tab.
> >    - Add a list of plugins with the state (plus reason why they are not
> > enabled), info and a link to the optional info and configuration page.
> >       - Debug info can also be added. I'm thinking of a page that shows
> > the registered classes, jars, resource directories, backend providers
> > used/offered extension points, etc.
> >
> > There are probably a lot more features that can be thought off, so I'll
> > start a topic to list these and let it serve as a base for additional
> > requests and discussions.
> >
> > Regards,
> > Ivo
> >
> > --
> > Ivo van Dongen
> > Func. Internet Integration
> > W http://www.func.nl
> > T +31 20 4230000
> > F +31 20 4223500
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Webical-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webical-developers
>
>
> --
> Zoran Kovacevic
> Func. Internet Integration
> W http://www.func.nl
> M +31 6 48104284
> T +31 20 4230000
> F +31 20 4223500
> GPG http://www.func.nl/keys/z.k...@fu...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500

Re: [Webical-developers] Plugin development

[Zoran K. <zo...@fu...>]

should be possible. rscds should be very straightforward with respect to 
  installation. it requires postgres though. what are the cosmo 
requirements?

Ivo van Dongen wrote:
> Btw. What do you think off the infrastrucure needs. Is it possible to 
> set this up on the webical.org <http://webical.org> server?
> 
> On 9/24/07, *Zoran Kovacevic * <zo...@fu... <mailto:zo...@fu...>> wrote:
> 
>     Good news! Can you post a link to the topic?
> 
>     How about adding some of the smaller items to the trackers?
> 
>     Do you have any caldav server in mind? I think that RSCDS should be
>     pretty
>     okay. You can also apt-get install it:
>     http://rscds.sourceforge.net/
>     (PHP based though, but that really shouldn't matter)
> 
>     Best,
>     Zoran
> 
>     Ivo van Dongen wrote:
>      > Hello,
>      >
>      > In order to get the plugin framework somewhat stable and complete
>     I've
>      > started reviewing and expanded it. I'll do this in two steps:
>     first the
>      > backend and then the frontend. I've decided to do this by developing
>      > some plugins in parallel to get the requirements clear in a
>     practical
>      > way. For the the backend plugin I've already started on a caldav
>      > provider, I'll decide on the frontend plugin later (thinking off a
>      > google maps plugin).
>      > While working on the plugin a couple of issues/missing features
>     already
>      > popped up together with some infrastructure needs to make development
>      > easier. I'll list them here for now.
>      >
>      > Infrastructure needs:
>      >
>      > - A maven repository to deploy webical classes to. This enables
>     plugin
>      > developers to add webical as a compile time dependency.
>      > - A webdav location (or just web with some other form of upload) to
>      > deploy the plugin manifest xsd. This makes it possible to
>     reference the
>      > xsd online.
>      > - Nigthly builds that can be deployed to the maven repository
>     (through
>      > continuum?).
>      > - An svn restructuring to accommodate the plugins developed in-house.
>      > This could be done as a separate project or by dividing trunk in
>      > /webical and /plugins.
>      > - (Optional) A location to upload (nigtly) builds for the plugins.
>      >
>      >
>      > Webical enhancements:
>      >
>      > - Extension the pom so that a jar is created with the classes to
>     upload
>      > to the maven repository.
>      > - The possibility to include jar archives in the plugin:
>      >    - Extend the manifest xsd.
>      >    - Extend the plugin classloader.
>      > - Add dependency information in the framework
>      >    - Add a version number in the web.xml or applicationContext.xml
>      > (generated by maven)
>      >    - Add a compatible-webical-version in the manifest xsd
>      >    - Extend the Plugin registration system to check for the version
>      > numbers and only enable the plugin on a match.
>      >
>      > Possible desired enhancements:
>      >
>      > - Add a search method to the EventDao and manager to enable search on
>      > the calendars.
>      > - Extract the synchronization logic from the provider specific
>     details
>      > so it can be reused by plugins (a google calendar provider for
>     example).
>      > - Plugin framework enhancements:
>      >    - Add additional possibilities to describe the plugin:
>      >       - An version number (required)
>      >       - A description (required)
>      >       - A static html page to display additional information like
>      > licenses, developers and that sort of thing)
>      >    - Add configuration options
>      >       - Global settings. Give the opportunity to supply a
>     configuration
>      > page. The configurations are stored in the database.
>      >       - User settings. Give the opportunity to supply a per-user
>      > configuration page. These configurations are stored in the
>     database as
>      > well.
>      >    - Divide the configuration page in steps where the plugin
>      > configuration has a separate tab.
>      >    - Add a list of plugins with the state (plus reason why they
>     are not
>      > enabled), info and a link to the optional info and configuration
>     page.
>      >       - Debug info can also be added. I'm thinking of a page that
>     shows
>      > the registered classes, jars, resource directories, backend providers
>      > used/offered extension points, etc.
>      >
>      > There are probably a lot more features that can be thought off,
>     so I'll
>      > start a topic to list these and let it serve as a base for additional
>      > requests and discussions.
>      >
>      > Regards,
>      > Ivo
>      >
>      > --
>      > Ivo van Dongen
>      > Func. Internet Integration
>      > W http://www.func.nl
>      > T +31 20 4230000
>      > F +31 20 4223500
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      >
>     -------------------------------------------------------------------------
>      > This SF.net email is sponsored by: Microsoft
>      > Defy all challenges. Microsoft(R) Visual Studio 2005.
>      > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>      >
>      > _______________________________________________
>      > Webical-developers mailing list
>      > Web...@li...
>     <mailto:Web...@li...>
>      > https://lists.sourceforge.net/lists/listinfo/webical-developers
> 
> 
>     --
>     Zoran Kovacevic
>     Func. Internet Integration
>     W http://www.func.nl
>     M +31 6 48104284
>     T +31 20 4230000
>     F +31 20 4223500
>     GPG http://www.func.nl/keys/z.k...@fu...
> 
>     -------------------------------------------------------------------------
> 
>     This SF.net email is sponsored by: Microsoft
>     Defy all challenges. Microsoft(R) Visual Studio 2005.
>     http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>     <http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/>
>     _______________________________________________
>     Webical-developers mailing list
>     Web...@li...
>     <mailto:Web...@li...>
>     https://lists.sourceforge.net/lists/listinfo/webical-developers
> 
> 
> 
> 
> -- 
> Ivo van Dongen
> Func. Internet Integration
> W http://www.func.nl
> T +31 20 4230000
> F +31 20 4223500
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers


-- 
Zoran Kovacevic
Func. Internet Integration
W http://www.func.nl
M +31 6 48104284
T +31 20 4230000
F +31 20 4223500
GPG http://www.func.nl/keys/z.k...@fu...

Re: [Webical-developers] Plugin development

[Ivo v. D. <ivo...@gm...>]

On 9/24/07, Zoran Kovacevic <zo...@fu...> wrote:
>
> should be possible. rscds should be very straightforward with respect to
>   installation. it requires postgres though. what are the cosmo
> requirements?


Cosmo is pretty self-contained actually. I didn't dive in to deed yet as the
default setup gave me enough possibilities for development. I'll give it a
look this weekend (if time permits).

Ivo van Dongen wrote:
> > Btw. What do you think off the infrastrucure needs. Is it possible to
> > set this up on the webical.org <http://webical.org> server?
> >
> > On 9/24/07, *Zoran Kovacevic * <zo...@fu... <mailto:zo...@fu...>>
> wrote:
> >
> >     Good news! Can you post a link to the topic?
> >
> >     How about adding some of the smaller items to the trackers?
> >
> >     Do you have any caldav server in mind? I think that RSCDS should be
> >     pretty
> >     okay. You can also apt-get install it:
> >     http://rscds.sourceforge.net/
> >     (PHP based though, but that really shouldn't matter)
> >
> >     Best,
> >     Zoran
> >
> >     Ivo van Dongen wrote:
> >      > Hello,
> >      >
> >      > In order to get the plugin framework somewhat stable and complete
> >     I've
> >      > started reviewing and expanded it. I'll do this in two steps:
> >     first the
> >      > backend and then the frontend. I've decided to do this by
> developing
> >      > some plugins in parallel to get the requirements clear in a
> >     practical
> >      > way. For the the backend plugin I've already started on a caldav
> >      > provider, I'll decide on the frontend plugin later (thinking off
> a
> >      > google maps plugin).
> >      > While working on the plugin a couple of issues/missing features
> >     already
> >      > popped up together with some infrastructure needs to make
> development
> >      > easier. I'll list them here for now.
> >      >
> >      > Infrastructure needs:
> >      >
> >      > - A maven repository to deploy webical classes to. This enables
> >     plugin
> >      > developers to add webical as a compile time dependency.
> >      > - A webdav location (or just web with some other form of upload)
> to
> >      > deploy the plugin manifest xsd. This makes it possible to
> >     reference the
> >      > xsd online.
> >      > - Nigthly builds that can be deployed to the maven repository
> >     (through
> >      > continuum?).
> >      > - An svn restructuring to accommodate the plugins developed
> in-house.
> >      > This could be done as a separate project or by dividing trunk in
> >      > /webical and /plugins.
> >      > - (Optional) A location to upload (nigtly) builds for the
> plugins.
> >      >
> >      >
> >      > Webical enhancements:
> >      >
> >      > - Extension the pom so that a jar is created with the classes to
> >     upload
> >      > to the maven repository.
> >      > - The possibility to include jar archives in the plugin:
> >      >    - Extend the manifest xsd.
> >      >    - Extend the plugin classloader.
> >      > - Add dependency information in the framework
> >      >    - Add a version number in the web.xml or
> applicationContext.xml
> >      > (generated by maven)
> >      >    - Add a compatible-webical-version in the manifest xsd
> >      >    - Extend the Plugin registration system to check for the
> version
> >      > numbers and only enable the plugin on a match.
> >      >
> >      > Possible desired enhancements:
> >      >
> >      > - Add a search method to the EventDao and manager to enable
> search on
> >      > the calendars.
> >      > - Extract the synchronization logic from the provider specific
> >     details
> >      > so it can be reused by plugins (a google calendar provider for
> >     example).
> >      > - Plugin framework enhancements:
> >      >    - Add additional possibilities to describe the plugin:
> >      >       - An version number (required)
> >      >       - A description (required)
> >      >       - A static html page to display additional information like
> >      > licenses, developers and that sort of thing)
> >      >    - Add configuration options
> >      >       - Global settings. Give the opportunity to supply a
> >     configuration
> >      > page. The configurations are stored in the database.
> >      >       - User settings. Give the opportunity to supply a per-user
> >      > configuration page. These configurations are stored in the
> >     database as
> >      > well.
> >      >    - Divide the configuration page in steps where the plugin
> >      > configuration has a separate tab.
> >      >    - Add a list of plugins with the state (plus reason why they
> >     are not
> >      > enabled), info and a link to the optional info and configuration
> >     page.
> >      >       - Debug info can also be added. I'm thinking of a page that
> >     shows
> >      > the registered classes, jars, resource directories, backend
> providers
> >      > used/offered extension points, etc.
> >      >
> >      > There are probably a lot more features that can be thought off,
> >     so I'll
> >      > start a topic to list these and let it serve as a base for
> additional
> >      > requests and discussions.
> >      >
> >      > Regards,
> >      > Ivo
> >      >
> >      > --
> >      > Ivo van Dongen
> >      > Func. Internet Integration
> >      > W http://www.func.nl
> >      > T +31 20 4230000
> >      > F +31 20 4223500
> >      >
> >      >
> >      >
> >
> ------------------------------------------------------------------------
> >      >
> >      >
> >
> -------------------------------------------------------------------------
> >      > This SF.net email is sponsored by: Microsoft
> >      > Defy all challenges. Microsoft(R) Visual Studio 2005.
> >      > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >      >
> >      >
> >      >
> >
> ------------------------------------------------------------------------
> >      >
> >      > _______________________________________________
> >      > Webical-developers mailing list
> >      > Web...@li...
> >     <mailto:Web...@li...>
> >      > https://lists.sourceforge.net/lists/listinfo/webical-developers
> >
> >
> >     --
> >     Zoran Kovacevic
> >     Func. Internet Integration
> >     W http://www.func.nl
> >     M +31 6 48104284
> >     T +31 20 4230000
> >     F +31 20 4223500
> >     GPG http://www.func.nl/keys/z.k...@fu...
> >
> >
> -------------------------------------------------------------------------
> >
> >     This SF.net email is sponsored by: Microsoft
> >     Defy all challenges. Microsoft(R) Visual Studio 2005.
> >     http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >     <http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/>
> >     _______________________________________________
> >     Webical-developers mailing list
> >     Web...@li...
> >     <mailto:Web...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/webical-developers
> >
> >
> >
> >
> > --
> > Ivo van Dongen
> > Func. Internet Integration
> > W http://www.func.nl
> > T +31 20 4230000
> > F +31 20 4223500
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Webical-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/webical-developers
>
>
> --
> Zoran Kovacevic
> Func. Internet Integration
> W http://www.func.nl
> M +31 6 48104284
> T +31 20 4230000
> F +31 20 4223500
> GPG http://www.func.nl/keys/z.k...@fu...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Webical-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webical-developers
>



-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500