[campsite-dev] Plugin questions
  • Vote Up0Vote Down importimport
    Posts: 0Member
    Hi all,

    I'm trying to come up with clear instructions for our plugins. A rough
    draft is up in the 3.1 Campsite manual now in Chapter 7 - Plugins
    (http://code.campware.org/manuals/campsite/3.1 still works, as does
    http://manuals.campware.org/manuals/campsite/3.1).


    A few things still aren't clear to me:

    1) Where does a person get a plugin? Are they freely available somewhere
    yet?

    2) Will plugins have their own numbering convention and, I guess,
    maintainers? What would the version numbers be for the current plugins?

    3) Is a plugin in a certain format, like .tar.gz, which the Campsite server
    knows how to process? Or does a user have to untar it?

    4) Will plugins have their own .deb packages, or is that overkill? On one
    hand, I could see that it would be quite nice to have a .deb package
    mechanism, but on the other hand, it will mean that the plugin upload
    process in the admin interface wouldn't get used...

    5) Is there a list of available plugins somewhere? So far I know about
    polls, blogs and interview. What's on the development roadmap?

    6) When we release a plugin, we should also include templates that allow a
    user to use the plugin 'as is' by simply putting in the templates. Ideally
    they wouldn't even have to put the template in there; it would just get put
    there as part of the plugin install process.

    7) What are the steps a developer has to go through to make a plugin? Who's
    going to work on a 'Hello World' plugin? Or should one of the existing
    plugins serve as a training example?

    Cool Aside from the examples on edge (polls.edge.campware.org), are there
    other examples of plugins already in practice? Can I get some sample
    templates (with lots of comments) from those using the plugins already?



    Hope this list isn't too big. I'm actually quite excited about plugins, and
    want to make sure the documentation really makes it clear how to use them.


    doug
  • 2 Comments sorted by
  • Vote Up0Vote Down importimport
    Posts: 0Member
    Hi,

    1) The plugins are available via svn server. As soont hey are beta status, I
    will put them to sourceforge

    2) Yes, they have own versioning. I gave them 0.1 for the first. I think the
    plugin version should reflect compatibility with campsite. E.g. it could be
    3.x-0.1

    3) The plugins have to uploaded via admin-interface as an tar archive. The
    archive contains an file
    %plugnin_name%.info.php, and the installer reject archives which does not
    have this file.

    4) I don't plan .deb (or other os) packages

    5) polls, interview and blog is the complete current list. Once they are
    released, they should be more promoted on campware.org/sourceforge

    6) plugins come with sample templates. Each plugin have an INSTALL file,
    which descripes the installation. The templates could be copyed
    automatically (check if not same files/folders already exists)

    7) There must be an heelo worls example. Ideally someone else would write
    it, with my help, to revisit what I have done.

    Cool Seems sobodfy use them currently. Sample tamplates are here:
    http://code.campware.org/projects/campsite/browser/trunk/plugins/interview/i
    nstall/sample_templates
    http://code.campware.org/projects/campsite/browser/trunk/plugins/poll/instal
    l/sample_templates
    http://code.campware.org/projects/campsite/browser/trunk/plugins/blog/instal
    l/sample_templates



    Best regards,
    Sebastian


    > -----Original Message-----
    > From: Douglas.Arellanes@mdlf.org [mailto:Douglas.Arellanes@mdlf.org]
    > Sent: Tuesday, October 14, 2008 11:24 AM
    > To: campsite-dev@lists.campware.org
    > Subject: [campsite-dev] Plugin questions
    >
    >
    >
    > Hi all,
    >
    > I'm trying to come up with clear instructions for our plugins. A rough
    > draft is up in the 3.1 Campsite manual now in Chapter 7 - Plugins
    > (http://code.campware.org/manuals/campsite/3.1 still works, as does
    > http://manuals.campware.org/manuals/campsite/3.1).
    >
    >
    > A few things still aren't clear to me:
    >
    > 1) Where does a person get a plugin? Are they freely available somewhere
    > yet?
    >
    > 2) Will plugins have their own numbering convention and, I guess,
    > maintainers? What would the version numbers be for the current plugins?
    >
    > 3) Is a plugin in a certain format, like .tar.gz, which the
    > Campsite server
    > knows how to process? Or does a user have to untar it?
    >
    > 4) Will plugins have their own .deb packages, or is that overkill? On one
    > hand, I could see that it would be quite nice to have a .deb package
    > mechanism, but on the other hand, it will mean that the plugin upload
    > process in the admin interface wouldn't get used...
    >
    > 5) Is there a list of available plugins somewhere? So far I know about
    > polls, blogs and interview. What's on the development roadmap?
    >
    > 6) When we release a plugin, we should also include templates that allow a
    > user to use the plugin 'as is' by simply putting in the templates. Ideally
    > they wouldn't even have to put the template in there; it would
    > just get put
    > there as part of the plugin install process.
    >
    > 7) What are the steps a developer has to go through to make a
    > plugin? Who's
    > going to work on a 'Hello World' plugin? Or should one of the existing
    > plugins serve as a training example?
    >
    > Cool Aside from the examples on edge (polls.edge.campware.org), are there
    > other examples of plugins already in practice? Can I get some sample
    > templates (with lots of comments) from those using the plugins already?
    >
    >
    >
    > Hope this list isn't too big. I'm actually quite excited about
    > plugins, and
    > want to make sure the documentation really makes it clear how to use them.
    >
    >
    > doug
    >
  • Vote Up0Vote Down importimport
    Posts: 0Member
    1) The same site where you can download campsite.

    2) Plugins will have their own versioning. Maintainers: Sebastian for polls,
    blogs and interview plugins. No other plugins for the moment.

    3) Plugins have to be packet in a certain format, Sebastian will be able to
    help you with this.

    4) We can surely create separate debs for each plugin.

    5) Ask Sava

    6) It's a good idea to include some basic templates that can be used to
    improve the site. These templates can't always be used as they are because
    of the different article types, layout etc.

    Sebastian should be able to answer 7) and Cool

    Mugur

    On Tue, Oct 14, 2008 at 12:24 PM, wrote:

    >
    > Hi all,
    >
    > I'm trying to come up with clear instructions for our plugins. A rough
    > draft is up in the 3.1 Campsite manual now in Chapter 7 - Plugins
    > (http://code.campware.org/manuals/campsite/3.1 still works, as does
    > http://manuals.campware.org/manuals/campsite/3.1).
    >
    >
    > A few things still aren't clear to me:
    >
    > 1) Where does a person get a plugin? Are they freely available somewhere
    > yet?
    >
    > 2) Will plugins have their own numbering convention and, I guess,
    > maintainers? What would the version numbers be for the current plugins?
    >
    > 3) Is a plugin in a certain format, like .tar.gz, which the Campsite server
    > knows how to process? Or does a user have to untar it?
    >
    > 4) Will plugins have their own .deb packages, or is that overkill? On one
    > hand, I could see that it would be quite nice to have a .deb package
    > mechanism, but on the other hand, it will mean that the plugin upload
    > process in the admin interface wouldn't get used...
    >
    > 5) Is there a list of available plugins somewhere? So far I know about
    > polls, blogs and interview. What's on the development roadmap?
    >
    > 6) When we release a plugin, we should also include templates that allow a
    > user to use the plugin 'as is' by simply putting in the templates. Ideally
    > they wouldn't even have to put the template in there; it would just get put
    > there as part of the plugin install process.
    >
    > 7) What are the steps a developer has to go through to make a plugin? Who's
    > going to work on a 'Hello World' plugin? Or should one of the existing
    > plugins serve as a training example?
    >
    > Cool Aside from the examples on edge (polls.edge.campware.org), are there
    > other examples of plugins already in practice? Can I get some sample
    > templates (with lots of comments) from those using the plugins already?
    >
    >
    >
    > Hope this list isn't too big. I'm actually quite excited about plugins, and
    > want to make sure the documentation really makes it clear how to use them.
    >
    >
    > doug
    >
    >
Add a Comment