Django

[django_pylons]

Hi,
I've been lurking on the pylons and TG discussion group for a while
every so often, to keep up with the status. However, I am no in a
position where I have to choose my poison so to speak!
Where I work we are currently mostly a Django shop, it's my fault but
we've been very productive just because of the admin (a god send!! ).
Other wise pylons would have been my first choice. However I've found
that recent versions of pylons is not in sync with the documentation
and it's hurting my ability to bring it in our shop. Which brings me
to TG2.

TG2 seems to have all I want, almost but mainly :

+ Webhelpers (they save a lot of time )
+ SQLAlchemy

(though no admin yet)

Now I have a few questions :

- can I start developping with TG2 now and not have to much backward
incompatible changes to worry about ? (I had woes with pylons in the
past )
- is TG2 stable enough to be put in production ? if not what does that
entail ?
- When will TG2 be production ready ? ( or what quirks can I expect
with a "non production ready" release)
- Can I use Mako templates ? and how ?
- any documentation on scalling a TG or TG2 app ?


Cheers,

Sjol

[django_pylons]

addendum :
I have a few questions about TG2 :

- how can I configure the application to use webhelpers, to expose it
as a global "h" ? (I've looked into app_globals.py but I did not seem
to pick things up. and can webhelpers and toscawidgets be mixed
together ?
- is there a list of the availalble function decorators ?

[Matt Wilson]

On Jul 21, 4:39 pm, django_pylons <s.jolico...@gmail.com> wrote:

> TG2 seems to have all I want, almost  but mainly :
>
> + Webhelpers (they save a lot of time )
> + SQLAlchemy

What are webhelpers?

Matt

[Felix Schwarz]

Matt Wilson wrote:
> What are webhelpers?

What about Google?
http://pylonshq.com/WebHelpers/

fs

Btw: No offense meant.

[Mark Ramm]

- can I start developping with TG2 now and not have to much backward
incompatible changes to worry about ? (I had woes with pylons in the
past )

We're working on making things less backwards incompatable than pylons (by moving a few things into the framework that pylons puts in generated code). 

Pylons is also getting very close to release 1.0, which means that they should be pretty stable now, so overall I think TG2 is not going to have a lot of backwards incompatable API changes.   And most of those will probably be centered around plugins, and other features that are slightly outside of "standard"

- is TG2 stable enough to be put in production ? if not what does that
entail ?

TG2 itself is stable, and the underlying components are all pretty much all used in production in various places.    Basically you can just run your tg2 wsgi app with any WSGI server from mod_wsgi to cherrypy3's wsgi server. 

 

- When will TG2 be production ready ? ( or what quirks can I expect
with a "non production ready" release)

We'll probably have stable 1.9.7 release in the next month or perhaps 2.  But people are already running the alpha1 in production in some places. 

 

- Can I use Mako templates ? and how ?

Yea, answered in a separate thread.

  

- any documentation on scalling a TG or TG2 app ?

Not a lot yet.  But this is one area we are working on. 

 

[Matt Wilson]

On Jul 22, 6:47 pm, Felix Schwarz <felix.schw...@web.de> wrote:
> Matt Wilson wrote:
> > What are webhelpers?
>

> What about Google?http://pylonshq.com/WebHelpers/

>
> fs
>
> Btw: No offense meant.

None taken. I had already read that page, but I was hoping for some
links to some real-world examples.

Matt

[Jorge Vargas]

basically any pylons app. a webhelper is a function that does
something so common almost everyone will use it.

it's inspired (everything before 0.6 was a direct port) of Ruby on
Rail's same concept.

Have you seen all those sites that say "Posted XX hours, XX minutes
and XX seconds ago", that one of the less useful ones, but other are
really helpful.

the best docs on webhelpers are in the source, and that's not because
it's badly documented but because it's just a bunch of functions you
will find useful, so you have to read them to know them.

> Matt
> >
>