[Qt-components] QML component APIs and techniques
Aaron J. Seigo
aseigo at kde.org
Thu Jan 10 12:33:59 CET 2013
On Wednesday, January 9, 2013 20:13:50 Marco Martin wrote:
> What i would suggest, is for each part to list here the components that we
> would like to see standardized (or more generic things, like theming api),
> then we can discuss them, move things in, move things out...
>
> How does it sound?
to me, this sounds great.
to refine the proposal on how to facilitate the standardization, i would
propose this:
once we have our list of targets, to then have someone (anyone, but someone
who will help take this process through to completion :) take each component
one by one in whatever order amuses them and start a thread on this list for
that component. a wiki page for that component should also be started
$SOMEWHERE[1] for each component to catch the results.
we can then do up a quick matrix on the wiki page of each property seen for
that component across all the component sets. sth like:
==Button==
===All Existing Properties===
Property type allowed values purpose
text any any optional text to be shown on button
icon image null or a valid image optional image for the button
..etc ..
===Implementations===
Property Qt Desktop Plasma Canonical Jolla RIM
text x x x x x
icon x x x x x
squirqle
dingbat x x x
foo x x x
..etc..
===Standardized Set of Properties===
...
then we can figure out which properties we want standardized. perhaps each
project could fill in the blank spaces in the table for their component set
with a mark denoting "would like to standardize on this" to short circuit the
discussions a bit. then we can discuss the remaining items: what is their
purpose, how are they defined, etc.
once we have our decided set of properties, each group can implement the ones
they are missing, updating the table as we go.
this should give us a definition of "standardized API" and where each
implementation is. this will be valuable to us working towards this goal, but
will be absolute *invaluable* to developers trying to write applications that
target more than one of our platforms :)
thoughts?
[1] i'm happy to offer community.kde.org for that, and even author the pages
based on the discussion, but if there is a better place that is also fine
--
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/20130110/3b237c39/attachment.bin
More information about the Qt-components
mailing list