|
childrenBlocks = [
- label("CategoryLabel", title=u"category"),
- field("CategoryAttribute",
- title=u"category", stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
|
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
| va...@yahoo.ca> |
childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 22 Feb, 04:55 |
|
widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
Sat, 07 Apr, 02:32 |
| od |
;gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Sat, 17 Aug, 17:33 |
| g...@washington.edu> |
l(parcel, _(u&quot;date&quot;), borderTop=2),
+ detail.makeSpacer(parcel, width=8),
+ detail.makeEditor(parcel, 'date',
+ viewAttribute=u'date',
+ border=RectType(0,2,2,2),
+ readOnly=True,
+ stretchFactor=0.0,
+ size=SizeType(90, -1)),
+ ],
+ ).install(parcel),
</span><span class="cx">
</span><span class="rem">- # Date area
- pair(&quot;DateArea&quot;, viewAttribute=u&quot;date&quot;, position=0.4,
- childrenBlocks = [
- label(&quot;DateLabel&quot;, title=u&quot;date&quot;),
- DateDetail.update(parcel, &quot;DateAttribute&quot;,
- title=u&quot;date&quot;,
- characterStyle=blocks.LabeleedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
Fri, 15 Nov, 13:18 |
|
title=u&quot;date&quot;,
- characterStyle=blocks.LabelStyle,
- stretchFactor=0.0,
- textAlignmentEnum=&quot;Left&quot;,
- ),
- ],
- ),
</span><span class="add">+ detail.makeSpacer(parcel, height=7, position=0.8999).install(parcel),
+
+ FeedItemDetail.update(parcel, &quot;ItemBodyArea&quot;,
+ position=0.9,
+ blockName=&quot;articletext&quot;,
+ size=SizeType(100,50),
+ minimumSize=SizeType(100,50),
+ ),
+ ]
</span><span class="cx">
</span><span class="rem">- # Category
- pair(&quot;CategoryArea&quot;, viewAttribute=u&quot;category&quot;,
- position=0.2,
- childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
|
| m |
title=u&quot;date&quot;,
- characterStyle=blocks.LabelStyle,
- stretchFactor=0.0,
- textAlignmentEnum=&quot;Left&quot;,
- ),
- ],
- ),
</span><span class="add">+ detail.makeSpacer(parcel, height=7, position=0.8999).install(parcel),
+
+ FeedItemDetail.update(parcel, &quot;ItemBodyArea&quot;,
+ position=0.9,
+ blockName=&quot;articletext&quot;,
+ size=SizeType(100,50),
+ minimumSize=SizeType(100,50),
+ ),
+ ]
</span><span class="cx">
</span><span class="rem">- # Category
- pair(&quot;CategoryArea&quot;, viewAttribute=u&quot;category&quot;,
- position=0.2,
- childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
Fri, 17 Sep, 18:43 |
| m |
title=u&quot;date&quot;,
- characterStyle=blocks.LabelStyle,
- stretchFactor=0.0,
- textAlignmentEnum=&quot;Left&quot;,
- ),
- ],
- ),
</span><span class="add">+ detail.makeSpacer(parcel, height=7, position=0.8999).install(parcel),
+
+ FeedItemDetail.update(parcel, &quot;ItemBodyArea&quot;,
+ position=0.9,
+ blockName=&quot;articletext&quot;,
+ size=SizeType(100,50),
+ minimumSize=SizeType(100,50),
+ ),
+ ]
</span><span class="cx">
</span><span class="rem">- # Category
- pair(&quot;CategoryArea&quot;, viewAttribute=u&quot;category&quot;,
- position=0.2,
- childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
Fri, 17 Sep, 18:43 |
| m |
title=u&quot;date&quot;,
- characterStyle=blocks.LabelStyle,
- stretchFactor=0.0,
- textAlignmentEnum=&quot;Left&quot;,
- ),
- ],
- ),
</span><span class="add">+ detail.makeSpacer(parcel, height=7, position=0.8999).install(parcel),
+
+ FeedItemDetail.update(parcel, &quot;ItemBodyArea&quot;,
+ position=0.9,
+ blockName=&quot;articletext&quot;,
+ size=SizeType(100,50),
+ minimumSize=SizeType(100,50),
+ ),
+ ]
</span><span class="cx">
</span><span class="rem">- # Category
- pair(&quot;CategoryArea&quot;, viewAttribute=u&quot;category&quot;,
- position=0.2,
- childrenBlocks = [
- label(&quot;CategoryLabel&quot;, title=u&quot;category&quot;),
- field(&quot;CategoryAttribute&quot;,
- title=u&quot;category&quot;, stretchFactor=1.0
- ),
- ]
- ),
- ],
</span><span class="add">+
+ # The DetailTrunkSubtree ties the blocks to our FeedItem's Kind.
+ detail.DetailTrunkSubtree.update(parcel, &quot;ChannelSubtree&quot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chand302204156.65C0CF10E4@tutu.osafoundation.org> |
Fri, 17 Sep, 18:43 |
| lt |
;lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Tue, 19 Apr, 06:07 |
|
uot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
|
|
uot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Sat, 18 Sep, 17:42 |
|
uot;,
+
+ # This ensures that this detail view gets attached to feed items
+ key = feeds.FeedItem.getKind(parcel.itsView),
+ rootBlocks = feedItemRootBlocks,
</span><span class="cx"> )
&lt;/pre&gt;
&lt;p /&gt;
</span><span class="rem">-Each &lt;code&gt;rootBlocks&lt;/code&gt; attribute refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way.
</span><span class="add">+The &lt;code&gt;rootBlocks&lt;/code&gt; attribute of the &lt;code&gt;DetailTrunkSubtree&lt;/code&gt; refers to a widget or fragment of user interface which will be displayed in the Detail View. Chandler will ensure that these user interface fragments will display and edit the correct data in a consistent way. For the details on the feedItemRootBLocks, you'll need to look at the &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;feeds tutorial&lt;/a&gt;. You cand find a list of all the available blocks &lt;a href=&quot;cpia-blocks.html&quot;&gt;here&lt;/a&gt;.
</span><span class="cx"> &lt;p /&gt;
&lt;h2&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler&quot;&gt; &lt;/a&gt;&lt;a name=&quot;Loading_the_Items_into_Chandler_&quot;&gt; &lt;/a&gt; Loading the Items into Chandler: Parcels &lt;/h2&gt;
&lt;p /&gt;
</span><span class="lines">@@ -484,20 +369,20 @@
</span><span class="cx"> &lt;p /&gt;
&lt;strong&gt;Behind the scenes:&lt;/strong&gt; The Python code for Kinds and Items is merely a bootstrapping mechanism to get data loaded into the Repository. The Repository is the primary data store that Chandler uses to keep all user data, schemas, and more. If data that is declared in your Parcel is changed within the Repository, those changes will &lt;em&gt;not&lt;/em&gt; be serialized back the Python code in your Parcel..
&lt;p /&gt;
</span><span class="rem">-&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where Chandler is today &lt;/h2&gt;
</span><span class="add">+&lt;h2&gt;&lt;a name=&quot;Where_Chandler_is_today&quot;&gt; &lt;/a&gt; Where we've been&lt;/h2&gt;
</span><span class="cx"> &lt;p /&gt;
In this paper, you have seen how to:
&lt;p /&gt;
&lt;ul&gt;
</span><span class="rem">-&lt;li&gt; Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chandler home page for ideas on how to &lt;a href=&quot;http://chandler.osafounation.org/getinvolved.php&quot;&gt;get involved&lt;/a&gt; with the Chandler project.
&lt;p /&gt;
</span>
</pre>
</div>
</div>
</body>
</html>
|
Sat, 18 Sep, 17:42 |
|
Define new data types
</span><span class="add">+&lt;li&gt; Define new data types by declaring kinds
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">-&lt;li&gt; Populate the repository with new data
</span><span class="add">+&lt;li&gt; Populate the repository with new data using the &lt;code&gt;update&lt;/code&gt; method
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt; Display that data in the Sidebar, Summary View, and Detail View
&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
</span><span class="rem">-The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind.
</span><span class="add">+The next step is to spend some time developing your own data types and application behavior. The steps described here will get you some basic functionality out of your data but Chandler's true potential comes to light when you begin to explore some of its more advanced capabilities. When Items have been properly defined, many of these capabilities &quot;just work&quot; for your new Kind. Two examples of these capabilities are Sharing and Stamping.
</span><span class="cx"> &lt;p /&gt;
&lt;h3&gt;&lt;a name=&quot;Sharing&quot;&gt; &lt;/a&gt; Sharing &lt;/h3&gt;
&lt;p /&gt;
</span><span class="lines">@@ -513,7 +398,7 @@
</span><span class="cx"> &lt;img src=&quot;http://wiki.osafoundation.org/pub/Documentation/BuildingChandlerParcels/mac_calendar_vertical.png&quot; alt=&quot;mac_calendar_vertical.png&quot; width=&quot;1024&quot; height=&quot;532&quot; /&gt;
--&gt;
&lt;h2&gt;What to do next&lt;/h2&gt;
</span><span class="rem">-There is a more detailed &lt;a href=&quot;&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will explain more of the details of writing a parcel.
</span><span class="add">+There is a more detailed &lt;a href=&quot;http://chandler.osafoundation.org/docs/0.6/feeds-tutorial.html&quot;&gt;tutorial&lt;/a&gt; on the workings of the Feeds parcel that will fill in the details of writing a parcel.
</span><span class="cx"> &lt;p /&gt;
You can visit the Chan |