February 2015 - Pharo-users

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Esteban Lorenzano

it depends on your definition of âstatusâ :) first version is integrated latest vm includes also SDL2 plugin. but is there as *preview*, which means a lot of work still needs to be done. cheers, Esteban > On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > > What is the state of OSWindow integration? > This release or later? > > > > 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hi, > > Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixedâ¦ we are aiming to release in April 1st. > This version will not be spur-based, that will come with the summer release. > > Cheers, > Esteban >

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Nicolai Hess

What is the state of OSWindow integration? This release or later? 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 > after February 28, and we will work on stabilisation and bug fixedâ¦ we are > aiming to release in April 1st. > This version will not be spur-based, that will come with the summer > release. > > Cheers, > Esteban >

Feb. 18, 2015

[ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Esteban Lorenzano

Hi, Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixedâ¦ we are aiming to release in April 1st. This version will not be spur-based, that will come with the summer release. Cheers, Esteban

Feb. 18, 2015

Re: [Pharo-users] What happens to saved inspectors?

by ClÃ©ment Bera

Hey, Inspectors are different between Moose and Pharo 3. Can you precise, are you using the Glamour inspector, the EyeInspector or the old Morphic inspector ? I have never seen that in Pharo. Are your titles dynamic (I mean, when the object changes, can your title change ?) ? 2015-02-18 11:35 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk>: > Hello > > > > I am using Moose 5, which is essentially Pharo 3, downloaded late December > 2014. I have a development project which mainly consists of a collection of > workspaces and inspectors (I really do intend to turn it into a properly > structured set of classes one day!). I have noticed that, whenever I save > an image with some inspectors open and then reopen the image, the title > bars of the inspectors have become red rectangles with a cross > superimposed. Often I can work out what the title should be and carry on, > but in many cases all I can do is close down the inspector and reopen it. > Is this a known problem, and is there any way to work round it? > > > > Thanks for any help > > > > Peter Kenny >

Feb. 18, 2015

What happens to saved inspectors?

by PBKResearch

Hello I am using Moose 5, which is essentially Pharo 3, downloaded late December 2014. I have a development project which mainly consists of a collection of workspaces and inspectors (I really do intend to turn it into a properly structured set of classes one day!). I have noticed that, whenever I save an image with some inspectors open and then reopen the image, the title bars of the inspectors have become red rectangles with a cross superimposed. Often I can work out what the title should be and carry on, but in many cases all I can do is close down the inspector and reopen it. Is this a known problem, and is there any way to work round it? Thanks for any help Peter Kenny

Feb. 18, 2015

Re: [Pharo-users] Small benchmark

by SergeStinckwich

Dear Andrea, thank you for your message. This is something really interesting for the sci-smalltalk project: https://github.com/SergeStinckwich/SciSmalltalk Do you mind to add your k-means code in Sci-Smalltalk distribution? Please feel free to join the sci-smalltalk for future discussions : https://groups.google.com/forum/#!forum/scismalltalk Regards, -- View this message in context: http://forum.world.st/Small-benchmark-tp4806092p4806309.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 18, 2015

Re: [Pharo-users] [Pharo-dev] GSOC 2015 Call for Ideas

by Serge Stinckwich

On Wed, Feb 18, 2015 at 11:01 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > OK, try making a proposal then, http://gsoc.pharo.org has the instructions and the current list, you probably know more about data science than I do. > >> On 18 Feb 2015, at 10:53, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >> >> I am sorry if the previous messages came off as too harsh. The Neo >> tools are perfectly fine for their intended use. >> >> What I was trying to say is that a good idea for a SoC project would >> be to develop a framework for data analysis that would be useful for >> data scientists, and in particular this would include something to >> import unstructured data more freely. Sorry Andrea. I didn't see you message because I'm not pharo-users mailing-list, only on pharo-dev. I'm also really interested to have a gsoc project to develop data analysis framework. Please let's talk together in order to discuss about a proposal. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 18, 2015

Re: [Pharo-users] GSOC 2015 Call for Ideas

by Andrea Ferretti

I am sorry, I must have misunderstood the purpose of this thread. I read "Even if you have a vague idea, you can contribute." and tried to give a couple of vague ideas. I did not really mean that I would be able or have time to mentor such a project 2015-02-18 11:01 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > OK, try making a proposal then, http://gsoc.pharo.org has the instructions and the current list, you probably know more about data science than I do. > >> On 18 Feb 2015, at 10:53, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >> >> I am sorry if the previous messages came off as too harsh. The Neo >> tools are perfectly fine for their intended use. >> >> What I was trying to say is that a good idea for a SoC project would >> be to develop a framework for data analysis that would be useful for >> data scientists, and in particular this would include something to >> import unstructured data more freely. >> >> 2015-02-18 10:39 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> Well, you are certainly free to contribute. >>> >>> Heuristic interpretation of data could be useful, but looks like an addition on top, the core library should be fast and efficient. >>> >>>> On 18 Feb 2015, at 10:35, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >>>> >>>> For an example of what I am talking about, see >>>> >>>> http://pandas.pydata.org/pandas-docs/version/0.15.2/io.html#csv-text-files >>>> >>>> I agree that this is definitely too much options, but it gets the job >>>> done for quick and dirty exploration. >>>> >>>> The fact is that working with a dump of table on your db, whose >>>> content you know, requires different tools than exploring the latest >>>> opendata that your local municipality has put online, using yet >>>> another messy format. >>>> >>>> Enterprise programmers deal more often with the former, data >>>> scientists with the latter, and I think there is room for both kind of >>>> tools >>>> >>>> 2015-02-18 10:26 GMT+01:00 Andrea Ferretti <ferrettiandrea(a)gmail.com>: >>>>> Thank you Sven. I think this should be emphasized and prominent on the >>>>> home page*. Still, libraries such as pandas are even more lenient, >>>>> doing things such as: >>>>> >>>>> - autodetecting which fields are numeric in CSV files >>>>> - allowing to fill missing data based on statistics (for instance, you >>>>> can say: where the field `age` is missing, use the average age) >>>>> >>>>> Probably there is room for something built on top of Neo >>>>> >>>>> >>>>> * by the way, I suggest that the documentation on Neo could benefit >>>>> from a reorganization. Right now, the first topic on the NeoJSON >>>>> paper introduces JSON itself. I would argue that everyone that tries >>>>> to use the library knows what JSON is already. Still, there is no >>>>> example of how to read JSON from a file in the whole document. >>>>> >>>>> 2015-02-18 10:12 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>>> >>>>>>> On 18 Feb 2015, at 09:52, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >>>>>>> >>>>>>> Also, these tasks >>>>>>> often involve consuming data from various sources, such as CSV and >>>>>>> Json files. NeoCSV and NeoJSON are still a little too rigid for the >>>>>>> task - libraries like pandas allow to just feed a csv file and try to >>>>>>> make head or tails of the content without having to define too much of >>>>>>> a schema beforehand >>>>>> >>>>>> Both NeoCSV and NeoJSON can operate in two ways, (1) without the definition of any schema's or (2) with the definition of schema's and mappings. The quick and dirty explore style is most certainly possible. >>>>>> >>>>>> 'my-data.csv' asFileReference readStreamDo: [ :in | (NeoCSVReader on: in) upToEnd ]. >>>>>> >>>>>> => an array of arrays >>>>>> >>>>>> 'my-data.json' asFileReference readStreamDo: [ :in | (NeoJSONReader on: in) next ]. >>>>>> >>>>>> => objects structured using dictionaries and arrays >>>>>> >>>>>> Sven >>>>>> >>>>>> >>>> >>> >>> >> > >

Feb. 18, 2015

Re: [Pharo-users] GSOC 2015 Call for Ideas

by Sven Van Caekenberghe

OK, try making a proposal then, http://gsoc.pharo.org has the instructions and the current list, you probably know more about data science than I do. > On 18 Feb 2015, at 10:53, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: > > I am sorry if the previous messages came off as too harsh. The Neo > tools are perfectly fine for their intended use. > > What I was trying to say is that a good idea for a SoC project would > be to develop a framework for data analysis that would be useful for > data scientists, and in particular this would include something to > import unstructured data more freely. > > 2015-02-18 10:39 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Well, you are certainly free to contribute. >> >> Heuristic interpretation of data could be useful, but looks like an addition on top, the core library should be fast and efficient. >> >>> On 18 Feb 2015, at 10:35, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >>> >>> For an example of what I am talking about, see >>> >>> http://pandas.pydata.org/pandas-docs/version/0.15.2/io.html#csv-text-files >>> >>> I agree that this is definitely too much options, but it gets the job >>> done for quick and dirty exploration. >>> >>> The fact is that working with a dump of table on your db, whose >>> content you know, requires different tools than exploring the latest >>> opendata that your local municipality has put online, using yet >>> another messy format. >>> >>> Enterprise programmers deal more often with the former, data >>> scientists with the latter, and I think there is room for both kind of >>> tools >>> >>> 2015-02-18 10:26 GMT+01:00 Andrea Ferretti <ferrettiandrea(a)gmail.com>: >>>> Thank you Sven. I think this should be emphasized and prominent on the >>>> home page*. Still, libraries such as pandas are even more lenient, >>>> doing things such as: >>>> >>>> - autodetecting which fields are numeric in CSV files >>>> - allowing to fill missing data based on statistics (for instance, you >>>> can say: where the field `age` is missing, use the average age) >>>> >>>> Probably there is room for something built on top of Neo >>>> >>>> >>>> * by the way, I suggest that the documentation on Neo could benefit >>>> from a reorganization. Right now, the first topic on the NeoJSON >>>> paper introduces JSON itself. I would argue that everyone that tries >>>> to use the library knows what JSON is already. Still, there is no >>>> example of how to read JSON from a file in the whole document. >>>> >>>> 2015-02-18 10:12 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>> >>>>>> On 18 Feb 2015, at 09:52, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >>>>>> >>>>>> Also, these tasks >>>>>> often involve consuming data from various sources, such as CSV and >>>>>> Json files. NeoCSV and NeoJSON are still a little too rigid for the >>>>>> task - libraries like pandas allow to just feed a csv file and try to >>>>>> make head or tails of the content without having to define too much of >>>>>> a schema beforehand >>>>> >>>>> Both NeoCSV and NeoJSON can operate in two ways, (1) without the definition of any schema's or (2) with the definition of schema's and mappings. The quick and dirty explore style is most certainly possible. >>>>> >>>>> 'my-data.csv' asFileReference readStreamDo: [ :in | (NeoCSVReader on: in) upToEnd ]. >>>>> >>>>> => an array of arrays >>>>> >>>>> 'my-data.json' asFileReference readStreamDo: [ :in | (NeoJSONReader on: in) next ]. >>>>> >>>>> => objects structured using dictionaries and arrays >>>>> >>>>> Sven >>>>> >>>>> >>> >> >> >

Feb. 18, 2015

Re: [Pharo-users] GSOC 2015 Call for Ideas

by Andrea Ferretti

I am sorry if the previous messages came off as too harsh. The Neo tools are perfectly fine for their intended use. What I was trying to say is that a good idea for a SoC project would be to develop a framework for data analysis that would be useful for data scientists, and in particular this would include something to import unstructured data more freely. 2015-02-18 10:39 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Well, you are certainly free to contribute. > > Heuristic interpretation of data could be useful, but looks like an addition on top, the core library should be fast and efficient. > >> On 18 Feb 2015, at 10:35, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >> >> For an example of what I am talking about, see >> >> http://pandas.pydata.org/pandas-docs/version/0.15.2/io.html#csv-text-files >> >> I agree that this is definitely too much options, but it gets the job >> done for quick and dirty exploration. >> >> The fact is that working with a dump of table on your db, whose >> content you know, requires different tools than exploring the latest >> opendata that your local municipality has put online, using yet >> another messy format. >> >> Enterprise programmers deal more often with the former, data >> scientists with the latter, and I think there is room for both kind of >> tools >> >> 2015-02-18 10:26 GMT+01:00 Andrea Ferretti <ferrettiandrea(a)gmail.com>: >>> Thank you Sven. I think this should be emphasized and prominent on the >>> home page*. Still, libraries such as pandas are even more lenient, >>> doing things such as: >>> >>> - autodetecting which fields are numeric in CSV files >>> - allowing to fill missing data based on statistics (for instance, you >>> can say: where the field `age` is missing, use the average age) >>> >>> Probably there is room for something built on top of Neo >>> >>> >>> * by the way, I suggest that the documentation on Neo could benefit >>> from a reorganization. Right now, the first topic on the NeoJSON >>> paper introduces JSON itself. I would argue that everyone that tries >>> to use the library knows what JSON is already. Still, there is no >>> example of how to read JSON from a file in the whole document. >>> >>> 2015-02-18 10:12 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> >>>>> On 18 Feb 2015, at 09:52, Andrea Ferretti <ferrettiandrea(a)gmail.com> wrote: >>>>> >>>>> Also, these tasks >>>>> often involve consuming data from various sources, such as CSV and >>>>> Json files. NeoCSV and NeoJSON are still a little too rigid for the >>>>> task - libraries like pandas allow to just feed a csv file and try to >>>>> make head or tails of the content without having to define too much of >>>>> a schema beforehand >>>> >>>> Both NeoCSV and NeoJSON can operate in two ways, (1) without the definition of any schema's or (2) with the definition of schema's and mappings. The quick and dirty explore style is most certainly possible. >>>> >>>> 'my-data.csv' asFileReference readStreamDo: [ :in | (NeoCSVReader on: in) upToEnd ]. >>>> >>>> => an array of arrays >>>> >>>> 'my-data.json' asFileReference readStreamDo: [ :in | (NeoJSONReader on: in) next ]. >>>> >>>> => objects structured using dictionaries and arrays >>>> >>>> Sven >>>> >>>> >> > >

Feb. 18, 2015