Hi!

-------- Original-Nachricht --------
> Datum: Mon, 2 Apr 2012 10:17:38 -0700
> Von: Mark Fortner <[email protected]>
> An: [email protected]
> Betreff: Re: [argouml-dev] Usability Observations

--<snip>--
 
> As I've indicated before, if we can address the problems with CG, and
> support design reviews, it will be easier for people to see how the 
> tool can support their processes beyond simply creating pictures.

Thomas agreed now to post this stuff, so...

Those sources are a bit dated and I guess they are not even the
latest version, but maybe someone can use them to add new CG
features. I ran them with a UML2 version, so they should work
more or less with the latest sources (sorry, I have many dozens
of Argo versions here and most of them are customized in some 
way or another).

I cannot post the modules here, since they are too big, so I
attached them here:

http://argouml.tigris.org/issues/show_bug.cgi?id=5093

I cannot upload attachments > 1 MB, so I had to delete some
files. You need:

argouml-templatecg/lib/commons-collections-3.2.1.jar
argouml-templatecg/lib/velocity-1.6.3.jar
argouml-templatecg/lib/commons-lang-2.4.jar

in the template CG base module.

The idea behind those modules is, that a CG module provides
the infrastructure for the actual CG modules, but does not do
any actual CG. The language CG modules could then add a menu
item and a jar with a template set for the target language
to do the actual CG.

I guess, there are still quite some features missing in those
sources (like the template overloading), but I cannot check
at the moment.

Ciao,
Andreas

-- 
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!                          
        
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2944554

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]]

Reply via email to