Submissions from 2015-02-15 to 2015-02-16 (3 total)

Unfortunately, didn't do too much today. Did some sketching and drew one building, not sure what will it be. I'll add the image to this update. I would be happy for any feedback since I'm not he best artist and the building definitely can (and will) be improved. :)

Yesterday's update can be found here.
In a case of any questions or suggestions, don't hesitate to contact me here or on twitter. ;)
For more updates, you should follow my twitter account - @PeterLauris and the account of Crystal Kingdom - @CrystalKingdom_
.

Spent a fair amount of time benchmarking the Go code against Sprockets (I was curious.) The Go Javascript serving isn't as fast as the Sprockets implementation currently. One thing that I can think of that could get it closer to that speed would be last modified checks and serving the preprocessed version. Overall though, as far as on my desktop, I wasn't too disappointed with the results. 20ms to serve the Ember.js app (including the debug ember.js & jquery.js files.) compared to 8ms from Rails with Unicorn. Somewhat interesting was the BeagleBone Black took roughly 1400ms to serve the same files from Go. I wasn't able to run the Rails test on BeagleBone Black hardware because...

A good portion of my time was spend trying to figure out why ember-rails on the BeagleBone Black was throwing an "undefined method 'ember'" error when trying to run rails generate ember:bootstrap.

I finished the night off writing unit tests for the template code. I got to about 60% code coverage (of ~150 lines.) Overall, I was pretty happy with how well the code behaved when I started writing tests. A few things that I expected to throw errors or junk output, ended up being handled gracefully. It's likely because I did a fair amount of iterative testing before this point.

Today I spent a couple of hours getting the HTML classes and CSS outputted to be optimal. The styling is now diff'd between parameterized components and base components so that there's no doubling up and HTML classes are only applied based on whether variables were read from in the 'styles' block which is helping make the HTML a lot cleaner.

In the midst of this I've noticed that 'attributes' have become broken, but I'll either rectify that tonight or tomorrow. For now, immediate future goals will be parsing selectors better so you can reference components and adding caching mechanisms for parsing and compiling.