CCU FAQ
Use XDoclet.
Register on freshmeat.net.
They will be, but this feature is not yet available. If difficulties occur in transferring project files from one computer to another, be certain that identical versions of the CCU are in use; the application build time can be found at the end of the 'readme.txt' file.
JShift consultants are available to add language support. If the desired language is non-proprietary, we may add it to the product in the future. If you're in a hurry or the language is obscure/proprietary, you can implement support on your own or pay us to do it. Contact us for details on obtaining product API's or consulting services.
The CCU mimics all existing constructors in a superclass. This occurs so that, when you extend a CCU-defined class, you don't lose access to the superclass' constructors. This is also necessary so that the new class doesn't throw a compilation error if the superclass lacks an empty constructor. In order for this feature to work, the superclass must be in your classpath. If you wish to extend an entity defined in the same project, you must shut down the CCU and compile the 'superentity' before defining the 'subentity'.
Some regular expressions are impossible to convert to the less expressive, ANSI LIKE clause. Others can be converted but would require unduly complex logic. Still others can be partially converted at the user's discretion. ^JS.*ft$ converts cleanly to JS%ft$ for example. ^JS*.*na$ isn't as easy, though. We could again convert to JS%ft or we could return null depending upon whether the user prefers a partial translation (all strings that pass the regEx test will pass the like test but the inverse is not necessarily true) or an "all or nothing" deal. This preference can be updated under the SQL Project Properties Window.
Preferences are set in property bags. Here you can update the 'Indentation String' property. Use a series of spaces instead of '\t'.
In a properties bag (see above), update the 'Line Separator' property from '\r\n' to '\n'.
Yup.
This app is for programmers. Don't you have better things to worry about? If not, check out some alternate look and feels. Put the PLAF jar(s) in your classpath (or in the 'lib' directory if you ran the standard Windows install). If you want to try a LAF that's not automatically supported, try editing the registry or equivalent backing store. On Windows, you'll find a LAF classname (something like 'com.whatever.whatever.WhateverLookAndFeel') somewhere in My Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\com\jshift\ccu. If the selected LAF doesn't support essential widgets, the CCU may crash. In this case, just reset or delete the non-functional setting and restart. A good hint that the LAF won't work is if it was designed for JRE 1.1.x. Oh, another way to enable a LAF is to put a file named "swing.properties" in $JDK_HOME/jre/lib with the following contents:
swing.defaultlaf=[LAF classname]