[web2py] Re: SQLFORM.grid, links and buttons placement specification (before other columns, after, or both)
I apologize I have overlooked this patch. I tried apply it now but does not apply. Would you mind rewriting the patch against latest trunk and posting the patch on google code? thanks. Massimo On Tuesday, 17 April 2012 03:57:04 UTC-5, nikos wrote: > > Hello there follow web2py users, > > First of all, Massimo, thanks for the great work you have done to get > web2py to this high level of functionality. > > I recently started using it for a project and was faced with a challenge: > in SQLFORM.grid, when a table has many fields, the users have to scroll to > the far right to get to the action buttons, and this has proved cumbersome > to them. > The same goes for the links that we are allowed to add to the grid. > > I chose to resolve this issue by adding two extra optional arguments to > SQLFORM.grid, namely buttons_placement and links_placement > The two are expected to have a value among 'left', 'right', 'both' > Both default to 'right' to maintain backward compatibility. > > If you set them to 'left' the corresponding column(s) will appear at the > beginning of the grid (1st column). > If you set them to 'right, they will appear at the end (as it was already > working) > If you set them to 'both', the columns will appear twice, at the beginning > and at the end (usefull for large tables where the user can locate the > column he wants to decide upon and find a button closeby, either at the > beginning or the end) > > I am attaching a patch against the stock 1.99.7 that I used to begin with. > > It would be great if some form of this patch would be included in future > releases. > > Again, thanks for all the hard work you all have put into this. > > Nikos > > > --
[web2py] Re: SQLFORM.grid, links and buttons placement specification (before other columns, after, or both)
+1 needed this since January :) links on left side would be great. https://groups.google.com/d/topic/web2py/ZlxQ3AfWrr4/discussion On Tuesday, April 17, 2012 4:57:04 AM UTC-4, nikos wrote: > > Hello there follow web2py users, > > First of all, Massimo, thanks for the great work you have done to get > web2py to this high level of functionality. > > I recently started using it for a project and was faced with a challenge: > in SQLFORM.grid, when a table has many fields, the users have to scroll to > the far right to get to the action buttons, and this has proved cumbersome > to them. > The same goes for the links that we are allowed to add to the grid. > > I chose to resolve this issue by adding two extra optional arguments to > SQLFORM.grid, namely buttons_placement and links_placement > The two are expected to have a value among 'left', 'right', 'both' > Both default to 'right' to maintain backward compatibility. > > If you set them to 'left' the corresponding column(s) will appear at the > beginning of the grid (1st column). > If you set them to 'right, they will appear at the end (as it was already > working) > If you set them to 'both', the columns will appear twice, at the beginning > and at the end (usefull for large tables where the user can locate the > column he wants to decide upon and find a button closeby, either at the > beginning or the end) > > I am attaching a patch against the stock 1.99.7 that I used to begin with. > > It would be great if some form of this patch would be included in future > releases. > > Again, thanks for all the hard work you all have put into this. > > Nikos > > > --
[web2py] Re: SQLFORM.grid, links and buttons placement specification (before other columns, after, or both)
I would love for this to go in the main trunk. (Especially interested in links_placement='left') If this can't go into the release, what is the best way that allows me to make this change in my local web2py installation, as well as keep getting subsequent web2py changes ? -Mandar On Tuesday, April 17, 2012 2:27:04 PM UTC+5:30, nikos wrote: > > Hello there follow web2py users, > > First of all, Massimo, thanks for the great work you have done to get > web2py to this high level of functionality. > > I recently started using it for a project and was faced with a challenge: > in SQLFORM.grid, when a table has many fields, the users have to scroll to > the far right to get to the action buttons, and this has proved cumbersome > to them. > The same goes for the links that we are allowed to add to the grid. > > I chose to resolve this issue by adding two extra optional arguments to > SQLFORM.grid, namely buttons_placement and links_placement > The two are expected to have a value among 'left', 'right', 'both' > Both default to 'right' to maintain backward compatibility. > > If you set them to 'left' the corresponding column(s) will appear at the > beginning of the grid (1st column). > If you set them to 'right, they will appear at the end (as it was already > working) > If you set them to 'both', the columns will appear twice, at the beginning > and at the end (usefull for large tables where the user can locate the > column he wants to decide upon and find a button closeby, either at the > beginning or the end) > > I am attaching a patch against the stock 1.99.7 that I used to begin with. > > It would be great if some form of this patch would be included in future > releases. > > Again, thanks for all the hard work you all have put into this. > > Nikos > > > --
[web2py] Re: SQLFORM.grid, links and buttons placement specification (before other columns, after, or both)
+1 all work to improve the grid is good! I am a big fan of it.. On Tuesday, 17 April 2012 09:57:04 UTC+1, nikos wrote: > > Hello there follow web2py users, > > First of all, Massimo, thanks for the great work you have done to get > web2py to this high level of functionality. > > I recently started using it for a project and was faced with a challenge: > in SQLFORM.grid, when a table has many fields, the users have to scroll to > the far right to get to the action buttons, and this has proved cumbersome > to them. > The same goes for the links that we are allowed to add to the grid. > > I chose to resolve this issue by adding two extra optional arguments to > SQLFORM.grid, namely buttons_placement and links_placement > The two are expected to have a value among 'left', 'right', 'both' > Both default to 'right' to maintain backward compatibility. > > If you set them to 'left' the corresponding column(s) will appear at the > beginning of the grid (1st column). > If you set them to 'right, they will appear at the end (as it was already > working) > If you set them to 'both', the columns will appear twice, at the beginning > and at the end (usefull for large tables where the user can locate the > column he wants to decide upon and find a button closeby, either at the > beginning or the end) > > I am attaching a patch against the stock 1.99.7 that I used to begin with. > > It would be great if some form of this patch would be included in future > releases. > > Again, thanks for all the hard work you all have put into this. > > Nikos > > >
