sproutit-sproutcore 1.0.203 → 1.0.20090721145236

data/frameworks/sproutcore/frameworks/desktop/views/split_divider.js

@@ -1,55 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-
-sc_require('views/split');
-
-/**
-  @class
-
-  A SplitDividerView displays a divider between two views within a SplitView.
-  Clicking and dragging the divider will change the thickness of each view
-  either to the top/left or bottom/right of the divider.
-
-  Double-clicking on the SplitDividerView will try to collapse the first
-  view within the SplitView that has property canCollapse set to true,
-  so it is not visible, unless you have canCollapse disabled on the SplitView.
-
-  This view must be a direct child of the split view it works with. It must
-  be surrounded by two other views.
-
-  @extends SC.View
-
-  @author Charles Jolley
-  @author Lawrence Pit
-  @author Erich Ocean
-  @test in split
-*/
-SC.SplitDividerView = SC.View.extend(
-/** @scope SC.SplitDividerView.prototype */ {
-
-  classNames: ['sc-split-divider-view'],
-  
-  /** @private */
-  prepareContext: function(context, firstTime) {
-    var splitView = this.get('splitView') ;
-    if (splitView) this.set('cursor', splitView.get('thumbViewCursor')) ;
-    return sc_super() ;
-  },
-  
-  mouseDown: function(evt) {
-    var splitView = this.get('splitView');
-    return (splitView) ? splitView.mouseDownInThumbView(evt, this) : sc_super();
-  },
-  
-  // FIXME: how does this work with event capture?
-  doubleClick: function(evt) {
-    console.log('doubleClick in split divider');
-    var splitView = this.get('splitView');
-    return (splitView) ? splitView.doubleClickInThumbView(evt, this) : sc_super();
-  }
-  
-});

data/frameworks/sproutcore/frameworks/desktop/views/stacked.js

@@ -1,101 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-
-sc_require('views/collection') ;
-
-/**
-  @class 
-
-  A StackedView is a CollectionView that expects its content to use static 
-  layout to stack vertically.  This type of collection view is not designed 
-  for use with large size collections, but it can be very useful for 
-  collections with complex displays and variable heights such as comments or
-  small notification queues.
-  
-  h2. Static Layout
-  
-  This view makes no attempt to size or position your child views.  It assumes
-  you are using StaticLayout for your child views.  If you don't enable static
-  layout your views will probably overlay on top of eachother and will look 
-  incorrect.
-
-  Note also that the default layout for this view set's the height to "auto".
-  This is usually the behavior you will want. 
-  
-  @extends SC.CollectionView
-  @since SproutCore 0.9
-*/
-SC.StackedView = SC.CollectionView.extend( 
-/** SC.StackedView.prototype */ {
-  
-  classNames: ['sc-stacked-view'],
-  
-  /** 
-    Default layout for a stacked view will fill the parent view but auto-
-    adjust the height of the view.
-  */
-  layout: { top: 0, left: 0, right: 0, height: 1 },
-
-  /**
-    Updates the height of the stacked view to reflect the current content of 
-    the view.  This is called automatically whenever an item view is reloaded.
-    You can also call this method directly if the height of one of your views
-    has changed.
-    
-    The height will be recomputed based on the actual location and dimensions
-    of the last child view.
-    
-    Note that normally this method will defer actually updating the height
-    of the view until the end of the run loop.  You can force an immediate 
-    update by passing YES to the "immediately" parameter.
-    
-    @param {Boolean} immediately YES to update immedately
-    @returns {SC.StackedView} receiver
-  */
-  updateHeight: function(immediately) {
-    if (immediately) this._updateHeight();
-    else this.invokeLast(this._updateHeight);
-    // ^ use invokeLast() here because we need to wait until all rendering has 
-    //   completed.
-    
-    return this;
-  },
-  
-  _updateHeight: function() {
-    
-    var childViews = this.get('childViews'),
-        len        = childViews.get('length'),
-        view, layer, height;
-        
-    if (len === 0) {
-      height = 1; 
-    } else {
-      view = childViews.objectAt(len-1);
-      layer = view ? view.get('layer') : null ;
-      height = layer ? (layer.offsetTop + layer.offsetHeight) : 1 ;
-      layer = null ; // avoid memory leaks
-    }
-    this.adjust('height', height);
-  },
-  
-  // ..........................................................
-  // INTERNAL SUPPORT
-  // 
-
-  /** @private
-    Whenever the collection view reloads some views, reset the cache on the
-    frame as well so that it will recalculate.
-  */
-  didReload: function(set) { return this.updateHeight(); },
-
-  /** @private
-    When layer is first created, make sure we update the height using the 
-    newly calculated value.
-  */
-  didCreateLayer: function() { return this.updateHeight(); }
-  
-});

data/frameworks/sproutcore/frameworks/desktop/views/tab.js

@@ -1,191 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-
-sc_require('views/segmented');
-
-SC.TOP_LOCATION = 'top';
-SC.BOTTOM_LOCATION = 'bottom';
-
-/** 
-  @class
-
-  Incorporates a segmented view and a container view to display the selected
-  tab.  Provide an array of items, which will be passed onto the segmented
-  view.
-  
-  @extends SC.View
-  @since SproutCore 1.0
-*/
-SC.TabView = SC.View.extend(
-/** @scope SC.TabView.prototype */ {
-
-  classNames: ['sc-tab-view'],
-  
-  displayProperties: ['nowShowing'],
-
-  // ..........................................................
-  // PROPERTIES
-  // 
-  
-  nowShowing: null,
-  
-  items: [],
-  
-  isEnabled: YES,
-  
-  itemTitleKey: null,
-  itemValueKey: null,
-  itemIsEnabledKey: null,
-  itemIconKey: null,
-  itemWidthKey: null,
-  
-  tabLocation: SC.TOP_LOCATION,
-  
-  /** 
-    If set, then the tab location will be automatically saved in the user
-    defaults.  Browsers that support localStorage will automatically store
-    this information locally.
-  */
-  userDefaultKey: null,
-  
-  
-  // ..........................................................
-  // FORWARDING PROPERTIES
-  // 
-  
-  // forward important changes on to child views
-  _tab_nowShowingDidChange: function() {
-    var v = this.get('nowShowing');
-    this.get('containerView').set('nowShowing',v);
-    this.get('segmentedView').set('value',v);
-    return this ;
-  }.observes('nowShowing'),
-
-  _tab_saveUserDefault: function() {
-    // if user default is set, save also
-    var v = this.get('nowShowing');
-    var defaultKey = this.get('userDefaultKey');
-    if (defaultKey) {
-      SC.userDefaults.set([defaultKey,'nowShowing'].join(':'), v);
-    }
-  }.observes('nowShowing'),
-  
-  _tab_itemsDidChange: function() {
-    this.get('segmentedView').set('items', this.get('items'));
-    return this ;    
-  }.observes('items'),
-
-  /** @private
-    Restore userDefault key if set.
-  */
-  init: function() {
-    sc_super();
-    this._tab_nowShowingDidChange()._tab_itemsDidChange();
-  },
-
-  awake: function() {
-    sc_super();  
-    var defaultKey = this.get('userDefaultKey');
-    if (defaultKey) {
-      defaultKey = [defaultKey,'nowShowing'].join(':');
-      var nowShowing = SC.userDefaults.get(defaultKey);
-      if (!SC.none(nowShowing)) this.set('nowShowing', nowShowing);
-    }
-
-  },
-  
-  createChildViews: function() {
-    var childViews = [], view, ContainerView ;
-    
-    if (this.get('tabLocation') === SC.TOP_LOCATION) {
-      ContainerView = this.containerView.extend({
-        layout: { top:12, left:0, right:0, bottom: 0 }
-      });
-    } else {
-      ContainerView = this.containerView.extend({
-        layout: { top:0, left:0, right:0, bottom: 12 }
-      });
-    }
-    
-    view = this.containerView = this.createChildView(ContainerView, { 
-      rootElementPath: [0] 
-    }) ;
-    childViews.push(view);
-    
-    view = this.segmentedView = this.createChildView(this.segmentedView, { 
-      rootElementPath: [1] 
-    }) ;
-    childViews.push(view);
-    
-    this.set('childViews', childViews);
-    return this; 
-  },
-  
-  // ..........................................................
-  // COMPONENT VIEWS
-  // 
-
-  /**
-    The containerView managed by this tab view.  Note that TabView uses a 
-    custom container view.  You can access this view but you cannot change 
-    it.
-  */
-  containerView: SC.ContainerView,
-  
-  /**
-    The segmentedView managed by this tab view.  Note that this TabView uses
-    a custom segmented view.  You can access this view but you cannot change
-    it.
-  */
-  segmentedView: SC.SegmentedView.extend({
-    layout: { left: 0, right: 0, height: 24 },
-
-    /** @private
-      When the value changes, update the parentView's value as well.
-    */
-    _sc_tab_segmented_valueDidChange: function() {
-      var pv = this.get('parentView');
-      if (pv) pv.set('nowShowing', this.get('value'));
-      
-      // FIXME: why is this necessary? 'value' is a displayProperty and should
-      // automatically cause displayDidChange() to fire, which should cause 
-      // the two lines below to execute in the normal course of things...
-      this.set('layerNeedsUpdate', YES) ;
-      this.invokeOnce(this.updateLayerIfNeeded) ;
-    }.observes('value'),
-    
-    /** @private
-      When we need to actually create a container, look for the tab loc from
-      the parent view and adjust the internal frame accordingly.  Also copy
-      the item key settings from the tab view.
-    */
-    render: function(context, firstTime) {
-      sc_super();
-      // copy some useful properties from the parent view first
-      var pv = this.get('parentView');
-      var tabLoc = (pv) ? pv.get('tabLocation') : SC.TOP_LOCATION ;
-      if (tabLoc === SC.TOP_LOCATION) {
-        context.addStyle('top', '0px');
-      } else {
-        context.addStyle('bottom', '0px');
-      }
-    },
-    
-    init: function() {
-      // before we setup the rest of the view, copy key config properties 
-      // from the owner view...
-      var pv = this.get('parentView');
-      if (pv) {
-        SC._TAB_ITEM_KEYS.forEach(function(k) { this[k] = pv.get(k); }, this);
-      }
-      return sc_super();
-    }
-  })
-  
-}) ;
-
-SC._TAB_ITEM_KEYS = 'itemTitleKey itemValueKey itemIsEnabledKey itemIconKey itemWidthKey'.w();

data/frameworks/sproutcore/frameworks/desktop/views/thumb.js

@@ -1,49 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-
-/**
-  @class
-
-  A ThumbView works in concert with SC.SplitView to adjust the divider 
-  position from an arbitrary subview of the SplitView. Simply make an
-  instance of ThumbView a child somewhere in the childViews (or 
-  descendants) of the split view and add the path to the ThumbView to the
-  SplitView's thumbViews array.
-  
-  SplitView will automatically set the splitView property of the views in
-  its thumbViews array.
-
-  @extends SC.View
-  @author Erich Ocean
-  @test in split
-*/
-SC.ThumbView = SC.View.extend(
-/** @scope SC.ThumbView.prototype */ {
-
-  classNames: ['sc-thumb-view'],
-  
-  /**
-    Enable this thumb view to control its parent split view.
-  */
-  isEnabled: YES,
-  isEnabledBindingDefault: SC.Binding.bool(),
-  
-  /** @private */
-  prepareContext: function(context, firstTime) {
-    var splitView = this.get('splitView') ;
-    if (splitView) this.set('cursor', splitView.get('thumbViewCursor')) ;
-    return sc_super() ;
-  },
-  
-  mouseDown: function(evt) {
-    if (!this.get('isEnabled')) return NO ;
-    
-    var splitView = this.get('splitView');
-    return (splitView) ? splitView.mouseDownInThumbView(evt, this) : sc_super();
-  }
-    
-});

data/frameworks/sproutcore/frameworks/desktop/views/toolbar.js

@@ -1,49 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-
-/** @class
-
-  A toolbar view can be anchored at the top or bottom of the window to contain
-  your main toolbar buttons.  The default implementation assumes you may have
-  a leftView, rightView, and centerView, which will be properly laid out.
-  
-  You can also override the layout property yourself or simply set the 
-  anchorLocation to SC.ANCHOR_TOP or SC.ANCHOR_BOTTOM.  This will configure
-  the layout of your toolbar automatically when it is created.
-
-  @extends SC.View
-  @since SproutCore 1.0
-*/
-SC.ToolbarView = SC.View.extend(
-  /** @scope SC.ToolbarView.prototype */ {
-
-  classNames: ['sc-toolbar-view'],
-  
-  /**
-    Default anchor location.  This will be applied automatically to the 
-    toolbar layout if you set it.
-  */
-  anchorLocation: null,
-
-  // ..........................................................
-  // INTERNAL SUPPORT
-  // 
-  
-  /** @private */
-  layout: { left: 0, height: 32, right: 0 },
-  
-  /** @private */
-  init: function() {
-    // apply anchor location before setting up the rest of the view.
-    if (this.anchorLocation) {
-      this.layout = SC.merge(this.layout, this.anchorLocation);
-    }
-    sc_super(); 
-  }
-
-});
-

data/frameworks/sproutcore/frameworks/desktop/views/web.js

@@ -1,86 +0,0 @@
-// ==========================================================================
-// Project:   SproutCore - JavaScript Application Framework
-// Copyright: ©2006-2009 Sprout Systems, Inc. and contributors.
-//            Portions ©2008-2009 Apple, Inc. All rights reserved.
-// License:   Licened under MIT license (see license.js)
-// ==========================================================================
-/** @class
-
-  Used to display an iframe. The source, (specified by the value property) of 
-  the iFrame should be from the same domain. (i.e. the src / value should be 
-  from the same domain) if you want to access the contents of the iframe.
-
-  @extends SC.View, SC.Control
-  @since SproutCore 1.0
-*/
-SC.WebView = SC.View.extend(SC.Control, {
-
-  classNames: 'sc-web-view',
-  displayProperties: ['value', 'shouldAutoResize'],
-
-  /**
-  The content of the iframe can be bigger than the size specifed when creating
-  the view. If you want the view to be auto-resized to the dimensions of the 
-  iframe, then set the value of this property to YES.
-  The web view can be auto resized only if the contents are from the same
-  domain as the parent domain.
-  @property{Boolean}
-  */
-  shouldAutoResize: NO,
-
-  render: function(context, firstTime) {
-    var src = this.get('value');
-    if (firstTime) {
-      context.push('<iframe src="' + src + 
-      '" style="position: absolute; width: 100%; height: 100%; border: 0px; margin: 0px; padding: 0p;"></iframe>');
-    } else {
-      var iframe = this.$('iframe');
-      // clear out the previous src, to force a reload
-      iframe.attr('src', 'javascript:;');
-      iframe.attr('src', src);
-    }
-  },
-
-  /**
-  Called when the layer gets created. 
-  */
-  didCreateLayer: function() {
-    var f = this.$('iframe');
-    // Attach an onload event to the iframe.
-    SC.Event.add(f, 'load', this, this.iframeDidLoad);
-  },
-
-
-  /** 
-  Called when iframe onload event is fired.
-  1. Resizes the view to fit the contents of the iframe using the 
-  scroll width and scroll height of the contents of the iframe
-  
-  The iframe contents can be accessed only when the src is from the same
-  domain as the parent document
-  @returns {void}
-  */
-  iframeDidLoad: function() {
-    //fit the iframe to size of the contents.
-    if (this.get('shouldAutoResize') === YES){
-      var contentWindow;
-      var iframeElt = this.$('iframe')[0];
-      if(iframeElt && iframeElt.contentWindow){
-        contentWindow = iframeElt.contentWindow;
-        if(contentWindow && contentWindow.document && contentWindow.document.documentElement){
-          var docElement = contentWindow.document.documentElement;
-          // setting the width before the height gives more accurate results.. 
-          // atleast for the test iframe content i'm using.
-          //TODO: try out document flows other than top to bottom.
-          if (!SC.browser.isIE){
-            this.$().width(docElement.scrollWidth);
-            this.$().height(docElement.scrollHeight);          
-          } else {
-            this.$().width(docElement.scrollWidth + 12);
-            this.$().height(docElement.scrollHeight + 5);          
-          }
-        }
-      }
-    }
-  }
-});

data/frameworks/sproutcore/frameworks/foundation/TESTING

@@ -1,46 +0,0 @@
-SproutCore Unit Testing
-
-ABOUT UNIT TESTS
-
-Unit tests are divided into two types of tests: API unit tests and integration 
-tests. API unit tests test each public method and property to ensure that the method behaves correctly according to its documentation.  Integration tests 
-spot check the way various API methods are used together to ensure they 
-function correctly in usage scenarios.
-
-Most unit tests found in the SproutCore framework are API unit tests.  
-Typically the testing directory for a framework will contain a folder 
-structure matching the framework source.  Within those folders will be one 
-folder per source class file.  Within that folder will be one test file per
-method (or groups of methods of the methods are very closely related).
-
-Integration tests, on the other hand, are all kept in the tests/integration
-folder.  Each file is named for the general type of integration scenarios 
-tested, but the structure and naming of this directory is less rigid.
-
-WHERE TO ADD NEW UNIT TESTS
-
-If you find a bug and reduce the problem down to a particular API method that
-is not responding in the way you might expect, then the best place to add a 
-test for this is in the API unit tests.  This will effectively make your unit
-test part of the API "specification" that must be satisified for all future
-releases.
-
-Often times, however, you will find bugs that are not due to a particular 
-method behaving badly but is due to a problem that occurs when you use a 
-series of API methods together in a certain way.  For these kinds of tests
-you should add a test to the integration directory.  If one of the existing
-files makes sense for your scenario, add it there.  Otherwise, create a new
-test file and add it there.
-
-HOW TO WRITE API UNIT TESTS VS INTEGRATION
-
-The purpose of an API unit test is to excercise individual methods in the API
-in isolation of the rest of the API.  You should swap out methods, mock objects, or make any other temporary modifications to the framework needed to
-make the method run as isolated as possible from other methods.
-
-Integration tests, on the other hand, are about testing API usage in place.
-Avoid mocking parts of the framework unless necessary.  Try to run the 
-framework code in its natural state to ensure the full stack is excercised 
-just as it would be in production code.
-
-