sproutcore 1.5.0 → 1.6.0.beta.1

data/lib/frameworks/sproutcore/frameworks/desktop/views/file.js

@@ -1,148 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2011 Strobe Inc. and contributors.
-//            Portions ©2008-2011 Apple Inc. All rights reserved.
-// License:   Licensed under MIT license (see license.js)
-// ==========================================================================
-
-/*
-  TODO revisit this to see if these classnames are usable
-*/
-
-/** @class
-
-  Implements a customized file input by creating a standard file input in a
-  transparent iframe over top of a SC.ButtonView.
-  
-  SC.FieldView uses the SC.Control mixin which will apply CSS 
-  classnames when the state of the file view changes:
-  
-    - active     when button is active
-    - sel        when button is toggled to a selected state
-  
-  @extends SC.FieldView
-  @since SproutCore 1.0
-  @author Tyler Keating
-*/
-SC.FileView = SC.FieldView.extend(
-/** @scope SC.FileView.prototype */ {
-
-  /**
-    @type Array
-    @default ['sc-file-view']
-    @see SC.View#classNames
-  */
-  classNames: ['sc-file-view'],
-  
-  /** @private */
-  childViews: ['button', 'form'],
-
-
-  // ..........................................................
-  // Properties
-  // 
-
-  /**
-    @type Boolean
-    @default YES
-  */
-  autoSubmit: YES,
-
-  /**
-    The name of the action you want triggered when the button is pressed.  
-    
-    This property is used in conjunction with the target property to execute
-    a method when a regular button is pressed.  These properties are not 
-    relevant when the button is used in toggle mode.
-    
-    If you do not set a target, then pressing a button will cause the
-    responder chain to search for a view that implements the action you name
-    here.  If you set a target, then the button will try to call the method
-    on the target itself.
-    
-    For legacy support, you can also set the action property to a function.
-    Doing so will cause the function itself to be called when the button is
-    clicked.  It is generally better to use the target/action approach and 
-    to implement your code in a controller of some type.
-    
-    @type String
-    @default 'uploadImage'
-  */
-  action: 'uploadImage',
-  
-  /**
-    The target object to invoke the action on when the button is pressed.
-    
-    If you set this target, the action will be called on the target object
-    directly when the button is clicked.  If you leave this property set to
-    null, then the button will search the responder chain for a view that 
-    implements the action when the button is pressed instead.
-    
-    @type Object
-    @default null
-  */
-  target: null,
-  
-  /**
-    @type String
-    @default "Choose File"
-  */
-  title: "Choose File",
-
-
-  // ..........................................................
-  // Views
-  // 
-
-  /** @private */
-  button: SC.ButtonView.design({
-    title: 'Choose File',
-    theme: 'capsule'
-  }),
-
-  /** @private */
-  form: SC.View.design({
-    tagName: 'form',
-    
-    /** @private */
-    render: function(context, firstTime) {
-      context.attr('method', 'post').attr('action', "javascript:;").attr('enctype', 'multipart/form-data');
-      sc_super();
-    },
-    
-    childViews: ['input'],
-    
-    input: SC.View.design({
-      tagName: 'input',
-
-      /** @private */
-      render: function(context, firstTime) {
-        context.attr('type', 'file').end();
-        sc_super();
-      }
-    })
-  }),
-  
-  
-  // ..........................................................
-  // FieldView Overrides
-  // 
-  
-  /** @private
-    Since it is impossible to set the value of file inputs, don't attempt it.
-  */
-  setFieldValue: function(newValue) {
-    SC.Logger.log("SC.FileView: setFieldValue: %@ does nothing".fmt(newValue));
-    //if (newValue) throw SC.$error('SC.FileView can not set the value of the file field');
-  },
-  
-  /** @private */
-  fieldValueDidChange: function(partialChange) {
-    sc_super();
-    if (this.get('autoSubmit')) {
-      //this.form.submit();
-      
-      var resp = SC.Request.postUrl('/proxy/user/update_image').json().async(NO).send({picture: this.get('value')});
-    }
-  }
-});

data/lib/sproutcore/vendor/github_gem_lint.rb

@@ -1,22 +0,0 @@
-#!/usr/bin/env ruby
-require 'yaml'
- 
-if ARGV.size < 1
-  puts "Usage: github-test.rb my-project.gemspec"
-  exit
-end
- 
-require 'rubygems/specification'
-data = File.read(ARGV[0])
-spec = nil
- 
-if data !~ %r{!ruby/object:Gem::Specification}
-  Thread.new { spec = eval("$SAFE = 3\n#{data}") }.join
-else
-  spec = YAML.load(data)
-end
- 
-spec.validate
- 
-puts spec
-puts "OK"

data/vendor/sproutcore/src/SCCompiler/build.xml

@@ -1,74 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- You may freely edit this file. See commented blocks below for -->
-<!-- some examples of how to customize the build. -->
-<!-- (If you delete it and reopen the project it will be recreated.) -->
-<!-- By default, only the Clean and Build commands use this build script. -->
-<!-- Commands such as Run, Debug, and Test only use this build script if -->
-<!-- the Compile on Save feature is turned off for the project. -->
-<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
-<!-- in the project's Project Properties dialog box.-->
-<project name="SCCompiler" default="default" basedir=".">
-    <description>Builds, tests, and runs the project SCCompiler.</description>
-    <import file="nbproject/build-impl.xml"/>
-    <!--
-
-    There exist several targets which are by default empty and which can be 
-    used for execution of your tasks. These targets are usually executed 
-    before and after some main targets. They are: 
-
-      -pre-init:                 called before initialization of project properties
-      -post-init:                called after initialization of project properties
-      -pre-compile:              called before javac compilation
-      -post-compile:             called after javac compilation
-      -pre-compile-single:       called before javac compilation of single file
-      -post-compile-single:      called after javac compilation of single file
-      -pre-compile-test:         called before javac compilation of JUnit tests
-      -post-compile-test:        called after javac compilation of JUnit tests
-      -pre-compile-test-single:  called before javac compilation of single JUnit test
-      -post-compile-test-single: called after javac compilation of single JUunit test
-      -pre-jar:                  called before JAR building
-      -post-jar:                 called after JAR building
-      -post-clean:               called after cleaning build products
-
-    (Targets beginning with '-' are not intended to be called on their own.)
-
-    Example of inserting an obfuscator after compilation could look like this:
-
-        <target name="-post-compile">
-            <obfuscate>
-                <fileset dir="${build.classes.dir}"/>
-            </obfuscate>
-        </target>
-
-    For list of available properties check the imported 
-    nbproject/build-impl.xml file. 
-
-
-    Another way to customize the build is by overriding existing main targets.
-    The targets of interest are: 
-
-      -init-macrodef-javac:     defines macro for javac compilation
-      -init-macrodef-junit:     defines macro for junit execution
-      -init-macrodef-debug:     defines macro for class debugging
-      -init-macrodef-java:      defines macro for class execution
-      -do-jar-with-manifest:    JAR building (if you are using a manifest)
-      -do-jar-without-manifest: JAR building (if you are not using a manifest)
-      run:                      execution of project 
-      -javadoc-build:           Javadoc generation
-      test-report:              JUnit report generation
-
-    An example of overriding the target for project execution could look like this:
-
-        <target name="run" depends="SCCompiler-impl.jar">
-            <exec dir="bin" executable="launcher.exe">
-                <arg file="${dist.jar}"/>
-            </exec>
-        </target>
-
-    Notice that the overridden target depends on the jar target and not only on 
-    the compile target as the regular run target does. Again, for a list of available 
-    properties which you can use, check the target you are overriding in the
-    nbproject/build-impl.xml file. 
-
-    -->
-</project>

data/vendor/sproutcore/src/SCCompiler/manifest.mf

@@ -1,3 +0,0 @@
-Manifest-Version: 1.0
-X-COMMENT: Main-Class will be added automatically by build
-