Archive for category system development
Alhamdulillah~eventhough in my critical phases…
Posted by growingyourthought in system development on April 24, 2011
:: Bismillahirahmanirrahim ::
Alhamdulillah.. only one more thing o be done for my java application- the stegoText validation..after this i will deploy it as an executable program.. here is the interface of my system..just a temporary.. i will create a new look for the sharp-edges branding cover
insyaallah … syukur ya Allah … 90% of my system..last part = deploy
p/s: my dear me, ermm.. we should prepare for VIVA right? a week to go ..! huhu!
must try this RCP first
Posted by growingyourthought in system development on April 15, 2011
:: Bismillahirahmanirrahim ::
learn from the exercise … no need to build it from scratch …
RCP overview
Posted by growingyourthought in system development on April 15, 2011
:: BIsmillahirahmanirrahim ::
A plugin is a small unit of Eclipse Platform that can be developed separately. It must be noted that all of the functionality of eclipse is located in different plugins (except for the kernel).A plug-in can be delivered as a jar file. A plug-in is self-contained bundle in a sense that it contains the code and resources that it needs to run for ex: code, image files, resource bundles etc. A plug-in is self describing – when I say it is self describing it means that it describes who it is and what it contributes to the world. It also declares what it requires from the world.
wow! RCP besh!
Posted by growingyourthought in system development on April 15, 2011
:: Bismillahirahmanirrahim ::
RCP sooo~ good~
love to do those tutorial step by step yoish!
let print out this RCP Tutorial! hmm,.. need to execute it first then i will configure it to suite with my stego-system! long way to go…
error in RCP
Posted by growingyourthought in system development on April 15, 2011
:: Bismillahirahmanirrahim ::
error in running the RCP tutorial due to the different JVM SWT library version
Eclipse RCP Tutorials …
Posted by growingyourthought in system development on April 4, 2011
:: BIsmillahirahmanirrahim ::
Eclipse RCP Overview..
Eclipse RCP allows developers to use the Eclipse platform to create flexible and extensible desktop applications. Eclipse is build upon a plugin architecture . Plugins are the smallest deployable and installable software components of Eclipse. A plugin is a collection of files and a configuration file (MANIFEST.MF) which describes the plugin and its dependencies. The following picture show the content of an example plugin.
This plugin architecture allows the Eclipse applications to get extended by third parties. Eclipse RCP provides the same modular concept for stand-alone applications.
This tutorial will introduce you to the exciting world of development of Eclipse RCP applications.


Eclipse Form
Posted by growingyourthought in system development on April 4, 2011
:: BIsmillahirahmnairrahim ::
1.1. Overview
Eclipse supports a web-like user interface style, called Eclipse Forms. Eclipse Forms is a plugin based on SWT and JFace that provides the support for creating portable web-style user interfaces across all Eclipse UI categories. The Eclipse forms functionality is contained in the plugin “org.eclipse.ui.forms”.
The class FormToolkit serves as a factory for the creation of the required user interface elements. This factory adjust the look and and feel of the standard SWT and JFace elements to the Forms API. Existing UI elements can be enhanced to the form API via the method adapt(Composite).
FormToolkit provides Form or ScrollForm which are serves as the frame for the user interface elements. They provide a header, a toolbar and a body. The body can get accessed via getBody() and contains other ui elements.
How to Make Dialogs
Posted by growingyourthought in system development on April 4, 2011
:: Bismillahirahmanirahim ::
A Dialog window is an independent subwindow meant to carry temporary notice apart from the main Swing Application Window. Most Dialogs present an error message or warning to a user, but Dialogs can present images, directory trees, or just about anything compatible with the main Swing Application that manages them.
For convenience, several Swing component classes can directly instantiate and display dialogs. To create simple, standard dialogs, you use the JOptionPane class. The ProgressMonitor class can put up a dialog that shows the progress of an operation. Two other classes, JColorChooser and JFileChooser, also supply standard dialogs. To bring up a print dialog, you can use the Printing API. To create a custom dialog, use the JDialog class directly.
The code for simple dialogs can be minimal. For example, here is an informational dialog:
How to Create a Windows Installer for an SWT Application
Posted by growingyourthought in system development on April 2, 2011
:: BIsmillahirahmanirrahim::
Native Windows installers offer unparalleled integration with the operating system, as well as familiar installation for users. Learn how to build a native Windows installer for an SWT application using open source tools.
SD : Java stand alone system dev
Posted by growingyourthought in system development on April 2, 2011
Java programming language was primarily developed to deal with embedded applications. But with the introduction of Swing and other user interface utilities to Java, it made its mark in desktop applications too. Now the trend is to use Java technology in developing large web and enterprise applications. Java is more focused on web then desktop applications.
But, in this article, we are going to discuss how useful Java is as a development technology for stand alone desktop application development in present scenario.


Recent Comments