[web2py] Problem with admin debugger still in 2.17.1
I occasionally use the admin debugger package to investigate problems when running in my test environment on Windows 10 using the source distribution of web2py and Python 2.7 When I place a breakpoint on the code and execute my test case the interactive debugger is triggered, and I can step through code, examine variables, etc. When I have gathered the information I need and click 'continue' the application indeed continues and can be used as normal (though I think it runs slowly, as if the debugger is still checking). The problem is that the debugger will no longer work. Code will execute straight through either previously or newly set breakpoints without going into debug mode. Only shutting down the test server and restarting it works. I raised this a long time ago in the context of 2.16.1, problem still exists in 2.17.1. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Re: Future of web2py
Not sure if this thread is finished yet but I would like to add my requests for the new framework. * Something with a mobile first perspective would be nice. * Data and page caching on client side. * And offline capabilities. That said, it goes without saying it would need some kind of syncing capabilities. :-) On Saturday, May 27, 2017 at 3:11:02 AM UTC-4, Andrea Fae' wrote: > > Hello guys, > I'd like to know if there will be future of web2py? Any information about > it? > Thanks > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Strange behaviour of calendar size in grid?
Hello,
I am using bootstrap3_stacked formstyle in grid. Everything works fine
except one thing (calendar size) please refer image for more information.
NOTE- I am using Version-2.16.1
#modal
db.define_tabel('name',
Field('date_of_entry','date',default=date.today(),label="Date Of
Entry"),..)
#Controller
grid = SQLFORM.grid(query,maxtextlength=250,paginate=10,formstyle
='bootstrap3_stacked',)
Please suggest where am I going wrong?
Thanks
SP
[image: calender.PNG]
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[web2py] Re: UPDATE BOOTSTRAP VERSION FROM 3 TO 4
Leonel, could you go into a bit more depth on the changes you had to make in the menu? I would certainly appreciate it. On Wednesday, April 26, 2017 at 8:51:15 AM UTC-5, Leonel Câmara wrote: > > The forms in Boostrap 4 are pretty much the same as in bootstrap 3, you do > need to change some stuff in the menu and grid. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Re: web2py 2.17.1
I have this problem too, there are a few forms where for information
clarity I want to show fields which cannot be changed in a particular
context.
On Monday, October 1, 2018 at 7:43:06 AM UTC-4, Awe wrote:
>
> Well, yes I think it breaks something,
> in 2.16.1 this was fine:
> form = SQLFORM.factory(
> Field('always_show', default='123', readable=True, writable=False),
> Field('writable_if_intended', default='456', readable=True,
> writable=True),
> readonly=False,
> )
> Both fields were shown, first field as textonly, and second one as
> edit/input field
>
> In 2.17.1
> print form.fields
> ->['id', 'writable_if_intended']
> The first field does not appear, so all my forms a broken for the moment
> and I do not know how to
> create a form with mixed intentions for the fields (readable only / and
> writable fields)
>
> many thanks for your help,
> Andreas
>
>
>
> Am Montag, 13. August 2018 03:36:06 UTC+2 schrieb Massimo Di Pierro:
>>
>> On second look this is correct and intentional and fixed a bug. this form
>> is a from a factory and there is no record. the field is not writable
>> therefore it can only be displayed in read-only mode but there is no value
>> (record) to display.
>>
>> Does it break something?
>>
>> On Sunday, 12 August 2018 12:52:31 UTC-7, Jim Karsten wrote:
>>>
>>> I'm seeing a change in behaviour between versions 2.16.1 and 2.17.1.
>>>
>>> form = SQLFORM.factory(Field('name', writable=False))
>>> print form.fields
>>>
>>> # In 2.16.1 prints: ['id', 'name']
>>> # In 2.17.1 prints: ['id']
>>>
>>> Is this intentional?
>>>
>>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
