Comments on: MeeGo Thoughts http://zchydem.enume.net/2010/02/26/meego-thoughts/ #Qt, #Linux, #Programming, #MeeGo... Sat, 07 Jan 2012 18:23:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: lapnd http://zchydem.enume.net/2010/02/26/meego-thoughts/comment-page-1/#comment-180 lapnd Thu, 31 Mar 2011 01:20:30 +0000 http://zchydem.enume.net/?p=622#comment-180 Hi Zchydem! Thank for your comments. I'm sorry for trouble you again. Could you please help me to understand one more thing about UX layer of Meego? As we know, UX layer includes 2 parts: - UI framework ( Netbook UI framework, Handset UI framework, IVI UI framework) - Applications I'm confusing about UI framework and Applications. In my understanding: - UI framework is the GUI part is displayed when start up for end-user such as pannel, homescreen,taskbar. - Applications are some application such as chatting,web-browser, calculator,open-offices... Is my understanding correct? Hi Zchydem! Thank for your comments.
I’m sorry for trouble you again.
Could you please help me to understand one more thing about UX layer of Meego?
As we know, UX layer includes 2 parts:
– UI framework ( Netbook UI framework, Handset UI framework, IVI UI framework)
– Applications
I’m confusing about UI framework and Applications. In my understanding:
– UI framework is the GUI part is displayed when start up for end-user such as pannel, homescreen,taskbar.
– Applications are some application such as chatting,web-browser, calculator,open-offices…
Is my understanding correct?

]]> By: zchydem http://zchydem.enume.net/2010/02/26/meego-thoughts/comment-page-1/#comment-179 zchydem Sat, 26 Mar 2011 11:00:26 +0000 http://zchydem.enume.net/?p=622#comment-179 Hi lapnd! Good thing about MeeGo is that you can always take it, modify it to your purposes and use it. Afaik, the X11 is only needed by UX layer which can be replaced by your own UX layer implementation. To be honest, MeeGoTouch is too heavy for doing anything sensible and therefore it I highly recommended to throw it away and replace it with something better. Actually I'm working atm in project where we have done it. Another thing which is interesting, is to see how Wayland (http://wayland.freedesktop.org/) could provide an alternative for X11. I'm not a Wayland expert and haven't done anything on top of it, but it's certainly something to worth to think about. Hi lapnd! Good thing about MeeGo is that you can always take it, modify it to your purposes and use it. Afaik, the X11 is only needed by UX layer which can be replaced by your own UX layer implementation. To be honest, MeeGoTouch is too heavy for doing anything sensible and therefore it I highly recommended to throw it away and replace it with something better.

Actually I’m working atm in project where we have done it. Another thing which is interesting, is to see how Wayland (http://wayland.freedesktop.org/) could provide an alternative for X11. I’m not a Wayland expert and haven’t done anything on top of it, but it’s certainly something to worth to think about.

]]> By: lapnd http://zchydem.enume.net/2010/02/26/meego-thoughts/comment-page-1/#comment-178 lapnd Thu, 24 Mar 2011 03:21:18 +0000 http://zchydem.enume.net/?p=622#comment-178 Hi Zchydem, Thank for your information. I'm thinking about your first paragraph of your conclusion. As we know, for embedded devices with limited resource capacities, it is not good solution when build GUI based on X11.For this kind of devices, if we want to port Meego on them, I think we need eliminate X11 and then build our UX from scratch by using QT embedded. 1. To build our UX from For Meego (use QT embedded). Based on requirements of UI by ourself,I think it's ok 2. To eliminate X11 from Meego. I checked Meego source code core, I found that around 8% packages related to X11 directly.Do you think it is hard work to eliminate X11? Hi Zchydem,
Thank for your information.
I’m thinking about your first paragraph of your conclusion. As we know, for embedded devices with limited resource capacities, it is not good solution when build GUI based on X11.For this kind of devices, if we want to port Meego on them, I think we need eliminate X11 and then build our UX from scratch by using QT embedded.
1. To build our UX from For Meego (use QT embedded). Based on requirements of UI by ourself,I think it’s ok
2. To eliminate X11 from Meego. I checked Meego source code core, I found that around 8% packages related to X11 directly.Do you think it is hard work to eliminate X11?

]]> By: zchydem http://zchydem.enume.net/2010/02/26/meego-thoughts/comment-page-1/#comment-134 zchydem Mon, 07 Jun 2010 11:17:34 +0000 http://zchydem.enume.net/?p=622#comment-134 saikoushik: Yes, I mention those as examples of the services that you can use via WRT. I didn't mean that there are source code examples. I guess the best way to get familiar with MeeGo is to follow what happens in gitorious: http://meego.gitorious.org/. I'm sorry that I couldn't point you any real examples. saikoushik:

Yes, I mention those as examples of the services that you can use via WRT. I didn’t mean that there are source code examples. I guess the best way to get familiar with MeeGo is to follow what happens in gitorious: http://meego.gitorious.org/. I’m sorry that I couldn’t point you any real examples.

]]> By: saikoushik http://zchydem.enume.net/2010/02/26/meego-thoughts/comment-page-1/#comment-133 saikoushik Mon, 07 Jun 2010 09:12:44 +0000 http://zchydem.enume.net/?p=622#comment-133 hi , in above you said some examples for WRT like phonebook ,location and ovi , can you please help me by providing links to the above examples source-code , and i am newbie to WRT and web apps , it will be helpful to me and i will make reference of those apps hi ,
in above you said some examples for WRT like phonebook ,location and ovi , can you please help me by providing links to the above examples source-code , and i am newbie to WRT and web apps , it will be helpful to me and i will make reference of those apps

]]>