Jupiter algorithm

after days, weeks and months, i finally found the algorithm that will help solve the consistency problem for our application. the jupiter algorithm is an improvement of dOPT (Distributed Operational Transform) algorithm which is suitable for a client-server environment and requires synchronization with a central server to manage all the changes on a document and broadcast the results to other clients. it does not require any locking mechanism, so it supports synchronous collaboration.

i just found out that ACE and Gobby uses it. good thing i also found an API for it in the ACE website. anyway, more on this later, since i’m still reading some articles about it.

c/o ariel

http://www.seas.upenn.edu/~cse400/CSE401_2006/Saviano/architecture.html

http://stanley.cs.toronto.edu/reports/2004-winter/collabauth-ae.html

waah!

computers anakin and c3po have no network… reah and i miss our computers.

hayy…sad

eh? (for lack of a better title)

sorry for the uber-late update. anyway, on my part–tabs, enter key, delete and backspace now works. currently working on collaboration (how to maintain consistency across all users). i’ve also disabled history/offline messages in multi-user chat because it’s not really necessary… once a user joins the room, the admin sends all the updates to the new user…

hmm… what else? i’m also updating the GUI to add the icons and sounds included in the application.

c/o ariel

so far..

we finished integrating the added packet collector and chat manager to the already existing application features.  we’ve been working on text highlighting and weren’t able to make it work with JTextArea so we decided to switch to JTextPane instead.  we are currently working on the needed changes on the collaboration since the two components have somewhat different functions.  we still have to work on efficient color assignment though, now that the app has a chat manager.   for now, we are thinking of limiting the number of users in a session to a certain number for basic assignment.  we are also done with the display of the typing status of the participants in the session.

current status…

we have just finished integrating one-to-one chat, new session alert, and polling on online session…

still working on the text highlighting feature…

issue: is the ordinary member of the room allowed to invite other users or this privelege is only given to the admin/creator of the room?

c/o hana

paper v3

we have just finished working on the paper. check pa ulit mamaya.

c/o reah

wiki updated (ulit)

wiki updated!

aside from the mentioned collaboration issues, we are working on the following:

1. pag update nung session list (walang listener)
2. admin privileges ng creator ng session
3. may bugs din yung sa list ng participants sa session
4. aside from the collaboration, minsan din eh hindi lumalabas sa panel nung ibang yung messages (muc)
5. dapat destroyed na ang room once mawala yung admin, pati yung muc

c/o reah

wiki updated

actually kanina pa sya updated kaso ngayon ko lang naipost. wala pa yung bagong screenshots.

wiki update

updated wiki (just a small part on Preliminary Studies).

app update:

• still can’t figure out how to fix bug (see previous post: collaboration v1.0). once connected on a wildfire server, backspace is sent accordingly to other users (but shows an unknown character) in a collaboration session, but on jabber.org server, if a user types the backspace, the user suddenly leaves the session for an unknown reason. have to fix this bug…
•  moreover, there were also problems encountered in outputting the text on the text area. has to do with the positioning.

that’s all for now, i guess…

-ariel

collaborate version 1.0

12/27/2006 8:12 am

collaboration works… or at least part of it.

notes:

1. carriage return doesn’t work (doesn’t show in other clients)
2. backspace doesn’t work (other clients show an unkown character)
3. letters work (both upper and lower case)
4. haven’t tested other characters. although if uppercase letter works, then most probably characters that need the shift key would also work.

later…

c/o ariel (no vacation here)

ps.

messages sent in MUC are wrapped in <collaborate> </collaborate> tags (just to take the feel of having an xml-based app). to differentiate a chat message from a collaboration message, a type attribute is added. chat messages are of type “chat” while collaboration message (the one that goes in the collaboration area) are of type “work”. attribute will be expaned once the radar view feature and keyboard simulation feature is added.