vasil

module Sinatra

  #class TemplateNotFound < Sinatra::NotFound
  class TemplateNotFound < Sinatra::ShowExceptions
  end

  module Partials
    # Render a partial template. [Adapted from Merb]
    #
    # ==== Parameters

vasil

gem "rack",          "1.1.0"
gem "rack-mount",    "~> 0.4.0" # :git => "git://github.com/rails/rack-mount.git"
gem "rack-test",     "~> 0.5.0"                                                  
gem "erubis",        "~> 2.6.0"                                                  
gem "arel",          :git => "git://github.com/rails/arel.git"                   
gem "sqlite3-ruby"                                                               
gem "rails", "3.0.pre", :git => "git://github.com/rails/rails.git"

vasil

directory "/rails", :glob => "{*/,}*.gemspec"

git "git://github.com/rails/rack.git"
git "git://github.com/rails/arel.git"

vasil

velija@a1:~$ history | tail -1
 1733  sudo iptables -A INPUT -p tcp -m tcp --destination-port 22 -j ACCEPT

vasil

MOD_PYTHON ERROR

ProcessId:      28841
Interpreter:    'time.mk'

ServerName:     'time.mk'
DocumentRoot:   '/home/mkrobot/www/www.time.mk/'

URI:            '/www.time.mk/index.psp'
Location:       None

vasil

cd /tmp
git clone git://github.com/GM-Script-Writer-62850/Ubuntu-Mainline-Kernel-Updater
bash Ubuntu-Mainline-Kernel-Updater/install
KernelUpdateChecker -no-rc
/tmp/kernel-update

vasil

        \                           /
         \                         /
          \                       /
           ]                     [    ,'|
           ]                     [   /  |
           ]___               ___[ ,'   |
           ]  ]\             /[  [ |:   |
           ]  ] \           / [  [ |:   |
           ]  ]  ]         [  [  [ |:   |

vasil

New features and changes workflow guide

This guide describes what steps usually work best when adding new features to a product. The guidelines are not mandatory; simpler features may not need any of these steps. They exist to help battle the hardest new features to add :)

The steps are not necessarily in the correct order - this is the usual order. Going back to an older step to add/change things is okay.

Brainstorming sessions

Goal: collect all that we can come up with for the new feature or change. Everything goes into an unorganized document (wiki page). Possible ways to organize this document is into proposal items (and proposal detail item for each proposal item).

vasil

import signal
def  int_handler(signal, frame):
        import pdb
        pdb.set_trace(frame)
signal.signal(signal.SIGINT, int_handler)

vasil

<link rel="import" href="../core-ajax/core-ajax.html">
<link rel="import" href="../core-pages/core-pages.html">
<link rel="import" href="../topeka-elements/theme.html">
<link rel="import" href="../topeka-elements/topeka-resources.html">
<link rel="import" href="../topeka-elements/topeka-app.html">

<polymer-element name="my-element">

  <template>
    <style>