Please come with me (end)-notes for using ext and Llano

There are more and more business events! So I have to take some time to write out the key points I know and discuss them with you. Although I have been mixing in the software industry for more than 10 years, I always feel that I know too few things (ext2.0 is indeed very good and I have only been in touch with Js for three months. Code At present, I just looked at the areas that are commonly used in our actual projects ). Hope to make some talented friends.
In fact, my technology is not strong, and I have been doing management and quality work. Sometimes writing code is only for research or interest. Two years ago, because the project team was too busy and experts could not spare time, I wrote the company's web development framework. At that time, I had not learned java. It was really hard, everything is now available. After two years of project testing, the product can be used within the company. As for the. NET version, some problems may occur after it is transplanted. If you need any help, you can contact me: QQ: 657241411 emial: liusj@139.com
I will share my research experiences with you below:

1) Notes for extjs 2.0:
A) There is no good ide, and it is really not as convenient as Delphi development! According to Wangjing browser and Castle's example referenced by Ms, I believe that if the ext team does not provide better development support in a timely manner, it will be difficult to promote good things. Currently, we can install Firefox and install another firebug to reduce the debugging time. If vs2008 is used, JS debugging may be easier.
B) ext provides a wide range of components. If you want to create some new interface components, try to use the combination method with less inheritance. The following figure shows the components of the task board: Msgs =   Function (CFG) {
This. Initialconfig=CFG;
This. Panel=Null;
This. Draw (CFG );
}

Msgs. Prototype =   {

Draw: Function (CFG) {
// If (this. panel! = NULL) for (var p in this. Panel. Items) This. Panel. Remove (this. Panel. items [p]);
If ( This . Panel ! = Null ) Ext. Destroy ( This . Panel );
This . Panel =   New Ext. Panel ( {
Width: cfg. width, height: cfg. height,
// Basecls: 'x-plain ',
Renderto: cfg. div_id,
Title: cfg. title,
Autoshow: True ,
Layout: ' Table ' ,
Layoutconfig: {Columns:3} ,
Collapsible: True ,
Frame: True ,
Defaults: {Frame:True, Width:200, Height:200} ,
Items: cfg. Items
} );
} ,
Sethtml: Function (ID, text) {
//Alert (text );
VaRMSG=This. Panel. findbyid (ID );
MSG. Body. Update (text );
} ,
Removeitem: Function (ID) {
This. Panel. Remove (ID,True);
This. Panel. dolayout ();
} ,
Additem: Function (ID, title, text) {

Ext. Apply ( This . Initialconfig. Items ,[ {ID: ID, Title: title, HTML: text} ]); // Todo decode tostring then encode
This . Initialconfig. Items = Ext. Decode ( " [{ID: 'msg1', Title: 'item 1'}, {ID: 'msg2', Title: 'item 2'}, {Title :' " + Title + " ', HTML :' " + Text + " '}] " );
Alert (Ext. encode ( This . Initialconfig. Items ));
This . Draw ( This . Initialconfig );
}
} ;

C) Clarify the event model mechanism and component registration mechanism. Some introductions are provided in the garden.ArticleCan view, if there is not much time I suggest looking at ext-2.0 \ source \ widgets \ pagingtoolbar. js
D) try to use the debug version during development and output it using Ext. log. However, it is not as convenient as log4j and so on.

2) Llano considerations:
Although it is owned by the company, you can study it and use it in business. Please inform us so that we can discuss how to provide technical services to achieve a win-win situation.
A) based on the lessons learned from previous project teams, our basic entity can only use string-type IDs.
B) simple multi-to-multiple relationships can be centrally maintained by the system. Invalid link data is automatically cleared when an object is deleted.
C) directly develop the required data parameter dictionary function and use the cache policy.
D) JAVA supports toxml (), and the net version reloads tostring () to output JSON format, and does not support XML

Due to stability requirements, the company's requirements should be as simple as possible. In fact, I agree that "the most effective is often very simple! ". Llano simply integrates the excellent achievements of others with some of our best practices, so the entire framework is 40 K. In some tests, we found that there are still many differences between nhib.pdf and Java versions.

Well, it will be written here recently. I feel that everyone must pay attention to technical ideas. After all, the success of a project usually accounts for only 20% of technical factors, but the energy consumption is 80% of the time. If you have mastered the key ideas, in fact, there is no worries about the framework and tools in. net. LINQ is a good example. But it is also two sides. The poor Java tools cultivate a large number of outstanding architects.

Alex 1-7