search

Imagio / mvc-mini-profiler

Automatically exported from code.google.com/p/mvc-mini-profiler
0 stars 0 forks source link

jquery Templates #118

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Trying to use the new version of jQuery Templates (jsRender)

What is the expected output? What do you see instead?
I am getting an error message as the two templating engines are not compatible.

Are you planning on using the new version of the templating engine anytime 
soon? I know it's still in "beta", but so was the other and the other is dead. 
Now I cannot use both the new one and the mvc-mini-profiler together as the 
templating engines collide.

Original issue reported on code.google.com by jamier....@gmail.com on 1 Nov 2011 at 1:07

GoogleCodeExporter commented 8 years ago 
Another vote for this, I think it should be high priority. The jQuery Templates 
project is now dead, so more people will be using jsrender in their projects, 
as I am doing. The two don't work together, and it wastes good time debugging 
why jsRender isn't working. The Mini Profiler shouldn't interfere with anything 
in a project.

If somebody could outline the preferred way ahead for this, I may be able to 
spend a few hours on it as I need it to work. Options may be:

- Modify the jQueryTemplate file used in the Mini Profiler to not clash with 
jsRender

- Allow jQueryTemplates or jsRender to be used and maintain two separate 
versions of the template(s)

- Move over fully to jsrender. (Will likely create the reverse problem for 
existing jQueryTemplate users)

The best all-round option may be to add another default parameter on to 
RenderIncludes(), jsRenderCompatible = false. If false, keep things exactly as 
they are now. If true, include a modified version of jQueryTemplate that does 
not clash with jsRender.

Original comment by conceptd...@gmail.com on 7 Jan 2012 at 9:23

GoogleCodeExporter commented 8 years ago 
my ideal solution is a standalone templating piece that can be loaded side by 
side with any templating engine the user loads

One approach may be to stub out all the jQuery extension points and have a 
single obscurely named method for all the templating needs.

Original comment by sam.saff...@gmail.com on 13 Feb 2012 at 6:09

GoogleCodeExporter commented 8 years ago 
I went ahead and made us a standalone templating bit by renaming a whole bunch 
of methods, I think it should play nice now

Original comment by sam.saff...@gmail.com on 13 Feb 2012 at 6:47

GoogleCodeExporter commented 8 years ago

Original comment by sam.saff...@gmail.com on 13 Feb 2012 at 6:47