I am looking Flash MX, and know about rich client side. And I think if the Zope 3 have a flash like rich client side, It can help Zope 3 spread more quickly, and popular not only in the web, but alse on mobile . and can make it more easy to develop a application through the web browser then now.
And one thing in server side. it is much stronger than flash, because zope 3. [EMAIL PROTECTED] wrote:
Send Zope3-users mailing list submissions tozope3-users@zope.orgTo subscribe or unsubscribe via the World Wide Web, visithttp://mail.zope.org/mailman/listinfo/zope3-usersor, via email, send a message with subject or body 'help' to[EMAIL PROTECTED]You can reach the person managing the list at[EMAIL PROTECTED]When replying, please edit your Subject line so it is more specificthan "Re: Contents of Zope3-users digest..."Today's Topics:1. Re: Re: Traverse to nearest site in menu action (Stephan Richter)2. Re: Traverse to nearest site in menu action (j?rgen Kartnaller)--Message: 1Date: Sat, 2 Apr 2005 07:37:18 -0500From: Stephan Richter <[EMAIL PROTECTED]>Subject: Re: [Zope3-Users]
Re:
Traverse to nearest site in menu actionTo: zope3-users@zope.orgCc: j?rgen Kartnaller <[EMAIL PROTECTED]>Message-ID: <[EMAIL PROTECTED]>Content-Type: text/plain; charset="utf-8"On Saturday 02 April 2005 04:38, j眉rgen Kartnaller wrote:> > Why in the world would you want to do that? This seems just awful. What> > is your use case?>> In my case I want to have the possibility to jump back to my base view> (which is the default view of my site) from wherever I am within my site.>> But, if there is an easier way to do this, please let me know.Then write a wrapper view for all interfaces that internally looks up the next site and looks up the default view:class SiteDefaultView(object):def __call__(self):site = getNextSiteSomehow()defaultViewName = getDefaultViewName(site, self.request, site)view = zapi.getMultiAdapter((s
ite,
request), Interface, name=defaultViewName)return view()Regards,Stephan-- Stephan RichterCBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)Web2k - Web Software Design, Development and Training--Message: 2Date: Sat, 02 Apr 2005 16:27:07 +0200From: j?rgen Kartnaller <[EMAIL PROTECTED]>Subject: [Zope3-Users] Re: Traverse to nearest site in menu actionTo: zope3-users@zope.orgMessage-ID: <[EMAIL PROTECTED]>Content-Type: text/plain; charset=UTF-8; format=flowedStephan Richter wrote:> On Saturday 02 April 2005 04:38, j眉rgen Kartnaller wrote:> >>>Why in the world would you want to do that? This seems just awful. What>>>is your use case?In my case I want to have the possibility to jump back to my base view>>(which is the default view of my site) from wherever I am with
in my
site.But, if there is an easier way to do this, please let me know.> > > Then write a wrapper view for all interfaces that internally looks up the next > site and looks up the default view:> > class SiteDefaultView(object):> > def __call__(self):> site = getNextSiteSomehow()> defaultViewName = getDefaultViewName(site, self.request, site)> view = zapi.getMultiAdapter((site, request), Interface, name=defaultViewName)> return view()> Thanks Stephan,I learned a lot from this code.But I think my solution is much easier to handle.I don't need to define a view for every interface.I just have to implement my traverser which is a one liner.ZCML is also reusable, it could be easily integrated into zope as a standard traverser
;)J眉rgen--___Zope3-users mailing listZope3-users@zope.orghttp://mail.zope.org/mailman/listinfo/zope3-usersEnd of Zope3-users Digest, Vol 6, Issue 3*Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂美女明星应有尽有，搜遍美图、艳图和酷图
1G就是1000兆，雅虎电邮自助扩容！___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
