StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19237128
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-10-08T00:29:01.030
FavoriteCount
0
LastActivityDate
2013-10-08T06:23:02.577
LastEditDate
2013-10-08T06:23:02.577
LastEditorUserId
350478
OwnerUserId
350478
ParentId
19236988
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think you are almost there. Firstly - yes, changing the css with javascript on runtime will immediately change the appearance of dom elements. On the client side - you want to indicate to the user which images have been selected, but you also need to store the approved value for each element in your submit form. In Rails it is common to create hidden input elements storing additional data. Given the task at hand - they can store a value of 0/1 - rejected/approved. You can come up with your own convention for naming the image/select values. Then, in your view, add onclick listeners to your images pointing to a javascript function: 1) checking if the clicked element is already selected, 2) changing the css of the current element, 3) updating the hidden input value for that element. Here is a dummy demonstration - <a href="http://jsfiddle.net/brj6h/2/" rel="nofollow">jsfiddle</a> Later, you can then get the approved/rejected value from the <code>params</code> in your controller, like (see below). In case you want to assign a css class when constructing the view and depending on an <code>approved</code> flag value, you could do something like: <pre><code> <img id="image_<%= image_id %>" src="<%= image_item.path" class="<%= (image_item.approved.to_i == 1) ? 'approved_img' : 'non_appr_img' %>" %> <input id="image_<%= image_id %>_app_flg" type="hidden" value="<%= image_item.approved %>" /> </code></pre> where image_item is an object properties <code>path</code> and <code>approved</code> (self explanatory), <code>image_id</code> the id of the image object, <code>approved_img</code> and <code>non_appr_img</code> - css classes. I'm not discussing the back-end for storing the approved flag, as it seems it is out of the scope of the question EDIT Brief concerning back-end Given the you have an images model, extend it to include an approval property (prepare a database migration and edit your model .rb file to include the new columns). In the view, include all of the hidden inputs inside a form which will be submitted to your controller(for example looping through an array on your images). For example: <pre><code> <%= form_for :images, :url => {:action => "approve_images"}, :html => {:name => "testForm"} do |f| %>  <% @images.each do |imageItem| %> <%= f.hidden_field "#{imageItem.id}_appproved", {:value => imageItem.approved}%> <% end %>  <% end %> </code></pre> *You need to Here <code>:images</code> is the controller, <code>approve_images</code> is the function in the controller that the form will be submitted to (include in routes), <code>@images</code> is an array with images data (from your model) and that you have prepared in the controller before rendering the view. I assume the images have ids and approved property. This will yield in your view dom elements like this: <pre><code><input id="images_IMAGEID_appproved" name="images[IMAGEID_approved]" type="hidden" value="1" /> </code></pre> After submitting the form, in your controller you will be able to access these values like this: <pre><code>img_approved = params[:images][IMAGEID+"_approved"] </code></pre> Finally you can store that value to your database. Good luck! :) <hr> I am omitting a lot of even more basic things, but I think the question is too broad as it is and there are plenty of resource detailing how to create,read,write a model, prepare data for the view etc. If not - please get started with <a href="http://guides.rubyonrails.org/getting_started.html" rel="nofollow">http://guides.rubyonrails.org/getting_started.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POClick rails button to permanently change data model and css
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USılǝ
UserOwnerUserId
1. USılǝ
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. COHey thanks for your advice. I'm actually curious to know what you would do with the backend, because I want my client to click and make those changes, but I want to see it on my own browser as well.
 singulars
 PostPostId
 PO
 UserUserId
 USBrice Lin
2. COActually your browser (user agent) is also client side :) The question is becoming rather broad, I will update my answer a bit, but it would be better to ask a more specific question or start with a tutorial (plenty freely available) if you are not certain how to approach this.
 singulars
 PostPostId
 PO
 UserUserId
 USılǝ

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.