Relevant information about the eRedG4 please visit the news posted, I will not go into details here.
Here the value of a word, easy to subsequent discussions. ERedG4 related key technology selection: ExtJS3.X + Struts1.X + Spring2.X + iBatis2.X.
(Comment: The next version may be streamlined: Ext3.X + Spring2.X + iBatis2.X)
eRedG4 GoogleCode project home page: http://code.google.com/p/g4-xiongchun
eRedG4 online demo system: http://web230531.host89.chinajsp.net
The topics discussed here today:
Currently, G4 next focus is how to solve the premise of guaranteeing the performance:
(1). Reduce the cost of the project team learning and training.
(2). Reduce project development costs and improve the maintainability of the project later.
Ultimate realization of the rapid development of secondary industry application target.
I now have 2 sets of programs:
Option One. Will EXTJS labeling, the use of dynamically generated template engine G4 ExtJS characters flow through the JSPTag output response. Generated using the Eclipse-Plugin technology the SQL single-table CRUD iBatis mapping file and data persistence object or a substantive area of the object.
a). labeling package is simple, even hundreds of times. Very short development cycle will complete a full set of UI components EXtJS labeling.
b). JspTag lower capacity requirements for developers, simple post-training team members can get started developing reduce the learning and training costs, improve development efficiency.
c). JspTag later called the ExtJS code in terms of maintenance is relatively easy.
Defects and deficiencies:
a). JspTag run-time code to dynamically generate EXTJS increase Web server computing costs and increase the CPU, memory resources and network bandwidth overhead cost. Will the performance bottlenecks in the UI does not really experience.
b). is not conducive to static JS resources to do some compression and caching, to performance tuning from this point of view of the difficult and obstacles.
c). This implementation is really nothing POINT lost, is not conducive to the promotion phase of the project "Fudge."
Option II. Using Eclipse-Plugin technology to achieve a positive ExtUI visual code generation and reverse engineer the UI designer; generate the SQL single-table CRUD iBatis mapping file and data persistence object or a substantive area of the object.
a). lower capacity requirements for developers, simple post-training team members can get started developing reduce the learning and training costs, improve development efficiency.
b). compile-time generation native EXTJS, at run time can easily be compressed, and caching.
c). implementations than JspTag attractive, easy promotion.
Defects and deficiencies:
a). to achieve a positive reverse visual UI designer to achieve a relatively technical requirements higher than JspTag, the development cycle will be very long.
2 programs on the above fact, I have been entangled for a long time, but now the time that must make a choice. So please send to see what comments and suggestions. Or a better implementation. Hope you feel free.