tilemill-project / tilemill Goto Github PK

No idea why this one's the case, but it's annoying.

Simple, but a much-needed tweak. Need to find a javascript library for this.

Not sure how it broke.

They should also help users out with images, textures, shields, etc.

in project.js, it should be possible to start with a different shapefile.

In some cases, the layer inspector will inspect the first layer even if others are selected.

This should be relatively simple, but it's by no means necessary.

It's a tiny tweak, but will make things a bit more tilemilly

Will have to be fast with this one...

As noted in map.js

As it says on the tin and in the code.

Since integration, they'll work, but won't work straight-off right now.

It'd be useful to have an openlayers or polymaps snippet generator in the info tab.

potential feature creep: provide embeds

It's the big one.

jQuery, etc., is bundled with this. Same thing with the openlayers theme. This shouldn't be the case, but this isn't a super-high priority.

We need to handle really long font names and cases in which people have more swatches than we provide space for.

For designing base and overlay layers, it's useful to mix & match layers from different projects in the map. This shouldn't be insanely difficult, so let's do it.

AIR is kind of a failed system, right? People only install it if they want Twitter apps... it's not a huge amount of code so it's not begging to get removed, but I don't think that it's very well justified here.

Users need to know which fonts are available.

We need some way of entering in data that doesn't require you to know and copy/paste URLs.

A naïve implementation might be:

• Something needs to provide JSON in a certain structure to TileMill
• One of the providers is TileMill itself, and it does this by letting users manually add URLs and stuff into it
• For demo purposes, we can include a JSON file with some already in there
• Down the road, you can plug in an S3 bucket which will be automatically traversed to provide said JSON
• The add layer popup will add the layer to the database and then a reference to it in the project

Currently the S3 provider shows all files. It should only show public files.

Right now it's annoying that TileMill requires 5 processes to run. Narrow it down a bit.

This will require TileLive to expose 'yet another' thing about layers, but will be terribly useful for demos of subsets of data, which otherwise require lots of guessing & finding things.

Something (probably the ctrl-s addition) broke this, and it's important. Need to fix.

This is the most common error a new user would see, and right now the system just crashes and burns. I can think of some better ways to handle this case.

Not decided on whether the preview should just be larger all the time, or whether it should be a draggable division, etc. But cascadenik is rarely wide, and the map preview is always so tiny, thus, let's adjust.

Currently a file thrown in there shuts it all down, this shouldn't be the case.

TileMill should be able to access local shapefiles and keep track of them decently well - possibly having a folder of resources with the ability to add them in via a drop-down.

Feature-creep could include searching, metadata editing, etc.

TileMill includes a plethora of javascript in its head element - this shouldn't be the case. We should use head js http://headjs.com/ to load them.

Instead of AIR, we should support offline by adding localstorage. This might get interesting if we use backend.js as a cache/sync.

Inline help would basically work as:

• detect selection in codemirror
• show and add/move question-mark element
• on click of question mark, bring up popup reference

Might be a popup or an accordion-style task.

• The UI should support hierarchal structures, in the directory provider and s3 provider.
• DONE Providers should be Backbone models
• DONE One should be able to add providers via the UI, and multiple of each type
• DONE Providers should support paging

We should use a better, more mature template system instead of the john resig code.

It shouldn't be super hard to let users interact with tiles.

Unclear exactly how this should play out, but it's gotta happen.

We need to decide what browsers and other requirements should be placed on using TileMill. This is really important because we have the chance to use other technology (aka 'the good stuff') if we don't support IE, and we should keep certain Javascript quirks in mind if we do support IE.

Currently TileMill requires IE7+.

This is relatively simple to do an a pretty big usability win for continuously testing styles

This probably came about via PHP, but this needs to be fixed - there's a straight call to http://localhost:8889/file which fails on the browser level.

gotta do it.

The current 'doing something' icon is okay, but it'd be better if there was some description of what's going on behind the scenes.