Hi Christoph,
Christoph Zwerschke schrieb:
I have worked on the TG 1.5 branch this week and ported one of my apps
from TG 1.1 to 1.5. The major change in TG 1.5 is that it is based on
CherryPy 3 instead of CherryPy 2, and that it fully supports Genshi, not
only for page templates, but also
Daniel Fetchinson wrote:
Can't wait for cp 2.3.1 and the new tg1 release based on cp 2.3.1!
You probably noticed that Christoph put out TG 1.1.1 a few days ago. I
expect it to work perfectly with CherryPy 2.3.1 when it is released! :)
If there ary any incomptibilities, we will of course release
Daniel Fetchinson schrieb:
Actually, I should have thought about that earlier, I'll give the 1.5
trunk a try.
You're welcome to do so. The more people use it, the more issues we can
find and smooth out. Be aware though, that the code base is a bit torn
apart atm. There's Christoph's branch for
svn-comm...@turbogears.org schrieb:
Author: jon
Date: Thu Dec 17 08:36:02 2009
New Revision: 6981
URL: http://trac.turbogears.org/changeset/6981
Log:
thanks to bochecha contrib and mine, added a task registry to be able to
cancel and reschedule tasks already scheduled... bumped
Diez B. Roggisch schrieb:
Having just been invited to Google's new cool kid on the block, Wave, I
wonder
if - at least for development-centric discussions, not for normal support -
this couldn't be an alternative to make those kinds of discussions more
valuable, approachable and
Hi everybody,
I'm sorry, but we didn't manage to finish the TurboGears 1.1.1 release
as planned this past week end, due to exceptionally good weather in
South Germany ;)
We plan to make the release next weekend instead.
Chris
--
You received this message because you are subscribed to the
Diez B. Roggisch wrote:
Hi,
I might need a fork of TG 2.0. I tried and searched
http://bitbucket.org/turbogears/tg-2_0/
but didn't find a release-tag for 2.0.3. Is that just an ommission, or am I'm
missing something?
No, that's the sad state of affairs. Christoph Zwerschke brought
Jorge Vargas wrote:
I went over that list and commented, slotted properly and/or closed
almost all of them
Your feedback is appreciated.
Thanks a lot for going over the tickets.
please note a lot of them where simply misplaced which you could have
looked at instead of sending them to 2.x
Ken Kuhlman schrieb:
That's a good point, but the implied point behind Christoph's r6950 --
that 1.5 development has moved beyond the basics of getting things
running under CP3 -- is valid, too.
That's right, but from a developer's perspective I don't care about
version numbers, they are just
TurboGears schrieb:
#1955: Ensure 1.1 changes get applied to 1.5
Changes are now being applied to 1.5 first then backported as necessary;
this task is no longer needed.
Work has started on 1.5a2, so attaching last diff between 1.1 1.5a1
closing ticket.
Since 1.5a1 was never
Chris Arndt schrieb:
Hello everybody,
I'd like to issue a maintenance release of TurboGears 1.1 in the 2nd
half of November. This would be TurboGears version 1.1.1.
I have created a milestone for this release in track and started
moving tickets into it. No new features are planned for
Hi all,
I have summarized the development plans for TG 1.5 (as discussed on the
main mailing list) on the docs wiki:
http://docs.turbogears.org/1.5/DevPlans
These are open to discussion and improvements. Please direct questions,
comments, and suggestions to this list.
We would be also happy
Another logging related (?) issue:
When I run the tests for a 1.5 project (either with nosetests or with
python setup.py test), I get the following warnings on the console
(actual paths generalized):
[...]
'.../project/pkg/config/static' (root + dir) is not an existing
filesystem path.
Ken Kuhlman wrote:
Does anyone see the problem behind the failing 1.5 test? In test_identity,
it's test_json.
So far it's eluding me..
These are the lines of the test where it is failing:
response = self.app.get('/json', status=403)
# we get the output of the
Hi everybody,
ticket #2396 [1] has led me to the discovery that the TG scheduler was
extracted as an external project hosted on code.google.com [2]. I see
that several TG maintainers are listed as project owners for this project.
What is the status of this project?
- Why was it extracted
percious wrote:
If you have a 2.1a1 site, simply: easy_install -U TurboGears to
upgrade.
I think that should be
easy_install -U TurboGears2
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears
Ken Kuhlman schrieb:
Console logging is part cherrypy's default logging config, so you're
still getting it because your [[[cp_errors]]] section isn't taking. If
you change the qualname to cherrypy.error apply the patch below to
your 1.5 install [1], you'll have better luck.
Thanks Ken, I
Christopher Arndt schrieb:
Ken Kuhlman schrieb:
Console logging is part cherrypy's default logging config, so you're
still getting it because your [[[cp_errors]]] section isn't taking. If
you change the qualname to cherrypy.error apply the patch below to
your 1.5 install [1], you'll have
Hi all, hi Ken ;)
I ran my HelloWorld benchmark app [1] for TG 1.1 with the 1.5 branch
and apart from a few config fixes, it works well, but I couldn't get
CherryPy to stop logging access and other crud to the console.
I read the CherryPy 3 docs on logging but I'm a bit confused about what
is
enjoy!
--
Christopher Arndt sysad...@turbogears.org
TurboGears Systems Administrator
http://www.turbogears.org/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group.
To post to this group, send
Jorge Vargas schrieb:
The code is backwards compatible so the documentation is pretty much
@expose('json')
A ton of docs mention it, so I'm not really sure if it's needed.
However a section on __json__ should be nice. yet this didn't exist in
the original docs.
Christophe de VIENNE wrote:
Hi,
I was looking for what replaced turbojson in TG2 to find out it is still
there but not mentioned at all in the TG 2.0 documentation.
I would suggest an addition.
If you like I can report this on the tg trac.
Yes, you can use
Christopher Arndt schrieb:
Currently there are no tickets for TG 1 with no milestone, but there are
about 30 tickets for TG2 with no milestone. Would it be possible to move
these into appropriate 2.x milestones, so it is more easy to see at one
glance for which branch a ticket is relevant
Hi Christophe,
just discovered while going through this thread again, that your
question was never answered.
Christophe de VIENNE schrieb:
A few question about the TG 1.1 documentation :
- is there a 1.0 to 1.1 migration howto ?
There is http://docs.turbogears.org/1.1/RoughDocs/Upgrade to
Hi all,
in the process of the 1.1rc1 release and afterwards I went through all
of the tickets for TG 1 and those without a milestone and discarded many
cruft tickets:
- enhancements without patch or feedback in a long time
- enhancements for unmaintained (CatWalk) or to-be-phased-out (TG
Hi Christoph,
Christoph Zwerschke schrieb:
Christoph Zwerschke schrieb:
Tomorrow I will update a larger app in production from 1.0.8 to 1.1rc1
and report how it went.
The update went as smoothly as one would imagine, and I even think the
app website has become a bit snappier - maybe
Christoph Zwerschke schrieb:
And you get a 401 error in TG 1.1 due to changeset 5253. The problem
still existed when you add the query parameter tg_format=json, but this
has just been fixed as well, in revisions 6660 and 6661.
Nice!
Though I'm wondering if changing the error code to 401
Christopher Arndt schrieb:
So, should we prepare a TG 1.1 rc1 release this weekend now that the
SQLAlchemy mapper issue is resolved?
I would volunteer to carry out the preparations. If there are any
outstanding tickets, which you would like to resolve (i.e. provide a
solution for) before
Hi all,
I just released first the release candidate for TurboGears 1.1. The list
of changes is at
http://trac.turbogears.org/wiki/ChangeLog
This list only includes changes which are unqiue to TG = 1.1. There are
also a lot of changes, which also went into the 1.0 branch, so they are
documented
Hi all,
I tried to reproduce the problem described in ticket
http://trac.turbogears.org/ticket/2036 but couldn't.
I created a small example project and attached it to the ticket.
Can somebody confirm that it is indeed working as it should?
Chris
Florent Aide schrieb:
As per your question I think we should make this happen only after 1.1
final (rc this weekend!)
Agreed. As mentioned in another mail, I'm trying to get most of the
defects for the 1.1 milestone done and then I will create appropriate
milestones in trac as necessary and
Christoph Zwerschke schrieb:
Please don't forget 1.0.9. Maybe we can release it together with 1.1rc1?
I have rather enough tasks with the 1.1rc1 release at hand at the
moment. But if somebody prepares the release (mainly updating the
changelog and testing), I'll gladly help with the
Hi everybody,
a while ago I commited a patch [1] for i18n in TG 1.1 that allowed
translatable strings in Genshi templates to be collected with tg-admin
i18n collect.
The current function does not collect any strings within Python
expressions, because with the Genshi Translator filter [2] you do
Daniel Fetchinson schrieb:
Unfortunately I don't have a fix but what's the official point of view
on this ticket?
http://trac.turbogears.org/ticket/2207
That leaves the CatWalk problem, which could probably be solved by
adding SecureResource as a mix-in dynamically. But I think that's not
I'm currently going through the list of open tickets for the 1.1
milestone (see http://trac.turbogears.org/wiki/TicketQueries) and I've
already fixed and closed a few. I would like at least to close (either
through fixing or closing as invalid) the defects with priority normal
before the 1.1rc1
Christopher Arndt schrieb:
So, should we prepare a TG 1.1 rc1 release this weekend now that the
SQLAlchemy mapper issue is resolved?
I would volunteer to carry out the preparations. If there are any
outstanding tickets, which you would like to resolve (i.e. provide a
solution for) before
So, should we prepare a TG 1.1 rc1 release this weekend now that the
SQLAlchemy mapper issue is resolved?
I would volunteer to carry out the preparations. If there are any
outstanding tickets, which you would like to resolve (i.e. provide a
solution for) before that, please speak up until this
Daniel Fetchinson schrieb:
Unfortunately I don't have a fix but what's the official point of view
on this ticket?
http://trac.turbogears.org/ticket/2207
Neither identity.SecureObject nor identity.SecureResource protects a
whole URL tree currently.
Sorry, I can't confirm your findings.
Christoph Zwerschke schrieb:
Christopher Arndt schrieb:
And it only works with SA = 0.5 :(
scoped_session.query_property() does not take arguments in earlier versions.
It would be possible to work around that, too. Or we could monkey-patch
SA to make the base Query class itself callable
Christoph Zwerschke schrieb:
Christopher Arndt schrieb:
Can we up the SA requirement for TG1.1. accordingly?
This will also allow some simplification in command.sacommand and
turbogears.database.
What do you mean?
but maybe something like this could do the trick:
cls.query
Christopher Arndt schrieb:
Christoph Zwerschke schrieb:
but maybe something like this could do the trick:
cls.query.__call__ = lambda self: self
Ok, I'll try that and write a test for it.
That doesn't work, unfortunately.
Chris
Christoph Zwerschke schrieb:
You're right, this needs to be done more complicated:
def query_cls(mapper, session):
class query(session.query(mapper).__class__):
__call__ = lambda self: self
return query(mapper)
cls.query =
Christopher Arndt schrieb:
We could also make it configurable. Or how would you check for the SA
version? sqlalchemy.__version__ only has the version number a string value.
I created a new patch that just puts the definition of the
session_mapper factory outside the if/else structure
Christoph Zwerschke schrieb:
After having a second look I noticed that after some polishing (already
done in r6633) this is not a real problem.
The old Session.mapper is still available as turbogears.database.mapper
as long as it's available in SA. So old projects will continue to work
Christoph Zwerschke schrieb:
Christopher Arndt schrieb:
I just checked and Session.mapper is still available in SA 0.6beta1. I
think the test in turbogears.database, line 90 needs to be different.
This is actually the intended behavior. As long as Session.mapper is
available (even
Florent Aide schrieb:
At the moment I have just replaced the session mapper with the
sqlalchemy.orm.mapper. BUT this means that user code that relied on
the session_mapper behaviour (instanciating the object with arguments,
auto saving, query method on the class) will break.
We could try
Diez B. Roggisch schrieb:
On Sunday 23 August 2009 13:24:07 Christopher Arndt wrote:
Jorge Vargas schrieb:
so I'll like to revise the decision. Back then the pro index arguments
where - unreleased packages
- maintaining a well known set
- pypi's instability
Are those still valid?
What
Jorge Vargas schrieb:
so I'll like to revise the decision. Back then the pro index arguments where
- unreleased packages
- maintaining a well known set
- pypi's instability
Are those still valid?
What is everyone's opinion on this? and more importantly are the ones
in favor of the
Hello,
currently all turbogears.org servers are down. I can't even reach the
WebFaction control panel to open a ticket, I onyl get an error message
from their server. I hope the WebFaction staff will notice this soon and
act accordingly.
I'll let you know, when the server is up again, but I'll
Christopher Arndt schrieb:
Hello,
currently all turbogears.org servers are down. I can't even reach the
WebFaction control panel to open a ticket, I onyl get an error message
from their server. I hope the WebFaction staff will notice this soon and
act accordingly.
I'll let you know
Paul Johnston schrieb:
So, this is a call to the authors of all web authentication libraries.
Add JavaScript MD5 as an authentication mechanism. And if support
becomes widespread, the internet becomes a little bit safer for
everyone.
I'm surprised that no one has mentioned it yet, but
Paul Johnston schrieb:
No need for plaintext passwords, you can hash them in the database
too. In fact, in the scheme I recommend the server never sees a
plaintext password. It's true that the stored hashes are password-
equivalents, that a hacker could use them to login to the site. But
the
Qwait schrieb:
On Feb 12, 5:10 am, Diez B. Roggisch de...@web.de wrote:
On Wednesday 11 February 2009 23:55:40 Qwait wrote:
I am working on a project that I want to create static pages from the
output of the controller methods. Is there a public function that I
can use to get this rendered
percious schrieb:
I was editing our pages for GSoC 2009 and got locked out. What is the
sequence of events leading to surge protection lock out? How long am
I locked out for?
Is there a way for our usual editors to avoid surge protection. It
seems a bit odd to me that I would be treated
Mark Ramm schrieb:
Ok, this is done.
The url and redirect functins no longer take lists of path elements,
and no longer take dictionaries of parameters -- so you need to append
your path elements manually now, and you need to do *dict to turn your
dictionary into keyword arguments if you
Daniel Fetchinson schrieb:
We now have a styled login box... Please test.
Hi Florent, I wanted to take a look at it so 'svn up'-ed my tg-1.5
directory, then installed a virtualenv, tried to install tg from the
tg-1.5 directory using python from the virtualenv, but
Jorge Vargas wrote:
On Sat, Dec 13, 2008 at 2:57 PM, Iain Duncan iaindun...@telus.net wrote:
actually someone bet me to it his name is Jon which is from the
other side of the sea together with Florent, so they bet me by
timezone.
Jon is Jonathan Schemoul, a designer and web developer from
Florent Aide schrieb:
We need to get a balance here... Going over 80 is ok, because as you
said we don't have to follow pep8 for XML documents. But having line
100/150 chars is also a pain...
+1
I usually break long lines before element attributes and try to avoid
breaking between an
is
down more than 10 minutes. I didn't receive anything, so I suppose it
was a temporary glitch. Also no message from WebFaction or anything on
their status blog (http://statusblog.webfaction.com/) to indicate any
serious problems.
--
Christopher Arndt [EMAIL PROTECTED]
TurboGears Systems
Iain Duncan wrote:
Have we considered asking for a VPS from someone? I would not be
surprised if Slicehost were open to the suggestion, having just been
purchased by a larger company with the dough for promo. I've been really
happy with them and have been moving more and more clients to VPS's
Ken Kuhlman schrieb:
I'm struggling with the decision of whether I should backport
use_wsgi_app-type functionality to tg1.1b2,
I think that full wsgi-compliance isn't a key feature of TG 1.1. Florent
told me in a chat that he agrees with this view. So I think it's ok to
move this to te next
awaiting their
response. I'll let you all know about further developments.
--
Christopher Arndt [EMAIL PROTECTED]
TurboGears Systems Administrator
http://www.turbogears.org/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Christopher Arndt schrieb:
The server where turbogears.org is having trouble again at the moment,
which means that the SVN, trac and the wiki are not working properly at
the moment.
The main website seems to work ok, because it only used static files and
no database.
I have opened
Christophe de VIENNE schrieb:
2008/11/12 Christoph Zwerschke [EMAIL PROTECTED]:
Christophe de VIENNE schrieb:
Shouldn't line 108 be :
108if identity.anonymous:
No, I think current.anonymous is correct; current is the identity
wrapper. Maybe you were confused because it's named
James schrieb:
Hello, Where can I get pre-compiled binaries for windows James
For what? For Turbogears? TurboGears itself is a pure Python package,
there are no binaries (for any system). TurboGears depends on some C
extensions though, which need to be compiled. We provide pre-compiled
binary
Lukasz Szybalski schrieb:
On Mon, Nov 3, 2008 at 8:55 AM, Christopher Arndt [EMAIL PROTECTED] wrote:
Lukasz Szybalski wrote:
Hello,
Is there a reason the view tickets screen asks me to do a custom
query instead of showing the usual choices aka. Reports.
I'm trying to view all tickets and I
Diez B. Roggisch schrieb:
Christopher Arndt schrieb:
I fixed the issue in SVN. Should we do another release?
Sure. 0.2Beta2?
Yep.
Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group
Diez B. Roggisch schrieb:
I'm happy to announce
tgMochiKit 0.2beta
Unfortunately this release contains an error that prevents MK version
1.4 from working properly with TG.
The paths tgmochikit/static/javascript/1.4/packed/* in the project
should be
Christopher Arndt schrieb:
alex bodnaru schrieb:
is this requirement for tg1.1 with toscawidgets too?
Technically, yes, since the requirement is put down in TG's setup.py
file. But IIRC, tw comes with it's own version of MochiKit and
preferably uses jQuery anyway, so it won't use
Gustavo Narea schrieb:
Hello,
I think
Do you need Identity (usernames/passwords) in this project? [no]
should be replaced by
Do you need authentication and authorization in this project? [yes]
in the quickstart.
What do you think?
Good idea +1
Could you open a ticket so we
Christoph Zwerschke schrieb:
Finally, MochiKit 1.4 has been released!
Oh, wow, can we expect Hurd and Duke Nukem forever next? ;)
Shall we add it to TG 1.0, plus a config parameter to choose between 1.3
and 1.4 (with 1.3 as default, to be backward compatible)?
Would that mean using
Jorge Vargas schrieb:
that is awesome. In fact it's less obscure than how websetup.py works.
I think most of it should go inside TG, and we should write docs on
how to modify it, for that part I think the best will be to provide a
callback by means of a callable to add more stuff to the
Florent Aide schrieb:
On Wed, Oct 15, 2008 at 10:28 PM, Jorge Vargas [EMAIL PROTECTED] wrote:
I have answer this two times in the past 2 days on IRC, which i think
is something that could be back ported or at least write some
documentation.
The issue at hand is that people want to
Helio Pereira schrieb:
When I include the follow tag in a template, tgw (or genshi) gives an
error:
a href=teste?ola=olepp=xxteste/a
TemplateSyntaxError: not well-formed (invalid token): line 88, column
45 (/media/Dados/wWw/vhosts/tg2/bp/bp/templates/posto.html, line 88)
As the error
Florent Aide schrieb:
-- Forwarded message --
From: Christopher R. Gabriel [EMAIL PROTECTED]
I found a problem in the i18n string collection in TG 1.0.x using the
pygettext module. I've patched the pygettext to get it work, attached
to this mail.
Please open a ticket in
Florent Aide schrieb:
I have macos 10.5 on a macbook air (wifi-only-no-ethernet) but I can
put it right beside the wifi box to see if it works. Chris do you have
any macos specifics for BB ?
Not yet. I haven't set up the slave on my Mac yet. If I encounter any
problems, hickups, etc. on the
iain duncan schrieb:
I can't find a good way to have both:
A) change something in one place only
B) have middle content appear before floated columns in the document
structure
The best method for that that I've seen using the jiggery pokery is that
used by the Drupal Zen theme, (
Jorge Vargas schrieb:
On Thu, Oct 9, 2008 at 8:21 AM, Christopher Arndt [EMAIL PROTECTED] wrote:
The more build slaves we got for a particular system, the better and the
lower the numbers a single build slave has to be online.
oh really? I though 1 per os was good enough.
If it's up for 24
(taking this back to the trunk ml. Sorry, sent my reply to the wrong
list before)
Diez B. Roggisch schrieb:
Christopher Arndt schrieb:
Florent Aide schrieb:
On Sun, Oct 5, 2008 at 6:18 PM, Steven Mohr [EMAIL PROTECTED] wrote:
our BuildBot system needs slaves.
I'll certainly be able
Christopher Arndt schrieb:
Hi all,
Python 2.6 is out since yesterday!
Did anybody already test TG 1.0.x, 1.1 or TG 2 with it?
I just tried to install TurboGears 1 on Python 2.6 on Windows and
already failed at the first hurdle :( :
C:\Documents and Settings\Christopher
ArndtC
Daniel Fetchinson schrieb:
#1710: [PATCH] one-time task scheduler
-+--
Reporter: khorn|Owner: Chris Arndt
Type: enhancement | Status: closed
Priority: normal
Florent Aide schrieb:
On 9/24/08, Christopher Arndt [EMAIL PROTECTED] wrote:
Florent Aide schrieb:
On 9/24/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
For 1.1 this will be an intermediate solution anyway, since I want to
use the tgsetupng.py way for 1.1 and going forward as soon
Mark Ramm schrieb:
On Wed, Sep 24, 2008 at 1:09 AM, Daniel Fetchinson
Nevertheless, if technically possible, I agree that easy_install
should only install stable releases. If it is technically not possible
I of course accept that and will use tgsetup.py
Well if the beta releases are not
Chris Miles wrote:
On 23/09/2008, at 10:06 AM, Christopher Arndt wrote:
Thatswhy the official and supported installation method is the one
described on http://docs.turbogears.org/Install using the tgsetup.py
script, which will install the correct current stable version.
I don't agree
Christoph Zwerschke schrieb:
Christoph Zwerschke schrieb:
Btw, it doesn't seem like the mapping parameter to view.render hasn't
been used anywhere, so I suggest renaming it to options.
I mean it *does* seem like it hasn't been used. Since the parameter is
called options in the __init__
Christoph Zwerschke schrieb:
Right, it's passed all along from expose to view.render. And the
expose() function even mentions it in the docstring:
@keyparam mapping
mapping with options that are sent to the template engine
Yep, that's what I said in my original post. ;)
I still
Christopher Arndt wrote:
Chris Miles wrote:
My assumption is that setuptools will find the latest stable version
of 1.0.x from pypi, but as you say this is incorrect. This should be
made clear, as I (and others in the same position) will need to make
sure we define the TG dependencies
Christoph Zwerschke schrieb:
Christopher Arndt schrieb:
- Should the Genshi Buffet plugin determine the doctype from the
template format? Should this be reported as a bug to the Genshi project?
I think Genshi should never send a doctype that is incompatible with the
format (doctype=HTML
iain duncan wrote:
On Tue, 2008-23-09 at 02:06 +0200, Christopher Arndt wrote:
No, easy_install is always installing the latest version, that's
available on the download page linked on the projects PyPI page.
Thatswhy the official and supported installation method is the one
described
Florent Aide wrote:
I am sorry to ask you that so late after the ticket but could you
adapt your patch from this ticket:
http://trac.turbogears.org/ticket/1628
and commit it to the 1.1 branch ?
The matter has been complicated a bit in the meantime, since the visit
framework now also support
iain duncan wrote:
So I'm thinking I could:
- write the core assuming that the standards compliant box model is in
effect
+1 gazillion on not wasting your voluntary effort for TG on supporting
this outdated piece of crap. If customers want support for IE6 they
should pay for it BIG TIME.
iain duncan schrieb:
On Sat, 2008-20-09 at 13:33 +0200, Florent Aide wrote:
Once we've worked out the administrative details, I hope you'll be
able to begin hacking directly on the css and templates content. The
ticket Chris talked about could be handled by me, chris*, deets or
whoever else
Ken Kuhlman schrieb:
On Thu, Sep 18, 2008 at 6:45 PM, Florent Aide [EMAIL PROTECTED] wrote:
I created a ticket #1992 in our trac and begun work on it.
My concern with the original wording here was that it sounded a little
bit defensive. A quickstarted template isn't the right place for
Hi all,
Florent Aide schrieb:
I created a ticket #1992 in our trac and begun work on it. Attached is
a screen grab of how it looks like on my machine. Sorry for the file
size but trac did not accept my attachement.
The text is not finalized and Ken is working on it right now. Please
don't
Lukasz Szybalski schrieb:
While we are on this topic..would we be interested in having a build in menu?
What for? There aren't any sub-pages this menu could link to. And if
there where any, I don't think we would have enough of them to justify a
a full-blown drop-down menu a simple nav bar like
Florent Aide schrieb:
On 9/19/08, Christopher Arndt [EMAIL PROTECTED] wrote:
For the search field I thought of integrating a custom TG Google search
engine, like this one for TG 2:
http://www.google.com/coop/cse?cx=013833837327090257708%3Af0q5ocbisby
Maybe we could even include
Paul Johnston schrieb:
Hi,
I've just committed a tweak to the 1.0 branch. Not sure where we're up
to with branches these days - can someone please merge as appropriate?
Paul, can you please add an explanation what your change does exactly?
Preferably in the form of a trac ticket. This
Florent Aide schrieb:
- http://trac.turbogears.org/ticket/1963 seems quite finished
(regarding the beta1
My suggestion for finally resolving this one is to remove the meta tags
with the content-type from the quickstart templates completely. The
original issue of this ticket is already solved
When forging a 1.1 release, we should also pay attention to the tickets
in the 1.0.x-bugfix milestone since some of them are relevant to the
1.1/1.5 branches as well. Here's the appropriate ticket query:
http://tinyurl.com/5tppdx
Atm, in this list, there is an open question for this ticket:
Here's an update on those issues:
Christopher Arndt schrieb:
here is a review of some misc trac tickets concerning milestone
1.0.x-bugfix, 1.1 or 1.5 that have open issues and where we need
feedback. This is just an arbitrary selection of tickets that caught my
attention, there are a lot
1 - 100 of 272 matches
Mail list logo
