Status Report: one.world (02/13/2001)
We fell a bit short of the goals we set out for last week. We
will need a few more days to meet the goals we set.
- Working on user repository/registry (named Inbox) (Daniel)
- Wrote a wrapper for the RemoteManager (Daniel)
- Wrote a super class (MainComponent) for some of our components (Daniel)
- Hacked and reworked skeletor into something extendable and wrote inital extension for one.box componenets (Albert)
- Router and Filter mostly implemented (Albert)
- Finish Inbox (Daniel)
- Finish Pop3 interface to clients using Ian's work
- Integrate with the rest of system (Daniel)
- Anything else that is on the horizon (Daniel)
- Finish Router and Filter -- shouldn't take long (Albert)
- Integrate with Daniel's components (Albert)
- Figure out what needs to happen next (Albert)
Deliverables for next tuesday
- Inbox, Pop3 interface and integration *WILL* be done (Daniel)
- Router and Filter should fit in with above too!!! (Albert)
By next week, we want a demoable system without any frills.
- Research REP: 3hrs
- Worked on Inbox: 12hrs
- Refactoring Inbox (RemoteManagerWrapper + MainComponent): 8hrs
- Learn javax.swing.text interface: 4hrs
- Hacking Skeletor: 1hr
- Writing text editing interface and extending for one.box: 4hrs
- Router and Filter Implementation: 5hrs
- Reading Daniel's code: 2 hrs
Just some stuff for writing the report later on. If anybody
likes to comment on them, I'll be glad to listen.
Chaining events. It would seem useful to have some
framework to do within the system as it is fairly common.
I managed to hack it right now. The main difficulty is that
right now when you have events coming into the EventHandler,
you have to 'forward' it to the appropriate component. However
this assumes that you know what events the forwarded handler
can accept. This situation occured because I needed to use the
RemoteManager and my component at the same time which both
need to get EnvironmentEvents.
REP is sweet, once you get over the initial learning curve,
It would be nice to have some starter code for
it since it appears setting it up would be the same for most
applications. Enter RemoteMgrWrapper which is a ripoff of the
RemoteManagerWrapper that is in TestREP.java. Hopefully this will
make its functionality easier to setup.
When two environments are communicating via REP, is the
communication bidirectional without one side (client) setting up a
- Checkpointing. I can't get it to work. I made transisent but
I still get the not serializable error. Why can't Java tell me
exactly which field is causing me problem. Will linkforcing
and making Inbox single threaded solve this problem.
Two things this week
- Swing isn't listed in the protection domain. I'm not sure what this means. Can I use it? The counter does, but it isn't explicitly allowed...
- Why was skeletor declared final? It would seem useful to be able to extend the thing to create skeletons for other projects
- I'm finding some of the comments in the documentation to be vague. For instance in SimpleOutputRequest, the comments for the constructor parameters are something like, "closure -- The closure for the new simple output request" is a fairly obvious statement and doesn't provide information. It may have been nicer to have no comments than a reflexive one.
Last modified: Tue Feb 13 14:34:49 PST 2001