avernois / devfriendlyplaces Goto Github PK

Some places are closed during one weekday, to balance the working-saturday. maybe it would be a good idea to put a "closed-on" propery in the dataset to indicate this

All data could fit on one map. Or perhaps a complemtary map could contain all markers ?

in the readme, the paris link points to cumbria

Add a link on the page to help visitor knows where and how they can contribute and add new friendly places.

A solution could be a ribbon like github's "fork me on github" in the upper right corner

... and see what can be done to merge the address on a map

https://github.com/diasdavid/awesome-hacking-spots

An url field wich seems to be always "undefined" is shown in popup of places.
And another field called website wich seems to be correctly filled.

There should be only one.
And if no url is defined in the JSON for that place, nothing should appear in the popup.

Just like power and wifi are important for the dev’s machine tools, bathroom is useful for the dev’s body ;)

To really modernize the application, and prepare for eventual evolutions, we could refactor the javascript to use require.js and implement AMD modules.

http://requirejs.org/docs/whyamd.html

Wanted to had a place and all the data are gone.
https://raw.githubusercontent.com/devfriendlyplaces/data/data/locations/locations.json works but there is no branch in the url.

And what about the local dev fix: #201 ? Should it be trowed if favor of an elm version ?

It would be great to automatically deploy the new version when something is pushed/merged in master.

It would be great to have an index of all available cities.

Maybe via the root devfriendlyplaces.net ?

This issue come from a comment by @brunobord on issue #19

It could be nice to display maki map icons depending on the type of place.

• cafe for café,
• bar for pubs or bars,
• restaurant for restaurants, brasseries

when no icon is suitable, use the default marker, et voilà.

Right now we have these JSON semantics for describing a place:

    {
      "name": "L'impro",
      "lat": "43.602984",
      "lon": "1.4416109999999662",
      "address": "7 Carriera Leon Gambetta" ,
      "type" : "coffee",
      "power": "no",
      "wifi": "no"
    }

I could totally see switching from strings to boolans for the wifi & power fields to ease further filtering/facetting; but the we would miss the ability to comment on the feature, so why not introducing a simple substructure which would just allow combining both aspects? eg.

  {
      "name": "L'impro",
      "lat": "43.602984",
      "lon": "1.4416109999999662",
      "address": "7 Carriera Leon Gambetta" ,
      "type" : "coffee",
      "power": {"available": true},
      "wifi": {"available": true, "comment": "intermittent failures when overcrowded"}
    }

We could even support undefined for when the situation is unclear, eg.

    {
      "wifi": {"comment": "short term subscription required"}
    }

Places with flags set to undefined would be retrieved anycase when filtering.

Thoughts?

hi there,

is it possible to create an index page or pane that allows people to navigate to the city they are looking for, also, defaulting to the city closest to the visitors location would be good..

Cordialement

As a contibutor I want to report a particularity to better describe the place

example :

• noisy on friday
• room upstairs for meetings

Right now latitude and longitude fields are stored in strings, while they should imho be stored as numbers:

    {
      "name": "L'impro",
      "lat": 43.602984,
      "lon": 1.4416109999999662
    }

I know js supports dynamic type inference but I wouldn't suggest relying on it too much ;)

On my phone (htc one S) and my tablet (samsung galaxy II) when I touch the selector notihng happen.
Problems occurs with firefox or chrome (latest version).

Works fine on my laptop.

Maybe a problem of click/touch
(ping @AntoineCezar)