Closed sleepdeprecation closed 10 years ago
Never mind, it seems to have worked now... weird...
Though I do have this error:
Failed to load resource: the server responded with a status of 404 (Not Found)
http://127.0.0.1:3030/turbo_wookie/web/dart/main.dart.js
Also, looking at what opens up with the dart editor, shouldn't you move the index.html file to just frontend/turbo_wookie/web
? Because it references stuff not in only the html subdirectory, and if we want to access those, we'll have to adjust lots of things...
You probably had to run the pubspec.yaml
file to get the first errors to go away, but it may have done that for you. That's the file that handles all the dependencies.
As for the second error you have, I get that too, but Rick doesn't. I have no idea what it is.
Run in what way?
If you use the editor you can right click the file and choose pub get
.
I think you can also just use pub get pubspec.yaml
in the command line.
K.
Hows about that web/index.html
instead of web/html/index.html
?
Why would that benefit it? We can access all the front end things if it's there. Can you not or something?
Uh ... no we can't...
There is no ../
from index.html
, there's also no css
directory, img
directory, or dart
directory. Because those are all out of the range of the file server (which is only html
and things inside it).
Ok. calm down. It works fine with just Dart, so I wasn't sure if Go didn't allow you to go back or not.
It doesn't work just fine in dart. Dart's server sets the root to either the frontend directory, or the turbo_wookie directory, and just opens up the web/html/index file for you. Look at the URL when you run it...
Don Kuntz http://don.kuntz.co | don@kuntz.co
On Thu, Nov 14, 2013 at 10:09 PM, Michael Peterson <notifications@github.com
wrote:
Ok. calm down. It works fine with just Dart, so I wasn't sure if Go didn't allow you to go back or not.
— Reply to this email directly or view it on GitHubhttps://github.com/dkuntz2/turbo-wookie/issues/5#issuecomment-28546068 .
And that is why I didn't know.
Define "worked fine"...
It worked, but it wasn't doing what you're implying it should...
Also, completely separate: http://ianstormtaylor.com/design-tip-never-use-black/
You wrote that too fast...
Quoi?
If your trying to say that we shouldn't use black, that article says don't use pure black, meaning that close to black is ok, which is what we use.
So the file thing?
I just pushed a change that fixed that.
Cool. Cool, cool, cool.
Dart failed to load some resources...
Exact error:
So, uh, that's not good...