[web2py] Re: AutocompleteWidget: experimental, magic, RFC
Tito, I had the same problem, but after i copied the latest jquery.js file to the static/ folder of my application, it automatically closes (after 2 or 3 seconds). Closing should/should be a little faster to give it a more responsive feeling. (i am on linux / firefox 3.5.8) On Mar 16, 11:59 pm, Tito Garrido wrote: > Is there a way to close the autocomplete field when the option get clicked? -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
[web2py] Re: AutocompleteWidget: experimental, magic, RFC
Cool feature, Is it possible to use the value in input A as a limiting select for input B. eg. If your targets can belong to different groups and Borg2 is only in Group2, not Group1. If i select Group2 in my first input field in a form, then in field 2 of the form the autocomplete should only select values that belong to Group2. 1. reading the entered value from the first input field. 2. using that value for the autocomplete of the next input field. Is / how would this be possible. On Feb 6, 9:30 pm, mdipierro wrote: > People say there is some magic in web2py. > Here is some real magic now in trunk that I am sure you have never > seen. > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
[web2py:37594] starting web2py in the foreground for debugging
Hi, underdev advised me on to ask my question here is there a way to start web2py in the foreground, so that i can see all the error messages / warnings on the foreground in the terminal where i started web2py ? i like to work with as little as possible mouse clicking and such way of starting would be very useful. another option would be a logfile that i can follow with "tail -f ". kind regards, jean-paul -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
[web2py:37656] Re: starting web2py in the foreground for debugging
Massimo, Tnx for replying. > You can find requests logged in httpserver.log > What kind of logs would you like to see? > > Massimo Basically, having a plain text version of the logs that are now send to the tickets in one big long file would be a nice start. The tickets are great, but during debugging, i tend to make so much of those tickets, and keep clicking around untill i get pain from using my mouse. (says more about me than web2py). I can imagine it would be great to have an option to have a "tail -f web2pydebug.log" running in a terminal to see the debugging information running over my screen while i reload a page with problems. It imagine it could also be an idea for the people who use web2py in production to configure web2py to log to their syslog server, so they can use their normal toolings for processing warnings and errorlogs. Not logging by default, i like the default behaviour to be clean. Just an option to switch on logging in a syslog standard way, or to a local logfile would be nice. Kind regards, Jean-Paul -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
[web2py:37887] Re: starting web2py in the foreground for debugging
Tnx, it works :)
Best wishes,
On Dec 22, 3:57 pm, mdipierro wrote:
> Hi Jep,
>
> create a file routes.py and in it
>
> routes_onerror=[('*/*','/logging/default/index')]
>
> and the create an app "logging" with a "controllers/default.py" that
> does the following:
>
> from gluon.admin import *
>
> def index():
> from restricted import RestrictedError
> app, ticket_id = request.vars.ticket.split('/')
> e = RestrictedError()
> e.load(request, app, ticket_id)
> print e.traceback
> return 'ticket: %s' % request.vars.ticket
>
> all tickets will be logged by the logging app.
>
> On Dec 22, 8:21 am, jep wrote:
>
> > Massimo,
>
> > Tnx for replying.
>
> > > You can find requests logged in httpserver.log
> > > What kind of logs would you like to see?
>
> > > Massimo
>
> > Basically, having a plain text version of the logs that are now send
> > to the tickets in one big long file would be a nice start.
>
> > The tickets are great, but during debugging, i tend to make so much of
> > those tickets, and keep clicking around untill i get pain from using
> > my mouse. (says more about me than web2py).
> > I can imagine it would be great to have an option to have a "tail -f
> > web2pydebug.log" running in a terminal to see the debugging
> > information running over my screen while i reload a page with
> > problems.
>
> > It imagine it could also be an idea for the people who use web2py in
> > production to configure web2py to log to their syslog server, so they
> > can use their normal toolings for processing warnings and errorlogs.
>
> > Not logging by default, i like the default behaviour to be clean.
> > Just an option to switch on logging in a syslog standard way, or to a
> > local logfile would be nice.
>
> > Kind regards,
>
> > Jean-Paul
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
[web2py:37888] Re: starting web2py in the foreground for debugging
For the record, i changed the import line in the index() function to:
{{{
from gluon.restricted import RestrictedError
}}}
Else the browser gives me an errorpage, that it gets a redirect that
will never complete.
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
[web2py] SQLFORM.grid many2many name of referenced table instead of id
Is it possible to show the referenced name field, instead of the id
when showing a grid of a many2many table?
my model:
tsmadm.define_table('report_contact',
Field ('report_id', db.reports,
requires=IS_IN_DB(db, db.reports.id,'%(name)s') ),
Field ('contact_id', db.contacts,
requires=IS_IN_DB(db, db.contacts.id,'%(name)s') ),
)
my controller:
def reportcontact():
gridquery=(rc.report_id==int(request.vars.rid))
grid = SQLFORM.grid(gridquery,)
return dict(grid=grid)
result looks like
idreport_id contact_id
1 1 2view edit delete
3 1 1view edit delete
As you can see the numbers don't give me any information, i would like
to see
In other forms, taken from the model, i get drop downs based on the
name.
I would expect the default view of this grid would also show the
names, instead of the id's - taken from the model (requires
IS_IN_DB).
Jean-Paul
[web2py] skeleton.css resetting possible css mistake
With web2py 1.99.7 i try to display preformatted code between " " but the result does not look like preformatted text should look like. . In skeleton.css on line 28 i found that pre is being reset to default (inherit) font, I think this might be the cause. After I removed pre from line 28 in skeleton.css it looked ok. Can somebody confirm this is a mistake ?
