Re: [MeeGo-community] Feedback for video offering.
Hi Sivan, Sivan Greenberg wrote: There are now videos as part of the developer offering getting started. Your feedback is highly appreciated. See it here: http://developer.meego.com/guides/getting-started/meego-application-development-walkthrough (user/pass: meego/developer) They look good! One detail I noticed: in the second tutorial, Danny uses F1 to get the documentation for NumberAnimation, to show how you can find out about it. He then adds two attributes: to and duration. I noticed that duration wasn't mentioned in the documentation pane as a possible attribute. Looking at the docs [1], the attribute is used in a code sample, but not documented independently on that page. It looks like the duration property is inherited from PropertyAnimation [2] - but there doesn't seem to be any way to see all properties possible including inherited properties in the docs. Is this a bug in the docs? Cheers, Dave. [1] http://doc.qt.nokia.com/4.7-snapshot/qml-numberanimation.html [2] http://doc.qt.nokia.com/4.7-snapshot/qml-propertyanimation.html -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] MeeGo vs WebOS
Hi, Zahedonline wrote: So going ahead which one to choose? As I have used Maemo I prefer to go with it, but touchstone pulls me towards WebOS... To be frank, this doesn't seem like the best place to ask that question. Thanks, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] An Update from Intel
On Tue, Feb 15, 2011 at 21:37, Foster, Dawn M dawn.m.fos...@intel.com wrote: I wanted to make sure that everyone saw the post that Imad wrote yesterday on the meego.com blog: http://meego.com/community/blogs/imad/2011/update-intel Does this answer the question of whether or not Nokia's change of strategy warrants a revisit and restatement of MeeGo's aims? http://lists.meego.com/pipermail/meego-community/2011-February/003376.html Just wanting to clarify if further discussion about how the MeeGo Project should see itself and move forward is useful (taking on board your comment about the possible impact on people's jobs, but I'm not sure the discussion above really impacts that) Thanks, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council member ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] An Update from Intel
On Wed, Feb 16, 2011 at 12:40 PM, Ville M. Vainio vivai...@gmail.com wrote: On Wed, Feb 16, 2011 at 11:51 AM, Andrew Flegg and...@bleb.org wrote: I wanted to make sure that everyone saw the post that Imad wrote yesterday on the meego.com blog: http://meego.com/community/blogs/imad/2011/update-intel Does this answer the question of whether or not Nokia's change of strategy warrants a revisit and restatement of MeeGo's aims? Radical changes in this area may be a bad idea until some clarity is coming from Nokia side (about concrete changes). It can take a while to gather all the pieces after the explosion. I would wait for something real official coming from Quim / Ronan before jumping around. I agree, I wish some sort of this official stand with respect to the project would have arrived already... -Sivan ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-community] Backup framework utilisation in graceful power drop and recover.
Hi List, From what I gathered during the Dublin meetup, I think the backup framework can help us make quite a reliable graceful power drop and recovery strategy. I have added my thoughts here: https://bugs.meego.com/show_bug.cgi?id=5521#c14 Please, your feedback and comments appreciated. BR, -Sivan ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] Feedback for video offering.
On Feb 16, 2011, at 1:21 AM, Dave Neary wrote: Hi Sivan, Sivan Greenberg wrote: There are now videos as part of the developer offering getting started. Your feedback is highly appreciated. See it here: http://developer.meego.com/guides/getting-started/meego-application-development-walkthrough (user/pass: meego/developer) They look good! One detail I noticed: in the second tutorial, Danny uses F1 to get the documentation for NumberAnimation, to show how you can find out about it. He then adds two attributes: to and duration. I noticed that duration wasn't mentioned in the documentation pane as a possible attribute. Looking at the docs [1], the attribute is used in a code sample, but not documented independently on that page. It looks like the duration property is inherited from PropertyAnimation [2] - but there doesn't seem to be any way to see all properties possible including inherited properties in the docs. Is this a bug in the docs? Cheers, Dave. [1] http://doc.qt.nokia.com/4.7-snapshot/qml-numberanimation.html [2] http://doc.qt.nokia.com/4.7-snapshot/qml-propertyanimation.html Since most of the SDK team doesn't follow this list, probably a good idea to file it as a bug. Dawn ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] Questions
Hi, I don't know the answers to all your questions, but I can answer a few: Sivan Greenberg wrote: 1) Are we going to have the MeeGo Conference planned for spring? Yes. 2) Can we continue business as usual in terms of investing learning resources into MeeGo + (Qt / C++ / QML) ? Can other vendors that might read this list share their plans for future devices with MeeGo so we can get more context? Effectively, is Qt staying the de-facto tool for app developers on the MeeGo platform across all verticals? Whether you continue investing time in QML/Qt/C++ is up to you. What was your plan before the Nokia announcement? Did it depend on Nokia creating a big market for Qt? If so, you might want to revise. If you're here because you thought MeeGo was a cool project to work on, it probably still is. For Qs 2, 3 and 4 I have no strategic insight into what Intel or Nokia might do in the future. My best guesses are that no-one involved in MeeGo can afford another reset or retreating to where we were a year ago, I expect Qt to be pushed hard on MeeGo for as long as the project is viable at this point. Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] An Update from Intel
On Feb 16, 2011, at 4:18 AM, Sivan Greenberg wrote: On Wed, Feb 16, 2011 at 12:40 PM, Ville M. Vainio vivai...@gmail.com wrote: On Wed, Feb 16, 2011 at 11:51 AM, Andrew Flegg and...@bleb.org wrote: I wanted to make sure that everyone saw the post that Imad wrote yesterday on the meego.com blog: http://meego.com/community/blogs/imad/2011/update-intel Does this answer the question of whether or not Nokia's change of strategy warrants a revisit and restatement of MeeGo's aims? Radical changes in this area may be a bad idea until some clarity is coming from Nokia side (about concrete changes). It can take a while to gather all the pieces after the explosion. I would wait for something real official coming from Quim / Ronan before jumping around. I agree, I wish some sort of this official stand with respect to the project would have arrived already… If we had anything more detailed, we would share it. The reality is that it takes time to work out the details. I would expect to see more details rolling out in pieces over the next few weeks as Nokia makes some decisions about technology and staffing. As I've mentioned before in other places, these conversations involve people's lives and jobs. Let's try to be patient and sensitive toward all of the people involved. We'll be sharing more details as soon as we have them. Until then, let's just try to keep working on MeeGo and be patient with people until we get more tangible information. Dawn ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] An Update from Intel
On Wed, 2011-02-16 at 08:20 -0800, ext Foster, Dawn M wrote: If we had anything more detailed, we would share it. The reality is that it takes time to work out the details. I would expect to see more details rolling out in pieces over the next few weeks as Nokia makes some decisions about technology and staffing. Indeed. Nokia and Intel are meeting in MWC and I expect Imad/Valtteri to explain more details as soon as (like Dawn says) there is something clear to share. What is certain is that Nokia is not anymore in a position of parity, and Intel is the main driver of the project. This doesn't mean that the activities pushed by Nokia will be dismantled or taken by Intel overnight. Nobody has told us to stop working on MeeGo, and actually our top management is keeping very explicitly the main MeeGo goal set for this year: shipping a MeeGo based product (with all the activities that this implies). Also, the situation has different perspectives. For instance, Qt plays an important role in verticals like IVI or TV almost independently from the Handset activities. And Intel just unveiled a Tablet UX based on Qt where Nokia had no involvement. Sorting out this takes time. The Nokia executives could have shut down all MeeGo activities last Friday, yet they kept some doors open as part of the new strategy. Let's see what useful contributions can come through these doors. Taking blunt (short)cuts now doesn't really benefit anybody. fwiw, I have opened The informal but serious Nokia @ MeeGo thread http://forum.meego.com/showthread.php?t=2719 to share the updates from the Nokia side that might be relevant for the MeeGo community. Hopefully this will help cleaning the MeeGo project channels from Nokia specific discussions. Feel free pointing anybody off-topic there. -- Quim ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-community] Some Qt answers [Was: Questions]
On Onsdag 16. februar 2011, ext Dave Neary wrote: Whether you continue investing time in QML/Qt/C++ is up to you. What was your plan before the Nokia announcement? Did it depend on Nokia creating a big market for Qt? If so, you might want to revise. It's a big and growing market for Qt/QML apps. One of those markeds are +225 million Symbian devices going forward. What has this to do with MeeGo, you might ask? Developers who develops on Linux only, might overlook the real market opportunities presented with Qt. This because the current dominant design is single OS for programming toolchains and frameworks. Then it's easy to make a wrong assumption that one swallow doesn't make a summer. Please acknowledge that Qt is cross platform. MeeGo is one of several touch device OS's. This makes choosing Qt for your project like a summer breeze, as this blog from CuteHacks shows: http://cutehacks.com/2011/02/14/cross-platform-apps-at-mwc/ Back to MeeGo. Nokia plan to sell their first MeeGo device this year. Also, listen carefully to what Nokia CTO Rich Green says on Qt regarding the next disruption (focus on the videos about Qt, MeeGo and Symbian): http://www.youtube.com/user/NokiaConversations#p/u/0/nMe1qbqxVa0 If you're here because you thought MeeGo was a cool project to work on, it probably still is. Please stay. Learn to profit from your Qt skills like CuteHacks does. For Qs 2, 3 and 4 I have no strategic insight into what Intel or Nokia might do in the future. Some strategic insight is given from Stephen Elop on the QA at Mobile World Congress. Please start viewing 7:15 minutes into the cast: http://www.youtube.com/watch?v=4uglr-OkeMY My best guesses are that no-one involved in MeeGo can afford another reset or retreating to where we were a year ago, I expect Qt to be pushed hard on MeeGo for as long as the project is viable at this point During a Monday Intel event here at MWC, Renée J. James, senior vice president and general manager of Intel's Software and Services Group, said that Intel doesn't have any plans to change anything related to Qt. This reported by PCMag: http://www.pcmag.com/article2/0,2817,2380331,00.asp Best regards Knut Yrvin -- Open Source Community Manager Nokia, Qt Development Frameworks cell: + 47 934 79 561, phone: +47 21 60 27 58 http://qt.nokia.com ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] nokia new strategic direction what is the future for qt
On Mon, Feb 14, 2011 at 9:50 AM, Niels Mayer nielsma...@gmail.com wrote: Also, interesting to compare MeeGo's GUI/desktop offerings to the latest Android release (Gingerbread), whose innovations are things that have long been available in MeeGo and Qt and KDE and Maemo: I actually meant Honeycomb, not Gingerbread. See: http://androidcommunity.com/android-3-0-honeycomb-full-preview-guide-user-features-20110130/ Note the pictures and features in the above Android tablet release versus, say, the latest Intel Tablet http://blog.laptopmag.com/intel-shows-off-meego-tablet-ux-complete-with-panel-based-home-screen I think the Qt-based panel based home screen is very nice, and it felt nice to operate when I tried out the release ( http://appdeveloper.intel.com/en-us/meego-swype-esla ). Looks like the main thing we need for open-source parity with Android is a libre QtQuick based version of the Swype keyboard?? Also, is the source-code for the Intel panel based home screen available? (Basically, the coding in the QML files -- not the graphics assets). -- Niels http://nielsmayer.com ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-community] nokia new strategic direction what is the future for qt
On 17/02/11, Niels Mayer wrote: I think the Qt-based panel based home screen is very nice, and it felt nice to operate when I tried out the release ( http://appdeveloper.intel.com/en-us/meego-swype-esla ). Yes, I've been playing with meego-tablet-ia32-pinetrail.iso which seems to also include the /usr/share/meego-ux-panels/ code which is mostly QML files but also uses... import MeeGo.Components 0.1 import MeeGo.Panels 0.1 import MeeGo.Sharing 0.1 so the source for the above (and possibly other plugins) is what is needed. Looks like the main thing we need for open-source parity with Android is a libre QtQuick based version of the Swype keyboard?? Yes. I'd like to start working on that. Also, is the source-code for the Intel panel based home screen available? (Basically, the coding in the QML files -- not the graphics assets). I'd also like to hear from Intel where is, or when they are going to release, the source to their MeeGo tablet UX? And/or, why isn't Intel using repo.meego.com / gitorious.org? And/or, what is the best way to contribute to the tablet UX? --markc ___ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
