Re: Maemo Missteps, your thoughts?
 

I'm not sure, but I'm guessing you're talking about this list:
"Nokia has a strong community. But the biggest failure could be, they don't ask or doesn't matter. Their staff seems to use other devices or the N900 only in development environments." (only for all who are interested, I wouldn't repeat the list here) - It will not change anything, but please vote if you care about one of the Bugs...

And I added a additional one in the small hope we could get the good Idea of a community Brainstorm system working again: #10687 (at the moment it is more like a storage siding - "move it there and shut up")

Re: Maemo Missteps, your thoughts?
 

Sure... but MeeGo is all about the Qt. Like I said, it's a good choice: I bet MeeGo will gain more developers for this fact.
GTK would never reach the level of integration in MeeGo that it has in Fremantle. This is why my interests lie in Fremantle and not MeeGo.

Re: Maemo Missteps, your thoughts?
 

On a side note, this is a two edged sword. This means that there will not be a single OMAP3 'real' MeeGo device, which casts certain shadows on the N9's future. It could help A LOT if somebody official dropped in a future-proofing guarantee or two around release time. What I'm saying is that, from a MeeGo aspect, the N900 and the N9 aren't that much different, not only hardware, but software-wise, either. You will never be able to OTA the N9 to the next version of MeeGo, and, from what is known currently, has the same stance on drivers and closed components as Fremantle (if you can't wrap your head around this, think about it as Maemo 6 and it will be clearer), so I can already envision stskeeps doing an "N9 hardware adaptation project for MeeGo". This has to be handled from day 1 of the N9 - the Maemo missteps were bad, but given the N9's 'mainstream' goal, questions of this magnitude CANNOT be left to the community.

Re: Maemo Missteps, your thoughts?
 

Yes. Otherways seemingly intelligent people love Apple products. Adult, thinking and functioning people believe in God. I am sure they could make you reconsider Qt.

Re: Maemo Missteps, your thoughts?
 

@volt
And otherwise intelligent people believe in picking one library and running with it.

Why can't we have both?

The argument over inclusion of qt vs gtk is arbitrary.

And I forsee down the road the libraries merging (in several decades).

From a development perspective, should a developer have to learn a new language every time something new comes along? No. We left that "new language of the day" mess in the 80s.

Of course my beef with it, is that Nokia isn't using stock qt, they decided to add in their tweaks/"enhancements".

There are two distinct groups of developers at work here: the coders, writing software from scratch for a platform; and the porters, trying to get existing software working on another platform.

The coders have to adapt and learn to code in a new language or an existing language that has been modified.

The porters have to try and remedy dependency hell.

And yet "we're moving to qt. deal with it" is a good argument, how?

After so many people have learned to deal with Maemo's push for gtk*+hildon, you just want to lead them down another dead-end path?

Re: Maemo Missteps, your thoughts?
 

FWIW, (as I've extended the invitation elsewhere) - I'm more than happy to help you - or anyone else - learn. Just try things, ask questions, and we'll get there. I have a wide base of skills, but a lot of it centres around Qt, so use what I have.

I don't have as much time as I used to, but if tutorials would help you, then ask for specific topics, and I'm happy to look at working on that.

I'm in the same boat, but on the opposite side of the river. I have no CS degree, and I can't even tell you what 8 x 8 is without resorting to a calculator, yet I can code. Life's weird ;)

Re: Maemo Missteps, your thoughts?
 

That's what Samsung is doing. Putting out Android phones while trying to get their Bada platform finalized and decent developer support for that.

Re: Maemo Missteps, your thoughts?
 

Well, from that point of view, maybe what "they" would need to talk to qwerty12 about is more along the lines, "while we're building the frameworks around Qt, you're still free to...". It's not like they're blocking anyone from setting up alternative libraries and frameworks. (?) I know they don't want to push away apt loving people, and they surely don't want to push away gtk loving people... They just have to focus on one way to go. They've been encouraging people to move on to Qt. Not forcing.

My point is, though, I believe Nokia should have a brainstorming session around how to make long-time resource people @ maemo.org stay resource people, short term and long term. Or they could start a meego community from scratch and see how long that takes. It's not like Android has a head start...


Oh wait.


Edit: I am sorry that I keep writing names with no capital letters with capital letters.

Re: Maemo Missteps, your thoughts?
 

w00t, thank you. Who knows, I might just take you up on that :)

volt, I don't want this to be about me. My inability to use Qt is just that - my inability. I'm not blind; I can see that most new Maemo contributors are using Qt so something about it must be easier.

Believe it or not, I find Autotools (yes, Autotools!) easier to qmake despite qmake being a lot more simpler and, essentially, doing the same thing. I've managed to make quite a few GObjects during my time (and even managing to export them over D-Bus. Though, after seeing how much easier it is to do the same in Qt...). I've gotten used to it. It wasn't like this in the beginning, though but the way it worked clicked to me. I wish I could say the same looking at Qt code, but, again, it's my problem.

For every one contributor liking GTK, there's 10 more using Qt so, no, my coming or going makes no difference. I want to get back to Nokia's problems*! :)

EDIT: *I still stand behind #174.

Re: Maemo Missteps, your thoughts?
 

http://lists.meego.com/pipermail/mee...ne/003201.html might interest you then.

EDIT: Above is Hildon 2.2.19 built for MeeGo, against stock GTK+.