Re: Looking for help from a GTK guy with 2 projects

[Michael Hasselmann]

On Tue, 2011-11-15 at 11:05 +0200, Mohammad Abu-Garbeyyeh wrote:
> How else does the main window / ux show then?

It uses QWidgets as viewports, and then uses Qt Graphics View. So it's
not something like one QWidget per key or such, that's why I simply
don't believe the painting speed difference matters too much, if it's
only one QWidget.

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Looking for help from a GTK guy with 2 projects

[Michael Hasselmann]

On Mon, 2011-11-14 at 12:44 +0200, Mohammad Abu-garbeyyeh wrote:
> Although probably related to memory usage, painting Qt widgets takes
> much more time than Gtk ones (on Fremantle), for apps this may be ok,
> but for something that has to show quickly this may not be acceptable

Maliit is not painting QWidgets. Perhaps you should check the painting
performance first?

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Re: Looking for help from a GTK guy with 2 projects

[Michael Hasselmann]

On Mon, 2011-11-14 at 10:23 +0200, Ивайло Димитров wrote:
> Meh. The reason why QT keyboard would not be acceptable to replace
> hildon vkb is very simple - QT memory footprint. Did you forget n900
> comes with 256MB of RAM? And running even simple QT/QML application
> consumes about 8%-10% of that? While it sounds very good in theory, in
> practice(under memory pressure) it would just slow the device even
> further.

Memory footprint is an issue, but most of it should be shared unless you
plan to never ever run any other Qt app on the N900.

Also, why not tackle the memory footprint? As it seems, Qt is not using
a slab allocator. So even for a "simple" QString, the PIMPL and the
QMetaObject are seemingly heap-allocated. Memory trashing is a real
concern.

Glib has been using slab allocators for ages, perhaps the time has come
for Qt to use more than the Glib mainloop ;-)

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Looking for help from a GTK guy with 2 projects

[Michael Hasselmann]

On Sun, 2011-11-13 at 17:53 +0800, Jonathan Wilson wrote:
> > Have you considered Maliit?
> > http://wiki.maliit.org/Documentation/Installing#Maemo_5_.28Fremantle.29
> That looks nice but:
> 1.Its clearly stated that its use on Maemo5 is "not ready for prime time"
> 2.Its written in QT (and not only that, it uses QT version labeled 
> "experimental") and takes over a lot more of the input system than I would 
> like (including not using Maemo keyboard layouts which is something I want 
> to keep doing)
> and 3.There is no way Maliit or anything based on it would be accepted into 
> the CSSU because of #1 and #2. (and the CSSU is the eventual target for any 
> keyboard replacement.

Huh? You sound a bit confused, my friend. Since when would being
Qt-based be a reason against inclusion in CSSU? These days, QML + PySide
is all the rage, and Qt has been in base Maemo5 image for ages now.

Maliit is not ready for prime-time for Fremantle because no one is
actively working on it. What I did back then was a proof of concept,
nothing more.

We do have GTK+ support and we even took in some matchbox-specific
patches. But you need to scratch your own itch. You cannot expect others
to do it for you. That's just how open-source works. So yes, it requires
someone to work on it, and while it won't be me, I'll gladly accept
patches. In an open-source community, your first argument simply doesn't
hold.

You also seem to ignore that it wouldn't only be the MeeGo Keyboard from
Harmattan that you could get (together with all the language layouts
that have gone through extensive usability tests). Maliit is a fully
pluggable framework. Hildon IM was that, too, which is no surprise, as
Maliit is the legitimate successor of Hildon IM – in fact, it's been
designed by the same architect. The architecture allows the possibility
to run other Maliit plugins, Swype being one of them (on the N9), see
http://wiki.maliit.org/Plugins

Sorry to sound harsh, but your arguments appear to belong in the
category of rationalize-after-the-fact (of having decided to go with
reverse engineering hildon-im-vkbrenderer). I know that you're looking
for a cool hack, and I wish you good luck with that. But why not invest
your time in something with wider benefits and contribute to an active
project?

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Harmattan Python is available

[Michael Hasselmann]

On Tue, 2011-06-21 at 19:26 -0300, Luciano Wolf wrote:
> Supported on Nokia's N9 phone and preloaded on the Nokia N950 developer
> device as well as the Harmattan Platform SDK

That means end users would have to install PySide first?

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Stopping QML update when not visible

[Michael Hasselmann]

On Mon, 2011-05-30 at 17:35 +0200, Cornelius Hald wrote:
> To improve the drawing performance a bit more, you should not stack
> several Rectangles if you can't actually see the bottom ones. QML will
> first paint the bottom rectangle, then paint the second rectangle over
> it etc. Use Item instead as the container element.

Hahahahahahahah, what? Like, really? What a quirky workaround, and how
absolutely not-scene-graph-y at all.  If that's not reason enough to
just go and fix , with
QML2 and its  supposedly better QML scene graph still being months away
(and QGraphicsView being used in real world apps for years to come),
then I don't know what else it.

Anyway, about just setting those rectangles you dont want to be painted
to fully translucent?

regards,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Request: Tutorials & use-cases for documentation

[Michael Hasselmann]

> ext Gary Birkett wrote:
> > there is more than one method of doing everything.

But that's part of the problem, at least for newcomers. They look for
the best/easiest way, most likely.

Am Freitag, den 12.02.2010, 10:29 +0200 schrieb Quim Gil: 
> There is a good point behind this which is how to cross use cases with
> technologies. I don't think the answer is to aim to cover all
> technologies equally for each use case e.g.
> How to get a nice % progress bar

I wouldn't neccessarily expect that the solution to a usecase looks
similar with each toolkit. If you then start to explain the exceptions
(and why things are different) then you'll quickly blow up the size of
the tutorial-style usecase, without helping the reader. It'll only add
to the confusion.

> I guess developers first make a decision about the toolkit they are
> going to use and then expect to find documentation specific to that
> toolkit. Cross-links are nice but that's it.
> [...]
> Looking at http://wiki.maemo.org/Documentation/Use_case_template it is
> not clear whether such links should be placed in the intro, Related
> APIs... Tips & Tricks would force the template too much.

A title suffix such as " (gtkmm)" plus wiki categories would help if
one wanted to make usecases available for all toolkits.

regards,
Michael


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Considering /opt and MyDocs in your packages

[Michael Hasselmann]

Hi,

Am Mittwoch, den 09.09.2009, 14:25 +0300 schrieb Quim Gil:

> As a workaround, the /opt directory
> has been linked to a different partition with more space (about 1 GB)

[snipped]

> In summary, you can't really put programs, libraries or theme graphics
> into /home/user/MyDocs. Instead, use /opt for these.

1 GB might be a bit limiting in that case, no? Perhaps 2 GB would be
more appropiate. At least that would allow the /usr/share of my box to
fit into it (yeah, comparing apples with oranges ... maybe).

regards,
Michael




___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Missing dependencies on build bot system

[Michael Hasselmann]

Hello list,

I tried to build a package with Maemo's build bots. However, the build
failed during the configure check and now the log contains this:

"Package hildon-notify was not found in the pkg-config search path.
Perhaps you should add the directory containing `hildon-notify.pc'
to the PKG_CONFIG_PATH environment variable
Package 'hildon-notify', required by 'hildon-notifymm', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix."

Any ideas how to solve that dependency problem?

thanks in advance,
Michael

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers