Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

there are 2 issues with using QML:

1. Resource usage - the more libs we load, the more RAM we use.
2. hildon-desktop integration

You don't need alopex for Qt5, embedlite repo already has QT5 ui https://github.com/tmeshkova

BTW feel free to join #embedlite on mozilla.org to discuss issues, etc

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

Thanks for the repo link. About resource usage: a QtQuick application in Qt5 does not need libQt5Widgets, which is larger than libQt5Qml and libQt5Quick combined.

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

Could be, but Qt5 integration with hildon-desktop is missing at all iiuc. And having yet another qt library(ies) loaded along qt4 would be an overkill. Though who knows how it will behave, I might be totally wrong as well :)

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

[OT]: Lets go back to the roots, and drop Qt4 too, who needs parasites sitting in RAM? For N900, GTK uber allez! *naive dreaming*[/OT]

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

qml is nice, maybe I'll be able to help :)

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

OK, I have an idea what can be done. Let's temporarily drop the fremantle alopex ui, just stick with the same UI as on harmattan. When it works, let's push it further.

First of all: how the hell can I build the whole thing? Checked out xulrunner-package by tmeshkova but it complains 'bout scratchbox2 and harmattan target

You don't want parasites in RAM? Just find a way out for applauncherd, as it has something borked under fremantle. Harmattan uses it, Sailfish uses it, so we should utilize it too.

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

applauncherd seems possible, but as soon as I have no feedback, I won't carry on with anything. Seems that hardly one cares. If I get a stable base, I can go ahead, but I won't just reinvent the wheel.

First I need an instruction how to built the whole contraption. What has been changed and what not?

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

i would offer to help, but at the moment all my projects are on hold because of a problem with my build environment. anything newer than kernel 3.8 causes /usr/bin/moc to segfault when building qt apps. kept a version around for dev work but now Xephyr crashes trying to start UI in scratchbox. trying to find time to shift development to another machine in a debian 7 vm.

got some time next week so if you can give a difinitive link to source (which one is current ui based on, whose fork etc) i'll see if i can build current fremantle version of alopex. if it builds i'll have a play around see if there's anything i can contribute.

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

I have no idea what qwazix used, but I used tmeshkova's repo from github (i think its best to start with the normal harmattan ui)
maybe qwazix or fmg would know something interesting about the whole stuff

Re: [WIP] Alopex: a mozilla embedlite implementation on fremantle
 

did manage to get a vm set up and working yesterday. i like the ui that was in the original maemo preview as it was similar to microb. i think it would be better sticking with something like that but in qt not qml.

i can't remember the exact reason for not using gtk (issue gl canvas is floating around in my head), but we have some underlying components of microb reverse engineered, jonwill iirc did some. would it not be better to aim at making it a drop in replacement for what we already have.