Martin Aspeli wrote:
Hi Wichert,
Without having reviewed the code in detail, I just wanted to say this rocks. :)
indeed. abstracting out the AT dependence has been on my internal to-do list
for almost as long as membrane has been around. never actually needed it
myself, though, and so i never got around to doing it... c'est-la-open-source.
luckily, you _do_ need it, and now it's out there for the rest of the world.
vive-la-open-source!
-r
+1 on not trying to generalise the adapters for Dexterity content at
this time, too.
Martin
2009/6/9 Wichert Akkerman <[email protected]>:
I've finished what is hopefully the final set of changes needed to
support non-Archetypes content in membrane. The interface for Archetypes
based content has not changed. The necessary interfaces have moved to
Products.membrane.at.interfaces, but the old location still works (with
a deprecation warning).
To make a content type usable with membrane you need to have your
content type adaptable to
Products.membrane.interfaces.IMembraneUserObject. Once you do that your
object will automatically be indexed in the membrane_tool and usable as
a user. All the other interfaces are optional and add extra features
(authentication, member properties).
I did not write any convenience adapters for dexterity; since the
adapters are so trivial to implement I am not sure at the moment a
package with generic adapters will be very useful or be able to handle
all use cases without becoming way more complex than needed. Better
documentation for membrane would be much more useful.
As a result of these changes membrane trunk now requires Plone 3.3 and
collective.indexing.
Wichert.
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244569393108
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact [email protected] for
questions.
