Necessitas/TODO: Difference between revisions

From KDE Community Wiki
 
(24 intermediate revisions by the same user not shown)
Line 8: Line 8:
! Status  
! Status  
! Description  
! Description  
! Contact
! Difficulty


{{FeatureInProgress  
{{FeatureInProgress
|Compile and run all test and benchmarks, also make sure they pass
|Compile and run all test and benchmarks, also make sure they pass
|x}}
|Easy
}}


{{FeatureTodo
{{FeatureInProgress
|QSystemTrayIcon
|QSystemTrayIcon
|x}}
|Medium}}


{{FeatureInProgress4
{{FeatureInProgress
|x86 support
|x86 support
|Medium}}


{{FeatureInProgress4
{{FeatureInProgress
|Rewrite/redesign the software keyboard support
|Android style plugin.Qt apps must look the same as native Android apps.
|Hard}}


{{FeatureInProgress
|Android menus simulation/use. We need to find a way to use android native menus.
|Hard}}


{{FeatureTodo
{{FeatureTodo
|Android style plugin. We must to implement an android plugin, Qt apps must look the same as native Android apps.
|Find a way to compile for all android platforms at once, switch to [http://doc-snapshot.qt-project.org/qbs/index.html QBS]
|Alessandro}}
|Medium}}
|}


{{FeatureTodo
= QtCreator =
|Android menus simulation/use. We need to find a way to use android menus or to paint them from Qt.
 
|Marius}}
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
 
! Status
! Description
! Difficulty
 
{{FeatureInProgress
|x86 support
|Easy}}


{{FeatureTodo
{{FeatureTodo
|Find a way to compile for all android platforms at once
| Switch to [http://doc-snapshot.qt-project.org/qbs/index.html QBS], is the only way to compile for all android platforms at once
|BogDan}}
| Hard }}
 
|}
|}


= QtCreator =
=QtMobility=
 
==Support all android platforms==
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
Line 48: Line 61:
! Status  
! Status  
! Description  
! Description  
! Contact
! Difficulty


{{FeatureInProgress4
{{FeatureTodo
|x86 support
|Contacts implementation needs to be reviewd/rewritten, it crashes on my phone with 150+ contacts.
|Medium}}
 
{{FeatureTodo
|Check all mobility modules
|Medium}}


{{FeatureTodo
{{FeatureTodo
|Find a way to compile for all android platforms at once, and handle the results corectly
|Multimedia module
|x}}
|Hard}}


{{FeatureTodo
{{FeatureTodo
|Written documentation for Android platform
|Proper camera implementation
|x}}
|Hard}}


|}
|}
=QtMobility=
==Support all android platforms==
* Find a way to support as many android platforms we can. Currently platforms < android-8 are not supported by all QtMobility modules.


=QtWebKit=
=QtWebKit=
==Speed and memory usage==
==Speed==
* QtWebKit 2.2.x is still 2x times slower than Google's WebKit.
* QtWebKit 2.2.x is still 2x times slower than Google's WebKit.
=Android QML Controls=
Create Android QML Controls which looks and feel like native Android controls, you have to use Ministro's extracted look & feel data for every device which is already used by classic controls. To find out how to use the data, please take a look to qandroidstyle plugin.
Yes we know that there are a some implementation out there based on MeeGO/Symbian implementations, the problem is that apps made using these implementation looks & feels like MeeGO/Symbian apps not like Android apps.
=QBS=
* QBS is extremely important for QtCreator used by Necessitas project, it will actually make the difference between another IDE for Android and '''the''' IDE for Android.
{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Description
! Difficulty
{{FeatureTodo
|Find a better way to probe the toolchains and platforms, check [http://lists.qt-project.org/pipermail/qbs/2012-March/000062.html this] and [http://lists.qt-project.org/pipermail/qbs/2012-June/000159.html this] threads.
|Hard}}
{{FeatureTodo
| Find a way to configure the projects
|Hard }}
|}


=Platform Issues=
=Platform Issues=

Latest revision as of 11:03, 30 July 2012

Welcome to the Necessitas TODO wiki page

Qt framework

Status Description Difficulty
IN PROGRESS Compile and run all test and benchmarks, also make sure they pass Easy


IN PROGRESS QSystemTrayIcon Medium


IN PROGRESS x86 support Medium


IN PROGRESS Android style plugin.Qt apps must look the same as native Android apps. Hard


IN PROGRESS Android menus simulation/use. We need to find a way to use android native menus. Hard


TO DO Find a way to compile for all android platforms at once, switch to QBS Medium <{{{3}}}>

QtCreator

Status Description Difficulty
IN PROGRESS x86 support Easy


TO DO Switch to QBS, is the only way to compile for all android platforms at once Hard <{{{3}}}>

QtMobility

Support all android platforms

Status Description Difficulty
TO DO Contacts implementation needs to be reviewd/rewritten, it crashes on my phone with 150+ contacts. Medium <{{{3}}}>


TO DO Check all mobility modules Medium <{{{3}}}>


TO DO Multimedia module Hard <{{{3}}}>


TO DO Proper camera implementation Hard <{{{3}}}>


QtWebKit

Speed

  • QtWebKit 2.2.x is still 2x times slower than Google's WebKit.

Android QML Controls

Create Android QML Controls which looks and feel like native Android controls, you have to use Ministro's extracted look & feel data for every device which is already used by classic controls. To find out how to use the data, please take a look to qandroidstyle plugin. Yes we know that there are a some implementation out there based on MeeGO/Symbian implementations, the problem is that apps made using these implementation looks & feels like MeeGO/Symbian apps not like Android apps.

QBS

  • QBS is extremely important for QtCreator used by Necessitas project, it will actually make the difference between another IDE for Android and the IDE for Android.


Status Description Difficulty
TO DO Find a better way to probe the toolchains and platforms, check this and this threads. Hard <{{{3}}}>


TO DO Find a way to configure the projects Hard <{{{3}}}>

Platform Issues

Windows

  • Make it so that the Windows version can be built from Linux (mingw cross compiler support, quite a lot of work, esp. building Python which needs to run itself to compile the modules under Wine)
  • Fix make.exe -j support (would help with building on Windows as otherwise it requires baby-sitting).
  • Add support to 7za and installer-framework for symbolic links on Windows (see msdos command mklink) so there's no need to remove symlinks from the packages (and also MinGW's ln program)
  • Fix webkit build failure on Windows and Mac OS X
  • Fix installer framework so that it can install from local packages folder instead of always having to use the network -> this already works on Mac OS X (just modify config.xml to use file:/usr/www/ etc), but not on Windows (where it works partially, updates.xml is loaded but nothing else); I'm not sure about Linux, maybe add a command line option to override the repo url?