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

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.

current status

as of 12/27/2006 4:00 am:

1. multi-user chat works fine in the new prototype (or should i say current working app?)

currently working on:

1. sending contents of file being edited to users who joins a session
2. list of users in a session
3. collaboration
4. bugs, bugs, bugs… bug-a-boo

question:

1. should the one-to-one messaging be included?
2. can an owner of a session invite more users once the session has started? (take note that the current implementation is that to start a session, open/create a file, invite users, then start session.)

c/o ariel (no christmas here)

question…

hindi po ba medyo magiging sobrang simple kung mali-limit ang feature ng application namin down to “line numbers”?

current status

still working on session invitations. we are also integrating the finished application features into our new prototype. we have added:

1. line numbers to the collaboration area

2. close buttons to the tabs

3. opening and creating of files for each creation of session

c/o reah

hustle

we’re still in the process of modifying the application prototype according to the modified specifications indicated during last semester’s final demo. currently, the status is integrating all of the codes that each member has done. the integration would probably equate to that application that was done last semester (that is, without the collaboration part). we’re still trying to figure out how to manage the messages that comes from the collaboration area and how it will be processed in order to appear properly in a client’s view of the collaboration window.

-ariel

substance look and feel

i’ve looked up over the internet some look and feel API which could be considered in the development of the application and i got the substance java look and feel from https://substance.dev.java.net/. the problem is i don’t know which skin is appropriate for the application. obviously we want the application to be pleasing to the sight so it’s a no-no for the fancy-shmancy skins, as well as to the exotic skins. images of the sample skins can also be found on the same URL.

c/o ariel

One-to-One Chat Issues

I’ve finished integrating the one-to-one chat (i.e. private message) in the application, but there were issues that surfaced after the module was done. I’ve also implemented the tab-based system on the one-to-one chat (like the session chat) so all conversations will be placed in one frame/window (for better management).

Issues:

• Opening and closing of the one-to-one chat window. It seems that an error happens somewhere in the code that I can’t seem to track.
• Close button on each of the tab page. I’m looking for a way to add a close button on each of the generated tab page. I’m currently relying on the menu that would be used in removing the tabs.
• Duplicate tab pages. I don’t know if it has any adverse effects on the sending and receiving of messages though.
• Recipient of a message won’t see any messages being sent to him, unless he opens the window himself. This is of highest priority among the issues since a message must be delivered and seen on the recipient’s end.

All of these issues are GUI-related, unfortunately for me. But I’ll fix it. Although I’m going to move to the MUC part since it’s one of the required features. I’m still waiting for Hannah and/or Reah to finish the Roster part, so at least someone could help me with the MUC part.

:keeping my fingers crossed: :kinda sleepy as well:

updated: Oct 21, 2006 12:44pm
c/o ariel

Demo blues

So we weren’t able to present everything on the demo, just the login, logout and account creation part. To make things worst we had to make last minute changes because we weren’t able to use jabber.org due to lack of connectivity in JRDC. I found out at home that they too had problems with our DSL so I guess something really happened. I thought for a moment that the higher beings were convening against us. Good thing we were able to use Wildfire as a local server. I wanted to use this laptop as the server and the Solaris pc’s as the client stations, but for some reason, the connection always timed out. I ping-ed the IP address of this laptop at that time using Josiah’s group’s Windows pc and still had timed out results.

Well, at least we still have until Friday to finish this. Two modules left until this sem is done. I’m thinking of redesigning the whole look and feel of the application during the break to make it our own. I guess you can say that I’m tired of the usual Java look and feel of the GUI’s, not that I’m against it.

c/o ariel

Preparation for the demo

well, the second presentation was over and now we’re hustling over the completion of the requirements that needs to be done for tomorrow’s demo.

Thesis draft is being buffed up (especially the RRL part)

Pisara Editor application modules (integration with prototype–meaning functional):

• Login (ongoing) (done)
• Account Creation (done)
• One-to-One Chat (later) (ongoing)
• Multi-User Chat (later) (ongoing)
• Logout (uh… yeah, probably tomorrow) (done)

yeah, cramming… i know. apparently i had some last minute issues with my other cs subject. go figure, right?

c/o ariel