I'd suggest to learn the API then run ArgoUML with the MDR repository rather than the eUML repository. Place breakpoints in the model interface to determine what methods there are call by what interactions with the application.
Because much has yet to be implemente in eUML I imagine a great deal of the application will not work enough for you to determine what is going on. But once familiar with the model API and the MDR implementation of that then you should then start looking at the eUML equivalent methods that are not yet implemented. As far as API goes in ArgoUML I'm afraid to say the the model interface is the only strict API we have. For the rest of ArgoUML we are only just starting to break down into subsystems and have yet to define an API for each one. In effect any public class and any public method forms the API in the rest of ArgoUML. This makes learning the application difficult for anyone new but your mentor and other devs will be there to help you. However as one of your submissions is to work on eUML then that would be with a clearer API. Take a look at what is yet to be implemented there and see how it has been implemented in MDR. Regards Bob. On 02/04/2008, Amit Surana <[EMAIL PROTECTED]> wrote: > Hi Bogdan & Christian > > I tried your sugesstions. > NotYetImplementExceptions are present in many source code files. If am not > wrong this particular Exception is thrown only for those constructs which > are not yet implemented. > > I did not get your term "high functionality". By this do u mean to say the > Functioning, GUI of argoUML ?? > > > On Wed, Apr 2, 2008 at 1:10 AM, Bogdan Ciprian Pistol > <[EMAIL PROTECTED]> wrote: > > > Hi Amit, > > > > > > On Tue, Apr 1, 2008 at 3:29 PM, Amit Surana <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > I have downloaded, compiled & tested the argoUML from source using > Eclipse. > > > Now I have begun with my next task of understanding the API's. > > Glad to hear that. > > > > > > > Can you please help me where exactly I should put in break points and > start > > > analyzing what parts of code is executed & so on. > > You should try to correlate ArgoUML's high level functionality with > > the model parts that are used in that context. > > For example: creating a new comment in the diagram editor in the Class > > Diagram will use the > > > "org.argouml.model.euml.CoreFactoryEUMLImpl.buildComment(element, > > model)" method. (I hope I'm right, I actually didn't tested this, :) > > ) > > > > This will be an adequate approximation of how much low level stuff is > > involved in the high level ArgoUML's functionality. > > > > Also, track the NotYetImplementedException exceptions (as Christian > > suggested) and notice the high level functionality that generates > > them. > > > > Bogdan > > > > > > > > > > > > > > > > I am trying to use the under-progress eUML model implementation. > > > > > > > > > -- > > > Regards, > > > Amit > > > > > > http://suranaamit.blogspot.com/ > > > OPEN SOURCE: No Bill, No Gates, No Windows, Its open > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Regards, > Amit > > http://suranaamit.blogspot.com/ > OPEN SOURCE: No Bill, No Gates, No Windows, Its open --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
