[Xmi2code-develop] Working on the source

[AJ H. <aj...@aj...>]

Hello,

Still unable to leave well enough alone, I've continued working on the 
1.2beta3 code.  Rather than pass on what I've done so far, I thought I might 
mention what exactly I'm working on, so if I'm stepping on anyone's toes or 
if I should just stop, someone can let me know.

Things I am currently implementing:

	* x2c:codeblock ... x2c:endblock
	  These two documentation commands are for the Umbrello handler so when 
	  adding a nested class or multi-line enumeration a user doesn't have to use 
	  a x2c:def: command for each line.  

	* The ability to set the visibility of Class Scope Definitions.
	  Based on the current system, this would effect both x2c:def and the above 
	  commands (x2c:codeblock and x2c:endblock).

	* Processing aggregations and composition relationships
	  This is a continuation of what I started in the code I submitted 
	  previously.  In the code generation, this can create attributes (if 
	  necessary) describing the relationship.

	* Perl code Generator
	  What can I say, I'm a Perl junkie. 8-)

	* Code generation specifics based on stereotypes
	  Since certain UML spec defined stereotypes for classes indicate certain 
	  constructs, I wanted to get that kind of functionality.  For example 
	  enumerations can be defined by using a class widget with a stereotype of 
	 "enumeration".  The individual values of the enumeration are listed as the 
	 "attributes" with the "initial value" of any of the "attributes" being the 
	 assigned value to that particular value of the enumeration.  

	* Small minor additions/changes to prepare for the Umbrello 1.2 release.
	  There will be some changes in Umbrello's output file format in 1.2, and 
	  I've been putting some small parts in preparing for those changes (but 
	  nothing that prevents current functionality).  So far this has just been 
	  the extending of a couple of enumerations and the addition of a class 
	  variable to the Relationship tree.


I have, so far, implemented the codeblock .. endblock construct, but it's 
somewhat kludgey in it's current state, I'm currently refactoring the whole 
class scope definition system.

I hope I'm not offending anyone, or working on something others are currently 
working on.  Please feel free to tell me to stop (I promise I won't be 
offended!)  I'm just having a good time working on the source code.


Thanks,


AJ "Sandy" Harrington