> From: Dan Finkelstein [mailto:[EMAIL PROTECTED]] > > sob...sob... > > I guess what I was attempting appeared to be such a natural extension of > the framework that I just assumed that it would be supported.
It should be eventually, when somebody sits down and solves the technical problems :-) > I'm just wondering, if the <path> tag supported a type attribute, we could > say something like > > ><view path="faq.xml"> > > <transform type="dvsl"> > > <path value="faq.dvsl"/> > > <path value="frame.vm" type="document"/> > > </transform> > ></view> > > Do you think that this is how you would approach adding in this > feature? Maybe, if this were only supported for the most "natural > transformations", it would just fit into the current design. If it seems > easy, can you point me to where in the source to focus for modifying? Either that or allowing multiple <transform> nodes. With multiple transform nodes, we could probably dispense with the <path> node syntax. I don't have a strong opinion either way. It doesn't seem easy, but please feel free to look into it :-) The core of the magic would be in org.infohazard.maverick.flow.MasterTransformFactory. To be done right, the Transform interface itself should probably be broken down into separate interfaces for each mechanism (dom, sax, String, Reader, etc) and each interface should have some sort of priority. Then the preceding transform (including the view) could figure out (when built) what the best mechanism to use would be. The hardest part, I think, would be dealing with SAX events because they work differently than anything else. XSLT-to-XSLT with SAX events requires building the chain backwards and would be tricky to accommodate. > Anyway, thanks again, I really am having a good time with Maverick. Glad to hear it! If you would like to take a stab at support for heterogeneous transforms, feel free to post any architectural questions. Or, if you want a more immediate response, my MSN Messenger address is my email address (AIM and Yahoo is "lhoriman", but less reliable 'cause I use Trillian for those services). If it works, we'll put it in Maverick 2.1 :-) Good luck, Jeff Schnitzer [EMAIL PROTECTED] _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
