gatineauouverte / parcs Goto Github PK

The close button (x) of the InfoWindow is not showing unless you hover le element in Chrome. I am not sure yet what is causing the issue, but it might be related to some of our custom CSS code. I have noticed that the close button node has an opacity of 0.7 by default, but won't be visible until the opacity is changed to 1 (which is happening when you hover it).

A quick fix might be to set opacity: 1 !important; on that node. I have not tried to see if it works yet...

The facebook and twitter and other external scripts not required for the map should be loaded at the end of the body to avoid blocking the loading process of the page when they take time to gather.

Régler le problème mentionné ici: https://github.com/GatineauOuverte/parcs/pull/18/files#r648069

Fusion tables, MarkerClusterer https://developers.google.com/maps/articles/toomanymarkers?hl=da#fusiontables

Nous devons ajouter un lien qui permettra aux usagers de changer la langue de l'application.

?locale=en pour l'anglais et ?locale=fr pour le français.

Pour la version iPhone / iPod, j'aurais besoin d'une version 2x des icônes suivants:

• gatineauouverte.png (270x115): nouveau fichier "[email protected]" (540x230)
• pev1.png (309x115): nouveau fichier "[email protected]" (618x230)

SVP nommer les nouveaux fichiers avec "@2x" comme ça ils seront lus automatiquement par iOS.

Merci!

The query currently returns some duplicates when passing a sectors or installations criteria.

Devrait-on renommer le repository Parcs ou parcs au lieu de gatineau_parcsespacesverts?

I have merged the latest changes - deployed locally...
here is what we need to complete before we push live:

-Please do not make any changes to the UI for now - all nice and good (will make new changes once we clear all issues)
-English and French links OK, but would also like to see Facebook and Twitter button be localized when switching languages
-About Box/A Propos content should also be localized...

Once we have these addressed will push and we should consider these final changes as the last code base before we move to version 2.0