radiant 0.9.0.rc2 → 0.9.1

data/config/initializers/pagination.rb

@@ -1 +0,0 @@
-WillPaginate::ViewHelpers.pagination_options[:param_name] = :p

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/default.css

@@ -1,293 +0,0 @@
-* { margin:0; padding:0; }
-body, div, span, p, a, img, ul, ol, li, table, th, tr, td, form, fieldset, legend, dl, dt, dd, blockquote, applet, object { border:0; }
-body {
-    padding: 0;
-    background: #fff url("img/bg.jpg") repeat-x;
-    font: 0.8em/1.5 "arial",sans-serif;
-    color: #354146;
-    text-align: center;
-}
-
-/* links --------------------------------------------------------------- */
-a {color:#1666a3;}
-a:link {color:#1666a3;}
-a:hover {color:#0b4775;}
-
-/* header tags --------------------------------------------------------------------- */
-h1, h2, h3, h4, h5, h6 { margin:15px 0 10px 0; }
-h1 { font-size:200%; font-family: Georgia;}
-h1#logo a{color: #ced1d2; text-decoration: none; display: block;padding: 18px 0 17px; font-weight: normal;}
-h1#logo a:hover{color: #fff;}
-h1#logo span.slogan {font-size: 60%; padding-left: 1.5em;}
-h2 { font-size:130%; color: #354146;font-weight: bold; padding: 0; }
-h3 { font-size:120%; }
-h4 { font-size:120%; }
-h5 { font-size:100%; }
-
-/* layout ---------------------------------------------------------------------- */
-#layout {
-    text-align:left;
-}
-#container {
-    clear: both;
-}
-#intro{
-    background: #e6e8e9; height: auto;
-}
-#intro-in{
-    width:891px;
-    margin: 0 auto;
-    padding: 20px 0;
-}
-
-#header {
-    width:891px;
-    margin:0 auto;
-}
-
-
-/* horizontal navigation --------------------------------------------------- */
-#nav {
-    width:891px;
-    margin:0 auto;
-}
-#nav ul {
-    margin:0;
-    padding:0;
-    list-style:none;
-    height: 35px;
-}
-#nav ul li {
-    float:left;
-    display:block;
-    margin:0;
-    padding:0;}
-#nav ul li a, #nav ul li span {
-    display: block;
-    float: left;
-    font-size: 90%;
-    color: #fff;
-    text-decoration: none;
-    padding: 12px 20px 8px;
-    text-align: center;
-}
-#nav ul li a:hover, #nav ul li span:hover {
-    color: #ced1d2;
-    text-decoration: underline;
-}
-#nav ul li#active a, #nav ul li.webgen-menu-item-selected span {
-    color: #101517;
-    border: 1px solid #fff;
-    border-bottom:1px solid #e6e8e9;
-    background:#e6e8e9; text-decoration:none;}
-
-/* main content ---------------------------------------------------------------- */
-
-.content {
-    padding: 0 0 0 0;
-    z-index: 10;
-    width:891px;
-    margin:0 auto;
-}
-.content .in{
-    padding: 20px 0 30px;
-}
-p.intro{
-    background: url("img/line.jpg");
-    line-height: 23px;
-    margin:0 0 0;
-}
-.shadow{
-    border-top: 1px solid #dddddd;
-    padding: 10px 0;
-    background: url("img/shadow.jpg") no-repeat;
-}
-
-img.thumb{padding: 3px; background: #fff; border: 1px solid #d1d1d1;}
-
-.columns {list-style: none;margin:10px 0 0 0;padding:0; font-size: 90%;}
-.columns li{float: left; width: 32%;}
-.columns li.col2{border-left: 1px solid #d7d7d7;border-right: 1px solid #d7d7d7;}
-.columns li h3{padding: 0 10px;color: #2e4650; margin: 0 0 5px;}
-.columns li.col2 h3{padding-left: 20px;}
-.columns li.col3 h3{padding-left: 20px;}
-.columns li p{line-height: 22px;padding: 0 20px 0 10px; margin: 0; color: #3f4345;}
-.columns li.col2 p{padding: 0 20px 0 20px;}
-.columns li.col3 p{padding: 0 10px 0 20px;}
-.columns li a.more{display: block;color: #1666a3;padding: 5px 0;}
-.columns li a.more:hover{color: #0b4775; text-decoration: none;}
-
-
-
-/* footer ----------------------------------------------------------------- */
-#footer {
-    width:891px;
-    margin:0 auto;
-    clear:both;
-    font-size: 85%;
-    padding-bottom: 70px;
-    color: #898989;
-}
-#footer a{color: #898989;}
-#footer a:hover{color: #666666; text-decoration: none;}
-#footer .f-left, #footer .f-right { padding: 0 10px; }
-
-
-
-
-/* paragraphs -------------------------------------------------------------------- */
-p { margin:15px 0; }
-
-/* tables --------------------------------------------------------------------- */
-table { margin:15px 0; border-collapse:collapse; border-spacing:0; font-size:100%; }
-th { text-align:center; font-weight:bold; }
-th, td { padding:3px 5px; }
-
-/* lists --------------------------------------------------------------------- */
-ul, ol { display:block; margin:15px 0 15px 40px; }
-ul ul, ul ul ul, ol ol, ol ol ol { margin:0; margin-left:20px; }
-ol { list-style-type:decimal; }
-ol ol { list-style-type:upper-alpha; }
-ol ol ol {list-style-type:lower-alpha; }
-li { display:list-item; }
-ul li a { text-decoration:underline; }
-
-/* definitions -------------------------------------------------------------------- */
-dl { margin:15px 0; }
-dt { font-weight:bold; }
-dd { margin-left:30px; }
-
-/* other HTML tags --------------------------------------------------------------------- */
-fieldset { margin:15px 0; padding:10px; border:1px solid #CCC; }
-legend { margin-left:10px; font-size:100%; font-weight:bold; color:#000; }
-abbr, acronym, .help { border-bottom:1px dotted #CCC; cursor:help; }
-blockquote { margin:15px 20px; font-style:italic; }
-del, .del { text-decoration:line-through; }
-strong, .strong { font-weight:bold; }
-cite, em, q, var { font-style:italic; }
-code, kbd, samp  {font-family:monospace; font-size:110%; }
-hr { display:block; height:1px; margin:10px 0; padding:0; border:0 solid #CCC; background:#CCC; color:#CCC;}
-.f-left {float:left;}
-.f-right {float:right;}
-.a-left, tr.a-left td {text-align:left;}
-.a-center, tr.a-center td {text-align:center;}
-.a-right, tr.a-right td {text-align:right;}
-.a-justify {text-align:justify;}
-.va-top {vertical-align:top;}
-.va-middle {vertical-align:middle;}
-.va-bottom {vertical-align:bottom;}
-.clear { clear:both; }
-.box { min-height:1px; }
-.box:after { display:block; visibility:hidden; clear:both; line-height:0; font-size:0; content:"."; }
-.noscreen { display:none; }
-.mleft10 { margin-left: 10px; }
-.mright10 { margin-right: 10px; }
-.mtop10 { margin-top: 10px; }
-.mbottom10 { margin-bottom: 10px; }
-
-
-
-input.small{
-    width: 50px;
-}
-input.normal{
-    width: 146px;
-}
-.bigger {font-size:115%;}
-.smaller {font-size:85%;}
-
-.high {color:#00F;}
-.nonhigh {color:#777;}
-
-.foto{  display: block; border: 3px solid #ddd;}
-
-
-/* added definitions ------------------------------------------------------------ */
-.news-item + .news-item {
-    border-top: 1px solid #dddddd;
-}
-.news-date {
-    margin-top: 5px;
-}
-
-pre {
-    margin: 15px 10px;
-    background-color: #e6e8e9;
-    color: #000;
-}
-
-pre.show-whitespaces .ws-space {
-    background-color: #f44;
-}
-pre.show-whitespaces .ws-space-l {
-    background-color: #f22;
-}
-pre.show-whitespaces .ws-space-r {
-    background-color: #f00;
-}
-
-pre.show-whitespaces .ws-tab {
-    background-color: #ff4;
-}
-pre.show-whitespaces .ws-tab-l {
-    background-color: #ff2;
-}
-pre.show-whitespaces .ws-tab-r {
-    background-color: #ff0;
-}
-
-pre.show-whitespaces.ws-lr .ws-tab {
-    background-color: inherit;
-}
-pre.show-whitespaces.ws-lr .ws-space {
-    background-color: inherit;
-    opacity: 0;
-}
-
-blockquote.markdown-difference {
-    margin: 15px 20px;
-    padding: 5px;
-    border: 2px solid #e6e8e9;
-    background-color: #ffffee
-}
-
-blockquote.markdown-difference:before {
-    content: "Difference to Standard Markdown";
-    display: block;
-    font-weight: bold;
-    margin-top: 5px
-}
-
-pre.kdexample-before {
-    width: 45%;
-    float: left;
-}
-
-pre.kdexample-after-source {
-    width: 45%;
-    float: right;
-    background-color: #ffffee;
-    border: 2px solid #e6e8e9;
-    margin-bottom: 3px;
-}
-
-div.kdexample-after-live {
-    width: 45%;
-    float: right;
-    clear: right;
-    background-color: #eeffee;
-    border: 2px solid #e6e8e9;
-    margin: 0px 10px;
-}
-
-div.kdsyntaxlink {
-    float: right;
-    padding: 5px;
-    border: 1px solid #e6e8e9;
-    margin-right: 10px;
-    margin-left: 10px;
-}
-
-div.kdsyntaxlink a {
-    text-decoration: none;
-}

data/vendor/plugins/haml/FAQ

@@ -1,138 +0,0 @@
-= Frequently Asked Questions
-
-== Haml
-
-=== How do I put a punctuation mark after an element, like "<tt>I like <strong>cake</strong>!</tt>"?
-
-Expressing the structure of a document
-and expressing inline formatting are two very different problems.
-Haml is mostly designed for structure,
-so the best way to deal with formatting is to leave it to other languages
-that are designed for it.
-You could use Textile:
-
-  %p
-    :textile
-      I like *cake*!
-
-or Markdown:
-
-  %p
-    :markdown
-      I like **cake**!
-
-or plain old XHTML:
-
-  %p I like <strong>cake</strong>!
-
-If you're inserting something that's generated by a helper, like a link,
-then it's even easier:
-
-  %p== I like #{link_to 'chocolate', 'http://franschocolates.com'}!
-
-=== How do I stop Haml from indenting the contents of my +pre+ and +textarea+ tags?
-
-Because Haml automatically indents the HTML source code,
-the contents of whitespace-sensitive tags like +pre+ and +textarea+
-can get screwed up.
-The solution is to replace the newlines inside these tags
-with HTML newline entities (<tt>&#x000A;</tt>),
-which Haml does using the Haml::Helpers#preserve and Haml::Helpers#find_and_preserve helpers.
-
-Normally, Haml will do this for you automatically
-when you're using a tag that needs it
-(this can be customized using the <tt>:preserve</tt> option;
-see the Options section of the {Haml reference}(../classes/Haml.html)).
-For example,
-
-  %p
-    %textarea= "Foo\nBar"
-
-will be compiled to
-
-  <p>
-    <textarea>Foo&#x000A;Bar</textarea>
-  </p>
-
-However, if a helper is generating the tag,
-Haml can't detect that and so you'll have to call +find_and_preserve+ yourself.
-You can also use <tt>~</tt>, which is the same as <tt>=</tt>
-except that it automatically runs +find_and_preserve+ on its input.
-For example:
-
-  %p= find_and_preserve "<textarea>Foo\nBar</textarea>"
-
-is the same as
-
-  %p~ "<textarea>Foo\nBar</textarea>"
-
-and renders
-
-  <p><textarea>Foo&#x000A;Bar</textarea></p>
-
-=== How do I make my long lines of Ruby code look nicer in my Haml document?
-
-Put them in a helper or your model.
-
-Haml purposefully makes it annoying to put lots of Ruby code into your templates,
-because lots of code doesn't belong in the view.
-If you take that huge +link_to_remote+ call
-and move it to a +update_sidebar_link+ helper,
-it'll make your view both easier to read and more semantic.
-
-If you absolutely must put lots of code in your template,
-Haml offers a somewhat awkward multiline-continuation tool.
-Put a <tt>|</tt> (pipe character) at the end of each line you want to be merged into one
-(including the last line!).
-For example:
-
-  %p= @this.is(way.too.much). |
-      code("and I should").   |
-      really_move.it.into(    |
-        :a => @helper)        |
-
-=== I have Haml installed. Why is Rails (only looking for <tt>.html.erb</tt> files | rendering Haml files as plain text | rendering Haml files as blank pages)?
-
-There are several reasons these things might be happening.
-First of all, make sure vendor/plugins/haml really exists
-and has an init.rb file in there.
-Then try restarting Mongrel or WEBrick or whatever you might be using.
-
-Finally, if none of these work,
-chances are you've got some localization plugin like Globalize installed.
-Such plugins often don't play nicely with Haml.
-Luckily, there's usually an easy fix.
-For Globalize, just edit globalize/lib/globalize/rails/action_view.rb
-and change
-
-  @@re_extension = /\.(rjs|rhtml|rxml)$/
-
-to
-
-  @@re_extension = /\.(rjs|rhtml|rxml|erb|builder|haml)$/
-
-For other plugins, a little searching will probably turn up a way to fix them as well.
-
-== Sass
-
-=== Can I use a variable from my controller in my Sass file?
-
-No. Sass files aren't views.
-They're compiled once into static CSS files,
-then left along until they're changed and need to be compiled again.
-Not only don't you want to be running a full request cycle
-every time someone requests a stylesheet,
-but it's not a great idea to put much logic in there anyway
-due to how browsers handle them.
-
-If you really need some sort of dynamic CSS,
-the best thing to do is put only the snippet you need to dynamically set
-in the +head+ of your HTML document.
-
-== You still haven't answered my question!
-
-Sorry! Try looking at the Haml or Sass references,
-in the doucmentation for the haml and Sass modules, respectively.
-If you can't find an answer there,
-feel free to ask in #haml on irc.freenode.net
-or send an email to the {mailing list}[http://groups.google.com/group/haml?hl=en].

data/vendor/plugins/haml/README.rdoc

@@ -1,319 +0,0 @@
-= Haml and Sass
-
-Haml and Sass are templating engines
-for the two most common types of documents on the web:
-HTML and CSS, respectively.
-They are designed to make it both easier and more pleasant
-to code HTML and CSS documents,
-by eliminating redundancy,
-reflecting the underlying structure that the document represents,
-and providing elegant, easily understandable, and powerful syntax.
-
-== Using
-
-There are several ways to use Haml and Sass.
-They can be used as a plugin for Rails or Merb,
-or embedded on their own in other applications.
-The first step of all of these is to install the Haml gem:
-
-  gem install haml
-
-To install Haml and Sass as a Rails plugin,
-just run <tt>haml --rails path/to/rails/app</tt>
-and both Haml and Sass will be installed.
-Views with the <tt>.haml</tt> (or <tt>.html.haml</tt> for edge)
-extension will automatically use Haml.
-Sass is a little more complicated;
-<tt>.sass</tt> files should be placed in public/stylesheets/sass,
-where they'll be automatically compiled
-to corresponding CSS files in public/stylesheets when needed
-(the Sass template directory is customizable...
-see the Sass module docs for details).
-
-For Merb, <tt>.html.haml</tt> views will work without any further modification.
-To enable Sass, you also need to add a dependency.
-To do so, just add
-
-  dependency "merb-haml"
-
-to config/dependencies.rb (or config/init.rb in a flat/very flat Merb application).
-Then it'll work just like it does in Rails.
-
-To use Haml and Sass programatically,
-check out the RDocs for the Haml and Sass modules.
-
-== Formatting
-
-=== Haml
-
-The most basic element of Haml
-is a shorthand for creating HTML tags:
-
-  %tagname{ :attr1 => 'value1', :attr2 => 'value2' } Contents
-
-No end-tag is needed; Haml handles that automatically.
-Adding <tt>class</tt> and <tt>id</tt> attributes is even easier.
-Haml uses the same syntax as the CSS that styles the document:
-
-  %tagname#id.class
-
-In fact, when you're using the <tt><div></tt> tag,
-it becomes <em>even easier</em>.
-Because <tt><div></tt> is such a common element,
-a tag without a name defaults to a div. So
-
-  #foo Hello!
-
-becomes
-
-  <div id='foo'>Hello!</div>
-
-Haml uses indentation
-to bring the individual elements to represent the HTML structure.
-A tag's children are indented two spaces more than the parent tag.
-Again, a closing tag is automatically added.
-For example:
-
-  %ul
-    %li Salt
-    %li Pepper
-
-becomes:
-
-  <ul>
-    <li>Salt</li>
-    <li>Pepper</li>
-  </ul>
-
-You can also put plain text as a child of an element:
-
-  %p
-    Hello,
-    World!
-
-It's even possible to embed Ruby code into Haml documents.
-An equals sign, <tt>=</tt>, will output the result of the code.
-A hyphen, <tt>-</tt>, will run the code but not output the result.
-You can even use control statements
-like <tt>if</tt> and <tt>while</tt>:
-
-  %p
-    Date/Time:
-    - now = DateTime.now
-    %strong= now
-    - if now > DateTime.parse("December 31, 2006")
-      = "Happy new " + "year!"
-
-Haml provides far more tools than those presented here.
-Check out the reference documentation in the Haml module.
-
-=== Sass
-
-At its most basic,
-Sass is just another way of writing CSS.
-Although it's very much like normal CSS,
-the basic syntax offers a few helpful features:
-tabulation (using *two spaces*)
-indicates the attributes in a rule,
-rather than non-DRY brackets;
-and newlines indicate the end of an attribute,
-rather than a semicolon.
-For example:
-
-  #main
-    :background-color #f00
-    :width 98%
-
-becomes:
-
-  #main {
-    background-color: #f00;
-    width: 98% }
-
-However, Sass provides much more than a way to make CSS look nice.
-In CSS, it's important to have accurate selectors,
-so your styles don't just apply to everything.
-However, in order to do this,
-you need to use nested element selectors.
-These get very ugly very quickly.
-I'm sure everyone's had to write something like
-"#main .sidebar .top p h1 a",
-followed by
-"#main .sidebar .top p h1 a:visited" and
-"#main .sidebar .top p h1 a:hover".
-Well, Sass gets rid of that.
-Like Haml, it uses indentation to indicate the structure of the document.
-So, what was:
-
-  #main {
-    width: 90%;
-  }
-  #main p {
-    border-style: solid;
-    border-width: 1px;
-    border-color: #00f;
-  }
-  #main p a {
-    text-decoration: none;
-    font-weight: bold;
-  }
-  #main p a:hover {
-    text-decoration: underline;
-  }
-
-becomes:
-
-  #main
-    :width 90%
-    p
-      :border-style solid
-      :border-width 1px
-      :border-color #00f
-      a
-        :text-decoration none
-        :font-weight bold
-      a:hover
-        :text-decoration underline
-
-Pretty nice, no? Well, it gets better.
-One of the main complaints against CSS is that it doesn't allow constants.
-What if have a color or a width you re-use all the time?
-In CSS, you just have to re-type it each time,
-which is a nightmare when you decide to change it later.
-Not so for Sass!
-You can use the "!" character to set constants.
-Then, if you put "=" after your attribute name,
-you can set it to a constant.
-For example:
-
-  !note_bg= #55aaff
-
-  #main
-    :width 70%
-    .note
-      :background-color= !note_bg
-    p
-      :width 5em
-      :background-color= !note_bg
-
-becomes:
-
-  #main {
-    width: 70%; }
-    #main .note {
-      background-color: #55aaff; }
-    #main p {
-      width: 5em;
-      background-color: #55aaff; }
-
-You can even do simple arithmetic operations with constants,
-adding numbers and even colors together:
-
-  !main_bg= #46ar12
-  !main_width= 40em
-
-  #main
-    :background-color= !main_bg
-    :width= !main_width
-    .sidebar
-      :background-color= !main_bg + #333333
-      :width= !main_width - 25em
-
-becomes:
-
-  #main {
-    background-color: #46a312;
-    width: 40em; }
-    #main .sidebar {
-      background-color: #79d645;
-      width: 15em; }
-
-Taking the idea of constants a bit further are mixins.
-These let you group whole swathes of CSS attributes into a single
-directive and then include those anywhere you want:
-
-  =blue-border
-    :border
-      :color blue
-      :width 2px
-      :style dotted
-
-  .comment
-    +blue-border
-    :padding 2px
-    :margin 10px 0
-
-  .reply
-    +blue-border
-
-becomes:
-
-  .comment {
-    border-color: blue;
-    border-width: 2px;
-    border-style: dotted;
-    padding: 2px;
-    margin: 10px 0;
-  }
-
-  .reply {
-    border-color: blue;
-    border-width: 2px;
-    border-style: dotted;
-  }
-
-A comprehensive list of features is in
-the documentation for the Sass module.
-
-== Executables
-
-The Haml gem includes several executables that are useful
-for dealing with Haml and Sass from the command line.
-
-=== +haml+
-
-The +haml+ executable transforms a source Haml file into HTML.
-See <tt>haml --help</tt> for further information and options.
-
-=== +sass+
-
-The +sass+ executable transforms a source Sass file into CSS.
-See <tt>sass --help</tt> for further information and options.
-
-=== <tt>html2haml</tt>
-
-The <tt>html2haml</tt> executable attempts to transform HTML,
-optionally with ERB markup, into Haml code.
-Since HTML is so variable, this transformation is not always perfect;
-it's a good idea to have a human check the output of this tool.
-See <tt>html2haml --help</tt> for further information and options.
-
-=== <tt>css2sass</tt>
-
-The <tt>css2sass</tt> executable attempts to transform CSS into Sass code.
-This transformation attempts to use Sass nesting where possible.
-See <tt>css2sass --help</tt> for further information and options.
-
-== Authors
-
-Haml and Sass are designed by Hampton Catlin (hcatlin) and he is the author
-of the original implementation. However, Hampton doesn't even know his way
-around the code anymore and mostly just concentrates on the language issues.
-Hampton lives in Toronto, Ontario (though he's an American by birth) and
-is a partner at Unspace Interactive.
-
-Nathan Weizenbaum is the primary maintainer and architect of the "modern" Ruby
-implementation of Haml. His hard work has kept the project alive by endlessly
-answering forum posts, fixing bugs, refactoring, finding speed improvements,
-writing documentation, implementing new features, and getting Hampton
-coffee (a fitting task for a boy-genius). Nathan lives in Seattle, Washington and
-while not being a student at University of Washington he consults for
-Unspace Interactive and Microsoft.
-
-If you use this software, you must pay Hampton a compliment. And
-buy Nathan some jelly beans. Maybe pet a kitten. Yeah. Pet that kitty.
-
-Some of the work on Haml was supported by Unspace Interactive.
-
-Beyond that, the implementation is licensed under the MIT License.
-Ok, fine, I guess that means compliments aren't *required*.