Even more off-topic... How much work would it take to fit every important feature of OOo into the Maemo 5 HIG? It would be very difficult. But, if we could, I think it would quickly become a Maemo Star.

Tim

Interesting. So a possible win for Nokia AND Microsoft vs RIM.

This makes sense in another way: Nokia finally canned the Lotus enterprise suite to be replaced by SharePoint for in-house use... scheduled for after I was gone of course.

I hate Notes.

people, do not forget that this will benefit E-series products, maemo is used on N-series products...

Tim, that would Rock The World. Too bad it isn't a path to riches. Fame, maybe, but that doesn't tend to drive the average developer as much as money.

Actually, it benefits E-Series devices from the outset with the Office Communicator Mobile portion. Its the future development that will see other Nokia devices added t the fold.

FYI: Office 2010 goes web-based; and will be supported in multiple browsers; Maemo 5 uses a variant of the Firefox Geko engine, therefore it should be possible that not only its supported not long after release, but with a change on MS's end, or even with the addition of an extension, that Maemo 5 will be office friendly and ready with little end-user effort.

Ding!

EDIT:
Share Point is a huge cash cow right now, and Nokia basically got into bed with the perfect situation to get enterprise acceptance (easily) into govs and private businesses alike. All at the simple cost of making the already existing E-Series devices further compatible with Exchange environments.

Maemo has nothing on Symbian in this regard; and given the price of Symbian devices going down, can you say win-win.

Now, on the Maemo side, think a Qt-coded browser and accompanying controls...

I would help do it if we new we could. Maybe we should start a wiki page:

• Outline important features
• Break-down important menus
• Wireframe OOo->HIG designs
• Create high fidelity UI

Not so much... Who would take care of integrating UI, graphics, etc.? Would we ask OOo?

Tim

Imagine a web version of MS Office that's 100% services, where you could wrap any UI around it...

for some reason, my hear was gray for a moment...

MS Office can do that (indeed, I've seen solutions which drive MS Word in exactly that way for a couple of pieces of its functionality).

The problem is that the UI is just as big - if not bigger - than the rest of the app; an issue which is overlooked in practically every single major project I've ever seen.

So a web-based service-oriented version of MS Office would give you - at most - 50% of the required code.

one thing about ms office btw, it seems to have mutated into some kind of RAD of in-offfice solutions...