- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Roassal Survey

by Alexandre Bergel

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. 25, 2012

[Pharo-project] Transform sends to ANSI standard?

by HernÃ¡n Morales Durand

Hi folks, I am rewriting packages to be compatible or more portable between Smalltalks. Code Critics gives the following information on my packages: - #cr, #crlf, #lf, #space, #tab, #findTokens:, ... are not part of the ANSI string protocol. - #cr and #lf are not part of the ANSI stream protocol. - The ANSI standard does not support #asInteger and #asString on Object. - Some collection methods are not ANSI compatible: #pairsDo:, #collect:thenDo:, #reject:thenDo:, #detectSum:, #valuesDo:, #keysSortedSafely, #new:withAll:, etc. Does anyone have an idea on how to transform those sends to be ANSI compatible? Best regards, HernÃ¡n

Sept. 25, 2012

Re: [Pharo-project] The roadmap aka fight plan to make image control host window

by Eliot Miranda

On Sat, Sep 22, 2012 at 11:22 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > First, we need to make one thing: > > Change the VM to not call ioProcessEvents function directly, but > rather use a variable which will hold a function pointer. > Initially, when VM starts, that function pointer is NULL, and so, > "process events" is NOP. > Please don't reinvent the wheel. The Cog source has a variable inIOProcessEvents that controls this. If negative it disables inIOProcessEvents. If non-negative it prevents reentrancy, essential if one is receiving events from the OS. There's a primitive, primitiveEventProcessingControl, to flip it between the enabled and disabled states. This code has been used for years in the Newspeak system which has a full native GUI on Windows. Going your own way creates an unnecessary fork. > Then we need to implement a module which will manage host windows, > and once image tells it to create a window, > it can change the function pointer to ioProcessEvents to own function. > > This change, would allow us to temporary disable any external event > processing (like in case of callbacks). > > Second, we should move all event-related stuff to new plugin (for > instance, all definitions in sq.h > like sqInputEvent , ioSetInputSemaphore() ioGetNextEvent() etc). > > For all UI-related stuff the image should communicate with a new > plugin, while VM should get rid of all knowledge of any existence of > UI events, > like input semaphores, primitives for fetching them etc. > > Third, of course, all screen update/refresh primitives should be > deprecated, and image should use new primitives to update the contents > of host window(s). > > > -- > Best regards, > Igor Stasenko. > > -- best, Eliot

Sept. 25, 2012

Re: [Pharo-project] OSProcess ... ported to 2.0?

by Dale Henrichs

Cami, Your code seems to have conflicts with the implementation of FileSystem in Pharo-2.0 ... besides overriding a number of methods (most that I looked at involved comments) there are a couple of places where the class names have been changed ... so it looks like your wrapper code has become outdated ... Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Monday, September 24, 2012 11:23:35 PM | Subject: Re: [Pharo-project] OSProcess ... ported to 2.0? | | | On 2012-09-25, at 01:11, Dale Henrichs <dhenrich(a)vmware.com> wrote: | | > As I take yet another stab at getting the Metacello Preview running | > on Pharo2.0, I find that OSProcess is sprinkled with references to | > FileDirectory ... at least in the packages referenced by the | > configuration, so I'm wondering if a port exists for Phar0-2.0 ... | > At the moment OSProcess is a prerequisite .... | | use my compatibility layer for FileDirectory, which wraps around | FileReference: | http://smalltalkhub.com/mc/dh83/fisleg/main | | With that it should be possible to load most old code in 2.0. | There are a 4 methods or so I haven't ported yet and I should | properly isolate the package... | | > If there is an alternate mechanism for running shell commands from | > Pharo2.0, then I assume that I'll be able to use that instead ... | | currently there isn't any other option :/ |

Sept. 25, 2012

Re: [Pharo-project] OSProcess ... ported to 2.0?

by Dale Henrichs

Thanks Cami... Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Monday, September 24, 2012 11:23:35 PM | Subject: Re: [Pharo-project] OSProcess ... ported to 2.0? | | | On 2012-09-25, at 01:11, Dale Henrichs <dhenrich(a)vmware.com> wrote: | | > As I take yet another stab at getting the Metacello Preview running | > on Pharo2.0, I find that OSProcess is sprinkled with references to | > FileDirectory ... at least in the packages referenced by the | > configuration, so I'm wondering if a port exists for Phar0-2.0 ... | > At the moment OSProcess is a prerequisite .... | | use my compatibility layer for FileDirectory, which wraps around | FileReference: | http://smalltalkhub.com/mc/dh83/fisleg/main | | With that it should be possible to load most old code in 2.0. | There are a 4 methods or so I haven't ported yet and I should | properly isolate the package... | | > If there is an alternate mechanism for running shell commands from | > Pharo2.0, then I assume that I'll be able to use that instead ... | | currently there isn't any other option :/ |

Sept. 25, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 374 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 25, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 373 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 25, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 372 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 25, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 371 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 25, 2012

Re: [Pharo-project] Roassal Survey

by HernÃ¡n Morales Durand

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. 25, 2012