7th week

Finally, we were able to go back and forth between the fullscreen and smallscreen windows. However, this is still a small problem that whenever switching from fullscreen to the smaller screen, two windows pop up. Wierdly enough, both windows are the smaller screen, one is a "mirage" and you can't even type in it and it doesn't have the theme, and the other does have the theme (which we don't want  on the smaller screen) but you can edit it in. Next week, we'll hope to find an answer to this problem. Also, now that I have learned about the UIL Contest, I'm starting to become interested in it. I've looked on the website, and there's a individual test and then there's a team programming contest. And the good thing is that teams are allowed to use up to 2 reference books chosen prior.

6th Week

Having only 2 days this week, we weren't able to manage as much stuff as we had done in the previous weeks. This week, we were all assigned our specific tasks, like Matt working on the save/open buttons and functionality, I'm working on connecting both the projects together, and Micah working on the fonts. In the 2nd or 3rd week, I had found an online JAVA code that ran a program that opened an open and save window which let you choose through the files, but we're having a hard time trying to incorporate that code into our project. For the fonts, we are still working on it. One thing I was able to accomplish this week was getting both the fullscreen project and the main project interconnected. This is a big step to our project because now when running the Main Project, you get to type whatever, and whenever you click the menu item "Go Fullscreen" the application actually turns fullscreen! This makes us feel quite accomplished and professional, but now the problem is getting the text from the small window to be the same in the fullscreen window. We've tried to deal with this problem for over 30 minutes but there's been no luck.

5th Week

The greatest achievement of this week was the implementation of a theme into our project. It seems quite confusing, but actually all that needs to be done is download the theme file, and have the java class "implent it". With this, our text editor is very professional looking, with this classy-black new theme. Before, it was the window's classic, with the bright colors and not-so good looking menubar and scroll bar. But with this theme, everything looks better. If one would look at our project now it would seem that we worked on it for a very long time now. Also we are still working on the button functionality.

Our theme:

 

4th week

Even with Micah out the entire week, Matt and I were able to accomplish a lot in the class. Rather than making robocode, we decided to work on our projects instead and we got a lot of things done. First, we were able to retrieve the lost code (make a new code) for making the screen fullscreen. Then we made the background black, and the font green. We were also able to figure out how to adjust the font and font size of the text that goes into the text area. Then, we were able to come up with the margins so the text doesn't go all the way to the edges of the screen. We made a scroll pane, that includes the scroll bar, which allows the user to go up and down freely through the text editor. The more button functionality we worked on was the cut/cope/paste button which all work appropriately when pressed (control + x/c/v). The two major problems we had was having it to do those 3 conditions when a button is clicked, but we came to a consensus that when in fullscreen mode, the user will be using keyboard shortcuts, not the buttons in the file menubar. Thus, it makes no real difference. Another problem was the border of the fullscreen page was white, but we were able to make it black also. The still occuring issue is making the scroll bar not appear because its very distracting and doesn't match write-room.

3rd week

This week we were able to figure out how functionality is given to buttons, menubars, etc. All this is made possible with the help of ActionListeners. This is a method in Java, that allows us to tell what the program should do if the button or any other task is clicked or chosen. I was able to figure out a button which was able to clear all the text on the screen, and Matt was able to add functionality to the "Close" button on the file menubar. ActionListeners are actually a bit tricky but I think that if we read few more tutorials we can give a few more buttons functionality.