Dylan Jay wrote:
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.
that was my suggestion.
I haven't thought through all the implications yet but that would be more
than a non-AT solution right?
yes, that would be putting the auto-UI generation stuff where it belongs. any
number of property providers could be used, it wouldn't matter what they were.
That would take memberane out of the picture
all together I think.
i think i know what you mean here, but this is a bit strong. membrane would
still be a useful tool for using content to drive member information, but it
could be more smoothly merged with other property providers w/o having to jump
through strange hoops to get a nice integrated UI.
Prob not something you guys are interested in.
we're interested in it. it's just not something that belongs within the scope
of membrane or remember. it belongs inside of Plone. once it was in place
there, then remember could do less, since it would no longer have to reroute
the standard Plone member profile pages to point at the AT edit form... the
standard forms would automatically reflect the AT schema by virtue of the
membrane plug-ins wiring up the properties.
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).
yup, this is exactly the problem.
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).
indeed.
-r
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228936883774
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
