Adobe Creative Suite 4 Launched

On September 22nd, Adobe has officially released its forth version of Adobe Creative Suite.

You can watch the 1 hour launch event

دول طلعوا شهرين

أنا ماكنتش متصور إن الموضوع هيطلع كده .... الراجل لبس شهرين بس ..... طب هايتفاخر إزاي بالحبس في شهرين دول.

علي العموم يا كبير السجن للجدعان ... الجدعان بجد

أنا اللي أخذت سنة في الريس

مش من زمان أوي ... كان لما تييجي تقابل شاب صايع أو بلطجي ... كنت تلاقيه متفاخر أوي بموضوع إنه أخذ ست شهور جنحة في اللي كح في وشه .... و لا إعترض يوم على طريقه نظره لمرات أخينا، بس الموضوع ده إنخفض شوية بعد مابقا إن السجن مش للجدعان إنما السجن للمصريين جميعاً (و ده توحيد إجتماعي يشكر عليه اسيادنا في الداخلية)

المهم ظهرت بارقة جديدة من الأمل لإحياء هذا التراث المصري بس لنوعية جديدة من المصريين، بقت فيه جريمة جديدة إسمها إهانة رئيس الجمهورية و هي المرادف اللغوي للعيب في الذات الملكية (في الزمن جمهوري الإسم ديكتاتوري المعني ده) و أعتقد إن عقوبتها سنة.

أنا كنت بتابع أخر أخبار قضية إبراهيم عيسي و هوا بيحاول يخرج من التهمة العجب إللي هما ملزقنهاله (و إللي هيا أصلاً كانت أمل .. مش خبر ... يعني بزمتك مش كل واحد كان نفسه الإشاعة إللي هما بيتكلموا عنها تبقي حقيقة؟ و نخلص بقا)

المهم ..... بعد إبراهيم عيسي ماهاينطس السنة المتينة بعد كل المحاميين و الجلسات هاتلاقية في كل الجرايد و المقالات بتاعته بيتفاخر بأنه أول  من أخذ في الريس سنة.... و بأن الوطنية لا تكتمل إلا لما تأخذ في الريس سنة!!!!

والله يعني أنا بشكر سيادة الرئيس و السادة القائمين علي القوانين و الأحكام إللي قدروا يرجعوا للتراث المصري عادة مصرية أصيلة.

The Eclipse RCP - 3 - Launching configuration

A Launch configuration in Eclipse defines the environment under which your application will be started, e.g. compiler flag, plug-in (classpath) dependencies etc.

Select your plugin.xml -> Run As -> Run Configurations

On the tab Arguments you should add the parameter -consoleLog. This will send error message of your Eclipse RCP application to your Eclipse development IDE.

On the Arguments tab, you will find also the -os -ws -arch -nl arguments associated with ${target} variables, they can be edited form Window -> Preferences -> Plug-in Development -> Target Platform

On the Plug-ins Tab select "Validate plug-ins prior to launching". This will check if you have all required plug-ins in your launch configuration.

The Eclipse RCP - 2 - Create your first RCP application

1. Download the package "Eclipse for RCP/Plug-in Developers" from the webpage of eclipse (www.eclipse.org).
   
2. Extract, and Run.
   
3. In Eclipse select File -> New Project.
   
4. From the list select Plug-In Project.
   
5. Give your RCP plug-in a name, "MyFirstRCP", click Next
   
6. Select "Yes" at the question "Would you like to create a rich client application", click Next
   
7. Select "RCP application with a view", as a template, click Next
   
8. Type the name of the Title Bar in the "Application window title" field, and Select "Add branding", click Finish
   

To Launch the application, double-click on the file "MANIFEST.MF". You should see an editor and the tab "Overview" should be selected. Click the link "Launch an Eclipse Application".

The Eclipse RCP - 1 - Rich Client Platform

For the full tutorial, see http://www.vogella.de/articles/RichClientPlatform/article.html

The Platform
The Eclipse RCP is a platform, where no functionality is implemented in it; its sole purpose is to manage the plug-ins, where everything in the program is done using the plug-ins.
The plug-ins implement everything, from the menu bar, to the status bar, to the main toolbar, to the views (or panels), to the Editors (which may not be editing anything, but they are the main focus of the program), to auxiliary functionality like software automatic update and help and the management of long-running background operations; these plug-ins are the heart-and-soul of any Eclipse RCP-based program.
The basis for this architecture is the runtime environment of Eclipse which is based on the OSGi Alliance. Eclipse used the OSGi reference implementation Equinox to run upon. The Plug-in concept of Eclipse is the same as the bundle concept of OSGi.

Minimum Requirements
As a minimum, a RCP application requires:

• Main program or Application (org.eclipse.core.runtime.applications extension point)
  
• Workbench Advisor (invoked from the Application handler, it sets the default Perspective, invokes WorkbenchWindowAdvisor which configures the default Main window state and subsequently invokes ActionBarAdvisor, which in turn provides one of the ways to configure the Action Bar or the main menu and Cool Bar or the main toolbar)
  
• A Perspective (org.eclipse.ui.perspectives extension point)
  
• A View (org.eclipse.ui.views extension point, views are technically not required for a RCP application, but they are the base interface element)
  

The RCP application depends on 2 main plug-ins:

• org.eclipse.core.runtime
  
• org.eclipse.ui
  

Plug-ins Architecture
The RCP architecture is based on the concept of extension-points, which a plug-in provides so that any other plug-ins can contribute functionality to it in the form of extensions, e.g. you can easily provide your menu items in the Action Bar (an extension point provided by the org.eclipse.ui plug-in) by implementing extensions that connect to the org.eclipse.ui.menus extension point and provide their own implementation. In general an extension point can be used several times (either by the same plug-in or by other plug-ins).
The plug-in architecture is based on 2 configuration files (or manifests) that describe the behavior of the plug-in, "MANIFEST.MF" and "plugin.xml", by double clicking on any of them, Eclipse provides a graphical editor of the files contents.
The plug-in manifest ties all the code and the resources together, the OSGi bundle manifest is stored in "MANIFEST.MF", while the Eclipse specific parts are stored in "plugin.xml".

سبتمبر جاانا

الصراحة رمضان السنه دي جامد جداً ..... جه أول سبتمبر .... و الصراحة سعيد صالح باين عليه كان عارف من الأول فجهز الأغنية التمام لرمضان السنادي

The Eclipse RCP Platform

I've started in my quest to learn the Eclipse RCP Platform, the Java Rich Client Platform built on the Eclipse foundation softwareand using the Standard Widget Toolkit (SWT).

While I think that Swing and the Swing Application Framework (JSR 296) would be a more pure Java approach, I personally prefer the Eclipse RCP approach for large scaled projects, where it can provide high degree of modularity to the system (this can be also achieved in the NetBeans Platform, but I prefer the look and feel of the Eclipse-based applications).

Also I think that the NetBeans IDE is better in the more broad Java picture, where I assume it is better in handling the Java EE and Java ME applications and provide a higher of community participation in its code base (this may not be correct, but I got this impression, maybe because I was a close watcher for the NetBeans news earlier than Eclipse).

But the Eclipse RCP won because of its large base of implemented applications, one for example was the main reason that I tried the Eclipse RCP in the first place, uDig, the internet-friendly desktop GIS application, and i don't know until now if I'm gonna to run inside it with my plug-ins, or that I will embed its plugins inside my application(s).

Also the Eclipse SWT library is more responsive and native-looking than Swing (personally I love the Java Metal look and feel, but thats just me, everybody else hates it).

So, in the next few days, I will start posting about my findings in the Eclipse RCP world and the Java world in general.

اللهم تقبل منا رمضان