[tg-tickets] [TurboGears] #775: [PATH] quickstart templates is not valid html
#775: [PATH] quickstart templates is not valid html
+---
Reporter: Lazy| Owner: anonymous
Type: defect | Status: new
Priority: low | Milestone: 0.9a5
Component: TurboGears | Version: 0.9a4
Severity: minor |Keywords:
+---
Hello,
Login and main templates are missing type=text/css in stylesheet
definition.
Path follows
{{{
--- qstemplates/quickstart/+package+/templates/master.kid (revision
1210)
+++ qstemplates/quickstart/+package+/templates/master.kid (working
copy)
@@ -6,7 +6,7 @@
meta content=text/html; charset=UTF-8 http-equiv=content-type
py:replace=''/
title py:replace=''Your title goes here/title
meta py:replace=item[:]/
-style
+style type=text/css
#pageLogin
{
font-size: 10px;
--- qstemplates/quickstart/+package+/templates/login.kid(revision
1210)
+++ qstemplates/quickstart/+package+/templates/login.kid(working
copy)
@@ -8,7 +8,7 @@
meta content=text/html; charset=UTF-8
http-equiv=content-type py:replace=''/
titleLogin/title
-style
+style type=text/css
#loginBox
{
width: 30%;
}}}
--
Ticket URL: http://trac.turbogears.org/turbogears/ticket/775
TurboGears http://www.turbogears.org/
TurboGears front-to-back web development
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Tickets group.
To post to this group, send email to turbogears-tickets@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #775: [PATH] quickstart templates is not valid html
#775: [PATH] quickstart templates is not valid html +--- Reporter: Lazy|Owner: anonymous Type: defect | Status: closed Priority: low |Milestone: 0.9a5 Component: TurboGears | Version: 0.9a4 Severity: minor | Resolution: duplicate Keywords: | +--- Changes (by Lazy): * status: new = closed * resolution: = duplicate Comment: Part of #768 -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/775 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #724: Turn of automatic svn add behavior in quickstart
#724: Turn of automatic svn add behavior in quickstart +--- Reporter: kevin |Owner: anonymous Type: defect | Status: closed Priority: normal |Milestone: 0.9a5 Component: TurboGears | Version: 0.9a4 Severity: normal | Resolution: fixed Keywords: | +--- Changes (by alberto): * status: new = closed * resolution: = fixed Comment: I've bumped PasteScript to 0.5.1 in [1213]. However, I don't seem to find the switch you're talking about in create_distro.CreateDistroCommand. A svn_repository option seems to be there but it's not on by default (maybe this is the change form 0.5 to 0.5.1?) and not touched by quicstart. I've tried to reproduce the problem by tg-admin quickstarting an empry project inside a svn sandbox as the tickets described and nothing was automatically added to the repository. I guess it's safe to close the ticket. Please feel free to reopen if I've missed anything. Alberto P.S. Leaving the two tickets mentioned above open until someone reviews this in case I screwed up. :) -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/724 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] [TurboGears] #776: Enhancements for CogBin
#776: Enhancements for CogBin -+-- Reporter: anonymous| Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: 1.0 Component: Docs | Version: 0.9a4 Severity: normal |Keywords: -+-- Here is a list of enhancements for CogBin: * A table of contents section should be added to the page to simplify navigation as the page grows larger. * Currently the project name and version columns are vertically centered and should be changed to align to the top to clean up the appearances of the tables. * Projects in each section should be sorted in alphabetical order. * A new column is needed for '''Supported TurboGears Versions'''. Not sure how this would be accomplished as this information is not available from the Cheese Shop. * Once '''Supported TurboGears Version''' is supported a filter on the top of the page should be added to show only the projects that are compatible for the version of TG the user is interested in. * For the Widgets section it would be nice if there was an image to make it easier for users to find Widgets of interest. Also, are there any links to the CogBin page outside of it's mention in the mailing list? I have not seen one so I assume most new users or those who don't search the list will not likely find the page. Maybe the links are there and I just have not come across them. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/776 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value
--+-
Reporter: godoy | Owner: anonymous
Type: defect| Status: new
Priority: high | Milestone: 0.9a5
Component: CherryPy | Version: 0.9a4
Severity: critical |Keywords:
--+-
Hi! With the following widget declaration I am not being able to set the
value of its text_field programatically:
{{{
endereco = widgets.AutoCompleteField(
search_controller=/clientes/search_endereco,
search_param=endereco,
result_name=enderecos,
text_field = widgets.TextField(name = 'endereco_text',
attrs = {'size':51},
label = _(u'Endereço'),
validator =
validators.UnicodeString(if_empty = None)),
)
}}}
I've tried attributing values to it using the following idioms:
* dict(endereco = value)
* dict(endereco_text = value)
* dict(text_field = value)
* dict(text = value)
* dict(widget = value)
* {'endereco.widget': value}
and some more combinations based on the generated HTML and the source
code. I can't precisely say when this started hapenning, but it was with
some of the latest changes.
Here I have:
{{{
% tg-admin info | sort
cElementTree 1.0.5-20051216
Cheetah 1.0
CherryPy 2.2.0
elementtree 1.2.6
elementtree 1.2.6
FormEncode 0.5.1
FormEncode 0.5.1
kid 0.9
nose 0.8.4
Paste 0.5
PasteDeploy 0.5
PasteScript 0.5
PyProtocols 1.0a0
RuleDispatch 0.5a0
setuptools 0.6a11
simplejson 1.3
SQLObject 0.7.1dev-r1707
TurboGears 0.9a5dev-r1207
TurboJson 0.9.2dev-r1204
TurboKid 0.9.4dev-r1123
}}}
This makes this kind of field unusable for editing data.
--
Ticket URL: http://trac.turbogears.org/turbogears/ticket/777
TurboGears http://www.turbogears.org/
TurboGears front-to-back web development
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Tickets group.
To post to this group, send email to turbogears-tickets@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value
--+-
Reporter: godoy |Owner: anonymous
Type: defect| Status: new
Priority: high |Milestone: 0.9a5
Component: CherryPy | Version: 0.9a4
Severity: critical | Resolution:
Keywords:|
--+-
Changes (by godoy):
* component: Widgets = CherryPy
Comment:
In my controller I have this:
{{{
valores = dict(
# ...
endereco = dict(endereco_text = fornecedor.endereco),
# ...
)
return dict(
# ...
data = valores,
# ...
)
}}}
and in my Kid template I have:
{{{
span py:replace=formulario.display(value = data,
action='%s/update/' % root_link, method = 'post') /
}}}
So if you're asking about the nested dicts I believe I did, unless you
were asking about a third level -- mine only has two levels.
--
Ticket URL: http://trac.turbogears.org/turbogears/ticket/777
TurboGears http://www.turbogears.org/
TurboGears front-to-back web development
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Tickets group.
To post to this group, send email to turbogears-tickets@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value --+- Reporter: godoy |Owner: anonymous Type: defect| Status: new Priority: high |Milestone: 0.9a5 Component: CherryPy | Version: 0.9a4 Severity: critical | Resolution: Keywords:| --+- Comment (by alberto): You're last example should be working... This is certainly a bug. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/777 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value
--+-
Reporter: godoy |Owner: anonymous
Type: defect| Status: new
Priority: high |Milestone: 0.9a5
Component: Widgets | Version: 0.9a4
Severity: critical | Resolution:
Keywords:|
--+-
Comment (by alberto):
{{
value = dict(endereco=dict(text=Something))
form.display(value=value)
}}}
--
Ticket URL: http://trac.turbogears.org/turbogears/ticket/777
TurboGears http://www.turbogears.org/
TurboGears front-to-back web development
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Tickets group.
To post to this group, send email to turbogears-tickets@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value --+- Reporter: godoy |Owner: anonymous Type: defect| Status: new Priority: high |Milestone: 0.9a5 Component: Widgets | Version: 0.9a4 Severity: critical | Resolution: Keywords:| --+- Comment (by godoy): Nope, it didn't work. I even added a third level dictionary at my controller... I'll try reproducing it in a minimal application and I'll attach it here (if I don't find my mistake while doing that). -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/777 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] [TurboGears] #778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider
#778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider ---+ Reporter: anonymous | Owner: anonymous Type: defect | Status: new Priority: normal | Milestone: 0.9a5 Component: Identity | Version: 0.9a4 Severity: normal |Keywords: ---+ This patch makes the default soprovider more suitable for a wider range of uses by making the email address and display name optional. It does remove the alternateId status of emailAddress. Tim Lesher has rightly expressed some concern. ( http://tinyurl.com/rfwqu ) My thinking is that: 1. TG 1.0 will be used in internet apps, intranet apps, and apps in small mom and pop shops for which the term intranet would be overkill... as would be requiring an email address and (to a lesser extent) display name. The current tg_user enforces a decidedly Internet App flavor. 2. As Jorge Godoy pointed out on the Turbogears list, it's easier to add constraints than to remove them. 3. The TG 1.0 API will be fixed in stone and we will be living with it for a while. 4. The fields are useful to a large enough percentage of people that it makes sense to keep them for (optional) use than to remove them entirely. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/778 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider
#778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider ---+ Reporter: anonymous |Owner: anonymous Type: defect | Status: new Priority: normal |Milestone: 0.9a5 Component: Identity | Version: 0.9a4 Severity: normal | Resolution: Keywords: | ---+ Comment (by [EMAIL PROTECTED]): The first patch is against 0.9a4. (Oops, selected the wrong file. Sorry.) The second ( ident_email_dispname_optional.patch ) is against the trunk. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/778 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value
--+-
Reporter: godoy |Owner: anonymous
Type: defect| Status: closed
Priority: high |Milestone: 0.9a5
Component: Widgets | Version: 0.9a4
Severity: critical | Resolution: worksforme
Keywords:|
--+-
Changes (by anonymous):
* status: new = closed
* resolution: = worksforme
Comment:
It's not a bug in AutoCompleteField but in you app. Try:
{{{
#!py
@turbogears.expose(html = 'ticket777.templates.clients')
def index(self):
values = dict(
endereco = dict(endereco_text = 'Default Value'),
)
}}}
In the Clients controller. You had 'addresses' instead of 'endereco' and
'text' instead of 'endereco_text'. A snippet form the form so you can
compare:
{{{
#!py
class widgets_clients_addresses(widgets.WidgetsList):
endereco = widgets.AutoCompleteField(
search_controller=/clients/search_address,
search_param=address,
result_name=addresses,
text_field = widgets.TextField(name = 'endereco_text',
attrs = {'size':51},
label = _(u'Endereço'),
validator =
validators.UnicodeString(if_empty = None)),
)
my_form_address = widgets.TableForm(fields = widgets_clients_addresses())
}}}
--
Ticket URL: http://trac.turbogears.org/turbogears/ticket/777
TurboGears http://www.turbogears.org/
TurboGears front-to-back web development
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Tickets group.
To post to this group, send email to turbogears-tickets@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #777: Impossible to programatically set an AutoCompleteField default value
#777: Impossible to programatically set an AutoCompleteField default value --+- Reporter: godoy |Owner: anonymous Type: defect| Status: closed Priority: high |Milestone: 0.9a5 Component: Widgets | Version: 0.9a4 Severity: critical | Resolution: worksforme Keywords:| --+- Comment (by godoy): Silly me. Indeed it works and I haven't fully searched and replaced the text from my application to this test case. Sorry... So, it is some bug in my code that I need to find. Probably something as silly as this :-) Thanks for your time. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/777 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider
#778: [PATCH] Patch to make emailAddress and displayName optional in default soprovider ---+ Reporter: anonymous |Owner: anonymous Type: defect | Status: new Priority: normal |Milestone: 0.9a5 Component: Identity | Version: 0.9a4 Severity: normal | Resolution: Keywords: | ---+ Comment (by anonymous): Well, I really can't disagree with the idea of having tg_user defined in model.py, with username and password fields (and no others) being a requirement of the model. That would be heaven. Unfortunately, I'm not up to coding that and the fact is that we currently do have a default model with requirements that get in the way. It is much easier for the programmer to simply extend tg_user to add fields or constraints than it is to get around constraints that don't make sense for the particular app. Including some commonly used fields seems like a good idea to me. But *requiring* them is where they start to get in the way. Particularly when they are required to be unique. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/778 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] Re: [TurboGears] #779: turbogears.util.DictObj improvement
#779: turbogears.util.DictObj improvement --+- Reporter: [EMAIL PROTECTED] |Owner: anonymous Type: enhancement | Status: new Priority: normal|Milestone: 0.9a5 Component: TurboGears| Version: 0.9a4 Severity: normal| Resolution: Keywords:| --+- Comment (by godoy): From discussions in the trunk mailing list I believe that this will be removed and Bunch will be the class that will be left. If somebody can confirm and close this bug as 'wontfix'/'invalid', I'd appreciate. -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/779 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
[tg-tickets] [TurboGears] #780: patch attempt (non functional) at making identity more adaptable
#780: patch attempt (non functional) at making identity more adaptable +--- Reporter: [EMAIL PROTECTED] | Owner: anonymous Type: enhancement | Status: new Priority: normal | Milestone: Component: Identity| Version: 0.9a4 Severity: normal |Keywords: +--- The current Identity schema requires both a user_name and a user_email. I dislike that, because while on some projects I want users to have both, on many I want the user to have one or the other. Someone submitted a patch earlier that makes email not-required , which is great for their application, but doesn't work for mine - it still requires a unique user submitted id name. my attached patch doesn't work - I couldnt get things quite right, but it presents a different approach that hopefully someone else can take over or help me complete let me just elaborate on the idea a_ app.cfg the setting for identity.form.user_name is changed to 'account_identifier', which can either be 'user_name' or 'user_email' we add a 'identity.account_identifier' setting that can either be 'user_name' or 'user_email' . this represents the primary unique idfield. we add 'required.user_email' and 'required.user_name' boolean options - should these fields be required? b_ visitor.py references to user_name are replaced with account_identifier c_ so/sa providor essentially, _get_user_name becomes _get_account_identifier i tried to make things backwards compatible (perhaps too much) , so 'user_name' is still stored in some places (as is user_email'), but only in addition to account_identifier i upped user_name from 16 to 255 characters. user_email and display_name are both 255. I hope at least this idea is accepted - it would at least give people the chance to put an email address in user_name (although that would be really confusing) i wasn't sure if this would work or not, but if possible, i think we should set alternateId, alternateIdMethod in TG user based on the settings in app.cfg hopefully, an approach like this will accomplish the following: a- have no impact on people already using identity b- let people use user_name as the primary id (and omit user_email) c- let people use user_email as the primary id (and omit user_name) d- let people use both user_name and user_email -- Ticket URL: http://trac.turbogears.org/turbogears/ticket/780 TurboGears http://www.turbogears.org/ TurboGears front-to-back web development --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups TurboGears Tickets group. To post to this group, send email to turbogears-tickets@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-tickets -~--~~~~--~~--~--~---
