On 7/22/06, Jorge Vargas <[EMAIL PROTECTED]> wrote:
XML() filtered the output into the kid template such that the '<' was replaced with < so the XML was displayed rather than being embedded into the HTML page. At other times when the XML passed through to the output, all the attributed were upper-cased and the name spaces were mangled. Plex could not operate on the XML because of that.
Mansi and I tried a lot of varitions to try to get the XML that was 'displayed' to be the
XML that was embedded...
After about 4 or 5 days of experimenting with kid, I went to cheetah and had the results
I needed in about an hour.
I tried that but it didn't work either. We also tried xhtml, plain and what ever we could think
of. I think it's because we are trying to embed XML in an HTML document. XML is not the exposed output, html is.
Right now I am working on wrapping the Plex widgets I want to use in my project. Once I have that I think I'll give kid another shot.
I can wrap up a small test case tomorrow if you care to look?
Nicky
On 7/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Apologies for the long post.I was able to use it to embed pure XML into an HTML page very quickly.
(I could not find a way to get it to work using Kid.)
why didn't the XML() work?
XML() filtered the output into the kid template such that the '<' was replaced with < so the XML was displayed rather than being embedded into the HTML page. At other times when the XML passed through to the output, all the attributed were upper-cased and the name spaces were mangled. Plex could not operate on the XML because of that.
Mansi and I tried a lot of varitions to try to get the XML that was 'displayed' to be the
XML that was embedded...
After about 4 or 5 days of experimenting with kid, I went to cheetah and had the results
I needed in about an hour.
I wanted to use the PXTK js library in a gui we are working on and used it as a reason
to go through the JS library packaging screencast. (Thanks for that,
Kevin. Well worth the cost of the DVD ) It worked like a charm. As I
mentioned in a previous post, the system seems to require embedding xml
on the HTML page. While trying to create TG widgets for the
coresponding PXTK widgets I ran across a lot of issues that are most
likely due to my lack of understanding of Kid. In any case, I turned
to TurboCheetah and I have the results that I want.
Did you change the default kid serializer to output XML instead of html?
I tried that but it didn't work either. We also tried xhtml, plain and what ever we could think
of. I think it's because we are trying to embed XML in an HTML document. XML is not the exposed output, html is.
if you will like support for those please post the problems and we can create that set of widgets.
Right now I am working on wrapping the Plex widgets I want to use in my project. Once I have that I think I'll give kid another shot.
I can wrap up a small test case tomorrow if you care to look?
Nicky
--
--
Nicky Ayoub
G-Mail Account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
