KDE TechBase - User contributions [en]

Projects/Marble/GeoData/GeoDataWriter

2009-08-03T10:50:10Z

Mansona: Created page with '== Writing XML documents with Marble == * How to set the type of writer? ** GeoParser uses a single hash table to map qualified names to the GeoParser that is to deal with tha...'

== Writing XML documents with Marble ==

* How to set the type of writer?
** GeoParser uses a single hash table to map qualified names to the GeoParser that is to deal with that tag.
** This will have to be dealt with differently in the GeoDataWriter because we will have to be able to deal with the one to many mapping. ( i.e. one GeoData format will be exportable to many different types of XML and we will need to choose the GeoTagWriter based on the desired XML output.

Projects/Marble

2009-08-03T10:44:23Z

Mansona:

Projects/Marble/ModelView

2009-07-28T09:20:55Z

Mansona: Filling in the status on the GpxFileModel

== ModelView framework in Marble ==

Marble uses Qt's Model/View framework as a way to signal updates to a model to interested parts. In that respect, a Model class can wrap any possible data.

Here is the list of Model class, and a description of how they are used.

=== QAbstractItemModel ===
* {{class|GeoDataDebugModel|kdeedu}}
It represents a data file, parsed into a {{class|GeoDataDocument|kdeedu}} tree structure.

It is used by the {{class|DataViewPlugin|kdeedu}} debug plugin (and is broken atm)

* {{class|GpxFileModel|kdeedu|4.x}}
It represents a list of gpx data file represented as {{class|GpxFile|kdeedu|4.x}}

This was originally intended to but used as the model for the File List View ( which is accessible by running marble with --enableFileView ) but has since been replaced by another, more centralised, File Model. This new File Model is located in {{class|PlacemarkManager|kdeedu|4.x}}.
The model that is in the GpsLayer is currently only being used as a collection class and is deprecated. This, along with the whole current GPX implementation, needs to be removed and updated to the current concepts in Marble. See [[Projects/Marble/GPXStatus|Gpx Status]]

* {{class|MarbleGeometryModel|kdeedu}}
It represents the {{class|GeoDataGeometry|kdeedu}} and the {{class|GeoDataFeature|kdeedu}} items of the {{class|GeoDataDocument|kdeedu}} which contains all Placemarks.

It is used by the {{class|GeoRenderPlugin|kdeedu}} to access the list of placemarks.

=== QAbstractListModel ===
* {{class|FileViewModel|kdeedu}}
It represents the list of files opened. The {{class|PlacemarkManager|kdeedu}} appends the documents it opens, and the {{class|MarbleWidget|kdeedu}} appends the gpx files it opens.

It is used by the {{class|FileViewFloatItem|kdeedu}} and manipulated by the {{class|PlaceMarkManager|kdeedu}} and the {{class|MarbleModel|kdeedu}}.

* {{class|MarbleGeoDataModel|kdeedu}}
It represents a list of {{class|GeoDataDocuments|kdeedu}}. Only the {{class|PlacemarksPlugin|kdeedu}} uses it

It is used by no other code.

* {{class|MarblePlacemarkModel|kdeedu}}
It represents

It is used by

Projects/Marble/GPXStatus

2009-07-28T08:57:39Z

Mansona: Created page with '==Gpx Status== This page is intended to be a reference as to what needs to be done to update the current GPX implementation in Marble. *Remove the Abstract Layer *Make GPX lo...'

==Gpx Status==
This page is intended to be a reference as to what needs to be done to update the current GPX implementation in Marble.

*Remove the Abstract Layer
*Make GPX loading and rendering a plugin
*Uncouple the current GPS location rendering from the GPS Layer

Development/Doxygen

2009-07-17T12:37:56Z

Mansona: Redirected page to Development/Tutorials/API Documentation

#REDIRECT [[Development/Tutorials/API_Documentation]]

Development/Comments

2009-07-17T12:36:12Z

Mansona: Redirected page to Development/Tutorials/API Documentation

#REDIRECT [[Development/Tutorials/API_Documentation]]

Reviewboard

2009-07-16T10:09:46Z

Mansona:

== KDE Review Board ==

Located at http://reviewboard.kde.org/ the review board is....

=== Creating Groups ===
To create a group on the KDE Review Board you need to file a system admin request. This is done with the [https://bugs.kde.org/enter_sysadmin_request.cgi this web form ]

Reviewboard

2009-07-16T09:45:44Z

Mansona: Created page with '== KDE Review Board == Located at http://reviewboard.kde.org/ the review board is.... === Creating Groups === To create a group on the KDE Review Board ....'

== KDE Review Board ==

Located at http://reviewboard.kde.org/ the review board is....

=== Creating Groups ===
To create a group on the KDE Review Board ....

Projects/Marble/GraphicsViewGeoParser

2009-07-09T14:01:56Z

Mansona: Created page with '== GeoParser and the GeoGraphicsView == The current GeoData XML Parser ( aka. GeoParser ) has been implemented to specifically deal with our current GeoData data structure. If y...'

== GeoParser and the GeoGraphicsView ==
The current GeoData XML Parser ( aka. GeoParser ) has been implemented to specifically deal with our current GeoData data structure. If you want to see a more complete documentation of the GeoData library you can see the [[Projects/Marble/LibGeoData|GeoData Library documentation]]. I will only describe the particular problem to the GeoGraphicsView implementation here.


=== Parsing GeoData ===
The GeoParser is an implementation of the QXMLStreamReader class in Qt, more information can be found [http://doc.qtsoftware.com/4.5/qtxml.html here]. There are other things built into this implementation that simplify the creation of a parser for new XML format document, namely:
* The Concept of a TagHandler class that deals with only one tag
* A Stack Item class that implements the Structural parts of the XML document
* The collection class where the results of the XML parsing will be placed
* A element dictionary that prevents the need for string comparison everywere

To implement a new XML parser you need to
#compile an element dictionary of all of the available tags in the namespace
#implement a tag handler for each of these elements
#register that tag handler with the GeoParser

==== Implementing a tag handler ====
Each tag handler is called when the relevant XML tag is reached by the GeoParser ( which knows what tags to call by its registered tag list ). Each tag can access the stack data structure of the GeoParser as well as the Collection Data Structure of the GeoParser. This allows the tag handler to access items from the stack and allows root elements of the XML to add themselves to the collection data structure.


=== Down Casting ===
The unfortunate thing about the current implementation of the GeoParser is that when any item is added to the Collection Data Structure it is effectively downcast to the collection's type and removes any ability for 3rd party developers to add parsing capability to marble with functionality other than that which marble provides. This is not in line with the design of the QGraphicsItem implementation and something that is a current development effort to fix. What needs to happen is that an extra data model needs to be added to the GeoParser that is more in line with the idea of passing pointers around and that way we can conserve the typing information at run time.

Projects/Marble

2009-07-09T13:16:09Z

Mansona:

{{Template:I18n/Language Navigation Bar|Projects/Marble}}

__NOTOC__
[[Image:Marble_logo.png]]

== About Marble ==
;[[/FAQ|Marble FAQ]]

== Examples of Use ==
;[[/MarbleUsedBy|Applications using the Marble library]]

== Using the Marble Widget in other applications ==
;[[/MarbleDesigner|with QtDesigner]]
;[[/MarbleCPlusPlus|with C++]]
;[[/MarblePython|with Python]]

;[[/MarbleDBus|via a shell script]]

== How to become a Marble developer ("Marblehead") ==

=== So you are new to Marble development ... ===

Welcome!

Here you'll get all the information you need to start Marble development:

;[[/GoMarble|How to become a Marble Developer]]

== Packaging Marble ==

Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.

===General===

===Linux===

===Mac OS X===

==== Qt-Only ====

Configure Marble with:
<pre>
cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../marble
</pre>

To generate a Diskimage (.dmg) one can use this script (based on parts by Tim Sutton, thanks!):

<code bash>
VERSION=0.7.1
APPNAME=Marble

VOLNAME=${APPNAME}-${VERSION}
DMGNAME=${VOLNAME}Uncompressed.dmg
COMPRESSEDDMGNAME=${VOLNAME}.dmg

function deploy_file() {
for n in $(otool -L $1 | grep Qt); do
path=`echo $n | grep Qt`
if [ $path ] ; then
name=$(basename $path)
FRAMEWORKS="$FRAMEWORKS $name"
fi
done

for framework in $FRAMEWORKS ; do
install_name_tool -change \
$framework.framework/Versions/4/$framework \
@executable_path/../Frameworks/$framework.framework/Versions/4/$framework \
$1
done
}

function deploy_plugins() {
for plugin in $1/Contents/Resources/plugins/*; do
deploy_file $plugin
done
}

function set_bundle_display_options() {
osascript <<-EOF
tell application "Finder"
set f to POSIX file ("${1}" as string) as alias
tell folder f
open
tell container window
set toolbar visible to false
set statusbar visible to false
set current view to icon view
delay 1 -- sync
set the bounds to {20, 50, 300, 400}
end tell
delay 1 -- sync
set icon size of the icon view options of container window to 64
set arrangement of the icon view options of container window to not arranged
set position of item "Marble.app" to {100,150}
set position of item "Applications" to {280, 150}
set background picture of the icon view options of container window to file "background.png" of folder "Pictures"
set the bounds of the container window to {0, 0, 300, 400}
update without registering applications
delay 5 -- sync
close
end tell
delay 5 -- sync
end tell
EOF

}

function create_symlinks() {
cd "$1/Contents/Resources"
ln -s "../MacOS/resources/data/" "data"
ln -s "../MacOS/resources/plugins/" "plugins"
cd -
}

rm ~/Desktop/${DMGNAME}
rm ~/Desktop/${COMPRESSEDDMGNAME}
hdiutil create -size 150m -fs HFS+ -volname ${VOLNAME} ~/Desktop/${DMGNAME}

# Mount the disk image
hdiutil attach ~/Desktop/${DMGNAME}

# Obtain device information
DEVS=$(hdiutil attach ~/Desktop/${DMGNAME} | cut -f 1)
DEV=$(echo $DEVS | cut -f 1 -d ' ')
VOLUME=$(mount |grep ${DEV} | cut -f 3 -d ' ')

# copy in the application bundle
cp -Rp /Applications/${APPNAME}.app ${VOLUME}/${APPNAME}.app

# fix the libs
macdeployqt ${VOLUME}/${APPNAME}.app
create_symlinks ${VOLUME}/${APPNAME}.app
deploy_file "${VOLUME}/${APPNAME}.app/Contents/MacOS/lib/libmarblewidget.7.dylib"
deploy_plugins ${VOLUME}/${APPNAME}.app

# copy in background image
mkdir -p ${VOLUME}/Pictures
# fixme: path
cp ~/Desktop/marble-dmg-background.png ${VOLUME}/Pictures/background.png
# symlink applications
ln -s /Applications/ ${VOLUME}/Applications
set_bundle_display_options ${VOLUME}
mv ${VOLUME}/Pictures ${VOLUME}/.Pictures

# Unmount the disk image
hdiutil detach $DEV

# Convert the disk image to read-only
hdiutil convert ~/Desktop/${DMGNAME} -format UDBZ -o ~/Desktop/${COMPRESSEDDMGNAME}
</code>

It uses the macdeployqt tool which copies Qt and its plugins into the App Bundle.
macdeployqt also tells the main application to link against the libs contained in the bundle, instead of the system libs.
This does not happen to the libmarblewidget and the Marble plugins, so it has to be done by the script.
The script also sets a background Image for the dmg. (Place it at ~/Desktop/marble-dmg-background.png or change the path in the script)

After that you should have Marble-version.dmg on you Desktop.

===Windows===

== Programming Coordination ==

Here are a few links to various issues we are working on:

=== User Interface ===
;[[/Mockups|Mockups]]

=== Texture Mapping ===
;[[/TextureNG|Texture Mapping]]

=== GeoData Library / KML ===
;[[/LibGeoData|GeoData Library]]
;[[/KMLStatus|KML Status]]
;[[/GPXStatus|GPX Status]]

=== Geo Graphics View ===
;[[/GeoGraphicsViewOverview|Overview of the plans for GeoGraphicsView]]
;[[/GraphicsViewGeoParser| Developing the GeoParser to work with GeoGraphicsView]]

=== GeoPainter / DGML ===
;[[/GeoPainter|GeoPainter]]
;[[/Dgml|DGML]]

=== Marble Runner ===
;[[/CoordinateRunner|Coordinate Runner]]
;[[/OsmNameFinderRunner|OSM Runner]]
;[[/RunnerHOWTO|Runner HOWTO]]

=== Projections ===
;[[/WinkelIii|Winkel III]]

=== Tile Download ===
;[[/TileDownload|Tile Download]]

=== Documentation ===
;[[/ApiDocs|API Docs]]
;[[/CustomMaps|How to customize maps]]
;[[/MarblesSecrets|Marble's Secrets]]
;[[/ProxyConnection|How to use the Proxy]]

=== GeoClue / GPS ===
;[[/GeoClue|GeoClue support in Marble]]

== Mapping Coordination ==
=== Documentation ===
;[[/HistoricalMaps|How to create Historical Maps]]

;[[/PalaeoMaps|Global Palaeogeography]]

== Routing ==
;[[/RoutingIdeas|General ideas about routing]]

== valgrind logs ==
;[[/ValgrindLogs|if you want to fix memory leaks, valgrind logs can be found here]]

== Meetings ==
Summaries and logs of scheduled Marble meetings can be found on the following pages:
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]]

Projects/Marble

2009-07-09T13:15:32Z

Mansona:

{{Template:I18n/Language Navigation Bar|Projects/Marble}}

__NOTOC__
[[Image:Marble_logo.png]]

== About Marble ==
;[[/FAQ|Marble FAQ]]

== Examples of Use ==
;[[/MarbleUsedBy|Applications using the Marble library]]

== Using the Marble Widget in other applications ==
;[[/MarbleDesigner|with QtDesigner]]
;[[/MarbleCPlusPlus|with C++]]
;[[/MarblePython|with Python]]

;[[/MarbleDBus|via a shell script]]

== How to become a Marble developer ("Marblehead") ==

=== So you are new to Marble development ... ===

Welcome!

Here you'll get all the information you need to start Marble development:

;[[/GoMarble|How to become a Marble Developer]]

== Packaging Marble ==

Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.

===General===

===Linux===

===Mac OS X===

==== Qt-Only ====

Configure Marble with:
<pre>
cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../marble
</pre>

To generate a Diskimage (.dmg) one can use this script (based on parts by Tim Sutton, thanks!):

<code bash>
VERSION=0.7.1
APPNAME=Marble

VOLNAME=${APPNAME}-${VERSION}
DMGNAME=${VOLNAME}Uncompressed.dmg
COMPRESSEDDMGNAME=${VOLNAME}.dmg

function deploy_file() {
for n in $(otool -L $1 | grep Qt); do
path=`echo $n | grep Qt`
if [ $path ] ; then
name=$(basename $path)
FRAMEWORKS="$FRAMEWORKS $name"
fi
done

for framework in $FRAMEWORKS ; do
install_name_tool -change \
$framework.framework/Versions/4/$framework \
@executable_path/../Frameworks/$framework.framework/Versions/4/$framework \
$1
done
}

function deploy_plugins() {
for plugin in $1/Contents/Resources/plugins/*; do
deploy_file $plugin
done
}

function set_bundle_display_options() {
osascript <<-EOF
tell application "Finder"
set f to POSIX file ("${1}" as string) as alias
tell folder f
open
tell container window
set toolbar visible to false
set statusbar visible to false
set current view to icon view
delay 1 -- sync
set the bounds to {20, 50, 300, 400}
end tell
delay 1 -- sync
set icon size of the icon view options of container window to 64
set arrangement of the icon view options of container window to not arranged
set position of item "Marble.app" to {100,150}
set position of item "Applications" to {280, 150}
set background picture of the icon view options of container window to file "background.png" of folder "Pictures"
set the bounds of the container window to {0, 0, 300, 400}
update without registering applications
delay 5 -- sync
close
end tell
delay 5 -- sync
end tell
EOF

}

function create_symlinks() {
cd "$1/Contents/Resources"
ln -s "../MacOS/resources/data/" "data"
ln -s "../MacOS/resources/plugins/" "plugins"
cd -
}

rm ~/Desktop/${DMGNAME}
rm ~/Desktop/${COMPRESSEDDMGNAME}
hdiutil create -size 150m -fs HFS+ -volname ${VOLNAME} ~/Desktop/${DMGNAME}

# Mount the disk image
hdiutil attach ~/Desktop/${DMGNAME}

# Obtain device information
DEVS=$(hdiutil attach ~/Desktop/${DMGNAME} | cut -f 1)
DEV=$(echo $DEVS | cut -f 1 -d ' ')
VOLUME=$(mount |grep ${DEV} | cut -f 3 -d ' ')

# copy in the application bundle
cp -Rp /Applications/${APPNAME}.app ${VOLUME}/${APPNAME}.app

# fix the libs
macdeployqt ${VOLUME}/${APPNAME}.app
create_symlinks ${VOLUME}/${APPNAME}.app
deploy_file "${VOLUME}/${APPNAME}.app/Contents/MacOS/lib/libmarblewidget.7.dylib"
deploy_plugins ${VOLUME}/${APPNAME}.app

# copy in background image
mkdir -p ${VOLUME}/Pictures
# fixme: path
cp ~/Desktop/marble-dmg-background.png ${VOLUME}/Pictures/background.png
# symlink applications
ln -s /Applications/ ${VOLUME}/Applications
set_bundle_display_options ${VOLUME}
mv ${VOLUME}/Pictures ${VOLUME}/.Pictures

# Unmount the disk image
hdiutil detach $DEV

# Convert the disk image to read-only
hdiutil convert ~/Desktop/${DMGNAME} -format UDBZ -o ~/Desktop/${COMPRESSEDDMGNAME}
</code>

It uses the macdeployqt tool which copies Qt and its plugins into the App Bundle.
macdeployqt also tells the main application to link against the libs contained in the bundle, instead of the system libs.
This does not happen to the libmarblewidget and the Marble plugins, so it has to be done by the script.
The script also sets a background Image for the dmg. (Place it at ~/Desktop/marble-dmg-background.png or change the path in the script)

After that you should have Marble-version.dmg on you Desktop.

===Windows===

== Programming Coordination ==

Here are a few links to various issues we are working on:

=== User Interface ===
;[[/Mockups|Mockups]]

=== Texture Mapping ===
;[[/TextureNG|Texture Mapping]]

=== GeoData Library / KML ===
;[[/LibGeoData|GeoData Library]]
;[[/KMLStatus|KML Status]]
;[[/GPXStatus|GPX Status]]

=== Geo Graphics View ===
[[/GeoGraphicsViewOverview|Overview of the plans for GeoGraphicsView]] ;
[[/GraphicsViewGeoParser| Developing the GeoParser to work with GeoGraphicsView]] ;

=== GeoPainter / DGML ===
;[[/GeoPainter|GeoPainter]]
;[[/Dgml|DGML]]

=== Marble Runner ===
;[[/CoordinateRunner|Coordinate Runner]]
;[[/OsmNameFinderRunner|OSM Runner]]
;[[/RunnerHOWTO|Runner HOWTO]]

=== Projections ===
;[[/WinkelIii|Winkel III]]

=== Tile Download ===
;[[/TileDownload|Tile Download]]

=== Documentation ===
;[[/ApiDocs|API Docs]]
;[[/CustomMaps|How to customize maps]]
;[[/MarblesSecrets|Marble's Secrets]]
;[[/ProxyConnection|How to use the Proxy]]

=== GeoClue / GPS ===
;[[/GeoClue|GeoClue support in Marble]]

== Mapping Coordination ==
=== Documentation ===
;[[/HistoricalMaps|How to create Historical Maps]]

;[[/PalaeoMaps|Global Palaeogeography]]

== Routing ==
;[[/RoutingIdeas|General ideas about routing]]

== valgrind logs ==
;[[/ValgrindLogs|if you want to fix memory leaks, valgrind logs can be found here]]

== Meetings ==
Summaries and logs of scheduled Marble meetings can be found on the following pages:
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]]

Projects/Marble

2009-07-09T13:14:29Z

Mansona:

{{Template:I18n/Language Navigation Bar|Projects/Marble}}

__NOTOC__
[[Image:Marble_logo.png]]

== About Marble ==
;[[/FAQ|Marble FAQ]]

== Examples of Use ==
;[[/MarbleUsedBy|Applications using the Marble library]]

== Using the Marble Widget in other applications ==
;[[/MarbleDesigner|with QtDesigner]]
;[[/MarbleCPlusPlus|with C++]]
;[[/MarblePython|with Python]]

;[[/MarbleDBus|via a shell script]]

== How to become a Marble developer ("Marblehead") ==

=== So you are new to Marble development ... ===

Welcome!

Here you'll get all the information you need to start Marble development:

;[[/GoMarble|How to become a Marble Developer]]

== Packaging Marble ==

Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.

===General===

===Linux===

===Mac OS X===

==== Qt-Only ====

Configure Marble with:
<pre>
cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../marble
</pre>

To generate a Diskimage (.dmg) one can use this script (based on parts by Tim Sutton, thanks!):

<code bash>
VERSION=0.7.1
APPNAME=Marble

VOLNAME=${APPNAME}-${VERSION}
DMGNAME=${VOLNAME}Uncompressed.dmg
COMPRESSEDDMGNAME=${VOLNAME}.dmg

function deploy_file() {
for n in $(otool -L $1 | grep Qt); do
path=`echo $n | grep Qt`
if [ $path ] ; then
name=$(basename $path)
FRAMEWORKS="$FRAMEWORKS $name"
fi
done

for framework in $FRAMEWORKS ; do
install_name_tool -change \
$framework.framework/Versions/4/$framework \
@executable_path/../Frameworks/$framework.framework/Versions/4/$framework \
$1
done
}

function deploy_plugins() {
for plugin in $1/Contents/Resources/plugins/*; do
deploy_file $plugin
done
}

function set_bundle_display_options() {
osascript <<-EOF
tell application "Finder"
set f to POSIX file ("${1}" as string) as alias
tell folder f
open
tell container window
set toolbar visible to false
set statusbar visible to false
set current view to icon view
delay 1 -- sync
set the bounds to {20, 50, 300, 400}
end tell
delay 1 -- sync
set icon size of the icon view options of container window to 64
set arrangement of the icon view options of container window to not arranged
set position of item "Marble.app" to {100,150}
set position of item "Applications" to {280, 150}
set background picture of the icon view options of container window to file "background.png" of folder "Pictures"
set the bounds of the container window to {0, 0, 300, 400}
update without registering applications
delay 5 -- sync
close
end tell
delay 5 -- sync
end tell
EOF

}

function create_symlinks() {
cd "$1/Contents/Resources"
ln -s "../MacOS/resources/data/" "data"
ln -s "../MacOS/resources/plugins/" "plugins"
cd -
}

rm ~/Desktop/${DMGNAME}
rm ~/Desktop/${COMPRESSEDDMGNAME}
hdiutil create -size 150m -fs HFS+ -volname ${VOLNAME} ~/Desktop/${DMGNAME}

# Mount the disk image
hdiutil attach ~/Desktop/${DMGNAME}

# Obtain device information
DEVS=$(hdiutil attach ~/Desktop/${DMGNAME} | cut -f 1)
DEV=$(echo $DEVS | cut -f 1 -d ' ')
VOLUME=$(mount |grep ${DEV} | cut -f 3 -d ' ')

# copy in the application bundle
cp -Rp /Applications/${APPNAME}.app ${VOLUME}/${APPNAME}.app

# fix the libs
macdeployqt ${VOLUME}/${APPNAME}.app
create_symlinks ${VOLUME}/${APPNAME}.app
deploy_file "${VOLUME}/${APPNAME}.app/Contents/MacOS/lib/libmarblewidget.7.dylib"
deploy_plugins ${VOLUME}/${APPNAME}.app

# copy in background image
mkdir -p ${VOLUME}/Pictures
# fixme: path
cp ~/Desktop/marble-dmg-background.png ${VOLUME}/Pictures/background.png
# symlink applications
ln -s /Applications/ ${VOLUME}/Applications
set_bundle_display_options ${VOLUME}
mv ${VOLUME}/Pictures ${VOLUME}/.Pictures

# Unmount the disk image
hdiutil detach $DEV

# Convert the disk image to read-only
hdiutil convert ~/Desktop/${DMGNAME} -format UDBZ -o ~/Desktop/${COMPRESSEDDMGNAME}
</code>

It uses the macdeployqt tool which copies Qt and its plugins into the App Bundle.
macdeployqt also tells the main application to link against the libs contained in the bundle, instead of the system libs.
This does not happen to the libmarblewidget and the Marble plugins, so it has to be done by the script.
The script also sets a background Image for the dmg. (Place it at ~/Desktop/marble-dmg-background.png or change the path in the script)

After that you should have Marble-version.dmg on you Desktop.

===Windows===

== Programming Coordination ==

Here are a few links to various issues we are working on:

=== User Interface ===
;[[/Mockups|Mockups]]

=== Texture Mapping ===
;[[/TextureNG|Texture Mapping]]

=== GeoData Library / KML ===
;[[/LibGeoData|GeoData Library]]
;[[/KMLStatus|KML Status]]
;[[/GPXStatus|GPX Status]]

=== Geo Graphics View ===
[[/GeoGraphicsViewOverview|Overview of the plans for GeoGraphicsView]]
[[/GraphicsViewGeoParser| Developing the GeoParser to work with GeoGraphicsView]]

=== GeoPainter / DGML ===
;[[/GeoPainter|GeoPainter]]
;[[/Dgml|DGML]]

=== Marble Runner ===
;[[/CoordinateRunner|Coordinate Runner]]
;[[/OsmNameFinderRunner|OSM Runner]]
;[[/RunnerHOWTO|Runner HOWTO]]

=== Projections ===
;[[/WinkelIii|Winkel III]]

=== Tile Download ===
;[[/TileDownload|Tile Download]]

=== Documentation ===
;[[/ApiDocs|API Docs]]
;[[/CustomMaps|How to customize maps]]
;[[/MarblesSecrets|Marble's Secrets]]
;[[/ProxyConnection|How to use the Proxy]]

=== GeoClue / GPS ===
;[[/GeoClue|GeoClue support in Marble]]

== Mapping Coordination ==
=== Documentation ===
;[[/HistoricalMaps|How to create Historical Maps]]

;[[/PalaeoMaps|Global Palaeogeography]]

== Routing ==
;[[/RoutingIdeas|General ideas about routing]]

== valgrind logs ==
;[[/ValgrindLogs|if you want to fix memory leaks, valgrind logs can be found here]]

== Meetings ==
Summaries and logs of scheduled Marble meetings can be found on the following pages:
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]]

Projects/Marble

2009-07-09T10:50:47Z

Mansona:

{{Template:I18n/Language Navigation Bar|Projects/Marble}}

__NOTOC__
[[Image:Marble_logo.png]]

== About Marble ==
;[[/FAQ|Marble FAQ]]

== Examples of Use ==
;[[/MarbleUsedBy|Applications using the Marble library]]

== Using the Marble Widget in other applications ==
;[[/MarbleDesigner|with QtDesigner]]
;[[/MarbleCPlusPlus|with C++]]
;[[/MarblePython|with Python]]

;[[/MarbleDBus|via a shell script]]

== How to become a Marble developer ("Marblehead") ==

=== So you are new to Marble development ... ===

Welcome!

Here you'll get all the information you need to start Marble development:

;[[/GoMarble|How to become a Marble Developer]]

== Packaging Marble ==

Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.

===General===

===Linux===

===Mac OS X===

==== Qt-Only ====

Configure Marble with:
<pre>
cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../marble
</pre>

To generate a Diskimage (.dmg) one can use this script (based on parts by Tim Sutton, thanks!):

<code bash>
VERSION=0.7.1
APPNAME=Marble

VOLNAME=${APPNAME}-${VERSION}
DMGNAME=${VOLNAME}Uncompressed.dmg
COMPRESSEDDMGNAME=${VOLNAME}.dmg

function deploy_file() {
for n in $(otool -L $1 | grep Qt); do
path=`echo $n | grep Qt`
if [ $path ] ; then
name=$(basename $path)
FRAMEWORKS="$FRAMEWORKS $name"
fi
done

for framework in $FRAMEWORKS ; do
install_name_tool -change \
$framework.framework/Versions/4/$framework \
@executable_path/../Frameworks/$framework.framework/Versions/4/$framework \
$1
done
}

function deploy_plugins() {
for plugin in $1/Contents/Resources/plugins/*; do
deploy_file $plugin
done
}

function set_bundle_display_options() {
osascript <<-EOF
tell application "Finder"
set f to POSIX file ("${1}" as string) as alias
tell folder f
open
tell container window
set toolbar visible to false
set statusbar visible to false
set current view to icon view
delay 1 -- sync
set the bounds to {20, 50, 300, 400}
end tell
delay 1 -- sync
set icon size of the icon view options of container window to 64
set arrangement of the icon view options of container window to not arranged
set position of item "Marble.app" to {100,150}
set position of item "Applications" to {280, 150}
set background picture of the icon view options of container window to file "background.png" of folder "Pictures"
set the bounds of the container window to {0, 0, 300, 400}
update without registering applications
delay 5 -- sync
close
end tell
delay 5 -- sync
end tell
EOF

}

function create_symlinks() {
cd "$1/Contents/Resources"
ln -s "../MacOS/resources/data/" "data"
ln -s "../MacOS/resources/plugins/" "plugins"
cd -
}

rm ~/Desktop/${DMGNAME}
rm ~/Desktop/${COMPRESSEDDMGNAME}
hdiutil create -size 150m -fs HFS+ -volname ${VOLNAME} ~/Desktop/${DMGNAME}

# Mount the disk image
hdiutil attach ~/Desktop/${DMGNAME}

# Obtain device information
DEVS=$(hdiutil attach ~/Desktop/${DMGNAME} | cut -f 1)
DEV=$(echo $DEVS | cut -f 1 -d ' ')
VOLUME=$(mount |grep ${DEV} | cut -f 3 -d ' ')

# copy in the application bundle
cp -Rp /Applications/${APPNAME}.app ${VOLUME}/${APPNAME}.app

# fix the libs
macdeployqt ${VOLUME}/${APPNAME}.app
create_symlinks ${VOLUME}/${APPNAME}.app
deploy_file "${VOLUME}/${APPNAME}.app/Contents/MacOS/lib/libmarblewidget.7.dylib"
deploy_plugins ${VOLUME}/${APPNAME}.app

# copy in background image
mkdir -p ${VOLUME}/Pictures
# fixme: path
cp ~/Desktop/marble-dmg-background.png ${VOLUME}/Pictures/background.png
# symlink applications
ln -s /Applications/ ${VOLUME}/Applications
set_bundle_display_options ${VOLUME}
mv ${VOLUME}/Pictures ${VOLUME}/.Pictures

# Unmount the disk image
hdiutil detach $DEV

# Convert the disk image to read-only
hdiutil convert ~/Desktop/${DMGNAME} -format UDBZ -o ~/Desktop/${COMPRESSEDDMGNAME}
</code>

It uses the macdeployqt tool which copies Qt and its plugins into the App Bundle.
macdeployqt also tells the main application to link against the libs contained in the bundle, instead of the system libs.
This does not happen to the libmarblewidget and the Marble plugins, so it has to be done by the script.
The script also sets a background Image for the dmg. (Place it at ~/Desktop/marble-dmg-background.png or change the path in the script)

After that you should have Marble-version.dmg on you Desktop.

===Windows===

== Programming Coordination ==

Here are a few links to various issues we are working on:

=== User Interface ===
;[[/Mockups|Mockups]]

=== Texture Mapping ===
;[[/TextureNG|Texture Mapping]]

=== GeoData Library / KML ===
;[[/LibGeoData|GeoData Library]]
;[[/KMLStatus|KML Status]]
;[[/GPXStatus|GPX Status]]

=== Geo Graphics View ===
[[/GeoGraphicsViewOverview|Overview of the plans for GeoGraphicsView]]

=== GeoPainter / DGML ===
;[[/GeoPainter|GeoPainter]]
;[[/Dgml|DGML]]

=== Marble Runner ===
;[[/CoordinateRunner|Coordinate Runner]]
;[[/OsmNameFinderRunner|OSM Runner]]
;[[/RunnerHOWTO|Runner HOWTO]]

=== Projections ===
;[[/WinkelIii|Winkel III]]

=== Tile Download ===
;[[/TileDownload|Tile Download]]

=== Documentation ===
;[[/ApiDocs|API Docs]]
;[[/CustomMaps|How to customize maps]]
;[[/MarblesSecrets|Marble's Secrets]]
;[[/ProxyConnection|How to use the Proxy]]

=== GeoClue / GPS ===
;[[/GeoClue|GeoClue support in Marble]]

== Mapping Coordination ==
=== Documentation ===
;[[/HistoricalMaps|How to create Historical Maps]]

;[[/PalaeoMaps|Global Palaeogeography]]

== Routing ==
;[[/RoutingIdeas|General ideas about routing]]

== valgrind logs ==
;[[/ValgrindLogs|if you want to fix memory leaks, valgrind logs can be found here]]

== Meetings ==
Summaries and logs of scheduled Marble meetings can be found on the following pages:
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]]

Projects/Marble/GeoGraphicsViewOverview

2009-07-09T10:31:05Z

Mansona: moved GeoGraphicsViewOverview to Projects/Marble/GeoGraphicsViewOverview: Make it a sub item of Marble

== GeoGraphicsView Overview ==

We are currently working on an implementation of a GeoGraphicsView system, which is intended to be very closely modeled on the QGraphicsView classes. We have to work on this as an internal project due to the current limitations that are in the QGraphicsView classes that do not allow for the implementation of projections directly. There is talk about these problems being fixed for Qt 4.6 and so it is important to model our API for this system on the current Qt classes so that we can convert the system painlessly when Qt 4.6 is released.

=== Benefits of QGrahpicsView for marble ===

Some of the main benefits that we would like to take advantage of from the QGraphicsView classes are:
* Simplified input event model
* QGraphicsItems "know" how to draw themselves

The QGraphicsView input model integrates the passing of mouse events based on the position of the mouse event, passing mouse events down through a stack of items and the ability to have a standard implementation of Drag and Drop.

If you are not familiar with the system check out the [http://doc.qtsoftware.com/4.5/graphicsview.html Qt Documentation]

Also a problem with the current way things are done in marble is that we have adopted a QVariant style Typing system for the GeoData classes. This is very effective ( and very fast ) for the current implementation of marble but does not allow for extension of the system by 3rd party developers for things like plugins. If we adopt the QGraphicsItem system then we will be passing pointers to objects around which will adhere to the C++ Run-Time Typing System and will not loose any Class/Inheritance information when passed around the Marble system ( e.g. passing from the Geo Parser to the model ).

Projects/Marble/GeoGraphicsViewOverview

2009-07-09T10:27:07Z

Mansona: Created page with '== GeoGraphicsView Overview == We are currently working on an implementation of a GeoGraphicsView system, which is intended to be very closely modeled on the QGraphicsView class...'

Projects/Marble

2009-07-09T10:00:58Z

Mansona:

{{Template:I18n/Language Navigation Bar|Projects/Marble}}

__NOTOC__
[[Image:Marble_logo.png]]

== About Marble ==
;[[/FAQ|Marble FAQ]]

== Examples of Use ==
;[[/MarbleUsedBy|Applications using the Marble library]]

== Using the Marble Widget in other applications ==
;[[/MarbleDesigner|with QtDesigner]]
;[[/MarbleCPlusPlus|with C++]]
;[[/MarblePython|with Python]]

;[[/MarbleDBus|via a shell script]]

== How to become a Marble developer ("Marblehead") ==

=== So you are new to Marble development ... ===

Welcome!

Here you'll get all the information you need to start Marble development:

;[[/GoMarble|How to become a Marble Developer]]

== Packaging Marble ==

Here is some advice about how packaging is supposed to happen on the various plattforms that are supported.

===General===

===Linux===

===Mac OS X===

==== Qt-Only ====

Configure Marble with:
<pre>
cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../marble
</pre>

To generate a Diskimage (.dmg) one can use this script (based on parts by Tim Sutton, thanks!):

<code bash>
VERSION=0.7.1
APPNAME=Marble

VOLNAME=${APPNAME}-${VERSION}
DMGNAME=${VOLNAME}Uncompressed.dmg
COMPRESSEDDMGNAME=${VOLNAME}.dmg

function deploy_file() {
for n in $(otool -L $1 | grep Qt); do
path=`echo $n | grep Qt`
if [ $path ] ; then
name=$(basename $path)
FRAMEWORKS="$FRAMEWORKS $name"
fi
done

for framework in $FRAMEWORKS ; do
install_name_tool -change \
$framework.framework/Versions/4/$framework \
@executable_path/../Frameworks/$framework.framework/Versions/4/$framework \
$1
done
}

function deploy_plugins() {
for plugin in $1/Contents/Resources/plugins/*; do
deploy_file $plugin
done
}

function set_bundle_display_options() {
osascript <<-EOF
tell application "Finder"
set f to POSIX file ("${1}" as string) as alias
tell folder f
open
tell container window
set toolbar visible to false
set statusbar visible to false
set current view to icon view
delay 1 -- sync
set the bounds to {20, 50, 300, 400}
end tell
delay 1 -- sync
set icon size of the icon view options of container window to 64
set arrangement of the icon view options of container window to not arranged
set position of item "Marble.app" to {100,150}
set position of item "Applications" to {280, 150}
set background picture of the icon view options of container window to file "background.png" of folder "Pictures"
set the bounds of the container window to {0, 0, 300, 400}
update without registering applications
delay 5 -- sync
close
end tell
delay 5 -- sync
end tell
EOF

}

function create_symlinks() {
cd "$1/Contents/Resources"
ln -s "../MacOS/resources/data/" "data"
ln -s "../MacOS/resources/plugins/" "plugins"
cd -
}

rm ~/Desktop/${DMGNAME}
rm ~/Desktop/${COMPRESSEDDMGNAME}
hdiutil create -size 150m -fs HFS+ -volname ${VOLNAME} ~/Desktop/${DMGNAME}

# Mount the disk image
hdiutil attach ~/Desktop/${DMGNAME}

# Obtain device information
DEVS=$(hdiutil attach ~/Desktop/${DMGNAME} | cut -f 1)
DEV=$(echo $DEVS | cut -f 1 -d ' ')
VOLUME=$(mount |grep ${DEV} | cut -f 3 -d ' ')

# copy in the application bundle
cp -Rp /Applications/${APPNAME}.app ${VOLUME}/${APPNAME}.app

# fix the libs
macdeployqt ${VOLUME}/${APPNAME}.app
create_symlinks ${VOLUME}/${APPNAME}.app
deploy_file "${VOLUME}/${APPNAME}.app/Contents/MacOS/lib/libmarblewidget.7.dylib"
deploy_plugins ${VOLUME}/${APPNAME}.app

# copy in background image
mkdir -p ${VOLUME}/Pictures
# fixme: path
cp ~/Desktop/marble-dmg-background.png ${VOLUME}/Pictures/background.png
# symlink applications
ln -s /Applications/ ${VOLUME}/Applications
set_bundle_display_options ${VOLUME}
mv ${VOLUME}/Pictures ${VOLUME}/.Pictures

# Unmount the disk image
hdiutil detach $DEV

# Convert the disk image to read-only
hdiutil convert ~/Desktop/${DMGNAME} -format UDBZ -o ~/Desktop/${COMPRESSEDDMGNAME}
</code>

It uses the macdeployqt tool which copies Qt and its plugins into the App Bundle.
macdeployqt also tells the main application to link against the libs contained in the bundle, instead of the system libs.
This does not happen to the libmarblewidget and the Marble plugins, so it has to be done by the script.
The script also sets a background Image for the dmg. (Place it at ~/Desktop/marble-dmg-background.png or change the path in the script)

After that you should have Marble-version.dmg on you Desktop.

===Windows===

== Programming Coordination ==

Here are a few links to various issues we are working on:

=== User Interface ===
;[[/Mockups|Mockups]]

=== Texture Mapping ===
;[[/TextureNG|Texture Mapping]]

=== GeoData Library / KML ===
;[[/LibGeoData|GeoData Library]]
;[[/KMLStatus|KML Status]]
;[[/GPXStatus|GPX Status]]

=== Geo Graphics View ===
[[GeoGraphicsViewOverview|Overview of the plans for GeoGraphicsView]]

=== GeoPainter / DGML ===
;[[/GeoPainter|GeoPainter]]
;[[/Dgml|DGML]]

=== Marble Runner ===
;[[/CoordinateRunner|Coordinate Runner]]
;[[/OsmNameFinderRunner|OSM Runner]]
;[[/RunnerHOWTO|Runner HOWTO]]

=== Projections ===
;[[/WinkelIii|Winkel III]]

=== Tile Download ===
;[[/TileDownload|Tile Download]]

=== Documentation ===
;[[/ApiDocs|API Docs]]
;[[/CustomMaps|How to customize maps]]
;[[/MarblesSecrets|Marble's Secrets]]
;[[/ProxyConnection|How to use the Proxy]]

=== GeoClue / GPS ===
;[[/GeoClue|GeoClue support in Marble]]

== Mapping Coordination ==
=== Documentation ===
;[[/HistoricalMaps|How to create Historical Maps]]

;[[/PalaeoMaps|Global Palaeogeography]]

== Routing ==
;[[/RoutingIdeas|General ideas about routing]]

== valgrind logs ==
;[[/ValgrindLogs|if you want to fix memory leaks, valgrind logs can be found here]]

== Meetings ==
Summaries and logs of scheduled Marble meetings can be found on the following pages:
;[[/MarbleMeeting20081029|Wednesday Nov. 10th, 2008]]

User:Mansona

2009-04-23T16:22:17Z

Mansona: Created page with 'Hi! Not really very much to add right now, i just wanted to make this page so that i could tell you all a little bit more about myself. I will put more info in later. First t...'

Hi!

Not really very much to add right now, i just wanted to make this page so that i could tell you all a little bit more about myself. I will put more info in later.

First thing i need to say is that I'm a man of many names. Not too many so that its just stupid but enough to be confusing! The two user names that i use are real_ate and mansona, sorry if this confuses anyone.

My blog is here http://realate.blogspot.com/ and if anyone wants to follow me on twitter you can go to http://twitter.com/real_ate .

My normal hang-outs are on #kde-edu and sometimes i go onto #kde-devel, if you want to pm me on freenode my username is real_ate

Talk:Projects/Summer of Code/2009/Projects

2009-04-23T16:15:16Z

Mansona: Created page with 'Hi guys, I'm wondering if we should put a direct link to our external pages in the project list. I'm just going by what the 2007 people have done and they have a link to a wiki p...'

Hi guys, I'm wondering if we should put a direct link to our external pages in the project list. I'm just going by what the 2007 people have done and they have a link to a wiki page about their project and external links as a part of that page. Take a look at my page [[Projects/Summer_of_Code/2009/Projects/OSM_Annotation_Marble]] [[User:Mansona|Mansona]] 16:15, 23 April 2009 (UTC)

Projects/Summer of Code/2009/Projects/OSM Annotation Marble

2009-04-23T16:10:48Z

Mansona: Created page with '==OSM Annotation for Marble Desktop Globe with an Optimised interface for smaller screens== This page will get populated with more information about my project as it starts to u...'

==OSM Annotation for Marble Desktop Globe with an Optimised interface for smaller screens==

This page will get populated with more information about my project as it starts to unfold. Add this page to your watch list by using the tab at the top right of the page if you're interested in the project.

More information about the project is available to anyone who is interested [http://realate.blogspot.com/2009/04/accepted-google-summer-of-code-proposal.html Here on my blog] where i have made my application public. If you want to comment on the idea or the design you can leave me a comment on the blog post or if you would like to email me you can get to me on the marble mailing list as well as the kde-soc mailing list.

Projects/Summer of Code/2009/Projects

2009-04-23T16:01:23Z

Mansona:

The projects for 2009 have been selected! Congratulations to all our students who will be working on KDE for the Summer of Code.

The table below reflects the selected projects as seen on [http://socghop.appspot.com/org/home/google/gsoc2009/kde Google SoC Homepage]:

{| class="wikitable"
|-
!Project
!Student
!Mentor
|-
||[http://www.jacksofscience.com/physics/summer-of-fast-fluid-and-gas-simulation/ Fast Water and Gas Simulation in Step]
|Christopher Ing
|Vladimir Kuznetsov
|-
|[[Projects/Summer_of_Code/2009/Projects/OSM_Annotation_Marble|OSM Annotation for Marble Desktop Globe with an Optimised interface for smaller screens]]
|[[User:mansona|Andrew Manson]]
|Jens-Michael Hoffmann
|-
|Add
|Yourself
|Here!
|}

Projects/Summer of Code/2009/Projects

2009-04-23T16:00:23Z

Mansona:

The projects for 2009 have been selected! Congratulations to all our students who will be working on KDE for the Summer of Code.

The table below reflects the selected projects as seen on [http://socghop.appspot.com/org/home/google/gsoc2009/kde Google SoC Homepage]:

{| class="wikitable"
|-
!Project
!Student
!Mentor
|-
||[http://www.jacksofscience.com/physics/summer-of-fast-fluid-and-gas-simulation/ Fast Water and Gas Simulation in Step]
|Christopher Ing
|Vladimir Kuznetsov
|-
|[[Projects/Summer_of_Code/2009/Projects/OSM_Annotation_Marble|OSM Annotation for Marble Desktop Globe with an Optimised interface for smaller screens]]
|Andrew Manson
|Jens-Michael Hoffmann
|-
|Add
|Yourself
|Here!
|}

Projects/Summer of Code/2009/Projects

2009-04-23T15:57:57Z

Mansona:

The projects for 2009 have been selected! Congratulations to all our students who will be working on KDE for the Summer of Code.

The table below reflects the selected projects as seen on [http://socghop.appspot.com/org/home/google/gsoc2009/kde Google SoC Homepage]:

{| class="wikitable"
|-
!Project
!Student
!Mentor
|-
||[http://www.jacksofscience.com/physics/summer-of-fast-fluid-and-gas-simulation/ Fast Water and Gas Simulation in Step]
|Christopher Ing
|Vladimir Kuznetsov
|-
|OSM Annotation for Marble Desktop Globe with an Optimised interface for smaller screens
|Andrew Manson
|Jens-Michael Hoffmann
|-
|Add
|Yourself
|Here!
|}

Talk:Schedules/KDE4/4.3 Release Schedule

2009-04-17T16:59:45Z

Mansona: Removing all content from page

Talk:Schedules/KDE4/4.3 Release Schedule

2009-04-17T16:39:23Z

Mansona: New page: Hi I'm just wondering about the removal of the ICal File. Why did you do that Toma? I only added it because I felt like it would help people like me keep track of the Release Schedule.

Hi I'm just wondering about the removal of the ICal File. Why did you do that Toma? I only added it because I felt like it would help people like me keep track of the Release Schedule.

Schedules/KDE4/4.3 Release Schedule

2009-04-16T00:01:28Z

Mansona:

KDE 4.3 is the third feature release for KDE 4. All dates given here are subject to revision, but we will try our best to stick to them if possible. The KDE Release Team is acting as the coordinator for the 4.3 release.

== KDE 4.3 ==

If you would like to follow this Release Schedule in your desktop calendar application you can use [http://www.google.com/calendar/ical/5rvr73av7k3501kaecua182k6c%40group.calendar.google.com/public/basic.ics this ICal] link. Alternatively you can see the Calendar on [http://realate.blogspot.com/2009/04/kde-43-release-schedule.html this website].

=== April 16th, 2009: Soft Feature Freeze ===
Trunk is frozen for feature commits that are not listed in the [[Schedules/KDE4/4.3_Feature_Plan | planned feature document]]. Only bugfixes and the code implementing the listed features are to be committed. The feature list also closes today.

Features not already finished or listed on the planned features page will have to wait until KDE 4.4.

=== May 4th, 2009: Hard Feature Freeze ===
Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed. Binary compatibility for new API is not yet required.

=== May 5th, 2009: Message Freeze. ===
All translated messages (GUI strings) are frozen on this date. Only previously untranslated strings or clear errors in strings can be fixed. No major new strings changes should be done. It is ok to remove strings. Exception: Artwork (try to keep the number of new strings low anyways).

=== May 5th, 2009: Tag KDE 4.3 Beta 1 ===
Trunk is frozen for Beta 1 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated.

=== May 12th, 2009: Release KDE 4.3 Beta 1 ===
Beta 1 becomes available for general consumption.

=== May 26th, 2009: Documentation/Handbook Freeze ===
No more substantive changes to documentation or handbooks after this date. Typos, spelling and simple grammar changes are permitted.

=== June 2th, 2009: Tag KDE 4.3 Beta 2 ===
Trunk is frozen for Beta 2 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.

=== June 9th, 2009: Release KDE 4.3 Beta 2 ===
Beta 2 becomes available for general consumption.

=== June 23rd, 2009: Artwork and Bindings Freeze ===
All artwork is frozen on this date. No new artwork should be added. Existing artwork can continue to be tweaked and fixed.

No new additions to the language bindings, except optional bindings as permitting by the kde-bindings team.

=== June 23rd, 2009: Tag KDE 4.3 RC 1 ===
Trunk is frozen for RC 1 release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.

=== June 30th, 2009: Release KDE 4.3 RC 1 ===
RC 1 becomes available for general consumption. Incoming bugs will be reviewed for their severity. Additional release candidates will be created as needed.

=== July 21rd, 2009: Tag KDE 4.3 ===
Assuming there is only one release candidate, trunk is frozen for KDE 4.3 tagging. Only urgent fixes, such as those fixing compilation errors, should be committed.

=== July 28th, 2009: Release KDE 4.3 ===
KDE 4.3 becomes available for general consumption.

Projects/Marble/ProxyConnection

2009-04-05T11:56:18Z

Mansona:

==Introduction==
For all of you who are trapped behind a proxy connection at school or at work and could not connect to the marble repository for downloading new maps, help is now on it way.

Marble now supports two types of proxy connection: Http and Socks5.

==Http Proxy==

There is currently a bug that is not allowing people to connect via a Http proxy, we hope to have this problem fixed soon.

==Socks5 Proxy==

If your Network Provider has given you access to a Socks5 proxy you can fill in the details in
<blockquote>
Settings > Configure Marble Desktop Globe > Cache & Proxy
</blockquote>
or in
<blockquote>
Settings > Settings > Cache and Proxy
</blockquote>
if you are using the Qt Only version.

If you do not have access to a Socks5 proxy there is a Very easy way to set one up for yourself. You will need to have a SSH account on a server that is directly connected to the internet.

====Socks5 for Linux====
As long as you have the SSH command installed ( which you probably do ) you can setup a Socks5 proxy using the command

ssh -D port_number username@hostname.com

where port_number is any port number ( eg 9999 ) that the proxy will be open on your local machine.

with this set up successfully you can enter the proxy host in the Marble Settings as localhost and the port as the port_number you specified.

This will be an Non-Authenticated Proxy so make sure the Authentication Checkbox is not Checked.

====Socks for Windows====
To setup a Socks5 proxy on Windows you will probably have to use the Putty SSH client.

More information will be added here at a later stage or on request.

Projects/Marble/ProxyConnection

2009-04-05T11:54:32Z

Mansona: New page: ==Introduction== For all of you who are trapped behind a proxy connection at school or at work and could not connect to the marble repository for downloading new maps, help is now on it wa...

==Introduction==
For all of you who are trapped behind a proxy connection at school or at work and could not connect to the marble repository for downloading new maps, help is now on it way.

Marble now supports two types of proxy connection: Http and Socks5.

==Http Proxy==

There is currently a bug that is not allowing people to connect via a Http proxy, we hope to have this problem fixed soon.

==Socks5 Proxy==

If your Network Provider has given you access to a Socks5 proxy you can fill in the details in
<blockquote>
Settings > Configure Marble Desktop Globe > Cache & Proxy
</blockquote>
or in
<blockquote>
Settings > Settings > Cache and Proxy
</blockquote>
if you are using the Qt Only version.

If you do not have access to a Socks5 proxy there is a Very easy to set one up for yourself. You will need to have a ssh account on a server that is directly connected to the internet.

====Socks5 for Linux====
As long as you have the ssh command installed ( which you probably do ) you can setup a Socks5 proxy using the command

ssh -D port_number username@hostname.com

where port_number is any port number ( eg 9999 ) that the proxy will be open on your local machine.

with this set up successfully you can enter the proxy host in the Marble Settings as localhost and the port as the port_number you specified.

This will be an Non-Authenticated Proxy so make sure the Authentication Checkbox is not Checked.

====Socks for Windows====
To setup a Socks5 proxy on Windows you will probably have to use the Putty SSH client.

More information will be added here at a later stage or on request.

Projects/Marble

2009-04-05T11:27:21Z

Mansona:

User:Mansona/Marble geodata

2008-09-02T21:47:14Z

Mansona:

==Introduction==
This page is intended to allow for a fuller understanding of how Marble deals with Layers/Geodata. After reading this guide you should be able to:
# understand how marble paints geodata on top of texture data
# develop your own handler for geodata

==Sections==
The Geodata Implementation has been split into two main sections, a parser and a handler.

===Handler===

===Data===
refers to a geodata document, this is what the parser produces if working with a set of geodata

====Difference between a scene and a Data Document====
Not really sure of the difference, but there is one!

====Element Dictionary ====
an element dictionary is intended to be a static list of all of the tags in XML namespace of your geodata XML. this allows for one static list of tags and prevents large amounts of string comparisons throughout the code

==Process==
#create a new GeoDataParser or GeoSceneParser with enum argument referring to the type of document. Enum is available in respective header files
#use the parser to read the file using Parser->read(String filename)
#extract the datadocument from the parser using parser->releaseDocument()

User:Mansona/Marble geodata

2008-08-28T22:56:37Z

Mansona: New page: ==Introduction== the geodata library is were the magic happens from within marble, once you understand this library you have opened pandora's box and the world will be yours for the takin...

==Introduction==
the geodata library is were the magic happens from within marble, once you understand this library you have opened pandora's box and the world will be yours for the taking... Now for the explination