D3 - Javascript visualization

Hello,

Just to show you a nice Javascript library (D3) for create visualization:

http://d3js.org
https://github.com/mbostock/d3/wiki/Gallery

--
Andre Hora


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

It is good library :) 
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I would really like to see how roassal can become something like that.

Stef

On Jul 3, 2012, at 5:15 PM, Santiago Vidal wrote:


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> I would really like to see how roassal can become something like that.

We will soon release the Javascript version of Roassal...

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Jul 3, 2012, at 11:52 PM, Alexandre Bergel wrote:

>> I would really like to see how roassal can become something like that.
>
> We will soon release the Javascript version of Roassal…

but my point is more can we use athens to build a d3 for pharo.

My problem is that if we do not build our future it will not be and this is why I'm ***really*** happy about roassal
coming to life.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi,
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Just wanted to bump this and ask: what is the status of this Javascript version of Roassal?

Today I have a meeting with the rest of my group.
We will probably release it very soon. Before the week end hopefully.

Cheers,
Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi,

Does this mean that we could easily have a Roassal visualization
produced on the server and rendered in the web browser?

Cheers,
Doru


On Wed, Sep 12, 2012 at 1:30 PM, Alexandre Bergel
<[hidden email]> wrote:


--
www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Does this mean that we could easily have a Roassal visualization
> produced on the server and rendered in the web browser?

Everything is entirely rendered in the web browser. Roassal works on Amber. No need of Seaside or what so ever.

Apparently we will delay the release of the JavaScript version. The reason is that we are experiencing an important slowdown. We are still unsure why.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi,

--


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> But, if we want to use moose on the server (for example to handle the models), we would need to communicate from the client to the server. And I  was thinking that if the implementation is the same one-to-one, we could just prototype in the image against the model, and then send it to the client as a string (instead of JavaScript). Would that work?

This is doable, but I am not sure how.
In the Amber mailing list I have seen some posts about the communication between clients and the server.
Probably something easy is to have the server produce a JSON description of what has to be processed by the client.

I have totally no experience on this for now.

Alexandre


--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I have been thinking that STON[1] would be "perfect" for communication between Amber and Pharo. I am working on a port of STON to Amber[2], but it is not quite finished...

In a nutshell, STON is a superset of JSON and you can use it to serialize Smalltalk objects. So when you say "one-to-one mapping of objects", STON should make it easier to preserve that mapping over the wire between Amber and Pharo ...

Dale

[1] https://github.com/svenvc/ston/blob/master/ston-paper.md
[2] https://github.com/dalehenrich/ston/tree/amber
----- Original Message -----
| From: "Alexandre Bergel" <[hidden email]>
| To: "Moose-related development" <[hidden email]>
| Sent: Friday, September 14, 2012 6:22:37 AM
| Subject: [Moose-dev] Re: D3 - Javascript visualization
|
| > But, if we want to use moose on the server (for example to handle
| > the models), we would need to communicate from the client to the
| > server. And I  was thinking that if the implementation is the same
| > one-to-one, we could just prototype in the image against the
| > model, and then send it to the client as a string (instead of
| > JavaScript). Would that work?
|
| This is doable, but I am not sure how.
| In the Amber mailing list I have seen some posts about the
| communication between clients and the server.
| Probably something easy is to have the server produce a JSON
| description of what has to be processed by the client.
|
| I have totally no experience on this for now.
|
| Alexandre
|
|
| >
| >
| > On Friday, September 14, 2012, Alexandre Bergel wrote:
| > > Does this mean that we could easily have a Roassal visualization
| > > produced on the server and rendered in the web browser?
| >
| > Everything is entirely rendered in the web browser. Roassal works
| > on Amber. No need of Seaside or what so ever.
| >
| > Apparently we will delay the release of the JavaScript version. The
| > reason is that we are experiencing an important slowdown. We are
| > still unsure why.
| >
| > Alexandre
| >
| > >
| > >
| > >
| > > On Wed, Sep 12, 2012 at 1:30 PM, Alexandre Bergel
| > > <[hidden email]> wrote:
| > >>> Just wanted to bump this and ask: what is the status of this
| > >>> Javascript version of Roassal?
| > >>
| > >> Today I have a meeting with the rest of my group.
| > >> We will probably release it very soon. Before the week end
| > >> hopefully.
| > >>
| > >> Cheers,
| > >> Alexandre
| > >>
| > >>>
| > >>> On Wed, Jul 4, 2012 at 8:02 AM, Stéphane Ducasse
| > >>> <[hidden email]> wrote:
| > >>>
| > >>> On Jul 3, 2012, at 11:52 PM, Alexandre Bergel wrote:
| > >>>
| > >>>>> I would really like to see how roassal can become something
| > >>>>> like that.
| > >>>>
| > >>>> We will soon release the Javascript version of Roassal…
| > >>>
| > >>> but my point is more can we use athens to build a d3 for pharo.
| > >>>
| > >>> My problem is that if we do not build our future it will not be
| > >>> and this is why I'm ***really*** happy about roassal
| > >>> coming to life.
| > >>>
| > >>>>
| > >>>> Alexandre
| > >>>>
| > >>>>>
| > >>>>> On Jul 3, 2012, at 5:15 PM, Santiago Vidal wrote:
| > >>>>>
| > >>>>>> It is good library :)
| > >>>>>>
| > >>>>>> Last year we used it with Alexandre to export Mondrian
| > >>>>>> visualizations to HTML. It is in the export section of
| > >>>>>> Mondrian easel.
| > >>>>>>
| > >>>>>> Cheers,
| > >>>>>> Santiago
| > >>>>>>
| > >>>>>> 2012/7/3 Andre Hora <[hidden email]>
| > >>>>>> Hello,
| > >>>>>>
| > >>>>>> Just to show you a nice Javascript library (D3) for create
| > >>>>>> visualization:
| > >>>>>>
| > >>>>>> http://d3js.org
| > >>>>>> https://github.com/mbostock/d3/wiki/Gallery
| > >>>>>>
| > >>>>>> --
| > >>>>>> Andre Hora
| > >>>>>>
| > >>>>>>
| > >>>>>> _______________________________________________
| > >>>>>> Moose-dev mailing list
| > >>>>>> [hidden email]
| > >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
| > >>>>>>
| > >>>>>>
| > >>>>>>
| > >>>>>>
| > >>>>>> --
| > >>>>>> Santiago Vidal
| > >>>>>> _______________________________________________
| > >>>>>> Moose-dev mailing list
| > >>>>>> [hidden email]
| > >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
| > >>>>>
| > >>>>>
| > >>>>> _______________________________________________
| > >>>>> Moose-dev mailing list
| > >>>>> [hidden email]
| > >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
| > >>>>
| > >>>> --
| > >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
| > >>>> Alexandre Bergel  http://www.bergel.eu
| > >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
| > >>>>
| > >>>>
| > >>>>
| > >>>> _______________________________________________
| > >>>> Moose-dev mailing list
| > >>>> [hidden email]
| > >>>> h
| >
| >
| > --
| > www.tudorgirba.com
| >
| > "Every thing has its own flow"
| >
| > _______________________________________________
| > Moose-dev mailing list
| > [hidden email]
| > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
|
| --
| _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
| Alexandre Bergel  http://www.bergel.eu
| ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
|
|
|
|
| _______________________________________________
| Moose-dev mailing list
| [hidden email]
| https://www.iam.unibe.ch/mailman/listinfo/moose-dev
|

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev