> Am 25.10.2014 um 18:12 schrieb Esteban A. Maringolo :
>
> 2014-10-25 5:44 GMT-03:00 Norbert Hartl :
>> There is a lot of polling going on. You can't get rid of it completely. To
>> lower the cpu usage it might be good to suspend the ui thread. You need some
>> external trigger to resume it if
2014-10-25 5:44 GMT-03:00 Norbert Hartl :
> There is a lot of polling going on. You can't get rid of it completely. To
> lower the cpu usage it might be good to suspend the ui thread. You need some
> external trigger to resume it if you want to connect via RFB.
I don't use RFB, is there a way to
There is a lot of polling going on. You can't get rid of it completely. To
lower the cpu usage it might be good to suspend the ui thread. You need some
external trigger to resume it if you want to connect via RFB.
Norbert
> Am 24.10.2014 um 22:18 schrieb Esteban A. Maringolo :
>
> Ah, I forgot
Ah, I forgot.
The only drawback here is the 5% permanent idle load per image.
Every image I add adds a 5% load to the server, even when it's only standby.
That's a totally bummer, though manageable if you have less than 10
images like I do :)
Esteban A. Maringolo
2014-10-24 16:29 GMT-03:00
>> I'd like to know the development process of others, from SCM to
>> building, deploying and server provisioning.
>
> I would say the standard approach is:
>
> - use Monticello with any repo type
> - split your code in some big modules, some private, some from public source
> - have a single overa
this nice discussion should be turned into a blog/chapter :)
Any taker?
Stef
On 23/10/14 20:16, Esteban A. Maringolo wrote:
tl;dr version:
I'd like to be able to do something like
$PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8091
and:
$PATH/app/pharo-vm/pharo --nod
Hi Sven and Phil,
Thanks for your answers.
So I already use the zeroconf handlers ;-)
The problem is that I do not benefit from the cache well enough because our
command line tool (pharo-based and installed by this script
http://car.mines-douai.fr/scripts/PhaROS) is dedicated to create custom
im
On Fri, Oct 24, 2014 at 12:50 AM, Luc Fabresse
wrote:
> Hi,
>
>
>> Note that zeroconf handlers allow you to build images incrementally (the
>> image is saved after each build), which is way faster than always starting
>> from scratch.
>>
>
> what are zeroconf "handlers"?
>
the things you get in
On Thu, Oct 23, 2014 at 11:11 PM, Esteban A. Maringolo wrote:
> 2014-10-23 17:04 GMT-03:00 Sven Van Caekenberghe :
>
> >> Why do you use the pharo shell script instead of pharo-vm with
> >> --no-display? Is there any benefit other than having the pwd set to
> >> the image location? And hence, the
> On 24 Oct 2014, at 00:50, Luc Fabresse wrote:
>
> Hi,
>
> Note that zeroconf handlers allow you to build images incrementally (the
> image is saved after each build), which is way faster than always starting
> from scratch.
>
> what are zeroconf "handlers"?
> because I use zeroconf to reb
Hi,
> Note that zeroconf handlers allow you to build images incrementally (the
> image is saved after each build), which is way faster than always starting
> from scratch.
>
what are zeroconf "handlers"?
because I use zeroconf to rebuild images and it is slow because it
downloads the vm, the ima
> On 23 Oct 2014, at 23:11, Esteban A. Maringolo wrote:
>
> 2014-10-23 17:04 GMT-03:00 Sven Van Caekenberghe :
>
>>> Why do you use the pharo shell script instead of pharo-vm with
>>> --no-display? Is there any benefit other than having the pwd set to
>>> the image location? And hence, the argu
> On 23 Oct 2014, at 21:54, Esteban A. Maringolo wrote:
>
> 2014-10-23 16:08 GMT-03:00 Sven Van Caekenberghe :
>> Nah, you can do it way easier:
>>
>> $ cat run.st
>> NonInteractiveTranscript stdout install.
>>
>> Transcript show: Smalltalk commandLine arguments; cr.
>>
>> Smalltalk quitPrimi
2014-10-23 16:08 GMT-03:00 Sven Van Caekenberghe :
> Nah, you can do it way easier:
>
> $ cat run.st
> NonInteractiveTranscript stdout install.
>
> Transcript show: Smalltalk commandLine arguments; cr.
>
> Smalltalk quitPrimitive.
>
> $ ./pharo Pharo.image run.st 1 2 3
> #('1' '2' '3')
>
> HTH,
U
> On 23 Oct 2014, at 21:17, Esteban Lorenzano wrote:
>
> $ cat startserver.sh
> #! /bin/sh
> nohup ./pharo Pharo.image eval —no-quit “MyServerStart port: $1” &
>
> ./startserver 8080
> ./startserver 8081
> ./startserver 8082
>
> but is a bit… “trucho” (in plain argentinian)… which means a bad
$ cat startserver.sh
#! /bin/sh
nohup ./pharo Pharo.image eval —no-quit “MyServerStart port: $1” &
./startserver 8080
./startserver 8081
./startserver 8082
but is a bit… “trucho” (in plain argentinian)… which means a bad quality hack :P
> On 23 Oct 2014, at 21:08, Sven Van Caekenberghe wrote:
On Thu, Oct 23, 2014 at 8:16 PM, Esteban A. Maringolo
wrote:
> How can I capture the --port argument? For what I saw, only "boolean"
> parameters can be defined (--quit, --save, etc, without arguments). It
> is, no getopts compatibility.
no; it is possible to define parameters like --to=html as
Nah, you can do it way easier:
$ cat run.st
NonInteractiveTranscript stdout install.
Transcript show: Smalltalk commandLine arguments; cr.
Smalltalk quitPrimitive.
$ ./pharo Pharo.image run.st 1 2 3
#('1' '2' '3')
HTH,
Sven
> On 23 Oct 2014, at 20:52, Esteban A. Maringolo wrote:
>
> 2014-1
2014-10-23 15:19 GMT-03:00 Esteban Lorenzano :
>
>> On 23 Oct 2014, at 20:16, Esteban A. Maringolo wrote:
>> Do I have to define a subclass of STCommandLineHandler?
> yes
I thought so.
>> How can I capture the --port argument? For what I saw, only "boolean"
>> parameters can be defined (--quit,
> On 23 Oct 2014, at 20:16, Esteban A. Maringolo wrote:
>
> tl;dr version:
>
> I'd like to be able to do something like
>
> $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8091
> and:
> $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8092
> etc
tl;dr version:
I'd like to be able to do something like
$PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8091
and:
$PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8092
etc.
Do I have to define a subclass of STCommandLineHandler?
How can I capture
21 matches
Mail list logo
