Django, Rails and ASP.Net, all have community-generated 'template' 
(scaffolding) apps and demo-apps for many of the popular client-side 
frameworks that had emerged in the last 2-3 years.
The Breeze middle-ware, also has many different front-ends and back-ends 
integration examples.

Does web2py have a repository that exemplifies specific
 frameworks-integration?

I know about the plugins repository, and the built-by-web2py website, but 
It's not exactly what I'm looking for - it's not a substitute, but a 
complementary kind of repository.
It's one thing to have examples that express different *internal*capabilities 
of your framework, and have components that people can use as 
a starting-point for implementing their own solution using the same 
mechanism. It's another thing entirely to have different 
starting-point-apps, each targeting a different client-side framework.

The 'Welcome' app has notoriously been a target for endless debates of 
weather or not to add this-or-that library-support, but I think we've been 
going about it in the wrong way - it's not about a 
'single-welcome-app-to-rule-hem-all' - it's about variety - it's about 
options.

If you are, say, an Angular.js developer, looking for a back-end solution, 
you're going to look for server-side solutions that already have "examples" 
that integrate-well with your client-side frameworks. It is so prevelant 
these days, that it has become something to be expected. You are not going 
to go through the due-diligence of coming-up with an integration yourself, 
especially when you don't know the server-side framework well enough to do 
so to begin with....
You are thus going to choose Django, or RoR, or ASP.Net-MVC - just because 
there are already existing scaffold-apps implementing the integration for 
that server-side framework (the plumbings). You are NOT going to choose 
web2py, and NOT because it is a poorer choice (it isn't), and NOT even 
because it is difficult to implement such an integration (you are not going 
to know that it isn't...).

Conversely, If you are a web2py all-around-web-developer, waning to write, 
say, an Ember.js app, you are going to look for a scaffold that already 
shows how to do that.
And you are not going to find any... At least I haven't...

This is really unfortunate...

I think it is really detrimental to web2py's popularity.

I am in an on-going process of researching SPA frameworks in order to make 
a decision on weather or not it is worth the effort of converting our 
existing web2py into using one of those, as our client-side code is in sour 
need of 'structure' for maintainability and testability.

I have already learned quite a lot about Backbone, Angular, Ember and 
Durandal (which uses Knockout among others). But I keep coming back to this 
question of - which one would be most suited for web2py as a back-end? 
Which could be best integrated with it?

And I can't seem to get an answer to that, as there are no examples to go 
through to figure it out.

And so, instead of just ranting, I decided to do something about it.
But I will not be able to do that alone - I'm going to need help.

My plan is to start a few projects, that show how these client-side 
frameworks can interact with web2py, and in the process, generate some 
'client-side-framework'-specific code in python using web2py 

I call it " js2py ", which is an umbrella-term describing different 
'javascript-framework-target'-projects' for web2py - for example:

"Ember2py" - Would be the name of a project entailing integration-code for 
Ember.js.
"Angular2py" - Would be the same for Angular.js.
"Durandal2py" - Would be the same for Durandal.js
Etc...

I am going to start with Durandal, but before that, there would have be 2 
smaller projects: "Require2py" and "Knockout2py" - As requier.js and 
knockout.js are pre-requisites of Durandal.js.
 
In a similar manner, for Ember.js, there is going to have to be a 
pre-project of "Handlebars2py" and/or "Emblem2py" for integrating web2pt's 
views with Ember's template-technologies.

For Angular2py and Knockout2py, there will be targeted sub-classes for the 
HTML-Helpers, for adding attributes more conveniently - either in the 
controller-actions and/or the Python code in the views.

I already toyed with the idea a while back, and got Massimo's blessing... :)

So, It's going to be an interesting, challenging and exciting ride...

Who's with me?

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to