锘??xml version="1.0" encoding="utf-8" standalone="yes"?>
鍙槸鏈変竴涓緢灝忕殑楹葷儲錛屽氨鏄疪CP鍘熸潵鐨勫紓甯稿璇濇涓殑鍐呭錛屾瘡涓鍙ュ悗闈㈤兘浼氭湁\n錛岃帿闈炲鍥借璦鐨勬椂鍊橽n琚漿涔変簡錛?br />
甯屾湜鍙互寰楀埌鏀硅繘錛?
]]>
涓婃e4鏀懼嚭鐨勫熀浜巜eb鐨処DE灝變嬌鐢╢lash浣滀負浠g爜灞曠ず鍜岀紪杈戠殑緙栬緫鍣紝鐪嬫潵Eclipse紺懼洟涔熸劅瑙夊埌綰殑js鍩烘湰涓婁笉鑳藉畬鎴愪換鍔′簡銆?/p>
Demo涓嬭澆鍦板潃錛?a title="http://www.innoopract.com/fileadmin/user_upload/Bilder/Films/draw2d_640x480.mp4" >http://www.innoopract.com/fileadmin/user_upload/Bilder/Films/draw2d_640x480.mp4
Java紼嬪簭鍛樹滑鍙兘浼氱粡甯擱亣鍒癢indows涓嬬殑UI闂,Java紼嬪簭鎬繪槸鍜學indows鐨勫瑙傜粺涓涓嶈搗鏉?鐗瑰埆鏄疺ista,闅懼害鏇撮珮. 榪欎篃鏄井杞湭鏉ュ紑鏀捐鍒掔殑涓閮ㄥ垎,寰蔣璁や負涓涓棩鐩婂紑鏀?閫忔槑鐨勬柟寮忔鍦ㄥ嚭鐜?涔嬪墠,寰蔣榪樻垚绔嬩簡Linux鐨勪簰鎿嶄綔鎬у疄楠屽,騫朵笌JBoss,Zend Technologies絳夊叕鍙稿疄鐜頒簡鎶鏈悎浣? |
The e4 moniker is a reference to Eclipse 4.0, which would be the next major release number for the classic Eclipse distribution and platform projects. The last three major Eclipse releases shared these version number relationships: Callisto corresponded to the Eclipse platform v3.2, Europa corresponded to the Eclipse platform v3.3, and the upcoming Ganymede release corresponds to the Eclipse platform 3.4.Component Description:The Eclipse Project PMC is announcing a new component, called E4, as part of the Eclipse Project Incubator.
During the Eclipse Project 3.4 release cycle, one of the important plan items was "Create the Eclipse 4.0 Plan". The intent of this work was to identify the most pressing issues that would impact the ongoing success of Eclipse, and come up with a plan to address them. The result was the design of a new platform "e4", which will be the basis for Eclipse 4.0.
The goal of the e4 component is to provide a public venue for the initial explorations that were done, leading up to the e4 design. We expect to continue to work in this area until we have reached consensus on how the full e4 effort will be structured.
While there was some heated discussion over the format and approach of the initial project announcement, the e4 project is likely to become a central test-bed for the various transformations that Eclipse will go through to reach its next major milestone. In the past, major version number increments for Eclipse have represented significant changes for the Eclipse project. The transition to Eclipse 3.0 encompassed the move of Eclipse to the OSGi platform, the announcement and creation of Eclipse rich-client platform, and both a look-and-feel and performance overhaul. The expectation is that Eclipse 4.0 will also represent such a major shift.We on the platform team care passionately about Eclipse. We know you do too. We want to see it live a long, healthy life. We want it to serve its community as best it can. When we can’t achieve that it makes us sad. It’s clear to us that for Eclipse as a platform to remain long lived, vibrant, and relevant, it must be able to change. But the weight of a zillion plug-ins, projects, and API means the path of least resistance is stagnation, and the effort to effect change given the current constraint system is becoming monumental.
Therefore, two things must happen:
- A new space must be carved out in which experimentation can happen, leading to change.
- New people must get involved, bringing with them their energy, ideas, requirements, knowledge, passion.
These two are intrinsically tied.
That is e4.
鎴戞瘡澶╅兘瑕佺湅Eclipse鐨勫悇澶ф柊闂葷粍錛孷E铏界劧璇存槸娌夊瘋浜嗕竴騫達紝浣嗘槸鏂伴椈緇勯噷闈㈣繕鏄瘮杈冪儹闂圭殑錛屾瘡澶╅兘鏈変竴涓ょ瘒闂鏇存柊銆?/p>
In general, the main theme is to get the project back on track and in good shape.
From a goals perspective, we have the following alternatives:
My head tells me to go with (1) and my heart with (2).
Retrieved from "http://wiki.eclipse.org/VE/Roadmap"
鎴戞渶鏈熷緟鐨勮繕鏄疺E瀵逛簬鐢熸垚XML鏂囦歡鐨勬墿灞晘鍔犳補鍟妦VE錛?/p>
鍦ㄩ」鐩欏典笂鍒楀嚭浜嗕竴浜涙綔鍦ㄧ殑鐢ㄩ?
鍦ㄧ敤鎴瘋嚜宸辯殑搴旂敤涓煡鐪婸DF.
鎻愪緵PDF鏂囦歡鐨勬墦鍗伴瑙?
灝哖DF緇樺埗涓篜NG鍥懼儚,鐢ㄤ互鍦ㄦ湇鍔″櫒绔殑Web搴旂敤涓樉紺?
灝哖DF鍚堝茍鍒?D鍦烘櫙涓?
鍦≒DF涔嬩笂緇樺浘,騫跺彲浠ュ湪緗戠粶鏌ョ湅鍣ㄤ腑榪涜鏍囨敞.
铏界劧榪欎釜欏圭洰鏄湪2007騫?2鏈堣寮婧愮殑,浣嗘槸瀹冨嵈鏈変竴孌甸涔呯殑鍘嗗彶:
鍦?003騫?Sun瀹為獙瀹ょ殑涓緹ょ爺絀跺憳寮鍙戝嚭浜哖DF Renderer,褰撴椂瀹冭繕鏄竴嬈捐棰戝崗浣滃伐鍏?Sun(TM)Labs Meeting Suite鐨勪竴閮ㄥ垎.榪欎釜宸ュ叿鍦⊿un鍐呴儴鐨勫垎甯冨紡浼氳涓緱鍒頒簡騫挎硾搴旂敤.Meeting Suite鐨勮璁″垵琛鋒槸鏂逛究浜轟滑浣跨敤OpenOffice鍒涘緩鐨勬枃紼垮仛鍙戣█.
鐜板湪,榪欎釜鍏紬欏圭洰榪樺彧鏄浜庢棭鏈熼樁孌?鎵浠ユ枃妗h祫婧愯繕寰堝噷涔?涔熸病鏈夊緢澶х殑鐢ㄦ埛紺懼尯.浣嗘槸,Joshua Marinacci甯屾湜閫氳繃鎶婅繖涓」鐩紑婧?鎶婇偅浜涘彲鑳戒負欏圭洰璐$尞鍔涢噺鐨勫紑鍙戣呬滑鍑濊仛鎴愪竴涓ぞ鍖?
铏界劧鏈鍘熷鐨勪唬鐮佹槸鏉ヨ嚜Sun鐨?浣嗘垜浠笇鏈涜兘鑾峰緱紺懼尯鐨勯珮搴﹀弬涓?涓轟繚璇佽繖涓鐐?鎴戜滑鑱樿浜咵lluminate鐨凾om Oke鏉ョ鐞嗚繖涓」鐩?浠栧皢鎷呬換欏圭洰鎵鏈夎呭拰棣栧腑鏋舵瀯甯堢殑瑙掕壊.浠栧緢蹇帉鎻′簡鐜版湁鐨勪唬鐮?騫舵湡寰呯潃涓庡叾浠栫殑鍙備笌鑰呰繘琛岃璁?
鎴戜滑鏈寮濮嬬殑鐩爣鏄皢PDF杈撳嚭鎴怬penOffice鏍煎紡,鎵浠ユ湁浜涚壒鎬ц閬楁紡鎺変簡.瀹冨疄鐜頒簡緇濆ぇ澶氭暟鐨凱DF 1.4瑙勮寖,浣嗘槸灝戜簡閫忔槑搴?transparency),濉厖琛ㄥ崟(fill-in forms)鍜屾煇浜涚壒瀹氱殑瀛椾綋緙栫爜.鎴戜滑甯屾湜鏈夊叴瓚g殑寮鍙戣呭彲浠ュ府鍔╂垜浠畬鎴愯繖浜涚壒鎬?
鍙﹀,Josh榪樺皢榪欎釜欏圭洰涓庡叾浠朠DF搴撹繘琛屼簡姣旇緝:JPedal浣跨敤浜咷PL璁稿彲,鎵浠ユ湁浜涘簲鐢ㄦ牴鏈氨娌℃硶鐢ㄥ畠.鎴戜滑璁や負瀵逛簬綾諱技榪欐牱鐨勫簱鑰岃█,浣跨敤LGPL鏄洿濂界殑閫夋嫨.iText涓嶆槸涓涓煡鐪嬪櫒/娓叉煋鍣?瀹冨彲浠ョ敓鎴怭DF鏂囨。,浣嗗茍涓嶈兘鏌ョ湅鏂囨。.榪欒iText鍜孲wingLabs PDF Renderer鍙樻垚浜嗕紭縐鐨勫悎浣滀紮浼?鎴戞湡鐩肩潃鐪嬪埌浜轟滑濡備綍灝嗗畠浠繘琛屽悎騫?
璁塊棶:PDF Renderer: a 100% Java PDF renderer and viewer