Hi all, Before I started writing patches I thought I'd bounce this idea around the list to see what others think.
I'm currently finding the built in parameter names for things such as paginate and expose's tg_format more than a little cumbersome. One click of a next button in a paginated page and you have an unholy mess of a url. Is there any reason why configuring particular parameter names to combat the above might be a bad idea? I was thinking something along the lines of, in app.cfg: tg.custom_parameter.tg_format = 'format' This would mean if, for example, you're using one method to deliver user content and a feed using tg_format, your url keyword would change from ?tg_format=feed to ?format=feed. I'm not against having the tg_ there by default as it will prevent name clashes, but a little customisability would go a long way imo. Another problem, related to this, is that the paginate decorator includes positional parameters in its parameter list. So a url that reads: http://example.com/method/positional Changes to: http://example.com/method/positional?tg_paginate_limit=10&positional_param1=positional&tg_paginate_no=2 Note the extra positional param. I'm not sure what can be done about this (if anything) but I'm certainly looking into it. Questions/Comments? Lee -- Lee McFadden blog: http://www.splee.co.uk work: http://fireflisystems.com skype: fireflisystems --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
