[Marble-devel] Re: 1.1 Release Preparations

Torsten Rahn tackat at t-online.de
Tue Apr 12 23:28:37 CEST 2011


On Tuesday, 12. April 2011 21:01:14 Bernhard Beschow wrote:
> Hi everyone,
> I just had a look at the state of the map wizard in the marble-1.1 branch.
> Compared to the master branch, it is missing quiet important improvements
> such as intensive error checking and a simplified UI. 

The Map Wizard feature has been advertized as the most important feature of 
Marble 1.1. I've just presented it during the FOSSGIS conference as one of the 
important milestones of Marble 1.1.

I see your point that Marble 1.2 has a better version of it which is much 
closer to the perfect world solution. But this is natural: Marble 0.4 sucked 
big times compared to Marble 0.8. And if I see Marble 0.8 these days installed 
on a computer I immediately cringe and feel bad because Marble 1.0 is so much 
better in many ways. I'd say: get over it :-) The 1.1 Map Wizard works quite 
well and in the Marble 1.1 version it's certainly something that is rather 
suited for the experienced user. And that is better than providing no wizard 
at all. Like this we can still ship it and collect feedback to make the wizard 
in Marble 1.2 even better than the one that we currently have in 1.1.

Don't worry: We won't ship it for long since Marble 1.2 will follow in 3-4 
months (and I'm sure you'll feel bad about the state of the Map Wizard by the 
time that Marble 2.0 gets released since that one will have an even so much 
better solution ;-)

I'd even go so far to say that without the Map Wizard feature we can basically 
forget about the whole Marble 1.1 release.

So I'd say: let's ship it. It works quite well, is documented and it's of 
course just a start and a quite good one even :-)

Best Regards,

> IMO, these
> improvements are essential for users to get a working map theme.
> Unfortunately, due to significant API changes, backporting has not been
> done. Thus, I wonder whether we should deactivate the map wizard or
> advertize it as an unfinished feature for now. To be onest, I'd rather
> switch the map wizard off.
> If we go for deactivating the map wizard feature for now, there is a simple
> solution for the KDE version: If we just comment out the action in the rc
> file, an advanced user could re-activate the map wizard by uncommenting
> the action. I wonder whether there exists a similar clever solution for
> the Qt version?
> Greetings,
> Bernhard
> _______________________________________________
> Marble-devel mailing list
> Marble-devel at kde.org
> https://mail.kde.org/mailman/listinfo/marble-devel

More information about the Marble-devel mailing list