- Wiki Home
- FAQ Frequently asked questions
- Best practices for using Umple
- Publications and theses
- Installing Eclipse plugin
- Developer Setup
- UmpleOnline Setup
- Contribution Process
- Cheat sheet
- Umpleonline manual tests
- Planned development
Clone this wiki locally
Each UCOSP participant is asked to log all their accomplishments as well as the difficulties they have getting set up to understand Umple and other experiences they have. Difficulties might include understanding how to model in Umple, using UmpleOnline, code that is difficult to figure out, and development tools that are hard to figure out, or don't seem to work properly. The more log entries added the more we can better get a grip on the usability issues with Umple, and the more we can help future new contributors come up to speed.
Added Issue 567 (on Google Code).
Reverted Glossary change due to it breaking the tests when run in Eclipse.
Added Issue 563 (on Google Code).
Removed unused Pair class in r4021 (on Google Code). Removed unused CodeFileWriter interface in r4023 (on Google Code).
r4016 (on Google Code): Made Glossary a singleton, and updated the related getGlossary calls in cruise.umple/src/ and cruise.umple/test/.
Committed r4002 (on Google Code) and r4004 (on Google Code) refactoring code in Main_Code.ump. I removed some static state, reformatted the file, and removed the print/println/printerr functions, replacing them with just System.out.print, System.out.println, and System.err.print.
Some of the tests were depending on the console output being stored to a file as well as being printed, so I changed the relevant tests to intercept System.out and System.err and make assertions based on the output.
Committed r3966 (on Google Code). Removed unused classes in Plugin.ump, ActionResponse, and ErrorItem. Removed an unused member in GrammarAnalyzer.
Replaced usage of FileManager with SampleFileWriter and removed FileManager in r3907 (on Google Code).
Removed unused classes Type, SimpleType, ReferenceType in r3914 (on Google Code), removed unused class SemanticException in 3916.
Made refactoring commits for Umple code, notably in the Parser: r3899 (on Google Code), r3900 (on Google Code).
Made several refactoring commits for core Umple code, notably in UmpleFile and ExtraCode: r3896 (on Google Code), r3897 (on Google Code), r3898 (on Google Code).
Added the USESupport page.
Fixed Issue 538 (on Google Code) in r3885 (on Google Code).
Reported Issue 538 (on Google Code) for personal reference.
Committed r3863 (on Google Code) to make progress on Issue 487 (on Google Code). Changed USEGenerator to use UmpleTemplate and use external associations, added a unit test.
I have the USE generator working with external associations now. Still need to write unit tests to describe the functionality.
Started converting the USE generator to use the new templating language. Still have to work on the code formatting and adding unit tests.
Added support for slightly simplified USE associations in r3810 (on Google Code). This was partially deciphering the Association and AssociationVariable machinery and partially studying the USE grammar.
Working on USE associations. I'm able to parse them, but now am trying to understand the existing Association code so I can adapt it to the USE association tokens.
Looking into why the USE extension to the grammar isn't working in UmpleOnline. Set up a local instance of UmpleOnline to debug it without involving the build server. Found it was because UmpleOnline appends a "// End_of_model" comment, and inline comments were not part of the USE grammar. r3772 (on Google Code) fixes this in the diagram shown but only allows generation of USE code from the USE code; the others produce the same error.
More work on Issue 529 (on Google Code). Added simple attributes to USE classes in r3757 (on Google Code).
Changing from using a separate grammar to working the USE grammar into the Umple main grammar (Issue 529 (on Google Code)). Added in r3753 (on Google Code).
Removed Velocity from build process and removed the USE generator that used it, in preparation for using the other template language in r3741 (on Google Code)
Have an idea for why the unit test I wrote for the USE Importer is failing. RuleBasedParser uses some static variables internally to optimize the tests (and not have to parse the rules every time). Sent an email to umple-dev about it.
Struggling with writing a test case to describe the added functionality.
Implemented transforming USE files with empty classes into the Umple model. Works on the command line.
Looked through the usage of the custom EBNF grammar to see how to apply it to the USE language.
Created Issue 529 (on Google Code) describing the work in the USE extension to UmpleImporter.
Made progress on Issue 349 (on Google Code), adding the Ruby part of it in r3652 (on Google Code). Started looking into the UmpleImporter code for ECore; I should be able to reuse a large part of it; getting a parser for USE will be the hard part.
Made progress on Issue 349 (on Google Code), adding the PHP part of it in r3647 (on Google Code).
Made progress on Issue 349 (on Google Code), adding the Java part of it in r3576 (on Google Code).
Attempted work on Issue 349 (on Google Code), but was too ambitious with changes and ran into problems.
Committed r3472 (on Google Code), r3473 (on Google Code) (reverting the previous revision), and r3474 (on Google Code), adding the changes and fixing the issues.
Submitted Issue 504 (on Google Code). Submitted Issue 508 (on Google Code). Submitted patch which was committed as r3451 (on Google Code).
Submitted patch, added in r3427 (on Google Code) to make progress on Issue 457 (on Google Code).
Submitted issue 500 (on Google Code).
Submitted issue 489 (on Google Code).
Successfully built Umple on the command line, and attended the introductory Google Hangout. Submitted issue 486 (on Google Code).
Andrew Forward created this initial entry for Cody