Multiple instances of the same template at the same page

[himikel]

Hi Carles & mindtouchers
Because the separation of concerns, the CoDoer framework have two layers, the engine templates & the widget templates.
We can move the engine templates to "Template:" namespace with no problems.

But nowadays we have two main problems to move widget templates to "Template:" namespace
1- We can't run the templates inside "Template:" namespace
a) then we can't test the widgets directly (to see the difference with Calculator widget: outside template, inside template)
b) then we can't reuse the widgets as helpers to do the designing/programming tasks easier

2- We love WYSIWYG design (great designed in DekiWiki), and outside of "Template:" namespace we can hide programming code and do the work of design more easy to non programmer users. (to see the difference with TodoList widget: outside template, inside template)

Other fundamental difference is the organization of the templates, about this we think that its implementation have some pros & cons:
The Pros about outside namespace are that users can organize templates as he/she likes (inside user/general namespaces, mixed with regular pages, etc.). The cons are that i like to have all the templates well organizated in one place. Why not two options?

We need to think more about the posibilities, but thus far, these are the handicaps that we've found related to this issue.
We'll appreciate any suggestion or opinion
thanks!!
@himikel - CoDoer framework co-creator

[carles.coll]

Hi himikel,

Just a hint in spanish: "No estáis intentando matar moscas a cañonazos?" trying to put MVC to just do Widgets, Or it's just for fun?

Just an advice: take care of Poor Template performance with this added layer.

Carles.

[himikel]

Hi Carles, good question
We think that all the layers that we are using add value: OS, Apache2, Dream, DekiWiki back-en, DekiWiki front-end, CoDoer engines, CoDoer Widgets
We're designing CoDoer framework following the best practices that we've learned in our 20 years or programming experience (better or poorer), and our building process is based in "learning by doing", then we're designing a innovative & useful tools with a open distributed collaborative goal, and avoiding technical/non-technical users gap (from bottom to up but reusing upper architectures)

We've adapted a Calculator widget designed for Android, you can see building process & code here and then see a tutorial of our process in our MindTouch blog.
Then, i'll propose you a exercise to develop the same widget in three different ways:
1- Using regular dekiscript
2- Using CoDoer framework (considering that still is an experiantial alpha release)
3- Using Android framework
And measuring the time you take to do it in each of these.

I raise you a question: do you think that Android framework is a simple implementation to build widgets...?
What you propose to make it simpler?

About the performance, yes this is a handicap, in the server side we think that cache will help it, and in the other hand, you know that interactive applications move a lot of the code to client part, and this is a regular JavaScript performance issue that we are trying to manage.

thanks Carles, you help us a lot with your great InteractiveComments template
hugs!
@himikel - CoDoer framework co-creator

[carles.coll]

Just do it all in Javascript, it will work on both platforms ( Android & Mindtouch ) also, iOS, drupal, joomla,....

[himikel]

Ok Carles, is a possibility
But then we would need to reimplement all the great collaborative/distributive capabilities that DekiWiki has well implemented, furthermore we can make a best architecture that Android/iPhone has using a distributed systems (not centralized), simply co-creating it
We use DekiScript language because is a easy maintainable and based in a powerful RESTful wiki, but in our 4th step of Codoer framework we inject a lot of JavaScript/jQuery code to the Controller layer to provide interaction capabilities, and in following steps will use all the power of RESTful architecture
@himikel - CoDoer framework co-creator