modular

Simple (I hope), HTML question. Let's say I have a column group that spans 3 columns. But it also spans 9 rows. But in actuality, I want there to be 3 levels of columns (so basically, 3 columns, split across 9 rows). The only objectives really are: a) avoid embedding tables (for various reasons) b) keep the sections modular. c) allow for styling of the semantically modular areas. So in the end, I would have something visually like: | col 1 | col 2 | col 3 | | row 1 | row 1 | row 1 | | row 2 | row 2 | row 2 | | row 3 | row 3 | row 3 | | col 4 | col 5 | col 6 | | row 4 | row 4 | row 4 | | row 5

require 'sinatra/base' class Foo < Sinatra::Base get('/foo') { 'foo' } end class Bar < Sinatra::Base get('/bar') { 'bar' } end run Rack::Cascade, [Foo, Bar] I just can't guess what is wrong with this code. When I ran: ruby server.rb, it throws an error First of all, the last line should read run Rack::Cascade.new [Foo, Bar] But you can only use this in a Rackup File. So second, you need to create a File called config.ru (Rackup File) with the following contents: require './app' run Rack::Cascade.new [Foo, Bar] and a file called app.rb with your actual app: require 'sinatra/base' class Foo <

How do you manage dummy data used for tests? Keep them with their respective entities? In a separate test project? Load them with a Serializer from external resources? Or just recreate them wherever needed? We have an application stack with several modules depending on another with each containing entities. Each module has its own tests and needs dummy data to run with. Now a module that has a lot of dependencies will need a lot of dummy data from the other modules. Those however do not publish their dummy objects because they are part of the test resources so all modules have to setup all

I'm currently part of team building a Windows 8 application using JavaScript. We are using npm and browserify to manage dependencies and convert our modules to AMD browser friendly format. One issue we are running into is crazy require paths. This is because we have a top level folder inside our application "components". This folder contains a bunch of nested ui components/modules. These modules sometimes require lib utils and helpers, which reside in the lib directory. So for example, a module living in "my/app/components/product/grid/item" might require a helper module which is located "my