There is a huge number of various GUI libraries and GUI components
for different environments, platforms and languages on the market
at present. Such a situation can drive you mad if you try to find
the best solution. What should be selected: the .NET or Java platform,
Windows or UNIX? Which one provides the most flexible solution?
Where is the richest UI component set? What about performance and
system resources usage? And so forth ...
If you have these or the like problems in your project, then LwVCL
is the very solution to these technological challenges.
Forget about the Microsoft vs. Sun war. LwVCL provides the
same solution for both - Java and .NET! It means the same API, the
same components set, the same functionality, and at last the same
look and feel. Take a look at the images below to compare screen
shots of .NET and Java LwVCL applications:
The unique technologies, which I use in
our product, allow me to transparently support both the Java and
.NET platforms. As a result, any new J2SE LwVCL component appears
in the .NET version immediately.
 |
LwVCL can be easy adopted for other platforms and languages.
The .NET and Java LwVCL versions are just particular cases.
Do you need to have rich, flexible GUI in Pyton or anything
else? I can develop LwVCL for it, and you will have the same
GUI library as the .NET and Java versions. The unified API
and abstract components level give you a chance to start working
quickly, independently from what platform LwVCL is going to
be used on. |
The bursting PDA market needs to have a good GUI components
set. This is LwVCL that can provide one of the richest components
set on the marketplace! It works fine for both J2SE and J2ME
Personal Profile (Personal Java as before) without any differences!
Moreover I have J2ME MIDP LwVCL (draft) for devices with
limited resources, such as cellular phones, Palm OS oriented
PDAs, and so on. The J2ME MIDP LwVCL version completes the
magic circle shown at the left.
|
This
library provides a rich set set of various GUI components.
I also offer simple components like label, button, panels,
etc., as well as complex components like grid, tree, tree
grid, and so on. The LwVCL components are based on the MVC
(Model-View-Controller) concept, support view customization,
so you can use multiple skins to design an LwVCL application
according to your preferences and needs. Go to screen
shots, online demo
pages to show you what the LwVCL components set looks like.
|

 |
As a result, you
get a powerful GUI solution for most IT sectors, that unites
different platforms and environments, simplifies support and
development processes, solves problems with GUI cross-platform
interoperability. LwVCL is not just a components set - it's
a solid GUI toolkit that adds transparent support for J2SE,
J2ME, SWT and .NET platforms to your application.
Preserve your freedom to choose the library! |
 |
In the end, I would like to list the basic characteristics of
the library to convince you that I have a really powerful solution:
-
Layered architecture.
This library has a layered architecture where UI components
set has minimal dependencies on a concrete platform. The LwVCL
components are abstract as much as it is possible to be easily
adapted to any other platforms and languages. See
the library basic ideas page.
-
Small size.
The library packages are very small. The core Java package is
about 160 Kb (the .NET DLL is about 200 Kb). PDA likes eating
it!
-
Provides about 30 various GUI components.
In spite of the small size of the library, LwVCL provides a
huge number of UI components! In addition to simple components,
you will get a grid, tree, tree grid, and other complex, flexible
components. The components set grows up very fast!
-
Dynamic and thrifty to system resources
usage (CPU/Memory/Disk Space).
The library is very fast and takes care of use of system resources.
-
MVC (Model-View-Controller) compliance.
The library components are designed according to the MVC concept
that allows separating data models, views, and business logic.
-
Flexible and customizable.
The library is customizable. It is very easy to extend the library
with new components, or change its behavior according to your
requirements.
Currently I develop and support the following LwVCL versions:
| J2SE LwVCL |
Use it for desktop systems - Windows,
UNIX, Mac OS, everywhere you can have java installed.
This is the base implementation of the library that is
the "master" branch for all others. All new
features come here first and after that are applied to
other versions. |
| J2ME Personal Profile (Personal
Java) LwVCL |
Use it for PDAs like Zaurus, iPAQ
to have the same capabilities as you have on the desktop
systems. The version doesn't differ from J2SE LwVCL! If
you have a J2SE LwVCL application, it means you have it
for J2ME Personal Profile LwVCL too. |
| .NET LwVCL |
Get the same for the .NET platform
and never mind MS and SUN fighting! The version has the
same J2SE LwVCL capabilities. |
| SWT LwVCL |
Get the same for the Standard Widget
Tookit. Using the version you can compile your application
into native code. |
| J2ME MIDP LwVCL |
Use it for the resources limited
devices. This version is under development now. I provide
a draft version. |
|
|