Agreed! I'm not too keen on this idea but have been searching for a
solution to better encapsulate my code and assets. I do not consider domo
the answer, but was an interesting idea.
Something we are doing in prototype with the Template class does put HTML
markup directly into the JS code. I
At Mad Mimi I created an extension to Template which looks something like
this:
Template.from = function(id) {
if(!$(id)) {
console.warn(Missing template for + id);
} else {
return new Template($(id).innerHTML.replace(/%23%7B(.*)%7D/g, #{$1}));
}
};
Then in your HTML you'd have
Domo
http://domo-js.com/
From the J2EE developer's point of view it looks like return back to 2000s,
to Servlets and tons of HTML/CSS markup in code. IMHO all advanced Java
developers agree that moving HTML markup from Java code into separate JSP
files was great step forward.
--
You
What is domo? Share a link please.
--
You received this message because you are subscribed to the Google Groups
Prototype script.aculo.us group.
To view this discussion on the web visit
https://groups.google.com/d/msg/prototype-scriptaculous/-/_0QkXgH3wG4J.
To post to this group, send email
Domo
http://domo-js.com/
I'm also looking at Eyeballs and Choco as possible, MVC like, frameworks to
sit on top of Prototype.
https://github.com/paulca/eyeballs.js
https://github.com/ahe/choco
On Friday, November 16, 2012 2:08:23 AM UTC-7, Victor wrote:
What is domo? Share a link please.
--
Here's sample code:
http://pastie.org/5388646
On Friday, November 16, 2012 8:28:33 AM UTC-7, kstubs wrote:
Domo
http://domo-js.com/
I'm also looking at Eyeballs and Choco as possible, MVC like, frameworks
to sit on top of Prototype.
https://github.com/paulca/eyeballs.js
