natclipse allows integration with most versioning systems available today. By taking the source code from the mainframe and allowing Eclipse full control of it, developers can use all the tools available to the desktop. CVS, Subversion, Team Foundation Server or ClearCase are among the many code management systems that can be accessed from natclipse professional.
Unify how you manage code across technologies
If you already have web development teams, employ the same methodology they are using in Natural. Concurrent code editing, team code reviews, software releases, unlimited code history, code comparisons across versions, branching, merging, tagging, and so on. The list of modern software engineering principles available in this new world is virtually unlimited.
If you think your Natural application is one big monolithic block of code, think again. You can actually look into the application with bulk analysis tools and find metrics for most of your questions.
- Is the code ready for modernization?
- What is the quality of my code? Am I making it worse?
- What do I have to do to migrate from a mainframe to Open Systems?
natclipse contains natanalyzer that lets you look into the Natural code and find out what you have to do. Analysis results show up in a graphical view as well as an Excel-like detail view and you can export them into a CSV file.
Visual Data Browsing. No hassle.
Natural developers often face data heavy applications. Obviously they need to inspect the data their programs run on to make informed decisions about how their code performs. Natural/Adabas does not have a data browsing facility known from other databases like Oracle or MSSQL Server. They revert to writing small programs to read and print out data.
In a modern development environment like natclipse it would simply be antiquated to have to write such queries manually over and over again. adaclipse, part of natclipse, creates queries on data, remembers the queries, generates the Natural code required to run them and visualizes the results in an Eclipse view.
Developers can focus on their tasks again instead of having to write throw away code over and over again.
|Integration with team systems
natclipse's tight integration with practically any versioning/SCM system out there allows integration of Natural code and developers into ongoing other development efforts, like web projects in .NET, enterprise application in Java, and even C/C++ programming.
natclipse embraces this and extends the concepts by automatically considering and resolving all dependencies created by a change. This means in particular that synchronization processes (that often introduce code from other team members into the workspace) are possible and handled by natclipse.
The first screenshot shows an error introduced in a copy code that was detected by an automatic compile of the main program that includes it. The error is marked in both objects.
The cross reference is maintained by natclipse without requiring any manual intervention.
The second screenshot shows how an easy view into the history of an object is possible, and how files from the past can be accessed and compared.
|Synchronization and Teamwork
Many versioning systems allow concurrent teamwork. When two developers are editing objects at the same timne, changing different parts of the code, the synchronization perspective allows finding conflicts (which objects are affected) all the way down to the conflicting line of code. Merges are supported through quick toolbar buttons, that allow copying the current or all changes down.
The first screenshot shows how a view of a database table is created using an existing DDM. In the second screenshot, the query on the view is defined. The last screenshot gives you the result of the query.
No more hassle developing these small queries over and over again, the adaclipse plug-in of natclipse makes it simple to compare your development, test, or production data.