QTMapWidget - Revision history

joerg_rw: Undo revision 45989 by 114.79.28.10 (Talk) vandalism/spam

2011-12-15T06:24:37Z

Undo revision 45989 by 114.79.28.10 (Talk) vandalism/spam

← Older revision		Revision as of 06:24, 15 December 2011
Line 100:		Line 100:
	== Count me in! ==		== Count me in! ==

-	We need some people who would like to contribute. Please state here if you want to contribute some of your time ~~[http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm]~~.	+	We need some people who would like to contribute. Please state here if you want to contribute some of your time.

	Widget coding:		Widget coding:

114.79.28.10: /* Count me in! */

2011-12-15T03:04:47Z

Count me in!

← Older revision		Revision as of 03:04, 15 December 2011
Line 100:		Line 100:
	== Count me in! ==		== Count me in! ==

-	We need some people who would like to contribute. Please state here if you want to contribute some of your time.	+	We need some people who would like to contribute. Please state here if you want to contribute some of your time [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm].

	Widget coding:		Widget coding:

amigadave: categorize and wikify slightly

2010-06-16T12:10:23Z

categorize and wikify slightly

← Older revision		Revision as of 12:10, 16 June 2010
Line 1:		Line 1:
-	This page is intended to collect thoughts about a QT map widget.	+	This page is intended to collect thoughts about a Qt map widget.

	== Why a QTMapWidget? ==		== Why a QTMapWidget? ==

-	Maemo/Meego devices are mobile GPS based devices. A demand for mapping services is thus very obvious. The current situation in ~~Maemo5~~ shows that leaving this task to the individual developers has several disadvantages for the developer as well for the end user.	+	Maemo/Meego devices are mobile GPS based devices. A demand for mapping services is thus very obvious. The current situation in [[Open development/Maemo roadmap/Fremantle\|Maemo 5]] shows that leaving this task to the individual developers has several disadvantages for the developer as well for the end user.

	=== Disadvantages of current Maemo5 situation ===		=== Disadvantages of current Maemo5 situation ===
Line 29:		Line 29:
	* Support for various map sources		* Support for various map sources
	** Classic tile based sources (openstreetmap [http://www.openstreetmap.org], google [http://maps.google.com], yahoo [http://maps.yahoo.com], virtual earth [http://www.bing.com/maps/])		** Classic tile based sources (openstreetmap [http://www.openstreetmap.org], google [http://maps.google.com], yahoo [http://maps.yahoo.com], virtual earth [http://www.bing.com/maps/])
-	*** Simple/dynamic method to add more sources (also user specific ones like [~~http://wiki.maemo.org/~~Maemo-~~mapper_topomaps~~])	+	*** Simple/dynamic method to add more sources (also user specific ones like [[Maemo-mapper topomaps]])
	** WMS data [http://www.ogc-services.net/]		** WMS data [http://www.ogc-services.net/]
	** Vector data		** Vector data
Line 60:		Line 60:
	== Related resources ==		== Related resources ==

-	QT mobility location [http://labs.trolltech.com/page/Projects/QtMobility]	+	Qt mobility location [http://labs.trolltech.com/page/Projects/QtMobility]

	== Existing widgets ==		== Existing widgets ==

-	We are not the first ones to work with maps under QT. What projects exist? Can they be re-used? What are their advantages and disadvantages?	+	We are not the first ones to work with maps under Qt. What projects exist? Can they be re-used? What are their advantages and disadvantages?

	=== QMapControl [http://www.medieninf.de/qmapcontrol/] ===		=== QMapControl [http://www.medieninf.de/qmapcontrol/] ===
Line 83:		Line 83:
	Pros:		Pros:
	* Very active big developer community. Some core developers are involved with the Maemo / MeeGo project already. There are currently 3 GSoC developers working exclusively on Marble.		* Very active big developer community. Some core developers are involved with the Maemo / MeeGo project already. There are currently 3 GSoC developers working exclusively on Marble.
-	* Support for ~~Maemo5~~ and MeeGo. Early ~~Maemo5~~ packages available.	+	* Support for Maemo 5 and MeeGo. Early Maemo 5 packages available.
	* Lightweight for what it does (100000LOC).		* Lightweight for what it does (100000LOC).
	* Used in KDE as a generic map widget already.		* Used in KDE as a generic map widget already.
Line 94:		Line 94:

	Cons:		Cons:
-	* Performance improvements for ~~Maemo5~~ necessary. However these are in the works.	+	* Performance improvements for Maemo 5 necessary. However these are in the works.
	* While the overall quality of the code is pretty good there is still some legacy code in a few places.		* While the overall quality of the code is pretty good there is still some legacy code in a few places.
	* I am very concerned regarding battery usage with this 3d approach as it puts a huge load (currently 100%) on the CPU even at low refresh rates --[[User:harbaum\|harbaum]] 18:40, 12 June 2010 (UTC)		* I am very concerned regarding battery usage with this 3d approach as it puts a huge load (currently 100%) on the CPU even at low refresh rates --[[User:harbaum\|harbaum]] 18:40, 12 June 2010 (UTC)
Line 109:		Line 109:

	UI-Design, Mockups:		UI-Design, Mockups:
		+
		+	[[Category:Development]]
		+	[[Category:Qt]]

harbaum: /* Marble [http://edu.kde.org/marble/] */

2010-06-12T18:40:14Z

Marble [http://edu.kde.org/marble/]

← Older revision		Revision as of 18:40, 12 June 2010
Line 96:		Line 96:
	* Performance improvements for Maemo5 necessary. However these are in the works.		* Performance improvements for Maemo5 necessary. However these are in the works.
	* While the overall quality of the code is pretty good there is still some legacy code in a few places.		* While the overall quality of the code is pretty good there is still some legacy code in a few places.
-	* I am very concerned regarding battery usage with this 3d approach as it puts a huge load (currently 100%) on the CPU even at low refresh rates	+	* I am very concerned regarding battery usage with this 3d approach as it puts a huge load (currently 100%) on the CPU even at low refresh rates --[[User:harbaum\|harbaum]] 18:40, 12 June 2010 (UTC)

	== Count me in! ==		== Count me in! ==

88.130.221.136: /* Marble [http://edu.kde.org/marble/] */

2010-06-12T18:39:35Z

Marble [http://edu.kde.org/marble/]

← Older revision		Revision as of 18:39, 12 June 2010
Line 96:		Line 96:
	* Performance improvements for Maemo5 necessary. However these are in the works.		* Performance improvements for Maemo5 necessary. However these are in the works.
	* While the overall quality of the code is pretty good there is still some legacy code in a few places.		* While the overall quality of the code is pretty good there is still some legacy code in a few places.
		+	* I am very concerned regarding battery usage with this 3d approach as it puts a huge load (currently 100%) on the CPU even at low refresh rates

	== Count me in! ==		== Count me in! ==

tackat: /* Marble [http://edu.kde.org/marble/] */

2010-06-11T18:53:39Z

Marble [http://edu.kde.org/marble/]

← Older revision		Revision as of 18:53, 11 June 2010
Line 85:		Line 85:
	* Support for Maemo5 and MeeGo. Early Maemo5 packages available.		* Support for Maemo5 and MeeGo. Early Maemo5 packages available.
	* Lightweight for what it does (100000LOC).		* Lightweight for what it does (100000LOC).
-	* Used in KDE as a generic map widget.	+	* Used in KDE as a generic map widget already.
	* Supports OpenStreetMap, Google Maps, Yahoo, Custom Server Layouts. Basic WMS support.		* Supports OpenStreetMap, Google Maps, Yahoo, Custom Server Layouts. Basic WMS support.
		+	* Online Routing support (via e.g. ORS).
		+	* Support for position providers as plugins (gpsd, GeoClue, liblocation).
		+	* Support for KML, GPS (support for OSM in the works).
		+	* Different projections (sphere, Mercator, Equirectangular).
		+	* Qt-Style API throughout the Marble Library.
		+
		+	Cons:
		+	* Performance improvements for Maemo5 necessary. However these are in the works.
		+	* While the overall quality of the code is pretty good there is still some legacy code in a few places.

	== Count me in! ==		== Count me in! ==

harbaum: /* QMapControl [http://www.medieninf.de/qmapcontrol/] */

2010-06-11T18:37:54Z

QMapControl [http://www.medieninf.de/qmapcontrol/]

← Older revision		Revision as of 18:37, 11 June 2010
Line 75:		Line 75:
	Cons:		Cons:
	* Not actively maintained atm		* Not actively maintained atm
-	* Lacks basic functionality (GPS integration, ~~dynamic~~ track ~~cature~~, ...)	+	* Lacks basic functionality (GPS integration, live track capture, ...)
	* Has some rendering problems under Maemo (track display)		* Has some rendering problems under Maemo (track display)
	* Google maps integration broken		* Google maps integration broken

harbaum: /* Wishlist */

2010-06-11T18:36:12Z

Wishlist

← Older revision		Revision as of 18:36, 11 June 2010
Line 29:		Line 29:
	* Support for various map sources		* Support for various map sources
	** Classic tile based sources (openstreetmap [http://www.openstreetmap.org], google [http://maps.google.com], yahoo [http://maps.yahoo.com], virtual earth [http://www.bing.com/maps/])		** Classic tile based sources (openstreetmap [http://www.openstreetmap.org], google [http://maps.google.com], yahoo [http://maps.yahoo.com], virtual earth [http://www.bing.com/maps/])
-	*** Simple/dynamic method to add more sources (also user specific ones)	+	*** Simple/dynamic method to add more sources (also user specific ones like [http://wiki.maemo.org/Maemo-mapper_topomaps])
	** WMS data [http://www.ogc-services.net/]		** WMS data [http://www.ogc-services.net/]
	** Vector data		** Vector data

tackat: /* Marble [http://edu.kde.org/marble/] */

2010-06-11T18:35:50Z

Marble [http://edu.kde.org/marble/]

← Older revision		Revision as of 18:35, 11 June 2010
Line 86:		Line 86:
	* Lightweight for what it does (100000LOC).		* Lightweight for what it does (100000LOC).
	* Used in KDE as a generic map widget.		* Used in KDE as a generic map widget.
		+	* Supports OpenStreetMap, Google Maps, Yahoo, Custom Server Layouts. Basic WMS support.

	== Count me in! ==		== Count me in! ==

tackat: /* Marble [http://edu.kde.org/marble/] */

2010-06-11T18:34:25Z

Marble [http://edu.kde.org/marble/]

← Older revision		Revision as of 18:34, 11 June 2010
Line 81:		Line 81:
	=== Marble [http://edu.kde.org/marble/] ===		=== Marble [http://edu.kde.org/marble/] ===

-	~~Looks pretty complex, do we want~~ the ~~basic~~ map widget ~~to be that complex?~~	+	Pros:
		+	* Very active big developer community. Some core developers are involved with the Maemo / MeeGo project already. There are currently 3 GSoC developers working exclusively on Marble.
		+	* Support for Maemo5 and MeeGo. Early Maemo5 packages available.
		+	* Lightweight for what it does (100000LOC).
		+	* Used in KDE as a generic map widget.

	== Count me in! ==		== Count me in! ==