subprojects that we could give back to django

[Evgeny]

I think it's cool when a project generates spinoffs. so we might
package some things as separate applications or libraries.

for example:

* signon system
* skinnable feature
* reputation system

here's one more idea - google closure library works with a templating
engine called "soy".

currently soy templates can be rendered by javascript and java. would
be super cool to use those templates in python - but there is no
parser yet.

so templates like that in theory (and in practice - in Java) can be
rendered both on server side and client side.

somebody brave enough should create soy parser in python!

[Adolfo Fitoria]

2010/3/26 Evgeny <evgeny...@gmail.com>:

> I think it's cool when a project generates spinoffs. so we might
> package some things as separate applications or libraries.
>
> for example:
>
> * signon system

This is something we could give back, currently there is a lot of
django-registration, django-openid and so on... why not a universal
user system?
> * skinnable feature
Build a templating framework??

> * reputation system
>
> here's one more idea - google closure library works with a templating
> engine called "soy".

Is this "soy"? http://code.google.com/closure/templates/

>
> currently soy templates can be rendered by javascript and java. would
> be super cool to use those templates in python - but there is no
> parser yet.
>
> so templates like that in theory (and in practice - in Java) can be
> rendered both on server side and client side.
>
> somebody brave enough should create soy parser in python!
>

> To unsubscribe from this group, send email to askbot+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>

--
Adolfo Fitoria
http://fitoria.net

[Evgeny]

Hey Adolfo,

yes that's soy
http://code.google.com/closure/templates/
The benefit of this is that you can render pages on the server and
client side using the same templates and build real dynamic web
applications much easier.

on skins.

There is actually skin implementation in our code. It's just a method
of template and media resolution,
based on the default skin setting. You can't yet switch skins on the
fly, but there must be an easy hack for that.

It more or less works. Now skins can be created by adding more to
directory forum/skins following the pattern.

But what I thought that that feature could be packaged as a django
"app", well just an addon since it does not
yet use models and views.

I''ve pushed out a baseline commit, btw.

Cheers,
Evgeny.

On Mar 27, 11:36 am, Adolfo Fitoria <adolfo.fito...@gmail.com> wrote:
> 2010/3/26 Evgeny <evgeny.fad...@gmail.com>:> I think it's cool when a project generates spinoffs. so we might

> > package some things as separate applications or libraries.
>
> > for example:
>
> > * signon system
>
> This is something we could give back, currently there is a lot of
> django-registration, django-openid and so on... why not a universal
> user system?> * skinnable feature
>
> Build a  templating framework??> * reputation system
>
> > here's one more idea - google closure library works with a templating
> > engine called "soy".
>

> Is this "soy"?http://code.google.com/closure/templates/