Re: [Pharo-users] [Ann] Workshop: IndieWeb with pocket infrastructures

[Stéphane Ducasse]

I published it on Pharo weekly
Keep pushing. I love this local first and your effort. 

s

> On 29 Aug 2020, at 02:08, Offray Vladimir Luna Cárdenas 
>  wrote:
> 
> Hi all,
> 
> Due to the confinement in the pandemic, our forms of telepresence become
> more important and many suddenly got even more immersed into an
> Oligopoly cyberspace (Zoom, Google, Facebook, Twitter, Apple, Amazon,
> Microsoft, etc) with opaque algorithms that under extractive logic
> commodify our privacy and communications, try to condition our attention
> and habits, as well as to shape our current and future behavior. But
> this is not the only way to inhabit cyberspace.
> 
> From the Grafoscopio community[1], we would like to invite you to a
> series of workshops that we are doing to make visible other ways of
> populating and building the web, aligned with the movements of
> IndieWeb[1a], from what we have called "pocket infrastructures". You can
> find more information about these topics in [2] and in particular about
> the workshops in [3] (in Spanish).
> 
> [1] https://mutabit.com/grafoscopio/en.html
> [1a] https://indieweb.org/
> [2] https://mutabit.com/repos.fossil/indieweb/
> [3]
> https://mutabit.com/repos.fossil/indieweb/doc/trunk/docs/es/index.html#talleres
> 
> 
> The second workshop will be tomorrow, Saturday, Aug. 29 from 3:15 PM to
> 7:15PM CO (GMT - 5) -- I will try to share the other workshops earlier,
> but the site in [2] will be the consolidated memory of them, for those
> who want to join us asynchronously.
> 
> We will see how IndieWeb sites help us to untangle and reweave that
> other web and how this help us to reconnect in this stranger times.
> 
> Rethinking the infrastructure is also to rethink the ways in which it
> enables and makes visible (or not) certain ways of being and acting.
> Infrastructures are embodied discourses. So thank you in advance for
> joining us in rethinking this in practice.
> 
> Of course, Pharo is behind scenes, as usual, powering this experience.
> But with these IndieWeb workshops I think we have found a sweet spot
> that puts coding in front with a practical introduction and motivation
> beyond the kind of boring "Hello World". Following a "local first"
> approach, documentation will be in Spanish, but source code[5] and
> interactive documentation will be in English to bridge our worlds :-),
> 
> [4] https://mutabit.com/offray/blog/en/entry/dumb-hello-world
> [5] https://mutabit.com/repos.fossil/brea/
> 
> 
> See you on cyberspace,
> 
> Offray
> 
> 
> 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Re: [Pharo-users] Checking baseline before publishing

[Stéphane Ducasse]

> On 28 Aug 2020, at 23:45, Jonathan van Alteren  
> wrote:
> 
> Ah yes, sorry, you're right. You do have to commit/push for that to work.
> 
> I'm interested to hear what your experience is with using #record.

My experience is that there is nothing better than what you propose. 

> 
> Kind regards,
> 
> Jonathan van Alteren
> 
> Founding Member | Object Guild B.V.
> Sustainable Software for Purpose-Driven Organizations
> 
> jvalte...@objectguild.com
> On 28 Aug 2020, 20:00 +0200, Esteban Maringolo , wrote:
>> Hi Jonathan,
>> 
>> I never thought of SmalltalkCI for that (I use Gitlab) but in essence
>> it still requires a trial and error approach (of committing the
>> Baseline and loading it afterwards to see if it works).
>> 
>> Metacello has a "record" operation that basically does a dry run of
>> the load, but I don't know if there is a way to do it using the
>> Baseline in the image instead of one in a repository.
>> 
>> Regards!
>> 
>> Esteban A. Maringolo
>> 
>> On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren
>>  wrote:
>>> 
>>> Hi Esteban,
>>> 
>>> You might want to give smalltalkCI a try: 
>>> https://github.com/hpi-swa/smalltalkCI
>>> 
>>> I've recently started using it myself, with GitLab CI and GitHub Actions, 
>>> but one of the cool things is that you can use it to test your build 
>>> locally.
>>> 
>>> For example, create a .smalltalk.ston file for your project which loads the 
>>> baseline that you want to test, like this:
>>> 
>>> SmalltalkCISpec {
>>> #loading : [
>>> SCIMetacelloLoadSpec {
>>> #baseline : 'MyProject',
>>> #directory : 'source',
>>> #load : [ 'default' ],
>>> #onWarningLog : true,
>>> #platforms : [ #pharo ]
>>> }
>>> ],
>>> #testing : {
>>> #categories : [ 'MyProject-Tests' ]
>>> }
>>> }
>>> 
>>> Then clone the smalltalkCI repo locally and open a terminal on its 
>>> location, for example /Users/johndoe/git/smalltalkCI. You can then simply 
>>> use smalltalkCI to build a Pharo image of your baseline, which effectively 
>>> tests the correct working of your baseline:
>>> 
>>> bin/smalltalkci -s "Pharo64-8.0" 
>>> /Users/johndoe/git/MyProject/.smalltalk.ston
>>> 
>>> By default, it will run all tests in the image, but you can change the list 
>>> of tests being run by modifying the .smalltalk.ston file accordingly (see 
>>> https://github.com/hpi-swa/smalltalkCI#testcase-selection).
>>> 
>>> Hope this helps!
>>> 
>>> Kind regards,
>>> 
>>> Jonathan van Alteren
>>> 
>>> Founding Member | Object Guild B.V.
>>> Sustainable Software for Purpose-Driven Organizations
>>> 
>>> jvalte...@objectguild.com
>>> On 27 Aug 2020, 04:12 +0200, Esteban Maringolo , 
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> How can I check that my baseline works without having to publish
>>> everything, check that it fails and then going to the origin, fixing,
>>> etc?
>>> 
>>> I might be particularly idiot to always miss something, I usually have
>>> to try at least four times (in a blank image) that my Baseline,
>>> dependencies, etc. works as expected.
>>> 
>>> There must be some other way.
>>> 
>>> Esteban A. Maringolo
>>> 
>> 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Re: [Pharo-users] Getting rid of .sources file for deployment

[Stéphane Ducasse]

Hi 

I’m really interested in this. 
Because we should be able to ship without the sources. 
 FFI needs the source at some point but I guess that this is the first time
and that the information could be stored in the compiledMethod. 
But I do not remember. 

Now may be esteban or pablo can give you some hints 
but frankly we are super super super busy 
but if you have a way and that Pharo should be changed to support this scenario 
let
us know we will support you. 

S

> On 29 Aug 2020, at 04:49, Esteban Maringolo  wrote:
> 
> Hi,
> 
> Is there a way to get rid the .sources file in a deployment scenario?
> 
> I followed this guide [1], but I cannot get rid of the .sources files,
> because I'm using PharoADO (which uses PharoCOM) and it uses some
> reflection for FFI and for some reason that implies using the .sources
> file. I installed the FFICompilerPlugin as per the instructions, but I
> don't have a way to tell whether I did in the right place/moment, nor
> how to assess its proper installation.
> 
> If such [2] .sources file cannot be removed, what is the criteria for
> the lookup, can it be renamed or modified via some parameter/config?
> 
> Thanks!
> 
> [1] 
> https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/DeployYourPharoApplication.md#sources-obfuscation
> [2] Pharo8.0-32bit-0932da8.sources in my case
> 
> 
> Esteban A. Maringolo
> 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Re: [Pharo-users] Pharo at JPL

[Stéphane Ducasse]

> On 29 Aug 2020, at 01:46, tbrunz  wrote:
> 
> Thanks!  
> 
> And I want to give special thanks to Stef and to Alexandre Bergel for being
> generous with their time in helping me with my advocacy.
> 
> It's just as you said, Offray: "We live in an attention economy" -- and the
> competition is *fierce*!  

Yes this is what many smalltalking people forgot. Pharo is in competition 
against
many large languages and we are not concerned with the little fight about other 
dead smalltalk compatibilities. 

> 
> (I think it's worse when you're dealing with educated professionals -- they
> work hard, they play hard, and there's little left over to "learn something
> new" sometimes.  But I am not discouraged... I take the long view on this. 
> Computers taught me patience.  I'm using that now...  ;^)
> 
> -t
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

[Pharo-users] Getting rid of .sources file for deployment

[Esteban Maringolo]

Hi,

Is there a way to get rid the .sources file in a deployment scenario?

I followed this guide [1], but I cannot get rid of the .sources files,
because I'm using PharoADO (which uses PharoCOM) and it uses some
reflection for FFI and for some reason that implies using the .sources
file. I installed the FFICompilerPlugin as per the instructions, but I
don't have a way to tell whether I did in the right place/moment, nor
how to assess its proper installation.

If such [2] .sources file cannot be removed, what is the criteria for
the lookup, can it be renamed or modified via some parameter/config?

Thanks!

[1] 
https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/DeployYourPharoApplication.md#sources-obfuscation
[2] Pharo8.0-32bit-0932da8.sources in my case


Esteban A. Maringolo

[Pharo-users] [Ann] Workshop: IndieWeb with pocket infrastructures

[Offray Vladimir Luna Cárdenas]

Hi all,

Due to the confinement in the pandemic, our forms of telepresence become
more important and many suddenly got even more immersed into an
Oligopoly cyberspace (Zoom, Google, Facebook, Twitter, Apple, Amazon,
Microsoft, etc) with opaque algorithms that under extractive logic
commodify our privacy and communications, try to condition our attention
and habits, as well as to shape our current and future behavior. But
this is not the only way to inhabit cyberspace.

From the Grafoscopio community[1], we would like to invite you to a
series of workshops that we are doing to make visible other ways of
populating and building the web, aligned with the movements of
IndieWeb[1a], from what we have called "pocket infrastructures". You can
find more information about these topics in [2] and in particular about
the workshops in [3] (in Spanish).

[1] https://mutabit.com/grafoscopio/en.html
[1a] https://indieweb.org/
[2] https://mutabit.com/repos.fossil/indieweb/
[3]
https://mutabit.com/repos.fossil/indieweb/doc/trunk/docs/es/index.html#talleres


The second workshop will be tomorrow, Saturday, Aug. 29 from 3:15 PM to
7:15PM CO (GMT - 5) -- I will try to share the other workshops earlier,
but the site in [2] will be the consolidated memory of them, for those
who want to join us asynchronously.

We will see how IndieWeb sites help us to untangle and reweave that
other web and how this help us to reconnect in this stranger times.

Rethinking the infrastructure is also to rethink the ways in which it
enables and makes visible (or not) certain ways of being and acting.
Infrastructures are embodied discourses. So thank you in advance for
joining us in rethinking this in practice.

Of course, Pharo is behind scenes, as usual, powering this experience.
But with these IndieWeb workshops I think we have found a sweet spot
that puts coding in front with a practical introduction and motivation
beyond the kind of boring "Hello World". Following a "local first"
approach, documentation will be in Spanish, but source code[5] and
interactive documentation will be in English to bridge our worlds :-),

[4] https://mutabit.com/offray/blog/en/entry/dumb-hello-world
[5] https://mutabit.com/repos.fossil/brea/


See you on cyberspace,

Offray

Re: [Pharo-users] Pharo at JPL

[tbrunz]

JPL has its own Slack server...  Of course I started a channel:

 



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo at JPL

[tbrunz]

Thanks!  

And I want to give special thanks to Stef and to Alexandre Bergel for being
generous with their time in helping me with my advocacy.

It's just as you said, Offray: "We live in an attention economy" -- and the
competition is *fierce*!  

(I think it's worse when you're dealing with educated professionals -- they
work hard, they play hard, and there's little left over to "learn something
new" sometimes.  But I am not discouraged... I take the long view on this. 
Computers taught me patience.  I'm using that now...  ;^)

-t



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo at JPL

[Offray Vladimir Luna Cárdenas]

Ted,

Thanks for this advocacy and best of lucks.

Cheers,

Offray

On 28/08/20 5:27 p. m., tbrunz wrote:
> Hi Konrad,
>
> I'm the person at JPL who (somehow) got "The Powers That Be" here to agree
> to join the Consortium.
>
> I'm also the major champion of Pharo at JPL, and am leading an effort to get
> Pharo introduced & infused at JPL.
>
> I see the initial "market" for Pharo here to be:
>
> * Scientific & engineering data analysis & visualization,
> * Modeling and simulation, 
> * Internal web servers,
> * Custom ground support & test systems, 
> * Small-to-medium sized scripting to "support applications".
>
> I'm sure more application areas will open up as I get people to start using
> Pharo in their particular areas of expertise.
>
> I'm doing what I can be promoting Pharo, providing introductions & training,
> and I'm now working on demonstrations that can catch the attention of both
> engineers and managers -- to see the potential.
>
> Wish me luck!
> -Ted
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

Re: [Pharo-users] Pharo at JPL

[Richard Sargent]

On Fri, Aug 28, 2020 at 3:27 PM tbrunz  wrote:

> Hi Konrad,
>
> I'm the person at JPL who (somehow) got "The Powers That Be" here to agree
> to join the Consortium.
>
> I'm also the major champion of Pharo at JPL, and am leading an effort to
> get
> Pharo introduced & infused at JPL.
>
> I see the initial "market" for Pharo here to be:
>
> * Scientific & engineering data analysis & visualization,
> * Modeling and simulation,
> * Internal web servers,
> * Custom ground support & test systems,
> * Small-to-medium sized scripting to "support applications".
>
> I'm sure more application areas will open up as I get people to start using
> Pharo in their particular areas of expertise.
>
> I'm doing what I can be promoting Pharo, providing introductions &
> training,
> and I'm now working on demonstrations that can catch the attention of both
> engineers and managers -- to see the potential.
>
> Wish me luck!
> -Ted
>

Good luck! And Well Done!!


>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>

Re: [Pharo-users] Pharo at JPL

[tbrunz]

Hi Konrad,

I'm the person at JPL who (somehow) got "The Powers That Be" here to agree
to join the Consortium.

I'm also the major champion of Pharo at JPL, and am leading an effort to get
Pharo introduced & infused at JPL.

I see the initial "market" for Pharo here to be:

* Scientific & engineering data analysis & visualization,
* Modeling and simulation, 
* Internal web servers,
* Custom ground support & test systems, 
* Small-to-medium sized scripting to "support applications".

I'm sure more application areas will open up as I get people to start using
Pharo in their particular areas of expertise.

I'm doing what I can be promoting Pharo, providing introductions & training,
and I'm now working on demonstrations that can catch the attention of both
engineers and managers -- to see the potential.

Wish me luck!
-Ted



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Checking baseline before publishing

[Jonathan van Alteren]

Ah yes, sorry, you're right. You do have to commit/push for that to work.

I'm interested to hear what your experience is with using #record.

Kind regards,

Jonathan van Alteren

Founding Member | Object Guild B.V.
Sustainable Software for Purpose-Driven Organizations

jvalte...@objectguild.com
On 28 Aug 2020, 20:00 +0200, Esteban Maringolo , wrote:
> Hi Jonathan,
>
> I never thought of SmalltalkCI for that (I use Gitlab) but in essence
> it still requires a trial and error approach (of committing the
> Baseline and loading it afterwards to see if it works).
>
> Metacello has a "record" operation that basically does a dry run of
> the load, but I don't know if there is a way to do it using the
> Baseline in the image instead of one in a repository.
>
> Regards!
>
> Esteban A. Maringolo
>
> On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren
>  wrote:
> >
> > Hi Esteban,
> >
> > You might want to give smalltalkCI a try: 
> > https://github.com/hpi-swa/smalltalkCI
> >
> > I've recently started using it myself, with GitLab CI and GitHub Actions, 
> > but one of the cool things is that you can use it to test your build 
> > locally.
> >
> > For example, create a .smalltalk.ston file for your project which loads the 
> > baseline that you want to test, like this:
> >
> > SmalltalkCISpec {
> > #loading : [
> > SCIMetacelloLoadSpec {
> > #baseline : 'MyProject',
> > #directory : 'source',
> > #load : [ 'default' ],
> > #onWarningLog : true,
> > #platforms : [ #pharo ]
> > }
> > ],
> > #testing : {
> > #categories : [ 'MyProject-Tests' ]
> > }
> > }
> >
> > Then clone the smalltalkCI repo locally and open a terminal on its 
> > location, for example /Users/johndoe/git/smalltalkCI. You can then simply 
> > use smalltalkCI to build a Pharo image of your baseline, which effectively 
> > tests the correct working of your baseline:
> >
> > bin/smalltalkci -s "Pharo64-8.0" 
> > /Users/johndoe/git/MyProject/.smalltalk.ston
> >
> > By default, it will run all tests in the image, but you can change the list 
> > of tests being run by modifying the .smalltalk.ston file accordingly (see 
> > https://github.com/hpi-swa/smalltalkCI#testcase-selection).
> >
> > Hope this helps!
> >
> > Kind regards,
> >
> > Jonathan van Alteren
> >
> > Founding Member | Object Guild B.V.
> > Sustainable Software for Purpose-Driven Organizations
> >
> > jvalte...@objectguild.com
> > On 27 Aug 2020, 04:12 +0200, Esteban Maringolo , 
> > wrote:
> >
> > Hi,
> >
> > How can I check that my baseline works without having to publish
> > everything, check that it fails and then going to the origin, fixing,
> > etc?
> >
> > I might be particularly idiot to always miss something, I usually have
> > to try at least four times (in a blank image) that my Baseline,
> > dependencies, etc. works as expected.
> >
> > There must be some other way.
> >
> > Esteban A. Maringolo
> >
>

Re: [Pharo-users] Checking baseline before publishing

[Dale Henrichs]

Esteban,

#record _is_ run against the baseline that is in the image if it is 
present. This is true for all of the Metacello commands - if the 
BaselineOf is present it is used, if it is not present it will be 
loaded. The #get command will load a fresh copy of the baseline from the 
repository.


There is an option to ignore image state (#ignoreImage) when running 
#record (or any other command) to simulate loading into an "empty" image 
... depending upon the volume of output, you could read the report to 
determine if the packages/projects that you are expecting to see are 
being loaded and of course if your goal is to expose outright errors 
#record should do that as well ...


Dale

On 8/28/20 10:59 AM, Esteban Maringolo wrote:

Hi Jonathan,

I never thought of SmalltalkCI for that (I use Gitlab) but in essence
it still requires a trial and error approach (of committing the
Baseline and loading it afterwards to see if it works).

Metacello has a "record" operation that basically does a dry run of
the load, but I don't know if there is a way to do it using the
Baseline in the image instead of one in a repository.

Regards!

Esteban A. Maringolo

On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren
 wrote:

Hi Esteban,

You might want to give smalltalkCI a try: https://github.com/hpi-swa/smalltalkCI

I've recently started using it myself, with GitLab CI and GitHub Actions, but 
one of the cool things is that you can use it to test your build locally.

For example, create a .smalltalk.ston file for your project which loads the 
baseline that you want to test, like this:

SmalltalkCISpec {
   #loading : [
 SCIMetacelloLoadSpec {
   #baseline : 'MyProject',
   #directory : 'source',
   #load : [ 'default' ],
   #onWarningLog : true,
   #platforms : [ #pharo ]
 }
   ],
   #testing : {
 #categories : [ 'MyProject-Tests' ]
   }
}

Then clone the smalltalkCI repo locally and open a terminal on its location, 
for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI 
to build a Pharo image of your baseline, which effectively tests the correct 
working of your baseline:

bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston

By default, it will run all tests in the image, but you can change the list of 
tests being run by modifying the .smalltalk.ston file accordingly (see 
https://github.com/hpi-swa/smalltalkCI#testcase-selection).

Hope this helps!

Kind regards,

Jonathan van Alteren

Founding Member | Object Guild B.V.
Sustainable Software for Purpose-Driven Organizations

jvalte...@objectguild.com
On 27 Aug 2020, 04:12 +0200, Esteban Maringolo , wrote:

Hi,

How can I check that my baseline works without having to publish
everything, check that it fails and then going to the origin, fixing,
etc?

I might be particularly idiot to always miss something, I usually have
to try at least four times (in a blank image) that my Baseline,
dependencies, etc. works as expected.

There must be some other way.

Esteban A. Maringolo

Re: [Pharo-users] Pharo.exe and PharoConsole.exe VM Difference

[Stéphane Ducasse]

On windows you cannot have the same executable being to log info or not. 
So this is why we are forced to have two different versions. 

S

> On 28 Aug 2020, at 03:48, Esteban Maringolo  wrote:
> 
> Hi,
> 
> What is the difference between the Pharo.exe and PharoConsole.exe?
> They have the same size, but are binary different.
> 
> I'd expect the PharoConsole to run headless by default, but it is not the 
> case.
> 
> So... is this documented anywhere?
> 
> Thanks!
> 
> Esteban A. Maringolo
> 


Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Re: [Pharo-users] Checking baseline before publishing

[Esteban Maringolo]

Hi Jonathan,

I never thought of SmalltalkCI for that (I use Gitlab) but in essence
it still requires a trial and error approach (of committing the
Baseline and loading it afterwards to see if it works).

Metacello has a "record" operation that basically does a dry run of
the load, but I don't know if there is a way to do it using the
Baseline in the image instead of one in a repository.

Regards!

Esteban A. Maringolo

On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren
 wrote:
>
> Hi Esteban,
>
> You might want to give smalltalkCI a try: 
> https://github.com/hpi-swa/smalltalkCI
>
> I've recently started using it myself, with GitLab CI and GitHub Actions, but 
> one of the cool things is that you can use it to test your build locally.
>
> For example, create a .smalltalk.ston file for your project which loads the 
> baseline that you want to test, like this:
>
> SmalltalkCISpec {
>   #loading : [
> SCIMetacelloLoadSpec {
>   #baseline : 'MyProject',
>   #directory : 'source',
>   #load : [ 'default' ],
>   #onWarningLog : true,
>   #platforms : [ #pharo ]
> }
>   ],
>   #testing : {
> #categories : [ 'MyProject-Tests' ]
>   }
> }
>
> Then clone the smalltalkCI repo locally and open a terminal on its location, 
> for example /Users/johndoe/git/smalltalkCI. You can then simply use 
> smalltalkCI to build a Pharo image of your baseline, which effectively tests 
> the correct working of your baseline:
>
> bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston
>
> By default, it will run all tests in the image, but you can change the list 
> of tests being run by modifying the .smalltalk.ston file accordingly (see 
> https://github.com/hpi-swa/smalltalkCI#testcase-selection).
>
> Hope this helps!
>
> Kind regards,
>
> Jonathan van Alteren
>
> Founding Member | Object Guild B.V.
> Sustainable Software for Purpose-Driven Organizations
>
> jvalte...@objectguild.com
> On 27 Aug 2020, 04:12 +0200, Esteban Maringolo , wrote:
>
> Hi,
>
> How can I check that my baseline works without having to publish
> everything, check that it fails and then going to the origin, fixing,
> etc?
>
> I might be particularly idiot to always miss something, I usually have
> to try at least four times (in a blank image) that my Baseline,
> dependencies, etc. works as expected.
>
> There must be some other way.
>
> Esteban A. Maringolo
>

Re: [Pharo-users] Checking baseline before publishing

[Jonathan van Alteren]

Hi Esteban,

You might want to give smalltalkCI a try: https://github.com/hpi-swa/smalltalkCI

I've recently started using it myself, with GitLab CI and GitHub Actions, but 
one of the cool things is that you can use it to test your build locally.

For example, create a .smalltalk.ston file for your project which loads the 
baseline that you want to test, like this:

SmalltalkCISpec {
  #loading : [
    SCIMetacelloLoadSpec {
      #baseline : 'MyProject',
      #directory : 'source',
      #load : [ 'default' ],
      #onWarningLog : true,
      #platforms : [ #pharo ]
    }
  ],
  #testing : {
    #categories : [ 'MyProject-Tests' ]
  }
}

Then clone the smalltalkCI repo locally and open a terminal on its location, 
for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI 
to build a Pharo image of your baseline, which effectively tests the correct 
working of your baseline:

bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston

By default, it will run all tests in the image, but you can change the list of 
tests being run by modifying the .smalltalk.ston file accordingly (see 
https://github.com/hpi-swa/smalltalkCI#testcase-selection).

Hope this helps!

Kind regards,

Jonathan van Alteren

Founding Member | Object Guild B.V.
Sustainable Software for Purpose-Driven Organizations

jvalte...@objectguild.com
On 27 Aug 2020, 04:12 +0200, Esteban Maringolo , wrote:
> Hi,
>
> How can I check that my baseline works without having to publish
> everything, check that it fails and then going to the origin, fixing,
> etc?
>
> I might be particularly idiot to always miss something, I usually have
> to try at least four times (in a blank image) that my Baseline,
> dependencies, etc. works as expected.
>
> There must be some other way.
>
> Esteban A. Maringolo
>

Re: [Pharo-users] pharo books as audiobooks

[niepiekm]

Hi Siemen, all,

you may listen to PDF files from the Web via 'Read Aloud' Chrome extension
(https://chrome.google.com/webstore/detail/read-aloud-a-text-to-spee/hdhinadidafjejdhmfkjgnolgimiaplp)
and use its service at
https://assets.lsdsoftware.com/read-aloud/page-scripts/pdf-upload.html to
open and listen to local PDF files.

Simply open a local PDF file via the service and click on the extension
button.

Regards,
Marek



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

[Pharo-users] pharo books as audiobooks

[Siemen Baader]

Hi all,

I'm interested in listening to the pharo books as audiobooks, away from my
desk. I read them to learn higher level concepts and can get back to the
code boxes later to look up the details, so I'm not too worried about how
to exactly convert the code boxes to audio.

One way to enable this would be if the books were served publicly as static
HTML. One can then use the Pocket App to save them and listen on the go. In
theory this should be something that the CI system could just be set up to
do, right?

(There are apps to convert PDFs to audio too, but those I have been able to
find are inconvenient and / or expensive.)

Is anyone who is already familiar with the CI system interested in setting
this up? I'd love to help but don't have the time, unfortunately. But I'm
happy to provide feedback. I'v

cheers
Siemen