Clone this wiki locally
Each UCOSP participant is asked to log all the difficulties they have getting set up to understand Umple. This includes 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.
( copy and pasted verbatim from another UCOSP student's log )
Log Entries in reverse chronological order
28 January 2015
UCOSP Semester Plan: UI/UX Features of State Tables
Improving the organization of the HTML for the state tables as outlined in issues 670 and 671:
--adding visual cues which will make nested states within state-event tables more apparent
--Concurrent state tables should also have visual cues which indicate parent and child events
--Child events should be displayed directly beneath parent events in state tables
Table Styling (keep .css styling within html code)
--Color coding state tables: states could be one color and transitions between states could be another
--Add tooltip popups for information not displayed in cells (such as guards)
--Change the background shade of substates to be a bit different from top level states. Each deeper nesting level would have incremental differences (a bit darker plus a bit greener for example)
--Create a visual cue to indicate when a transition applies to many substates
25 January 2015
-- I wrote a brief outline of my semester plan and sent it to Andrew and Tim with some questions.
-- One of my jUnit tests in Eclipse (which should pass I believe) is failing by giving me a null pointer exception at a lot of files (starting with cruise.umple.compiler.TextParser.load). I will be looking further into this issue on Wednesday morning.
21 January 2015
--Installed local server following instructions on code.google.com/p/umple/wiki/SettingUpLocalUmpleOnlineWebServer
18 January 2015
--This is the final day of the code sprint at SFU.
--During the morning I wrote a (currently) failing test which I will be applying to issue 670 (on Google Code).
--During my layover at the airport, I am experimenting with the test some more to make sure it is failing for the reason I want. I have some ideas as to what the problem with the nested state machines is, and my plan is to get the testing environment for state machines to be as efficient as possible as I will be working with them a lot this semester.
--I'm planning to install a local online web server for try.umple.org as soon as possible, also for testing.
17 January 2015
--Andrew Forward went over how to use some commands in svn to check which files have been modified/added/removed before submitting a patch
--Have been looking into issue 613 (on Google Code)
--Group presentation with all of the other UCOSP students
--Andrew discussed expectations for the program with us, and suggested I look into improving some UI problems with state machines. We created issue 670 (on Google Code) and issue 671 (on Google Code).
--Spent the rest of the afternoon researching how the code for state machines is currently working, trying to decide what exactly is going wrong with the way it is implemented now in regards to displaying nested states in tables (it looks someone has tried to indent nested states in the tables).
--Andrew went over some of the logistics regarding writing a test for a UI ticket.
16 January 2015
-- First day of code sprint at SFU Surrey
-- Ran another rebuild of umple using "svn -r revert". It now builds in Eclipse and all tests pass.
--Andrew Forward gave an overview of the Umple architecture and overall project.
--Andrew Forward explained test driven development to me as well as how to write a test
--Created first patch: added one line to the stateMachineComments() test in cruise.umple/test/cruise/umple/UmpleParserStateMachineTest.java to check that the number of classes created by the test file (100_stateMachineComments.ump) was one.
12 January 2015
--Made an ERD on try.umple.org: http://cruise.eecs.uottawa.ca/umpleonline/umple.php?model=150112581195
--I think (maybe) there are 3866 tests based on the Junit tab in Eclipse
9 January 2015
-- Set up most of the development environment on Linux Mint VM. Building umple from the command line was failing today and yesterday. Eventually the problem was resolved by uninstalling and reinstalling openjdk. The error I was getting when trying to build was:
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-7-openjdk-i386/lib/tools.jar
Buildfile: umple.build.xml does not exist!
Some threads which I found useful:
I think originally I had only one of the .jre and .jdk files installed for java, however I have no way of being sure exactly what the problem was. I tried installing JDK from the Eclipse website- but I now believe "sudo aptitude purge openjdk" (to uninstall) and "sudo aptitude install openjdk-7-jre openjdk-7-jdk" (to install) is the simpler way to go if you are on a Linux machine.
--Played around with try.umple.org