Closed springmeyer closed 13 years ago
It would be really nice to have more feedback from tilemill about exactly what it's doing, and how much more work there is to do. Downloading the initial shapefile isn't the only slow thing.
Progress indicator is similar to #427. I think bundling the basic shapefile makes sense. What are the downsides?
So the main concern I guess is where to draw the line once we start storing data in this repo. It would be better to keep all data centrally as resources like we have done now.
We also haven't hear of many people running into problems with this.
We have tried to address this in the past using other approaches. What other options do we have? Should we just work on a progress indicator system?
I agree we need to draw the line - but the default shapefile used for a new project is well within that line in my opinion. #639 was a great fix for the experienced user. This ticket is about the first run experience and it being potentially awful for those with slow or spotty connections. I think the only way to solve this is to bundle. For people with a good connection first project creation does not need a progress (or will not benefit from a) bar since it is likely be so fast, though a progress bar would be an awesome thing in other parts of the app.
This appears not to be working in the 0.5.1 ubuntu package. Here at foss4g testing trying to upgrade the VMs. Net is horrid. Creating a new project took about 5 minutes of wait on the spinner.
/usr/share/mapbox/data/
is empty.
@springmeyer, is this on a fresh install? Can you check your cache directory? TileMill should create a directory called 1aa2d236-10m-admin-0-countries
on first run, but only if the cache directory doesn't exist already.
It should be in /usr/share/mapbox/cache
.
ya, it is there now, after the initial wait. Maybe I am misunderstanding? Should there still be the first run download wait? I am on my first machine of 25, so I'll have a chance to check the cache directory on the next machine(s).
After installing, TileMill will start and the file will be copied over to the cache
directory on this first run. This is what happens on my system. Right after installing and before opening TileMill in the browser, look in the cache directory for the shapefile.
If it's there, it should get used. Could any slowness be related to downloading files for the sample projects? Also, maybe there is a problem with this on natty.
An easy way to rule out the sample project thing would be to delete them before opening TileMill in your browser.
Huh something else is going on. It looks like tilemill isn't satisfied with just the shapefiles and it gets upset that there isn't an actual zipfile. In hindsight this makes sense because it's the zipfile that is referenced by the project. I'll work on a fix.
ya, so the cache is there upon installation. the zipfile thing sounds likely. we should also not rule out that the downloading of the non-cached projects is blocking something around the project creation. It it looking like it will take these machines more than 30 minutes to get the projects downloaded.
Pushing a fix for the zip thing now. Not sure what to do about the sample projects for the immediate besides just deleting them manually after installation.
This should be fixed in the lastest ubuntu build.
Discussed with @yahn last week about bundling the default project shapefile. At the time I was on a rural connection. now I'm back in the city of Seattle and have basically the same download speeds: pathetic speeds around 30-40 KB/sec.
So, I'm back proposing that we bundle this 9 MB shapefile because on a connection like this creating a new project (if the shapefile is not cached) takes > 2 minutes.
For new users that download the tilemill.app and hit this its going to appear that tilemill is broken out of the box because they'll have no idea tilemill is even trying to download anything when they create a project for the first time.
Here is how bad things are:
This is despite speakeasy reporting my download speed as: