Hi! > However, I have to admit that I'm approaching this from a very basic > perspective, and I suspect that many other developers reading this list > will be in a similar position. Without any prior knowledge on the > subject, where should we start?
We all (should) know UML, the main UML metamodel elements (class, operation, package, namespace etc.). With this knowledge everybody should understand the purpose of most methods in argouml-core-model, and that everything there is the interface to a concrete UML implementation like Netbeans MDR or our eUML (that uses eclipse UML2). Very few further details are needed to know for now. Then, the eclipse environment should be set up and understood so that one can run the ArgoUML UML2-EUML debug launch configuration. Ready to start, launch it! The ArgoUML application will start and looks as if everything is fine. Of course it's not: create a class (OK), then an attribute for it (DANG!). Whatever you do, you'll eventually run into a problem. Concentrate on one simple case (e.g. attribute creation) and try to understand and fix it. Ask questions here, add found further tasks to the wiki. Create a JUnit test for your case (or, as Tom suggested, run an existing one without searching your own case). To the experienced: is this approach OK? > I don't know the reasons or the history behind it, but I suppose what > I'm really lacking at the moment is some sort of practical steps on what > to actually do. Which project do I have to load to start working on it? Open the argouml-core-model-euml project of course, aditionally to the projects you have opened for normal ArgoUML debugging. (You can close the argouml-core-model-mdr project probably.) > Where do I find the tests and how do I run them? I don't know (yet), but it should be easy to figure out. > How do I set up > ArgoUML with the new model, in whatever functional/non-functional state > it is in? It's in the wiki (Bogdan's report, a good starting point btw.). But you'll see when you launch as described, really! > How do I know what has or hasn't been updated yet? We must synchronize (issuezilla, wiki, here), but that's not a problem yet, a mail here if you start working on something is OK for now, but better create an issue for the euml subcomponent and mark it as STARTED (can be reverted). > How do I know if it is working? When it seems to work. Details will come later. We are at the beginning! > How do I know the difference between a test that > is supposed to pass and an obsolete test that will never pass? Only the spec will tell, or ask here. > The > topic sounds vast and complicated - are there any safe bits I can work > on without risking breaking something? Sorry for all the questions. I believe that after trying the above it won't look complicated anymore. Two topics of higher complexity probably (like getting ModelMemento work for Undo/Redo), but it's not needed to start with it. > If someone could break down some tasks to the beginner level, then there > would probably be a lot more help available, as (baring the top 5 or 6 > people involved), this is probably where most of the developers are. If > there are no tasks at this level, then I seriously think that those with > knowledge of the subject need to invest some time in creating training > materials for those without. The Wiki is a great start on this, but at > the moment, most of it goes over my head! Yes the wiki! I try to write down any simple task I see, but I'm just a beginner too! Quite late to admit this... ;-) Try and have fun! Thomas -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1536191 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
