Hey Sveto, I'm still in the midst of merging the My Collection branch into trunk, and have stumbled across a few issues that I wanted to run by you before fixing them.
1. It seems like the Artifact View page now depends on your "collectionOperations" subcomponent, but it hasn't been linked to in the HTML. As a result, viewing any artifact causes an error on page load. Was this working at some point in the past, or are you still in the midst of implementing collect/uncollect in Artifact View? 2. The change to fluid.engage.makeAcceptorForResource() to support resource-oriented URLs seems to cause other services to break. Exhibition Browse, for example, is returning data instead of markup from its markupSpout(). Justin and I are going to try to reimplement this in a non-breaking way. If you have any suggestions, let us know. Colin --- Colin Clark Technical Lead, Fluid Project Adaptive Technology Resource Centre, University of Toronto http://fluidproject.org _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
