StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12170246
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-08-29T02:47:32.273
FavoriteCount
0
LastActivityDate
2012-08-29T02:47:32.273
LastEditDate
LastEditorUserId
0
OwnerUserId
191846
ParentId
12145606
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It depends on how you want to render the hash. Assuming the code: <pre><code>require 'inversion' the_hash = { :a => [ { :b => 'foo', :c => 'bar' }, { :d => 'blah', :e => 'blubb'} ] } </code></pre> You can render it as-is, of course: <pre><code> <code><?pp the_hash ?></code> </code></pre> and then: <pre><code>tmpl = Inversion::Template.load( 'prettyprint.tmpl' ) tmpl.the_hash = the_hash puts tmpl.render </code></pre> which will render as: <pre><code> <code>{:a=&gt;[{:b=&gt;"foo", :c=&gt;"bar"}, {:d=&gt;"blah", :e=&gt;"blubb"}]}</code> </code></pre> Assuming you want to do something more complex with the hash, like render some of its members: <pre><code> A's first B is: <?call the_hash[:a].first[:b] ?> A's first C is: <?call the_hash[:a].first[:c] ?> A's second D is: <?call the_hash[:a][1][:d] ?> A's second E is: <?call the_hash[:a][1][:e] ?> </code></pre> which (with the same code as the previous example except loading 'members.tmpl' instead) will render like so: <pre><code> A's first B is: foo A's first C is: bar A's second D is: blah A's second E is: blubb </code></pre> But building a big complex data structure like your hash, and then later merging it with a template is not really how Inversion is intended to be used. The idea is really that loading the template gives you a Ruby object with an API, suitable for passing around and incrementally adding stuff to before rendering it. Instead of building a hash, just pass the template object itself around and call accessors on it, then let it pull out what it needs to build the view: <pre><code>tmpl.users = User.all tmpl.company = "ACME Widgets, Pty" tmpl.render </code></pre> This also has the advantage of being more amenable to mocking: <pre><code># (rspec) tmpl = mock( "members template" ) tmpl.should_receive( :users ).with( User.all ) tmpl.should_receive( :company ).with( company_name ) tmpl.should_receive( :render ).and_return( "the rendered stuff" ) </code></pre> This removes the template contents from the test entirely, and just focuses on what messages the controller should be sending to the view. There's a fairly full-featured example <a href="http://deveiate.org/code/Inversion-manual/examples.html" rel="nofollow">in the manual</a>, along with <a href="https://github.com/ged/inversion/blob/master/experiments/demo.rb" rel="nofollow">the code that renders it</a>. The library (and its documentation) are fairly new, so thanks for bringing this up. I have a pending patch to merge <a href="http://deveiate.org/code/Inversion-manual/" rel="nofollow">the manual</a> with the API docs, which should help, but in the meantime it's probably the best place to find examples. Hope this helps. I'm happy to answer more in-depth questions personally (ged at FaerieMUD.org), or accept patches via pull request on <a href="https://github.com/ged/inversion" rel="nofollow">Github</a> or <a href="https://bitbucket.org/ged/inversion" rel="nofollow">Bitbucket</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORender Inversion template from hash
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMichael Granger
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORender Inversion template from hash
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COFantastic, thanks a lot!
 singulars
 PostPostId
 PO
 UserUserId
 USchristina

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.