Please explain me why this is API change?
old code
http://trac.turbogears.org/browser/projects/tg.devtools/trunk/devtools/templates/turbogears/%2Bpackage%2B/websetup.py_tmpl?rev=6511
new code
On Mon, Mar 23, 2009 at 12:35 PM, dimaz...@gmail.com dimaz...@gmail.com wrote:
Hello,
I'm interested in a TurboGears CMS development for this GSOC.
I would suggest you join forces with this
http://bitbucket.org/jon1012/tgextpages/
which is a light CMS we are working on and which extends any
Am I doing something fundamentally wrong or is there a problem with the
validate decorator in TG 2.0rc1?
I'm using it in the very basic way as described here:
http://turbogears.org/2.0/docs/main/Validation.html#validating-arguments-without-form-widgets
To reproduce the problem, quickstart an
We now have 2.0 branches for both tg.devtools and the main tg code.
These branches are ONLY for bugfixes, docstring improvements and other
changes that belong in the 2.0 release.
That means 2.1 work can get started in trunk right now. :) And in
fact there's already a 2.1 feature that have
Ouch, this sounds bad.
I will look into it as soon as I get a break at work.
If somebody else could take a look that would be great!
On Mon, Mar 23, 2009 at 9:48 AM, Christoph Zwerschke c...@online.de wrote:
Am I doing something fundamentally wrong or is there a problem with the
validate
Actually, not so bad. You can validate get parameters, or post
parameters but not URL args.
This is something we need to work out for 2.1 because it's now come up
two or three times.
On Mon, Mar 23, 2009 at 9:48 AM, Christoph Zwerschke c...@online.de wrote:
Am I doing something
i managed to understand the soprovider structure but i still didn't
find where the table tg_user_group was defined so i can define the
tg_user_role table
i used the related join with tg_user _role but it din't work as i
expected :s
plz help thx
On Mon, Mar 23, 2009 at 7:35 AM, dimaz...@gmail.com dimaz...@gmail.com wrote:
Hello,
I'm interested in a TurboGears CMS development for this GSOC.
Idea mentions the CMS itself and the library of CMS components which
should be extensible outside the CMS framework.
I see it as some minimal
Honestly guys, if you want a bug for this change I can produce one in
about 30 seconds.
$ paster quickstart tgtest
$ cd tgtest
$ paster setup-app development.ini
change model
$ pastser setup-app development.ini
error ensues
My change fixes this bug and is a minor refactor. This is the biggest
I can probably fix this next week with the dispatch refactor. I will
take a special note of it.
cheers.
-chris
On Mar 23, 9:15 am, Mark Ramm mark.mchristen...@gmail.com wrote:
Actually, not so bad. You can validate get parameters, or post
parameters but not URL args.
This is something we
On Monday March 23, 2009 16:58:17 Jorge Vargas wrote:
On Mon, Mar 23, 2009 at 8:02 AM, Gustavo Narea m...@gustavonarea.net wrote:
On Monday March 23, 2009 07:29:54 Jorge Vargas wrote:
Please explain me why this is API change?
snip
please tell me how the calling code changes from A to B ?
On Mar 23, 1:18 pm, Florent Aide florent.a...@gmail.com wrote:
On Mon, Mar 23, 2009 at 12:35 PM, dimaz...@gmail.com dimaz...@gmail.com
wrote:
Hello,
I'm interested in a TurboGears CMS development for this GSOC.
I would suggest you join forces with
On Mar 23, 5:08 pm, Jorge Vargas jorge.var...@gmail.com wrote:
On Mon, Mar 23, 2009 at 7:35 AM, dimaz...@gmail.com dimaz...@gmail.com
wrote:
I see it as some minimal core application (cms), to which components
are plugged in. In the best case everything should be a pluggable
This has taken way too long and it's way out of topic. I won't bother
answering inline anymore. If you want to think it's api change then
fine go ahead this is no api at all as you don't even need quickstart
to have a TG2 project. If you keep insisting it changes the API fine I
won't argue about
On Mon, Mar 23, 2009 at 3:59 PM, dimazest dimaz...@gmail.com wrote:
On Mar 23, 1:18 pm, Florent Aide florent.a...@gmail.com wrote:
On Mon, Mar 23, 2009 at 12:35 PM, dimaz...@gmail.com dimaz...@gmail.com
wrote:
Hello,
I'm interested in a TurboGears CMS development for this GSOC.
I
On Mon, Mar 23, 2009 at 4:05 PM, dimazest dimaz...@gmail.com wrote:
On Mar 23, 5:08 pm, Jorge Vargas jorge.var...@gmail.com wrote:
On Mon, Mar 23, 2009 at 7:35 AM, dimaz...@gmail.com dimaz...@gmail.com
wrote:
I see it as some minimal core application (cms), to which components
are
Look, it was my choice to make this happen, and I stand by it.
We can tell people installing pages to update websetup.py as
nessisary, and the people reading the python magazine article can use
code that just works.
And from my perspective the code inside the quickstart--that we intend
for
The TurboGears Development team is proud to announce TG2 Release
Candidate 1 just in time for pycon.
This is a huge milestone for us, and I'm personally very proud that
we've made it here. This is the culmination of a long, challenging,
and fun, process of re-creating TurboGears to solve many of
Yea, that was my fault, I got hard-core about the feature freeze only
after I first encouraged adding the new feature. In my defense, I
wanted that new feature ;) And also in my defense, we needed to
respect the feature freeze and get 2.0 out the door so we can start
adding features like this
19 matches
Mail list logo
