[maemo-developers] Questions about HildonPannableArea

[From: Till Harbaum]

Hi,

currently i have just returned to a scrolled window instead of the pannable
area and i am not completely unsatisfied with this as text selection
still works this way.

So unless there's be a method to use selections again with pannable
areas i'd actually prefer if you don't change anything. This gives me a somewhat
inconsistent mixture of scrolled windows and pannable areas but selections
is important to me in that main html window (these are geocaching descriptions
displayed there and sometimes i copy formulas etc over to a gtktextview to
work on them there).

The coolest thing would of course be if selection can be enabled in a pannable
are as well. If that's the case i wouldn't mind if you completely remove the built-in
panning support from gtkhtml.

If there are no plans for selection support in pannable areas, how is this then to 
be solved? Is the "fremantle xterm" solution the way to go?

Till

----- original Nachricht --------

Betreff: Re: Questions about HildonPannableArea
Gesendet: Mo, 08. Jun 2009
Von: Claudio Saavedra<csaavedra at igalia.com>

> El mié, 03-06-2009 a las 20:54 +0200, Till Harbaum / Lists escribió:
> > Hi,
> > 
> > Am Mittwoch 03 Juni 2009 schrieb Alejandro Garcia Castro:
> > > I do not know about the current status of out gtkhtml code, but I
> > > think probably we will have to add a parameter to deactivate it in the
> > > gtkhtml widget, or maybe just ifdef it or remove it.
> > There's no such property in gtkhtml. And what do you mean by "ifdef" it?
> > I sure won't remove that feature from gtkhtml as this would then affect
> > _all_ applications.
> 
> You are right, there is no such property. In maemo, GtkHtml was patched,
> a long time ago, to allow panning when dragging on the widget. This
> panning is currently interfering with the way the pannable area works
> and it can't be disabled nor configured.
> 
> There are two plausible approaches to fix this in GtkHtml (which I'm
> currently weighting):
> 
> 1. Remove the patch to allow panning in the GtkHtml widget. This has the
> advantage to be a quite straightforward solution. The con is that any
> application relying on this feature will loose panning until they
> migrate to use a pannable area.
> 
> 2. Make this hardcoded panning feature a property, enabled by default.
> The advantage of this approach is that no application is broken and
> those willing to use a pannable area have the chance to disable the
> property. The disadvantage of this is that it will probably take some
> extra effort and time to implement it, that I could pretty well use in
> more relevant issues.
> 
> Personally, I'm more inclined to go for (1). Mainly, because GtkHtml, as
> André pointed out, is a dead-end widget, and any extra efforts on it are
> probably not worth. Anyone willing to get a nice and consistent panning
> experience in Fremantle should use a pannable area.
> 
> Nevertheless, I'd read some opinions before doing anything.
> 
> Claudio
> 
> 
> 

--- original Nachricht Ende ----