|
|
Introduction
Why use a framework?
Download
Vision
API stability
Code optimization
Bibliography
Features
Object messaging
Extensibility
Drag-and-Drop
Networking
3D Graphics
Powerful tables
Styled text editor
Memory leak debugger
Tutorial
Class tree
Open protocols
Known bugs
Next release
Future plans
Projects
FAQ
Other software
Log in
|
|
|
|
Projects for the Bazaar
If there is a Contact for a particular project, then that person is working on it, though possibly quite slowly, so don't hesitate to offer to help out if you're interested. If there is no Contact, then nobody is working on the project, so you can claim it by simply contacting us.
API documentation
It would be nice to have complete documentation on the web!
Automated configuration
It would be nice if the source distribution could use an automated configuration system (e.g. GNU's autoconf) instead of a large set of handwritten configuration files.
Porting to other platforms
Porting to another UNIX variant is not usually very difficult, but it does require somebody who has an account on that type of system.
Porting to Windows® is also under way, by implementing the Xlib interface on top of the Windows C API. It should also be possible to support multiple displays since libX11 doesn't require anything beyond a network connection to the server. (The Display object will merely need to be extended to know whether it is local or remote.)
Internationalization (i18n)
Supporting Asian and other multi-byte languages would allow JX to spread beyond America and Europe.
Bindings for other languages
It would be nice if one could use JX from other languages like Python, Perl, C, etc. SWIG looks like a really good way to do this!
It would be nice if JX applications could blend in with any theme set by either Gnome or KDE. It would be nice to develop a single protocol that everybody can agree on, so Gnome, KDE, and JX applications could all blend in on the same desktop, but this is probably hopeless.
J3D is still embryonic. It needs a lot more basic shapes, text, texture mapping, lighting, animation, hit detection, etc.
Raytracing
J3D could support raytracing by having classes write an input file for povray. The output could be displayed via JXImage.
HTML
Currently, JTextEditor can read HTML, but it doesn't display graphics, handle Java code, etc. It would be nice to have a separate widget strictly for displaying HTML. The best way may be to put a wrapper on top of the Mozilla rendering engine or borrow code from the XmHTML Widget Set.
Sound
There is no support for sound, yet. One possibility is to build on top of the Open Sound System. The best choice, however, appears to be rplay. (Thanks to Brian Jones for this suggestion.) There is also the aRts system used by KDE.
Text Editor features
Reading and writing text/enriched (RFC 1896), RTF, and TeX.
It would be nice to support this. Netscape simply gives you an X window to play with.
|
|