Roadmap to 2.2.0

[Indigo744]

@neveldo

Can we list the remaining features / tasks needed for the release of 2.2.0?

• Fix Tooltip is blinking when hovered to the lower part of the map #361
• Review/Merge PR Enhance zoom options with plot and area #337
• Review/Merge PR Various internal improvements #344
• Implements Disable plots zooming #253/Review/Merge PR Zoom plots scaling #352
• Fix Strange border lines in 'world_countries' #346/Review/Merge PR Add a better version of world countries map mapael-maps#44
• Implements zoomOnCLick/Review/Merge PR (TBD)
• Update Changelog (in progress)
• Update documentation (in progress)

Also, should we implement #276 for 2.2.0?

Regarding the mapael-maps repo, should it follow the mapael repo version or should it have its own numbering?

[neveldo]

Hi,

This roadmap looks very good for the version 2.2.0 ! I think that #253 should be more prioritary than #337 if we stricly consider the number of requests from the users, but it seems that you are already working to resolve #276 !

Have you already begin to work on the changelog or documentation ? Maybe I can help on this parts ... (sorry for not helping you more on code itself and the features, I have quite few free time at the moment...)

[Indigo744]

Sorry I mixed up the PR number! I am actually working on #253 and plan to land the PR soon. As you said, a lot of people were asking for this feature.

#276 is actually more complicated than previously though. We will need some more discussion there.

I've added #340 to clean up some bbox codes.

I would be glad if you want to tackle the changelog/documentation part :)

[neveldo]

Ok for the changelog/documentation part, I will make some PRs soon, probably in the next few days :)

Ok for #276 , it will bring a highly requested feature !

Thanks for having added #340, I was just editing the roadmap, but you have been quicker than me ;)

[Indigo744]

Alright! Hopefully our modifications didn't collide :)

But I think you meant #253 (plot size reduction), right? So much different numbers....

Also, what about the mapael-maps repo? Should we follow Mapael releases?

[neveldo]

What would be the advantages of following the same versions between the two projects ?

NB : For now, I didn't tagged any version on the mapael-maps repository.

Even if the two repositories are tightly related, I think that they could be versionned independently from each other. For instance, we could release a new major version of mapael-maps if we needed to bring some non-backward compatible changes to them in order to work properly with a new major version of jquery mapael (we can still add a note into the readme to mention the compatibility with the version(s) of mapael). We could tag a minor version whenever we add a new map, and a patch version for a fix on a particular map. What do you think ?

Moreover, maybe the mapael-maps repository should be available through NPM (and why not on cdnjs ? (mapael is already on cdnjs, but they didn't added mapael-maps despite I asked them to :( )

[Indigo744]

Regarding CDNJS, it's ongoing I think, see #270

I think you are right. However, we may need to tag version more regularly (and generate minified version), like after adding a map.

[neveldo]

But the PR is open since more than one year, I have ask for some news on it !

[neveldo]

Hello @Indigo744 ,

I'm thinking about some other features for the next release.

• Since you have added options to zoom-in ona specific area or plot, I think it could be interresting to have an option such as "zoomOnCLick : true|false" for areas and plot ! What do you think ?

• The more I think about it, the more I wonder if supporting GeoJson wouldn't be a "killer feature" ! I need to find some time to dive into the format (I confess, I don't know much about it for now).

• I wonder if we couldn't provide a way to set a CSV file as source to generate plots or areas ? I think it could ease the creation of choropleths. As you can see in https://www.vincentbroute.fr/mapael/try.html , it takes a very few lines of code to convert a CSV to a mapael-compatible collection of plots or areas properties. We could for instance set a conf like this :

{
    (...)
   "plots": {
      "csv": "http://www.(...).com/data/plots.csv",
      "separator": ",",
      "enclosure": "\"",
    },
    (...)
}

[Indigo744]

Love your ideas! However, should we really add these for 2.2.0? Or do you mean 2.3.0?

[neveldo]

You're right, the last two could take a long time to achieve ! However, the first one could be easy to add I think as the hard part is already done ! :)

[Indigo744]

Agreed. I'll make a PR for the first part. Should we open a new issue for discussing and scoping 2.3.0?

[neveldo]

Hello @Indigo744 ,

What do you think about extending this thread with the roadmap for all the next minor releases of Mapael, and discussions about the features & patchs to include in each of them ? And we could use the other thread #345 to discuss about the big changes for the next major releases.
Or maybe you prefer to split the discussions for each version into several threads ? (I have no preference for my part, but maybe it would be easier to handle the discussions within a limited amount of threads)

[Indigo744]

IMHO a thread per version would be better. Hence we can list the tasks and users have a clear view of the remaining work. When a version is out, we can close this thread so it will not be a burder anymore. We don't have a lot of version anyway, so we are not talking about hundred threads ^^

[neveldo]

Alright for me !