Harmattan UI framework development is opened

[tomasj]

Hi,

We're releasing the Harmattan UI framework as open source today: http://duiframework.wordpress.com/2010/02/15/announcing-the-open-source-release-of-the-maemo-6-ui-framework/

At the same time, we're transitioning to working entirely in public at http://qt.gitorious.org/maemo-6-ui-framework

It's still a work in progress, but already you can check out this very early version from the extras-devel repository by installing the Harmattan Widgets Gallery demo on your Nokia N900.

You should also be able to build and run the examples and demos on your normal Linux, Mac OS X, or Windows desktop. We will be making binary packages available as well, if you just want to see how it looks :)

Regards,
Tomas

[asidana]

dependency for widgets Gallery is missing in extras-devel

[drm]

Will the maemo 6 be released at all? Or shall we say meego1…

[davidmaxwaterman]

dependency for widgets Gallery is missing in extras-devel

Do you have something else that relies on a specific version of Qt? I've tried this on a freshly-flashed device and it works fine, pulling in all dependencies without a problem.

I've seen one instance where it wouldn't install due to a bad dependency, and removing libqt* fixed it, but that also removed a whole bunch of other packages, so you might consider that a little heavy handed - perhaps removing just libqt4-maemo5* is sufficient (and allow the application manager to pull them in again when it installs Widgets Gallery).

I'd be interested to know what you find. Please let us know, and if there's something to correct, we'll do so.

[pelago]

Videos of the Maemo 6 Widgets Gallery demo would be great!

[jak]

Intel already developed a MID UI for Moblin. So will this one then replace Intel's MID UI in MeeGo?

[dubik]

Videos of the Maemo 6 Widgets Gallery demo would be great!

Apparently I can't just send "Soon!" because it's too short.

[thp]

Pretty nice.

Ctrl+B, Ctrl+N and Ctrl+M turn on some overlays (name of widget is N and layout/spacing is M, don't know what B is supposed to do) for debugging.

[aldevil]

how about fixing the problems in Maemo 5 first?

[tomasj]

If you look at the MeeGo architecture picture (http://meego.com/developers/meego-architecture), you will see that there are several reference user interfaces for different classes of devices.

In the same way that it doesn't really make sense to directly port desktop applications to mobile, we are still finding out what works best on different device types. The common factor you can rely on across all MeeGo devices at the moment is Qt. That doesn't necessarily mean a Qt based UI is the optimal fit for a MID type of device. Let's see :)

[tomasj]

Pretty nice.

Ctrl+B, Ctrl+N and Ctrl+M turn on some overlays (name of widget is N and layout/spacing is M, don't know what B is supposed to do) for debugging.

Hah, you found our debug modes :)

Ctrl+B is bounding box visualization (the area a widget paints and reacts in)
Ctrl+N displays object names
Ctrl+M displays widget margins
Ctrl+S toggles object sizes

The really cool one however is Ctrl+R, it rotates the whole UI by 90 degrees at a time so you can test your app in different orientations without needing a special simulator or real hardware.

[tomasj]

how about fixing the problems in Maemo 5 first?

Maemo 5 has a whole separate team focused right now on bringing you lots of goodies in the already announced upcoming PR1.2 release for Maemo 5. Nokia is a pretty big company and Maemo's not so small either anymore, we're capable of multitasking and just throwing more people at one task doesn't necessarily make it go any faster (as those who have developed software surely can testify to) ;)

[dubik]

about those modes...
oh, well, tomas was faster, but there is another one
ctrl-f shows fps counter

[daperl]

If you look at the MeeGo architecture picture (http://meego.com/developers/meego-architecture), you will see that there are several reference user interfaces for different classes of devices.

In the same way that it doesn't really make sense to directly port desktop applications to mobile, we are still finding out what works best on different device types. The common factor you can rely on across all MeeGo devices at the moment is Qt. That doesn't necessarily mean a Qt based UI is the optimal fit for a MID type of device. Let's see :)

I think that page could use a quick edit. At the bottom, the picture should read

Adaptation

not

Application

[abubakar]

its pretty cool. There are 2 things though. After installing it, free space in / is only 14mb, before installation it was about 36mb.
Also after installation I cannot change my theme on n900, i goto Settings and click Themes but nothing shows up, happening with everyone? I also rebooted but same behavior. And one more thing which is pretty strange, in the gadget gallery, where ever text can be written, the letter "o" does not appear, i try writing "hello world" and what appears is "hell w rld".

[ARJWright]

In the same way that it doesn't really make sense to directly port desktop applications to mobile, we are still finding out what works best on different device types. The common factor you can rely on across all MeeGo devices at the moment is Qt. That doesn't necessarily mean a Qt based UI is the optimal fit for a MID type of device. Let's see :)

Rule of web design that would be nice to keep in mind here:

Content is separate from presentation is separate from functionality.

Qt is a toolkit, not a UI. It creates the ability to put content in the appropriate presentation container so that the desired functionality cam be demonstrated.

1 - 2.2in screens
2.2 - 3.3in
3.3 - 4.1in
5in - 7in
7in - 10(ish) in

These are all different sizes to which user interface has to be optimized. Inside of these screen sizes are expectations of use that drive function. Qt can write to all of these. The OS doesn't matter as long as there is tight governance around the abilities of devices in these form factors, and how the UI elements get presented.

Maemo 5 already has a leg up with Qt support; Symbian, Windows, Linux, etc will all benefit from the groundwork laid here. And except for the smallest two screen measurements I've listed, Maemo/Moblin/Meego is nicely positioned from a UX standpoint.

[davidmaxwaterman]

its pretty cool. There are 2 things though. After installing it, free space in / is only 14mb, before installation it was about 36mb.
Also after installation I cannot change my theme on n900, i goto Settings and click Themes but nothing shows up, happening with everyone? I also rebooted but same behavior. And one more thing which is pretty strange, in the gadget gallery, where ever text can be written, the letter "o" does not appear, i try writing "hello world" and what appears is "hell w rld".

Thanks for reporting this issue. I've managed to reproduce the theming issue on my device and will try to have it fixed.

I feel at this point that it's worth reminding people trying Widgets Gallery that, as with any preview software, it's wise to do a backup before trying it on your own device. While we have, of course, tested it on many devices, we can't test every possible situation and combination of packages. Our testing tends to focus on freshly flashed devices.

Thanks,

Max.

[maxximuscool]

this is bull crap, maemo5 will be forgotten in a 6 months from now. There are so much bugs to fix and the OS that nokia so hype about and proud of will only just a bridge. it's not like N900 is incapable of running Maemo6, it is very capable and should be bring forth the new OS into it. So far so many bulls going on with the controversy of N900 is not good enough to be the next subling of MAEMO6. Everyone who is buying he device now are holding back to wait, so as the developers? if the OS will soon be history and not many device sold enough to meet their margin of consideration to write software for this device no one is going to invest their money into a device that will not be a sucess product!

Why not just giving us the great maemo6 when it comes out? since maemo5 is the only bugjar to make maemo6 better. why treatig us with such terrible way of testing? there is no doubt that N900 is a good device but maemo5 is not even close to being refined. I can't even use my bluetooth headset with it!

seriously Nokia is big but size won't make the OS problems and hardware problems on the N900 goes away. i personally love my N900 but there are so much potential hidden inside it. Which could be discover by maemo6. But hey NO MAEMO6 for N900.

[qgil]

To the N900 users in this thread:

- The developers in this thread have nothing to do with Nokia business decisions e.g. N900 support and updates. If you notice the first thing they have done is to prepare a Widget Gallery binary for Maemo 5 making it available in Extras-devel. So please let them work on their stuff and help them with testing, feedback and hugs.

- Please get used to open development. Most of the interesting stuff that runs with software has a newer version being developed somewhere. The difference with open development is that you can have a preview and even an involvement long before a real product comes to the shelves.

- It is not easy to drag good developers to noisy forums like Talk. The easiest for themis to setup a project mailing list that anyway will get the people understanding the technology and discussing about it. Posts shouting at them about Nokia, the N900, etc won't help getting more of their time here.

Thank you for your understanding.

[silvermountain]

Maemo 5 has a whole separate team focused right now on bringing you lots of goodies in the already announced upcoming PR1.2 release for Maemo 5. Nokia is a pretty big company and Maemo's not so small either anymore, we're capable of multitasking

That would be a milestone if that is true as one thing that Nokia have consistently failed at has been to support anything but the latest-anything.

[dubik]

And here is the video....
<removed youtube link>

sorry guys, no video.

[RenegadeFanboy]

Video is private?

[qgil]

nibbles, you are getting confused. That article is quite old and this thread is about the open development of the Harmattan UI framework. Posts moved to the (old) thread where they belong to: http://talk.maemo.org/showthread.php?t=29055

[ezjd]

Since I didn't find place to discuss UI framework detail, I put some comments here (so it isn't as open as I expected;) ):

-- Why is the compositor based on QGLWidget instead of QWidget?
This implies that this UI framework requires HW OpenGL support all the time, similar to clutter.

This makes it less flexible when porting to a system w/o OpenGL and at least makes it more difficult to port as OpenGL driver is always closed source and not available from the beginning. (Actually, this is worst thing I think with Moblin).

-- Qt provides graphic system support, which make it possible to render using OpenGL or not. That is the flexibility I like with Qt. As such a fundamental component, using QWidget will provide more scalability. I like the idea in http://labs.trolltech.com/blogs/2009/12/16/qt-graphics-and-performance-an-overview/, which basically suggest to use SW raster engine by default and use QGLWidget when OpenGL acceleration is needed.

[xynopsis]

Since I didn't find place to discuss UI framework detail, I put some comments here (so it isn't as open as I expected;) ):

-- Why is the compositor based on QGLWidget instead of QWidget?
This implies that this UI framework requires HW OpenGL support all the time, similar to clutter.

This makes it less flexible when porting to a system w/o OpenGL and at least makes it more difficult to port as OpenGL driver is always closed source and not available from the beginning. (Actually, this is worst thing I think with Moblin).

-- Qt provides graphic system support, which make it possible to render using OpenGL or not. That is the flexibility I like with Qt. As such a fundamental component, using QWidget will provide more scalability. I like the idea in http://labs.trolltech.com/blogs/2009/12/16/qt-graphics-and-performance-an-overview/, which basically suggest to use SW raster engine by default and use QGLWidget when OpenGL acceleration is needed.

The Harmattan UI platform _is_ an OpenGL/GLES2-based platform and that backend is intentional. We are going to publish some validation test suites for hardware that can support our platform so this will not really be a big issue (e.g., GL extensions, shader support, etc).

Actually what Gunnar was talking in his blog is how off-screen painting is being handled. This is now made default in Qt i.e.,QPainter renders graphics to an off-screen buffer before displaying it on the framebuffer. The raster engine is of course the fastest off-screen painting approach because not all platform support GL rendering to pixmaps. Now how to render that off-screen buffer to the frame buffer is another issue, which of course the most efficient manner is by using GL.

Our compositor does not need to use raster because it completely bypasses QPainter since it is only interested in windows and already has the reference to off-screen representation of windows. What it needs is just a surface to draw to. That is why you see QGLWidget.

[ammadtira]

Dont install the demo widget.. Your themes would not work

[ezjd]

The Harmattan UI platform _is_ an OpenGL/GLES2-based platform and that backend is intentional. ...

OK, I am more clear about Harmattan targeting platform, which invalidates my comments basically. Looks like I should send this kind of requirement to MeeGo project, esp. assuming Harmarran UI framework will be the base of MeeGo's.

Technology wise, I'd say it will be more flexible that compositor can "fallback" to use QWidget or even QWindowSurface(?) when GL support isn't available or at least provides compile time options. One example is KWin, which can run well with or w/o GL support.

[tomasj]

Technology wise, I'd say it will be more flexible that compositor can "fallback" to use QWidget or even QWindowSurface(?) when GL support isn't available or at least provides compile time options. One example is KWin, which can run well with or w/o GL support.

Our compositor is really small (both code and feature wise) and intently focuses on filling the niche of a high-performance OpenGL compositor for handhelds or slightly larger devices. It's not really something you would want to use even on your laptop at this time. It does some quite innovative things like seamlessly un-redirecting the rendering for windows that fill the device screen, which is perfect for a handheld but doesn't make sense in other type of setups.

That said, the Harmattan UI framework can, and has been, run with other window managers and compositors. The apps don't really make any assumptions in this regard. Still, while the apps can technically be run in software by switching the graphics system, we see it as critical to the user experience that we can depend on OpenGL acceleration being available to us. So we are setting the minimum hardware baseline at the N900 level for the entire framework, and not making any compromises in order to also scale downwards.

[ezjd]

Our compositor is really small (both code and feature wise) and intently focuses on filling the niche of a high-performance OpenGL compositor for handhelds or slightly larger devices. It's not really something you would want to use even on your laptop at this time. It does some quite innovative things like seamlessly un-redirecting the rendering for windows that fill the device screen, which is perfect for a handheld but doesn't make sense in other type of setups.
I understand the reason doing so. What is this "seamlessly un-redirecting rendering"?

That said, the Harmattan UI framework can, and has been, run with other window managers and compositors. The apps don't really make any assumptions in this regard. Still, while the apps can technically be run in software by switching the graphics system, we see it as critical to the user experience that we can depend on OpenGL acceleration being available to us. So we are setting the minimum hardware baseline at the N900 level for the entire framework, and not making any compromises in order to also scale downwards.
As I assume (somewhat confirmed) that Harmattan UI framework will be the base of MeeGo, I think it was targeting much more devices. So I have these ideas because I view it as a more generic compositor and technically it is easy to achieve with Qt. Probably MeeGo will do another window manager/compositor, though it might not as HW OpenGL is also assumed, at least to what I heard.
I really like the graphic system/backend thing of Qt, which makes it possible to use OpenGL or not and it is transparent to application and can be changed at runtime. And this is impossible in clutter based system.

[Venemo]

I installed duitheme, because I liked its nice plain white look.
After that, I couldn't switch to the actual theme, because tapping on the "Themes" item didn't work anymore.

I didn't install any of the other packages.

[davidmaxwaterman]

I installed duitheme, because I liked its nice plain white look.
After that, I couldn't switch to the actual theme, because tapping on the "Themes" item didn't work anymore.

I didn't install any of the other packages.
yes, this is a known problem in fremantle and a fix has been made...not sure about the release plans.
we are considering a workaround in duitheme, however, i seriously doubt it will ever be possible to switch fremantle's ui to one in duitheme - though I will check to make sure.

Max.

[Venemo]

however, i seriously doubt it will ever be possible to switch fremantle's ui to one in duitheme - though I will check to make sure.
Thank you for checking that out!
However, if you doubt that it will ever be possible, why did you release it for Fremantle in the first place, then? :confused:

[conny]

Because now developers can already start to toy around with it, give feedback, adapt their own code, etc...

[davidmaxwaterman]

Thank you for checking that out!
However, if you doubt that it will ever be possible, why did you release it for Fremantle in the first place, then? :confused:

It's needed for the dui WidgetsGallery demo to look correct - it was never intended to work with the fremantle UI.

[davidmaxwaterman]

Thank you for checking that out!

I have checked this out and confirmed that at least it isn't supposed to work. I guess we can never say never, but it won't work 'as is' or without extra work.

It was mentioned that there might be some theme that looks at least similar...

[conny]

First, thank you very much for providing new versions of the Widget Gallery so often. It is really great to see the progress!

Now, I'm pretty sure that this is not the final Harmattan look and fell - there surely will be plenty of changes. Still, I'm wondering if we can assume the basic layouts etc. to be the same in Harmattan? E.g. the toolbar currently holds up to 4 actions. The application menu looks like it can hold a maximum of 8 actions. And so on...

Are those things, we can assume to be valid for the Harmattan release?

Another thing: What is the differentiation between a "check box" and a "switch"? Aren't they both doing exactly the same thing? When should I use a check box and when a switch? Or will one of them get dropped eventually?

Again, thanks for developing this in the open. Really exciting stuff :)

[conny]

I came about some more questions. I just had a short look into the code, so please excuse me, if I misunderstood something.

It seem that there are no sub classes for check buttons, switch buttons and check boxes. Instead this is all DuiButton.

Creating a normal button is as easy as:
DuiButton* pushButton = new DuiButton("Push Button");

But creating a check box I have to do:
DuiButton* checkbox = new DuiButton();
checkbox->setViewType(DuiButton::checkboxType);
checkbox->setCheckable(true);

Isn't setViewType(DuiButton::checkboxType) and setCheckable(true) somehow redundant?

Then to set a label for a check box, it looks like I have to do something like this:

checkboxLabel = new DuiLabel();
checkboxLabel->setText("Text");
QGraphicsLinearLayout *l = new QGraphicsLinearLayout(Qt::Horizontal);
l->addItem(checkbox);
l->addItem(checkboxLabel);
l->setAlignment(checkbox, Qt::AlignCenter);
l->setAlignment(checkboxLabel, Qt::AlignCenter);
containerPolicy->addItem(l);

I would rather expect to do simply
checkbox = new DuiButton("Text");
checkbox->setCheckable(true);

or even only
checkbox = new DuiCheckBox("Text");

Is the API to do this just not ready yet, or will it stay like this? Or did I simply miss something obvious? The code which I'm quoting is taken from the widget gallery.

Anyways, I would be happy to get some enlightenment :)

[dubik]

Sometimes you need togglable button, sometimes checkbox and sometimes switch. They all have the same semantics but different look. Thats why there is setViewType(...). So setCheckable can't decide which view you want. I think by default you get togglable button.

Regarding text..I will check with people who made it. But most likely there is no way to fix it. You may want to have text on the left, right, top or bottom, with spacer in between or not and so on. It's too complex to solve for general case.

[conny]

Sometimes you need togglable button, sometimes checkbox and sometimes switch. They all have the same semantics but different look. Thats why there is setViewType(...). So setCheckable can't decide which view you want. I think by default you get togglable button.
Ok, then setViewType() should be enough?! What will setCheckable(true) do on a push button?

Regarding text..I will check with people who made it. But most likely there is no way to fix it. You may want to have text on the left, right, top or bottom, with spacer in between or not and so on. It's too complex to solve for general case.
In this regard I really like the HildonCheckButton. I think it's a great idea to put the label inside the button. This way it is clear, that the label can be used to toggle the button and while tapping the button the change of state can be seen.

Of course, if you want to be super flexible on where/how the label should be placed a simple constructor with a string is not enough. On the other hand I think that in 95% of the cases people want to have a checkbox and a label on its right side. And the label should be clickable to change the check state of the button.

So how about doing a CheckButton that would be a composite of CheckBox and Label. CheckBox can then be used in cases where a CheckButton is not enough.

[tissot]

Anybody got video about widget gallery or know of any video?
I installed widget gallery back then, but i got the endless reboot problem and searching currently a video to show.

[davidmaxwaterman]

Anybody got video about widget gallery or know of any video?
I installed widget gallery back then, but i got the endless reboot problem and searching currently a video to show.

As I understand it, there's no official video, but maybe there's something done unofficially that I don't know of....check youtube. Many people have installed it, so I guess someone had made a video.

I wonder how you got an endless reboot problem. The only situation I know of that could cause this is when you try to *uninstall* it, and that was just with the first (?) version released and was quickly fixed. It should be fine now. If you still get such a problem, please let us know.

Max.

[TheBootroo]

i just checked harmattan on gitourious and compiled libdui and duitheme and installed them on my ubuntu laptop, but duihome and duicompositor don't want to compile...

what is the probleme ? could you give me a step by step procedure to get a fonctionnal testing duihome on linux please ?

[TheBootroo]

UPDATE :

I downloaded contextkit and libcontentaction from maemo-af gitorious and got contextkit compiling but not libcontentaction

then i got libdui, duitheme, duicontrolpanel and duihome compiling on my ubuntu but not duicompositor because of contentaction missing...

and i can't run mthemedaemon, so all harmattan apps launched just shows me a blank screen


but there's some progress !!

[manjiri]

i just checked harmattan on gitourious and compiled libdui and duitheme and installed them on my ubuntu laptop, but duihome and duicompositor don't want to compile...

what is the probleme ? could you give me a step by step procedure to get a fonctionnal testing duihome on linux please ?

Hi TheBootroo,
I have been trying to compile harmattan UIF.
Have you compiled in scratchbox envt or in your host envt?
Has anybody tried to put it onto the device?

Found a very useful post to start:
http://forum.meego.com/showpost.php?p=1482&postcount=7

git clone git://gitorious.org/maemo-6-ui-framework/libdui.git
cd libdui
./configure
make doc
(you will need doxygen)
Then in a browser:
file:///.../libdui/doc/html/tutorial.html

Of course it is Maemo 6 ui documentation ;-) ...

[bzhbok]

I compiled it on my laptop, unfortunatelly it doesn't run correctly. I asked for help on irc, and it looks like you need some in-house utility to be able to run it on a laptop. It is called dui-run, from dui-sb-session package. And they are not available in the open right now (from what I have been told). If you find a solution, I'm interested...

anyway, even if it is not working, the doc is interesting.

[rasjani]

Hiya.

Id assume that dui-run is very similar to what previous sdk's had: run-standalone.sh or something..

If you check the code it should be pretty evident that very basic requirements are session - and possibly system - dbus and gconf. Try starting those up and and export the session dbus environment and see what comes up?

[TheBootroo]

mthemedaemin seems to make some problems, as it doesn't want to start, apps screens are completely black.

[manjiri]

It's needed for the dui WidgetsGallery demo to look correct - it was never intended to work with the fremantle UI.

Does this mean it is not possible to compile duikeyboard and install it on N900 with PR1.2 update?

I have been able to compile and install libdui and duitheme on my ubuntu 9.10 desktop as well as scratchbox for maemo5. How do I put them on the device?

[davidmaxwaterman]

Does this mean it is not possible to compile duikeyboard and install it on N900 with PR1.2 update?


No, it doesn't mean that; I think that comment was about the duitheme package specifically.


I have been able to compile and install libdui and duitheme on my ubuntu 9.10 desktop as well as scratchbox for maemo5. How do I put them on the device?

I would build packages, copy them to the device, and install them. Since you've already build them, I assume you know how to build packages/etc. If not, let me know...

[sevla]

As I understand it, there's no official video, but maybe there's something done unofficially that I don't know of....check youtube. Many people have installed it, so I guess someone had made a video.

I wonder how you got an endless reboot problem. The only situation I know of that could cause this is when you try to *uninstall* it, and that was just with the first (?) version released and was quickly fixed. It should be fine now. If you still get such a problem, please let us know.

Max.

http://www.youtube.com/watch?v=SgVTQG1qbas

[sevla]

:: error: No rule to make target `/mgen/debug/mgen.exe', needed by `\lib\meegotouchcore.dll'. Stop.

I got this error when attempting to build libdui. Any ideas? I've been having troubles getting anything to work right in qt..

[hschroeder]

:: error: No rule to make target `/mgen/debug/mgen.exe', needed by `\lib\meegotouchcore.dll'. Stop.

I got this error when attempting to build libdui. Any ideas? I've been having troubles getting anything to work right in qt..

hi,

you might want to try this branch instead of master:

http://qt.gitorious.org/maemo-6-ui-framework/basyskom-libdui and then branch holger-windows

it seems that the current master is still missing a patch...


kr Holger

[ossipena]

how about fixing the problems in Maemo 5 first?

what about "fixed in fremantle"? why are there still older tablets in use?!?

it seems that there are always people who complain no matter what...

[sevla]

hi,

you might want to try this branch instead of master:

http://qt.gitorious.org/maemo-6-ui-framework/basyskom-libdui and then branch holger-windows

it seems that the current master is still missing a patch...


kr Holger

Thanks, I'll try that when I get home. Hopefully it will work because I want to get familiar with the code.

I installed the Nokia qt sdk found on Nokia's site. It's hard to tell if I have the environment set up incorrectly or if the code is just not in a state to be compiled.

[woof404]

I seem to be late in the game, but seriously congratz to tomasj and Harmattan UI framework team for going (L)GPLed! You make a difference :)

[ZogG]

To the N900 users in this thread:

- The developers in this thread have nothing to do with Nokia business decisions e.g. N900 support and updates. If you notice the first thing they have done is to prepare a Widget Gallery binary for Maemo 5 making it available in Extras-devel. So please let them work on their stuff and help them with testing, feedback and hugs.

- Please get used to open development. Most of the interesting stuff that runs with software has a newer version being developed somewhere. The difference with open development is that you can have a preview and even an involvement long before a real product comes to the shelves.

- It is not easy to drag good developers to noisy forums like Talk. The easiest for themis to setup a project mailing list that anyway will get the people understanding the technology and discussing about it. Posts shouting at them about Nokia, the N900, etc won't help getting more of their time here.

Thank you for your understanding.


I agree that this is meego releated thread, but the question is when we'll have meego community port for N900, would we get an official port of these widgets and other stuff that are tested on N900. because for now there were a lot of stuff tested by us (demos) or things we saw on nokia's videos running on N900 and still we didn't get them. and i'm not sure we would.

[qgil]

There are two sticky threads in this forum: one discussing the MeeGo project release running on the N900 and another one discussing the MeeGo-Harmattan release from Nokia being ported to N900 in a community effort.

Please let's keep this thread to discuss the now called MeeGo Touch Framework.

By the way, by the renaming of these libraries it is clear that this is another topic that would make more sense to have in http://forum.meego.com now...

[attila77]

The naming is still confusing. What is the actual relation of the MeeGo Touch Framework to MeeGo proper (is there any) ? It is not part of the MeeGo API, AFAIK does not build on it, touches on no MeeGo device except on the one that used to be called Maemo 6... And then there is something called MeeGo UI framework which IS part of the MeeGo API. Or is the MeeGo UI framework an alias for the MeeGo Touch framework ?

[conny]

No hard facts here, but I *think* MeeGo Touch Framwork (formerly known as DUI) will be the default MeeGo UI for handsets. Not only for Nokia handsets.

[qgil]

Simple: the MeeGo Touch Framework is the framework to be used in MeeGo touch devices. It is powering the MeeGo Handset UX planned to be published this month.

[attila77]

Fair enough. What is the relation between the MeeGo UI Framework and the MeeGo Touch Framework, are they the same thing or is one the subset of the other ?

[qgil]

Are you referring to the "MeeGo UI Framework" mention at http://meego.com/developers/meego-api ? If so, well spotted. Looks like it should simply say "MeeGo Touch Framework" there.

[attila77]

Yes, that's the one. Thanks for clearing that up.

[pKuo]

Hi, Sir:
I checked out libdui and make install it, however, I always get fails like below after executing "dui-sb-session start".

/usr/bin/duihome is not there, skipped

Then nothing happens....

Simple: the MeeGo Touch Framework is the framework to be used in MeeGo touch devices. It is powering the MeeGo Handset UX planned to be published this month.

[Diph]

Maybe you just have to wait for a week. I think the development should be easier when Meego pre-Alpha is out.

[vivainio]

Maybe you just have to wait for a week. I think the development should be easier when Meego pre-Alpha is out.

No need to wait or build yourself if you have Lucid.

Just do:

sudo add-apt-repository ppa:villemvainio/meego

Then (after "apt-get update" of course) you can install (unofficial) meegotouch packages (including demos and documentation).

[Diph]

Last time I checked libdui it complained about missing themes (problems with duitheme installation).

[vivainio]

Last time I checked libdui it complained about missing themes (problems with duitheme installation).

Well, the ppa I referenced works. It has a week+ old MT because the new ones require Qt 4.7 (Ubuntu has just 4.6 so far).

[conny]

No need to wait or build yourself if you have Lucid.

Just do:

sudo add-apt-repository ppa:villemvainio/meego

Then (after "apt-get update" of course) you can install (unofficial) meegotouch packages (including demos and documentation).

Your packages are working great. Thank you! Do you also have packages for duihome?

[vivainio]

Your packages are working great. Thank you! Do you also have packages for duihome?

Nope. But I imagine they are not needed if you want to do app development.

[conny]

No, I was just trying to get the complete stack running to see how GTK+ will behave in this setup and unfortunately I failed building it myself. Anyways, I'll just wait for the MeeGo/Handset alpha release and try again then. Thanks :)

[davidmaxwaterman]

Hi, Sir:
I checked out libdui and make install it, however, I always get fails like below after executing "dui-sb-session start".

/usr/bin/duihome is not there, skipped

Then nothing happens....

I think you should be using 'meego-sb-session' now - it replaced 'dui-sb-session'. There are still quite many places where 'dui' remains, so I understand the confusion. I don't know if dui-sb-session will still work, but I imagine there at least a few things that have been renamed (in /etc/meego-sb-session, I see 20input-method is invoking meego-im-uiserver, so that's one).

Yes, I think you don't really need the homescreen to develop applications, though I suppose you will want to check the .desktop files, icons and things like that. I'm not sure there any plans to make the homescreen work on top of maemo5. We are trying to get a new version of widgetsgallery out, but are having trouble (http://talk.maemo.org/showthread.php?p=728915#post728915) with the repository. If anyone can help, please do.

[Diph]

No need to wait or build yourself if you have Lucid.

Just do:

sudo add-apt-repository ppa:villemvainio/meego

Then (after "apt-get update" of course) you can install (unofficial) meegotouch packages (including demos and documentation).
I tried this and still same problem: "Failed to connect to theme daemon (IPC)"

Do I have to start the daemon before running for example widgetsgallery? Where do I find this daemon?

[vivainio]

Do I have to start the daemon before running for example widgetsgallery? Where do I find this daemon?

No, you don't need to start theme daemon. You should be able to run widgetsgallery without doing anything special.

Perhaps you may want to try "widgetsgallery -software" to use software rendering?

[Diph]

The whole error message:

"MRemoteThemeDaemon: Failed to connect to theme daemon (IPC)
MThemeDaemon - base theme directory not found: /usr/local/share/themes/base/meegotouch/libmeegotouchcore/style. Please (re)install meegotouchtheme package."

I tried "widgetsgallery -software" and same problem.

E: There isn't libmeegotouchcore under /themes/base/meegotouch.

[vivainio]

The whole error message:

"MRemoteThemeDaemon: Failed to connect to theme daemon (IPC)
MThemeDaemon - base theme directory not found: /usr/local/share/themes/base/meegotouch/libmeegotouchcore/style. Please (re)install meegotouchtheme package."

Check "which widgetsgallery" to verify that it isn't trying to run anything from /usr/local (e.g. result of previous compilation). You may want to clear all the old crap you find in /usr/local in general...

[Diph]

Yeah it's in usr/local. So what's the best way to uninstall all the old crap. :D

[vivainio]

Yeah it's in usr/local. So what's the best way to uninstall all the old crap. :D

"rm" ;-).

Just removing the binary (/usr/local/bin/widgetsgallery) ought to be enough, but sometimes it helps to remove other stuff you find as well.

E.g. /usr/local/lib is a good place to look for unwanted files.

[Diph]

Now I got it working (except all items in widgetsgallery are empty :> ). I removed all old files and reinstalled libmeegotouch-dev. Thanks.

[vivainio]

Now I got it working (except all items in widgetsgallery are empty :>

You should see real items in widgetsgallery, just like you used to in the old n900 version. Try "widgetsgallery -software". If that's still broken, you have a problematic installation; I've seen these packages work on ubuntu installations in several different computers.

[davidmaxwaterman]

You should see real items in widgetsgallery, just like you used to in the old n900 version. Try "widgetsgallery -software". If that's still broken, you have a problematic installation; I've seen these packages work on ubuntu installations in several different computers.

I'm not sure what 'empty' means. If it means they're all red (or green), then it's a problem related to the theme.

One thing you might try: the program the loads the theme has to be run with a specific graphics system. On maemo5, IIRC, we used '-graphicssystem native', but I guess that depends on the platform - try the specific ones - 'raster' or 'opengl'.

I assume you have the theme installed ok? It's a separate package on gitorious.

Note that, if you don't have the theme daemon running, then the application will attempt to load it itself with built-in code. The daemon helps when you run multiple applications and widgetsgallery should work just fine without it. IE, you can ignore messages about failing to communicate with the daemon.

Note that we have some more widgetsgallery (etc) packages up on extras-devel for maemo5. Unfortunately, we put in the wrong 'Section' for meegotouch-demos-widgetsgallery, but you should be able to install it just fine from the command line. I expect we'll have the Section fixed tomorrow and so the Application Manager will notice it and set the 'update' icon flashing for people who have the previous version installed.

HTH.

[vivainio]

I assume you have the theme installed ok? It's a separate package on gitorious.

My packages have functional meegotouhtheme at least...

Note that we have some more widgetsgallery (etc) packages up on extras-devel for maemo5. Unfortunately, we put in the wrong 'Section' for meegotouch-demos-widgetsgallery, but you should be able to install it just fine from the command line. I expect we'll have the Section fixed tomorrow and so the Application Manager will notice it and set the 'update' icon flashing for people who have the previous version installed.

Are you depending on qt 4.6 or 4.7? Meego Touch recently broke Qt 4.6 compatibility, I'm not sure whether they got it fixed (or decided to fix it) already...

[davidmaxwaterman]

My packages have functional meegotouhtheme at least...



Are you depending on qt 4.6 or 4.7? Meego Touch recently broke Qt 4.6 compatibility, I'm not sure whether they got it fixed (or decided to fix it) already...

4.7...the experimental packages.

[Diph]

This worked: "widgetsgallery -software". Thanks again.

[vivainio]

Note that we have some more widgetsgallery (etc) packages up on extras-devel for maemo5. Unfortunately, we put in the wrong 'Section' for meegotouch-demos-widgetsgallery, but you should be able to install it just fine from the command line.

I can confirm that apt-get now works, and the widgetsgallery demo now seems to work fine.

However, I don't seem to be getting the page transitions when navigating between pages... animations in general work fine though.