September 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] vm download site

by Chris Cunningham

On Wed, Sep 26, 2012 at 11:42 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > http://pharo.gforge.inria.fr/ci/vm/mac > http://pharo.gforge.inria.fr/ci/vm/linux > > and once we fixed the win builds > http://pharo.gforge.inria.fr/ci/vm/mac/win Is that win location right? a subset of mac? > best > igor + cami >

Sept. 26, 2012

Re: [Pharo-project] Learnable Programming

by phil＠highoctane.be

cool!!!! 2012/9/26 Sven Van Caekenberghe <sven(a)stfx.eu>: > This is _very_ interesting and _very_ welll presented: > > http://worrydream.com/LearnableProgramming/ > > Keep on reading, it keeps on getting better towards the end. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Sept. 26, 2012

[Pharo-project] Workspace>>#theme

by Sven Van Caekenberghe

Clicking the window menu of a Workspace in 20308 gives a MNU Workspace>>#theme in Workspace>>#addModelItemsToWindowMenu: Maybe Workspace subclassing from Object is the problem ? -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 26, 2012

[Pharo-project] UIManager>>#request: broken ?

by Sven Van Caekenberghe

In 20308, the following UIManager default request: 'Enter some text'. ask the question twiceâ¦ -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 26, 2012

[Pharo-project] Learnable Programming

by Sven Van Caekenberghe

This is _very_ interesting and _very_ welll presented: http://worrydream.com/LearnableProgramming/ Keep on reading, it keeps on getting better towards the end. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Alexandre Bergel

Thanks Torsten for your input. Indeed, many expressed a similar interest: being able to graphically edit a graph. Cheers, Alexandre On Sep 26, 2012, at 11:03 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > I just wonder what is necessary to use Roassal not > only as a visualization engine of existing data > but to give it more interactivity to create new > data/shapes/connections. > > An example: one can build a UML class shape and visualize > the existing class hierarchy of Pharo with the current engine. > > But is it possible to also hook into the engine so one can > have a palette and by visually adding new nodes (here UML classes) > and wire them visually to create new classes in the system > and use it as a modeling tool too? > > Simply said: whats required to additionally transform it into a > universal diagram tool with palette for custom shapes > and connections, outline, custom menues on shapes/nodes/connections > to open dialogs, properties page ... > > Something similar to GEF from Eclipse > http://www.eclipse.org/gef/ > http://www.eclipse.org/articles/Article-GEF-diagram-editor/shape.html > > I'm sure this would open up lots of opportunities to > build graphical applications with Pharo. > > Thx > T. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Alexandre Bergel

Thanks Ciprian! Cheers, Alexandre On Sep 26, 2012, at 3:49 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > Hello everybody, > > During the weekend I had a look at the Roassal project and I found it very good. Moreover I find that asking around the community for good ideas to drive the future of the project a cool initiative. > > About that, I completely agree with Ben's first 3 directions. Other cool ideas in terms of ergonomy can be found in the Yed graph drawing tool. > > From my experience working on computer-aided design tools for the electrical (electronical) industry i can say that one very important feature that these kind of tools need is the ability to create/edit large hierarchical graphs. From my perspective a electrical circuit is nothing more than a large graph of interconnected elements with each node representing a physical device. Hierarchical composition of such structures is necessary to ease the understanding of the system. In consequence IMHO being able to easily dive-in and get-out of hierarchical components is the most important feature that Roassal is missing right now. Just imagine looking at a layed-out graph of ten interconnected nodes, then just by clicking on one of these nodes the view is replaced by another graph representing the inner components. Furthermore I believe that such an approach can be abstracted away to more complex interactions (opening a view with an editor window on that particular instance of the node, etc). > > Another feature that I think it is missing in most (if not all) graph viewers/layout systems/editors is the possibility to have connection ports on the hierarchical nodes in order to preserve the connections passing through the hierarchy. > > some pointers: > > http://www.slideshare.net/teodorov/tools-and-crossbarbased-nanocmos-archite… > > http://stiff.univ-brest.fr/~cteodorov/manuscript-teodorov_FINAL.pdf > > > > Cheers, > > Ciprian Teodorov > > > > On Sep 26, 2012 6:16 PM, "Vanessa PeÃ±a Araya" <van.c.pena(a)gmail.com> wrote: > Thank you, Ben. And yes, this is the kind of things that are very useful. > > 3. Electrical Software Development Platform - CRITICAL priority > Of course, my own project to complete my masters within the next couple of months!! This is implementing a model browser for the IEC 61970 Common Information Model. I showed this to Alex a while ago and am just now getting back to the point I was at before switching from Mondrian to Roassal. While this has taken a while I am very happy with the additional control I have with Roassal (and a lot of this time has been too many demands by my day job). Perhaps a rough early release is not too far away. > I'm sorry but I don't know this, so I don't understand really. Is there some place I can see it? > > As yes, the features you mentioned are interesting. You are not the first to mention features 4, for example. > > Thank you very much :) > > Vanessa. > > > Alexandre Bergel wrote: > This is not that we do not have ideas :-) > > Our todo list includes: > - book chapter on Roassal > - exporters (e.g., HTML, SVG, JavaScript) > - semantic zooming > - way to compose shapes > - scalability > > We obtained this list from our personal needs and the need of the Moose and VW communities. > > Vanessa is working on a proposal for ESUG to help us on the development of Roassal. We are therefore surveying the Pharo community in case of there is a wished feature that we did not see or did not put high on our todolist. We are currently maintaining Roassal (i.e., fixing bugs) and pursuing our innovation effort (i.e., implementing cool ideas). The ESUG support will help us increase our productivity. > > And yes, we would love to see someone use Roassal to visualize genome, DNA and other biological data. We are ready to provide a strong support. > > Cheers, > Alexandre > > > On Sep 25, 2012, at 12:33 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > I don't know your project scope, but these pointers may help you to grab some features to implement: > > http://www.tm4.org/mev/features > > Also take a look into the Circular Genome Viewer: http://wishart.biology.ualberta.ca/cgview/gallery.html > > specially the browsable maps > > http://wishart.biology.ualberta.ca/BacMap/cgview_linked_maps/NC_003198/inde… > > check out the Expand+ and Rotate+ operations > > Other very nice engine is Circos > > http://circos.ca/ > > which contains plots that has been published in Science, Nature and PLOS. > > Cheers, > > HernÃ¡n > > > On 25/09/2012 11:48, Vanessa PeÃ±a Araya wrote: > Hello! > As you probably know, Roassal was presented at ESUG. We received a lot > of positive feedback from you and also a lot of request for features. > Thank you very much! > > We want to start working on this, but also prioritize what seems to be > more urgent. > For this, we would like to survey the community about > 1 - what are the features you would like to see in Roassal. Please, > provide a list of features requests and tell us about their priority > 2 - scenarios where you would like to use Roassal. > > Thank you very much, > Vanessa. > > > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Ciprian Teodorov

Hello everybody, During the weekend I had a look at the Roassal project and I found it very good. Moreover I find that asking around the community for good ideas to drive the future of the project a cool initiative. About that, I completely agree with Ben's first 3 directions. Other cool ideas in terms of ergonomy can be found in the Yed<http://www.yworks.com/en/products_yed_about.html>graph drawing tool. >From my experience working on computer-aided design tools for the electrical (electronical) industry i can say that one very important feature that these kind of tools need is the ability to create/edit large hierarchical graphs. From my perspective a electrical circuit is nothing more than a large graph of interconnected elements with each node representing a physical device. Hierarchical composition of such structures is necessary to ease the understanding of the system. In consequence IMHO being able to easily dive-in and get-out of hierarchical components is the most important feature that Roassal is missing right now. Just imagine looking at a layed-out graph of ten interconnected nodes, then just by clicking on one of these nodes the view is replaced by another graph representing the inner components. Furthermore I believe that such an approach can be abstracted away to more complex interactions (opening a view with an editor window on that particular instance of the node, etc). Another feature that I think it is missing in most (if not all) graph viewers/layout systems/editors is the possibility to have connection ports on the hierarchical nodes in order to preserve the connections passing through the hierarchy. some pointers: http://www.slideshare.net/teodorov/tools-and-crossbarbased-nanocmos-archite… http://stiff.univ-brest.fr/~cteodorov/manuscript-teodorov_FINAL.pdf Cheers, Ciprian Teodorov On Sep 26, 2012 6:16 PM, "Vanessa PeÃ±a Araya" <van.c.pena(a)gmail.com> wrote: > Thank you, Ben. And yes, this is the kind of things that are very useful. > > 3. Electrical Software Development Platform - CRITICAL priority >> Of course, my own project to complete my masters within the next couple >> of months!! This is implementing a model browser for the IEC 61970 Common >> Information Model. I showed this to Alex a while ago and am just now >> getting back to the point I was at before switching from Mondrian to >> Roassal. While this has taken a while I am very happy with the additional >> control I have with Roassal (and a lot of this time has been too many >> demands by my day job). Perhaps a rough early release is not too far away. >> > I'm sorry but I don't know this, so I don't understand really. Is there > some place I can see it? > > As yes, the features you mentioned are interesting. You are not the first > to mention features 4, for example. > > Thank you very much :) > > Vanessa. > > >> Alexandre Bergel wrote: >> >>> This is not that we do not have ideas :-) >>> >>> Our todo list includes: >>> - book chapter on Roassal >>> - exporters (e.g., HTML, SVG, JavaScript) >>> - semantic zooming >>> - way to compose shapes >>> - scalability >>> >>> We obtained this list from our personal needs and the need of the Moose >>> and VW communities. >>> >>> Vanessa is working on a proposal for ESUG to help us on the development >>> of Roassal. We are therefore surveying the Pharo community in case of there >>> is a wished feature that we did not see or did not put high on our >>> todolist. We are currently maintaining Roassal (i.e., fixing bugs) and >>> pursuing our innovation effort (i.e., implementing cool ideas). The ESUG >>> support will help us increase our productivity. >>> >>> And yes, we would love to see someone use Roassal to visualize genome, >>> DNA and other biological data. We are ready to provide a strong support. >>> >>> Cheers, >>> Alexandre >>> >>> >>> On Sep 25, 2012, at 12:33 PM, HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com> wrote: >>> >>> I don't know your project scope, but these pointers may help you to >>>> grab some features to implement: >>>> >>>> http://www.tm4.org/mev/**features <http://www.tm4.org/mev/features> >>>> >>>> Also take a look into the Circular Genome Viewer: >>>> http://wishart.biology.**ualberta.ca/cgview/gallery.**html<http://wishart.biology.ualberta.ca/cgview/gallery.html> >>>> >>>> specially the browsable maps >>>> >>>> http://wishart.biology.**ualberta.ca/BacMap/cgview_** >>>> linked_maps/NC_003198/index.**html<http://wishart.biology.ualberta.ca/BacMap/cgview_linked_maps/NC_003198/inde…> >>>> >>>> check out the Expand+ and Rotate+ operations >>>> >>>> Other very nice engine is Circos >>>> >>>> http://circos.ca/ >>>> >>>> which contains plots that has been published in Science, Nature and >>>> PLOS. >>>> >>>> Cheers, >>>> >>>> HernÃ¡n >>>> >>>> >>>> On 25/09/2012 11:48, Vanessa PeÃ±a Araya wrote: >>>> >>>>> Hello! >>>>> As you probably know, Roassal was presented at ESUG. We received a lot >>>>> of positive feedback from you and also a lot of request for features. >>>>> Thank you very much! >>>>> >>>>> We want to start working on this, but also prioritize what seems to be >>>>> more urgent. >>>>> For this, we would like to survey the community about >>>>> 1 - what are the features you would like to see in Roassal. Please, >>>>> provide a list of features requests and tell us about their priority >>>>> 2 - scenarios where you would like to use Roassal. >>>>> >>>>> Thank you very much, >>>>> Vanessa. >>>>> >>>>> >>>>> >>> >> >> >> > >

Sept. 26, 2012

[Pharo-project] vm download site

by Camillo Bruni

http://pharo.gforge.inria.fr/ci/vm/mac http://pharo.gforge.inria.fr/ci/vm/linux and once we fixed the win builds http://pharo.gforge.inria.fr/ci/vm/mac/win best igor + cami

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Vanessa PeÃ±a Araya

Thank you, Ben. And yes, this is the kind of things that are very useful. > 3. Electrical Software Development Platform - CRITICAL priority > Of course, my own project to complete my masters within the next > couple of months!! This is implementing a model browser for the IEC > 61970 Common Information Model. I showed this to Alex a while ago and > am just now getting back to the point I was at before switching from > Mondrian to Roassal. While this has taken a while I am very happy > with the additional control I have with Roassal (and a lot of this > time has been too many demands by my day job). Perhaps a rough early > release is not too far away. I'm sorry but I don't know this, so I don't understand really. Is there some place I can see it? As yes, the features you mentioned are interesting. You are not the first to mention features 4, for example. Thank you very much :) Vanessa. > > Alexandre Bergel wrote: >> This is not that we do not have ideas :-) >> >> Our todo list includes: >> - book chapter on Roassal >> - exporters (e.g., HTML, SVG, JavaScript) >> - semantic zooming >> - way to compose shapes >> - scalability >> >> We obtained this list from our personal needs and the need of the >> Moose and VW communities. >> >> Vanessa is working on a proposal for ESUG to help us on the >> development of Roassal. We are therefore surveying the Pharo >> community in case of there is a wished feature that we did not see or >> did not put high on our todolist. We are currently maintaining >> Roassal (i.e., fixing bugs) and pursuing our innovation effort (i.e., >> implementing cool ideas). The ESUG support will help us increase our >> productivity. >> >> And yes, we would love to see someone use Roassal to visualize >> genome, DNA and other biological data. We are ready to provide a >> strong support. >> >> Cheers, >> Alexandre >> >> >> On Sep 25, 2012, at 12:33 PM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >> >>> I don't know your project scope, but these pointers may help you to >>> grab some features to implement: >>> >>> http://www.tm4.org/mev/features >>> >>> Also take a look into the Circular Genome Viewer: >>> http://wishart.biology.ualberta.ca/cgview/gallery.html >>> >>> specially the browsable maps >>> >>> http://wishart.biology.ualberta.ca/BacMap/cgview_linked_maps/NC_003198/inde… >>> >>> >>> check out the Expand+ and Rotate+ operations >>> >>> Other very nice engine is Circos >>> >>> http://circos.ca/ >>> >>> which contains plots that has been published in Science, Nature and >>> PLOS. >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> >>> On 25/09/2012 11:48, Vanessa PeÃ±a Araya wrote: >>>> Hello! >>>> As you probably know, Roassal was presented at ESUG. We received a lot >>>> of positive feedback from you and also a lot of request for features. >>>> Thank you very much! >>>> >>>> We want to start working on this, but also prioritize what seems to be >>>> more urgent. >>>> For this, we would like to survey the community about >>>> 1 - what are the features you would like to see in Roassal. Please, >>>> provide a list of features requests and tell us about their priority >>>> 2 - scenarios where you would like to use Roassal. >>>> >>>> Thank you very much, >>>> Vanessa. >>>> >>>> >> > > >

Sept. 26, 2012