...
Project name | Description |
---|---|
com.servoy.eclipse.appserver | Eclipse plugin to start the application server in developer |
com.servoy.eclipse.core | Core eclipse classes that make up developer |
com.servoy.eclipse.debug | Classes that revolve arround debugging, connectors to DLTK |
com.servoy.eclipse.designer | All Form designer code |
com.servoy.eclipse.feature | Holds the definition to makeup the eclipse Servoy Developer |
com.servoy.eclipse.jsunit | JSunit <-> Junit bridge and command line JS unit test/suite runner |
com.servoy.eclipse.profiler | The profiler (view) which is present in Servoy developer |
com.servoy.eclipse.team | The servoy team provider, used against the server/repository interfaces |
com.servoy.eclipse.ui | GUI helper classes, some default dialogs, abstract GUI elements |
com.servoy.extensions | All Contains the default shipped plugins and beans, shipped in installer |
servoy_debug | client side debug classes and connectors |
servoy_headless_client | The headless and webclient code |
servoy_smart_client | The Smart client (webstart) |
servoy_shared | The shared code / libs between web and smart client |
Some entry point hints when looking at the code:
*ClientState.Java is in fact the most top level class containing logic, from which all other "client" applications are made. derived (tip view class hierarchy in eclipse) **As you might have seen servoy is all about data handling, another very important class is IFoundset.java (tip view class hierarchy in eclipse)
**
...
...
...
...
We have a MVC for Servoy forms
J2DBClient.java is the webstart client, generates interfaces via ComponentFactory and ItemFactory
WebClient.java is the apache-wicket browser client, generates interfaces via ComponentFactory/ItemFactory and TemplateGenerator (produces templates in html)