July 2017 - Pharo-users - lists.pharo.org

Job for Spec & Roassal?
by David Epstein July 30, 2017

July 30, 2017

Hello, I've been reading over the documentation and want to try my first project with Pharo. The project will begin as a simple diagramming program for making logic models<http://ctb.ku.edu/en/table-of-contents/overview/models-for-community-health…>. Are there any similar projects or demos I should look at? As I progress with Pharo, I intend for the diagram elements to carry a lot of built-in functionality and data for program evaluation. Would I build the interface with Spec and the diagramming elements with Roassal? So, clicking a Spec button would create a Roassal object? -david

1 0

NeoCSV on Irregular Files
by Sean P. DeNigris July 30, 2017

July 30, 2017

I have a CSV file that has several subsections, each with its own format. What I'd like to do is parse one, reset the NeoCSVReader, set it up for the next section, and continue. I didn't see an API for this. Is it possible? Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/NeoCSV-on-Irregular-Files-tp4956850.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

3 4

Adaptable Tree-Based Cherry-Pick Tool
by Sean P. DeNigris July 30, 2017

July 30, 2017

Do we have something like a merge UI that can be used on an underlying model that may have nothing to do with VCS? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Adaptable-Tree-Based-Cherry-Pick-Tool-tp4957766.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

1 0

Iceberg needs to gracefully revert to readonly
by Herby VojÄÃk July 29, 2017

July 29, 2017

Hello! IMNSHO, now that Iceberg has three vendor-specific protocol (and before as well, because of people like me who do not have github account), Iceberg needs to gracefully revert to readonly access in case credentials are not present or do not allow full access to repository. This is primarily for dependencies of Configurations and Baselines. If any of them is github://, bitbucket:// or gitlab:// and the user happens not to have account on those systems, he will get LGit ssh credential error. Thoughts? ETA? Herby

2 2

How to calculate someone's age elegantly? Does Duration work?
by Tim Mackinnon July 28, 2017

July 28, 2017

Hi - I just ran a great MobProgramming session with Smalltalk for the XProLo group - and there was lots of great feedback and questions, however one of them really got me thinkingâ¦ We did a little exercise to create a Person class with name, dob - and then we TDDâd an age methodâ¦ which seems simple on the surface but it gets to an interesting point - what about leap years? How old is someone on those years? I thought that our plethora of Date/Duration classes might handle this - but I couldnât spot something obvious and was wondering if someone had a neat answer. Essentially if you try: age ^Date today - self dob You get a Duration, But there isnât : ^(Date today - self dob) asYears There is is asDay ^(Date today - self dob) asDays But then can you really ^(Date today - self dob) asDays / 365) truncated But what about leap yearsâ¦ so ^(Date today - self dob) asDays / 365.25) truncated It all feels a bit inelegant and I suspect there is a better Smalltalk way that is eluding me? Any suggestions? Tim

6 17

BaselineOfXxx equivalent of npm's devDependencies
by Herby VojÄÃk July 28, 2017

July 28, 2017

Hello! I'd like to ask what is the equivalent of devDependencies (dependencies to be loaded only when developing, but not when in profuction / used as a dependency) of a baseline. My baseline method looks like: baseline: spec <baseline> spec for: #common do: [ spec package: 'Towergame' with: [ spec requires: 'GarageGlorp'; requires: 'NeoJSON' ]. spec project: 'GarageGlorp' with: [ spec className: 'ConfigurationOfGarageGlorp'; version: #stable; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]. spec project: 'NeoJSON' with: [ spec className: 'ConfigurationOfNeoJSON'; version: #stable; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]. spec baseline: 'Mocketry' with: [ spec repository: 'github://dionisiydk/Mocketry:v4.0.x' ] ] and I want to have Mocketry as dev-only dependency. How to write it and how to load it with dev / without dev dependencies? Atm I load it this way: Metacello new baseline: 'Towergame'; repository: 'gitlocal:///', (hereRef / 'src') fullName; load. where hereRef is file reference to project dir. Thanks, Herby

3 4

[ANN] Mustache moved to github
by Norbert Hartl July 28, 2017

July 28, 2017

In the spirit of git notificationâ¦I moved mustache to github. https://github.com/noha/mustache <https://github.com/noha/mustache> Enjoy! Norbert

1 0

Shameful advertisement
by Serge Stinckwich July 28, 2017

July 28, 2017

Hi all, I was talking about Twitter in my previous email. This is a nice way to advertise the work of the community to others communities. Now some **shameful advertisement** : you can subscribe to my Twitter account here: https://twitter.com/SergeStinckwich I try my best to publish info about Pharo/Smalltalk community and with my 1733 followers I can have some impact sometimes. Please send me a private email if you want to advertise something specific about your work. They are other interesting accounts to follow: - PharoProject: https://twitter.com/pharoproject - PharoJS: https://twitter.com/pharojs â- StÃ©phane Ducasse: https://twitter.com/stephaneducasse - Tudor Girba : https://twitter.com/girba â- ObjectProfile : https://twitter.com/ObjectProfile âand many others !â âRegards,â -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

Beyond Live Coding
by Jimmie Houchin July 27, 2017

July 27, 2017

Pharo (Smalltalk) is much more than simply live coding. All of us here dearly love live coding. Kilon states it is possible to do live coding in other languages. I have no experience doing so in any other language. I will say that I know of no other language that it is integral to development in that language. Pharo is a live object environment. It has objects that would take someone with a better understanding of the entire image than myself to tell when the object was created. But suffice it to say that Pharo (Smalltalk) have some very old objects, possibly back to 1980 or 1972? The live environment supports live objects, not just live coding as understood by someone who may attempt live coding in some language that does not by nature do live coding. Objects have state and behavior. Objects in Pharo grow and shrink in behavior and state as messages are sent to them. They evolve, they dynamic not static. Pharo's environment can survive crashes. Yes, I know, there are times when some unrecoverable event happens and you can not recover lost changes. But the community attempts to fix anything that would cause such an event. Other languages, do not have such. Segfaulting is normal, to be expected. You go back to your dead code editor and fix what caused the segfault and start up again, clean without the state your objects were in when it happened or even before. They do autopsies on their core dumps to attempt to discover what went wrong. Yes, you can explicitly choose to run a debugger on your app to watch its state and behavior. Pharo's environment survives shutdown of its environment and shutdown or restart of an operating system. Once restarted your Pharo environment is exactly as it was with all it's live objects and live code. It survives change of operating systems and computers. All the image needs is the appropriate vm for the image and the operating system currently running. Pharo can survive stupid programmer errors. I have written infinite loops and lived to tell about it. My objects and environment survived. I have written code which took hours to execute over a large set of data only to discover I had an error in my code on the last method or so that executed and it raised a debugger. I fixed it and continued. Nice. In some other language, you fix and start over executing that multiple hour process and hope there are no more errors. I know of no other language that facilitates this behavior. The editing of the code is in a different environment from the execution of the code. The state of the objects in the executing code disappears when the code ceasing execution whether by choice or error. And yes, some of that is and can be mitigated by files and databases. Live debugging of code is by executing an application (debugger) on the application you want to debug. This all by nature is static and dead. Only to discover problems in my fixed in time code and objects. You can't fix the debugger while debugger some program. I don't know that you necessarily fix the program outside of discover of where to fix it in the separate editing process. Then you start all over again. Even if you can overcome ever single one of my perceived technical difficulties. And I may be in error. I do not program in those environments and have little experience there. One thing that is indisputable at least to my understanding is this. Whatever language you may overcome all of this in, you are quite possibly doing it alone or at best in very small groups. There is no community or cultural support. Pharo has a community, a culture which supports the artifact which provides this live object environment. This is of tremendous value. Pharo has a culture which supports live objects and live coding. It has a culture that says your stupid code should not crash the environment. If it does, we need to fix it. Pharo is not perfect. Its community is not perfect. But I have not found anything or place better. So I am learning C, and dead programming hopefully sufficiently enough that I can bridge the gap where Pharo does it well or where Pharo could use a little outside help. But I still get to live in my nice live object environment. I have nothing against other languages. I would love it if there were other languages which had this ability and culture. But I don't find them anywhere. I have programmed in Python, Lua, played with PicoLisp. Pharo is home. :) And to top it all off, Stef's Pharo 7 and 8 roadmap looks pretty sweet. I just wanted to say that Pharo (Smalltalk) is so much more than what I perceive other languages understanding of live coding to be. And that I know of no other language or community which approaches what is done by nature in Pharo (Smalltalk). All the above is my naive opinion. Do with it as you will. Have a great day! Jimmie

3 5

Documentation
by Jimmie Houchin July 27, 2017

July 27, 2017

I am looking at participating in the documentation if that is a good area to plug in. I do not necessarily have the expertise on the subjects, but I can bring fresh eyes and the eyes of a native English speaker. What is the best way to assist? For example I am currently reading the Booklet-uFFI. I have some questions and suggestions. How or to whom do I communicate these? If I modify the UnifiedFFI.pillar file, do I do the normal GitHub pull requests? Or is this process handled via Iceberg? Do I edit them manually in a normal text editor or is there a preferred way within Pharo. Is this process documented somewhere? Or do I need to document it? :) And what about similar for the MOOC? Any guidance or suggestions, and suggestions where you would like help the most are greatly appreciated. Thanks. Jimmie

4 4