Stupid trucking brain
-
Don't you hate it when you envision this beautiful, elegant system which you know will kick ass. Then you get down to implementing it and little stupid God-forsaken things make it less elegant. Stupid things like having to support ASP code in XML which naturally falls over when it finds <%. Or stupid things like XSL processing HTML code instead of just bloody well copying it to the output stream. Arrggh soon enough your system is still beautiful but behind it there are tons of string-and-pin functions which cater for all the daft CDATA problems. Aarrgghhh! It makes my blood boil. Why can't XML just accept trucking ASP!!! Aarrgghhhhhhhhhh... *sniff* still, the system is cool, just not as cool as I wanted it to be :( So who knows how to put ASP into XML elements WITHOUT having to use
<%? regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 Stormfront -
Don't you hate it when you envision this beautiful, elegant system which you know will kick ass. Then you get down to implementing it and little stupid God-forsaken things make it less elegant. Stupid things like having to support ASP code in XML which naturally falls over when it finds <%. Or stupid things like XSL processing HTML code instead of just bloody well copying it to the output stream. Arrggh soon enough your system is still beautiful but behind it there are tons of string-and-pin functions which cater for all the daft CDATA problems. Aarrgghhh! It makes my blood boil. Why can't XML just accept trucking ASP!!! Aarrgghhhhhhhhhh... *sniff* still, the system is cool, just not as cool as I wanted it to be :( So who knows how to put ASP into XML elements WITHOUT having to use
<%? regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 StormfrontI'm curious as to why exactly you would want to put ASP into XML elements?
-
I'm curious as to why exactly you would want to put ASP into XML elements?
MarSCoZa wrote: I'm curious as to why exactly you would want to put ASP into XML elements? I am working on a CMS (content management system) project. Authors of content are allowed to put ASP into their content and because all content is stored in XML files the XML must be able to contain ASP. Then that XML file is transformed using XSLT into XHTML and presented to the browser. regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 Stormfront
-
Don't you hate it when you envision this beautiful, elegant system which you know will kick ass. Then you get down to implementing it and little stupid God-forsaken things make it less elegant. Stupid things like having to support ASP code in XML which naturally falls over when it finds <%. Or stupid things like XSL processing HTML code instead of just bloody well copying it to the output stream. Arrggh soon enough your system is still beautiful but behind it there are tons of string-and-pin functions which cater for all the daft CDATA problems. Aarrgghhh! It makes my blood boil. Why can't XML just accept trucking ASP!!! Aarrgghhhhhhhhhh... *sniff* still, the system is cool, just not as cool as I wanted it to be :( So who knows how to put ASP into XML elements WITHOUT having to use
<%? regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 StormfrontPaul Watson wrote: and little stupid God-forsaken things make it less elegant Damn, Paul, didn't you have a design phase to account for all those little things? :omg: I am really shocked. :-D "Thank you, thank you very much" Elvis.
-
Paul Watson wrote: and little stupid God-forsaken things make it less elegant Damn, Paul, didn't you have a design phase to account for all those little things? :omg: I am really shocked. :-D "Thank you, thank you very much" Elvis.
Stan Shannon wrote: Damn, Paul, didn't you have a design phase to account for all those little things? I am really shocked. Har, har, har... X| Smar alec. Actually I am just dabbling in some pre-spec thought processes which happens to involve code. I have a great idea up here *taps my noggin* and I want to see what is possible before I start speccing fully. I am learning the technologies first :-D regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 Stormfront
-
MarSCoZa wrote: I'm curious as to why exactly you would want to put ASP into XML elements? I am working on a CMS (content management system) project. Authors of content are allowed to put ASP into their content and because all content is stored in XML files the XML must be able to contain ASP. Then that XML file is transformed using XSLT into XHTML and presented to the browser. regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 Stormfront
Paul Watson wrote: I am working on a CMS (content management system) project. Authors of content are allowed to put ASP into their content and because all content is stored in XML files the XML must be able to contain ASP. Then that XML file is transformed using XSLT into XHTML and presented to the browser. I started off on the same thing, and in the end, we found the most elegant solution to the problem. What we ended up with was our own server that took XML, processed it (by pulling certain stuff out of DBs, performing calcs, firing events from the browser) into more XML, then processed with XSLT and presented. So your problem is over come because instead of having people write ASP (and then having to re-process after you have transformed for the ASP to work) they would write XML, your own tags that formed a language. That is what we did. Worked fabulously for a first cut version. -- David Wengier
-
Paul Watson wrote: I am working on a CMS (content management system) project. Authors of content are allowed to put ASP into their content and because all content is stored in XML files the XML must be able to contain ASP. Then that XML file is transformed using XSLT into XHTML and presented to the browser. I started off on the same thing, and in the end, we found the most elegant solution to the problem. What we ended up with was our own server that took XML, processed it (by pulling certain stuff out of DBs, performing calcs, firing events from the browser) into more XML, then processed with XSLT and presented. So your problem is over come because instead of having people write ASP (and then having to re-process after you have transformed for the ASP to work) they would write XML, your own tags that formed a language. That is what we did. Worked fabulously for a first cut version. -- David Wengier
David Wengier wrote: So your problem is over come because instead of having people write ASP (and then having to re-process after you have transformed for the ASP to work) they would write XML, your own tags that formed a language. That sounds really cool. I even recommended that no HTML be used when Authors author their content. e.g. Instead of using
<P>they would use<PARA>and so on for all the structure tags. However they were not keen on the idea, maybe next phase. Also there are some pretty complex ASP driven forms on the site which need to be made available via the CMS to Authors who know ASP. It definitley was not an option replacing ASP with an XML based language as then a lot of their skills would have been lost. All in all we are providing a framework CMS in which they can create templates, content and input the odd bit of ASP (everything from simple dates via Now() to full blown data access via ASP.) David Wengier wrote: That is what we did. Worked fabulously for a first cut version. Do you sell it as a product or have any demos I can take a look at? regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 Stormfront -
David Wengier wrote: So your problem is over come because instead of having people write ASP (and then having to re-process after you have transformed for the ASP to work) they would write XML, your own tags that formed a language. That sounds really cool. I even recommended that no HTML be used when Authors author their content. e.g. Instead of using
<P>they would use<PARA>and so on for all the structure tags. However they were not keen on the idea, maybe next phase. Also there are some pretty complex ASP driven forms on the site which need to be made available via the CMS to Authors who know ASP. It definitley was not an option replacing ASP with an XML based language as then a lot of their skills would have been lost. All in all we are providing a framework CMS in which they can create templates, content and input the odd bit of ASP (everything from simple dates via Now() to full blown data access via ASP.) David Wengier wrote: That is what we did. Worked fabulously for a first cut version. Do you sell it as a product or have any demos I can take a look at? regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Sonork ID: 100.9903 StormfrontPaul Watson wrote: Do you sell it as a product or have any demos I can take a look at? Unfortunately no. It was a job I worked on while in R&D for a web developer. The product is still in use, but as an intranet, so its a bit hard to show you. What you said about not losing skills is very true. We had the opposite situation, where we wanted to allow people to alter the content without knowing ASP. -- David Wengier