Most recent edit on 2007-07-02 09:27:49 by LuanO

Additions:
∞

Deletions:
{{image link="http://www.sourceforge.net/projects/xui∞" url="http://sourceforge.net/sflogo.php?group_id=76693∞

---

Edited on 2007-06-29 21:01:49 by KpkAgk

Additions:
{{image link="http://www.sourceforge.net/projects/xui∞" url="http://sourceforge.net/sflogo.php?group_id=76693∞

Deletions:
∞

---

Edited on 2007-04-23 02:06:57 by LuanO

Additions:
∞

Deletions:
∞

---

Edited on 2007-04-23 02:06:08 by LuanO

Additions:
Windows Vista
On Windows Vista hightened security requirements mean that some changes to the regsitry permissions are required to build XUI. Run REGEDIT and find the "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment" key. Right click the key and choose Permissions...
Change the permissions for the key to give yourself full control (or a setting that gives you write access).
∞

Deletions:
{{image link="http://www.sourceforge.net/projects/xui∞" url="http://sourceforge.net/sflogo.php?group_id=76693∞

---

Edited on 2007-04-19 22:17:29 by HdyJws

Additions:
{{image link="http://www.sourceforge.net/projects/xui∞" url="http://sourceforge.net/sflogo.php?group_id=76693∞

Deletions:
∞

---

Edited on 2006-12-01 09:52:24 by LuanO

Additions:
for the compile target on line 86. See SVN∞ for a version of these files.

Deletions:
for the compile target on line 86

---

Edited on 2006-09-20 04:26:04 by LuanO

Additions:
Problems with harness.dir
If you get errors mentioning the harness.dir file, make sure that you have opened the svn/xuisuite/trunk project in NetBeans. The suite ties together the various NetBeans modules and is referenced in the build of those modules. The error occurs if you have opened the individual modules without opening the suite.
Problems finding the Eclipse classes
If you are building the NetBeans modules then you may encounter problems compiling if you do do place a modified version of the common.xml file in your program files/netbeans/harness folder. The modification to this file is the following:

1.         <javac srcdir="${src.dir}" excludes="${module.excludes}" destdir="${build.classes.dir}" debug="${build.compiler.debug}" debuglevel="${build.compiler.debuglevel}" deprecation=

instead of (i.e. the excludes="${module.excludes}" attribute was added )

1.         <javac srcdir="${src.dir}" destdir="${build.classes.dir}" debug="${build.compiler.debug}" debuglevel="${build.compiler.debuglevel}" deprecation=

for the compile target on line 86

---

Edited on 2006-08-14 10:35:34 by LuanO

Additions:
∞

---

Edited on 2006-07-28 12:03:12 by LuanO

Additions:
Problems?
If you are having problems compiling, please check that you are using the correct version of the XUI jars for the Java JDK that you use.
If you manage to compile and there are classes missing you will get a ClassNotFound exception. Again check that the correct Jars are included, you can review the contents of the Jars by opening them with a tools such as WinZip.

---

Oldest known version of this page was edited on 2006-07-28 11:59:41 by LuanO []

Compilation

A XUI application can be compiled either from the command-line or from within and IDE such as NetBeans or Eclipse. The main requirement for compiling a XUI application is that you have the necessary Jars in the classpath.

The choice of Jars depends upon the version of the Java compiler and JDK that you are using. XUI ships with versions of the Jars for various JDKs including 1.1.8, 1.3 and 1.5. The oldest JDK support is included so that XUI applications can run on JVMs for handheld devices such as PDA which only support JDK 1.1 features. JDK 1.3 support is provided for those who cannot use JDK 1.5 support including generics.

The XUI libraries are also compiled in two version, a debug version with lots of logging and diagnostics and a release version with the logging and diagnostics removed. XUI itself is split into a number of Jars. XuiCore.jar contains the basic classes needed by the framework and the AWT widgets, XuiCoreSwing contains the same core classes and the Swing widgets. XuiOptional contains everything else, including advanced components and utilities, including the database access components. In most cases a XUI application will use a version of the XuiCore jar and the XuiOptional jar. You application may not use all the classes in these Jars and you are free to bundle just those classes you need with your application instead of the full Jars, however be sure to read and comply with the license before doing so.

Compiling in NetBeans

1. To setup the build in NetBeans you must ensure that the Jars are included in the project. The KalIDEoscope wizard automatically includes a copy of these Jars in the project's lib folder and then references these jars in project's build file. To check that the libraries are included:
2. Right click on the project folder and choose properties
3. Under the libraries section check that a version of the XuiCore and XuiOptional jars are listed on the Compile tab.
4. Under the Run tab, check that the project's pages, lang, and resources folders are included.
5. Click on the Run or Debug toolbar buttons, just press F5 to compile and run the application.

Command-line compilation