motion-prime 0.4.3 → 0.4.4

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    ZWVmZmZjNDVhMTMxZGE4ZjMzMWQyMzM0OWU4NDMzZGUzMjdmZTNjMQ==
-  data.tar.gz: !binary |-
-    ZDBkMTNhODQzYjQyZGMwOTI1ZTEwYWM2NzUyNTFjZDJhYTBiODUyZg==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    NDJkY2JmMzAzMWFmY2QyODM0Yzg1ODllMjRmNDY2MWIzMTk5MDRlMDI5NWQ1
-    NTIwZmJmYWE5Y2U2NzZjNWM3NGUwMTVkNDM0YzAyYzNiZjNlMDVkYmUwZGEw
-    NTkxNWJlY2U5ODM4NTIyNWNhN2I2M2UzZTRiYmYyMDllYWM0NDc=
-  data.tar.gz: !binary |-
-    NTU5YzUwZmUwYWVhYWNiYzc0YWIzOGU4NzMxMDE4NGJkMjUyN2QxZjBkMGY3
-    ZWJjMmMwN2E4YmZkMGM0YWZkZWI0NTBlYzIzYmEyM2NmNjVmNTJiNWUyZjZh
-    M2Y0Yjk2MjYzNGI1NDkwZjU0NjNlYTMyNzUyMjY1YzQ4OTZkOTc=
+SHA1:
+  metadata.gz: ed397d9e2fd731cd20575ece1c67b150915711c3
+  data.tar.gz: d35b535aafc6ccfc39b317ab15387b0d58032edd
+SHA512:
+  metadata.gz: bf28b8ece9d90c0703b94b1763d0fb7ff61f7a6f7688d8355634ed0f76af2528e08e07f7e1d185824d8596715e251dc479fc99cca1e1f04114b0466f1d2b7c64
+  data.tar.gz: 35f315439efb220eb33d6c63def92b87dda91d52713abad7ad573956cc00a514de7d023aba6113282c07098f1a0f509b7094717386d1de22b98f197c63e2dabe

data/CHANGELOG.md

@@ -1,3 +1,8 @@
+=== 0.4.4
+* Added Prime.env support
+* Added Prime.root support
+* Fix memory leak issues
+
 === 0.4.3
 * Speed improvements
 * Rename dm_ views to mp_

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    motion-prime (0.4.3)
+    motion-prime (0.4.4)
       bubble-wrap
       cocoapods
       methadone

data/ROADMAP.md

@@ -1,12 +1,17 @@
 === 0.5.0
-* rename support/dm_* to support/mp_*
 * "id" attribute should always be added to model by default
-* add DSL for ViewStyles#setValue conditions
-* add auto-symbol-value for Prime::Config.color items
+* fix issue when draw element without table section in parent will not be drawn.
+* Ability to pass "locals" while opening screen.
+* navigation: true by default for screen initialization.
+* separate screen.open_screen to screen.open_child and screen.open_modal.
+* use model.assign_attributes instead of model.fetch_with_attributes and call it on initialization. 
+* separate sync#update and sync#fetch
 
 === 0.6.0
 * add testing framework
 * add auth backends to ApiClient: password auth and facebook auth
 
 === 0.7.0
-* add sections/screens/models generator
+* add sections/screens/models generator
+* add DSL for ViewStyles#setValue conditions
+* add auto-symbol-value for Prime::Config.color items

data/doc/code/getting_started.rb

@@ -20,8 +20,7 @@ end
 
 # **3. Create the main screen.**
 #
-# You should rewrite the `render` method, which will be runned after opening screen.
-# Note: you must always pass `screen` option, which points to screen to render
+# You should rewrite the `render` method, which will be runned after first opening screen.
 
 class MainScreen < Prime::BaseScreen
   title 'Main screen'

data/doc/code/screens.rb

@@ -0,0 +1,54 @@
+# ** Render the screen. **
+#
+# You should rewrite the `render` method of Prime::BaseScreen, which will be runned after first opening screen.
+
+class MainScreen < Prime::BaseScreen
+  def render
+    @main_section = MyProfileSection.new(screen: self, model: User.first)
+    @main_section.render
+  end
+end
+
+# ** Set screen's title **
+# 
+# This title will be used in screen's navigation controller and will be shown there.
+
+class MainScreen < Prime::BaseScreen
+  title 'Main screen'
+end
+
+# Also, you can pass block to define screen's title
+
+class MainScreen < Prime::BaseScreen
+  title { params[:title] }
+end
+
+# ** Initialize screen. **
+#
+# Available options:
+# * :navigation. when this options is true, screen will be created with navigation support, like left and right buttons and title.
+# This option is false by default.
+
+screen = MainScreen.new(navigation: true)
+
+# ** Open screen: using app delegate. **
+
+# Opening screen using app delegate is the most basic way, you would do it at least on app load.
+#
+# Available options:
+# * :root. when this option is true, screen will not be in content controller and will create new root screen. 
+# You can use root: true when you have already opened screen with sidebar, and you want to open new screen without sidebar.
+# This option is false by default if you already have root screen and true if not.
+#
+# * :sidebar. send Prime::BaseScreen instance to this option if you want to create root screen with sidebar. 
+# value of this options will be used as sidebar controller.
+
+app_delegate.open_screen MainScreen.new(navigation: true), sidebar: MySidebar.new
+
+# ** Open screen: using parent screen. **
+
+# Opening screen using parent screen is usefull if you want to create inherited screen. 
+# Parent screen should have been initialized with navigation support.
+
+screen.open_screen AnotherScreen.new(navigation: true)
+

data/doc/docs/getting_started.html

@@ -11,6 +11,27 @@
   <div id="container">
     <div id="background"></div>
     
+      <ul id="jump_to">
+        <li>
+          <a class="large" href="javascript:void(0);">Jump To &hellip;</a>
+          <a class="small" href="javascript:void(0);">+</a>
+          <div id="jump_wrapper">
+          <div id="jump_page">
+            
+              
+              <a class="source" href="getting_started.html">
+                getting_started.rb
+              </a>
+            
+              
+              <a class="source" href="screens.html">
+                screens.rb
+              </a>
+            
+          </div>
+        </li>
+      </ul>
+    
     <ul class="sections">
         
           <li id="title">
@@ -98,7 +119,7 @@ Note: you should always use AppDelegate class name.</p>
                 <a class="pilcrow" href="#section-5">&#182;</a>
               </div>
               <p><strong>3. Create the main screen.</strong></p>
-<p>You should rewrite the <code>render</code> method, which will be runned after opening screen.</p>
+<p>You should rewrite the <code>render</code> method, which will be runned after first opening screen.</p>
 
             </div>
             
@@ -106,8 +127,8 @@ Note: you should always use AppDelegate class name.</p>
   title <span class="string">'Main screen'</span>
 
   <span class="function"><span class="keyword">def</span> <span class="title">render</span></span>
-    <span class="variable">@main_section</span> = <span class="constant">MyProfileSection</span>.new(<span class="symbol">model:</span> <span class="constant">User</span>.first)
-    <span class="variable">@main_section</span>.render(<span class="symbol">to:</span> <span class="keyword">self</span>)
+    <span class="variable">@main_section</span> = <span class="constant">MyProfileSection</span>.new(<span class="symbol">screen:</span> <span class="keyword">self</span>, <span class="symbol">model:</span> <span class="constant">User</span>.first)
+    <span class="variable">@main_section</span>.render
   <span class="keyword">end</span>
 <span class="keyword">end</span></pre></div></div>
             
@@ -122,7 +143,7 @@ Note: you should always use AppDelegate class name.</p>
               </div>
               <p><strong>4. Create your first section.</strong></p>
 <p>&quot;Section&quot; is something like helper, which contains &quot;Elements&quot;.</p>
-<p>Each element will be added to the parent screen when you run <code>section.render(to: screen)</code></p>
+<p>Each element will be added to the parent screen when you run <code>section.render</code></p>
 
             </div>
             
@@ -141,9 +162,9 @@ Note: you should always use AppDelegate class name.</p>
                 <a class="pilcrow" href="#section-7">&#182;</a>
               </div>
               <p><strong>5. Create your first stylesheet file.</strong></p>
-<p>Styles will be applied to each element in section. 
+<p>Styles will be applied to each element in section.
 The simplest rule by default is: <code>:section-name_:element-name</code>.</p>
-<p>E.g. if you have &#39;MyProfileSection&#39; (the name for section by default will be - <code>my_profile</code>) 
+<p>E.g. if you have &#39;MyProfileSection&#39; (the name for section by default will be - <code>my_profile</code>)
 and &#39;title&#39; element, then you should use <code>my_profile_title</code> style name.</p>
 
             </div>

data/doc/docs/screens.html

@@ -0,0 +1,166 @@
+<!DOCTYPE html>
+
+<html>
+<head>
+  <title>screens.rb</title>
+  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
+  <meta name="viewport" content="width=device-width, target-densitydpi=160dpi, initial-scale=1.0; maximum-scale=1.0; user-scalable=0;">
+  <link rel="stylesheet" media="all" href="docco.css" />
+</head>
+<body>
+  <div id="container">
+    <div id="background"></div>
+    
+      <ul id="jump_to">
+        <li>
+          <a class="large" href="javascript:void(0);">Jump To &hellip;</a>
+          <a class="small" href="javascript:void(0);">+</a>
+          <div id="jump_wrapper">
+          <div id="jump_page">
+            
+              
+              <a class="source" href="getting_started.html">
+                getting_started.rb
+              </a>
+            
+              
+              <a class="source" href="screens.html">
+                screens.rb
+              </a>
+            
+          </div>
+        </li>
+      </ul>
+    
+    <ul class="sections">
+        
+          <li id="title">
+              <div class="annotation">
+                  <h1>screens.rb</h1>
+              </div>
+          </li>
+        
+        
+        
+        <li id="section-1">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-1">&#182;</a>
+              </div>
+              <p><strong> Render the screen. </strong></p>
+<p>You should rewrite the <code>render</code> method of Prime::BaseScreen, which will be runned after first opening screen.</p>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre><span class="class"><span class="keyword">class</span> <span class="title">MainScreen</span> <span class="inheritance">&lt; <span class="parent">Prime::BaseScreen</span></span></span>
+  <span class="function"><span class="keyword">def</span> <span class="title">render</span></span>
+    <span class="variable">@main_section</span> = <span class="constant">MyProfileSection</span>.new(<span class="symbol">screen:</span> <span class="keyword">self</span>, <span class="symbol">model:</span> <span class="constant">User</span>.first)
+    <span class="variable">@main_section</span>.render
+  <span class="keyword">end</span>
+<span class="keyword">end</span></pre></div></div>
+            
+        </li>
+        
+        
+        <li id="section-2">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-2">&#182;</a>
+              </div>
+              <p><strong> Set screen&#39;s title </strong></p>
+<p>This title will be used in screen&#39;s navigation controller and will be shown there.</p>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre><span class="class"><span class="keyword">class</span> <span class="title">MainScreen</span> <span class="inheritance">&lt; <span class="parent">Prime::BaseScreen</span></span></span>
+  title <span class="string">'Main screen'</span>
+<span class="keyword">end</span></pre></div></div>
+            
+        </li>
+        
+        
+        <li id="section-3">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-3">&#182;</a>
+              </div>
+              <p>Also, you can pass block to define screen&#39;s title</p>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre><span class="class"><span class="keyword">class</span> <span class="title">MainScreen</span> <span class="inheritance">&lt; <span class="parent">Prime::BaseScreen</span></span></span>
+  title { params[<span class="symbol">:title</span>] }
+<span class="keyword">end</span></pre></div></div>
+            
+        </li>
+        
+        
+        <li id="section-4">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-4">&#182;</a>
+              </div>
+              <p><strong> Initialize screen. </strong></p>
+<p>Available options:</p>
+<ul>
+<li>:navigation. when this options is true, screen will be created with navigation support, like left and right buttons and title.
+This option is false by default.</li>
+</ul>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre>screen = <span class="constant">MainScreen</span>.new(<span class="symbol">navigation:</span> <span class="keyword">true</span>)</pre></div></div>
+            
+        </li>
+        
+        
+        <li id="section-5">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-5">&#182;</a>
+              </div>
+              <p><strong> Open screen: using app delegate. </strong></p>
+<p>Opening screen using app delegate is the most basic way, you would do it at least on app load.</p>
+<p>Available options:</p>
+<ul>
+<li><p>:root. when this option is true, screen will not be in content controller and will create new root screen. 
+You can use root: true when you have already opened screen with sidebar, and you want to open new screen without sidebar.
+This option is false by default if you already have root screen and true if not.</p>
+</li>
+<li><p>:sidebar. send Prime::BaseScreen instance to this option if you want to create root screen with sidebar. 
+value of this options will be used as sidebar controller.</p>
+</li>
+</ul>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre>app_delegate.open_screen <span class="constant">MainScreen</span>.new(<span class="symbol">navigation:</span> <span class="keyword">true</span>), <span class="symbol">sidebar:</span> <span class="constant">MySidebar</span>.new</pre></div></div>
+            
+        </li>
+        
+        
+        <li id="section-6">
+            <div class="annotation">
+              
+              <div class="pilwrap ">
+                <a class="pilcrow" href="#section-6">&#182;</a>
+              </div>
+              <p><strong> Open screen: using parent screen. </strong></p>
+<p>Opening screen using parent screen is usefull if you want to create inherited screen. 
+Parent screen should have been initialized with navigation support.</p>
+
+            </div>
+            
+            <div class="content"><div class='highlight'><pre>screen.open_screen <span class="constant">AnotherScreen</span>.new(<span class="symbol">navigation:</span> <span class="keyword">true</span>)</pre></div></div>
+            
+        </li>
+        
+    </ul>
+  </div>
+</body>
+</html>

data/files/Gemfile

@@ -5,4 +5,4 @@ gem 'motion-support', '~> 0.2.4'
 gem 'sugarcube', '~> 1.3.7', require: 'sugarcube-classic'
 gem 'bubble-wrap', '~> 1.3.0'
 
-gem 'motion-prime', '~> 0.4.2'
+gem 'motion-prime', '~> 0.4.4'

data/files/Gemfile.lock

@@ -0,0 +1,64 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    activesupport (3.2.16)
+      i18n (~> 0.6, >= 0.6.4)
+      multi_json (~> 1.0)
+    bubble-wrap (1.3.0)
+    claide (0.4.0)
+    cocoapods (0.28.0)
+      activesupport (>= 3.2.15, < 4)
+      claide (~> 0.4.0)
+      cocoapods-core (= 0.28.0)
+      cocoapods-downloader (~> 0.2.0)
+      colored (~> 1.2)
+      escape (~> 0.0.4)
+      json_pure (~> 1.8)
+      open4 (~> 1.3)
+      xcodeproj (~> 0.14.1)
+    cocoapods-core (0.28.0)
+      activesupport (>= 3.2.15, < 4)
+      fuzzy_match (~> 2.0.4)
+      json (~> 1.8)
+      nap (~> 0.5)
+    cocoapods-downloader (0.2.0)
+    colored (1.2)
+    escape (0.0.4)
+    fuzzy_match (2.0.4)
+    i18n (0.6.9)
+    json (1.8.1)
+    json_pure (1.8.1)
+    methadone (1.3.1)
+      bundler
+    motion-cocoapods (1.4.0)
+      cocoapods (>= 0.26.2)
+    motion-prime (0.4.3)
+      bubble-wrap
+      cocoapods
+      methadone
+      motion-cocoapods
+      motion-require
+      motion-support
+      sugarcube
+    motion-require (0.0.7)
+    motion-support (0.2.5)
+      motion-require (>= 0.0.6)
+    multi_json (1.8.2)
+    nap (0.6.0)
+    open4 (1.3.0)
+    rake (10.1.1)
+    sugarcube (1.3.11)
+    xcodeproj (0.14.1)
+      activesupport (~> 3.0)
+      colored (~> 1.2)
+      rake
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bubble-wrap (~> 1.3.0)
+  motion-cocoapods (~> 1.4.0)
+  motion-prime (~> 0.4.3)
+  motion-support (~> 0.2.4)
+  sugarcube (~> 1.3.7)

data/files/app/environment.rb

@@ -0,0 +1,10 @@
+module MotionPrime
+  def self.env
+    ENV['PRIME_ENV'] || ENV['RUBYMOTION_ENV'] || 'development'
+  end
+
+  def self.root
+    File.expand_path File.dirname(__FILE__) + '/../'
+  end
+end
+::Prime = MotionPrime unless defined?(::Prime)