www_app 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: a2d329bf631e2d3ca2386b433a8b552d25896eda
+  data.tar.gz: 36ec7a7fb8580ce6bd15071da27ca9197f63217f
+SHA512:
+  metadata.gz: 50e3e9dbf94a9c28487c468719e936047f9719ce9f7a620bb719d6d35b188c9c87b79d6cdebf5ad01b2ff2520ee4b96600d5ecb574aa960df8940f46b32c80de
+  data.tar.gz: 110c46539691d9259483f85c4273af8b67c98dfd4b6c7f7550f8bb58cc5fd141237125d59519fd58e8228bd828bd5968d1e40ac6c7a33bbcbf2b5defedec6022

data/.gitignore

@@ -0,0 +1,36 @@
+/node_modules/
+/npm-debug.log
+/lib/vendor/*
+/.bundle
+/.yardoc
+/*.gem
+/*.rbc
+/*.gem
+/*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+## Specific to RubyMotion:
+
+
+## Environment normalisation:
+/.bundle/
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+/Gemfile.lock
+/.ruby-version
+/.ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+/node_modules/
+/npm-debug.log
+/lib/vendor/*

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2013-2014 da99
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,84 @@
+
+
+WWW\_App:
+---------
+
+Create HTML pages using just Ruby: HTML/CSS/JS.
+It's not done yet.
+
+
+Ruby:
+--------------
+
+To install:
+
+```ruby
+  gem install www_app
+```
+
+To Use:
+
+```ruby
+div {
+
+  border           '1px solid #000'
+  background_color 'grey'
+
+  on('scary') {
+    border           '2px dotted red'
+    background_color 'white'
+  }
+
+  p { 'Click the button to make me scared.' }
+
+  button {
+    parent 'div'
+    add_class 'scary'
+
+    'Scary-ify'
+  }
+
+}
+```
+
+It generates the CSS, JS, and HTML.
+
+Security:
+-----------
+
+1) Server-side: All data from user should be run through `:render` to
+ensure sanitization/escaping.
+
+2) Server-side: All JS meant for :script tags should be escaped before encoded into JSON.
+
+3) Client-side: No untrusted data presented to user: `:inner_html/:inner_text`:
+only uses content from the server after it has been sanitized/escaped.
+
+4) Client-side: No client-side sanitization/escaping. Too many bugs and security issues
+because of browser incompability/implementations. Content
+to be used in client-size JS can only come from the server using "lockboxed vars".
+
+5) Client-side: When using `:inner_html`, check for: `/<script/i` in String.
+
+6) All forms require a CSRF token.
+
+
+Notes:
+-------
+
+1) Blockquotes no longer allow the :cite attribute. Instead use the `cite` tag.
+More info at:  [http://html5doctor.com/cite-and-blockquote-reloaded/](http://html5doctor.com/cite-and-blockquote-reloaded/)
+
+2) Originally, this was going to be programs written in 100% JSON. This has changed
+because it turns out people do not want to create programs, they just want to customize them:
+[https://www.youtube.com/watch?v=9nd9DwCdQR0#t=857](https://www.youtube.com/watch?v=9nd9DwCdQR0#t=857)
+
+
+Fun fact:
+-----
+
+[JSON Applet](http://github.com/da99/json_applet) was changed to WWW\_Applet. WWW\_Applet was then changed to WWW\_App.
+
+
+
+

data/TODO.md

@@ -0,0 +1,13 @@
+
+
+TODO:
+-----
+
+1) Timestamps on filenames for css, js, etc.
+
+2) Cache control of HTML output.
+
+3) Combine all JS files into one:
+  * if one fails, the rest fails.
+  * prevent caching of old content.
+  * self-contained one file client apps.

data/VERSION

@@ -0,0 +1 @@
+1.0.0

data/bin/www_app

@@ -0,0 +1,46 @@
+#!/usr/bin/env ruby
+# -*- bash -*-
+#
+#
+
+case ARGV[0]
+
+when "help"
+
+  puts %^
+    # ===================="
+    www_app help"
+    www_app install_js"
+    # ===================="
+  ^
+
+when "install_js"
+
+  fail "
+    Must automate downloading of LATEST (security reason)
+    underscore, jquery, etc.
+  "
+  require "fileutils"
+  args   = ARGV.dup
+
+  applet_file = File.join File.dirname(File.dirname(__FILE__)), "lib/www_app.js"
+
+  target_dir = if ARGV[1]
+                 ARGV[1]
+               else
+                 Dir.pwd
+               end
+
+  new_file = File.join target_dir, "www_app.js"
+  FileUtils.cp applet_file, new_file
+  puts "#=== From:  #{applet_file}"
+  puts "#=== Wrote: #{new_file}"
+
+else
+
+  abort "Unknown operation: #{ARGV.first.inspect}"
+
+end # === case
+
+
+

data/doc/Design.md

@@ -0,0 +1,123 @@
+
+A
+=========================
+
+If :href is a Symbol
+  onclick, cancel default event
+  and run event named in
+  :href Symbol.
+
+Buttons
+=========================
+
+```
+   button.^(:submit) { 'Save" }
+   button.^(:cancel, :red) { 'Cancel" }
+   button.^(:blue, :yell) { 'Save" }
+```
+
+This behavior is special to buttons:
+  All buttons
+    when clicked
+    run each event from class names
+    ignore if event does not exist.
+
+Input
+=========================
+
+```
+  input(:text, :my_name, 'Robert')
+  input(:text, 'Robert')
+  input(:pass_phrase)
+```
+
+This behaviour is special to inputs:
+  when :input is in 
+    fieldset with one or more class names:
+      the first class name is the default name.
+      if class name is :password,
+        type is set to :password
+        if first arg is Symbol,
+          name is set to first arg.
+      else
+        type is set to :text
+      if last arg is String,
+        value is set to last arg.
+  else
+    return super
+
+Attaching Events to Tags and Parents
+====================================
+
+```
+  div {
+    observe :submit
+    form.action('...') {
+      button.^(:submit)
+    }
+```
+
+If no parent observes action name:
+  then attach to nearest :form tag.
+  else attach to tag (in this case, :button)
+
+CSS + JS
+========
+
+```
+  div {
+
+    on(:click) {
+
+      border '1px solid #fff'
+
+      when_eq :my_var, 'some js' do
+        emit :my_box_was_clicked
+      end
+
+      if_not_then do
+        emit :dont_know_what
+      end
+
+    }
+
+  }
+```
+
+JS Templates
+============
+
+```ruby
+  div.*(:mine) {
+
+    observe :record
+
+    span.^(:empty) { 'No records.' }
+
+    div.^(:list).template(:record, records) { |o|
+
+      div.^(:record) do
+
+        border_width '1px'
+
+        on(:delete) {
+          background 'some image'
+          server :delete
+        }
+
+        span.^(:title) { o[:title] }
+        a.href(:delete) { 'Delete' }
+      end
+    }
+
+  }
+```
+1) Parent and selectors.
+2) Passing the message to target + observers.
+3) Default message receivers:
+   Current tag, -> Parents -> Form
+
+
+
+
+

data/doc/Why_this_arch.rb

@@ -0,0 +1,104 @@
+
+Why Services and not a programming language?
+---------------------------
+
+
+Ideas to remember, in this order:
+
+  1. the majority of software for the Majority of Humans requires
+  customization and settings/options: in other words, configuration
+  rather than creating an app. Science and Nintendo-style
+  video games require more "power", (ie a programming language).
+
+  2. most of the action in WWW\_Apps is:
+  describing things you are doing to the
+  stacks... and things you are doing to the 
+  values on the stack.
+
+  3. universal problem solving: break up the problems
+  into re-usable components by complexing the problem
+  and comparing it to similar and different problems.
+
+  4. DSLs/POLs, even if they are a subset of a prog. lang.,
+  are stil their own culture/env./prog. lang. Just like
+  with anything else, people do not want to learn something
+  new unless they see LOTS of other people/companies using it,
+  or if it is being talked about a lot (eg XML, Java, etc.).
+
+  5. It doesn't matter if you can play well with others,
+  because no one wants to play with you. Hence, the lack of
+  good "virtual machine"-based architecture and sandboxing in
+  browsers.  Hence, the lack of demand for programming languages
+  written using nothing but JSON.
+
+  6. The most important and the most easily mis-understood
+  and overlooked: 
+
+    > It's not about solving problems.
+    > It's about finding "better" requirements.
+
+    Once the requirements change, you have to re-evaluate
+    the design/architecture immediately.
+
+  7. It's hard finding better requirements because of
+  familiarity and complexity (quantity and quantity).
+  Lazyiness and limited resources help you guide you to
+  fulfilling the requirements w/efficiency.
+
+  8. Programmers already have a common runtime:
+  HTML, CSS, Javascript, and their preferred server-side
+  language. They do not want something easier. They
+  want something familiar. Also, "write once, run anywhere"
+  is not something programmers want because they want to use
+  their own preferred language ...above all else... to generate
+  HTMl/CSS/JS. That leaves app-to-app messaging (ie JSON over AJAX).
+
+  9. Most apps/apps are:
+
+    > input -> JSON/AJAX -> Server -> markup
+
+    App/app makers do not neet programming capilities
+    outside of Nintendo-like gaming... because they will do
+    that in their favorite language on the server, then
+    send the final output to the user in the browser.
+    The "programming" happens on the server, and the client is
+    just a "dumb" GUI to collect and display input/output.
+
+    This is the closest people want to "write once/run everywhere"
+    because of their need to stick to their preferred language
+    and the limited needs of the consumer and producer (business).
+
+    Most industrial designers also do not want to run their own
+    business, but merely constant "experiment" with creating.
+    In other words, occasional invention, no innovation, and
+    constant experimenting. There is not much of a need, beyond
+    my own, of a better Smalltalk/Factor/Xananud system...
+    outside of Nintendo-like gaming.
+
+  10. If WWW\_App is going to be a programming language,
+  might as well go all the way: make it an abstraction over
+  everything (ie HTML/CSS/JS and all server-side langs,
+  including Ruby and Lua). A runtime will be created for
+  each language.
+
+I originally wanted this to be an abstraction layer over
+HTML, JS, CSS. However, during the development of "www\_app",
+I realized I could do that w/ just Ruby. In other words,
+I would not need a sophisticated runtime in the browser.
+Most of the work would be on the server (to generate the HTML, CSS)
+and the JS would mainly consist of calling functions in the browser
+from my own api/libs.
+
+The need for www\_app was pushed forward, also, because
+most people do not need a common way to exchange code in programming
+languages. Instead, their needs are configuration,
+rather than a programming language or DSL/POL.
+This is more higher level than HyperCard:
+
+  > Configure rather than create.
+
+Also, I realized www\_app can become it's own programming
+language with the power to replace PHP. It sounds crazy, but
+no more crazy than the popularity of garbage like PHP and Wordpress.
+It would only require an extra 2 weeks, but this is still too much
+time that I can not afford because I am going broke.