Organisational changes status

Hello Eliseros!

Exactly two months ago were announced important organisational changes
including:
- move from Subversion to Bazaar for source code revision control
- move from Trac to Launchpad for bug tracking
- move from Trac to MoinMoin for the wiki
- setup of a procedure for new features from specification to
implementation and integration

Two months later, everything is in place and smoothly running:
- Elisa's code is stored in bazaar branches
(https://code.launchpad.net/elisa)
- all the bugs have been migrated to Launchpad
(https://bugs.launchpad.net/elisa)
- the up to date content of the Trac wiki is now on the brand new
MoinMoin (http://elisa.fluendo.com/wiki); the old wiki is still online
but read-only
- specifications for new features are written in the new wiki
(http://elisa.fluendo.com/wiki/Specs) and tracked by Launchpad
(https://blueprints.launchpad.net/elisa)
- ... once implemented the new features are sent for review on a mailing
list; the merge requests are also tracked by a Bundle Buggy instance
(http://elisa.fluendo.com/quality/review)

On top of that a couple of important pieces of work were completed:
- a brand new website (http://elisa.fluendo.com)
- tutorials on the new architecture
(http://elisa.fluendo.com/documentation/tutorials)

New required dependency to run Elisa

Hi guys,

Friday's commit on pigment-python introduced a new dependency:
cssutils. It's needed by the new theming system which uses a css-like
syntax.
It is not packaged in Ubuntu.
Regardless of your system you can use easy_install to download and
install it.

On Ubuntu systems type:

sudo easy_install cssutils

Sorry for the inconvenience,

Florian

Developing a new plugin for elisa

Hi,

I'm a programmer (with little experience in python) and I would like to 
write a simple plugin for elisa,

the plugin called "Launcher" and it should be able to browse directories 
& files and launch a program associated with that within elisa.

(example of use: running a mame rom with mame executable)

Unfortunately  I didn't find enough documentation on elisa's site, the 
wiki, or any other google search that can help me with that.

I've tried the Amazon tutorial, but it failed to setup. (some error 
about "find_packages")

Is there any decent documentation that I can use for it?

its pretty bad, if people won't write plugins for elisa, just because 
lack of documentations.

thanks - leo. 

Re: Developing a new plugin for elisa

I believe the "Getting Started" under the "Participate" part of the
Elisa website (http://elisa.fluendo.com/participate/) would be
sufficient. I think the weather-plugin
(http://elisa.fluendo.com/documentation/tutorials/weather_plugin_tutorial.html)
is a good start.

Best Regards,

Jens

On Sun, 2008-06-01 at 20:37 +0200, Lior Tamam wrote:
> Hi,
> 
> I'm a programmer (with little experience in python) and I would like to 
> write a simple plugin for elisa,
> 
> the plugin called "Launcher" and it should be able to browse directories 
> & files and launch a program associated with that within elisa.
> 
> (example of use: running a mame rom with mame executable)
> 
> 
> Unfortunately  I didn't find enough documentation on elisa's site, the 
> wiki, or any other google search that can help me with that.
> 
> I've tried the Amazon tutorial, but it failed to setup. (some error 
> about "find_packages")
> 
> Is there any decent documentation that I can use for it?
> 

Re: Developing a new plugin for elisa

Hi,

Lior Tamam wrote:
> Hi,
> 
> I'm a programmer (with little experience in python) and I would like to
> write a simple plugin for elisa,
> 
> the plugin called "Launcher" and it should be able to browse directories
> & files and launch a program associated with that within elisa.
> 
> (example of use: running a mame rom with mame executable)
> 
> 
> Unfortunately  I didn't find enough documentation on elisa's site, the
> wiki, or any other google search that can help me with that.

It's true that we have very little documentation at the moment, but it
is a work in progress.

> I've tried the Amazon tutorial, but it failed to setup. (some error
> about "find_packages")

Can we have more details on this error? You can drop us a line on IRC
(#elisa  <at>  freenode), we'll be happy to help you get it to work.

> Is there any decent documentation that I can use for it?

As suggested by Jens, give a shot to the weather plugin tutorial.

Re: Developing a new plugin for elisa

As far as I have understood the weather plugin is solely for the 0.5
version. So you defintely have to download the development version,
which again is probably the most reasonable to tag along with, or else
your plugin might be unusable in the near future.

Best Regards,

Jens

On Mon, 2008-06-02 at 22:42 +0200, Lior Tamam wrote:
> Thanks again, i'll try the weather-plugin. will it work with the 0.3.5
> version or should i download the latest development version?
> 
> 
> Jens Fursund wrote:
> 
> > I believe the "Getting Started" under the "Participate" part of the
> > Elisa website (http://elisa.fluendo.com/participate/) would be
> > sufficient. I think the weather-plugin
> > (http://elisa.fluendo.com/documentation/tutorials/weather_plugin_tutorial.html)
> > is a good start.
> > 
> > Best Regards,
> > 
> > Jens
> > 
> > On Sun, 2008-06-01 at 20:37 +0200, Lior Tamam wrote:
> >   
> > > Hi,
> > > 

Idea for Plug-in transitions.

These are thoughts about transitions between plug-in views. 
Especially after I had a chat with Kaleo, yesterday, I would like to
post my thoughts about this. 

h1. Transitions

h2. Introduction

Some plug-ins need different views for themselves. For example a player
plug-in could have a view with a list of files and a view to play a file
(or the list). In one view the list is in foreground and the player in
the back and in the other view it is vice versa. As for now the
Elisa-Project holds only experimental support in thezerofive branch to
handle the transition and programming of these views.
These are only in Draft state and far from final, furthermore it seems
the structure is not fully implemented, yet. We will create a Plug-in
with multiple views to demonstrate the way these transitions could
work. 

h2. Idea

The Idea behind our plug-in is to get closer to the
model-controller-view pattern and be flexible in the design of each
view. Furthermore impressive transitions will be made possible. Our
plug-ins will have a modell for calculations and data-access to external
libraries/sources. Also it will include (atleast) one view. In each view
states of PGM-Drawables will be saved. The controller finally decides
which view to choose for example by user input. 

h2. Example

Re: Developing a new plugin for elisa

Correct, there is no way the plugin tutorials (both weather and amazon)
will work with versions prior to 0.5, they have been written
specifically for this branch.

 <at> Lior, have a look at http://elisa.fluendo.com/participate/ to get you
started with the development branch.
Also, please cc the mailing list when answering, these discussions may
be useful to others.

Regards,

Olivier

Jens Fursund wrote:
> As far as I have understood the weather plugin is solely for the 0.5
> version. So you defintely have to download the development version,
> which again is probably the most reasonable to tag along with, or else
> your plugin might be unusable in the near future.
> 
> Best Regards,
> 
> Jens
> 
> On Mon, 2008-06-02 at 22:42 +0200, Lior Tamam wrote:
>> Thanks again, i'll try the weather-plugin. will it work with the 0.3.5
>> version or should i download the latest development version?
>>
>>
>> Jens Fursund wrote:
>>

User Interface Mirroring

Re: User Interface Mirroring

Hi guys,

Forwarding my answer to Mohamed here :)

First of all I am no expert in UI mirroring. What you did in the piece
of code you sent looks find from a widget point of view. The remaining
question in my view is what the best place to store that parameter
(isRTL) is. My feeling is that it could be an option of the
PigmentFrontend.
What do you think of that?

Florian

Le mardi 03 juin 2008 à 13:05 +0300, Mohamed Imam a écrit :
> Hi All, 
> 
> Please let me share with you a UI requirement that is needed for RTL -
> Right to Left -  interfaces such as Arabic, Hebrew. 
> 
> This requirement is mirroring the user interface controls. 
> 
> For English interface the controls are laid out left to right while
> for RTL interface they are laid out right to left.
> 
> The following article explains the mirroring concept 
> http://www.microsoft.com/globaldev/getwr/steps/WRG_mirror.mspx 
> 
> In Elisa 0.3.5 I have implemented a limited version in some UI
> controls
> 
> A simple equation is used
> 
> Given a widget has x,y 
> Then the mirrored widget x = mx
> 
> mx = parentWidth - x - widgetWidth
> y is the same
> 
> To optimize the RTL support I have created a global application
> variable that I check during UI creation/relayout. Using a function
> named isRTL() 
> 
> 
> Sample change in context_bar.py 
> 
> def compute_layout(self):
>         if not self.parent:
>             return
>         p = 1
>         margin = self.icon_margin * self.parent.height
>         right_margin = self.right_margin * self.parent.height
>         index = 0
>         for i in reversed(self.children):
>             i.size = (self.parent.height - margin*2,
> self.parent.height - margin * 2)
>             x = self.parent.width - i.width * p - margin * (p-1) -
> right_margin
>             i.x = x
>             
>             #Added for RTL Support
>             if isRTL():
>                 i.x = self.parent.width - x - i.width
>             
>             i.y += margin
>             p += 1
>             if self._current_index > -1 and index ==
> self._current_index:
>                 i.opacity = 255
>             else:
>                 i.opacity = self.unselected_opacity
>             index += 1
> 
> 
> def isRTL():
>     return rtl_global
> 
> 
> I wonder if you have any ideas or suggestions on implementing this
> into the new Elisa 0.5.0 to support RTL/LTR interfaces  
> 
> 
> Best regards,
> Mohamed Imam
>