乡下人产国偷v产偷v自拍,国产午夜片在线观看,婷婷成人亚洲综合国产麻豆,久久综合给合久久狠狠狠9

  • <output id="e9wm2"></output>
    <s id="e9wm2"><nobr id="e9wm2"><ins id="e9wm2"></ins></nobr></s>

    • 分享

      [Dojo-interest] Dojo/Qooxdoo/Rico

       weicat 2006-02-21

      [Dojo-interest] Dojo/Qooxdoo/Rico

      Sebastian Werner info at sebastian-werner.net
      Thu Jul 7 11:19:46 PDT 2005


      Alex Russell schrieb:
      > I haven‘t looked at qooxdoo for a month or two but we also have several 
      > other notable (and to my mind, tremendously important) features which 
      > qooxdoo as yet doesn‘t:
      > 
      > 	1.) a package and build system that ensures that you only get what you 
      > need (the distribution file for qooxdoo is 392K, dojo can be as little 
      > as 10K, depending on the profile you build against)
      
      There is a new build script in qooxdoo, too, that can handle these 
      things including the respect of dependencies. With this new script you 
      can down-scale a typical qooxdoo gui script to 200K. And a core qooxdoo 
      script to 50K. qooxdoo‘s target are GUI‘s and so it‘s ok to load 300K or 
      more. If you pipe this to gzip/deflate on server side it‘s only 30-50K 
      and should be ok this way.
      
      > 	2.) using widgets from markup. Dojo lets you declare your widgets in 
      > your pages by adding extra attributes to standard HTML so you don‘t 
      > have to write lengthy script blocks or pack JS data structures to build 
      > and place widgets.
      
      We have used this approach in our previous non-opensource library. In 
      our implementation we have detected the boundaries at this time we want 
      to have full control about the layout. This is not so easy possible if 
      you want to transform/extend existing HTML code, I think. But your dojo 
      guys may have implement this in a better way as we before.
      
      > 	3.) a unified event system (AOP-style)
      
      qooxdoo includes a event interface, too. Also a focus- and selection- 
      handling manager.
      
      > 	4.) fast widget prototyping and customization in markup
      > 	5.) animations and effects
      
      these both are not included in qooxdoo.
      
      Best regards,
      
      Sebastian
      
      > 
      > Regards
      > 
      > On Thursday 07 July 2005 6:29 am, Sebastian Werner wrote:
      > 
      >>Yes, qooxdoo has no interface to use iframes for data communication.
      >>dojo has more feature in these parts, I think.
      >>
      >>Sebastian
      >>
      >>Eelco Hillenius schrieb:
      >>
      >>>My hunch is that Dojo is more generic in handling ‘a(chǎn)jax‘. Qooxdoo
      >>>uses XmlHttpRequest, while Dojo uses internal frames for browsers
      >>>that don‘t support XmlHttpRequest. Could someone confirm whether
      >>>this statement is true?
      >>>
      >>>Eelco
      >>>
      >>>Cameron Shorter wrote:
      >>>
      >>>>Has anyone done a comparison of Qooxdoo and Dojo?
      >>>>If so, is there any way to bring the best of these two projects
      >>>>together?
      >>>>
      >>>>It seems Dojo is strong on the backend, and Qooxdoo is strong with
      >>>>widget rendering.
      >>>
      >>>_______________________________________________
      >>>Dojo-interest mailing list
      >>>Dojo-interest at 
      >>>http:///mailman/listinfo/dojo-interest
      >>
      >>_______________________________________________
      >>Dojo-interest mailing list
      >>Dojo-interest at 
      >>http:///mailman/listinfo/dojo-interest
      > 
      > 
      
      


      More information about the Dojo-interest mailing list

        本站是提供個人知識管理的網(wǎng)絡(luò)存儲空間,所有內(nèi)容均由用戶發(fā)布,不代表本站觀點。請注意甄別內(nèi)容中的聯(lián)系方式、誘導(dǎo)購買等信息,謹防詐騙。如發(fā)現(xiàn)有害或侵權(quán)內(nèi)容,請點擊一鍵舉報。
        轉(zhuǎn)藏 分享 獻花(0

        0條評論

        發(fā)表

        請遵守用戶 評論公約

        類似文章 更多