[MGNLSTK-437] Show original code of a template in templates-resources (inplace templating) Created: 17/Aug/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: templates
Affects Version/s: 1.1.1
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Christian Ringele Assignee: Ondrej Chytil
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLSTK-436 Make inplace templating more usable Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When working with the STK templates in 'templates-resources' it would be very handy, if the original freemarker code would be displayed.
I mean that you always see the code which is used, it the option 'Enable Template' is deactivated - eg the original/unchanged code of the template.

I have seen people struggling while using the templates, because they cannot 'reset' the template to its origin state.
Seeing the original code would be very helpful for them too, because they could orientate on the origin code and start over again just by coping the origin code.



 Comments   
Comment by Boris Kraft [ 17/Aug/09 ]

I think a reset-button would do. Or we could turn on versioning (would be cool anyways) and thus people can simply choose an earlier version, up to the one bootstrapped.

Comment by Christian Ringele [ 17/Aug/09 ]

Yes, the reset button would do the most important of it.
But I think that for people who are not that familiar with freemarker code it still be quite useful to see the original code.
Like this you could always compare, and don't have to reset all the time when needed to see the original code.
And it would be possible to delete all the code and start from scratch. You always see what model class methods are provided by the original template shown.

Comment by Boris Kraft [ 17/Aug/09 ]

I think we shouldn't try to make inplace-templating a development environment - in other words, I expect people to be able to copy and paste the code into a real editor when using inplace templating; and compare it there instead of using the browser. As always our aim is to keep it simple by removing anything unessential.

Comment by Christian Ringele [ 25/Mar/13 ]

I think this is still a valid extension of the templating module.

It makes no sense it is still attached to me.
If these changes are still wanted by Boris, this is in better hands in maintenance.

Comment by Boris Kraft [ 25/Mar/13 ]

If we could enable versioning on this WS including the diff view it would be great. However, I don't see we should invest into the 4.x branch here. Only for 5 it would be interesting again. In that case we'd also add CMIS support so that people can actually work with the templates "like locally".

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:27:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.