]]>
]]>
]]>
]]>
]]>
http://labs.adobe.com
Flash Builder 4瀹夎鍖呭皢浼氭牴鎹綘鎿嶄綔緋葷粺鐨勮璦閰嶇疆涓鴻嫳鏂囧拰綆浣撲腑鏂囩殑閫夋嫨銆備笅闈㈡槸閮ㄥ垎鏉ヨ嚜Release Notes鐨勭炕璇戙?br /> 鏂板鍔熻兘錛?br /> Flex SDK
* 寮曞叆涓涓叏鏂扮殑鍔熻兘寮哄ぇ鐨勭粍浠剁毊鑲ゆ鏋訛紝鍙仛Spark銆?br /> * 鍩轟簬Spark妗嗘灦榪涜鍒濆鍖栫殑緇勪歡鍙互涓嶧lex3涓殑Halo緇勪歡闆嗗悎娣峰悎鍜屽尮閰嶄嬌鐢ㄣ?br /> * 鏀寔澹版槑鍖栫殑錛屽姩鎬佺殑MXML鍥懼艦錛屼互鍙奆XG鏍煎紡鐨勫浘褰€?br /> * 鍏ㄦ柊鐨凷park榛樿澶栬錛屾敮鎸佸叏鏂扮殑鏍峰紡闆嗗悎銆?br /> * 鏇村己澶х殑甯冨眬鏀寔錛屽寘鎷敮鎸丮XML鍥懼艦鍏冪礌錛屽寮哄浜庣炕杞拰鍏朵粬鍙樺艦鐨勬敮鎸侊紝鏀寔鎸囧畾鑷畾涔夌殑甯冨眬錛屽寮簔杞寸鐞嗐?br /> * 涓浜涙柊鐨勫拰澧炲己鐨勭壒鏁堬紝鍖呮嫭鏀寔MXML鍥懼艦鍏冪礌鐨勫姩鐢伙紝閫氳繃鑷畾涔夌殑鍔ㄧ敾淇敼錛屾洿澶氭槗鐢ㄧ殑API璋冪敤鏂瑰紡錛屾洿澶氱殑鑷姩鍖栫殑浜や簰琛屼負銆?br /> * 3D鐗規晥鏀寔
* Flash鍔ㄧ敾婊ら暅錛屽寘鎷琍ixel Bender銆?br /> * 鏇村楂樼駭瀛椾綋鏀寔銆傚熀浜嶧lash Text 寮曟搸鍜孴ext甯冨眬妗嗘灦錛屼篃鏀寔CFF錛圕ompact Font Format錛夈?br /> * 緙栬瘧鍣ㄦц兘鎻愬崌銆?br /> * 鏂扮殑MXML璇█鍔熻兘錛屽寘鎷琈XML 2009鍛藉悕絀洪棿錛屽０鏄庯紝搴撳拰鏍囩瀹氫箟銆?br /> * CSS澧炲己錛屽寘鎷敮鎸佸懡鍚嶇┖闂達紝緇ф壙閫夋嫨鍣紝ID閫夋嫨鍣紝鏇村鐨勭被閫夋嫨鍣ㄥ拰閽堝緇勪歡鐘舵佺殑浼夋嫨鍣ㄦ敮鎸併?br /> * 璇硶澧炲己鍜岀姸鎬乻tates澧炲己銆?br /> * 鏂逛究鐨勬暟鎹弻鍚戠粦瀹氳娉曘?br /> * ASDoc鏀寔鍦╩xml鏂囦歡閲岀殑緇勪歡銆?br /> * 澧炲己鐨凥TML妯℃澘錛屽熀浜嶴WFObject銆?br /> * adobe.com瀛樻斁 SDK榪愯鏃跺叡浜簱RSL銆?br /> * 棰濆鐨勬湰鍦板寲鏀寔錛屾洿濂界殑寮鍙戞湰鍦板寲搴旂敤銆?br />
Flash Builder鏂板姛鑳?br />
* 涓涓潰鍚戝垱寤烘暟鎹湇鍔″簲鐢ㄧ殑鏂板伐浣滄祦錛堝寘鎷珻F,PHP,Java,WebServices錛夈?br /> * 鏀寔鐢盕lash Catalyst鍒涘緩鐨凢XG欏圭洰
* 涓涓叏鏂扮殑Network鐩戞帶錛屽府鍔╄瘖鏂鎴風鍜屾湇鍔″櫒孌電殑閫氳闂
* Flex 鍗曞厓嫻嬭瘯鏁村悎銆?br /> * 鑷姩鐢熸垚getter鍜宻etter銆?br /> * ASDoc鏀寔鍦∕XML鍜孉S涓樉紺篈SDoc娉ㄩ噴
* 鑷畾涔夋枃浠舵ā鏉挎敮鎸丮XML錛孉S鍜孋SS鏂囦歡銆?br /> * 鑷姩鐢熸垚浜嬩歡澶勭悊鍑芥暟緇撴瀯銆?br /> * 璋冭瘯鍣ㄥ寮恒?br /> * Profiler澧炲己銆?br /> * Refactoring澧炲己
* 鏂扮殑Component kit for Flash CS4
* 鏂版敮鎸佸懡浠よ鏋勫緩鎵ц鏂瑰紡銆?br /> * 瀵煎叆鍜屽簲鐢‵lex涓婚鏂扮敤鎴風晫闈€?br /> * 鏂扮殑Flex綾誨寘嫻忚鍣ㄦ浛浠lex Navigator闈㈡澘銆?
]]>
]]>
]]>
]]>
]]>
From Adobe Labs
Product Codename: "Thermo"
"Thermo" is an upcoming Adobe product that makes it easy for designers to create rich Internet application UIs. Thermo allows designers to build on familiar workflows to visually create working applications that easily flow into production and development.
Features
- Use drawing tools to create original graphics, wireframe an application design, or manipulate artwork imported from Adobe Creative Suite tools.
- Turn artwork from Adobe Photoshop, Illustrator, or Fireworks directly into functional components that use the original artwork as a “skin”.
- Define and wire up interactive behavior, such as what to do when a user clicks on something, without having to write code.
- Easily design UIs that work with dynamic data, such as a list of contacts or product information, without having access to the actual data source. Design-time sample data can be used as a realistic placeholder when laying out an application, testing interactivity, and choreographing motion.
Applications created in Thermo are Flex applications that can be loaded directly into Flex Builder, providing a great roundtrip workflow for designers collaborating with developers. The designer's work can be incorporated directly into the production application with no loss of fidelity, and designers can continue to refine the design throughout the iterative development process.
Check back for more details on Thermo soon!
]]>
1. Flex Builder 3/AIR beta2 on lab
榪欎袱鏍蜂笢瑗夸細鍦?span> max 鏈熼棿鏀懼嚭 beta 2 (M5) 搴旇綆楁槸鏃ч椈錛岃繕鏈変漢浜嬪厛涓嶇煡閬撴墠鏄瘮杈冨鎬?/span>beta2 鏈韓鐨勬柊鍔熻兘鍦?wiki 涓婃湁璇︾粏浠嬬粛錛屼絾閲嶇偣涓嶅涔庡湪 IDE 鏈韓鐨勫己鍖栥?span>AIR 鏁村悎銆?span>CSS 璁捐涓?span> Profiler絳夈?/span>姣旇緝閲嶈鐨勬槸澶ф鏈変笁鐐?/span>-鏂板敭浠峰嚭鏉ヤ簡錛屽皢鏉?span> FB 鍒嗕袱縐嶇増鏈?/span>
Standard: $299
Pro: $699Standard 姣旂幇鍦?span> $499 榪橀檷200鍏冿紝鎵浠ョ幇鍦ㄦ槸嫻佽鏂扮増鏈兘瑕侀檷涓ょ櫨鍚?/span>錛熶笉榪囨病鏈?span> charting component, 榪欎簺鐜╂剰(鍖呭惈鍍?span> AdvancedDataGrid 榪欑 visual data component絳?span>)閮界Щ鍒?span> Pro 鐗堛?/span>榪欐牱鍋氱殑鎰忎箟寰堟槑鏄撅紝涓昏灝辨槸瑕佸ぇ騫呴檷浣?span> flex 鐨勮繘鍏ラ棬鍧庯紝鍘熸湰瑕?span>$499 鎵嶈兘鏈夋嫢鏈?span> IDE錛岀幇鍦ㄥ彧瑕?span> $299 鍑犱箮鏄漢浜轟拱鐨勮搗錛屽彟涓鏂歸潰錛屽姣忓ぉ闈犲紑鍙?span> flex 涓虹敓鐨勪漢鏉ヨ錛屽皢濂芥枡鐨勪竴嬈″叏濉炲叆pro鐗堬紝鑰屼笖姣旂幇鍦?span> $799 浣庝簡 100鍏冿紝涔熺畻鏄柟渚胯澶氾紝鑷沖皯浠樹竴嬈￠挶灝卞彲浠ヤ拱鍒板叏閮ㄧ殑涓滆タ(鑰屼笉鐢ㄥ啀涓鏍鋒牱鍘諱粯璐圭劧鍚庢嫾璧鋒潵)錛岃繖涓競鍦虹瓥鐣ヤ笉閿欍?/span>-Linux 鐗堥棶甯?/span>
榪欎笘鐣屼笂浼間箮鏈夊緢澶氫漢涓鐩存兂鍦?span> linux 涓婂紑鍙?span> flex錛岃屼笖鍙敤 text editor + sdk 榪樹笉澶燂紝涓瀹氳鏈?span> IDE 鎵嶈繃鐦撅紝鐜板湪鍙О蹇冨鎰忎簡錛?span>beta鐗堝凡鍙湪 lab 涓婁笅杞姐?/span>-flex testing framework 鏀逛負鍏嶈垂
浠ュ線瑕佺敤 Mercury Quicktest Pro 鏉ュ仛 UI testing 鏃訛紝蹇呴渶瑕佸厛瑁?span> testing framework, 浣嗗畠闇瑕佷竴緇?span> FDS 鐨勫簭鍙鋒墠鑳戒嬌鐢紝鑰屽嚑涔庢病浜轟細鎰挎剰鑺?span> $6,000-$12,000鐨勪環閽卞幓涔拌繖鐜╂剰銆?/span>涓や釜鏈堝墠鎴戝湪鐜╂煇涓?span>fb3 beta 鐗堟湰鏃訛紝鎰忓鍦ㄥ畨瑁呯洰褰曚笅鍙戠幇灞呯劧鍐呭緩浜嗚繖涓?span> installer錛岃屼笖榪樼湡鐨勫彲浠ヨ涔熷彲浠ョ敤錛岄偅鏃舵垜浠ヤ負鏄彧鏄崟綰殑鎰忓涓嶅皬蹇冨寘浜嗚繘鍘?span>(鎴栨槸 adobe 蹇冩兂鍙嶆鍗栦笉鎺夊共鑴嗘涔愬ぇ鏀鵑?span>)錛岀幇鍦ㄦ墠鐭ラ亾鍘熸潵榪欎簺鏄晠鎰忕殑鍟?span>~
2. Thermo
綺楃暐綆浠嬬湅榪欓噷
Max 鏈熼棿鍙︿竴涓噸澶存垙灝辨槸 Thermo 鍒濅寒鐩革紝緗戠粶涓婂凡緇忔湁涓浜涘獎鐗囧彲鐪嬨?/span>
鐩墠鐪嬫潵瀹冪殑鎿嶄綔鏂瑰紡寰堝儚 adobe 浜у搧鐨勫ぇ鍚堜綋錛屾垜瑙傚療鍒扮殑鍖呭惈-鍙洿鎺ヨ鍏?span> Photoshop PSD 妗ｏ紝騫朵笖褰撶劧淇濈暀鎵鏈夌殑 layer 淇℃伅涓?span> meta info
-璇誨叆鐨?span> psd 妗ｄ細浠?span> tracing image 鐨勬柟寮忔樉紺哄湪搴曞眰(榪欐槸璺?span> dreamweaver 涓?span> golive 鍊熸潵鐨勬蹇?span>)-鍙敤綾諱技 edit in place (榪欐槸 fireworks, image ready, golive 鏃朵唬灝辨湁鐨勪笢瑗?span>)灝嗙敾闈㈠厓绱犺漿鎹負 mxml 緇勪歡錛岃屼笖浼氫繚鐣?span> style info-杞崲鎴?span> mxml 鍚庝細浣跨敤鏂扮殑 tag 鏉ユ爣璇嗭紝渚嬪 mx:bitmapGraphic 涓?/span>mx:borderSkinFactory-鍙埗浣滃涓?span> state 騫跺湪鍏墮棿鍒囨崲(榪欒窡 fireworks cs3 閲屾柊鍑虹幇鐨?span> page 闈㈡澘姒傚康瀹屽叏涓鑷?span>)-鎷ユ湁 timeline 鍙埗浣?span> transition/effect錛屼緥濡?span> mouseover 鏃舵煇涓璞¤娓愬ぇ鎴栨笎灝忕瓑鍙樺寲錛屼箥鐪嬩箣涓嬪緢鍍忔槸 flash 闄勮韓 XD鏁存褰辯墖鐪嬪畬鍒濇鐨勬劅瑙夊涓嬶細1銆佹垜鑷沖皯鍦?span> thermo 閲岀湅鍒?span> photoshop, flash, fireworks, dreamweaver, image ready, golive 絳夎蔣浠剁殑鍔熻兘涓庡獎瀛愶紝榪欏簲璇ュ彲璇存槸鍚堝茍鍚?span> 1+1 > 2 鐨勪緥瀛愪箣涓鍚?/span>2銆佺洰鍓嶇湅鏉ュ伐浣滄祦紼嬩細鏄繖鏍?/span>Photoshop -> Thermo < -> Flex涔熷氨鏄瑙夌殑涓滆タ 70% 閮藉湪 photoshop/illustrator 閲屽仛濂斤紝鐒跺悗灝?span> psd 涓㈢粰 thermo 鍋?span> interaction design錛屼絾瀹冧篃鍚屾椂鎻愪緵浜?span> mxml 浜х敓鍣紝璁╄璁″笀鍙互灝嗚繘涓姝ヨ法鐣屽皢瑙嗚鍏冪礌杞垚鍙紪紼嬬殑 mxml 緇勪歡錛屾渶鍚庝氦緇欏伐紼嬪笀鍘?span> coding銆?/span>3銆佽嚦浜?span> thermo 瀹炰笉瀹炵敤鍛紵鍡紝榪欒鐪嬩綘鎬庝箞瀹氫綅瀹冦?/span>浠庡巻鍙蹭笂鏉ョ湅錛岀被浼?span> fireworks/image ready 榪欑 psd to html 浜х敓鍣ㄧ殑宸ヤ綔嫻佺▼鍩烘湰涓婁粠鏉ユ病鎴愬姛榪囷紝鍥犱負 one-way 寮忕殑浠?span> psd 鍒?span> html 鎴栬寰堝鏄擄紝浣嗗綋 html 瑕佸洖鍒?span> psd 鏃訛紝鍥伴毦搴﹀氨寰堥珮錛屽埌鏈鍚庨兘鏄庡伐浜烘櫤鎱с忔潵瑙ｅ喅銆?/span>浣嗗鏋滀粠 quick-prototyping or Proof of Concept(POC)鐨勮搴︽潵鐪嬶紝thermo 鍙兘浼氭槸寰堝ソ鐨勫府鎵嬶紝鍥犱負璁捐甯堝彲浠ュ敖鎯呯殑鍙戞尌瑙嗚璁捐灝嗙編緹庣殑鐗堥潰鍋氬嚭鏉ワ紝鐒跺悗閫忚繃 thermo 浜х敓鍙疄闄呮搷浣滅殑 flex 鎺ュ彛錛岃繖鏍峰鎴峰彲浠ョ湅鐨勫埌涔熸懜鐨勫埌灝嗘潵瀹為檯鎴愬搧鍙兘鐨勬牱璨岋紝鍒朵綔鍥㈤槦涔熻兘姣旇緝瀹屾暣鐨勬帉鎻″鎴鋒兂瑕佺殑涓滆タ銆?/span>鑷充簬鐪熸瑕佸紑濮嬪埗浣?span> flex app鏃訛紝鎴戞兂 thermo 鐨勫府鍔╁氨涓嶅ぇ錛屽洜涓鴻涓嶆噦紼嬪簭鐨勮璁″笀鏉ュ府蹇欏垏 ui 緇勪歡錛熷喅瀹氭瘡涓?span> module 璇ュ浣曠敾鍒嗭紵榪欐牱鍐掔殑椋庨櫓瀹炲湪澶ぇ錛屽垏鍑烘潵鐨?span>mxml 澶ф涔熸病娉曠敤錛屾渶鍚庤繕鏄閲嶆柊鏉ャ?/span>浣嗚繖鍙堝甫鍒板彟涓涓浮鐢熻泲銆佽泲鐢熼浮鐨勮侀棶棰樸?/span>Thermo 涔? 鎵浠ヤ細鍑虹幇錛屾槸涓轟簡瑙ｅ喅宸ョ▼甯堜笉鎳傚浣曞皢瑙嗚鐢婚潰杞崲涓烘垚鍝侊紝鍥犳甯屾湜鐢辮璁″笀鏉ュ府蹇欒繖浠朵簨錛屼絾鐢辮璁″笀鏉ュ仛榪欎歡浜嬬己鐐逛篃寰堝錛屼笂闈篃宸茬◢寰В閲婏紝鎵浠ヨ繖 浠嶇劧鏄竴涓袱闅劇殑闂錛屼篃灝辨槸璁捐甯堝府蹇欏垏鐢婚潰錛屽垏鍑烘潵鐨勪笢瑗垮彲鑳藉伐紼嬪笀瑙夊緱涓嶅ソ鐢ㄦ垨鏃犳硶鐢紝浣嗙敱宸ョ▼甯堝幓鍒囩敾闈紝鍙兘鏁存敮紼嬪簭鐢婚潰涔熷氨姣佷簡錛屾墍浠ユ渶緇堜笅 鍦哄樊涓嶅銆?/span>渚濇垜榪欏嚑騫村叏鑱屽紑鍙?span> flash/flex 鐨勭粡楠屾潵鐪嬶紝浠ュ線璁稿浜烘彁鍑虹殑
graphic designer - interaction designer - developer 涓夌駭鍒嗗伐鍒跺彧鑳界畻鏄涓姝ワ紝thermo 鐨勫嚭鐜板彲鑳藉彲浠ュ疄璐ㄥ府鍒?span> interaction designer 鐨勫繖錛屼絾 interaction designer 鍒?span> developer 榪欐浠嶇劧浼氭槸鏂眰錛岃岃В鍐充箣閬擄紝鍒欐槸瑕佹壘鍒頒竴涓柟寮忓皢榪?span> missing link 緇欒ˉ璧鋒潵錛岃繖涔熷皢鏄?span> thermo 鎴愯觸鐨勬渶澶у叧閿?span>(鐩墠鐪嬫潵錛?span>blend/expression/xaml 鐨勫皾璇曚笉鐢氭垚鍔燂紝甯屾湜 adobe鍙互鍙﹁瀹冮旇浜虹溂鐫涗竴浜晩)
3. Flash Player 10 (codename Astro)
FP9 浠?span> as2 鍙戝睍鍒?span> as3 鍙鏄?span> flash 鍗佸勾鏉ユ渶鎯婁漢鐨勫ぇ璺冭繘錛屽嚑涔庡畬鍏ㄦ敼鍐欎簡 RIA 鐨勫巻鍙詫紝鍘熸湰浠ヤ負澶ф寰堥毦鍐嶇湅鍒板悓鏍?span> level 鐨勬敼鐗堬紝浣嗗緢鏄劇劧鎴戦敊浜嗐?/span>FP10 鏂板鐨勫嚑涓噸鐐瑰姛鑳藉ぇ鐣ュ寘鍚?/span>-綆鏄撶殑 hardware 3D support錛氱湅鏉ュ師鏈墦姝諱笉鎰挎剰涓?span> fp 鍔犲叆3d鍔熻兘鐨?span> engineering team 榪樻槸寰堥『搴旀皯鎯呭晩錛屽綋鐒剁洰鍓嶇湅鍒扮殑 3d 鍔熻兘榪橀潪甯告湁闄愶紝鏈変漢縐板畠涓?span> 2.5D錛屼篃鏈変漢縐頒負 card-game style 3D錛屼笉榪囧氨鎴戝 flash player team 鐨勪簡瑙ｏ紝灝嗘潵鍐呭緩鐨?span> 3D 鍔熻兘榪戒笂 Papervision3D 搴旇鏄病闂鐨勩?/span>-advanced text layout: 榪欏寘鍚簡 multi-column 鐨勮蛋鏂囨柟寮忥紝涔熷寘鍚簡 right-to-left layout(RTL)錛岃繖涓や歡浜嬪湪榪囧幓鎴戜滑閮介亣榪囷紝鍘誨勾鍒朵綔鐨勪竴涓ぇ鍨?span>app鍦ㄥ鍥借璦鍖栨椂錛屽鎴峰眳鐒墮棶錛氥庡笇浼潵鏂囩増鐨勬帴鍙ｆ枃瀛楀簲璇ユ槸浠庡彸鍒板乏鍟婏紝鍙互鏀逛竴涓嬪悧錛熴忓綋鏃跺績閲岀殑鍥炵瓟錛氥庡綋鐒跺彲浠ワ紝浣犲厛涔頒笅 flash player team 浜ょ粰鎴戞寚鎸ワ紝鎴戜繚璇佸崐騫村唴鐢熷嚭鏉ョ粰浣?span>…銆忕幇鍦ㄨ繖浠朵簨鍙畝鍗曞浜嗭紝鍙槸 UI Component 閮ㄤ喚瑕佹敼鍐欑殑涓滆タ榪樻槸寰堣垂鍔涘晩銆?/span>-custom filter/effect with “Hydra” image processing language:
榪欑畻鏄潪甯告湁瓚ｇ殑鏂扮帺鎰忥紝Hydra 鏄竴縐嶇被浼?span> C 鐨勮璦錛?span>user 鍙敤瀹冪紪杈戣嚜宸茬嫭闂ㄧ殑 filter/effect錛屼箣鍓嶆湁 Vector/Bitmap API 澶у灝卞凡緇忕帺鍑轟竴鍫嗙柉鐙傜殑鎶婃垙錛岀幇鍦ㄦ湁浜嗘洿 low-level 鐨勫伐鍏鳳紝鍛靛懙鍛碉紝綺懼僵鍙湡錛屽彧鏄互鍚庢暀 flash 鐨勮甯堟槸涓嶆槸涔熻榪涗慨涓涓?span> C/C++ 浜?span>? Orz
4. Flash Lite 3 鎺ㄥ嚭
鍔熻兘浠嬬粛鐪?span>榪欓噷閲嶇偣鏈?/span>
-flash home: 榪欎釜綆楁槸鐪熸鐨勬柊鐜╂剰錛屼互寰 flash lite 閮芥槸浠?span> app 鐨勫瀷寮忓瓨鍦ㄤ簬鎵嬫満涓婏紝涔熷氨鏄鐢ㄦ椂鎵嶅惎鍔紝浣?span> flash home 鍒欐槸鐩存帴鐢?span> flash lite 鍙栦唬鎺夋墜鏈虹殑寮鏈虹敾闈紝涓寮鏈哄畬灝辨槸 flash lite 鍦ㄩ偅閲岋紝鑰屼笖瀹冩槸 instant on銆?/span>涔嬪墠鏇捐亰榪?span> LG phone 鏁翠釜 UI 閮界敤 flash lite 鍐欐垚錛岀幇鍦ㄥ垯鏄洿榪涗竴姝ユ敾鍗犱簡寮鏈虹敾闈紝鏈潵鐨勫彂灞曢潪甯告湁瓚ｅ晩錛屽笇鏈涘畠鑳藉敖蹇拷涓?span> as3 鐨勮剼姝ワ紝鎶婁紶璇翠腑鐨?span> flex framework for mobile 鎼嚭鏉ワ紝灞婃椂鍙氨鐜╁埌涔愮炕澶╀簡銆?/span>-as2 support: 榪欎釜濂藉儚鍠婂緢涔呬簡錛岀幇鍦ㄧ湡鐨勬敮鎸?span> class 浜嗗悧錛?/span>
-flv support: 榪欎釜鍒版槸寰堥噸瑕佺殑鏂板姛鑳斤紝涓嶈繃宸茬粡涓嶆槸鏂伴椈錛屼粖騫村垵鏃跺氨宸插彂琛?/span>
-xml loading: 浠?span> flash lite 2.1 璧峰氨鍙互鏀寔 socket server錛屾墍浠ヨ鍦ㄦ墜鏈轟笂鐜?span> push/pull 鍙樼殑闈炲父綆鍗?/span>
5. VOIP in flash
FP 灝嗘敮鎸?span> voip 涓嶆槸鏂伴椈錛屼絾鐪熸鐪嬪埌瀹冭繍浣滆繕鏄悡涓璺熾?/span>Pacifica 鏄繖涓駭鍝佺殑浠ｅ彿錛屽畠灝嗘彁渚涗笅鍒楀姛鑳?span>:Version 1:
* HQ voice chat
* text instant messaging
* presence
* NAT/Firewall traversal
* Ajax/HTML, Flash/FlexFuture Roadmap:
* video chat
* p2p
* AIR
* PSTN Access瑕佹敞鎰忕殑閲嶇偣鏄繖鍑犱釜瀛?span>: VoIP, SIP, SDP 涓?span> P2P銆?/span>
浣犺兘鎯寵薄涓鏃?span> flash player 鏈韓鍐呭緩 VoIP 涓?span> SIP 鏀寔鍚庯紝鍙兘鐨勫簲鐢ㄦ湁澶氬箍鍚楋紵綆鍗曟潵璇達紝涓婇潰listing 閲岄潰闅忎究涓欏癸紝閮藉彲浠ュ皢榪欎釜涓栫晫鍐嶇炕涓閬嶏紝宸笉澶氬氨鏄繖鏍風殑褰卞搷鍔涖?/span>
6. CoCoMo
榪欏彲涓嶆槸 Adobe 涓?Beach Boys 鐨勫紓涓氱粨鐩熴?/span>CoCoMo 鏄?span> Adobe Connect (涔熷氨鏄?span> Breeze) 鏂扮増鏈殑浠ｅ彿錛屼笉鍑烘墍鏂欐灉鐒剁敤 flex 鍏ㄩ儴鏀瑰啓錛屼絾鏇存儕浜虹殑鏄畠寮濮嬬帺璧峰彟涓涓洿鏈夋綔鍔涚殑甯傚満錛?span>API platform !灝嗘潵 flex developer 鍙搷浣?span> Adobe Connect 鐨?span> API 鏉ュ埗浣滃悇縐?span> desktop sharing, audio/video chat & collaboration錛岀浉杈冧箣涓嬶紝涔嬪墠鐐掔殑鐏儹鐨?span> facebook platform 瀹炲湪鏄病浠涔堝晩(涓嶈繃褰撶劧榪欎袱鑰呭彲浠ユ槸瀹岀編鐨勪簰琛ワ紝涓嶄竴瀹氭槸闆跺悎娓告垙)銆?/span>
7. Share
涓涓?span>鍦ㄧ嚎鏂囦歡銆佸垎浜侀槄璇葷殑騫沖彴錛屾瘡涓?span>user 鏈?span> 1gb 絀洪棿銆?/span>鍚屾牱鐢?span> flex 鍐欐垚錛岀敤浜嗚澶氱啛鎮夌殑緇勪歡錛屼緥濡?span> page component (oh, the great Ely!) 涓?span> flash paper錛屼篃鎻愪緵 REST style API 鍙緵 mesh up錛屽皢鏉ユ墦綆楁暣鍚?span> Buzzword 鎻愪緵緙栬緫鍔熻兘銆?/span>浠庢湰璐ㄦ潵鐪嬶紝online-doc sharing 榪欑涓滆タ褰撶劧鏃╁氨鏈変漢鍋氳繃浜嗭紝緗戠粶涓婇殢渚塊兘鍙互鎵懼埌涓鐙楃エ錛屽悓鏍鋒槸璁╀漢涓婁紶鏂囦歡錛岀劧鍚庤漿妗ｆ垚 swf 鍐嶇敤 flash player 鏉ョ湅錛岄偅 adobe 鍙堜綍鑻﹀憿錛?/span>灝辨垜鏉ョ湅錛?span>Share 鏄?span> adobe 鍦?span> web publishing 鏂歸潰鐨勬柊灝濊瘯錛屼富瑕佸埄鐢ㄧ殑浼樺娍褰撶劧灝辨槸鑷鐨?span> PDF 涓?span> flash player錛屼絾璺熷叾瀹冨崟綰彧鏄?web 2.0 startup 鍏徃涓嶅悓鐨勬槸錛?span>adobe 蹇冮噷鎯崇殑搴旇鏄畠瀹屾暣鐨?span> electronic publishing 騫沖彴錛屼粠鍐呭銆佸埗浣溿佺敓鎴愬埌娑堣垂錛屽笇鏈涜兘閫氶氬寘涓嬫潵錛屽緩绔嬪ぇ涓緇熺殑浣撶郴錛屾垜鐩鎬俊 Share 涓庝箣鍓嶄粙緇嶈繃鐨?span> ebook reader 閮藉彧鏄繖涓鍒掍笅鐨勯儴浠戒駭鐗╋紝鏈潵鍙戝睍榪樺緟瑙傚療銆?/span>
8. C/C++ to AS3 conversion
榪欎釜鐜╂剰闈炲父鏈夎叮錛岃繖浣嶇浜哄啓浜嗕竴涓?span> compiler錛屽彲浠ュ皢 C/C++ 鐨?span> code 鐩存帴杞瘧鎴?span> AS3錛岀劧鍚庡啀緙栬瘧鎴?span> swf 渚?span> flash/flex/air 浣跨敤錛岀幇鍦烘渶鍙︿漢闇囨捈鐨?span> demo 灝辨槸浠栫洿鎺ュ皢 Quake (涓涓?span> doom-like 鐨勫皠鍑繪父鎴?span>) 緙栬瘧鎴?span> flash 鐗堢劧鍚庣帺浜嗚搗鏉ワ紝浣犲彲浠ユ兂瑙佺幇鍦轟細鐤媯鍒頒粈涔堢▼搴?span>!! (鏇撮叿鐨勬槸榪欎綅宸ョ▼甯堣繕鏄竴鍓鉤娣＄殑琛ㄦ儏錛岀湡姝ｆ槸鎵尓鍚冭佽檸鐨勬瀬鑷磋〃鐜板晩)銆?/span>濂斤紝鐑儏瀹屾瘯錛屾帴鐫鍒嗘瀽甯堜笂韜?/span>鎴戜富瑕佹濊冪殑鏄笅鍒椾笁鐐癸細1. 涓轟綍闇瑕佽繖涓笢瑗匡紵涓婂浘涓洓涓钀藉啓鐫 (ruby, php, python, lua), 瀹冧唬琛ㄤ粈涔堬紵
2. 榪欎笢瑗胯儗鍚庣殑浼佸浘鏄粈涔堬紵
3. 璋佷細鑾風泭錛熷畠鍙互鐢ㄥ湪浠涔堝湴鏂癸紵鍙戝睍娼滃姏鏈夊澶э紵鍩烘湰涓婃垜宸茬粡鏈変簡涓濂楀ぇ鑷寸殑鎯蟲硶涓庣悊璁猴紝浣嗗緢鏈夊叴瓚ｆ兂鍚惉鍚勪綅鐨勬兂娉曘?/span>
9. Adobe 涔頒笅 Buzzword
榪欎歡浜嬪叾瀹炲嚑涓湀鍓嶅氨鏈夐澹板嚭鏉ワ紝褰?adobe 絎竴鎵瑰伐紼嬪笀榪涢┗ buzzword 鍔炲叕瀹ゆ椂錛屾槑鐪間漢灝辯煡閬撴槸鎬庝箞鍥炰簨浜嗭紝鍙嶈屾瘮杈冨鎬殑涓轟綍 SlideRocket 涓鐩磋皥涓嶄笅鏉?span>(瓚佷漢瀹惰繕娌?span> IPO 鍓嶅鎾掔偣閽卞揩鐐規悶瀹氬皢鏉ユ瘮杈冨ソ鍔炰簨鍟?span>)錛?/span>浠庡競鍦鴻搴︽潵鐪嬶紝Buzzword(綾諱技 word 鐨勬枃瀛楃紪杈戝櫒) 涓?span> SlideRocket(綾諱技 powerpoint 鐨勭畝鍗曡蔣浠?span>) 搴旇鏄綋浠?span> RIA 涓氱晫鏈淇變唬琛ㄦт笌鏉浼ゅ姏鐨勪袱鏀?span>app錛屽畠浠嚑涔庢湁鎾煎姩 Office 甯傚満鐨勮兘鍔涳紝鍥犳 adobe 瀵瑰畠浠殑閲嶈涓庡叧鐖卞彲璇存槸鍏舵潵鏈夎嚜錛屼撼涓嶅鎬?/span>姣旇緝鍊煎緱瑙傚療鐨勫皢鏄紝榪熸棭 Adobe 鎵嬩笂浼氭湁 word, powerpoint 涓?span> excel 鍏煎鐨勮蔣浠?span>(褰撶劧鏄?span> built with Flex/AIR)錛屽眾鏃朵笘鐣屼笂鍙湁鍥涢棿涓繪祦鍟嗕笟鍏徃鏈夋垚鐔熺殑 office 浜у搧(OO.o 榪欑灝卞厛涓嶇畻榪涙潵錛屽憙錛屽ソ錛屽叾瀹炶繕鏈?span> IBM Lotus Symphony錛屼笉榪囩煡鍚嶅害涓嶉珮涔熷厛鏀句竴杈?span>)-Microsoft: Office 鐨勯湼涓誨湴浣嶆棤搴哥疆鐤戯紝runs on desktop only
-Apple: Mac 涓婄殑 Office 闇鎬富, runs on desktop only
-Google: Doc 緋誨垪浜у搧錛岀畻鏄洰鍓?span> web-based 閲屾渶鎴愮啛鐨勪竴瀹?/span>
-Adobe: 鍚屾牱涓?span> web-based, 浣嗗洜涓洪噰鐢?span> flash 鍒朵綔錛屽洜姝ゆ搷浣滄帴鍙ｄ笌鍔熻兘灝嗘槑鏄捐秴瓚?span> google docs (涓庡叾瀹?span> ajax 緋誨垪鐨?span> office-apps)鑰屽叾涓彧鏈?span> google 涓?span> adobe 宸茬粡寰堢Н鏋佸湪 web-based 榪欏潡娣辮?span>(MS鐨?span> office live 鍒欒繕鏈垚鐔?span>)錛屼粠瓚嬪娍鏉ョ湅(on-line, access everywhere, collaboration, messaging)錛?span>web寮忕殑浜у搧鍓嶉旀槸姣旇緝鐪嬪ソ鐨勶紝鑰屼粠鎶鏈潰鏉ョ湅錛?span>flash寮忕殑 web app 寰寰鍙堟瘮 ajax 寮忕殑濂戒竴鐐?span>(鑷沖皯鍦?span> tool 綰ц繖涓鍩?span>)錛屾墍浠?span> adobe 鍙互璇存槸宸茬粡绔欏湪姣旇緝鏈夊埄鐨?span> position錛岃繖鏄緢鏈夎叮涔熷煎緱瑙傚療鐨勪簨(鑰屼笖瑕佺潄澶х溂鐫涘ソ濂界湅鐫)銆?/span>
10. Flash CS4 涓?/strong> Fireworks
CS4Flash 閮ㄤ喚鏈夎澶氫笉閿欑殑鏂板姛鑳斤紝渚嬪鍙湪 authoring time live preview video content錛?span>timeline 澶ф敼鑹?span>, tween 鏂瑰紡鏇磋嚜鐢憋紝浠ュ強紲炲鐨?span> IK 鏁堟灉錛屾垜鎯沖鑳芥帉鎻¤繖浜涙柊涓滆タ鐨勫濯掍綋璁捐甯堟潵璇達紝榪欏簲璇ユ槸闈炲父媯掔殑娑堟伅銆?/span>Fireworks 閮ㄤ喚鍒欐槸寮鴻皟涓?span> flex 鐨勬暣鍚堬紝渚嬪鍙湪 fireworks 閲屽埗浣滅粍浠朵笌style/skin 鐒跺悗鐩存帴杈撳嚭鏈?span> scale-9 鐨?span> swc 緇?span> flex 鐢紝鍩烘湰涓婇兘榪樻槸寰堢矖嫻呯殑鏁村悎灝濊瘯錛屾湭鏉?span>12涓湀榪樿澶氬姫鍔涖?/span>
鎬葷粨
緇艱浠ヤ笂 highlight 鍑烘潵鐨?span> 10鐐癸紝濡傛灉浣犱粩緇嗗幓鎺ㄦ暡姣忎竴鐐硅儗鍚庢墍浠ｈ〃鐨勬剰涔夛紝騫舵濊冨畠浠湭鏉ュ彲鑳界殑褰卞搷鍔涗笌鍐插嚮鏁堝簲錛屾垨璁鎬綘浼氬儚鎴戜竴鏍瘋寰楀叏韜彂鐑績璺沖姞蹇?/span>鍩烘湰涓婅瀵熻繖嬈?span> Max 鎻湶鐨勬秷鎭紝鎰熻寰堝儚鍦ㄧ湅楂樻墜瀵瑰紙錛屽綋浣犵湅鍒板眬涓竴姝ユ鏃訛紝灝辯煡閬撹儨璐熷凡瀹氾紝鏈潵鎵鏈夌殑姝ユ暟鐨嗗凡紜畾錛岀粨鏋滃彧鏄椂闂撮棶棰橈紝鑰屾洿浠や漢鎯婅鐨勬槸錛屽線寰榪欒嚧鑳滅殑涓姝ユ槸濡傛鐨勪笉鏄庢樉涓庝笉緇忔剰錛岃交杞葷殑婊戣繃灝卞喅瀹氫簡鏈潵錛岃繖鎵嶆槸鐪熸璁╀漢鑷徆寮楀鐨勫湴鏂廣?/span>鎯沖埌榪欓噷錛屽彧鑳借榪欑湡鐨勬槸涓涓?span> exciting times錛屽緢楂樺叴鑳界疆韜叾涓佷翰鑷粡鍘嗚屼笉鏄湪鍗佸勾鍚庡洖澶存潵璧炲徆褰撳勾銆?/span>
]]>
]]>
]]>
]]>
]]>
Often when you need to embed a font
you also need to include ‘bold’ and sometimes ‘italic’ styles.
Sometimes you need more than one fontFamily. Flex by default will embed
all glyphs of a fontFamily. Embedding every glyph if generally
unnecessary. By restricting the character set (’unicode-range’) you can
shave off between 50-100kb or more per font style (FontFamilies have
varying amounts of glyphs and obviously varying complexities of
outlines which effects how much you can save). Anyway by setting
unicode-range for fonts we managed to shave 300kb off our application,
I wasn’t expecting it to be so much so thought worth a blog ;)
@font-face {
src: url("assets/Arial.ttf");
fontFamily: Arial;
advancedAntiAliasing: true;
unicode-range: U+0030-U+0039, /* 0-9 */
U+0041-U+005A, /* Uppercase A-Z */
U+0061-U+007A, /* Lowercase a-z */
U+0021-U+002F, /* !"#$%&'()*+,-./ */
U+003A-U+0040, /* :;<=>?@ */
U+005B-U+0060, /* [\]^_ */
U+00A3-U+00A3, /* £ */
U+00A9-U+00A9, /* © */
U+00AE-U+00AE /* ® */
/* U+00BF-U+0259 FOREIGN CHRS */
}
if anyone knows of other ranges you think can be generally useful please let me know ;)
]]>
]]>
]]>
]]>
]]>
]]>
]]>
鍏充簬浜嬩歡嫻?/strong>
褰撲簨浠跺彂鐢熷悗鐢熸垚涓涓惡甯︽暟鎹殑瀵硅薄錛岀劧鍚庢鏌ョ洰鏍囧璞℃槸鍚﹀瓨鍦ㄦ樉紺哄眰涓紝騫墮亶鍘嗕粠鏍瑰鍣ㄤ竴鐩村埌鐩爣瀵硅薄鎵鍦ㄤ綅緗殑鎵鏈夊璞★紝浠ユ爲褰㈠娍琛ㄧず銆傝嚜鍔ㄦ嫻嬫墍緇忚繃鐨勮妭鐐規槸鍚︽敞鍐屼簡鐩戝惉鍣ㄣ?br id="e5.g" />
浜嬩歡嫻佹殫榪愯嫻佺▼鍒嗕負3姝ワ細
- 鎹曡幏闃舵錛氭崟鑾蜂簨浠?capturing錛屼粠鏍硅妭鐐瑰紑濮嬮『搴忚屼笅錛屾嫻嬫瘡涓妭鐐規槸鍚︽敞鍐屼簡鐩戝惉鍣ㄣ傚悓鏃訛紝Flex 灝嗕簨浠跺璞＄殑currentTarget 鍊兼敼涓哄綋鍓嶆鍦ㄦ嫻嬬殑瀵硅薄銆傚鏋滄敞鍐屼簡鐩戝惉鍣紝鍒欒皟鐢ㄧ洃鍚嚱鏁般?br id="y1rr3" />
- 鐩爣闃舵錛氭嫻嬬洰鏍囩殑鐩戝惉鍣?targeting錛氳Е鍙戝湪鐩爣瀵硅薄鏈韓娉ㄥ唽鐨勭洃鍚▼搴?br id="ti7p" />
- 鍐掓場闃舵錛氫簨浠跺啋娉?bubbling錛氫粠鐩爣鑺傜偣鍒版牴鑺傜偣錛屾嫻嬫瘡涓妭鐐規槸鍚︽敞鍐屼簡鐩戝惉鍣紝濡傛灉鏈夛紝鍒欒皟鐢ㄧ洃鍚嚱鏁般?/li>
姣忎釜浜嬩歡瀵硅薄閮芥湁浠ヤ笅灞炴э細
target錛氫簨浠剁殑媧懼彂鑰?br id="oani0" /> currentTarget錛氬綋鍓嶆鍦ㄦ嫻嬬殑鐨勫璞★紝甯姪璺熻釜浜嬩歡浼犳挱鐨勮繃紼嬨?br id="vp2g" />
榛樿鎯呭喌涓嬶紝鎹曡幏鍔熻兘澶勪簬鍏抽棴鐘舵侊紝涓鑸病鏈夊繀瑕佽繘琛屾崟鑾瘋窡韙?br id="tcta" /> 浜嬩歡鍙湪bubbles 灞炴т負true 鏃舵墠榪涜鍐掓場錛屽彲浠ュ啋娉＄殑浜嬩歡鍖呮嫭錛歝hange銆乧lick銆乨oubleClick銆乲eyDown銆乲eyUp銆乵ouseDown銆? mouseUp銆傚茍涓斾笉鑳藉湪涓涓洃鍚櫒涓悓鏃舵墦寮鎹曡幏鍜屽啋娉″姛鑳斤紝瑕佸仛鍒拌繖涓鐐癸紝鍙兘娉ㄥ唽涓や釜鐩戝惉鍣紝鍒嗗埆瀹炵幇銆?br id="r61a" />
鐜板湪鏉ョ湅涓涓緥瀛愶細
- <?xml version="1.0" encoding="utf-8"?>
- <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="initApp()">
- <mx:Style source="style.css" />
- <mx:Script>
- <![CDATA[
- import flash.events.MouseEvent;
- internal function initApp():void{
- canvas_1.addEventListener(MouseEvent.CLICK,pressBtn,true);
- canvas_2.addEventListener(MouseEvent.CLICK,pressBtn);
- btn_1.addEventListener(MouseEvent.CLICK,pressBtn);
- btn_2.addEventListener(MouseEvent.CLICK,pressBtn);
- }
- internal function output(msg:String):void{
- debug_txt.text += msg+"\n";
- }
- internal function pressBtn(evt:MouseEvent):void{
- output("鏄惁鍐掓場--"+evt.bubbles);
- output("鐩爣瀵硅薄-- "+evt.target+" -- "+evt.eventPhase);
- output("閬嶅巻瀵硅薄-- "+evt.currentTarget);
- output("------------");
- }
- ]]>
- </mx:Script>
- <mx:Canvas id = "canvas_1" styleName="box" x="37" y="63" width="445" height="216">
- <mx:Text x="13" y="10" text="Canvas_1"/>
- <mx:Canvas id="canvas_2" styleName="box" x="10" y="102" width="173" height="90">
- <mx:Text x="10" y="10" text="Canvas_2"/>
- <mx:Button id = "btn_2" x="10" y="38" label="Button_2"/>
- </mx:Canvas>
- <mx:Button id="btn_1" x="16" y="38" label="Button_1"/>
- </mx:Canvas>
- <mx:TextArea id="debug_txt" styleName="textBox" x="37" y="304" height="198" width="445"/>
- </mx:Application>
- target錛氭淳鍙戜簨浠剁殑鐩爣瀵硅薄
- currentTarget錛氫簨浠舵祦褰撳墠姝ｇ粡榪囩殑鐩爣瀵硅薄
- bubbles錛氭槸鍚︽墦寮浜嗗啋娉″姛鑳?/li>
- eventPhase錛氫簨浠舵祦褰撳墠鐨勯樁孌碉紝1錛氭崟鑾鳳紝2錛氱洰鏍囷紝3錛氬啋娉?/li>
addEventListener(
type:String, 浜嬩歡鐨勭被鍨?br id="vsyt0" />
listener:Function, 鐩戝惉鍑芥暟
useCapture:Boolean = false, 鏄惁鎵撳紑鎹曡幏鍔熻兘
priority:int = 0, 鐩戝惉鍣ㄤ紭鍏堢駭鍒?br id="vsyt3" />
useWeakReference:Boolean = false 鏄惁浣跨敤寮卞紩鐢?br id="vsyt4" />
)
濡傛灉useCapture 涓簍rue錛屾墦寮浜嗘崟鑾峰姛鑳斤紝鍒欒緇勪歡鐨勫啋娉￠樁孌佃鍙栨秷銆?br id="e-a:" />
鍙湁鍙鍖栫殑瀵硅薄鏈?涓樁孌碉紝鑰屽儚XML絳夐潪鍙鍖栧璞″彧鏈夌洰鏍囬樁孌點?/p>
8.2.2 浜嬩歡瀵硅薄
Event鐨勫睘鎬э細
- bubbles錛氬彧璇伙紝甯冨皵錛屼簨浠舵槸鍚﹀紑鍚啋娉″姛鑳?/li>
- cancelable錛氬彧璇伙紝甯冨皵錛屽鐞嗕簨浠剁殑榛樿琛屼負鏄惁鍙互鍋滄銆備富瑕侀拡瀵逛竴浜涚郴緇熶簨浠訛紝濡傛灉鍊間負true錛屽垯Event鐨刾reventDefault鏂規硶鍙互浣跨敤錛屽惁鍒欎笉鍙敤銆?/li>
- currentTarget錛氬彧璇伙紝瀵硅薄錛屽綋鍓嶆鍦ㄨ皟鐢ㄧ洃鍚櫒鐨勫璞?/li>
- eventPhase錛氬彧璇伙紝鏁存暟錛岃繑鍥炰簨浠舵祦姝ｇ粡鍘嗙殑闃舵銆?錛氭崟鑾鳳紝2錛氱洰鏍囷紝3錛氬啋娉?/li>
- target錛氬彧璇伙紝媧懼彂浜嬩歡鐨勭洰鏍囧璞?/li>
- type錛氬彧璇伙紝瀛楃錛屼簨浠剁被鍨嬨傛瘮濡傞紶鏍囩偣鍑諱簨浠剁殑綾誨瀷錛歝lick錛屽茍琚畾涔変負甯擱噺錛歁ouseEvent.CLICK
鏋勯犲嚱鏁幫細
Event(
type:String, 浜嬩歡綾誨瀷
bubbles:Boolean = false, 鏄惁鍐掓場
cancelable:Boolean = false 鏄惁鍙互鍋滄
)
Event 鐨勬柟娉曪細
- isDefaultPrevented錛氬垽鏂璸reventDefault 鏄惁宸茬粡琚皟鐢?br id="fs65" />
- preventDefault錛氬仠姝簨浠剁殑榛樿琛屼負銆傞拡瀵逛竴浜涚郴緇熶簨浠訛紝cancelable涓簍rue鏃舵墠鍙敤銆?/li>
- stopImmediatePropagation錛氬仠姝㈠綋鍓嶇殑浜嬩歡嫻佷紶鎾紝鍖呮嫭褰撳墠姝ｅ湪澶勭悊鐨勫璞?/li>
- stopPropagation錛氬仠姝㈠綋鍓嶇殑浜嬩歡嫻佷紶鎾紝浣嗕笉浼氬仠姝㈠綋鍓嶆鍦ㄥ鐞嗙殑瀵硅薄
- <?xml version="1.0" encoding="utf-8"?>
- <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="initApp()">
- <mx:Style source="style.css" />
- <mx:Script>
- <![CDATA[
- import flash.events.MouseEvent;
- internal function initApp():void{
- canvas_1.addEventListener(MouseEvent.CLICK,CanvasHandler);
- canvas_2.addEventListener(MouseEvent.CLICK,CanvasHandler);
- canvas_2.addEventListener(MouseEvent.CLICK,pressBtn);
- btn_1.addEventListener(MouseEvent.CLICK,pressBtn);
- }
- internal function output(msg:String):void{
- debug_txt.text += msg+"\n";
- }
- internal function pressBtn(evt:MouseEvent):void{
- output("鏄惁鍐掓場--"+evt.bubbles);
- output("鐩爣瀵硅薄-- "+evt.target+" -- "+evt.eventPhase);
- output("閬嶅巻瀵硅薄-- "+evt.currentTarget);
- output("------------");
- }
- internal function CanvasHandler(evt:MouseEvent):void{
- output("鐩爣瀵硅薄-- "+evt.currentTarget+" -- "+evt.eventPhase);
- //鍋滄浜嬩歡嫻佺殑浼犳挱
- evt.stopImmediatePropagation();
- //evt.stopPropagation();
- }
- ]]>
- </mx:Script>
- <mx:Canvas id = "canvas_1" styleName="box" x="37" y="63" width="425" height="160">
- <mx:Text x="13" y="10" text="Canvas_1"/>
- <mx:Canvas id="canvas_2" styleName="box" x="10" y="52" width="173" height="90">
- <mx:Text x="10" y="10" text="Canvas_2"/>
- <mx:Button id = "btn_1" x="10" y="38" label="Button_1"/>
- </mx:Canvas>
- </mx:Canvas>
- <mx:TextArea id="debug_txt" styleName="textBox" x="37" y="245" height="198" width="425"/>
- </mx:Application>
8.2.3 渚﹀惉鍜屽搷搴斾簨浠?-涓涓睛鍚敭鐩樹簨浠剁殑渚嬪瓙
娉ㄥ唽閿洏鎸変笅浜嬩歡錛屼氦緇檏eyHandler澶勭悊錛屼篃鍙互鍦ˋpplication鏍囩娣誨姞浜嬩歡錛?br id="arpa" /> keyDown="keyHandler(event)" 榪欑鎯呭喌鏃犳硶縐婚櫎浜嬩歡銆?br id="zevr" />
娉ㄥ唽浜嗕簨浠剁洃鍚櫒錛屼嬌鐢ㄥ畬姣曞悗錛屽繀欏諱嬌鐢╮emoveEcentListener 鏂規硶鍒犻櫎鐩戝惉鍑芥暟錛?br id="zevr1" /> removeEcentListener(
type:String, 浜嬩歡綾誨瀷
listener:Function, 鐩戝惉鍑芥暟
useCapture:Boolean = false 鏄惁寮鍚崟鑾峰姛鑳斤紝濡傛灉娉ㄥ唽鏃舵墦寮錛岀Щ闄や篃瑕佹墦寮銆?br id="zevr5" /> )
- <?xml version="1.0" encoding="utf-8"?>
- <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute"
- creationComplete="initApp()">
- <mx:Style source="style.css" />
- <mx:Script>
- <![CDATA[
- import flash.events.KeyboardEvent;
- internal function initApp():void{
- this.addEventListener(KeyboardEvent.KEY_DOWN,keyHandler);
- }
- private function keyHandler(e:KeyboardEvent):void{
- var str:String = "浣犳寜涓嬬殑鏄? "+e.keyCode;
- debug_txt.text += str +"\n";
- }
- ]]>
- </mx:Script>
- <mx:TextArea id="debug_txt" styleName="textBox" x="25" y="78" height="198" width="212" editable="false"/>
- <mx:Text x="25" y="50" text="鎸夐敭鐩樹笂鐨勪換鎰忛敭"/>
- </mx:Application>
]]>
Subtopics
About modules
Modules are SWF files that can be loaded and unloaded by an application. They cannot be run independently of an application, but any number of applications can share the modules.
Modules let you split your application into several pieces, or modules. The main application, or shell, can dynamically load other modules that it requires, when it needs them. It does not have to load all modules when it starts, nor does it have to load any modules if the user does not interact with them. When the application no longer needs a module, it can unload the module to free up memory and resources.
Modular applications have the following benefits:
- Smaller initial download size of the SWF file.
- Shorter load time due to smaller SWF file size.
- Better encapsulation of related aspects of an application. For example, a "reporting" feature can be separated into a module that you can then work on independently.
Benefits of modules
Modules are similar to Runtime Shared Libraries (RSLs) in that they separate code from an application into separately loaded SWF files. Modules are much more flexible than RSLs because modules can be loaded and unloaded at run time and compiled without the application.
Two common scenarios in which using modules is beneficial are a large application with different user paths and a portal application.
An example of the first common scenario is an enormous insurance application that includes thousands of screens, for life insurance, car insurance, health insurance, dental insurance, travel insurance, and veterinary pet insurance.
Using a traditional approach to rich Internet application (RIA) design, you might build a monolithic application with a hierarchical tree of MXML classes. Memory use and start-up time for the application would be significant, and the SWF file size would grow with each new set of functionality.
When using this application, however, any user accesses only a subset of the screens. By refactoring the screens into small groups of modules that are loaded on demand, you can improve the perceived performance of the main application and reduce the memory use. Also, when the application is separated into modules, developers' productivity may increase due to better encapsulation of design. When rebuilding the application, the developers also have to recompile only the single module instead of the entire application.
An example of the second common scenario is a system with a main portal application, written in ActionScript 3, that provides services for numerous portlets. Portlets are configured based on data that is downloaded on a per-user basis. Using the traditional approach, you might build an application that compiles in all known portlets. This is inefficient, both for deployment and development.
By using modules, you can establish an interface that contains portal services, and a generic portlet interface. You can use XML data to determine which modules to load for a given session. When the module is loaded, you obtain a handle to a class factory inside the module, and from that you create an instance of a class that implements the portlet interface. In this scenario, full recompilation is necessary only if the interfaces change.
Module API details
Modules implement a class factory with a standard interface. The product of that class factory implements an interface known to the shell, or the shell implements an interface known to the modules.
By using shared interface definitions, these shared interfaces reduce hard dependencies between the shell and the module. This provides type-safe communication and enforces an abstraction layer without adding significantly to the SWF file size.
The following image shows the relationship between the shell and the module's interfaces:
Creating modular applications
To create a modular application, you create separate classes for each module, plus an application that loads the modules.
To create a modular application:
- Create any number of modules. An MXML-based module file's root tag is
<mx:Module>. ActionScript-based modules extend the ModuleBase class. - Compile each module as if it were an application. You can do this by using the mxmlc command-line compiler or the compiler built into Adobe Flex Builder.
- Create an Application class. This is typically an MXML file whose root tag is
<mx:Application>, but it can also be an ActionScript-only application. - In the Application file, use an
<mx:ModuleLoader>tag to load each of the modules. You can also do this by using theload()method of the mx.modules.ModuleLoader class. For classes that extend ModuleBase, you should use the methods of the ModuleManager class to load them.
The following sections describes these steps in detail.
Creating modules
Modules are classes just like application files. To create a module
in ActionScript, you create a file that extends the
mx.modules.ModuleBase class. To create a module in MXML, you extend the
mx.modules.Module class by creating a file whose root tag is <mx:Module>.
In that tag, ensure that you add any namespaces that are used in that
module. You should also include a type declaration tag at the beginning
of the file.
The following example is a module that includes a Chart control:
<?xml version="1.0"?>
<!-- modules/ColumnChartModule.mxml -->
<mx:Module xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%" >
<mx:Script><![CDATA[
import mx.collections.ArrayCollection;
[Bindable]
public var expenses:ArrayCollection = new ArrayCollection([
{Month:"Jan", Profit:2000, Expenses:1500},
{Month:"Feb", Profit:1000, Expenses:200},
{Month:"Mar", Profit:1500, Expenses:500}
]);
]]></mx:Script>
<mx:ColumnChart id="myChart" dataProvider="{expenses}">
<mx:horizontalAxis>
<mx:CategoryAxis
dataProvider="{expenses}"
categoryField="Month"
/>
</mx:horizontalAxis>
<mx:series>
<mx:ColumnSeries
xField="Month"
yField="Profit"
displayName="Profit"
/>
<mx:ColumnSeries
xField="Month"
yField="Expenses"
displayName="Expenses"
/>
</mx:series>
</mx:ColumnChart>
<mx:Legend dataProvider="{myChart}"/>
</mx:Module>
Compiling modules
You compile the module as you would compile any Flex application using the mxmlc command-line compiler or the Flex Builder compiler. The following command is the simplest mxmlc command:
mxmlc MyModule.mxml
The result is a SWF file that you load into your application as a module. You cannot run the module-based SWF file as a stand-alone Flash application or load it into a browser window. It must be loaded by an application as a module.
Subtopics
Controlling module size
Module size varies based on the components and classes that are used in the module. By default, a module includes all framework code that its components depend on, which can cause modules to be large by linking classes that overlap with the application's classes.
To reduce the size of the modules, you can instruct the module to externalize classes that are included by the application. This includes custom classes and framework classes. The result is that the module only includes the classes it requires, while the framework code and other dependencies are included in the application.
To externalize framework classes, you generate a linker report from
the application that loads the modules, by using mxmlc commands. You
then use this report as input to the module's load-externs compiler option.
To create a linker report:
- Generate the linker report:
mxmlc -link-report=report.xml MyApplication.mxml
- Compile the application SWF file:
mxmlc MyApplication.mxml
- Compile the module:
mxmlc -load-externs=report.xml MyModule.mxml
Recompiling modules
You must recompile the modules if you make changes. Recompiling the main application does not trigger a recompilation of the modules. Similarly, if you change the application file, you do not have to recompile the modules, unless you make changes that might affect the linker report or common code.
|
NOTE |
|
If you externalize the module's dependencies by using the |
MXML-based modules can load other modules. Those modules can load other modules, and so on.
Loading and unloading modules
To load and unload modules you use the load() and unload()
methods of the ModuleLoader class. These methods take no parameters;
the ModuleLoader loads or unloads the module that matches the value of
the current url property.
The following example loads and unloads the module when you click the button:
<?xml version="1.0"?>
<!-- modules/ASModuleLoaderApp.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
import mx.modules.*;
public function createModule(m:ModuleLoader, s:String):void {
if (!m.url) {
m.url = s;
return;
}
m.loadModule();
}
public function removeModule(m:ModuleLoader):void {
m.unloadModule();
}
]]>
</mx:Script>
<mx:Panel title="Module Example"
height="90%"
width="90%"
paddingTop="10"
paddingLeft="10"
paddingRight="10"
paddingBottom="10"
>
<mx:TabNavigator id="tn"
width="100%"
height="100%"
creationPolicy="auto"
>
<mx:VBox id="vb1" label="Column Chart Module">
<mx:Button
label="Load"
click="createModule(chartModuleLoader, l1.text)"
/>
<mx:Button
label="Unload"
click="removeModule(chartModuleLoader)"
/>
<mx:Label id="l1" text="ColumnChartModule.swf"/>
<mx:ModuleLoader id="chartModuleLoader"/>
</mx:VBox>
<mx:VBox id="vb2" label="Form Module">
<mx:Button
label="Load"
click="createModule(formModuleLoader, l2.text)"
/>
<mx:Button
label="Unload"
click="removeModule(formModuleLoader)"
/>
<mx:Label id="l2" text="FormModule.swf"/>
<mx:ModuleLoader id="formModuleLoader"/>
</mx:VBox>
</mx:TabNavigator>
</mx:Panel>
</mx:Application>
Setting the location of a ModuleLoader triggers a call to the loadModule() method, too. This occurs when you first create a ModuleLoader with the url property set. It also occurs if you change the value of that property.
The following example loads the modules without calling the loadModule() method because the url property is set on the <mx:ModuleLoader> tags:
<?xml version="1.0"?>
<!-- modules/URLModuleLoaderApp.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Panel
title="Module Example"
height="90%"
width="90%"
paddingTop="10"
paddingLeft="10"
paddingRight="10"
paddingBottom="10"
>
<mx:Label width="100%" color="blue"
text="Select the tabs to change the panel."/>
<mx:TabNavigator id="tn"
width="100%"
height="100%"
creationPolicy="auto"
>
<mx:VBox id="vb1" label="Column Chart Module">
<mx:Label id="l1" text="ColumnChartModule.swf"/>
<mx:ModuleLoader url="ColumnChartModule.swf"/>
</mx:VBox>
<mx:VBox id="vb2" label="Form Module">
<mx:Label id="l2" text="FormModule.swf"/>
<mx:ModuleLoader url="FormModule.swf"/>
</mx:VBox>
</mx:TabNavigator>
</mx:Panel>
</mx:Application>
When you load a module, Flex ensures that there is only one copy of a module loaded, no matter how many times you call the load() method for that module.
Modules are loaded into the child of the current application domain.
You can specify a different application domain by using the applicationDomain property of the ModuleLoader class.
When two classes of the same name but different implementations are loaded, the first one loaded is the one that is used.
Subtopics
Loading modules from different servers
To load a module from one server into an application running on a different server, you must establish a trust between the module and the application that loads it.
To allow access across domains:
- In your loading application, you must call the
allowDomain()method and specify the target domain from which you load a module. So, specify the target domain in the preinitialize event handler of your application to ensure that the application is set up before the module is loaded. - In the cross-domain file of the remote server where your module is, add an entry that specifies the server on which the loading application is running.
- Load the cross-domain file on the remote server in the preinitialize event handler of your loading application.
- In the loaded module, call the
allowDomain()method so that it can communicate with the loader.
The following example shows the init() method of the loading application:
public function setup():void {
Security.allowDomain("remoteservername");
Security.loadPolicyFile("http://remoteservername/crossdomain.xml");
var request:URLRequest = new URLRequest("http://remoteservername
/crossdomain.xml");
var loader:URLLoader = new URLLoader();
loader.load(request);
}
The following example shows the loaded module's init() method:
public function initMod():void {
Security.allowDomain("loaderservername");
}
The following example shows the cross-domain file that resides on the remote server:
<!-- crossdomain.xml file located at the root of the server -->
<cross-domain-policy>
<allow-access-from domain="loaderservername" to-ports="*"/>
</cross-domain-policy>
For more information about using the cross-domain policy file, see Applying Flex Security in Building and Deploying Flex 2 Applications.
Using ModuleLoader events
The ModuleLoader class triggers several events, including setup, ready, loading, unload, progress, error, and urlChanged.
You can use these events to track the progress of the loading process,
and find out when a module has been unloaded or when the ModuleLoader's
target URL has changed.
Subtopics
Using the error event
The error event gives you an opportunity to gracefully
fail when a module does not load for some reason. In the following
example, you can load and unload a module by using the Button controls.
To trigger an error event, change the URL in the
TextInput control to a module that does not exist. The error handler
displays a message to the user and writes the error message to the
trace log.
Revision 1/10/2007: Minor change to createModule() method.
<?xml version="1.0"?>
<!-- modules/ErrorEventHandler.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
import mx.events.ModuleEvent;
import mx.modules.*;
import mx.controls.Alert;
private function errorHandler(e:ModuleEvent):void {
Alert.show("There was an error loading the module." +
" Please contact the Help Desk.");
trace(e.errorText);
}
public function createModule():void {
if (chartModuleLoader.url == ti1.text) {
// If they are the same, call loadModule.
chartModuleLoader.loadModule();
} else {
// If they are not the same, then change the url,
// which triggers a call to the loadModule() method.
chartModuleLoader.url = ti1.text;
}
}
public function removeModule():void {
chartModuleLoader.unloadModule();
}
]]>
</mx:Script>
<mx:Panel title="Module Example"
height="90%"
width="90%"
paddingTop="10"
paddingLeft="10"
paddingRight="10"
paddingBottom="10"
>
<mx:HBox>
<mx:Label text="URL:"/>
<mx:TextInput width="200" id="ti1" text="ColumnChartModule.swf"/>
<mx:Button label="Load" click="createModule()"/>
<mx:Button label="Unload" click="removeModule()"/>
</mx:HBox>
<mx:ModuleLoader id="chartModuleLoader" error="errorHandler(event)"/>
</mx:Panel>
</mx:Application>
Using the progress event
You can use the progress event to track the progress of a module as it loads. When you add a listener for the progress
event, Flex calls that listener at regular intervals during the
module's loading process. Each time the listener is called, you can
look at the bytesLoaded property of the event. You can compare this to the bytesTotal property to get a percentage of completion.
The following example reports the level of completion during the module's loading process. It also produces a simple progress bar that shows users how close the loading is to being complete.
<?xml version="1.0"?>
<!-- modules/SimpleProgressEventHandler.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
import mx.events.ModuleEvent;
import flash.events.ProgressEvent;
import mx.modules.*;
[Bindable]
public var progBar:String = "";
[Bindable]
public var progMessage:String = "";
private function progressEventHandler(e:ProgressEvent):void {
progBar += ".";
progMessage =
"Module " +
Math.round((e.bytesLoaded/e.bytesTotal) * 100) +
"% loaded";
}
public function createModule():void {
chartModuleLoader.loadModule();
}
public function removeModule():void {
chartModuleLoader.unloadModule();
progBar = "";
progMessage = "";
}
]]>
</mx:Script>
<mx:Panel title="Module Example"
height="90%"
width="90%"
paddingTop="10"
paddingLeft="10"
paddingRight="10"
paddingBottom="10"
>
<mx:HBox>
<mx:Label id="l2" text="{progMessage}"/>
<mx:Label id="l1" text="{progBar}"/>
</mx:HBox>
<mx:Button label="Load" click="createModule()"/>
<mx:Button label="Unload" click="removeModule()"/>
<mx:ModuleLoader
id="chartModuleLoader"
url="ColumnChartModule.swf"
progress="progressEventHandler(event)"
/>
</mx:Panel>
</mx:Application>
You can also connect a module loader to a ProgressBar control. The following example creates a custom component for the ModuleLoader that includes a ProgressBar control. The ProgressBar control displays the progress of the module loading.
<?xml version="1.0"?>
<!-- modules/MySimpleModuleLoader.mxml -->
<mx:ModuleLoader xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
private function clickHandler():void {
if (!url) {
url="ColumnChartModule.swf";
}
loadModule();
}
]]>
</mx:Script>
<mx:ProgressBar
id="progress"
width="100%"
source="{this}"
/>
<mx:HBox width="100%">
<mx:Button
id="load"
label="Load"
click="clickHandler()"
/>
<mx:Button
id="unload"
label="Unload"
click="unloadModule()"
/>
<mx:Button
id="reload"
label="Reload"
click="unloadModule();loadModule();"
/>
</mx:HBox>
</mx:ModuleLoader>
You can use this module in a simple application, as the following example shows:
<?xml version="1.0"?>
<!-- modules/ComplexProgressEventHandler.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" xmlns:local="*">
<mx:Panel title="Module Example"
height="90%"
width="90%"
paddingTop="10"
paddingLeft="10"
paddingRight="10"
paddingBottom="10"
>
<mx:Label text="Use the buttons below to load and unload
the module."/>
<local:MySimpleModuleLoader id="customLoader"/>
</mx:Panel>
</mx:Application>
This example does not change the ProgressBar's label property for all events. For example, if you load and then unload the module, the label
property remains at "LOADING 100%". To adjust the label properly, you
must define other event handlers for the ModuleLoader events, such as unload and error.
]]>
]]>
]]>
]]>