[prev in list] [next in list] [prev in thread] [next in thread] 

List:       meego-dev
Subject:    [MeeGo-dev] The role of Qt Mobility APIs in MeeGo OS (WAS: RE:
From:       thiago () kde ! org (Thiago Macieira)
Date:       2010-09-15 21:36:25
Message-ID: 201009152236.44478.thiago () kde ! org
[Download RAW message or body]

On Wednesday 15. September 2010 20.42.40 Jari.Palojarvi at nokia.com wrote:
> Standardizing a low(er) level C API to each middleware level ?service? in
> MeeGo OS would have two benefits:
> 
> - A single Qt Mobility API backend implementation would suffice
>   => no need for vendor specific implementations
> 
> - There would be a standard way to integrate middleware level
>   SW components via C APIs => less need for vendor specifics
>   in the middleware level (C++ APIs such as the Qt Mobility
>   APIs are somewhat hard to use from C so middleware components
>   written in C will typically use some other integration routes)

And a drawback:

- it's another level of indirection and abstraction, introducing potential 
delays and complexity (translating information from one format to another) and 
it's also a source of potential bugs.

I'm not saying the middlewares are of bad quality. Not at all.

But I don't want to see a middleware be written and added just because none 
existed before. A middleware has to have a reason to exist, a value to add.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.meego.com/pipermail/meego-dev/attachments/20100915/f673b881/attachment.pgp>

[prev in list] [next in list] [prev in thread] [next in thread]