Active Topics

 


Reply
Thread Tools
Posts: 222 | Thanked: 205 times | Joined on Jul 2009 @ Finland
#61
Originally Posted by lma View Post
One other thing to consider: if the "community" isn't able (or willing - unpaid volunteers have even fewer resources available) to pick up the slack in time for the Harmattan release it would mean that most existing apps simply won't work on Harmattan devices.
Those who want to be able to code in Gtk for phones certainly should be motivated enough to get the community port of hildon working on Harmattan, since that's going to be the only phone allowing that in the first place. If the community doesn't care enough, that would signal that it's not that important in the first place.

It shouldn't be a gigantic effort, you can basically get the fremantle version of hildon and remove the clutter-specific code. Perhaps Nokia could fund this enough to get it kickstarted, and leave the maintenance/improvement for the community.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#62
Originally Posted by vivainio View Post
Those who want to be able to code in Gtk for phones certainly should be motivated enough to get the community port of hildon working on Harmattan,
It's not just a matter of motivation. Someone who is able to code an app in Gtk+ doesn't necessarily have the skills to hack Gtk+ itself. Also, the switch involves all of Hildon, ie a lot more than just Gtk+ - what about control panel, home & statusbar applets, input methods, and libraries like libhildonmime & libhildonnotify? Consider that their Harmattan replacements most likely won't have C bindings.

It shouldn't be a gigantic effort, you can basically get the fremantle version of hildon and remove the clutter-specific code.
Which means Fremantle apps that utilise that code won't run, ie more fragmentation.

Perhaps Nokia could fund this enough to get it kickstarted, and leave the maintenance/improvement for the community.
That looks like exactly what they are doing, with Fremantle being the kickstart stage.
 
Posts: 35 | Thanked: 246 times | Joined on Feb 2009
#63
Originally Posted by vivainio View Post
It shouldn't be a gigantic effort, you can basically get the fremantle version of hildon and remove the clutter-specific code. Perhaps Nokia could fund this enough to get it kickstarted, and leave the maintenance/improvement for the community.
Clutter is used in Frematle mostly in Hildon desktop compositing
window manager, it is not used in applications.

The things need to be done are mostly same that we needed to do
for Hildonized QT. Adapt Hildon to Harmattan Styles and Input
method.
 

The Following User Says Thank You to kate For This Useful Post:
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#64
Originally Posted by lma View Post
Sure, current x86 chips don't have the power management features of current ARM chips, but there's nothing in the instruction set that dictates that, it's simply that they have been targetting the PC market so far.
Not really. There have been low power/embedded x86 versions quite a while now, even from vendors other than Intel (see geode). x86 (like ARM) isn't JUST an instruction set, it's a platform and brings quite a bit of baggage (which you need to carry on to be compatible), and instruction sets are just a facet of that. The two ways they can overcome this is that they break compatibility (not really x86 then, is it?), or make fabrication improvements WAY beyond any ARM licensee (not gonna happen in years).
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#65
Originally Posted by attila77 View Post
Not really. There have been low power/embedded x86 versions quite a while now, even from vendors other than Intel (see geode).
Yeah (my favourite being VIA), but they don't go far enough for "mobile" use yet. They concentrate on making the chip more efficient while leaving it and the associated "chipset" running all the time whereas an OMAP can switch off most parts when they are not used, getting similar idle consumption rates as "suspend to RAM" would on an x86. Oversimplifying a bit (yes, I know about C-states, P-states etc) but all current x86 chips eat a lot of juice unnecessarily even when they're doing nothing.

The two ways they can overcome this is that they break compatibility (not really x86 then, is it?)
There might be (I honestly don't know) implicit assumptions that could break things like Windows drivers on an aggressively power-saving chip, but Linux should be ok or at least fixable.
 
Posts: 356 | Thanked: 231 times | Joined on Oct 2007
#66
Originally Posted by lma View Post
They say they can't do that because of lack of resources, but at the same time they admit they'll have to rewrite everything that draws on the screen to C++/Qt which is orders of magnitude more work. Something does not quite compute there...
They have to rewrite only low level stuff. User space apps written for Qt in Fremantle should work without many problems in Harmattan.

I think this announcement means for developers: you want stable platform now: use GTK+ for now and face uphill battle later with unsupported foundations or rewriting of your program in Qt.

But if you plan with few years ahead you should start already with Qt. Yes, this will be unsupported officially now but you can use Fremantle as beta stage and have solid release with Harmattan in 2010.

Note that it is in sync with roadmap for Symbian^x (recently linked here) where also only in 2010 fully new version with Qt as primary user space language will be released. IMO every puzzle nicely fits in.
 
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#67
Originally Posted by vvaz View Post
They have to rewrite only low level stuff. User space apps written for Qt in Fremantle should work without many problems in Harmattan.
Uhmm... you are ignoring all the Nokia userland stuff. They will have to rewrite every single hildon user-space app/applet in C++/Qt. That includes the file manager, media player, image viewer, pdf reader, rss reader, calculator, clock, sketch, terminal, application manager, backup/restore, connection manager, internet call, chat, contacts, modest, microb, control panel, statusbar and desktop applets, the whole shebang.

Additionally, all the "partner" applications will have to be rewritten as well: skype, gizmo, wayfinder etc. I'm guessing the Mozilla (fennec, not microb) people may not be too happy to switch to Qt either.
 

The Following 2 Users Say Thank You to lma For This Useful Post:
Posts: 356 | Thanked: 231 times | Joined on Oct 2007
#68
So that's why it takes one more year to get fully supported Qt edition of IT. Mozilla, well who needs them with QtWebKit?
 
Posts: 222 | Thanked: 205 times | Joined on Jul 2009 @ Finland
#69
Originally Posted by lma View Post
They will have to rewrite every single hildon user-space app/applet in C++/Qt. That includes the file manager, media player, image viewer, pdf reader, rss reader, calculator, clock, sketch, terminal, application manager, backup/restore, connection manager, internet call, chat, contacts, modest, microb, control panel, statusbar and desktop applets, the whole shebang.
Luckily, Nokia will be footing the bill for those. Considering that it would have happened anyway at some point (in order to not completely "orphan" Maemo from the other stuff they are doing, e.g. with Symbian), it's better to do it now than 2 years down the road.
 
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#70
Again, no need to worry. All those pesky applications will be deprecated and only MicroB will ship in the default rootfs.... the rest will be "community" maintained.
 

The Following User Says Thank You to javispedro For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 07:39.