But apparently, the original author is liking it much more so he's changed it back. I could be very nasty and keep changing it, but it would be great if we could just discuss and/or comment on changes being made to a wiki instead.
Yes I changed it back, because I think the original title fits the subject better than your edit, sorry. :) The purpose is not to show that you can use inline code, but more that you can extend XSLT with your own library using your language of choice.
Other than that it could be a great idea with a place to comment wiki changes
There's nothing wrong with expanding the article even further, I feel like the subjects are overlapping :) but perhaps we can come up with a third and better title then?
I agree code and presentation should be kept separate, but you can also import your own .NET namespaces using <msxml:assembly name=""/> and <msxml:using namespace=""/> so its actually just down to a matter of preference.
Crap! I'm so sorry Tim, but I clicked the downvote button! :( I can't correct myself, that sucks.
Another feature request coming.
@Simon It's more than preference for me, I should be able to debug, set breakpoints, etc. But most of all, I believe XSLT should be used properly, as a way to transform data, not as a way of encapsulating and executing source code.
If you need to program, then you might as well create a simple XSLT extension, that's a much more valid way of dealing with this. However, I do believe that doing some code inline has its place and the documentation should be on the wiki! My brain is not so creative today, so I am currently unable to think of a better title, I'll save it for later ;)
Wiki: Discussion or revision commenting
I am currently not agreeing with the title of this wiki page:
http://our.umbraco.org/wiki/reference/xslt/extend-your-xslt-with-custom-functions
But apparently, the original author is liking it much more so he's changed it back. I could be very nasty and keep changing it, but it would be great if we could just discuss and/or comment on changes being made to a wiki instead.
Any plans or ideas for this?
Yes I changed it back, because I think the original title fits the subject better than your edit, sorry. :) The purpose is not to show that you can use inline code, but more that you can extend XSLT with your own library using your language of choice.
Other than that it could be a great idea with a place to comment wiki changes
I understand, but I think it will be confused with a future wiki article, explaining how to make XSLT extensions.
Other than that, I am of the opinion that code should live in a dll and not in an XSLT, ever. But that's a whole different discussion! :-)
Hi,
I've already added this as a feature request:http://our.umbraco.org/forum/ourumb-dev-forum/features/2875-Add-discussion-for-Wiki-posts"> http://our.umbraco.org/forum/ourumb-dev-forum/features/2875-Add-discussion-for-Wiki-posts
Vote there to push this up the list of feature to be implemented!
I think this is a really important area, otherwise we'll be in rollback war hell in no time, with little indication on what was changed or why.
T
http://our.umbraco.org/forum/ourumb-dev-forum/features/2875-Add-discussion-for-Wiki-posts">
There's nothing wrong with expanding the article even further, I feel like the subjects are overlapping :) but perhaps we can come up with a third and better title then?
I agree code and presentation should be kept separate, but you can also import your own .NET namespaces using <msxml:assembly name=""/> and <msxml:using namespace=""/> so its actually just down to a matter of preference.
Crap! I'm so sorry Tim, but I clicked the downvote button! :( I can't correct myself, that sucks.
Another feature request coming.
@Simon It's more than preference for me, I should be able to debug, set breakpoints, etc. But most of all, I believe XSLT should be used properly, as a way to transform data, not as a way of encapsulating and executing source code.
If you need to program, then you might as well create a simple XSLT extension, that's a much more valid way of dealing with this. However, I do believe that doing some code inline has its place and the documentation should be on the wiki!
My brain is not so creative today, so I am currently unable to think of a better title, I'll save it for later ;)
is working on a reply...