I figured out what you did with the layout. You basically copied the
{{block right_sidebar}} content few times in index.html and on the top
before the {{ entend layout.html}} you defined them for example:
{{left_sidebar_enabled=False,right_sidebar_enabled=False,middle_sidebar_enable=False,('message'
in globals())}}
That creates the tile layout broken up in three division. Cool!:-)
On Friday, June 5, 2015 at 5:04:09 PM UTC-4, Ron Chatterjee wrote:
>
> I agree with Niphlod for the most part. Just one note, the whole purpose
> of web2py was just that. As a learning tool for people who are not an
> expert. If you hear Massimo talk. Several times he mentioned, "web
> development doesn't need to be difficult". Thats the reason you run into
> lot of unskilled newbie as you put it. That said. It can be tested once and
> with a disclosure statement like "Use with your own risk. No support is
> provided if the code breaks"....something along that line. My two cents.
>
>
>
> On Friday, June 5, 2015 at 4:31:00 PM UTC-4, Niphlod wrote:
>>
>>
>>
>> On Friday, June 5, 2015 at 10:17:36 PM UTC+2, Rufus wrote:
>>>
>>> On Friday, June 5, 2015 at 3:35:08 PM UTC-4, Niphlod wrote:
>>>
>>>> BTW: until all snippets are continously tested, this is going to become
>>>> the 4th incarnation of a "web2py snippet blog/container/etc" with outdated
>>>> pieces of code within the next year, when the buzz wears off.
>>>>
>>>
>>> Nothing worse than getting broken code samples off the web, is there?
>>> (Well, there are worse things...)
>>> Maybe we can add some fields to each snippet to indicate: which versions
>>> it was tested on, when it was
>>> submitted, when last verified, etc.
>>>
>>>
>> I fell off the wagon too many times to trust again a "repository" of
>> sorts of untested thingies. It's the real truth that bites: there's no
>> manpower available and so if something else (a CI) does the job, it pretty
>> much stays viable until the developer that creates it uses it.
>> Then we get angry users here asking for "why is that not working anymore,
>> wasn't web2py supposed to be backward-compatible..." instead of asking the
>> original developer.
>> Once you put it in a plugin, people won't ever be interested in seeing
>> the code, the damn thing needs to work as intended.
>> They get crazier and crazier about it because web2py userbase is not -
>> that - skilled in python: it attracts lots of newbies for that reason and
>> we (the main developers) need to live with that: no feedback in testing,
>> not interested in poking a bit to maintain it/refresh it, huge interest in
>> being just disappointed.
>>
>>
--
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.
