And to answer your question, the current Moovida framework was designed
to allow multiple frontends but the fact is that no one (to my
knowledge) uses that aspect of the architecture. We basically always use
the pigment frontend...
Anyway, feel free to join us on #elisa @ irc.freenode.net and ask us
more questions. :)
Philippe
Le jeudi 27 août 2009 à 12:22 +0000, max.ott a écrit :
> On 10/08/2009, at 7:18 PM, Philippe Normand wrote:
>
> > python -c "import elisa; print elisa"
>
> I removed the package, and reinstalled everything.
>
> $ python -c "import elisa; print elisa"
> <module 'elisa' from '/home/max/src/elisa/elisa/elisa-plugins/elisa/
> __init__.pyc'>
>
>
> But when I run the weather plugin:
>
> $ python elisa-core/bin/moovida weather.config
>
> .....
>
>
> Traceback (most recent call last):
> File "/usr/local/lib/python2.6/dist-packages/Twisted-8.2.0-py2.6-
> linux-i686.egg/twisted/internet/gtk2reactor.py", line 225, in simulate
> self.runUntilCurrent()
> File "/usr/local/lib/python2.6/dist-packages/Twisted-8.2.0-py2.6-
> linux-i686.egg/twisted/internet/base.py", line 757, in runUntilCurrent
> call.func(*call.args, **call.kw)
> File "/usr/local/lib/python2.6/dist-packages/Twisted-8.2.0-py2.6-
> linux-i686.egg/twisted/internet/task.py", line 251, in _tick
> result = iterator.next()
> File "/home/max/src/elisa/elisa/elisa-core/elisa/core/manager.py",
> line 101, in load_components_iter
> dfr = plugin_registry.create_component(component_name)
> --- <exception caught here> ---
> File "/home/max/src/elisa/elisa/elisa-core/elisa/core/
> plugin_registry.py", line 1103, in create_component
> component_class = reflect.namedAny('%s.%s' % (module, klass))
> File "/usr/local/lib/python2.6/dist-packages/Twisted-8.2.0-py2.6-
> linux-i686.egg/twisted/python/reflect.py", line 456, in namedAny
> topLevelPackage = _importAndCheckStack(trialname)
> File "/home/max/.moovida/plugins/elisa_plugin_ipod-0.2.egg/elisa/
> plugins/ipod/ipod_resource.py", line 28, in <module>
>
> exceptions.ImportError: No module named gpod
>
> ....
>
> Ultimately, I get the full Moovida screen. I just want the weather
> GUI, nothing else. I thought that's what I get for with a config file,
> such as:
>
> [general]
> resource_providers = ['weather.report_provider:WeatherReportProvider']
> frontends = ['weather_frontend']
>
> [weather_frontend]
> frontend = 'pigment.pigment_frontend:PigmentFrontend'
> controller_path = '/elisa/weather'
>
> [weather.weather_controller:WeatherController]
> station = 'LEBL'
>
>
> Maybe the saner question to ask at this stage. Does it even make sense
> at this stage for somebody outside the core development team to try to
> use this framework beside just running the app and watch movies? Don't
> get me wrong, I have written plenty of software which only the very
> brave want to build on top. But I'm getting very frustrated of seeing
> all this error messages and having no idea what they mean nor where to
> start.
>
> All I want to do at this stage is re-creating the tutorial.
>
> Cheers,
>
> -max
>
Try:
python elisa-core/ bin/moovida -c weather.config
And to answer your question, the current Moovida framework was designed
to allow multiple frontends but the fact is that no one (to my
knowledge) uses that aspect of the architecture. We basically always use
the pigment frontend...
Anyway, feel free to join us on #elisa @ irc.freenode.net and ask us
more questions. :)
Philippe
Le jeudi 27 août 2009 à 12:22 +0000, max.ott a écrit : max/src/ elisa/elisa/ elisa-plugins/ elisa/ bin/moovida weather.config lib/python2. 6/dist- packages/ Twisted- 8.2.0-py2. 6- egg/twisted/ internet/ gtk2reactor. py", line 225, in simulate rrent() lib/python2. 6/dist- packages/ Twisted- 8.2.0-py2. 6- egg/twisted/ internet/ base.py" , line 757, in runUntilCurrent *call.args, **call.kw) lib/python2. 6/dist- packages/ Twisted- 8.2.0-py2. 6- egg/twisted/ internet/ task.py" , line 251, in _tick max/src/ elisa/elisa/ elisa-core/ elisa/core/ manager. py", _iter registry. create_ component( component_ name) max/src/ elisa/elisa/ elisa-core/ elisa/core/ registry. py", line 1103, in create_component namedAny( '%s.%s' % (module, klass)) lib/python2. 6/dist- packages/ Twisted- 8.2.0-py2. 6- egg/twisted/ python/ reflect. py", line 456, in namedAny Stack(trialname ) max/.moovida/ plugins/ elisa_plugin_ ipod-0. 2.egg/elisa/ ipod/ipod_ resource. py", line 28, in <module> ImportError: No module named gpod report_ provider: WeatherReportPr ovider' ] frontend' ] pigment_ frontend: PigmentFrontend ' weather_ controller: WeatherControll er]
> On 10/08/2009, at 7:18 PM, Philippe Normand wrote:
>
> > python -c "import elisa; print elisa"
>
> I removed the package, and reinstalled everything.
>
> $ python -c "import elisa; print elisa"
> <module 'elisa' from '/home/
> __init__.pyc'>
>
>
> But when I run the weather plugin:
>
> $ python elisa-core/
>
> .....
>
>
> Traceback (most recent call last):
> File "/usr/local/
> linux-i686.
> self.runUntilCu
> File "/usr/local/
> linux-i686.
> call.func(
> File "/usr/local/
> linux-i686.
> result = iterator.next()
> File "/home/
> line 101, in load_components
> dfr = plugin_
> --- <exception caught here> ---
> File "/home/
> plugin_
> component_class = reflect.
> File "/usr/local/
> linux-i686.
> topLevelPackage = _importAndCheck
> File "/home/
> plugins/
>
> exceptions.
>
> ....
>
> Ultimately, I get the full Moovida screen. I just want the weather
> GUI, nothing else. I thought that's what I get for with a config file,
> such as:
>
> [general]
> resource_providers = ['weather.
> frontends = ['weather_
>
> [weather_frontend]
> frontend = 'pigment.
> controller_path = '/elisa/weather'
>
> [weather.
> station = 'LEBL'
>
>
> Maybe the saner question to ask at this stage. Does it even make sense
> at this stage for somebody outside the core development team to try to
> use this framework beside just running the app and watch movies? Don't
> get me wrong, I have written plenty of software which only the very
> brave want to build on top. But I'm getting very frustrated of seeing
> all this error messages and having no idea what they mean nor where to
> start.
>
> All I want to do at this stage is re-creating the tutorial.
>
> Cheers,
>
> -max
>