Re: Feature: Template Components

2015-06-11 Thread Emil Stenström
On Wednesday, 10 June 2015 02:55:46 UTC+2, Curtis Maloney wrote: > > This sounds a bit like combining django-sniplates with django-amn, and > going a bit further... > > Fragments of templates, list of JS/CSS dependencies, and a way to collect > it all together and ensure your page has everything

Re: Feature: Template Components

2015-06-09 Thread Curtis Maloney
This sounds a bit like combining django-sniplates with django-amn, and going a bit further... Fragments of templates, list of JS/CSS dependencies, and a way to collect it all together and ensure your page has everything you need... Sounds interesting to me... I'd be happy to collaborate on it wi

Re: Feature: Template Components

2015-06-09 Thread Emil Stenström
On Tuesday, 9 June 2015 13:21:27 UTC+2, Yoong Kang Lim wrote: > > This seems like a huge change. If you were to include this feature in > Django, would it be straightforward for users to migrate from previous > versions? > What I'm suggesting is not a huge change. I'm just saying that Django sh

Re: Feature: Template Components

2015-06-09 Thread Sam Solomon
Speaking only for myself and the component framework we built here, I don't think I would expect it to ever be rolled into Django itself. However, the framework we made does work without any modifications to Django and works just fine alongside existing function and classed based views. This me

Re: Feature: Template Components

2015-06-09 Thread Yoong Kang Lim
This seems like a huge change. If you were to include this feature in Django, would it be straightforward for users to migrate from previous versions? On Sunday, May 31, 2015 at 2:52:37 AM UTC+10, Emil Stenström wrote: > > Hi, > > This is the first feature proposal as part of my general drive

Re: Feature: Template Components

2015-06-02 Thread Sam Solomon
If someone actually wants to use it I can set aside some time within the next week or two to actually open source the whole thing (docs + source on github/pypi). Here is an example of some of the basic functionality though: *What the following code does:* Creates a page for taking attendance of s

Re: Feature: Template Components

2015-06-01 Thread Emil Stenström
On Monday, 1 June 2015 19:12:36 UTC+2, Sam Solomon wrote: > > So a former co-worker with some help/guidance from me developed a > component system on top of Django that sounds sorta like what you are all > talking about. It's very complicated and I'm still not sure whether it was > ultimately a

Re: Feature: Template Components

2015-06-01 Thread Emil Stenström
On Monday, 1 June 2015 03:32:26 UTC+2, Rotund wrote: > > I actually think this is a great idea. In my mind it parallels Drupal's > "block" idea. (This is actually what I keep hoping DjangoCMS is.) > > That stated, it is more of a construct. I think a great idea is to make an > extension module. >

Re: Feature: Template Components

2015-06-01 Thread Sam Solomon
So a former co-worker with some help/guidance from me developed a component system on top of Django that sounds sorta like what you are all talking about. It's very complicated and I'm still not sure whether it was ultimately a good idea to use or not, but it does make some things very simple (

Re: Feature: Template Components

2015-06-01 Thread Unai Zalakain
Finally someone expressed my own feelings about it perfectly :D On Sun, May 31, 2015 at 08:32:18PM -0500, Joe Tennies wrote: I actually think this is a great idea. In my mind it parallels Drupal's "block" idea. (This is actually what I keep hoping DjangoCMS is.) That stated, it is more of a con

Re: Feature: Template Components

2015-05-31 Thread Joe Tennies
I actually think this is a great idea. In my mind it parallels Drupal's "block" idea. (This is actually what I keep hoping DjangoCMS is.) That stated, it is more of a construct. I think a great idea is to make an extension module. I don't know how long you've been in this community, but Django is

Re: Feature: Template Components

2015-05-31 Thread Emil Stenström
On Sunday, 31 May 2015 11:36:51 UTC+2, riccardo.magliocchetti wrote: > > Il 31/05/2015 11:00, Emil Stenström ha scritto: > > On Sunday, 31 May 2015 10:27:24 UTC+2, riccardo.magliocchetti wrote: > > Il 30/05/2015 18:52, Emil Stenström ha scritto: > > But your proposal keeps html and js se

Re: Feature: Template Components

2015-05-31 Thread Riccardo Magliocchetti
Hi Emil, Il 31/05/2015 11:00, Emil Stenström ha scritto: Hi, On Sunday, 31 May 2015 10:27:24 UTC+2, riccardo.magliocchetti wrote: Hi, Il 30/05/2015 18:52, Emil Stenström ha scritto: But your proposal keeps html and js separated. I think you are solving a problem for the on

Re: Feature: Template Components

2015-05-31 Thread Emil Stenström
Hi, On Sunday, 31 May 2015 10:27:24 UTC+2, riccardo.magliocchetti wrote: > > Hi, > > Il 30/05/2015 18:52, Emil Stenström ha scritto: > > Hi, > > > > This is the first feature proposal as part of my general drive for > getting > > Django to work better for javascript heavy sites. > > This is

Re: Feature: Template Components

2015-05-31 Thread Riccardo Magliocchetti
Hi, Il 30/05/2015 18:52, Emil Stenström ha scritto: Hi, This is the first feature proposal as part of my general drive for getting Django to work better for javascript heavy sites. This is a bold premise :) Template Components --- React.js popularized the notion that in fro

Feature: Template Components

2015-05-30 Thread Emil Stenström
Hi, This is the first feature proposal as part of my general drive for getting Django to work better for javascript heavy sites. Template Components --- React.js popularized the notion that in front-end development, code organization should be based on interface components, n