I'm no lawyer, but a simple layman's explanation would be:
MIT/BSD: Do whatever you want with the code, just give me (you/your company) written credit for it.
LGPL: If you modify this code, you're legally obligated to release these modifications under LGPL. If you link/reference this code, the code linking/referencing it does not have to be released under LGPL
GPL: If you modify this code, you're legally obligated to release these modifications under the same licensing terms. If you link/reference this code, that code also has to be released under the GPL.
My personal views about the above licenses:
I default to LGPL for desktop-based software/libs because you're free to use my stuff un-modified with no obligations, but if you do modify my stuff, I'd like these changes to be made publicly available as well.
GPL is a bit too extreme for me because I don't want to impose my licensing terms on your code that's using my lib/framework. GPL is said to be "viral" for this very reason and why I think it's a terrible license for web applications/libraries/frameworks IMO. Sencha licenses their code under GPL and that's why I don't touch it with a 10 foot pole, no matter how attractive that framework is.
MIT/BSD is a bit too liberal for me because I don't want my works to be free-loaded without some level of reciprocated contributions. LGPL enforces this. MIT/BSD does not.
So I'd pick between MIT, BSD or LGPL. LGPL if you care about people contributing back. MIT/BSD if you don't. Or you can license your code under multiple licenses and the user can choose which license they want to use your code under.
But yeah, putting your code on github/bitbucket/googlecode/etc will encourage external contributions from other developers.
You can open that wiki page and edit as necessary, but maybe not necessary since there is some information on the github page (there should be an "Edit This Page" button at the bottom). Prior to editing, you need to be logged into the trac system.
It looks like your mobile example has a little bit of interest just judging by the number of views for this thread.
This is a great viewer you have made. I am trying to get it up and running locally so I can play around with it. I've got it working... sort of. I can get it to load with no error messages but I get a map with Scale 1:0 which is just brown. I am specifying WEBLAYOUT in the URL like you would for mapviewerajax, as is stated in the installation instructions. I have tried a variety of different .WebLayouts but none will work properly. What would be the procedure to get a working web layout from the Sheboygan sample map? Thanks for reading.
You had mentioned that you had implemented MG natively. Can you by any chance share what you did to at least get me started? We are trying to implement an app for Android and possibly iOS that will have MG available offline and just don't know where to start. We have thought about PhoneGap but again don't know where to start. We have created mg-desktop successfully and want to do the same type of thing with tablets.
Any help you or anyone else can give would be greatly appreciated.
Would it be easy to capture a photo, a coordinate and about 10 attributes and
attribute values using the mobile app? Also, if it is not possible to be
connected to the internet when capturing the data, is it possible to create
a form and store the data on the mobile device until a connection is
possible? When the connection is possible, the data could then be uploaded
to SQL server... Is that functionality possible?
I do have one query though, the layer tree seems to show all layers, including hidden/invisible. In order to keep my mobile legend the same as the full AJAX viewer legend I'd prefer hidden/out-of-scale layers to remain hidden.
I tried changing getLayers() and getLayerGroups() methods in jqueryLayerTree.aspx to getLayers(true) and getLayerGroups(true) for onlyVisible, but this just causes a compilation error. I am no coder so I am probably being stupid here. Any ideas?
That works really well, and the legend icon in the layer control widget is really useful, thanks!
One last query, is it possible to also check the map definition to see whether or not each group/layer is shown in the map legend? Sometimes we hide layers and groups so that the user cannot turn them on and off or see them in the legend, but these groups and layers currently show up in the mobile layer control widget.
I have finally gotten around to installing this mobile viewer. I am currently using MGOS 2.5 on Win2008 server (64bit). I have followed the install instructions, and using the following url string to view the map (kaliopa is the application folder):
I am able to see my map without any error but when I click the "Locate me" button it opens a message box telling website says geolocation was blocked by the user.
I am able to see my location on Google maps etc.