web2py 2.1

[Massimo DiPierro]

I think we should released 2.1. We have some important bug fixes and we have some new features. I do not see a reason to keep users to 2.0 which has some known bugs.

Massimo

[Massimo DiPierro]

[Francisco Costa]

+1

Francisco Costa
http://franciscocosta.com

On Sat, Sep 29, 2012 at 2:27 AM, Massimo DiPierro <mdip...@cs.depaul.edu> wrote:

I think we should released 2.1. We have some important bug fixes and we have some new features. I do not see a reason to keep users to 2.0 which has some known bugs.

Massimo

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details    : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official    : http://www.web2py.com/

[Niphlod]

I'd first fix the issue with Rows and the pickle method associated to them.
When you cache Rows using something different than cache.ram  they come back as a list and no .find(), .exclude(), etc. is available.

[Massimo DiPierro]

yes, we can do that.

[Richard Vézina]

I found this problem :

http://stackoverflow.com/questions/11124777/twitter-bootstrap-navbar-fixed-top-overlapping-site

I don't like the workaround since if the navbar is more height, it is not anymore a solution.

I also notice that when the page is longer the stuff scroll under the navbar... It may be probably the behavior of bootstrap, but I would like to know what other think about that, should the body scroll under the navbar or not?

It is not a big deal and should not retard the release of 2.1 thought.

Richard

[Richard Vézina]

Ok, there is also : navbar-static-top, only have to change navbar-fixed-top, for static.

I would prefer have fixed, but I think it will need a bit of jQuery to change dynamically the body padding top depending of the number of row of the navbar...

Richard

[LightDot]

I personally like the current navbar defaults in general, but this is really a matter of "the eye of the beholder". I don't think I actually used the default in any of the designs of ours. I wouldn't, no matter what the default was, since every page / app is so different.

The welcome app is supposed to be hacked, deleted, obliterated to pieces, etc., so navbar is probably changed / adjusted / customized in one way or another in every single custom design out there. As for js dinamically changing the padding... I really don't see the need. Once it's set properly, it's set. So why running javascript every single time?

Regards,
Ales

[Osman Masood]

Agree with that, man. I mean, are there ANY web2py apps in production that keep the default styles and stuff?

[Alec Taylor]

Niphlod: Maybe a set?

Or if we want to get closer to Google's infrastructure, a Bloom Filter?

[Alec Taylor]

Sounds good,

Also, would it be possible to get sanction integration for web2py 2.1,
or soon after?

https://github.com/demianbrecht/sanction

[Massimo DiPierro]

So, I believe this has been addressed.

There are still some issues with cron and scheduler being reported but not clear if those are problems with apps. Once those are settled, can we release 2.1? Or I am forgetting something else important?

Massimo

On Sep 29, 2012, at 7:05 AM, Niphlod wrote:

[Niphlod]

it's quite clear that with the scheduler the new dal creates some issues.
Unfortunately the latest problem reported by adi on web2py-users stands. When you use a db with migrate=False, or migrate_enabled=False, or fake_migrate_all the new DAL replies back with an exception that it can't duplicate a singleton.
https://github.com/web2py/web2py/blob/master/gluon/dal.py#L6600
Unfortunately, I can't get where the problem lies into the scheduler's code.

[Massimo DiPierro]

I will try reproduce it later today.

We may need a copy method in the DAL class. We just need to understand where the copy is called.

[Mariano Reingart]

Yesterday I tried to debug with web2py 2.0 in the class room and it didn't work.

Setting a breakpoint was throwing an error "line doesn't exist" or similar

It was just me or anyone else has issues with the debugger?

Line number is detected correctly, so it shouldn't be an editor issue,
but sadly I lost track of last changes because lack of time.

Best regards,

Mariano Reingart
http://www.sistemasagiles.com.ar
http://reingart.blogspot.com

[Massimo DiPierro]

Honestly I have not used it recently. I cannot thing of any change that may have affected the debugger.

[szimszon]

I can too reproduce my problem with the sched...  http://code.google.com/p/web2py/issues/detail?id=1070 There is a little app you can try too...

[Massimo DiPierro]

I understand the problem…. The problem is that the task is executed in the same thread as the scheduler. web2py does not like the second db = DAL(…). If there are no attributes, it recycles the first. If there are attributes, it does not know what to do. This mechanism needs a little more thought. I can remove the check but I need to figure out the consequences.