For what it's worth, I disagree with the last statement completely.  I've 
used other frameworks and feel the documentation for web2py is far superior.

Some best practices docs would be nice but that hardly qualifies as poor 
documentation.

-Jim


On Friday, June 23, 2017 at 3:04:11 PM UTC-5, Oasis Agano wrote:
>
> It can be cool to have best practices documentations too;
>
> Unit testing(with auth,decorated methods...),
>
> Continuous Integration(Either travis-ci or jenkins...),
>
> because web2py may have many features but the documentation is still very 
> poor.
>
> kr,
> Oasis
>
>
> On Monday, June 5, 2017 at 10:39:11 AM UTC+2, Karoly Kantor wrote:
>>
>> Dear Massimo,
>>
>> I saw your question in the developers group where I cannot post, 
>> therefore i do it here.
>>
>> I am currently aware of the following issues to be fixed:
>>
>> 1. Google 2nd generation SQL is definitely a problem. Please note I made 
>> a temporary hack to fix it, described here: 
>> https://groups.google.com/forum/?fromgroups=#!topic/web2py/vs39zZpaH7g
>>
>> 2. We have a long overdue issue with the password reset emails not 
>> sending on GAE. I am using a temporary dirty workaround that sends a plain 
>> text new password, search for the issue about "lazyT object being passed to 
>> GAE".
>>
>> 3. I am having trouble making the date picker work nicely across all 
>> browsers, especially where there is a native solution. Microsoft Edge is 
>> the worst case. In general, would be good to have a nicer date picker
>>
>> 4. General comment: We have "batteries included", however, some of those 
>> batteries now have newer versions than included, e.g. bootstrap
>>
>>
>>
>>
>>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to