You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by David Pollak <fe...@gmail.com> on 2009/01/03 01:39:11 UTC
Big checkin
Folks,
I just checked in a bunch of code:
- messages are displayed using JavaScript. Each time messages need to get
displayed, the function displayMessage(arrayOfMessagesToDisplay,
nameOfSpanToDisplayIn) is called. I have not written the displayMessage
JavaScript function. Who wants to own this?
- I've moved around the elements and generally de-styled the whole thing.
We need some form of style, but I figured less style was a place to start.
Thanks,
David
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Big checkin
Posted by David Pollak <fe...@gmail.com>.
On Sun, Jan 4, 2009 at 2:40 AM, Mrinal Wadhwa <mr...@gmail.com>wrote:
> browser-side set of messages? -- could you elaborate
The latest code sends JavaScript objects rather than formatted XHTML to the
browser. This is the browser-side set of messages.
>
> _
> Mrinal
>
>
> On Sun, Jan 4, 2009 at 4:07 PM, David Pollak
> <fe...@gmail.com>wrote:
>
> > I'm pretty sure that the contents of the Message JSON objects does not
> give
> > all the information necessary to render them in the UI (e.g., complete
> > information about the user that posted the message).
> > Let's iterate in terms of additional information necessary, server-side
> > parsing/digestion of the XML, etc.
> >
> > Also, over time, it would be cool to build up a browser-side set of
> > messages
> > so ESME has more and more of a GMail feel to it.
> >
> > On Sun, Jan 4, 2009 at 2:14 AM, Darren Hague <dh...@fortybeans.com>
> > wrote:
> >
> > > Hi Mrinal,
> > >
> > > I'm making good progress right now, in that the basic JS-client update
> > > mechanism is working. Today I want to work on bugfixes to the code
> (it's
> > > pretty rough & ready at the moment), so I hope to be able to check
> > something
> > > in by the end of today. Once that's done, it's open to anyone with
> better
> > > design skills than mine to improve the UI - I'm just focusing on the
> > > JS-based Comet update technology.
> > >
> > > Cheers,
> > > Darren
> > >
> > >
> > > Mrinal Wadhwa wrote:
> > >
> > >> Darren,
> > >>
> > >> I would be glad to help out with this .. so let me know.
> > >> At this point I think we should have some serious discussions around
> > >> Bill's
> > >> proposed design for the web client and plan that effort out. Lets
> > discuss
> > >> this in our meeting this week.
> > >>
> > >> With regards,
> > >> Mrinal
> > >>
> > >>
> > >>
> > >>
> > >> On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com>
> > >> wrote:
> > >>
> > >>
> > >>
> > >>> I'm happy to pick up the JavaScript stuff - been looking forward to
> it,
> > >>> in
> > >>> fact...
> > >>>
> > >>> I plan to use jQuery to help with the implementation.
> > >>>
> > >>> Cheers,
> > >>> Darren
> > >>>
> > >>> P.S. Thanks for finding the code, David - now get back to writing the
> > >>> book!
> > >>> :-)
> > >>>
> > >>>
> > >>> David Pollak wrote:
> > >>>
> > >>>
> > >>>
> > >>>> Folks,
> > >>>>
> > >>>> I just checked in a bunch of code:
> > >>>> - messages are displayed using JavaScript. Each time messages need
> to
> > >>>> get
> > >>>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
> > >>>> nameOfSpanToDisplayIn) is called. I have not written the
> > displayMessage
> > >>>> JavaScript function. Who wants to own this?
> > >>>> - I've moved around the elements and generally de-styled the whole
> > >>>> thing.
> > >>>> We need some form of style, but I figured less style was a place to
> > >>>> start.
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> David
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> > --
> > Lift, the simply functional web framework http://liftweb.net
> > Collaborative Task Management http://much4.us
> > Follow me: http://twitter.com/dpp
> > Git some: http://github.com/dpp
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Big checkin
Posted by Mrinal Wadhwa <mr...@gmail.com>.
browser-side set of messages? -- could you elaborate
_
Mrinal
On Sun, Jan 4, 2009 at 4:07 PM, David Pollak
<fe...@gmail.com>wrote:
> I'm pretty sure that the contents of the Message JSON objects does not give
> all the information necessary to render them in the UI (e.g., complete
> information about the user that posted the message).
> Let's iterate in terms of additional information necessary, server-side
> parsing/digestion of the XML, etc.
>
> Also, over time, it would be cool to build up a browser-side set of
> messages
> so ESME has more and more of a GMail feel to it.
>
> On Sun, Jan 4, 2009 at 2:14 AM, Darren Hague <dh...@fortybeans.com>
> wrote:
>
> > Hi Mrinal,
> >
> > I'm making good progress right now, in that the basic JS-client update
> > mechanism is working. Today I want to work on bugfixes to the code (it's
> > pretty rough & ready at the moment), so I hope to be able to check
> something
> > in by the end of today. Once that's done, it's open to anyone with better
> > design skills than mine to improve the UI - I'm just focusing on the
> > JS-based Comet update technology.
> >
> > Cheers,
> > Darren
> >
> >
> > Mrinal Wadhwa wrote:
> >
> >> Darren,
> >>
> >> I would be glad to help out with this .. so let me know.
> >> At this point I think we should have some serious discussions around
> >> Bill's
> >> proposed design for the web client and plan that effort out. Lets
> discuss
> >> this in our meeting this week.
> >>
> >> With regards,
> >> Mrinal
> >>
> >>
> >>
> >>
> >> On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com>
> >> wrote:
> >>
> >>
> >>
> >>> I'm happy to pick up the JavaScript stuff - been looking forward to it,
> >>> in
> >>> fact...
> >>>
> >>> I plan to use jQuery to help with the implementation.
> >>>
> >>> Cheers,
> >>> Darren
> >>>
> >>> P.S. Thanks for finding the code, David - now get back to writing the
> >>> book!
> >>> :-)
> >>>
> >>>
> >>> David Pollak wrote:
> >>>
> >>>
> >>>
> >>>> Folks,
> >>>>
> >>>> I just checked in a bunch of code:
> >>>> - messages are displayed using JavaScript. Each time messages need to
> >>>> get
> >>>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
> >>>> nameOfSpanToDisplayIn) is called. I have not written the
> displayMessage
> >>>> JavaScript function. Who wants to own this?
> >>>> - I've moved around the elements and generally de-styled the whole
> >>>> thing.
> >>>> We need some form of style, but I figured less style was a place to
> >>>> start.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> David
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Collaborative Task Management http://much4.us
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
DB Schema
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Just blogged about the ESME schema: http://blog.esme.us/database-scheme/
D.
Re: Big checkin
Posted by David Pollak <fe...@gmail.com>.
On Sun, Jan 4, 2009 at 7:34 AM, Darren Hague <dh...@fortybeans.com> wrote:
> Agreed - iteration #1 is now checked in: just the user's timeline (not the
> public timeline or tags/words) is now updated by a JavaScript function using
> jQuery.
>
> This is my first go at using jQuery - I have to say, I'm pretty impressed
> with it!
Yeah, jQuery is pretty darned amazing. Plus the jQuery community is
awesome.
>
>
> Cheers,
> Darren
>
>
> David Pollak wrote:
>
>> I'm pretty sure that the contents of the Message JSON objects does not
>> give
>> all the information necessary to render them in the UI (e.g., complete
>> information about the user that posted the message).
>> Let's iterate in terms of additional information necessary, server-side
>> parsing/digestion of the XML, etc.
>>
>> Also, over time, it would be cool to build up a browser-side set of
>> messages
>> so ESME has more and more of a GMail feel to it.
>>
>> On Sun, Jan 4, 2009 at 2:14 AM, Darren Hague <dh...@fortybeans.com>
>> wrote
>>
>>> Hi Mrinal,
>>>
>>> I'm making good progress right now, in that the basic JS-client update
>>> mechanism is working. Today I want to work on bugfixes to the code (it's
>>> pretty rough & ready at the moment), so I hope to be able to check
>>> something
>>> in by the end of today. Once that's done, it's open to anyone with better
>>> design skills than mine to improve the UI - I'm just focusing on the
>>> JS-based Comet update technology.
>>>
>>> Cheers,
>>> Darren
>>>
>>>
>>
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Big checkin
Posted by Darren Hague <dh...@fortybeans.com>.
Agreed - iteration #1 is now checked in: just the user's timeline (not
the public timeline or tags/words) is now updated by a JavaScript
function using jQuery.
This is my first go at using jQuery - I have to say, I'm pretty
impressed with it!
Cheers,
Darren
David Pollak wrote:
> I'm pretty sure that the contents of the Message JSON objects does not give
> all the information necessary to render them in the UI (e.g., complete
> information about the user that posted the message).
> Let's iterate in terms of additional information necessary, server-side
> parsing/digestion of the XML, etc.
>
> Also, over time, it would be cool to build up a browser-side set of messages
> so ESME has more and more of a GMail feel to it.
>
> On Sun, Jan 4, 2009 at 2:14 AM, Darren Hague <dh...@fortybeans.com> wrote
>> Hi Mrinal,
>>
>> I'm making good progress right now, in that the basic JS-client update
>> mechanism is working. Today I want to work on bugfixes to the code (it's
>> pretty rough & ready at the moment), so I hope to be able to check something
>> in by the end of today. Once that's done, it's open to anyone with better
>> design skills than mine to improve the UI - I'm just focusing on the
>> JS-based Comet update technology.
>>
>> Cheers,
>> Darren
>>
Re: Big checkin
Posted by David Pollak <fe...@gmail.com>.
I'm pretty sure that the contents of the Message JSON objects does not give
all the information necessary to render them in the UI (e.g., complete
information about the user that posted the message).
Let's iterate in terms of additional information necessary, server-side
parsing/digestion of the XML, etc.
Also, over time, it would be cool to build up a browser-side set of messages
so ESME has more and more of a GMail feel to it.
On Sun, Jan 4, 2009 at 2:14 AM, Darren Hague <dh...@fortybeans.com> wrote:
> Hi Mrinal,
>
> I'm making good progress right now, in that the basic JS-client update
> mechanism is working. Today I want to work on bugfixes to the code (it's
> pretty rough & ready at the moment), so I hope to be able to check something
> in by the end of today. Once that's done, it's open to anyone with better
> design skills than mine to improve the UI - I'm just focusing on the
> JS-based Comet update technology.
>
> Cheers,
> Darren
>
>
> Mrinal Wadhwa wrote:
>
>> Darren,
>>
>> I would be glad to help out with this .. so let me know.
>> At this point I think we should have some serious discussions around
>> Bill's
>> proposed design for the web client and plan that effort out. Lets discuss
>> this in our meeting this week.
>>
>> With regards,
>> Mrinal
>>
>>
>>
>>
>> On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com>
>> wrote:
>>
>>
>>
>>> I'm happy to pick up the JavaScript stuff - been looking forward to it,
>>> in
>>> fact...
>>>
>>> I plan to use jQuery to help with the implementation.
>>>
>>> Cheers,
>>> Darren
>>>
>>> P.S. Thanks for finding the code, David - now get back to writing the
>>> book!
>>> :-)
>>>
>>>
>>> David Pollak wrote:
>>>
>>>
>>>
>>>> Folks,
>>>>
>>>> I just checked in a bunch of code:
>>>> - messages are displayed using JavaScript. Each time messages need to
>>>> get
>>>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
>>>> nameOfSpanToDisplayIn) is called. I have not written the displayMessage
>>>> JavaScript function. Who wants to own this?
>>>> - I've moved around the elements and generally de-styled the whole
>>>> thing.
>>>> We need some form of style, but I figured less style was a place to
>>>> start.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Big checkin
Posted by Mrinal Wadhwa <mr...@gmail.com>.
Cool, look forward to it :)
On Sun, Jan 4, 2009 at 3:44 PM, Darren Hague <dh...@fortybeans.com> wrote:
> Hi Mrinal,
>
> I'm making good progress right now, in that the basic JS-client update
> mechanism is working. Today I want to work on bugfixes to the code (it's
> pretty rough & ready at the moment), so I hope to be able to check something
> in by the end of today. Once that's done, it's open to anyone with better
> design skills than mine to improve the UI - I'm just focusing on the
> JS-based Comet update technology.
>
> Cheers,
> Darren
>
>
> Mrinal Wadhwa wrote:
>
>> Darren,
>>
>> I would be glad to help out with this .. so let me know.
>> At this point I think we should have some serious discussions around
>> Bill's
>> proposed design for the web client and plan that effort out. Lets discuss
>> this in our meeting this week.
>>
>> With regards,
>> Mrinal
>>
>>
>>
>>
>> On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com>
>> wrote:
>>
>>
>>
>>> I'm happy to pick up the JavaScript stuff - been looking forward to it,
>>> in
>>> fact...
>>>
>>> I plan to use jQuery to help with the implementation.
>>>
>>> Cheers,
>>> Darren
>>>
>>> P.S. Thanks for finding the code, David - now get back to writing the
>>> book!
>>> :-)
>>>
>>>
>>> David Pollak wrote:
>>>
>>>
>>>
>>>> Folks,
>>>>
>>>> I just checked in a bunch of code:
>>>> - messages are displayed using JavaScript. Each time messages need to
>>>> get
>>>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
>>>> nameOfSpanToDisplayIn) is called. I have not written the displayMessage
>>>> JavaScript function. Who wants to own this?
>>>> - I've moved around the elements and generally de-styled the whole
>>>> thing.
>>>> We need some form of style, but I figured less style was a place to
>>>> start.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
Re: Big checkin
Posted by Darren Hague <dh...@fortybeans.com>.
Hi Mrinal,
I'm making good progress right now, in that the basic JS-client update
mechanism is working. Today I want to work on bugfixes to the code (it's
pretty rough & ready at the moment), so I hope to be able to check
something in by the end of today. Once that's done, it's open to anyone
with better design skills than mine to improve the UI - I'm just
focusing on the JS-based Comet update technology.
Cheers,
Darren
Mrinal Wadhwa wrote:
> Darren,
>
> I would be glad to help out with this .. so let me know.
> At this point I think we should have some serious discussions around Bill's
> proposed design for the web client and plan that effort out. Lets discuss
> this in our meeting this week.
>
> With regards,
> Mrinal
>
>
>
>
> On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com> wrote:
>
>
>> I'm happy to pick up the JavaScript stuff - been looking forward to it, in
>> fact...
>>
>> I plan to use jQuery to help with the implementation.
>>
>> Cheers,
>> Darren
>>
>> P.S. Thanks for finding the code, David - now get back to writing the book!
>> :-)
>>
>>
>> David Pollak wrote:
>>
>>
>>> Folks,
>>>
>>> I just checked in a bunch of code:
>>> - messages are displayed using JavaScript. Each time messages need to get
>>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
>>> nameOfSpanToDisplayIn) is called. I have not written the displayMessage
>>> JavaScript function. Who wants to own this?
>>> - I've moved around the elements and generally de-styled the whole thing.
>>> We need some form of style, but I figured less style was a place to start.
>>>
>>> Thanks,
>>>
>>> David
>>>
>>>
>>>
>>>
>>
>
>
Re: Big checkin
Posted by Mrinal Wadhwa <mr...@gmail.com>.
Darren,
I would be glad to help out with this .. so let me know.
At this point I think we should have some serious discussions around Bill's
proposed design for the web client and plan that effort out. Lets discuss
this in our meeting this week.
With regards,
Mrinal
On Sat, Jan 3, 2009 at 5:04 PM, Darren Hague <dh...@fortybeans.com> wrote:
> I'm happy to pick up the JavaScript stuff - been looking forward to it, in
> fact...
>
> I plan to use jQuery to help with the implementation.
>
> Cheers,
> Darren
>
> P.S. Thanks for finding the code, David - now get back to writing the book!
> :-)
>
>
> David Pollak wrote:
>
>> Folks,
>>
>> I just checked in a bunch of code:
>> - messages are displayed using JavaScript. Each time messages need to get
>> displayed, the function displayMessage(arrayOfMessagesToDisplay,
>> nameOfSpanToDisplayIn) is called. I have not written the displayMessage
>> JavaScript function. Who wants to own this?
>> - I've moved around the elements and generally de-styled the whole thing.
>> We need some form of style, but I figured less style was a place to start.
>>
>> Thanks,
>>
>> David
>>
>>
>>
>
>
Re: Big checkin
Posted by Darren Hague <dh...@fortybeans.com>.
I'm happy to pick up the JavaScript stuff - been looking forward to it,
in fact...
I plan to use jQuery to help with the implementation.
Cheers,
Darren
P.S. Thanks for finding the code, David - now get back to writing the
book! :-)
David Pollak wrote:
> Folks,
>
> I just checked in a bunch of code:
> - messages are displayed using JavaScript. Each time messages need to get
> displayed, the function displayMessage(arrayOfMessagesToDisplay,
> nameOfSpanToDisplayIn) is called. I have not written the displayMessage
> JavaScript function. Who wants to own this?
> - I've moved around the elements and generally de-styled the whole thing.
> We need some form of style, but I figured less style was a place to start.
>
> Thanks,
>
> David
>
>