Hi Yarko, I like the pure CSS cascading menu.
Could you make it color neutral and post the required CSS for three
levels of nested popup menus assuming
<a href="#">click me to open menu</a>
<ul class="menu-level-1">
<li><a href="#">menu1</a>
<ul class="menu-level-2">
<li><a href="#">menu11</a>
<ul class="menu-level-4>
<li><a href="#">menu111</a>
</li>
...
</ul>
</li>
...
</ul>
</li>
...
</ul>
Massimo
On 27 Apr, 21:23, Yarko Tymciurak <[email protected]> wrote:
> Well, I, almost gagged adapting (very old sytle) corporate layout standards
> to a default web2py layout, and as of this weekend - well, it's not that I
> gave up so much, as it is I was just too bored with it to go on.
> Tonight, I'm back to looking thru old links I have surrounding the beauty of
> css elements, and ran across this (in case anyone wants to join in some
> experimentations):http://code.google.com/p/css-template-layout/ (for
> this:http://www.w3.org/TR/2009/WD-css3-layout-20090402/)
>
> I also, today, was again reminded of the simple beauty of this from Eric
> Meyer:
>
> and thinking of a nice SVG web2py image with elements from these:
>
> http://meyerweb.com/eric/css/edge/complexspiral/demo.htmlhttp://meyerweb.com/eric/css/edge/menus/demo.html
>
> Anybody else see anything clean, neat that is simple?
> (I like the css only menus, and am eager - in a minute - to start trying out
> code to load that contextually.... it just looks so clean from the source
> side).
>
> On Mon, Apr 27, 2009 at 9:05 PM, mdipierro <[email protected]> wrote:
>
> > I deleted that page because it is misleading and old. There are two
> > issues:
>
> > 1) the technical reason for your error is that
>
> > @f
> > def g(): return 'something'
>
> > is equivalent to
>
> > def g(): return 'something'
> > g=f(g())
>
> > and in your case f (i.e. run) does not take arguments.
>
> > 2) anyway the post is misleading because this is all already coded for
> > you and part of web2py core functionality. Here is a complete example
> > you can put in your controller
>
> > ### begin
> > from gluon.tools import Service
> > service=Service(globals())
>
> > @service.run
> > @service.json
> > def create(name): return name
>
> > def call(): return service()
> > ### end
>
> > now visit
> >http://..../call/run/create/Dave
> >http://..../call/run/create?name=Dave
> >http://..../call/json/create/Dave
> >http://..../call/json/create?name=Dave
>
> > same for xmlrpc, pyamf, etc. This is documented partially in the gluon/
> > tools file.
>
> > Massimo
>
> > On 27 Apr, 20:30, Dave <[email protected]> wrote:
> > > Hello,
> > > I'm following the steps given on AlterEgo to define fancy decorators.
> > > (http://mdp.cti.depaul.edu/AlterEgo/default/show/204). I'm only
> > > exposing procedures through run and am getting a TypeError.
>
> > > Here's the code in my model:
> > > from gluon.storage import Storage
> > > settings=Storage()
> > > settings.exposed_procedures=[]
>
> > > def expose(f):
> > > settings.exposed_procedures.append(f.__name__)
> > > return f
>
> > > And the code in my controller:
> > > def run():
> > > if request.args and request.args[0] in
> > > settings.exposed_procedures:
> > > return eval('%s(*request.args[1:],**dict
> > > (request.vars))'%request.args[0])
> > > return 'Not Authorized'
>
> > > @run
> > > def create(name):
> > > print name
>
> > > I appreciate any feedback on this typeerror. Also, can I assume this
> > > should work the same way service decorators do? Is there any
> > > advantage?
>
> > > Thanks,
> > > Dave
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
