Scrolling a list

[Sander van Grieken]

On Friday 21 March 2008 10:00:30 Tick wrote:
> Hi Raster,
>     I used ETK tree and vbox to make list and put them into assassin as
> you suggested.
> After thinking about how to make the list scrollable by finger, I have
> to following ideas.
>
> 1.     Let the vbox catch events and decide if it is a scrolling event
> and scroll the tree.
> 1.5                                  Or sending wheel event to tree.
>
> 2. Let Window Manager knows that press and drag up/down is a wheel event
> and send the event to the object that pressed.
>
> For the first idea, each application will have to manage their own
> behavior themselves, but I think it is not hard to implement.
>
> For the second idea. This will also defines the whole user experience of
> NEO. Like press and drag right may equals mouse right key clicked , and
> drag up means wheel rolls up for instance.
>
> If you choose the second choice, we can base on this behavior and
> designed our own usage experience.  And some old GUI applications
> designed for mouse  and desktop interface may behavior strangely.
>
> Do you have any suggestions, or better idea?

I just built EWL from cvs and it has a 'kinetic scrollpane' component that 
does what you describe.

Which leads me to my next question:

It seems both ETK and EWL are both widget toolkits. Which of them is the 
preferred one? They both have their merits AFAICS (ewl can be used together 
with pure edje, etk can use glade for UI definitions), but which one will be 
maintained?

Also, is there any work being done on eflpp? and python-efl?

A while back I did quite some work on python bindings for ETK, but it was then 
decided to create bindings by parsing/generating from the C headers, which 
Caio from INdT would work on fulltime I was told. Is there any progress made? 
eflpp binding/wrapping is done manually judging from CVS. Isn't it wise to 
also generate eflpp the same way?

grtz,
Sander