- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Anybody using Orca Smalltalk to JavaScript?

by Frank-B

Hello Craig, this approach just as Bert's VM in the browser is/are certainly technically very interesting projects and now comes the big "BUT": - I see absolutely no sense in this approach for real-world end-user applications - especially if their sources MUST be closely connected with existing Smalltalk code, which does not run in the client like all the data-driven model definitions etc that I already have - the Morph UI is out of any question related to what end-users expect (pardon, but end-users would regard this as a bad joke) - the esponsivness of such a solution in the browser must always be far slower than any "normal" browser UI - and it's impossible to port my >10.000 framwork and application classes to Squeak. There are several more reasons, why this would conflict with my future plans, which I do not want to disclose here. So, I see only academic reasons for this work. I do thank you for your answer. Should my view be copletely wrong, please let me know. Best regards Frank -- View this message in context: http://forum.world.st/Anybody-using-Orca-Smalltalk-to-JavaScript-tp4960519p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 14, 2017

Serializers/Encoders

by henry

I find I do not necessarily have a specific question regarding a specific implementations, but a higher-level question of feasible solution. I need substitutable, type-relevant JSON encoding, perhaps based upon JSON Schemas. I am looking at ASN1Modules & types, Fuel clusterings/substitutions and NeoJSON clusters & mappers. Is it feasible to bring all these together? I would use ASN1Types, Fuel graph walking/substitutions and NeoJSON encoding and cluster hooks. Fuel also has Clusters but I see that Fuel encodes these clusters in each encoding. I am torn about this philosophically: good to have self-describing data encoding, but not suitable for JSON, unless just a type-name extension. Lightweight & robust descriptions? Well, this is all Fuel cluster specs within the encoding really is: a type-specification. The aspect of NeoJSON that has me wondering is the lack of polymorphism in type-spec lookup and recursive substitution. This is where Fuel shines, I feel. So what is the vision of the end state encoder? Use ASN1 Types as cluster descriptors, Fuel proxification on materializations and NeoJSON encoding and mappers. Would you have for me guidances in this area? - HH

Aug. 14, 2017

Re: [Pharo-dev] Anybody using Orca Smalltalk to JavaScript?

by Stephane Ducasse

> > Oh, I'm plenty comfortable discussing it on the Pharo lists. :) I > was referring to different context in which someone asked me a question > here, and I got attacked for responding to it. I surprised about it. Because we are welcoming discussions. Now discussions around Pharo are better :) Stef

Aug. 14, 2017

Little article: keep your pharo repository in sync

by Guillermo Polito

This little article explains how you should keep your branches in sync with iceberg or (in worst-case scenario) from the command line. https://github.com/guillep/PharoIntegrationProcess/wiki/Keep-your-repo-in-s… These are the things I do all the time, if you have other cases, or you want to add anything, just tell. Guille -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 14, 2017

Re: [Pharo-dev] Fuel fails in squeak

by Stephane Ducasse

I checked and in Pharo 60 MCSmalltalkhubRepository owner: 'Pharo' project: 'Fuel' user: '' password: '' Now Fuel is by default loaded into Pharo so may be you have another scenario. Stef On Mon, Aug 14, 2017 at 7:02 PM, henry <henry(a)callistohouse.club> wrote: > I loaded the latest Fuel from squeak source and it fails when materializing > a Character from a FixedObjectCluster. Character class does not support > basicNew. > > Helpful>?? > > - HH > >

Aug. 14, 2017

Re: [Pharo-dev] Anybody using Orca Smalltalk to JavaScript?

by Craig Latta

Hi Frank-- I'm working on a different project called Caffeine[1]. It runs Pharo, Squeak, and Cuis object memories in web browsers, using the SqueakJS virtual machine. There is support for the Chrome Debugging Protocol, the A-Frame WebVR framework, and the Snowglobe remote UI framework (e.g., run Pharo in the cloud and interact with it live in a web browser), and for peer-to-peer communication and NodeJS server livecoding. The target is large-scale web deployments. The project is currently in alpha. thanks, -C [1] https://caffeine.js.org -- Craig Latta Black Page Digital Amsterdam :: San Francisco craig(a)blackpagedigital.com voice through 2017-09-12: + 1 510 833 5799 (SMS ok) +31 20 893 2796 (no SMS)

Aug. 14, 2017

Re: [Pharo-dev] Fuel fails in squeak

by henry

Alright, thank you, I will investigate. I attempted to create a SmalltalkHub account but I am unable to create a project. I am slightly overwhelmed at the fractious nature of repositories, between and within Squeak & Pharo, and also encoder serializations. I hope for reconsolidation. - HH On Mon, Aug 14, 2017 at 13:28, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Henry I do not think that Fuel is managed from SqueakSource. Fuel is central to Pharo so it should be under Pharo.. Have a look at the repo associated with the fuel package in Pharo 60 for example. Sent from a phone that is not trendy On Mon, Aug 14, 2017 at 7:02 PM, henry wrote: > I loaded the latest Fuel from squeak source and it fails when materializing > a Character from a FixedObjectCluster. Character class does not support > basicNew. > > Helpful>?? > > - HH > > @callistohouse.club>

Aug. 14, 2017

Re: [Pharo-dev] Fuel fails in squeak

by Stephane Ducasse

Hi Henry I do not think that Fuel is managed from SqueakSource. Fuel is central to Pharo so it should be under Pharo.. Have a look at the repo associated with the fuel package in Pharo 60 for example. Sent from a phone that is not trendy On Mon, Aug 14, 2017 at 7:02 PM, henry <henry(a)callistohouse.club> wrote: > I loaded the latest Fuel from squeak source and it fails when materializing > a Character from a FixedObjectCluster. Character class does not support > basicNew. > > Helpful>?? > > - HH > >

Aug. 14, 2017

Re: [Pharo-dev] [squeak-dev] Fuel fails in squeak

by H. Hirzel

According to https://travis-ci.org/theseion/Fuel the tests are fine for the release version Squeak 5.1. Could you post a code snippet which shows how it fails. If you are using Squeak 6.0a, which version do you use? --HH On 8/14/17, henry <henry(a)callistohouse.club> wrote: > I loaded the latest Fuel from squeak source and it fails when materializing > a Character from a FixedObjectCluster. Character class does not support > basicNew. > > Helpful>?? > > - HH

Aug. 14, 2017

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

by Guillermo Polito

On Mon, Aug 14, 2017 at 4:47 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Iâm definitely in favour of doing something (as I found it confusing, and > in a way also found it has the potential to leak what could be sensitive > information through command line contexts that are still lurking in the > image with details about previous directory structures and commands). > > I will try and and see how it impacts PharoLambda as a test example. > Sure, go on and play with the build artifacts in here: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > Tim > > On 14 Aug 2017, at 11:42, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi all, > > I'm proposing a kind-of critical change that I believe is very good for > the health of the system: I want that the startup of the system runs in > maximum priority and becomes non-interruptable. > > Right now, when you save your image, the shutdown and startup are run in > the same priority than the process that triggered the save (usually the ui > or the command line, priority 40). This can cause lots of problems and race > conditions: processes with higher priorities can interrupt the > shutdown/startup and try to do something while the system is unstable. As a > side effect also, when you use extensively the command line, you start > stacking startup contexts from old sessions: > > ... > session 3 ctxt 4 <- This guy makes a save and a new session starts > session 3 ctxt 3 > session 3 ctxt 2 > session 3 ctxt 1 > session 2 ctxt 4 <- This guy makes a save and a new session starts > session 2 ctxt 3 > session 2 ctxt 2 > session 2 ctxt 1 > session 1 ctxt 4 <- This guy makes a save and a new session starts > session 1 ctxt 3 > session 1 ctxt 2 > session 1 ctxt 1 > > Old contexts are never collected, and the objects they referenced neither. > > To fix these two problems I propose to do every image save/session start > in a new process in maximum priority. That way, other process should not be > able to interrupt the startup process. Moreover, every session > shutdown/startup should happen in a new clean process, to avoid the session > stacking. > > For normal users, this should have no side effect at all. This change will > have a good impact on people working on the debugger and the stack such as > fueling-out the stack because they will have a cleaner stack. > > There is however a side-effect/design point to consider: startup actions > should be quick to run. If a startup action requires to run a long-running > action such as starting a server or managing a command line action, that > should run in a separate process with lower priority (usually > userPriority). In other words, the startup action should create a new > process managing its action. > > If you want to review (and I'd be glad) > > Pull request: https://github.com/pharo-project/pharo/pull/198 > Fogbugz issue: https://pharo.fogbugz.com/f/cases/20309 > Current validation going on: https://ci.inria.fr/pharo-ci- > jenkins2/job/Test%20pending%20pull%20request%20and% > 20branch%20Pipeline/view/change-requests/job/PR-198/ > > Guille > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr/> > > > *Web:* *http://guillep.github.io* <http://guillep.github.io/> > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 14, 2017