From: <Hov...@ly...> - 2003-04-30 05:29:10
|
1. By autoconfig I did not mean system config. Just executable Jar file if we start it without parameter will look for autoconfig.xml in the current directory. It is like having default command line "mainclass autoconfig.xml", although it we want to start with another config we just need to provide another command line "mainclass anotherconfig.xml" 2. We agreed that need RC also in the system config. TestUI should initiate also RC instantiations. The only difference is that RC knows about itself and will not create new instance but rather will call its own methods. 3. I understand that you put it under system but TestUI should not be a part of system. My suggestion is to create a System device which will contain ModelConfig and RC (maybe a few more) and have TestUI communicate with this device and not directly with ModelConfig. Then we will have clear separation of logic and UI. Thoughts? 4. Last time we seems agreed to have one error outpin with message and error code. That will simplify the picture and code. Error message should also contain the part/connector id which it failed to add/delete etc. 5. Intuitively I feel that if we go that way that framework will keep the queue internally we may need to have also a framework part so that other parts can call its services (e.g. to get the queue and display it during the testing stage). Quite similar to RC case. Best Hovhannes |