[Marble-devel] Ideas for more tasks

Fri Mar 13 21:28:46 UTC 2015

Here is a rather "easy" task: 

In the Tourpanel when right-clicking the slider an RMB menu should appear. That RMB menu would contain a checkable menu entry "Repeat Tour". By toggling this action a user can decide whether the currently loaded Tour would only be played once or over and over again. This would be useful for Marble presentations at fairs where we could automatically play the same tour endlessly.

Best Regards,
Torsten

-----Original-Nachricht-----
Betreff: AW: [Marble-devel] Ideas for more tasks
Datum: Wed, 11 Mar 2015 18:37:32 +0100
Von: "Torsten Rahn" <tackat at t-online.de>
An: marble-devel at kde.org

Just to further clarify the motivation behind this task: While it's possible to move the nodes using drag and drop already, this node dialog allows to further tweak the position (e.g. to full minutes or to align the nodes to an exact location). So moving the nodes via drag and drop won't go away and both approaches have their own use-cases ... 

-----Original-Nachricht-----
Betreff: Re: [Marble-devel] Ideas for more tasks
Datum: Wed, 11 Mar 2015 18:33:46 +0100
Von: "Torsten Rahn" <torsten.rahn at t-online.de>
An: "Marius Stanciu" <stanciumarius94 at gmail.com>, marble-devel at kde.org

Sounds good - let's give others some time for feedback  on the issue in the meantime. And the node thing looks indeed a bit more straightforward. Looking at the existing widgets the better pick is probably to use the ready-made LatLonEdit widget which is located inside src/lib. I guess ideally on  selecting a node row in the dialog a delegate for editing would get instantiated which would display the coordinates using the LatLonEdit widget. Once a different row gets selected it would turn to normal text again. Does that sound good or do you have a better idea? :-)

-----Original-Nachricht-----
Betreff: Re: [Marble-devel] Ideas for more tasks
Datum: Wed, 11 Mar 2015 17:36:47 +0100
Von: Marius Stanciu <stanciumarius94 at gmail.com>
An: Torsten.Rahn at t-online.de

Since i'm not really sure how i would contribute to making such  a decision( which tag is more appropriate ), i'll go ahead and work on the Edit node position task you listed firstly. ( the one for the polygons ) At least until the course of action is decided for this one.
2015-03-11 16:22 GMT+02:00 Torsten Rahn <tackat at t-online.de>:

 I guess the gx:Wait doesn't usually expect the MetaData tag to be a child of the Wait tag.
 I'm not sure what solution would be the best fit - but we should decide on this (and validate the proposed KML code) before actual coding is started. What about doing maybe something like this (without the Wait and Metadata tags):

 <mx:Property name="theme">OpenStreetMap</mx:Property>
 <mx:Property name="projection">Mercator</mx:Property>

 -----Original-Nachricht-----
 Betreff: Re: [Marble-devel] Ideas for more tasks
 Datum: Wed, 11 Mar 2015 13:17:00 +0100
 Von: Marius Stanciu <stanciumarius94 at gmail.com>
 An: Torsten.Rahn at t-online.de

 I would like to implement the map-theme-change element for the tour panel. I was thinking about adding the element as Metadata/ExtendedData to a normal <gx:Wait> tag. It would look something like this:<gx:Wait>        <Metadata>       //or Extended-Data                   <Property name="theme">OpenStreeMap</Property>                   <Property name="projection">Mercartor</Property>        <Metadata>        <gx:duration>1</gx:duration></gx:Wait> This would be convenient also because changing to another theme shouldn't be done instantly, it should have a (customizable) delay before the next element starts, so essentially, it's still a type of Wait element.
 2015-03-11 10:11 GMT+02:00 Torsten Rahn <tackat at t-online.de>:

  Oh and after testing Marble a bit I just realized that the "Add GroundOverlay" feature doesn't seem to display the image anymore (it never displayed it in Atlas mode due to the special treatment of color palettes there but it should display it in almost all other map themes). This is certainly a regression. So another possible task might be to fix this bug (could be done by git-bisecting backwards and thereby identifying the point of time where the regression occured).

  -----Original-Nachricht-----
  Betreff: [Marble-devel] Ideas for more tasks
  Datum: Wed, 11 Mar 2015 08:59:01 +0100
  Von: "Torsten Rahn" <tackat at t-online.de>
  An: marble-devel at kde.org

  Hi,

  Here are a few more ideas for possible tasks:

  Edit Maps Panel:
  =============
  - Editing node positions: Currently when adding polygons or paths the associated dialog displays the nodes coordinates in the nodes tab. It would be nice if the coordinate position of those nodes could be changed from within the nodes tab. The challenge there would be how to deal with the different notations that we allow for (DMS, Decimal, ...). One possibility would be to have the text value turn into a set of spinboxes once an entry gets selected. Or the currently selected items is shown on top of the list as a regular EditLatLonWidget where it could get edited then.

  - Allow for draggable resizing of GroundOverlays: Currently it's only possible to specify the position and extent of a GroundOverlay via the associated dialog box. It would be nice if handles would be added to the corners and on the sides that would allow for resizing the GroundOverlay interactively.

  - Support for GroundOverlay Dialog in Files Panel: If you Right-Click on a GeoDataPlacemark entry in the "Files" Panel then you get a "View Properties" menu entry. Clicking it will bring up the "Edit Placemark Dialog" in Read-Only mode. It would be nice if the same would happen when clicking a GeoDataGroundOverlay (After it has been created e.g. via the Edit Maps Panel)

  Record Movie:
  ===========
  - Fix "Record Movie" feature. The feature provided "Edit -> Record Movie" has certainly got potential for further bugfixes and improvements. Try it yyourself and check what could be improved.

  Tour Panel:
  =========
  - It would be nice if it was possible inside a Tour to change the map theme or projection. This would allow for further automation of Marble via the Tour Feature. However this would most certainly require some "custom Marble KML tag". One of the challenges with this task would be to find some way to implement this so that e.g.  http://www.kmlvalidator.com/home.htm still considers the resulting KML code valid.

  If you want to work on one of these tasks please just speak up :-)

  _______________________________________________
  Marble-devel mailing list
  Marble-devel at kde.org
  https://mail.kde.org/mailman/listinfo/marble-devel

  _______________________________________________
  Marble-devel mailing list
  Marble-devel at kde.org
  https://mail.kde.org/mailman/listinfo/marble-devel

 _______________________________________________
 Marble-devel mailing list
 Marble-devel at kde.org
 https://mail.kde.org/mailman/listinfo/marble-devel 

_______________________________________________
Marble-devel mailing list
Marble-devel at kde.org
https://mail.kde.org/mailman/listinfo/marble-devel