ryosua / networkcodeeditor Goto Github PK

• JTextArea
• Remove other stuff

Your team report (PDF, please) must explain what your program does and how to use it.

"There must be a Java-based system for data persistence – in other words a text-file, database, or some other mechanism (e.g., XML) where user and possibly other data can be stored and retrieved for later use. "

I forgot about this requirement. I think this is why I added user authentication to the proposal. It is an easy way to add data persistence.

1. "They would be presented with the option to start or join a session."

   We changed it so that there is a server for each session, so clients may only join a session by inputting an ip.

2. "If they choose to start a session, they would be asked to select a directory to share. Once selected, the editor would open, with the file on the right, and the directory on the left, similar to the Sublime Text interface(or most other text editors)."

   They select a directory by clicking the load file button.

3. "They could then invite other users on their friends list or by entering an email."

   Because each session has its own server, users just share the ip address of the server to invite users.

4. "Once the other editors accept the invite, the application downloads a copy of the directory to their
   computer, and all users can begin editing the files simultaneously in real time."

   We chose instead to share just the contents of the document loaded. If the user wants a copy of the document that they are working on, and they are not the one that uploaded it, they can simply use the save button to save a copy. The user that loads a directory can easily switch to any file by clicking on the file in the list.

5. "We will also use threads to allow multiple sessions concurrently."

   Again, as each session has its own server, we do not need to handle multiple sessions.

6. "We will use a database for storing things like users. We will use another Java-based system for other data persistence, for example the file/files currently being edited."

   We have save and load buttons for data persistence instead.

Doing tonight after class.

• Enter a username to create a room. OR
• Join a room by entering the roomID

It doesn't look like the server synchronizes the data, am I missing anything?

I think this would be easy to implement and would make the take the editor much easier to use.

The document sharing runs really slowly, is really buggy.

If we can save a change to a file and open that file with an existing editor, we should be able to use it with many different editors.

For our readme.txt can we provide instructions for compiling the program with ant?
yes

If so can we assume that ant is installed, or do we have to provide or link to instructions for installing ant?
no

Is the individual report one page double spaced?
no

How close do we have to come to our proposal as far as features?
pretty close

What is the filename for the submission?
411-project-final-yosuarc

Should we submit the individual reports separately or include them in the group submission?
yes

You should include a readme.txt file that clearly and specifically explains how to compile and run your project from the command line, including how to handle any library files. You must be VERY specific about what it takes to compile and
run your program.

We need a way for people to invite eachother to "rooms" - a shared space where people can edit a file. Right now everyone can edit the same text area.

A short (1 page) individual report will detail your interpretation of your results and your
specific contribution to the project.

TODO:

• Ryan
• Eric
• Shane
• Jose