On Apr 11, 2014, at 4:47 PM, Luc Fabresse <luc.fabresse@gmail.com> wrote:

> Hi Sebastian,
> 
> Really nice video and demo app!
> Thanks a lot for sharing this.
> 
thanks for your feedback, I’m glad you enjoyed!

> Is the code available?
Two issues with that:
1. it has many piece and a screencast for that would be long
2. Amber is changing a little how it organises things, I would like to share the new way and that app has the old way. Hopefully this is the first screencast of many showing the new way which is way cooler.

What can be done? I’ll release the pieces and screencast as I can. One is already there but could find time to explain how to install motivation, applicability, etc. Stay tuned!


> To learn more in details ;-)
> 
> In the video, I also liked when you presented the root folder of your project and how you managed the marriage of everything.
> For example, you explained that you use filetree so I suppose that you use git or svn for versioning the whole thing? 

Glad you mention this. I was suspecting someone would appreciate that (I know I would a while ago).
Yes, I use filetree and git.
If I have to start it again from scratch I think I would do it a little simpler
I guess I’ve learned as I did it XD

> 
> I would also have liked more details on the network communications.
> 1 websocket per webpage?
> home-made protocol?
That’s something interesting I didn’t showed there, you’re right. Not too fancy, just WebSockets with a custom Zinc handler on the backend. I’m thinking on doing a second part showing just that.

again thanks for your input and glad you enjoyed


> 
> Cheers,
> 
> Luc
> 
> 
> #Luc
> 
> 
> 2014-04-11 0:51 GMT+02:00 Sebastian Sastre <sebastian@flowingconcept.com>:
> Hi guys,
> 
> this might be of interest to some:
> 
> A tour into tasks, a flowing experiment on full-duplex web applications using web sockets
> http://blog.flowingconcept.com/brandIt/a-tour-into-tasks-a-flowing-experiment-on-fullduplex-web-applications-using-web-sockets
> 
> Is a ~28m screencast I’ve published in enGrish giving a tour on various details of this little experiment:
> 
> http://tasks.flowingconcept.com/service/
> 
> These screencasts will be feedback-driven so feel free to comment and send suggestions on how to make them better or cover topics you feel need to be proven the most for a broader audience
> 
> hope you enjoy and don’t forget to vote up on youtube if you do!
> 
> sebastian
> 
> o/
> 
> 
> 
> 
> 
> 

On Apr 11, 2014, at 5:17 PM, Luc Fabresse <luc.fabresse@gmail.com> wrote:

If I have to start it again from scratch I think I would do it a little simpler I guess I’ve learned as I did it XD

ha, now I am curious ;-) what did you simplified?

1. the components (perhaps by coding it more stateless in the front-end) 2. not using announcements and favour javascript events (lately I don’t see announcements in the front-end pays off, is more code for no solid benefit beside code elegance) 3. the new way to start a new amber project said that, on the Pharo side I’m quite satisfied sebastian o/

Hi, I get Internal Error: BITSession>>currentUser for both links. Cheers, Javier On Mon, Apr 14, 2014 at 2:59 PM, Sebastian Sastre < sebastian@flowingconcept.com> wrote:

On Apr 11, 2014, at 4:47 PM, Luc Fabresse <luc.fabresse@gmail.com> wrote:

I would also have liked more details on the network communications. 1 websocket per webpage? home-made protocol?

And here it comes some additional details on Part 2 http://blog.flowingconcept.com/brandIt/a-tour-on-tasks-part-ii

enjoy

feel free to ask additional questions, comment and rate!

sebastian <https://about.me/sebastianconcept>

o/

-- Lic. Javier Pimás Ciudad de Buenos Aires