Re: [PiTiVi] Plugin-docs

[Gordon Allott <gordallott@gm...>]

Hi,
I finally got around to getting going on plugin writing so i just want
to check with you guys that I'm heading in the right direction.
Basically i just created a file named plugin.py that is defined as
follows:

#!/usr/bin/env python
#       plugin.py
#
#       Copyright 2008 Gordon Allott <gordallott@...>
#
#       This program is free software; you can redistribute it and/or
modify
#       it under the terms of the GNU General Public License as
published by
#       the Free Software Foundation; either version 3 of the License,
or
#       (at your option) any later version.
#
#       This program is distributed in the hope that it will be useful,
#       but WITHOUT ANY WARRANTY; without even the implied warranty of
#       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#       GNU General Public License for more details.
#
#       You should have received a copy of the GNU General Public
License
#       along with this program; if not, write to the Free Software
#       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
#       MA 02110-1301, USA.
#
#


from zope.interface import Interface, Attribute
import zope.interface as interface
from pitivi import plugincore

class Plugin:

    interface.implements(plugincore.IPlugin)
    name = 'test plugin'
    catagory = 'test'
    description = 'a test plugin, just gets the interface going'
    version = 1.0
    authors = 'Foobar'
    settings = ['foo', 'bar']
    enabled = True

    def __call__(self, manager):
        """ called when the plugin is loaded? """
        self.manager = manager
        print "Hello World! this is a __call__ function"


    def __init__(self, manager=None):
        self.__call__(manager)


I'm not so sure about the __init__ and call separation, it looks like
IPlugin wants to call __call__ when it loads the plugin
(pluginmanager.py: 361) passing it the manager, just like it specifies
in the IPlugin instance class but instead __init__ gets called.
 
-- 
Gordon Allott <gordallott@...>

[PiTiVi] Plugin-docs

[Gordon Allott <gordallott@gm...>]

Hi,
Does anyone happen to have any barebones plugin code laying around? from
the wiki plugin design document and a quick look at IPlugin it seems it
needs zope's interface code but its all a little confusing as to 'how to
just get up and running' 

it would be great if someone had some 'hello world' plugin example that
just created a gtk window with a hello world label or something :)
 
-- 
Gordon Allott <gordallott@...>

Re: [PiTiVi] Plugin-docs

[Edward Hervey <bilboed@gm...>]

Hi,

  There were some examples in tests/ but disabled because of autotools
stupidity :(
  The other problem is that... well there's no specific plugin API. You
can just create your code and add it anywhere, which isn't really ideal.
  Hopefully, once SoC is over, we'll be able to write more docs/plugins.

   Edward

On Wed, 2008-07-23 at 16:43 +0100, Gordon Allott wrote:
> Hi,
> Does anyone happen to have any barebones plugin code laying around? from
> the wiki plugin design document and a quick look at IPlugin it seems it
> needs zope's interface code but its all a little confusing as to 'how to
> just get up and running' 
> 
> it would be great if someone had some 'hello world' plugin example that
> just created a gtk window with a hello world label or something :)
>  
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________ Pitivi-pitivi mailing list Pitivi-pitivi@... https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi

Re: [PiTiVi] Plugin-docs

[Brandon Lewis <brandon_lewis@be...>]

Edward Hervey wrote:
> Hi,
> 
>   There were some examples in tests/ but disabled because of autotools
> stupidity :(
>   The other problem is that... well there's no specific plugin API. You
> can just create your code and add it anywhere, which isn't really ideal.
>   Hopefully, once SoC is over, we'll be able to write more docs/plugins.
> 
>    Edward

Or, if you wanted to work on improving the plugin architecture, we'd certainly 
offer what support we can. Even document what's already been done would be a big 
help.

Re: [PiTiVi] Plugin-docs

[Gordon Allott <gordallott@gm...>]

Hi,
I finally got around to getting going on plugin writing so i just want
to check with you guys that I'm heading in the right direction.
Basically i just created a file named plugin.py that is defined as
follows:

#!/usr/bin/env python
#       plugin.py
#
#       Copyright 2008 Gordon Allott <gordallott@...>
#
#       This program is free software; you can redistribute it and/or
modify
#       it under the terms of the GNU General Public License as
published by
#       the Free Software Foundation; either version 3 of the License,
or
#       (at your option) any later version.
#
#       This program is distributed in the hope that it will be useful,
#       but WITHOUT ANY WARRANTY; without even the implied warranty of
#       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#       GNU General Public License for more details.
#
#       You should have received a copy of the GNU General Public
License
#       along with this program; if not, write to the Free Software
#       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
#       MA 02110-1301, USA.
#
#


from zope.interface import Interface, Attribute
import zope.interface as interface
from pitivi import plugincore

class Plugin:

    interface.implements(plugincore.IPlugin)
    name = 'test plugin'
    catagory = 'test'
    description = 'a test plugin, just gets the interface going'
    version = 1.0
    authors = 'Foobar'
    settings = ['foo', 'bar']
    enabled = True

    def __call__(self, manager):
        """ called when the plugin is loaded? """
        self.manager = manager
        print "Hello World! this is a __call__ function"


    def __init__(self, manager=None):
        self.__call__(manager)


I'm not so sure about the __init__ and call separation, it looks like
IPlugin wants to call __call__ when it loads the plugin
(pluginmanager.py: 361) passing it the manager, just like it specifies
in the IPlugin instance class but instead __init__ gets called.
 
-- 
Gordon Allott <gordallott@...>

Re: [PiTiVi] Plugin-docs

[Gordon Allott <gordallott@gm...>]

Oh also, I am not sure about how to go about interfacing with pitivi,
all i really need to do is add a menu entry and be able to add clips to
the workspace, does such an interface exist? 
If not i can try hacking one up if someone can point me in the right
direction as to what are the main class instances that should be
provided to a plugin. 
-- 
Gordon Allott <gordallott@...>