Hi, My long/large rewrite has reached a significant milestone. Reminder: my work consist of adding features to easily extend it. I rewrote the MapSource related stuff in order to use GObject family of classes.
One first significant benefit of this rewrite is the ability to create MapSource from a configuration file. But I also hope to add the ability to add scripts/plugins around this (for more complex MapSource). In order to test this experimental stuff, you have to bring code from http://repo.or.cz/w/viking/guyou.git?a=shortlog;h=refs/heads/gobjectify-map-type * git remote add git://repo.or.cz/viking/guyou.git or * wget http://repo.or.cz/w/viking/guyou.git?a=snapshot;h=df82a41c434276ac74bd366d32bea7251cad20a3;sf=tgz Then, copy doc/examples/maps.xml to ~/.viking/maps.xml, compile and launch viking. Enjoy! This is a work in progress stuff. Many more thing must/can do to polish this feature. But feel free to comment this version (feature, implementation...). Here is a list of already identified ideas: - allow globals configuration files (/etc and /usr/share) /etc: system wide /usr/share: default configuration shipped with viking - decide the logic when reading multiple files: overwriting? complement? only read the latest/prior? inclusion? - should we remove hard-coded MapSource and only ship a configuration file? I think so, because it will easily allow the user to disable some unwanted/broken source. But doing this, a viking unable to find its configuration files will not be able to display maps. - I will certainly rename the classes in order to be more close than the OpenLayers names. Once again, test it and comment it. Any comment is welcome. ------------------------------------------------------------------------------ _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
