@jeroendemiranda : don't forget to try the desktop client

@yojibee : of course. Save time for everyone

@dickhirsch : I noticed you were tweeting, but haven't found the time to catch up...maybe you can summize it in the call?

@yojibee : did you guys see the twitter conversation I had with @vdichev today about clients. It was interesting. Made me realize the importance of the Desktop Client

@sudhirrs : re: follow .. yes for now .. ESME is in development (alpha) so the desktop client for now doesnt have that but it wil in the future

@dickhirsch : ok thanks .. I'll dig into it .. but after I'm done with the web client .. not sure how much time I'll have for the desktop client till Berlin

@mrinal - it is now frozen. I was working all the time, so the problem appears to be connected with sort of timeout / inactivity of the AIR app itself

@dickhirsch : my guess is it will not happen unless your system disconnects from the network

@dickhirsch : I think I know the problem .. no need of a debug version .. I'll try and fix this after finsihing the Web UI .. there is already a bug on google code about this

@mrinal : but the problem happens usually after a period of inactivity - not necessarily hibernation.

Locking the screen has no effect

@dickhirsch : ah so the client is not able to talk to the server anymore .. @yojibee had mentioned something similar .. when her system wakes up after sleep

@mrinal : If new messages arrive in the web client, these aren't updated to the air client

@mrinal : No, the application works. I can type in an esmet and hit return. The text disappears and I see the message "sending message". The message never arrives however.

@dickhirsch : when you say freeze .. do you mean .. nothing reacts to your mouse/keyboard ? .. for example if you mouse over cloud tab does it react with a color change etc. ?

@mrinal : I have the feeling that it might be connected with my laptop's screensaver being activated but I'm not sure. The desktop freezes and I don't see any new messages.

@dickhirsch : can you please describe the problem again please .. wheat do you mean by freeze ?

I'm having trouble with AIR client freezing. @mrinal - can you post the debug version

@esjewett : Google code would be perfect .. we are getting started on that now

@mrinal : I think it's good. I prefer it to a browser tab, mostly because of notifications. For feedback, do you prefer a ticket on Google Code, a message here, or some other method?

@esjewett : hope you like the desktop client, its still an early release so we'll appreciate any feedback

@mrinal : Yes, the team is awesome! When will be the Tech Ed in Berlin?

@hsilva : thanks :) .. this whole team is amazing .. I wouldnt call the desktop client perfect though .. lot of work before that happens .. but I like how its turned out till now

@mrinal : Glad that helped :D The client is perfect, you're the best!

Thank you :) .. glad you like it .. the SettingsManager clas you wrote was a big help in saving token, server config etc.

Another test from the new desktop client!!!!

by teh way v0.011 fixed scroll problems from last version ... now monitoring memory usage improvement .. there should be some

profiling the AIR app for memory performance .. need a good message flow

profiling the AIR app for memory performance .. need a good message flow

profiling the AIR app for memory performance .. need a good message flow

@yojibee And here I was thinking that social messaging was all about instant gratification. Turns out that it's just about instant information :-) I'll be happy to wait for the AIR client.

@esjewett Only patience at the moment. But we are talking hours, not days

I have stopped my tracks as well now

@dickhirsch : yup

@mrinal : That is why tracks are so memory-intensive

@dickhirsch : memory is consumed in rendering each message and keeping the image in memory .. I will optimize .. more messages more memory .. will optimize after server setting

@mrinal : memory problem is better since I dropped my tracks. If you want to get the memory problem real quick. track our names

the memory problem gets bad aget you have 200-300 messages .. 2nd on my list todo @dickhirsch

Dam ! I wanted to build an automatic update mechanism before repleasing .. that would be really helpful

@dickhirsch : yup that is fine .. it is our architecture .. we have implemented the Mate framework

I still have a lit of things to do, before we can give this out to people

@mrinal : What did you use instead of the mx:List?

#Tags show up twice #Bug

there is a scroll UP mouse wheel #Bug in this version though

notice how images are chached when scrolling in this version unlike v0.008 .. it was quite bad there

@yojibee : I spent over 5 hours on rendering messages ... it was painful .. stupid flex framework mx:List

back with V.0.10

we need to keep talking on this all day, thats how bugs will come out

I really really like how the tags show up in the message!

@mrinal : Ah, got it!

@yojibee : :) .. that dunctionality is built into client .. the api needs to change a little for track windows to go away @dhague said he will fix tonight

@dhague : Everything works fine here..

@mrinal : Nice, links look like links again! I still cannot close track windows though in v0.010 ;)

FW: @dickhirsch : The search results should say "Search" and not "Track" << i disagee actuall I think search tab should be called track since its live track and not a one time search

New build posted

@dickhirsch : yes I am working on that animation .. I actually plan to grow the window a little as well

After you search, I would make the search results window active, so that you don't have to scoll to get to it.

FW: @dickhirsch : Testing tracking << less than works too

@dickhirsch : test messages .. looks like rendering bug gone

FW: @raja : yes use search and change window size

Testing tracking

yes use search and change window size

can you track in the desktop client?

Funny! Have you noticed how the notification from desktop client comes before the message shows up on the web?

I broke rendering at teh last minute .. fix coming in 2 min

@mrinal : Wow!

tags are visible as well. Cool

New AIR client build posted .. check it out .. still work in progress

code comitted to google code .. now building test build

prioritizing things I have to finish before this build

@dickhirsch : no, the notification just hides on a click .. thats how Growl functions and I like that, I can change it if people prefer otherwise .. eventually these things should become configurable settings

just notice that when you click on notification window that the client doesn't open. Is this functionality planned?

@dickhirsch : ok

@mrinal : I'll use the same google document but add a new column "Version"

I will stop in exactly 2 hrs from now .. whereever I'm at and release a build .. everyone can then test and thrash it, will fix any bugs after that

redoing the whole message rendering code ... Flex mx:List component is way to buggy .. made a bad decision early on to use that

right now the token is not stored in an encrypted store .. this is a #Todo for later

@dhague : fixed already re: "Updating tag cloud .." #Bug ... thanks

got local storage working .. desktop client now remembers your token .. thanks @hsilva for writing the SettingsManager .. needed little tweaking only

@hsilva just wrote me a SettingsManager class ... awesome !!.. I should be able to save settings between sessions .. trying to integrate now

@dickhirsch Your two messages starting with << showed up as blank in the AIR client

ha .. its nice how the client knows if @username exists .. it underlines exiting users .. i did not build it .. just happened :D

I'm thinking of limiting alerts only to @replies till the time I can make it a configurable setting .. what say?

@ok : thanks long way from finish though .. I'd say this version is 50% done .. we'll have abt 75% by Las Vagas

are avatar images too big ?

uploading to assembla

notifications fixed ... making new build now so everyone can use this more peacefully

could someone test the desktop client on Linux

@mrinal Yes, that would be a nice feature

We more than liked it, Mrinal. Loving it!

new build with bug fixes coming in a little bit .. glad everyone liked it so far :D

ha another bug .. long messages are truncated

@kirsten : sorry about the notification bug, I realized it last night after sending the build .. but then there was a power cut .. will send fixed build in a little bit

found a bug, I am throwing notifications even when the new message count is zero

@dahowlett : thanks, still a work in progress .. lot more to come .. let me know if you find bugs

just sent a new desktop clienty build to the list ... not posting link here on purpose

posted bug list for desktop client to google docs

one last thing to do before I show this to everyone

No problem. Always good to see movement in the timeline

@dickhirsch very, very soon .. I slept off last night so could not get a build out .. maybe in a few hours

Morning. Curious to see desktop client. OK, I admit - more than curious. Any idea when I can greedy little hands on it.

lets try some more tags

need to populate some tags

on my way home. Looking forward to an evening drawing for the Desktop client.