Child pages
  • Servoy Design Principles

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Servoy defines a lot of behavior out of the box, but also provides the developers with the means to override the default behavior to fit their needs.

Client, Database, platform and device agnostic development

When developing a solution with Servoy, it will out of the box run in all Servoy Clients (Smart Client, Web Client, Headless Client and Batch processor), can be deployed on any platform, connected to any database and in any deployment model one chooses. 

...

While developing Solutions with Servoy, debug clients can be started from the Servoy Developer IDE to instantly run and test the code or start a debug session. More importantly, any changes made to the design of the Solution are instantly broadcasted to the connected debug clients. so, without having to restart the debug client or having to go through a compilation cycle, the changes can be seen/tested straight away

Modular & Object oriented development

Solutions can be built, maintained and versioned in modular fashion. A Solution can be used as a module in another solution, building a entire tree of modules, that together make up the end solution.

Besides modular development, Servoy also supports inheritance within the Solution. 

And finally a UI, called a Form in Servoy, is an object that can be reused in different locations and nested into other Forms using so-called container elements like TabPanels and SplitPanes 

Backwards compatibility

New Servoy version are always backwards compatible: take a Solution developed with Servoy 2.2 and import it on Servoy 6.0 and it will just work!

...