I am using the calendar field for week plans. I think, the following changes would make the calendar field more usefull:
At our office work appointments start at 08:30 and end at 17:30. The current calendar has a fixed start (07:00 )and end time (19:00) which means there is a lot of white space on the screen. This could be improved with:
1: A property for the start time of the calendar.
2: A property for the end time of the calendar.
Then next to this, we do not make appointments outside these office opening ours. So we could do without the rows 'sooner' and 'later' that are there for appointments outside the 'normal' ours.
3: A boolean property field (or tow) for showing or hiding the overflow rows.
Below the calendar there is an option field (day, workweek, week, month) we only need the workweek view.
4: A boolean property field for showing or hiding the option buttons
I experimented with the changes above and these changes can be done with rather simple code changes (for Swing and RCP client).
Then our minimum appointment time is 10 minutes. The space reserved for an appointment of 10 minutes is so small that you cannot read the text.
5: A property for the minimum row height ( = 1 hour).
For now I have only experimented with the minimum height for an appointment. This is easy to do and good enough for our solution yet, but not good enough for small screens or calendars that need more rows. The problem with this is that the calendar might get bigger then the screen and you need to add scrolling, which is harder to do.
Maybe there are more or better ideas for improvements.
Do you want a separate ticket for every item or one for all.
I have all the code with the changes hardcoded (so no property editors), but I don't know how to make a patch. What I did is that I created my own calendar component and copied all the code I needed into that.
Is there some tutorial on how to set up a development environment to work on Scout itself so I can make the patches.
The easiest way to create a patch is to clone our repo and import the plugin projects, that you want to modify into your workspace. We recently moved to GIT see http://wiki.eclipse.org/Scout/Contribution#Getting_the_Scout_Sources. Then you can modify the sources. To start your application with the scout projects in the workspace just make sure they are selected in the product. You may need to synchronize.
3: Now I imported (File->Import) from the Runtime only the org.eclipse.scout.rt.ui.swing plug-in
Then I get errors about missing imports, for example:
The project was not built since its build path is incomplete. Cannot find the class file for javax.mail.internet.MimeMessage.
I can try to fix this by modifying build path but it feels a little strange to me that I have to do this. ?
(I also get these errors when I import everything from the runtime)
Then one more question, what do you exactly mean by: "To start your application with the scout projects in the workspace just make sure they are selected in the product". Where do I have to make the selection in a way that the modified plug-in is used instead of the scout plug-in that is already there.