Working fine now :) Yesterday I was thinking that this could have also be solved by treating ids the same as names, that is:
name = form.fs.name id = form_fs_name name = fs.name id = fs_name Right now ids are always fully qualified... What do you think? Alberto On 11/03/2006, at 13:06, Michele Cella wrote: > > Michele Cella wrote: >> I'm going to take a look at this now... >> > > I've fixed the problem in r932, it works much like register, you > define > not_in_path=True and you're not... in the path, not only for names but > for ids also, you're absolutely out of the path, that could be useful > in some other situation probably. ;-) > > The problem is that I'm unable to test any javascript with source > related widget since I end up with \n in the html now... I think this > is the problem, can someone test the widget browser? > > Ciao > Michele > > PS > Soon I'm going to also tune how we use fully_qualified_form, we should > except a form to always be at the top of the path (otherwise we can't > validate it) and hence we just need to decide if while traversing the > path we start from the beginning (index 0) or the next element > (index 1) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
