Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

On Thu, Oct 26, 2017 at 12:00 AM, henry wrote: > I disabled vatId authorization in version 3, located in > SessionOperations>>processIWant > | SessionOperations>>processIAm:. > > I was asked to disseminate my news to Pharo Users, hello there. I was > asked to describe

Re: [Pharo-users] [ANN] Grafoscopio is now also an indexedpublication

Thanks Andrew. I'm glad to know that Grafoscopio has been useful to you and to meet new users. I'll be waiting for your release and to learn from it. Those use cases where the tool itself is changed are really valuable and worthy to me. Cheers, Offray El 28 de octubre de 2017 10:37:01

Re: [Pharo-users] [ANN] Iceberg 0.6.2 backported to Pharo 6.1

Thanks. I did not yet try if I can use it for push, but it's great already as I could remove all the workarounds I needed before to work with the local repo. Herby Esteban Lorenzano wrote: Hi, I backported lastest Iceberg version to Pharo 6.1 to allow people to benefit for latest

[Pharo-users] [ANN] OpenSSL wrapper

Hi all, I've put up the _beginnings_ of a wrapper for OpenSSL on STH: Metacello new baseline: 'OpenSSL'; smalltalkhubUser: 'PierceNg' project: 'OpenSSL-Pharo'; load. Verified on Pharo 6 32- and 64-bit. My near term goal is to wrap enough libcrypto functionality to implement the

Re: [Pharo-users] Actual Code to Improve the Pharo environment

I’m not working on that specifically, although what I am working on could definitely use that and vice versa, which would increase the capabilities of each. One thing I’m working on is using Vert.x for service registration and discovery, mapped to Apache River (JINI) to propagate that over

Re: [Pharo-users] [ANN] Grafoscopio is now also an indexedpublication

Btw, thank you personally. In another project I’ve started to use both Grafoscopio itself (from a developer perspective) but also programmatically to improve that project. Hopefully I’ll be able to release that project soon (i.e. in the next couple of weeks) and you’ll be able to see how

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

Does that mean the sets/bdd would be constructed mainly at comile time? Anyway, Andrew, feel free to contact me, I might help you with this. Best, Steffen Am .10.2017, 16:05 Uhr, schrieb Stephane Ducasse : I think that andrew would like to improve smacc when

Re: [Pharo-users] Linear solvers

On 10/28/2017 04:23 PM, Ben Coman wrote: > btw, what does PolyMath/SciSmalltalk offer in the way of linear solvers? Hi Ben, so far no linear solvers in PolyMath. i made a small constraint solver for PolyMath that is not restricted to linear problems, hence necessarily slower than linear solvers &

Re: [Pharo-users] Linear solvers

thx for the tip. cheers -ben On Sat, Oct 28, 2017 at 11:47 PM, werner kassens wrote: > On 10/28/2017 04:23 PM, Ben Coman wrote: > > btw, what does PolyMath/SciSmalltalk offer in the way of linear solvers? > Hi Ben, > so far no linear solvers in PolyMath. i made a small

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

Part of the reasoning is that by writing JVM bytecode, the differences between the various JVM languages become largely irrelevant, though in some ways it becomes slightly less convenient if calling, for example, Scala or Clojure code from Pharo. The other is inherent JVM limitations and

Re: [Pharo-users] perspective request for those earning a living fromSmalltalk

Thank you , Andrew, for that back-story! I really liked OS/2 and was extremely reluctant to give it up; it had a really good design. On Sat, Oct 28, 2017 at 10:59 AM, Andrew Glynn wrote: > Your history is accurate, but there’s a few things I’d like to add, due > to having

Re: [Pharo-users] Smalltalk Argument

I will, although in some ways the two may be more complementary than anything. Sent from Mail for Windows 10 From: Stephane Ducasse Sent: Saturday, October 28, 2017 5:06 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Smalltalk Argument Hi andrew you should contact

Re: [Pharo-users] Netstyle/Workflow Package discovery - (was: Business process (declaration and orchestration), ontology/taxonomy)

ok for now publish your changes on smalltalkhub somewhere so that they do not stay on your machine. On Sat, Oct 28, 2017 at 7:52 AM, Cédrick Béler wrote: > >> >> Did you send pull requests? > > Euh, actually I still don’t really know how to use git. > > I loaded it through

Re: [Pharo-users] Actual Code to Improve the Pharo environment

Writing that kind of code is another of the reasons I decided I don’t want to work in anything else . Maybe more important than some of the others, both to myself and to other users. I’ve gained so much personally, mostly for nothing, even just considering the relatively few projects I have

[Pharo-users] Read-only images / how to deploy new image as fast as possible?

Hi, I came to the phase where I actually deploy the small backend written in Pharo, and I wonder about two things: 1. Is it possible to make .image / .changes read-only? Will Pharo just work (not writing the image, but that is not needed, all data are in sqlite file)? 2. How to

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

I see. What is the task in detail? Are some of the set fixed or known in advance? What's the argument against a bitset-based solution? Cheers, Steffen Am 27. Oktober 2017 19:10:35 MESZ schrieb Stephane Ducasse : >It was for test inclusion of UTF-8 characters so we do

Re: [Pharo-users] Read-only images / how to deploy new image as fast as possible?

Hi Herby - for #1, yes you can do that (I do this in PharoLambda) - there was a snippet from Sven on how to do it (you need to override 2 classes I seem to recall) , if you search in the archives you should find it. I'm not near a computer to give you the exact bit - but if you can't find it

[Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

Hi, I had to find out how to automatically deploy the backend written in Pharo, and so far it uses docker-compose stop to stop the instance (and later docker-compose up -d to get everything up again). I noticed the stop phase takes a while and ends with status code 137. I presume it ended

Re: [Pharo-users] Actual Code to Improve the Pharo environment

Hi Andrew, Are you working to bring a Capabilities model to Pharo? This is precisely what I am working to bring with Hubbub, running on top of my ParrotTalk. I derived these from erights.org's ELib and have been working on them for many years. Now that ParrotTalk has stabilized (layer 5) I am

Re: [Pharo-users] Smalltalk Argument

I looked and was not able to find it. Which version of Pharo are we talking about? What is the name of the kafka integration? - HH > Original Message > Subject: RE: [Pharo-users] Smalltalk Argument > Local Time: October 27, 2017 11:10 PM > UTC Time: October 28, 2017 3:10 AM >

Re: [Pharo-users] Binary Decision Diagram Package in Smalltalk

I think that andrew would like to improve smacc when parsing inputs containing utf-8 characters. On Sat, Oct 28, 2017 at 1:46 PM, Steffen Märcker wrote: > I see. What is the task in detail? Are some of the set fixed or known in > advance? What's the argument against a

Re: [Pharo-users] Smalltalk Argument

I referred to a Lambda Architecture, not the availability of Lambdas in the language. Pharo has the best with BlockClosures. - HH > Original Message > Subject: RE: [Pharo-users] Smalltalk Argument > Local Time: October 27, 2017 11:10 PM > UTC Time: October 28, 2017 3:10 AM >

Re: [Pharo-users] Smalltalk Argument

I used Kafka as was illustrated in the image, as a durable event source for BigData to RDB, Hadoop and other facilities. Our Kafka consumers were writing into Hadoop and had no concept of map/reduce. I agree that if we had a map/reduce feature then Pharo could operate against HDB and Hadoop in

Re: [Pharo-users] Netstyle/Workflow Package discovery - (was: Business process (declaration and orchestration), ontology/taxonomy)

Hi I do not see why these classes would be mandatory for a workflow. There seems to be left over from the extraction. stef On Sat, Oct 28, 2017 at 12:11 PM, Cédrick Béler wrote: > >> ok for now publish your changes on smalltalkhub somewhere so that they >> do not stay on

[Pharo-users] Linear solvers

While reading around on Cassowary for constraint based UI, I noticed the original author and others expanded their work to a more general linear solver system Balsberg. Maybe something useful to many business, so just thought I'd drop some links... * Solving Interactive Logic Puzzles With

Re: [Pharo-users] [ANN] Grafoscopio is now also an indexed publication

well done. On Sat, Oct 28, 2017 at 12:58 AM, Offray Vladimir Luna Cárdenas wrote: > Hi, > > I would like to share with you the recent acceptation of Grafoscopio in the > Journal of Open Source Software (JOSS), which makes it also an indexed > publication. More details

Re: [Pharo-users] [ANN] Grafoscopio is now also an indexed publication

Thanks Stephan, As told many times. This community has been really empowering to prototype the artifacts for my PhD (which is *not* in software [1]). Is good to count with such proactive and helpful community. [1] http://www.doctoradoendiseno.com/en This learning process is just starting.

Re: [Pharo-users] Smalltalk Argument

Hi andrew you should contact esteban because he is writing an objective-C bridge. Stef On Sat, Oct 28, 2017 at 2:30 AM, Andrew Glynn wrote: > One thing I’m working on is a bridge between Pharo and F-Script. F-Script > is, basically, a Smalltalk dialect, as is obvious from

Re: [Pharo-users] [Pharo-dev] [ANN] Iceberg 0.6.2 backported to Pharo 6.1

Great work! Doru > On Oct 27, 2017, at 11:36 AM, Esteban Lorenzano wrote: > > Hi, > > I backported lastest Iceberg version to Pharo 6.1 to allow people to benefit > for latest changes. > This version has an important amount of tweak and fixes, but most important > is

Re: [Pharo-users] Smalltalk Argument

On Sat, Oct 28, 2017 at 6:10 AM Andrew Glynn wrote: > Web dev is a messy field. Not because it has grown too fast, but because > it was designed by amateurs, developed by amateurs, and continues to be so, > while depending on an underlying expertly designed system, the