- Pharo-users - lists.pharo.org

Re: [Pharo-users] [gsoc-mentors] GSoC: call for ideas

by Usman Bhatti

[Anne Etien could not post this msg on the mentors list I m forwarding it on her behalf]. Title: FAST JavaScript model Level: advanced Possible mentor: Anne Etien Possible second mentor: Nicolas Anquetil or Yuriy Tymchuk Description: For in depth source code analysis a support of abstract syntax trees is required. FAST is an abstract syntax tree extension for FAMIX meta-model that is used by Moose technology. The goal of this project is to create a JavaScript version of FAST. Technical Details: As programming languages are different, their AST representations are different too. FAST model aims for creation of as generic as possible core that can be extended for different languages. Also the structure of a model allows creation of generic algorithms like symbol resolution, metrics calculation and rule checking that will work for any language. Prototypes of FAST for Smalltalk and Java are already implemented. During the project a student will implement the JavaScript model. More detailed information about FAST is provided in the Moose day presentation: http://youtu.be/dRr3WHOD3x4 Benefits to the Student: The student will gain a deep understanding of a JavaScript syntax and abstract syntax tree model. He will also learn about PetitParser framework, and gain knowledge about software modeling and analysis. Benefits to the Community: Community will get a FAST model for JavaScript that can be used for software assessment with Moose. Also this model can be used later in PhD projects such as automation of source code translation. With this third model, the community will have raw material to real think and improve generic algorithms based on AST. On Tue, Feb 11, 2014 at 10:42 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > Hi fellow Pharo hackers, > > ESUG, the European Smalltalk User Group, is applying for this > year's Google Summer of Code. As you probably know, the Summer > of Code provides the opportunity to fund students to work during > the summer on Pharo. Please reply to this > email (be sure to use "Reply to all") if you have ideas you > would like to propose. > > Please include a summary of the project and links to web pages > that can help prospective students to write their application. > Please also include the following information: > > - if applicable, other dialects that you would be willing to > mentor this project for > > - the skill level > > - name of the mentor(s), email addresses, and possibly any IRC > network/channel/nickname where they can be found. > > Thanks for contributing to ESUG's Summer of Code application! > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- > You received this message because you are subscribed to the Google Groups > "Smalltalk GSoC mentors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to smalltalk-gsoc-mentors+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. >

Feb. 13, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Johan Fabry

Ben and I focused on getting a readable text out there that is useful for people wanting to use Spec. Personally, having experience with writing lots of English, I'm actually quite happy with how it turned out and I think the text is quite readable. This being said, we are nonnative English speakers (and writers) and I am sure that there are worse sentences than this one in the text. I don't think this one is bad at all, actually. If a decision is made by the people coordinating the PFTE book to appoint an editor, I'm sure Ben and I will be happy to cooperate. On Feb 13, 2014, at 9:42 AM, Robert Shiplett <grshiplett(a)gmail.com> wrote: > " > Creating a specific UI always starts with the subclassing of ""ComposableModel"". > " > > The above is passive with 2 gerunds. > No experienced tech editor should let that pass as an English instruction for an action or task to be performed by a reader - ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 13, 2014

Twitter Streaming API for Pharo

by Arturo Zambrano

Just fixing the subject of my post, sorry for the ambiguous previous one. On Thu, Feb 13, 2014 at 11:00 AM, Arturo Zambrano <arturo.zambrano(a)gmail.com > wrote: > Hi All, > we are playing with Roassal for the visualization of Twitter data. > So far we used Zn-SSO to connect to twitter and call REST API to > get some tweets for playing. > > Now, we would like to use the streaming API. I could not figure out how to > do this with Zn-*. > > According to Twitter Streaming API docs: > Some HTTP client libraries only return the response body after the > connection has been closed by the server. These clients will not work for > accessing the Streaming API. You must use an HTTP client that will return > response data incrementally > > I would like to know if Zn allows to get data incrementally. Furthermore > it would be great to know if there is some example where I can start from. > > > Once we have our toy working we plan to release it to the community. > > thanks. > > art > > > > >

Feb. 13, 2014

Re: [Pharo-users] Streaming API for Pharo?

by Sean P. DeNigris

Arturo Zambrano wrote > I would like to know if Zn allows to get data incrementally The Nabble mirror (http://forum.world.st/Pharo-f1294836.html will check both dev and user lists) has a great search feature. "Zinc stream" returned some interesting results... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Streaming-API-for-Pharo-tp4743273p4743294.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 13, 2014

Streaming API for Pharo?

by Arturo Zambrano

Hi All, we are playing with Roassal for the visualization of Twitter data. So far we used Zn-SSO to connect to twitter and call REST API to get some tweets for playing. Now, we would like to use the streaming API. I could not figure out how to do this with Zn-*. According to Twitter Streaming API docs: Some HTTP client libraries only return the response body after the connection has been closed by the server. These clients will not work for accessing the Streaming API. You must use an HTTP client that will return response data incrementally I would like to know if Zn allows to get data incrementally. Furthermore it would be great to know if there is some example where I can start from. Once we have our toy working we plan to release it to the community. thanks. art

Feb. 13, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Thomas Worthington

On Thu, 13 Feb 2014 12:42:59 -0000, Robert Shiplett <grshiplett(a)gmail.com> wrote: > " > Creating a specific UI always starts with the subclassing of > ""ComposableModel"". > " > > The above is passive with 2 gerunds. But is perfectly good and clear English nonetheless.

Feb. 13, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Robert Shiplett

humour: license to practice English humor note; 'subclass' may be a verb at wiktionary.org but not in current standard English (e.g. m-w.org or 2002 10th Ed, hardcover Merriam-Webster) ... so word is being used as a technical term in 2014 ... life was easier when a verb had one spelling and a noun another ... but 200+ yrs ago that divide was replaced by the Atlantic Ocean ... never-to-be : verb: subKlass noun: Subclass ... idull-y dreemin off eeleKterik-sheep inn ah nukular aedj On 12 February 2014 11:08, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > I am happy to announce that Ben and I finished the documentation of Spec > for the Pharo For The Enterprise book. This documentation is up-to-date > with the latest version of Spec, and is focused towards people wanting to > use it and even extend it (in contrast to the academic papers which are â¦ > academic ;-) ). I hope that this text will help all the people that are > building UIs in Pharo, and it will clear up any doubts that they may have. > > The chapter is available in source form from the GitHub project of the > PFTE book: > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english > > The easiest way to read the chapter is from the continuous integration > server, which produces a html file of the chapter here: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > (The same server also produces pdf and markdown files, but there are some > strange artifacts there, currently. I guess this will be cleared up in the > future) > > We tried our best to make it understandable and complete, but if you have > any doubts or comments please do not hesitate to let us know !! Ben prefers > Github apparently, but if you are oldskool like me you can also send a mail > (privately or to the mailing list). > > Now it's time to build some cool user interfaces! :-) > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > >

Feb. 13, 2014

Re: [Pharo-users] [ANN] Spec documentation in PFTE book finished

by Robert Shiplett

" Creating a specific UI always starts with the subclassing of ""ComposableModel"". " The above is passive with 2 gerunds. No experienced tech editor should let that pass as an English instruction for an action or task to be performed by a reader - especially if the reader may be using English as a second language or merely know English as a technical language. ALT non-passive sentence "To specify a UI, you must first declare a subclass of ComposableModel." But Smalltalkers use "subclass" as a verb, so we get "To specify a UI, you must subclass ComposableModel first." ALT How to specify a UI : First step : subclass ComposableModel ( we will declare ModelList in this class browser UI example.) Some of the Wiley "For Dummies" books offer good examples, as do some of the "Idiot's Guide" books. Some books in German offer examples only rivalled by books in Japanese. Sadly, English invites abstract constructions using Latin roots instead of simple Anglo-Saxon verbs. Japanese at least places a verb at the end of the sentence and has "ga" to distinguish true subjects from mere topics indicated by 'wa". German has the frightful practice of ending sentences with prepositions. Relatively more synthetic or analytic languages pose different challenges for technical clarity in explaining practical tasks such that an example can serve as an exemplary instance for future reference to refresh recall and to facilitate recognition. Boeing and NASA have some experience here : Apollo 13 has a reminder of the challenge of impedance mis-match and "round" meets "square"component. Note: the practical "principles" for landing light planes with power are not those for landing heavy jets with power, partly because piston engines do not "spool up" ; runway "flare" is not achieved by "Looking at how close you are to the runway" but must be learned - partly on the ambient flow of a visual gradient ... except in marginal visibility or over water or over waving tall grass ... Clear technical English is a challenge : it is not met by "knowing English" anymore than landing an airplane is achieved by knowing the names of the yoke and rudder ( and beware of rudder-less aircraft ! ) Can someone other than me volunteer as a technical editor ? It is not a matter of having the facts right or mentioning the "Gotcha's". For an MVP example, I would suggest giving the use of colour some serious thought : experiment with it. It is now used in some new bilingual dictionaries to very good effect. If you have never looked at a surgical manual for a new procedure, I would suggest doing so. Ask a spouse about the most useless instruction manual for the DIY project that refused to assemble. The writer of the latter also "knew" enough English to write the instructions. No offense intended WHATSOEVER and I hope none taken by anyone. As Marcus may recall, I now have more difficulties typing at a keyboard and even in the short term I may become less helpful and less useful. Perhaps there is a tool for blue-pen and red-pen : PDF annotations ? There should be a Smalltalk UI for editing text in tX ... ;-) R Canada PS For some readers, MVP can be no more obvious than MVC ; believing in MVP as being more obvious could impede presentation. MVC was a stumbling block for many learning to build UI's in various Smalltalk dialects in the past. Do you recall handing off a Smalltalk project for maintenance to someone who believed in C++ but was moved to your ST group or team ? I remember this very clearly. You can learn a lot from a dummy. I learned a bit from having taught English as a second-language to Vietnamese and to Poles that I did not learn teaching French students. A book for the "Enterprise" is surely not aimed chiefly at those of us who have enjoyed drinking the Kool-Aid ;-) On 12 February 2014 11:08, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > I am happy to announce that Ben and I finished the documentation of Spec > for the Pharo For The Enterprise book. This documentation is up-to-date > with the latest version of Spec, and is focused towards people wanting to > use it and even extend it (in contrast to the academic papers which are â¦ > academic ;-) ). I hope that this text will help all the people that are > building UIs in Pharo, and it will clear up any doubts that they may have. > > The chapter is available in source form from the GitHub project of the > PFTE book: > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english > > The easiest way to read the chapter is from the continuous integration > server, which produces a html file of the chapter here: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > (The same server also produces pdf and markdown files, but there are some > strange artifacts there, currently. I guess this will be cleared up in the > future) > > We tried our best to make it understandable and complete, but if you have > any doubts or comments please do not hesitate to let us know !! Ben prefers > Github apparently, but if you are oldskool like me you can also send a mail > (privately or to the mailing list). > > Now it's time to build some cool user interfaces! :-) > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > >

Feb. 13, 2014

Re: [Pharo-users] mathematical models

by Picci Pharo

I forgot to say that i downloaded MOOSE and Kendrick packages. Is there somebody who is currently working with this stuff? Is there any kind of tutorial? Thank you! From: prova213(a)hotmail.it To: pharo-users(a)lists.pharo.org Date: Thu, 13 Feb 2014 10:50:39 +0100 Subject: [Pharo-users] mathematical models Hi Guys! I'm going to start to teach as assistant professor of Operative Research, and i'd like to teach some stuff of Pharo. I was wondering if there are some Packages about mathematical models as Lotka-Volterra or other models about the dynamics of biological systems already implemented (with plot too). Thanks for the help.Paolo

Feb. 13, 2014

Re: [Pharo-users] Applications, features and unit tests

by Leonardo Silva

Hi Damien, By feature I mean any user-visible functionality that needs to be tested. Like you said, one feature can have many tests. The important thing for me is to know, given a unit test, what feature (high level) is going to be tested. If you name your tests putting the name of the feature as a prefix, then I can do this mapping. Leonardo On Thu, Feb 13, 2014 at 7:08 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Wed, Feb 12, 2014 at 1:17 PM, Leonardo Silva > <leonardo.humberto(a)gmail.com> wrote: > > I am looking for real applications in Smalltalk that have a mapping > between > > its features and the specific unit tests for them. > > > what is a feature for you? Because, typically, I have a feature per > test. If I need more tests, they typically share the same method name > prefix: e.g., testFeatureNameInSimpleCase, > testFeatureNameInStrangeCase1, testFeatureNameInStrangeCase2... > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Feb. 13, 2014