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

List:       kde-devel
Subject:    Re: GSoC project idea:solving smartphone management problem
From:       todd rme <toddrme2178 () gmail ! com>
Date:       2010-03-21 14:14:57
Message-ID: 6524e4801003210714o32220bffnf87421432d957c2d () mail ! gmail ! com
[Download RAW message or body]

On Sun, Mar 21, 2010 at 6:55 AM, Oswald Buddenhagen <ossi@kde.org> wrote:
> 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

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
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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