[Cosmo-dev] Cosmo UI Status

[Travis Vachon]

Hi folks

Just wanted to update on this again.

I wasn't totally clear on what Bobby and Matthew are working on  
regarding getting Item saving working from the ui, and as a result  
was probably pretty wrong in my estimate for that piece. We've also  
run into a couple bugs that looks like server problems, so my part  
(the service/translation stuff) of saving and creation are probably  
going to be later today or tomorrow at the earliest. I've been  
working on a way to get some semi-automated integration testing using  
a modification of our cosmo test runner (ctr.html) so hopefully we'll  
be able to keep this stuff regression tested as well.

I'm continuing to plug away on the items I mentioned, and will  
probably get some of the other items finished earlier than I  
expected. I'll keep updating this thread as appropriate.

-Travis


On May 15, 2007, at 6:56 PM, Travis Vachon wrote:

> Hi folks
>
> Just wanted to follow up on this and let everyone know where I'm at  
> with this stuff.
>
> Loading of events still only "mostly" works, but it mostly works in  
> most of our supported browsers, which is an improvement. The base  
> calendar ui loads without problems in all browsers, but event  
> loading is still hung up on a problem with XML parsing in IE. I'm  
> working with Brian to try to resolve this bug and hope to have good  
> news tomorrow. Unfortunately, fixing cross browser incompatibility  
> has taken all day today. The good news is we're getting these bugs  
> now while they're relatively simple to catch, and I've been adding  
> unit tests to avoid future regressions.
>
> Tomorrow, assuming no unforeseen cross browser problems, I'm  
> planning on finishing up the code to get Bobby's Object Model  
> translated to EIM for saves and updates. My goal is to get event  
> saving and/or creation working by tomorrow night. That may be  
> ambitious, and I have about medium confidence that I'll be able to  
> meet that. I can't see any reason why this wouldn't be done by the  
> end of Thursday, however, so I'd give an upper bound of about 2  
> days on getting that code in place.
>
> Bigger picture, I'm hoping we can get most of the details of this  
> stuff wrapped up by early next week. In my mind that includes:
>    * Saving/ creating events.
>    * Getting/saving collection details (should be pretty  
> straightforward)
>    * Getting bookmarkable URLs working again (probably easy, small  
> chance of  unforeseen problems)
>    * Getting preferences/subscriptions working again. This depends  
> on some server side code that I believe is not finished, so there  
> is some dependency on that.
>
> Let me know if you have any questions!
>
> -Travis
>
> On May 14, 2007, at 5:00 PM, Bobby Rullo wrote:
>
>> Here's my understanding of where we are with the Cosmo UI:
>>
>>
>> Getting us Back To Status Quo (i.e just getting old functionality  
>> working again)
>> --------------------------------------------------------------------- 
>> ------------------------------------
>> Loading of events "mostly" works. There are some cross-platform  
>> browser issues that Travis is dealing with.
>>
>> Saving/Updating/Deleting does not work yet. I believe that Travis  
>> is still working on some UI --> EIM stuff that is required to make  
>> this happen. Also, I am working on something (TBD in a followup  
>> email) which will hopefully make figuring out what the changes are  
>> between what the user enters (through either the form or through  
>> dragging, resizing, etc.) and the original event instance. This is  
>> also a dependency for getting updates to work, but it should  
>> untangle some of the tricky code that exists currently for  
>> diff'ing items.
>>
>> We are not currently displaying the real protocol URL's in the  
>> collection details dialog box. I stubbed out a method in the  
>> service layer for getting them, and then Brian added the server  
>> side code for getting them, so all we need to do is wire them up.
>>
>> I'm pretty sure that anonymous ticketed users are not working yet,  
>> but we should be close.
>>
>> Correct me if I am wrong, Brian, but I think we still need a way  
>> to CRUD subscriptions via Atom (or would it be CMP)?
>>
>> It sounds like a lot, but the grunt work is mostly done, now it's  
>> just tying up a bunch of loose ends.
>>
>>
>> Stuff for New (Dashboard) Functionality
>> -------------------------------------------------------
>> I have not yet coded the MessageStamp.
>>
>> Dashboard Atom projections still need to be done.
>>
>> _______________________________________________
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev