|
MoreMotion Application Studio supports team work. Big projects can be divided into sub projects that can be developed and tested independently. During deployment, the sub-projects are combined under the main project.
The biggest problem of the big sized projects is the preparing of hundreds of forms and lists. The other development tools may claim that the simple forms can be developed easily. But when it comes to developing intensive and function rich pages, the truth comes out and it may take days to complete even one single page.
MoreMotion Application Studio is way ahead of its nearest competitor as far as the rapid user interface design is concerned. Without getting lost in the complex HTML codes, even sophisticated pages can be constructed.
In addition to the visual elements, the Application Studio can handle all the functional component elements on a page easily in a comprehensive manner and it automatically configures them during the project build.
When using the other Java IDEs, sometimes it can be annoying to wait minutes long for the build and deployment following a small change in the project. Whereas the MoreMotion Application Studio can track that changes in the projects and can build the big projects (e.g. 200 - 1000 pages) in seconds.
One of the musts to handle for the big projects is to benefit from the reusability on a high level. The MoreMotion library which can be easily extended with the new components provides an ideal ground for that purpose.
When a library component is deployed into a page, only thing to do, by design, is to configure it. It is not necessary to write lines of code as it is the case in the other IDEs.
Complicated GUI elements can be designed and added to the library easily to let the other team members use it with simple drag & drops.
Experienced developers know that, large and business-logic rich applications can be better developed by applying a Model-View-Controller design pattern.
Usually one has to use an additional framework to benefit from this pattern if another IDE is being used. One example to it is the "Struts" framework.
MoreMotion has an integrated and advanced MVC implementation and with the visual tools provided by the Application Studio the business flows can be easily steered.
This integrated MVC implementation is so successful that whereas the main aspect of the other IDE is "coding", an MoreMotion developer hardly need Java coding. This feature, that is not believed to be true unless one sees it with his own eyes, has been used in MoreMotion successfully for years.
Probably the biggest advantage of the MoreMotion AF to the other well known Java web frameworks is that MoreMotion AF relies on XSLT to render the dynamic web pages instead of JSP or JSF.
A JSF component is responsible to generate the HTML code by itself for the area occupied it on the page. Therefore making the customization on the component user interface is limited to the components capability. Whereas a MoreMotion component is only responsible to provide data objects that can be transformed into XML. The forming the component's user interface on the page is done by the XSL that refers to the XML data provided by the component.
Since the user interfaces of the components are so loosely coupled with the data provided by the component, highly customizable general purpose components can be developed and the user interfaces of these components can be customized easily using the true WYSIWYG editor of the MoreMotion Application Studio.
The superiority of the XSL here is nonnegotiable. The data provided as XML contains no formatting information and it can be rendered in thousands of different sorts; the XML data can be sorted, queried and populated with the provided world-standard XSL functions.
For the programmers who are used to do everything with coding, the most important thing for a development tool is having the possibility to make low level coding in case of necessity. The common statement for that is usually “Yes, maybe I’m not as fast as your tool but I am capable of doing everything on a low level. I don’t like that a tool generates the code on behalf of me no matter how smart it is.”
As a matter of fact, we don’t like it too and therefore we did not design the MoreMotion like that. With the exception of transforming the visual page design into the XSL, MoreMotion Application Studio never generates code. It only utilizes the Java classes that were prepared for general use efficiently.
The total freedom is given to the developers in the HTML coding. When necessary a part of a page or the whole page can be prepared manually.
It is much more sensible to hand code only when it is really necessary and to enjoy the comfort of the Application Studio for the rest, instead of developing a 500 page project all the time with manual coding.
Besides, you can develop your own Java classes using the MoreMotion API and add it to the MoreMotion library as easy-to-use pieces. There is no restriction at all in the type of the Java classes. E.g. you can make hibernate or EJB calls from within your Java classes and evaluate the results.
Ajax development is no exception for the "Coding as less as possible" philosophy of MoreMotion Application Studio.
Different types of Ajax techniques can be employed in the pages easily again without coding. The pages enriched with MoreMotion Ajax functions are just like the forms of the Desktop applications in terms of the user / system interaction.
More over the refreshing the elements or the refreshing the parts of the pages can be executed as Processes. This way the refreshing processes like “Refresh the options of the combo with Ajax” or “Refresh the records of the shopping cart with Ajax” can be configured in the process lists after the other types of processes such as “Update Database”, “Inform customer with E-mail” or “Reserve Products”.
|
