On 8/31/07, Fernando Padilla <[EMAIL PROTECTED]> wrote: > Yes I've been looking all over the code. Right now I think that I have > two options. Could I get some more feedback? > > 1) hack :) > write a mixin that will go through the dom after rendering and > replace element/attribute names with desired versions: "fm_fbml" to > "fb:fbml". This is how I'll start, but it would be much better to have > tapestry support namespaces properly. > > 2) start submitting patches to have tapestry support namespaces: > a) Maintain Namespace in Tapestry DOM > 1) add url to tapestry.dom nodes > 2) have tapestry parser set them > 3) the information will be available for mixins/components > b) We can then print them out, by default or by configuration > 1) generate url/prefix mappings > 2) print them out as appropriate > 3) have some way to have desired prefixes > ( or somehow pull them out from the original template ).
I am in a similar position, wanting to develop a facebook app in Tapestry 5. Have you made any progress on this yet? Option 2 sounds like the best one but I agree its a fair bit more work. I have just tried (as a hello world) to feed the tutorial 1 first app to facebook as FBML on my canvas page. The Facebook FBML parser throws an error because Tapestry has generated an HTML (as would be expected). But the <html> tag is not on the allowed subset of HTML which is part of FBML. I was wondering if you had come across this or if anyone else knows a solution to this? Chalie M --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
