[Qt-components] QML component APIs and techniques
Aaron J. Seigo
aseigo at kde.org
Fri Jan 11 01:12:57 CET 2013
On Friday, January 11, 2013 09:22:00 you wrote:
> The Meego and Symbian components have a large API, so I think they should
> be used as a reference for naming the properties, rather than a starting
> point for an API.
while i agree that they have a lot to offer in terms of experience based
results that we can use as reference, they are also dead platform with limited
software available for them. if there is reason to diverge, the pre-existence
of these implementations should not hold us back imho.
> The trick is to define a minimal API, e.g. a Button has "text" property and
> "clicked" signal. Much more than that and it won't suit some platforms,
> especially those that are performance conscience and don't want features
> unnecessary for their design.
yes, we can define a minimal API. but most platforms will want more than that.
we know that because, well, they provide more than that. and that "more" needs
to be consistent.
i'd support the idea of marking API as "minimally required for conformance"
(whatever that might actually mean :), but we need to remain realistic and
recognize that the APIs will be richer on most platforms, and that richness is
precisely what we need to harmonize.
> > Did anyone look into standard icon naming? (which was oddly one of the
> > bigger problems when co-ordinating meego vs symbian API).
freedesktop.org has a standard for this. we can extend it as needed. i would
not suggest creating our own new standard for this, but to follow the
freedesktop.org one. this makes it far easier for applications which already
follow this (1000s) to be ported.
--
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-components/attachments/20130111/7bd2516f/attachment.bin
More information about the Qt-components
mailing list