Umple

Hi Vahdat, I have committed your first patch. Good work. It is in r2737 Umple can now take more than two umple files as command line arguments and will combine them as part of a system. This conforms with standard compiler command line syntax, but it also allows for compiling different versions of a system.

Hi, I have just completed the process to create umple release 1.17.0.2716 and committed the files. I followed the instructions at [link] Please do svn update to bring everything up to date. This release incorporates all the work done in UCOSP projects this past

Hi, Because I am expecting a major contribution that has been slightly delayed, the Umple release scheduled for today will be delivered Wednesday instead. Timothy C. Lethbridge, PhD, P.Eng., I.S.P., CSDP Professor of Software Engineering and Computer Science / Professeur Titulaire de gï¿œnie logiciel et d'informatique

Understood (I was missing the context). -- aforward

Hi, I agree with the spirit of this comment, but I think this is a broader issue than just with state machines, and might be an extreme edge case that we don't really need to worry about. A lot of things are strictly 'order-dependent' in Umple. The order in which attributes and associations appear in generated code is dependent on

Hi Gabriel, I do not know the full context, so this might not make sense, but is there anyway to make the names of the statemachines more predictable (i.e. with mixins and such it can be difficult to deterministically, at least as a user, which one is 1 versus 2 versus 3). This is important because despite the fact that we don't want others

It is now possible to declare several active objects in the same class. The state-machine names are going to be simple StateMachine1, StateMachine2, etc. The thread object names are also shorter now.

The change has been made for PHP even if multi-threading isn't implemented completly. No change for Ruby are necessary. Commit : 2708

Hi, Thanks. I think long variable names are sensible in this context. - Tim Timothy C. Lethbridge, PhD, P.Eng., I.S.P., CSDP Professor of Software Engineering and Computer Science / Professeur Titulaire de g�nie logiciel et d'informatique Facult� de genie / Faculty of Engineering

The problem was occuring when you try to declare several state-machines containing activity and the same state names. Exemple of the problem : class CourseY { activeSm { someState { thread1 { do { System.out.println("Statement" ); } } } } anotherActiveSm {