tweaks to second page of /questions/new about askthem HOT 10 CLOSED

Yeah, we used to have those fields as multiple flat lines (instead of basic input visuals) but saw the possibility of it becoming too confusing, especially when there are underlines dividing the headers from form content. I think we need to spend a little time back in photoshop to give the flow a fresh work through.

from askthem.

Looking at doing this for all stages of the questions flow. I'll probably copy the same layout for signing up. In order to provide greater focus on the tasks ahead of the user, I removed everything the user wouldn't need if they decided to ask a question (or signup/sign in). Interested in your thoughts on this @walter.

from askthem.

To make this layout possible, @walter, I think I'll need to create a new layout template. I'm not sure how those templates are properly called, I thought it was a routes.rb thing but it appears to be void of anything layout related. Any suggestions?

from askthem.

@kidfribble app/views/layouts/application.html.erb is the site wide default layout.

You can use a different layout specifically in a controller... however in this case, I might just alter app/views/questions/new.html.erb as all the partials are surrounded by it.

from askthem.

In order to use the same template I would need to have a body class or something to hide all the extra stuff I don't need, or just make a new template for this case, which I think is right. As it stands now (working inside of app/views/questions/new.html.erb) I can only edit what's in the white block: http://db.tt/juf0NOjg

from askthem.

Sorry, having a bit of trouble remembering how Ruby controllers link to layouts! :(
I assume we'd put something like "layout: layout_file_name" in here somewhere:

 def new
    layout: file_name
    #all other def stuffs
 end

from askthem.

Out at breakfast at the moment, but you should be able to find it in here:

http://guides.rubyonrails.org/layouts_and_rendering.html

On Jul 26, 2013, at 8:51 AM, Steve Trevathan [email protected] wrote:

Sorry, having a bit of trouble remembering how Ruby controllers link to layouts! :(
I assume we'd put something like "layout: layout_file_name" in here somewhere:

def new
layout: file_name
#all other def stuffs
end
—
Reply to this email directly or view it on GitHub.

from askthem.

Awesome, thanks! Enjoy breakfast :)

from askthem.

Got it with some help here. I was hitting some weird error and had placed my render in the wrong position. I also had a double render error which was solved by commenting out the "new!" at the bottom of the "new" method in questions_controller.rb

from askthem.

Yeah, Inherited Resources add a little twist to the controller.

from askthem.