StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5612472
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-10T14:39:32.287
FavoriteCount
0
LastActivityDate
2011-04-10T14:39:32.287
LastEditDate
LastEditorUserId
0
OwnerUserId
693554
ParentId
5417427
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I know that it is some time since you posted this, but I hope it helps or that others may find it helpfull. Assuming that you know how to make the calculations on the first page, lets call it the index-page (as it is properly named in rhodes), you can do it as follows: Before you begin make sure that you store the result of your calculations in a variable, for these instructions lets call it $result. 1) Create a new .erb file which you want to represent the result page (if you created a model, you already have a .erb file called "show" and could just as easily modify and use that). In this example - lets call the page "result". 2) Create a new def in your controller - lets call it "calculate". This could look something like this: <code>def calculate</code> <code>[do any calulations you should desire]</code> <code>$result = [result of calculations]</code> <code>render :action => :result, :back => url_for(:action => :index)</code> <code>end</code> This line: <code>render :action => :result, :back => url_for(:action => :index)</code> will send you to your result page and define the action for the smartphone's backbutton to navigate back to your index-page. 3) Make sure that your "get-result-button" on your index-page invokes your new def. For a simple link this could for example look something like this: <code><a href="<%= url_for :action => :calculate %>">get result</a></code> 4) Display the result in the result page. Your variable from your index-page is still available in the result-page, so you can show the result by adding the following line to your result-page (result.erb): <code><%= $result.to_s %> (this will insert your result as a string).</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POproblem for cross plateform rhodes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UScorthmann
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.