Hi Alexander > Ok, > > But export raster map is good feature, a long time ago I sent you > patch that exports full map instead of view port (you discard it). It > is useful feature: I can open raster map, draw tracks, POI and other > usefull info, export it to file print it and take to the backpaking as > a reserve map (in additional to GPS, for example).
If I say export I mean exporting a map into a GPS device readable format like JNX, RMAP or what ever. This is not the same like printing. Most likely I discarded your patch because it did not solve the big map problem. So far no one (including me) came up with a good idea on how to handle very large areas to print. Or how to store them in a normal image file like png, jpeg etc without risking to overload the system's capabilities. > > Referencing also good feature it makes QLGT more like Ozi. I don't > think that separate tool is needed. As a suggestion: make QMS > plugin-extensible. So, if I need referencing tool, I write plugin, it > integrates to Main menu/Other places and now I can create referenced > map inside QLGT/QMS. Also some other features can be implemeted via > plugin interface. Also, plugins can be distrubuted with QMS or as a > separate projects. GUI tool for jnx creation also good idea ;-) I maintain a couple of plugin extensible projects in real life. The idea of plugins has it's benefits as well as caveats. The crucial point is to define an API that gives you access to the data and the GUI. If that is done badly plugins are worth nothing. Anyway supporting such an API is additional work on every development step you do. That might be worth it if you have a highly modular application and you just want to hand parts to customers. But the average QMS/QLGT user wants it all anyway. Thus keeping the parts together in one monolithic application seems to be the better way. > > Regard "random map place", one usecase: I click link in browser to > referenced map, "Download/Open with" dialog is appear, I select Open > with... QLGT/QMS and maps opens. I am happy :-) And next time you want to use that map again, you do not know where it was downloaded (download path or temporary path?). I think placing the file into a designated path is reasonable. As long as it is no raster map that needs a *vrt file as wrapper, it's completely integrated into QMS by that. And the *vrt thing saves me a lot of work on the programming side. Probably this can be done a bit more user friendly. But so far using the command line is much faster for me than thinking of a good concept. ;) > > About name... KDE4 writen from scratch (KDE2, KDE3 in most cases too) > but name is same. Really QLGT is a best GUI mapping application in > Linux, so keep its name is a good idea. I use KDE more or less right from the start of it. The version steps where triggered by the QT library. And sure, they corrected concepts, too. But it was and is always the same bloated window manager that does a thousand things you don't need and has a heap of badly implemented features. Still, I like it. Probably because I know where to hit it. But that is not the kind of evolution I see in QMS/QLGT. Speaking in window mangers it's more like LXQT vs KDE. > > > PS heh, sorry for my english :( > > 2014-10-15 18:53 GMT+11:00 Oliver Eichler <[email protected] > <mailto:[email protected]>>: > > Hi Alexander, > > the main problem of a feature comparison list is to know the > features of > QLGT :) The plan is to implement all features I am using in QLGT > as fast > as possible in QMS and drop everything else silently. Except > someone is > asking for a feature explicitly and gives a good reason why it is of > general interest. > > The lesson I learned over the years is that trying to implementing > every > wish is consuming a lot of time and is making software bad as > there will > be concept clashes. Plus you implement stuff and never receive a > feedback. Month later you find a bug in the code and you know no one > ever used that feature. Time wasted. Thus it's not my goal to make > QMapShack 1:1 feature compatible with QLGT. > > And that is one of the reason why I changed the name. It will not be > QLandkarte 3.0. > > Btw, features I plan to keep _out of_ QMS: > > * Map export. I never used it in QLGT. I use the converters > directly on > my local raster map files. You do this once and that's it. No need to > export small parts. > * Map referencing. This is just the task of another tool. For the time > being this is QLGT. Maybe I write some standalone application one day. > * Extended Geocaching support. There are many applications doing > it better. > * WMS support. In all the years I did not find a source of WMS > maps that > is really worth the problems this is causing. > > Features that might be added if someone volunteers to add > maintained code: > > * Mapsforge maps. I had a look at their format. If you have a > ready made > tile render lib it's ok. But I will not write that from scratch in > c++. > * 3D: Everyone wants it, hardly no one uses it. > * Extended GPX data and other formats. > * ... > > Maintained code means: It's wrapped in ifdefs. QMS must compile > and work > with and without that stuff. As long as bugs and feature requests are > fixed the code will be mainstream. If support is dropped the > feature is > dropped. > > Concerning random placed maps: You can add as many paths to maps > as you > want. But opening a file from anywhere on-the-fly will not work. I > don't > know your system, but on mine data is sorted more or less by folders > grouping the data by what it is. Thus it's not that random after all. > > Oliver > > > > Am 15.10.2014 um 09:11 schrieb Alexander Drozdov: > > Hi Oliver! > > > > Is there feature comparation list between QMapShack and > QLandkarteGT? > > Also I found that QMapShack can't work with random-placed-maps (e.g. > > open from any place on file system) only with configured > collections, > > is it right? > > > > PS QLandkarte is a very good and vivid name, so it will be > perfect if > > name will be saved. IMHO :-) > > > > > > 2014-10-15 17:41 GMT+11:00 Oliver Eichler <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>>: > > > > Hi, > > > > a quick new release. It's all about manipulating and > changing tracks. > > See the wiki for more details: > > > > https://bitbucket.org/maproom/qmapshack/wiki/DocGisItemsTrk > > > > > > Oliver > > > > > > V 0.6.0 > > * Reverse tracks > > * Add dialog to combine tracks > > * Add range select to tracks > > * Add function to hide/show track points > > * Add function to copy selected track points as new track > > > > > > > > ------------------------------------------------------------------------------ > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push > > notifications. > > Take corrective actions from your mobile device. > > http://p.sf.net/sfu/Zoho > > _______________________________________________ > > Qlandkartegt-users mailing list > > [email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>> > > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > > > > > > > > > > -- > > WBR, Alexander Drozdov > > http://htrd.su > > > > > -- > WBR, Alexander Drozdov > http://htrd.su ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
