The main idea is to provide an all-in-one tool with maximum possible automation of routine development tasks. The powerful designer tools are available for every step of application creating, running, debugging, and the deployment process.
The database diagram tool enables creating and management of database structure in a visual way. You can create tables, columns, indexes, foreign keys and more. The following popular databases is completely supported: Oracle DB, SQL Server, MySQL, PostgreSQL, DB2 and H2. Database migrations allowing to store database schema snapshots and transfer schema configuration to any other supported database.
The application data access level in Platypus is built of SQL queries. The Application Designer supports visual creating and editing of complex queries. Named parameters is SQL and reuse of queries in other queries is also a very interesting features of Platypus Platform.
At the module level the data model is the definition of persistent data is also to be defined by drag-n-drop and configuration. The data model has an interesting ability: after the data have been loaded to it and you change them (insert new data or change something) the changes can be automatically saved to the database.
childrenEntity.parentEntity for entities backed by database tables connected by a foreign key link).
And here is why we've chosen NetBeans IDE and the NetBeans Platform over Eclipse for our project:
- We had our original application made in Swing and we didn't want to rewrite everything to SWT.
- In our opinion, NetBeans provides a more friendly and logical user experience. Some Eclipse concepts like "perspective" or "workspace" still seem not to be very intuitive for us.
- NetBeans works much faster, it starts faster too.
- We like NetBeans Platform's APIs.
Now we think that choosing NetBeans is a good solution and NetBeans is definitely worth being considered as the leading platform for creating complex cross-platform development tools.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)