[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: kde-devel Digest, Vol 84, Issue 42
From: Dinesh <saidinesh5 () gmail ! com>
Date: 2010-03-22 0:12:07
Message-ID: 2ca5cc7a1003211700u274e304eu6c675e70dcf7bbcb () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all,
A Diumenge, 21 de mar? de 2010, Oswald Buddenhagen va escriure:
>
> > On Sun, Mar 21, 2010 at 03:28:38PM +0530, Dinesh wrote:
> > > I am Dinesh, an undergraduate looking to spend my summer contributing
> > > full-time to KDE via the Google Summer of Code by making A proper
> > > Smartphone managing suite for KDE.
> >
> > this project idea sounds like it would be duplicating a lot of
> > http://labs.trolltech.com/page/Projects/QtMobility
>
> But as I understand it's almost impossible to get Nokia to accept big
> contributions to Qt (as oposed to bugfixes that seems to be working quite
> good) so are you suggesting that he just does nothing waiting for you to
code
> it? What if QtMobility doesn't end up working at the end or is a totally
> different thing?
1 small point from my side(somebody correct me if i am wrong) . even if qt
mobility provides the functionality, isnt qtmobility supposed to be talking
to the non-nokia platforms using their standard api that they give?? i mean
from whatever i ve read till now, SyncML is supposed to be a standardrized,
open platform for exchanging information. so isnt all i am doing is using
one open library instead of some another open library??
> yes, this is a known deficit which is being addressed. somehow.
> somewhen.
>
> > so are you suggesting that he just does nothing waiting for you to
> > code it?
> >
> that's one possibility. duplication would certainly affect kde's
> decision on spending a soc slot on it.
>
> > What if QtMobility doesn't end up working at the end
> >
> success is the only option. ;)
>
> > or is a totally different thing?
> >
> investigating this thoroughly would be part of pursuing this gsoc
> proposal further.
Yes, i agree.
>
> Is the mobility project an effort to get Qt to run on mobile
> platforms, or is an effort to get Qt on existing platforms to connect
> to mobile devices? I may just have missed it but I cannot find a
> clear explanation of what the actual goals of the project are. The
> best I could find is:
>
> "Our goal is to make Qt an even more comprehensive application and UI
> framework by developing new APIs addressing mobile functionality.
> Ultimately this will enable rich mobile applications to run across
> many more platforms? Nokia and non-Nokia platforms! Why didn?t we
> think of this earlier!"
>
> This seems to imply that it is designed to run on mobile platforms,
> but isn't very clear about that. I am sure you know far more about it
> then I do, but it might be a good idea for the people in the project
> to add more specific information on the site explaining exactly what
> they intend to do. Because based on the website and blog at least I
> couldn't find any indication they intend to support the sort of
> capabilities Dinesh suggested.
>
> One possible solution would be for Dinesh to write a system which
> support the addition of new device backends to support new sorts of
> devices. That way we aren't limited to the sorts of devices he had
> time to code for. Additionally, this would allow for a wrapper
> backend to be written for Qt mobility when and if the Qt mobility
> project supports the stuff his project needs, and any redundant
> backends could be phased out at that time while ones that support
> devices the Qt mobility project does not support or supports them
> better can be kept. Even if the Qt mobility project does everything,
> we still need KDE to be set up to take advantage of those
> capabilities.
>
> -Todd
I totally agree with this, but i have to admit, the only back-ends i worked
on till now are obexfs/obexftp for file transfer and opensync 's syncml for
getting contacts from my phone...so i am more of an illiterate when it comes
to the other backends available.... even though i am totally ready to learn
more(but i really need help on this, cuz it will be like researching on
things that i dont yet know)..
"qt mobility" is an umbrella project for "everything which has to do
>
> with mobile devices". in my book that includes synchronization. i don't
> know the details and i'm not sure how much i'd be allowed to talk about
> them anyway. ask the responsible trolls in #qt-labs at brisbane working
> hours.
can any one do this for me please?? my college blocked all the IRC channels
and i have my mid term exams this week, so by the time my exams are
done(this saturday), the bonding time with mentoring organizations will be
almost over.
> > "qt mobility" is an umbrella project for "everything which has to do
> > with mobile devices". in my book that includes synchronization. i don't
> > know the details and i'm not sure how much i'd be allowed to talk about
> > them anyway. ask the responsible trolls in #qt-labs at brisbane working
> > hours.
>
> If that is the case the website should probably say it. The website
> is not currently very clear.
once again, here is the link that might clarify things a bit:
http://qt.nokia.com/doc/qtmobility-1.0-beta/index.html#platform-compatability
in this link nokia says :
"A functional backend for the API on the platform is not being worked on. It
is possible for others to implement and integrate support."
for contacts on any of the desktop platforms (Windows,Linux,Mac OS)
however it also says:
"A functional backend for the API on the platform is being worked however it
is not functionally complete."
for versit for all the qt platforms.
(again, somebody correct me if i am wrong) i guess the only thing that means
is that the desktop platforms themselves have to implement the PIM modules
and QTMobility project can be used to make vcard, vcalender, vtodo files
etc. so that means someone still has to write a way to get Kontact to
exchange information with mobile phones, and doesnt that mean we are back to
where we have started?
Dinesh
[Attachment #5 (text/html)]
Hi all,<br><br>A Diumenge, 21 de mar? de 2010, Oswald Buddenhagen va \
escriure:<br>><br>> > On Sun, Mar 21, 2010 at 03:28:38PM +0530, Dinesh \
wrote:<br>> > > I am Dinesh, an undergraduate looking to spend my summer \
contributing<br> > > > full-time to KDE via the Google Summer of Code by \
making A proper<br>> > > Smartphone managing suite for KDE.<br>> \
><br>> > this project idea sounds like it would be duplicating a lot of<br> \
> > <a href="http://labs.trolltech.com/page/Projects/QtMobility">http://labs.trolltech.com/page/Projects/QtMobility</a><br>><br>> \
But as I understand it's almost impossible to get Nokia to accept big<br>> \
contributions to Qt (as oposed to bugfixes that seems to be working quite<br> > \
good) so are you suggesting that he just does nothing waiting for you to code<br>> \
it? What if QtMobility doesn't end up working at the end or is a totally<br>> \
different thing?<br><br>1 small point from my side(somebody correct me if i am \
wrong) . even if qt mobility provides the functionality, isnt qtmobility supposed to \
be talking to the non-nokia platforms using their standard api that they give?? i \
mean from whatever i ve read till now, SyncML is supposed to be a standardrized, \
open platform for exchanging information. so isnt all i am doing is using one
open library instead of some another open library??<br> <br>> yes, this is a \
known deficit which is being addressed. somehow.<br>> somewhen.<br>><br>> \
> so are you suggesting that he just does nothing waiting for you to<br> > > \
code it?<br>> ><br>> that's one possibility. duplication would certainly \
affect kde's<br>> decision on spending a soc slot on it.<br>><br>> > \
What if QtMobility doesn't end up working at the end<br> > ><br>> \
success is the only option. ;)<br>><br>> > or is a totally different \
thing?<br>> ><br>> investigating this thoroughly would be part of pursuing \
this gsoc<br>> proposal further.<br><br> Yes, i agree.<br><br>><br>> Is the \
mobility project an effort to get Qt to run on mobile<br>> platforms, or is an \
effort to get Qt on existing platforms to connect<br>> to mobile devices? I may \
just have missed it but I cannot find a<br> > clear explanation of what the actual \
goals of the project are. The<br>> best I could find is:<br>><br>> \
"Our goal is to make Qt an even more comprehensive application and UI<br>> \
framework by developing new APIs addressing mobile functionality.<br> > Ultimately \
this will enable rich mobile applications to run across<br>> many more platforms? \
Nokia and non-Nokia platforms! Why didn?t we<br>> think of this \
earlier!"<br>><br>> This seems to imply that it is designed to run on \
mobile platforms,<br> > but isn't very clear about that. I am sure you know \
far more about it<br>> then I do, but it might be a good idea for the people in \
the project<br>> to add more specific information on the site explaining exactly \
what<br> > they intend to do. Because based on the website and blog at least \
I<br>> couldn't find any indication they intend to support the sort of<br>> \
capabilities Dinesh suggested.<br>><br>> One possible solution would be for \
Dinesh to write a system which<br> > support the addition of new device backends \
to support new sorts of<br>> devices. That way we aren't limited to the sorts \
of devices he had<br>> time to code for. Additionally, this would allow for a \
wrapper<br> > backend to be written for Qt mobility when and if the Qt \
mobility<br>> project supports the stuff his project needs, and any \
redundant<br>> backends could be phased out at that time while ones that \
support<br>> devices the Qt mobility project does not support or supports them<br> \
> better can be kept. Even if the Qt mobility project does everything,<br>> we \
still need KDE to be set up to take advantage of those<br>> \
capabilities.<br>><br>> -Todd<br><br>I totally agree with this, but i have to \
admit, the only back-ends i worked on till now are obexfs/obexftp for file transfer \
and opensync 's syncml for getting contacts from my phone...so i am more of an \
illiterate when it comes to the other backends available.... even though i am totally \
ready to learn more(but i really need help on this, cuz it will be like researching \
on things that i dont yet know)..<br> <br><br> "qt mobility" is an umbrella \
project for "everything which has to do<br>><br>> with mobile \
devices". in my book that includes synchronization. i don't<br>> know the \
details and i'm not sure how much i'd be allowed to talk about<br> > them \
anyway. ask the responsible trolls in #qt-labs at brisbane working<br>> \
hours.<br><br>can any one do this for me please?? my college blocked all the IRC \
channels and i have my mid term exams this week, so by the time my exams are \
done(this saturday), the bonding time with mentoring organizations will be almost \
over.<br> <br>> > "qt mobility" is an umbrella project for \
"everything which has to do<br>> > with mobile devices". in my book \
that includes synchronization. i don't<br>> > know the details and i'm \
not sure how much i'd be allowed to talk about<br> > > them anyway. ask the \
responsible trolls in #qt-labs at brisbane working<br>> > \
hours.<br>><br>> If that is the case the website should probably say it. The \
website<br>> is not currently very clear.<br> <br>once again, here is the link \
that might clarify things a bit:<br><a \
href="http://qt.nokia.com/doc/qtmobility-1.0-beta/index.html#platform-compatability">h \
ttp://qt.nokia.com/doc/qtmobility-1.0-beta/index.html#platform-compatability</a><br> \
<br>in this link nokia says :<br><br>"A functional backend for the API on the \
platform is not being worked on. It is possible for others to implement and integrate \
support."<br>for contacts on any of the desktop platforms (Windows,Linux,Mac \
OS)<br> <br>however it also says:<br>"A functional backend for the API on the \
platform is being worked however it is not functionally complete."<br>for \
versit for all the qt platforms. <br><br>(again, somebody correct me if i am wrong) i \
guess the only thing that means is that the desktop platforms themselves have to \
implement the PIM modules and QTMobility project can be used to make vcard, \
vcalender, vtodo files etc. so that means someone still has to write a way to get \
Kontact to exchange information with mobile phones, and doesnt that mean we are back \
to where we have started?<br> <br><span class="anchor" id="line-42"></span><span \
class="anchor" id="line-43"></span> <span class="anchor" id="line-44"></span><span \
class="anchor" id="line-45"></span><span class="anchor" \
id="line-46"></span><br>Dinesh<br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic