On Thu, Dec 11, 2008 at 7:08 PM, Iain Duncan wrote:
>
> On Thu, 2008-12-11 at 15:21 -0600, Jorge Vargas wrote:
>>
>> On Wed, Dec 10, 2008 at 11:44 PM, Chris Miles wrote:
>> >
>> >
>> > On 11/12/2008, at 4:36 PM, Mark Ramm wrote:
>> >
>> >>> I assume Beaker is also the recommended caching solutio
On Thu, 2008-12-11 at 15:21 -0600, Jorge Vargas wrote:
>
> On Wed, Dec 10, 2008 at 11:44 PM, Chris Miles wrote:
> >
> >
> > On 11/12/2008, at 4:36 PM, Mark Ramm wrote:
> >
> >>> I assume Beaker is also the recommended caching solution for
> >>> TG2, but would like clarification.
> >>
> >> Yes, b
On Thu, Dec 11, 2008 at 10:21 PM, Jorge Vargas wrote:
>
> On Wed, Dec 10, 2008 at 11:44 PM, Chris Miles wrote:
>>
>>
>> On 11/12/2008, at 4:36 PM, Mark Ramm wrote:
>>
I assume Beaker is also the recommended caching solution for
TG2, but would like clarification.
>>>
>>> Yes, beaker is
On Wed, Dec 10, 2008 at 11:44 PM, Chris Miles wrote:
>
>
> On 11/12/2008, at 4:36 PM, Mark Ramm wrote:
>
>>> I assume Beaker is also the recommended caching solution for
>>> TG2, but would like clarification.
>>
>> Yes, beaker is the built in caching mechanism of TG2. Beaker supports
>> memcache
I totally agree with this. I had started using tg2 with only some
background of tg1 and with no background of pylons behind me and I
found that I could use tg2 to a large extent without problems.
Fortunately when I had started on TG1 about 2 years back, I had
started using tg1 along with SA as th
Of course Pylons knowledge doesn't harm.
However, it is a little bit the other way around.
I have now two webapps running TG2 and didn't use any Pylons before:
TG2 is good jump into Pylons. It has a good quickstart template
and chooses reasonable defaults.
Setting some components as defaults also
On 11/12/2008, at 4:36 PM, Mark Ramm wrote:
>> I assume Beaker is also the recommended caching solution for
>> TG2, but would like clarification.
>
> Yes, beaker is the built in caching mechanism of TG2. Beaker supports
> memcached, and lots of other back-ends. It also doesn't suffer from
> t
> I assume Beaker is also the recommended caching solution for
> TG2, but would like clarification.
Yes, beaker is the built in caching mechanism of TG2. Beaker supports
memcached, and lots of other back-ends. It also doesn't suffer from
the so-called dog-pile effect i the same way as some ot
On 11/12/2008, at 1:47 AM, Mark Ramm wrote:
>
>> I'm very interested to hear about how TG2 will avoid the scaling and
>> traffic issues that hit pownce and twitter.
>
> Well, there are lots of issues, and without being super-connected to
> either Twitter or Pownce, one of the things that seems t
Timur Izhbulatov schrieb:
> I feel that my impressions of learning TG 2 are getting stale. I'm
> going to share some random notes with you (and everybody else) before
> it's to late... :) Sorry for long email.
Thanks for writing this up. So it seems we will need a "everything a TG2
user needs to
On Wed, 2008-12-10 at 09:47 -0500, Mark Ramm wrote:
>
> > I'm very interested to hear about how TG2 will avoid the scaling and
> > traffic issues that hit pownce and twitter.
>
> Well, there are lots of issues, and without being super-connected to
> either Twitter or Pownce, one of the things th
> I'm very interested to hear about how TG2 will avoid the scaling and
> traffic issues that hit pownce and twitter.
Well, there are lots of issues, and without being super-connected to
either Twitter or Pownce, one of the things that seems to have
happened to both early on is that it was difficu
On Dec 9, 12:58 am, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
>
> TurboGears 2 is somewhat uneque in the modern web framework space in
> that it attempts to provide solutions for the archetectual problems
> that limited sites like Pownce, Twitter, and TG1 sites, that I've
> worked on in the past.
I'
On Wed, Dec 10, 2008 at 2:59 AM, Iain Duncan <[EMAIL PROTECTED]> wrote:
>
>> > I assume this means rather than TG 1.9.7.beta3, we'll be seeing TG
>> > 2.0.0.beta1 next right?
>>
>> Seems about right, and that was the plan.
>>
>> Though I'm not opposed to keeping the numbering scheme we have now
>>
On Tue, 2008-12-09 at 18:45 -0500, Mark Ramm wrote:
>
> > On Dec 8, 11:58 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
> >> I'd like to propose that we declare the next stable TG2 release 2.0
> >> and that we work together to get a release candidate by the end of the
> >> year.
> >
> > I assume thi
2008/12/10 Christoph Zwerschke <[EMAIL PROTECTED]>:
>
> Mark Ramm schrieb:
>> If you're interested in joining this support team, please let us know.
>> If you think you can help get it organized and make sure that it
>> runs smoothly defintely let us know.
>
> It's good to see TG2 making progress
On Tue, Dec 9, 2008 at 5:45 PM, Mark Ramm <[EMAIL PROTECTED]> wrote:
>
>> On Dec 8, 11:58 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
>>> I'd like to propose that we declare the next stable TG2 release 2.0
>>> and that we work together to get a release candidate by the end of the
>>> year.
>>
>> I
> On Dec 8, 11:58 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
>> I'd like to propose that we declare the next stable TG2 release 2.0
>> and that we work together to get a release candidate by the end of the
>> year.
>
> I assume this means rather than TG 1.9.7.beta3, we'll be seeing TG
> 2.0.0.beta
One more quick thought...
On Dec 8, 11:58 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote:
> I'd like to propose that we declare the next stable TG2 release 2.0
> and that we work together to get a release candidate by the end of the
> year.
I assume this means rather than TG 1.9.7.beta3, we'll be see
> I think the main reason why I didn't really
> look into TG 2 so far was that I never used Pylons, so I feel I first
> need to get aquainted with Pylons, but haven't found the time so far. It
> would be nice to have a kind of Pylons crash course available, or a
> "everything a TG user needs to k
Mark Ramm schrieb:
> If you're interested in joining this support team, please let us know.
> If you think you can help get it organized and make sure that it
> runs smoothly defintely let us know.
It's good to see TG2 making progress. So far I've focused on TG 1.x
which I'm using for my produ
> I'd love to see a final/stable release for 2.0, however I would ask
> you to please hold off at least until all your dependencies have their
> own stable releases. Most importantly SQLAlchemy and Pylons, which are
> both in beta/RC phases still. I'm sure we're still a few months away
> from TG2.
Mark,
As a user, I tend to think of using TurboGears as not only a
framework, but kind of like a full out distribution. I prefer to use
the packages you guys include in your own repo, rather than pull
individual components myself to make sure it's all as stable as
possible.
I'd love to see a fin
23 matches
Mail list logo
