No subject
Mon Jun 27 01:00:52 CEST 2011
applications and libraries available in the WeTab package repositories.
> The download of offline routing maps should work in either version. To
> have offline routing working, you also need the monav routing daemon
> (version 0.2 or 0.3) installed. This shouldn't be too hard if you can
> compile it somehow. Maybe even one of the binary versions [1] works on
> the WeTab.
WeTab has an Intel Atom processor so it can probably run most x86 binaries,
I haven't tried it yet and I also didn't research which system libraries it
uses (this can be quite a mess in embedded Linux world).
> The N900 version of Marble works great on the N900, but it won't be easy
> to extend it to other devices in that way. Still we are much interested
> in doing that. Therefore we're currently trying to make it easier to
> create Marble "applications" optimized for certain device form factors.
>
> Marble today looks like this:
>
> [Marble library]
> [Marble KDE application] || [Marble Qt application] || [Marble Qt
application, smallscreen profile]
>
> The vast majority of all code is part of the library, the applications
> are rather small. Nevertheless the QWidget based parts don't work too
> well on touchscreens and adjustments for different form factors could be
> easier. Therefore I'd like future Marble versions to go into this
direction:
>
> [Marble library] || [Marble QtDeclarative/Qt-Components/QML support]
> [Marble Desktop] || [Marble Maemo] || [Marble MeeGo] || [Marble Android*]
|| [Marble Active**] || [Marble Touch]] ...
>
> Each of the applications should be a small .qml application that
> combines the common QML/QtDeclarative/Qt-Components into a user
> interface optimized for a certain device form factor (and/or use case(s)).
>
> No doubt it will be much work to realize this, but fortunately we
> already made some progress: There are first QtDeclarative classes that
> export parts of Marble to QML, and sample .qml applications that show
> this. I'll work more on that in the future, next thing will be routing
> support (such that routes can be configured from .qml applications).
> Daniel Marth is working on a Marble .qml application for MeeGo that will
> make use of Qt-Components and the existing QML/QtDeclarative bindings.
> This is a GSOC project, so expect much progress here soon. Additionally
> Niko Sams has started working on an Android port.
>
> Please join us if the above sounds interesting; there are many open
> things to work on. A good start might be to get one of the qml examples
> running on the WeTab. There's a short introduction to those examples in
[2].
First I'll install the SDK for WeTab and do a few tests with QML (I haven't
had the chance to work with it yet), then I'll play around with the QML
examples that you mentioned.
I'll probably ask a few more questions when I get started :)
Could you send me some links for my first steps with Marble?
Regards,
Djuro Drljaca
--000e0cd2584c84fe3504a6dd1524
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
> I guess it is the Qt version of Marble. In that case you could start i=
t<br>> with the --smallscreen parameter which will make it run like the =
N900<br>> version. Possibly this won't be a too good choice, though:=
The behavior<br>
> of Qt on the N900 is quite different to Qt on other systems, so I'=
d<br>> expect some oddities.<br><br>The option "--smallscreen"=
does not exist.<br><br>The output I get from "marble -v" is:<br>
Qt: 4.7.0<br>KDE Development Platform: 4.5.4 (KDE 4.5.4)<br>Marble Desktop =
Globe: 0.10.3<br><br>From this I think it should be a "KDE version&quo=
t;. Also there are other KDE applications and libraries available in the We=
Tab package repositories.<br>
<br>> The download of offline routing maps should work in either version=
. To<br>> have offline routing working, you also need the monav routing =
daemon<br>> (version 0.2 or 0.3) installed. This shouldn't be too ha=
rd if you can<br>
> compile it somehow. Maybe even one of the binary versions [1] works on=
<br>> the WeTab.<br><br>WeTab has an Intel Atom processor so it can prob=
ably run most x86 binaries, I haven't tried it yet and I also didn'=
t research which system libraries it uses (this can be quite a mess in embe=
dded Linux world).<br>
<br>> The N900 version of Marble works great on the N900, but it won'=
;t be easy<br>> to extend it to other devices in that way. Still we are =
much interested<br>> in doing that. Therefore we're currently trying=
to make it easier to<br>
> create Marble "applications" optimized for certain device fo=
rm factors.<br>> <br>> Marble today looks like this:<br>> <br>>=
[Marble library]<br>> [Marble KDE application] || [Marble Qt applicatio=
n] || [Marble Qt application, smallscreen profile]<br>
> <br>> The vast majority of all code is part of the library, the app=
lications<br>> are rather small. Nevertheless the QWidget based parts do=
n't work too<br>> well on touchscreens and adjustments for different=
form factors could be<br>
> easier. Therefore I'd like future Marble versions to go into this =
direction:<br>> <br>> [Marble library] || [Marble QtDeclarative/Qt-Co=
mponents/QML support]<br>> [Marble Desktop] || [Marble Maemo] || [Marble=
MeeGo] || [Marble Android*] || [Marble Active**] || [Marble Touch]] ...<br=
>
> <br>> Each of the applications should be a small .qml application t=
hat<br>> combines the common QML/QtDeclarative/Qt-Components into a user=
<br>> interface optimized for a certain device form factor (and/or use c=
ase(s)).<br>
> <br>> No doubt it will be much work to realize this, but fortunatel=
y we<br>> already made some progress: There are first QtDeclarative clas=
ses that<br>> export parts of Marble to QML, and sample .qml application=
s that show<br>
> this. I'll work more on that in the future, next thing will be rou=
ting<br>> support (such that routes can be configured from .qml applicat=
ions).<br>> Daniel Marth is working on a Marble .qml application for Mee=
Go that will<br>
> make use of Qt-Components and the existing QML/QtDeclarative bindings.=
<br>> This is a GSOC project, so expect much progress here soon. Additio=
nally<br>> Niko Sams has started working on an Android port.<br>> <br=
>
> Please join us if the above sounds interesting; there are many open<br=
>> things to work on. A good start might be to get one of the qml exampl=
es<br>> running on the WeTab. There's a short introduction to those =
examples in [2].<br>
<br>First I'll install the SDK for WeTab and do a few tests with QML (I=
haven't had the chance to work with it yet), then I'll play around=
with the QML examples that you mentioned.<br><br>I'll probably ask a f=
ew more questions when I get started :)<br>
<br>Could you send me some links for my first steps with Marble?<br><br>Reg=
ards,<br>Djuro Drljaca<br>
--000e0cd2584c84fe3504a6dd1524--
More information about the Marble-devel
mailing list