Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 19 hrs, 48 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 21 hrs, 2 mins ago -
Maemo repository (3)
to Community by torsen - 1 day, 12 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 10 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 16 hrs ago - more...
 |
|
2011-03-04
, 07:53
|
|
Posts: 306 |
Thanked: 350 times |
Joined on Oct 2009
@ Sydney
|
#52
|
Originally Posted by wmarone
So you believe we never got Flash 10 on the N900 by Adobe's fault? Or even TI? Only Nokia is to blame here.
I was about to mention earlier that he's wrong about other things (a great many things) but you brought him up in a topic on something he's right about.
I blame Adobe because the software is proprietary and no one can support the device but Adobe. We could trivially have Flash 10.1 due to how similar maemo/meego are to desktop Linux systems but due to mobile devices being "special," Adobe refuse to move on it.
You can at least get open source mp3 and aac decoders. Last I checked the closest open source equivalent to adobe flash player was Gnash, and it can't do a huge number of things that Flash can.
I suppose it's back to mailing websites and asking them to support web standards instead of focusing on proprietary products. Hello 2002, welcome back.
The big thing about Flash 10.x is that is GPU accelerated, so the device/OS maker (Nokia) and the GPU maker (TI) have to make it work just like with H264. Whoever develops a video codec is not magically able to test and support all hardware variations out there.
There are lots of other free and paid programs that export to SWF / FLV and AIR. Get on with the times.
__________________
Mobile: HTC Desire HD @ 1.2GHz | Revolution HD ( Gingerbread 2.3.5 ) and LauncherPro
Just waiting for ICS!!!
Tablet: Asus Eee Pad Transformer @ 1.4GHz | Revolution HD ( Honeycomb 3.2.1 ) Just waiting for ICS!!!
Lost: Nokia N900
Mobile: HTC Desire HD @ 1.2GHz | Revolution HD ( Gingerbread 2.3.5 ) and LauncherPro
Just waiting for ICS!!!Tablet: Asus Eee Pad Transformer @ 1.4GHz | Revolution HD ( Honeycomb 3.2.1 ) Just waiting for ICS!!!
Lost: Nokia N900
|
|
2011-03-04
, 07:55
|
|
Posts: 46 |
Thanked: 54 times |
Joined on Feb 2010
|
#53
|
Do you have any new deadlines defined now that Nokia is more actively involved?
For example, IF the new device will be released in 2011 and it's sometime in october/november (my reasoning being that both the N900 and N8 where released on that timeframe, probably to catch some of that holiday market) and it will have the final Meego version.
Then should we be seeing early summer or late spring for the developer version? Not much sense in getting the developer version after a full featured product has shipped. No need to hone anything on it then. Just get the new one (or Nokia may give it away is it does with the E7 and WP7 phones).
For example, IF the new device will be released in 2011 and it's sometime in october/november (my reasoning being that both the N900 and N8 where released on that timeframe, probably to catch some of that holiday market) and it will have the final Meego version.
Then should we be seeing early summer or late spring for the developer version? Not much sense in getting the developer version after a full featured product has shipped. No need to hone anything on it then. Just get the new one (or Nokia may give it away is it does with the E7 and WP7 phones).
|
|
2011-03-04
, 08:08
|
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#54
|
Originally Posted by Stskeeps
I really much appreciate that you comment here, but after seeing n+1 threads where people do not understand what they read (or actually do not read thread at all where they post comments randomly) I have to underline this for users around here.
From hardware adaptation, not UI:
1) Already works, I saw an awesome demo - front camera ("webcam") still in progress, but the big camera is the one of actual use.
2) Already works
3) Already works
4) Already works
5) Works for non-AGPS but still in labs due to us needing legal approval to redistributable bits. Who'd want to use Ovi Maps?
6) Works
7) Works (but we don't have a switcher dialog in UI)
8) Works
9) Works
"From hardware adaptation, not UI"
Probably some people here do not even understand what that means :|
But great work! And after all most of stuff what we ask here can be checked from meego wiki.
__________________
TMO links: [iSpy] - [Power search] - [Most thanked] - [Cordia - Maemo5 UI on top MeeGo Core] - [CommunitySSU]
TMO links: [iSpy] - [Power search] - [Most thanked] - [Cordia - Maemo5 UI on top MeeGo Core] - [CommunitySSU]
|
|
2011-03-04
, 08:32
|
|
Posts: 999 |
Thanked: 1,117 times |
Joined on Dec 2009
@ earth?
|
#55
|
As I understand it:
The "hardware adaption" team (lead by stskeeps) are writing backend stuff (e.g. GPS hardware, ability to SMS and make phone calls). Also developing *standard "Meego" UI.
The "Developer Edition" team (lead by Nokia) are writing addiitional UI components to integrate with *standard "Meego" UI and possibly proprietory components too? (e.g. NOT Flash but mapping software).
Can I assume the "Developer Edition" is not a completely new UI stack atop of N900 Meego? If that's the case then "duplication" of standard "Meego" UI is pretty stupid. I hope it is in addition to standard "Meego" UI and developing "Nokia" UI components.
I'm not quite sure what the "boundaries" of the two projects are.
*I mean the Meego UI for "handsets".
The "hardware adaption" team (lead by stskeeps) are writing backend stuff (e.g. GPS hardware, ability to SMS and make phone calls). Also developing *standard "Meego" UI.
The "Developer Edition" team (lead by Nokia) are writing addiitional UI components to integrate with *standard "Meego" UI and possibly proprietory components too? (e.g. NOT Flash but mapping software).
Can I assume the "Developer Edition" is not a completely new UI stack atop of N900 Meego? If that's the case then "duplication" of standard "Meego" UI is pretty stupid. I hope it is in addition to standard "Meego" UI and developing "Nokia" UI components.
I'm not quite sure what the "boundaries" of the two projects are.
*I mean the Meego UI for "handsets".
__________________
I like cake.
I like cake.
 |
|
2011-03-04
, 08:49
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#56
|
Originally Posted by johnel
"Hardware adaptation" delivers the backend that makes the MeeGo.com platform work properly on N900. IE, drivers, kernels and other boring stuff.
As I understand it:
The "hardware adaption" team (lead by stskeeps) are writing backend stuff (e.g. GPS hardware, ability to SMS and make phone calls). Also developing *standard "Meego" UI.
The "Developer Edition" team (lead by Nokia) are writing addiitional UI components to integrate with *standard "Meego" UI and possibly proprietory components too? (e.g. NOT Flash but mapping software).
Can I assume the "Developer Edition" is not a completely new UI stack atop of N900 Meego? If that's the case then "duplication" of standard "Meego" UI is pretty stupid. I hope it is in addition to standard "Meego" UI and developing "Nokia" UI components.
I'm not quite sure what the "boundaries" of the two projects are.
*I mean the Meego UI for "handsets".
Intel works on MeeGo Handset UX with the intent only of delivering a reference UX for others to finish and built upon. We've (HW adaptation) here and there helped with some contributions on UI side when needed to speed some things up, but it's not our real duty to even touch UI side.
DE takes HW adaptation + MeeGo.com Core + MeeGo.com Handset UX and takes it and makes it usable for daily usage for developers/extreme power users, contributing UI changes back to MeeGo.com Handset UX. DE publishes a "MeeGo.com-based" "product", ie, the DE.
They start with simple but needed basic use cases. http://wiki.meego.com/ARM/N900/HE#Use_cases lists those. The idea is to make them work solidly, well and usable on a daily basis.
Long story short: Make Handset UX not "suck" and be able to use it for those use cases without wanting to throw it out from 6th floor like a Neo Freerunner.
Can it evolve beyond the basic use cases over time? Yes, but let's get the basic stuff working first and well. As an example, I could care less about DLNA working when my phonecalls don't
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
 |
|
2011-03-04
, 08:51
|
|
Posts: 279 |
Thanked: 231 times |
Joined on Apr 2010
@ Holland
|
#57
|
@Stskeeps, really appreciate that you are willing to share detailed information regarding the (hw) adoptation for the N900. There is one thing I'd like to ask and that is..
When you now something exciting is about to happen, e.g. an expected release date of software for instance, would you be willing to share that information with this community as well?
I am asking this because most N900 users are eager to hear about the progress of their Maemo replacement/alternative (in the long run). You probably know that we have been let in the cold for a couple of times, but adaptation teams like yours make us look forward to the N900 future!
When you now something exciting is about to happen, e.g. an expected release date of software for instance, would you be willing to share that information with this community as well?
I am asking this because most N900 users are eager to hear about the progress of their Maemo replacement/alternative (in the long run). You probably know that we have been let in the cold for a couple of times, but adaptation teams like yours make us look forward to the N900 future!
__________________
Is that a N900 in your pants or are you just happy to see me?
Is that a N900 in your pants or are you just happy to see me?
|
|
2011-03-04
, 08:53
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#58
|
Originally Posted by blipnl
We have weekly status meetings and publish minutes from this on meego-dev@ mailing list each time. We conduct our business in the open, on #meego-arm (as will the DE people) and our release schedule follows http://wiki.meego.com/Release_Engineering/Plans/1.2
@Stskeeps, really appreciate that you are willing to share detailed information regarding the (hw) adoptation for the N900. There is one thing I'd like to ask and that is..
When you now something exciting is about to happen, e.g. an expected release date of software for instance, would you be willing to share that information with this community as well?
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
|
|
2011-03-04
, 09:06
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#59
|
Also, keep in mind that contributions are very welcome. The DE project is intended to run in the open. Even implementing simple control panels for simple N900 specific things (TV out control as an example) in QML + PySide would be very valuable.
To add to the fun mix, it seems like the idea is to mix Intel Tablet UX + Handset UX (replacing some of the bad apps in Handset) So we'll get Intel's QML components too which should make things a lot easier.
To add to the fun mix, it seems like the idea is to mix Intel Tablet UX + Handset UX (replacing some of the bad apps in Handset) So we'll get Intel's QML components too which should make things a lot easier.
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
|
|
2011-03-04
, 09:15
|
|
Posts: 1,746 |
Thanked: 1,832 times |
Joined on Dec 2010
|
#60
|
I appreciate all the work being done for this, and if any donations are needed I'd be more than happy as this is something I'd like to see come to life rather than abandoned
| The Following User Says Thank You to m4r0v3r For This Useful Post: | ||
 |
| Tags |
| best thread yet, meegohorny, nokia rox, stupid guys say, we want bada |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 06:16.
I suppose it's back to mailing websites and asking them to support web standards instead of focusing on proprietary products. Hello 2002, welcome back.