O
> The issue isn't simply whether there have been changes in the file but
>> whether there have been changes in the file that are directly linked to
>> changes in the core framework. web2py.js includes code that depends on
>> particular HTML classes and data-* attributes generated by web2py HT
On Wednesday, January 6, 2016 at 5:30:25 PM UTC+1, Anthony wrote:
>
>
>> I guess, this is more-less what I need to do, but this is not perfect, as
>> I have several applications that I maintain and updating all of them
>> manually is not great. Also - is this the only file that should be update
>
> I guess, this is more-less what I need to do, but this is not perfect, as
> I have several applications that I maintain and updating all of them
> manually is not great. Also - is this the only file that should be updated
> in this way? I am not sure... What about web2py_ajax.html? appadmi
On Wednesday, January 6, 2016 at 1:58:19 PM UTC+1, Anthony wrote:
>
>
> Well, any time you upgrade the framework, you should always upgrade
> web2py.js (no need to check whether it has changed -- just do it).
>
>
I guess, this is more-less what I need to do, but this is not perfect, as I
have s
On Monday, January 4, 2016 at 6:20:42 PM UTC-5, Krzysztof Socha wrote:
>
> Ok. I think I got it... I started developing my application long time ago
> based on a welcome app. I have updated web2py regularly, but I have not
> updated original welcome application files that are specific to web2py,
Ok. I think I got it... I started developing my application long time ago
based on a welcome app. I have updated web2py regularly, but I have not
updated original welcome application files that are specific to web2py,
such as web2py.js It appears that there have been changes there as well,
but
Oops, got it. Still can't reproduce.
On Thursday, December 31, 2015 at 5:23:38 PM UTC-5, Krzysztof Socha wrote:
>
> As I wrote:
>
> 2.13.4-stable+timestamp.2015.12.26.04.59.39
> (Running on nginx/1.4.6, Python 2.7.6)
>
> Strange... I will have to investigate a bit more, than. I will report
> back
As I wrote:
2.13.4-stable+timestamp.2015.12.26.04.59.39
(Running on nginx/1.4.6, Python 2.7.6)
Strange... I will have to investigate a bit more, than. I will report back,
what I find.
Krzysztof.
On Thursday, December 31, 2015 at 10:38:10 PM UTC+1, Anthony wrote:
>
> Sorry, tried your exact cod
Sorry, tried your exact code and it works for me. Which version of web2py?
Maybe attach a minimal app that demonstrates the problem.
Anthony
On Thursday, December 31, 2015 at 3:39:37 PM UTC-5, Krzysztof Socha wrote:
>
> Anthony,
>
> Thank you for (very) quick reaction! And Happy New Year! ;)
>
>
Anthony,
Thank you for (very) quick reaction! And Happy New Year! ;)
Here is an example:
I define a grid in the following action:
def grid_test():
grid = SQLFORM.grid(db.project, formname='grid_test',selectable=[('Test',
lambda ids: 1/0)])
response.view = 'project/grid.load'
return dict(grid=gr
A basic example works for me. Can you show some code that you know exhibits
the problem?
Anthony
On Thursday, December 31, 2015 at 12:53:53 PM UTC-5, Krzysztof Socha wrote:
>
> I noticed a similar thing... I need two grids on a page. As documented, it
> does not work very well to simply put the
I noticed a similar thing... I need two grids on a page. As documented, it
does not work very well to simply put them in one controller function.
Hence, I tried with LOADing a component. This generally works, but I cannot
get the selectable actions to work. I have defined custom selectable
acti
12 matches
Mail list logo
