[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: KDE Platform Profiles
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: 2010-04-26 17:14:28
Message-ID: 201004261014.29436.aseigo () kde ! org
[Download RAW message or body]
On April 26, 2010, Sune Vuorela wrote:
> It is a very large job to figure out for all kde apps which parts of
> kdelibs&runtime (executables, kio slaves, kparts, and so on) requires.
big job, but one that we need to do. :)
> I would suggest that it is the application maintainer who specify which
> runtime components it needs. Maybe runtime components needed in 3
> 'levels'.
while i think this would be quite good for packaging and agree with what you
say on that, i don't believe this would help us one bit from the software
development side.
what would end up happening is every app would just define what it wanted to
use in these manifests and we'd end up right we were are now: with everything
being needed and no well defined set of "this will be there, that won't" API /
functionality for a given form factor.
it also won't do a great job of addressing the issue of things like "when
plasma is used on tablet or bigger, accessing widgets via GHNS makes sense and
so that's a valid API to use and rely on as a build-time requirement; on
mobile, it doesn't make any sense (devices tend to have their own app
delivery/update mechanism). i suppose one could expand the manifests to
include different dependency sets for different profiles ... but then we're
back to what we're doing now.
the one thing a manifest can not do at all is define things like "i don't need
KCoolClassThatOnlyMakesSenseOnTheDesktop from kdeui when used on a mobile
device form factor".
so while i like the ideas of the manifests as you outline them (which are also
a lot of work, of course :) they are somewhat orthogonal to getting to the
solutions we need here.
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Bitstream Vera Sans'; font-size:12pt; \
font-weight:400; font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">On April 26, 2010, Sune Vuorela wrote:</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> It is a very large job \
to figure out for all kde apps which parts of</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> kdelibs&runtime (executables, kio \
slaves, kparts, and so on) requires.</p> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">big job, but one that we need \
to do. :)</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"> </p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> I would suggest that it \
is the application maintainer who specify which</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> runtime components it needs. Maybe runtime \
components needed in 3</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> 'levels'.</p> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">while i think this would be \
quite good for packaging and agree with what you say on that, i don't believe this \
would help us one bit from the software development side.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">what would end up happening \
is every app would just define what it wanted to use in these manifests and we'd end \
up right we were are now: with everything being needed and no well defined set of \
"this will be there, that won't" API / functionality for a given form \
factor.</p> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">it also won't do a great job of addressing the issue of things \
like "when plasma is used on tablet or bigger, accessing widgets via GHNS makes \
sense and so that's a valid API to use and rely on as a build-time requirement; on \
mobile, it doesn't make any sense (devices tend to have their own app delivery/update \
mechanism). i suppose one could expand the manifests to include different dependency \
sets for different profiles ... but then we're back to what we're doing now.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">the one thing a manifest can \
not do at all is define things like "i don't need \
KCoolClassThatOnlyMakesSenseOnTheDesktop from kdeui when used on a mobile device form \
factor".</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">so while i like the ideas of the manifests as you \
outline them (which are also a lot of work, of course :) they are somewhat orthogonal \
to getting to the solutions we need here.</p> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">-- </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Aaron J. Seigo</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">humru othro a kohnu se</p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">GPG Fingerprint: 8B8B 2209 \
0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43</p> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">KDE core developer sponsored \
by Qt Development Frameworks</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic