Adding the extra line for the button and cancel link pushes everything down a bit. Could you experiment with displaying it on the same line as the summary? In that dark bar, all the way to the right. Maybe you don't even need a Cancel link?
The `flag` variable should be renamed to something more specific. And `if flag == True:` can be better written just `if flag:` Nice work figuring out that area of code though. It is "EasyWidgets" which is far from easy. In some new places we don't even use it since its fairly confusing. When you're done can you rebase and squash all the commits into one? And put `[#1695] ` at the beginning of the commit message. That helps us link our commits to the ticket and its discussion. --- ** [tickets:#1695] Add a Save button to the top half of the ticket view somewhere** **Status:** open **Milestone:** unreleased **Created:** Mon Mar 14, 2011 02:52 PM UTC by John Hoffman **Last Updated:** Mon Mar 14, 2016 02:08 AM UTC **Owner:** nobody Editing a ticket to change the status, milestone, or owner and then having to scroll to the bottom of the page to save the changes could be less painful with an additional save button near the top of the form. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
