Web-based Applications
Many of our applications are web based and as such, available online world wide.
Suppliers log in to the SupplyCockpit to see the latest developments. Via the web, customers are constantly kept up to date of their order’s latest progress.
This web interface is only one of many possibilities to present data. The flexible and light method of programming, allows for the data from our applications to be integrated without trouble into mobile devices such as PDA’s, smart phones, …
All this offers your company unique possibilities to manage your company from a distance, to maintain customer and supplier contracts, …
Eclipse
The development of the end user applications is done in Eclipse. Eclipse is the basis for the skeleton of the application, that can be fine-tuned to meet the customers needs. The use of Eclipse drastically shortens the Software Development Lifecycle. It allows us to develop efficiently and effectively in standards and tailored to our customer’s needs.
Eclipse is a powerful open-source framework for software development in Java. We use it to develop “rich client” applications. Contrary to the browser based “thin clients”, these are exceptionally suitable for intense GUI with heavy demands on data processing. One attribute of these applications is that they work easily with databases they consult via a network.
Important advantages of “rich client” applications are the expansive possibilities for the user interface. The response speed is much higher and yet the development costs are lower than that of “thin client” applications. This is caused by the reusable components and design patterns, that write easy to maintain, flexible code. All these attributes make Eclipse an interesting alternative for the heavy JavaScript-laden “thin clients”.
Spring
Spring is Swinging!
Spring is the latest in Java technology. It is a framework that offers many advantages. PearlChain.net uses Spring to implement the easiest solution to your problem. In traditional code, the component contacts the container. Spring takes the responsibility away from the application and places it with the framework instead. This method ensures that the component gets the right objects in real time. The system is faster, lighter and easier to write and implement. The configuration is consistent throughout all applications and projects. What is more, the business objects are independent of Spring. It is architectural glue.