Thanks for all the work on gathering and feeding back the results Ross. > When all things are considered, there may not be much value to be gained > from such an effort. But I've always wanted to be able to recommend > something more lightweight than the entire membrane/remember stack just > to make profile extension accessible to integrators familiar with AT.
I keep thinking about the "auto generating the UI from the PAS proptertysheets" idea someone suggested on the developer list. I haven't thought through all the implications yet but that would be more than a non-AT solution right? That would take memberane out of the picture all together I think. Prob not something you guys are interested in. But it would have solved some problems I had recently. I had a client that wanted half the profile info from LDAP and half from AT-Content. One way I could have solved it was by making an ATPASPropertyField or PASPropertySheetStorage which went back to PAS to store the data (and therefore mapped to LDAP if you wanted). Seemed a little overly complex to me (so I just wrote a sync script instead). If instead there was a user profile utility that either produced a dynamic z3c.form by introspecting Pas propertysheets, (or let you override it if you wanted more control). Then I can use PAS to define my storage policy (not coded in AT). -- Archive: http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228884190058 To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
