Steps to install SPREE

Leave a comment

## Ubuntu 10.04.1 LTS spree commerce setup rails 3.0.9 + ruby 1.9.2

cat /etc/issue
Ubuntu 10.04.1 LTS \n \l

## Install ruby for rvm
# aptitude install curl git-core ruby
The following NEW packages will be installed:
libruby1.8{a} ruby ruby1.8{a}

# ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]

# bash < <( curl )

## edit the .bashrc with lines:

# Replace:
#[ -z “$PS1” ] && return
# With:
if [[ -n “$PS1” ]]; then
if [[ -s $HOME/.rvm/scripts/rvm ]] ; then source $HOME/.rvm/scripts/rvm ; fi


# source ~/.bashrc

## export UTF8 lang

# export LANG=en_US.UTF-8

## Install necessary libs and tools

# aptitude install build-essential bison openssl libreadline5 libreadline-dev curl git-core zlib1g zlib1g-dev libssl-dev vim libsqlite3-0 libsqlite3-dev sqlite3 libreadline-dev libxml2-dev git-core subversion autoconf imagemagick libmagickcore-dev libmagickwand-dev

## Install ruby 1.9.2
# rvm install 1.9.2-head

## Set ruby 1.9.2 default
# rvm –default 1.9.2-head
# ruby -v
ruby 1.9.2p290 (2011-07-09 revision 32478) [x86_64-linux]

## Install rails 3.0.9
# gem -v
# gem install rails

## Install spree
# gem install spree

## Install bundler
# gem install bundler

## Create new store
# rails new mystore

## Edit Gemfile
source ‘

gem ‘rails’, ‘3.0.9’

# Bundle edge Rails instead:
# gem ‘rails’, :git => ‘git://’

gem ‘builder’
gem ‘activemerchant’
gem ‘mysql2’, ‘<0.3’
gem ‘aws-s3’, :require => ‘aws/s3’
gem ‘dynamic_form’
gem ‘heroku’
gem ‘memcache-client’
gem ‘rmagick’
gem ‘jrails’
gem ‘jquery-rails’
# Spree extensions
gem ‘spree’, ‘0.60.1’
# Followed by spree itself first, all spree-specific extensions second
gem ‘spree_active_shipping’, :git => ‘git://’
gem ‘spree_product_assembly’, :git => ‘git://’
gem ‘spree_static_content’, :git => ‘git://’

# Dev/Test gems
group :development, :test do
gem ‘sqlite3’
gem ‘webrat’
gem ‘cucumber-rails’
gem ‘rspec-rails’

## Run bundle install
# bundle install

## Initialize database
# rake db:create
rake aborted!
uninitialized constant Deface

(See full trace by running task with –trace)

## Running with trace shows:
# rake db:create –trace
uninitialized constant Deface
/usr/local/rvm/gems/ruby-1.9.2-head/bundler/gems/spree-product-assembly-5a150731393a/lib/spree_product_assembly_hooks.rb:1:in `<top (required)>’
/usr/local/rvm/gems/ruby-1.9.2-head/bundler/gems/spree-product-assembly-5a150731393a/lib/spree_product_assembly.rb:2:in `<top (required)>’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:68:in `require’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:68:in `block (2 levels) in require’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:66:in `each’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:66:in `block in require’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:55:in `each’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:55:in `require’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler.rb:120:in `require’
/var/www/cutedress/config/application.rb:7:in `<top (required)>’
/usr/local/rvm/rubies/ruby-1.9.2-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require’
/usr/local/rvm/rubies/ruby-1.9.2-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require’
/var/www/cutedress/Rakefile:4:in `<top (required)>’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/rake_module.rb:25:in `load’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/rake_module.rb:25:in `load_rakefile’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:495:in `raw_load_rakefile’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:78:in `block in load_rakefile’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:77:in `load_rakefile’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:61:in `block in run’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/lib/rake/application.rb:59:in `run’
/usr/local/rvm/gems/ruby-1.9.2-head/gems/rake-0.9.2/bin/rake:32:in `<top (required)>’
/usr/local/rvm/gems/ruby-1.9.2-head/bin/rake:19:in `load’
/usr/local/rvm/gems/ruby-1.9.2-head/bin/rake:19:in `<main>’

## Running rails g spree:site shows same error
#rails g spree:site
/usr/local/rvm/gems/ruby-1.9.2-head/bundler/gems/spree-product-assembly-5a150731393a/lib/spree_product_assembly_hooks.rb:1:in `<top (required)>’: uninitialized constant Deface (NameError)
from /usr/local/rvm/gems/ruby-1.9.2-head/bundler/gems/spree-product-assembly-5a150731393a/lib/spree_product_assembly.rb:2:in `<top (required)>’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:68:in `require’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:68:in `block (2 levels) in require’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:66:in `each’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:66:in `block in require’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:55:in `each’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler/runtime.rb:55:in `require’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.15/lib/bundler.rb:120:in `require’
from /var/www/cutedress/config/application.rb:7:in `<top (required)>’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/railties-3.0.9/lib/rails/commands.rb:15:in `require’
from /usr/local/rvm/gems/ruby-1.9.2-head/gems/railties-3.0.9/lib/rails/commands.rb:15:in `<top (required)>’
from script/rails:6:in `require’
from script/rails:6:in `<main>’

## Full gemlist

*** LOCAL GEMS ***

abstract (1.0.0)
actionmailer (3.0.9)
actionpack (3.0.9)
active_shipping (0.9.13)
activemerchant (1.15.0)
activemodel (3.0.9)
activerecord (3.0.9)
activeresource (3.0.9)
activesupport (3.0.9)
acts_as_list (0.1.2)
addressable (2.2.6)
arel (2.0.10)
aws-s3 (0.6.2)
bcrypt-ruby (2.1.4)
braintree (2.10.1)
builder (2.1.2)
bundler (1.0.15)
cancan (1.6.4)
capybara (1.0.0)
childprocess (0.2.0)
cocaine (0.1.0)
cucumber (1.0.2)
cucumber-rails (1.0.2)
devise (1.3.3)
diff-lcs (1.1.2)
dynamic_form (1.1.4)
erubis (2.6.6)
faker (0.9.5)
ffi (1.0.9)
formtastic (1.2.4)
gherkin (2.4.5)
heroku (2.4.0)
highline (1.5.1)
i18n (0.5.0)
jquery-rails (0.2.6)
jrails (0.6.0)
json (1.5.3)
json_pure (1.5.3)
launchy (2.0.5)
mail (2.2.19)
memcache-client (1.8.5)
meta_search (1.0.5)
mime-types (1.16)
mysql (2.8.1)
mysql2 (0.2.11)
nested_set (1.6.6)
nokogiri (1.5.0)
orm_adapter (0.0.5)
paperclip (2.3.16, 2.3.11)
polyglot (0.3.2)
rack (1.2.3)
rack-mount (0.6.14)
rack-test (0.5.7)
rails (3.0.9)
railties (3.0.9)
rake (0.9.2, 0.8.7 ruby)
rd_find_by_param (0.1.1)
rd_resource_controller (1.0.1)
rd_unobtrusive_date_picker (0.1.0)
rdoc (3.8)
rest-client (1.6.3)
rmagick (2.13.1)
rspec (2.6.0)
rspec-core (2.6.4)
rspec-expectations (2.6.0)
rspec-mocks (2.6.0)
rspec-rails (2.6.1)
rubyzip (0.9.4)
selenium-webdriver (0.2.2)
spree (0.60.1)
spree_api (0.60.1)
spree_auth (0.60.1)
spree_core (0.60.1)
spree_dash (0.60.1)
spree_editor (0.50.1)
spree_promo (0.60.1)
spree_sample (0.60.1)
sqlite3 (1.3.4)
state_machine (0.9.4)
stringex (1.0.3)
term-ansicolor (1.0.6)
thor (0.14.6)
treetop (1.4.10)
tzinfo (0.3.29)
warden (1.0.5)
webrat (0.7.3)
will_paginate (3.0.pre2)
xml-simple (1.1.0)
xpath (0.1.4)


online CSS Gradient Generator

Leave a comment

Ultimate CSS Gradient Generator

A powerful Photoshop-like CSS gradient editor from ColorZilla.

Why Google May Fail

Leave a comment


Staffing: Exacerbating the Problem


In talking to the OEMs, one of their biggest complaints was that the people they interface with are rude, unprofessional, inexperienced, clueless and generally unable to successfully resolve issues in a timely manner. The level of frustration with some of the OEMs is incredibly high.When confronted with this problem, Google’s common response has been that they simply can’t find qualified people, which is kind of amazing given the level of unemployment that exists in the world.This suggests that Google’s hiring policy is at fault; the company is known to favor recent graduates who will start at low salaries but have high GPAs, instead of more experienced employees. This exacerbates the quality problems significantly because it means these problems aren’t being properly communicated, escalated or resolved. In fact, in talking to the OEMs, you get a sense that much of the team that Google has working on operating systems are actually learning on the job. It kind of makes it even more amazing that they got a product out that works as well as it does.

via Why Google Android May Fail and Chrome OS Will Fail –


the old adage applies — “You get what you pay for…”


QJson – Home

Leave a comment

QJson – Home.


the easiest way to manage JSON objects with Qt

JSON (JavaScript Object Notation) is a lightweight data-interchange format. It can represents integer, real number, string, an ordered sequence of value, and a collection of name/value pairs.

QJson is a qt-based library that maps JSON data to QVariant objects: JSON arrays will be mapped to QVariantList instances, while JSON objects will be mapped to QVariantMap.

Easy to use

QJson is fast and reliable. Don’t waste your time writing another JSON parser!

Converting a JSON object to a QVariant requires just three lines of code:

1 // create a JSonDriver instance
2 QJson::Parser parser;
3 bool ok;
5 // json is a QString containing the data to convert
6 QVariant result = parser.parse (json, &ok);

It’s also possible to convert QVariant instances to JSON objects:

1 // create a Serializer instance
2 QJson::Serializer serializer;
3 const QByteArray serialized = serializer.serialize( json_object );

It’s possible to serialize QObject instances into JSON and also to initialize a QObject using the values stored inside of a JSON object.

Check out the usage section for more code snippets.