Linked by Thom Holwerda on Wed 22nd Aug 2012 19:54 UTC
Thread beginning with comment 531970
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by shmerl
by shmerl on Fri 24th Aug 2012 07:55
in reply to "RE[3]: Comment by shmerl"
Nemo is for handsets, built on Mer, and has a UI based on QT. Isn't Plasma Active also based on QT? And Jolla will build something based on QT and on a handset, but it won't be Nemo.
Qt is a base library which doesn't force you how UI should look and it can be used with various DEs and window managers, mobile and desktop ones.
Plasma Active uses KWin and their user interface to create a mobile optimized UX. Nemo is using Lipstick QML desktop to create the user experience. Jolla didn't really explain what they'll use besides Mer core and potentially some parts of Nemo to create their UX.
However, all these derivatives share common architecture - they are all conventional Linux (using either X.org or Wayland unlike Android which is incompatible with above) and common libraries (see http://gitweb.merproject.org/gitweb ).
So if you write a mobile Linux application using those libraries (including Qt for the interface for example) - you'll be able to build it for any of those distributions. Note that they can be built for various architectures (x86, ARMv7hl, ARMv7l, MIPS and etc.). So if you figure out what device you target - you can build your application for it for example with cross compilation (see
https://wiki.merproject.org/wiki/Platform_SDK
http://wiki.merproject.org/wiki/Platform_SDK_and_SB2
Adjusting your application to various form factors (different tablets, handsets and etc.) is the question of your design and flexibility of that application, it's not bound to the distribution per se. If you want to fit a certain theme/style that's already another question.
Android does all three, so I know how to write an app for that. How exactly do I write a... Mer app?
Mer is not an end user distro. Writing a "Mer app" means creating some library or runtime for example.
Nemo app?
GUI mobile application with Qt. You can compile it for Nemo target using the Mer SDK.
Are they all the same? Do they interoperate at all?
Mer derivatives aren't the same, but they are close enough to make porting between them easy. If architecture matches, one can potentially run some application even without recompilation, but there can be version differences and other specifics. In most cases you can just compile your program for different Mer based targets and that's it.
All the docs seem to be aimed at people putting stuff on hardware, or people looking to contribute straight to one of the projects, and there's stuff for writing QT apps... but what do I do as a potential App writer?
You can start with getting familiar with using Mer SDK. There are Hello World examples on the SDK & SB2 page:
https://wiki.merproject.org/wiki/Platform_SDK_and_SB2
Mer also allows using OBS.
Edited 2012-08-24 08:01 UTC




Member since:
2010-05-21
I'm still a little confused. Nemo is for handsets, built on Mer, and has a UI based on QT. Isn't Plasma Active also based on QT? And Jolla will build something based on QT and on a handset, but it won't be Nemo.
Android does all three, so I know how to write an app for that. How exactly do I write a... Mer app? Nemo app? Are they all the same? Do they interoperate at all?
All the docs seem to be aimed at people putting stuff on hardware, or people looking to contribute straight to one of the projects, and there's stuff for writing QT apps... but what do I do as a potential App writer?