Re: [Pharo-users] Pharo launcher

2019-10-13 Thread ilker özcan
I format my pc and reinstall windows..now it works..thank you.

On Tue, Oct 8, 2019, 18:10 Christophe Demarey 
wrote:

> Hi Ilker,
>
> It looks like you got the same issue as
> https://github.com/pharo-project/pharo-launcher/issues/349
> If you do not run Pharo Launcher from cmd line or unzip is not in the
> path, it should works fine (waiting for a proper fix).
> Please try to delete corrupted VMs (you can use Pharo Launcher VM Manager)
> and try again.
>
> Thanks for the report,
> Christophe
>
> > Le 8 oct. 2019 à 15:35, ilker özcan  a écrit :
> >
> > When i tried to install pharo 7 and 8 with the launcher on windows 10
> there happened a message which says windows can not run 16 bit program..
> >
> > It seems pharo.exe seems to be 16 bit ( i installed 64bit)..anyone with
> such a problem and any idea how i can solve this? Thanks all..
>
>
>


Re: [Pharo-users] Pharo launcher

2019-10-08 Thread Christophe Demarey
Hi Ilker,

It looks like you got the same issue as 
https://github.com/pharo-project/pharo-launcher/issues/349
If you do not run Pharo Launcher from cmd line or unzip is not in the path, it 
should works fine (waiting for a proper fix).
Please try to delete corrupted VMs (you can use Pharo Launcher VM Manager) and 
try again.

Thanks for the report,
Christophe

> Le 8 oct. 2019 à 15:35, ilker özcan  a écrit :
> 
> When i tried to install pharo 7 and 8 with the launcher on windows 10 there 
> happened a message which says windows can not run 16 bit program..
> 
> It seems pharo.exe seems to be 16 bit ( i installed 64bit)..anyone with such 
> a problem and any idea how i can solve this? Thanks all..




Re: [Pharo-users] pharo launcher chrash

2019-03-09 Thread Roelof Wobben

  
  
thanks 
  
  re-installing the launcher did the trick.
  
  Roelof
  
  
  
  Op 9-3-2019 om 16:31 schreef Ben Coman:


  
  

  

  Together with the changes file you sent over Discord,
I started the image and it didn't crash for me,
  but came up with an error "PrimitiveFailed: primitive
#removeProcess: in ProcessWrapper class failed"
  
  
  
ProcessWrapper-class >> removeProcess: arg1
	
	self
  primitiveFailed
  
  
  
  where arg1==>25416768
  
  
  
  
  So there is nothing for me to debug.
  Try uninstalling/reinstalling PharoLauncher.  It
won't touch your image files and will rescan them when
the fresh install starts.
  
  
  cheers -ben
  
  
  
  
On Sat, 9 Mar 2019 at
  21:09, Roelof Wobben 
  wrote:


  
Of
  course.
  
  Here are the links : 
  
  https://www.dropbox.com/s/5mwwaxwsy4we841/Pharo.image?dl=0
  
  if you need also the sources I can provide it
  also. 
  
  Roelof
  
  Op 9-3-2019 om 13:55 schreef Ben Coman:


  

  

  

  The most I can tell is this seems
significant...
  
  


  Stack backtrace:
  	[65942944]
signalSemaphore + 0xd64 in
ProcessWrapperPlugin.DLL
  	[659422CA]
signalSemaphore + 0x6ea in
ProcessWrapperPlugin.DLL
  
  
  
Smalltalk stack dump:
 0x11f8f84 M
  ProcessWrapper>finalize
  0x8cb4fb0: a(n) ProcessWrapper
 0x11f8fa0 M
  WeakFinalizerItem>finalizeValues
  0x8c94148: a(n) WeakFinalizerItem


  
  
  
  Can you upload your PharoLauncher
image somewhere for others to try -
although the change in environment
might disappear the error.
  
  
  cheers -ben
  
  




  
On
  Sat, 9 Mar 2019 at 18:55, Roelof
  Wobben 
  wrote:

Hello,
  
  When starting up the launcher on
  Windows 10 I see a crash.
  A dmp file is included.
  
  Roelof
  

  

  

  

  


  

  
   

Re: [Pharo-users] pharo launcher chrash

2019-03-09 Thread Ben Coman
Together with the changes file you sent over Discord, I started the image
and it didn't crash for me,
but came up with an error "PrimitiveFailed: primitive #removeProcess: in
ProcessWrapper class failed"

ProcessWrapper-class >> removeProcess: arg1

self primitiveFailed

where arg1==>25416768


So there is nothing for me to debug.
Try uninstalling/reinstalling PharoLauncher.  It won't touch your image
files and will rescan them when the fresh install starts.

cheers -ben


On Sat, 9 Mar 2019 at 21:09, Roelof Wobben  wrote:

> Of course.
>
> Here are the links :
>
>
> *https://www.dropbox.com/s/5mwwaxwsy4we841/Pharo.image?dl=0
>  *
> if you need also the sources I can provide it also.
>
> Roelof
>
> Op 9-3-2019 om 13:55 schreef Ben Coman:
>
> The most I can tell is this seems significant...
>
> Stack backtrace:
> [65942944] signalSemaphore + 0xd64 in ProcessWrapperPlugin.DLL
> [659422CA] signalSemaphore + 0x6ea in ProcessWrapperPlugin.DLL
>
> Smalltalk stack dump:
>  0x11f8f84 M ProcessWrapper>finalize 0x8cb4fb0: a(n) ProcessWrapper
>  0x11f8fa0 M WeakFinalizerItem>finalizeValues 0x8c94148: a(n)
> WeakFinalizerItem
>
>
> Can you upload your PharoLauncher image somewhere for others to try -
> although the change in environment might disappear the error.
>
> cheers -ben
>
>
>
> On Sat, 9 Mar 2019 at 18:55, Roelof Wobben  wrote:
>
>> Hello,
>>
>> When starting up the launcher on Windows 10 I see a crash.
>> A dmp file is included.
>>
>> Roelof
>>
>>
>


Re: [Pharo-users] pharo launcher chrash

2019-03-09 Thread Roelof Wobben

  
  
Of course.
  
  Here are the links : 
  
  https://www.dropbox.com/s/5mwwaxwsy4we841/Pharo.image?dl=0
  
  if you need also the sources I can provide it also. 
  
  Roelof
  
  Op 9-3-2019 om 13:55 schreef Ben Coman:


  
  

  

  

  The most I can tell is this seems significant...
  
  


  Stack backtrace:
  	[65942944]
signalSemaphore + 0xd64 in ProcessWrapperPlugin.DLL
  	[659422CA]
signalSemaphore + 0x6ea in ProcessWrapperPlugin.DLL
  
  
  
Smalltalk stack dump:
 0x11f8f84 M ProcessWrapper>finalize
  0x8cb4fb0: a(n) ProcessWrapper
 0x11f8fa0 M
  WeakFinalizerItem>finalizeValues 0x8c94148:
  a(n) WeakFinalizerItem


  
  
  
  Can you upload your PharoLauncher image somewhere
for others to try - although the change in
environment might disappear the error.
  
  
  cheers -ben
  
  




  
On Sat, 9 Mar 2019
  at 18:55, Roelof Wobben 
  wrote:

Hello,
  
  When starting up the launcher on Windows 10 I see
  a crash.
  A dmp file is included.
  
  Roelof
  

  

  

  

  


  




Re: [Pharo-users] pharo launcher chrash

2019-03-09 Thread Ben Coman
The most I can tell is this seems significant...

Stack backtrace:
[65942944] signalSemaphore + 0xd64 in ProcessWrapperPlugin.DLL
[659422CA] signalSemaphore + 0x6ea in ProcessWrapperPlugin.DLL

Smalltalk stack dump:
 0x11f8f84 M ProcessWrapper>finalize 0x8cb4fb0: a(n) ProcessWrapper
 0x11f8fa0 M WeakFinalizerItem>finalizeValues 0x8c94148: a(n)
WeakFinalizerItem


Can you upload your PharoLauncher image somewhere for others to try -
although the change in environment might disappear the error.

cheers -ben



On Sat, 9 Mar 2019 at 18:55, Roelof Wobben  wrote:

> Hello,
>
> When starting up the launcher on Windows 10 I see a crash.
> A dmp file is included.
>
> Roelof
>
>


Re: [Pharo-users] Pharo Launcher update installation issues

2019-02-25 Thread Christophe Demarey
Hi,

> Le 24 févr. 2019 à 06:33, Sanjay Minni  a écrit :
> 
> Hi,
> 
> I am trying to install Pharo Launcher 1.6 (.msi) in Windows 10
> it says "a more ecent version is already installed" and does not proceed
> but the version installed is 1.5.1
> 
> also 
> in 1.5.1 the left panel shows in the Distributions list 7.0 as "Development
> version" - should it not change to « Stable"

There was an issue : https://github.com/pharo-project/pharo-launcher/issues/310
If you download latest launcher version, it should be fixed. 
http://pharo.org/download

Regards,
Christophe


Re: [Pharo-users] Pharo Launcher and Command Line

2019-02-08 Thread Christophe Demarey
Hi Sergio,

> Le 5 févr. 2019 à 14:55, sergio ruiz  a écrit :
> 
> Hey, all.
> 
> I REALLY dig the pharo launcher! this is a great addition.
> 
> One quick question.
> 
> How do i go about running a method from the command line?
> 
> Specifically, I usually run something like:
> 
> ./pharo Pharo.image ../scripts/setup-client-application.st 
> 
> 
> To set up a new image with the current project.

This feature is not yet available in Pharo Launcher.
We are working to provide a configuration per image / template where you could 
describe a specific vm to run your image or a script to run at the image 
creation to load packages, etc.

For now, what you could do, is to have a CI job preparing the image with all 
you need for you, zip it, and use it as a template from Pharo Launcher. It is 
already doable from https://ci.inria.fr/pharo-contribution/. If your project is 
private, then you could add a source to a private Jenkins server.

> I am not sure which executable to run with this that will execute the same 
> executable as pharo launcher.

Pharo Launcher stores its vms under $HOME/Documents/Pharo/vms
If you want to run the same VM as PharoLaucher, you just need to know the Pharo 
version of the image (e.g. 70) and the architecture (e.g. 64 bits).
Then you can run you image with 
$HOME/Documents/Pharo/vms/70-x64/Pharo.app/Contents/MacOS/Pharo Pharo.image 
../scripts/setup-client-application.st  
(the end of the  path on windows or linux to the executable will change a bit)

Hope this helps,
Christophe

Re: [Pharo-users] Pharo launcher

2018-09-26 Thread Trussardi Dario Romano
Ciao Christophe,


> Hi Dario,
> 
> The problem is probably fixed in the latest PharoLauncher version (1.4) 
> available from http://pharo.org/download.

Yes, i download the last Pharo launcher ( 1.4 ) and everything works,

> If not, as specified in the dialog text, please run the given command from 
> the command line to give us more information on what is the problem.
> 
Thanks, 

Dario

> Regards,
> Christophe
> 
>> Le 26 sept. 2018 à 12:05, Trussardi Dario Romano 
>>  a écrit :
>> 
>> Ciao,
>> 
>>  on Ubuntu system with Pharo Launcher 1.3
>> 
>>  after create a new Pharo 7.0-64 bit ( development version )
>> 
>>  when i launch the images the system answer :
>> 
>> Cannot determine image version: image version file not found!
>> Try to run this command in a shell to get more information on the problem:
>> cd "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836" && export 
>> SQUEAK_PLUGINS="" && 
>> "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836/pharo" --nodisplay 
>> "/home/party/Pharo/images/Pharo 7.0 - 64bit (180926)-01/Pharo 7.0 - 64bit 
>> (180926)-01.image" eval "(Smalltalk imagePath asFileReference parent) / 
>> 'pharo.version' writeStreamDo: [ :stream | |major minor|major := 
>> SystemVersion current major.minor := SystemVersion current 
>> minor.(major = 6 and: [ SystemVersion current highestUpdate >= 
>> 60509 ])ifTrue: [ minor := 1 ].stream
>>  << major asString; << minor asString ]"pha
>> 
>>  Thanks for considerations,
>> 
>>  Dario
>> 
>>  P.S. In the same environment one hold  Pharo 7.0-64 bit ( development 
>> version ) image ran well with launch command
> 



Re: [Pharo-users] Pharo launcher

2018-09-26 Thread Christophe Demarey
Hi Dario,

The problem is probably fixed in the latest PharoLauncher version (1.4) 
available from http://pharo.org/download.
If not, as specified in the dialog text, please run the given command from the 
command line to give us more information on what is the problem.

Regards,
Christophe

> Le 26 sept. 2018 à 12:05, Trussardi Dario Romano  
> a écrit :
> 
> Ciao,
> 
>   on Ubuntu system with Pharo Launcher 1.3
> 
>   after create a new Pharo 7.0-64 bit ( development version )
> 
>   when i launch the images the system answer :
> 
> Cannot determine image version: image version file not found!
> Try to run this command in a shell to get more information on the problem:
> cd "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836" && export 
> SQUEAK_PLUGINS="" && 
> "/opt/pharolauncher/pharo-vm/lib/pharo/5.0-201805090836/pharo" --nodisplay 
> "/home/party/Pharo/images/Pharo 7.0 - 64bit (180926)-01/Pharo 7.0 - 64bit 
> (180926)-01.image" eval "(Smalltalk imagePath asFileReference parent) / 
> 'pharo.version' writeStreamDo: [ :stream | |major minor|major := 
> SystemVersion current major.minor := SystemVersion current minor. 
>(major = 6 and: [ SystemVersion current highestUpdate >= 60509 ])  
>   ifTrue: [ minor := 1 ].stream << 
> major asString; << minor asString ]"pha
> 
>   Thanks for considerations,
> 
>   Dario
> 
>   P.S. In the same environment one hold  Pharo 7.0-64 bit ( development 
> version ) image ran well with launch command



Re: [Pharo-users] Pharo Launcher & Stored Settings

2018-08-07 Thread werner kassens
On 08/07/2018 02:15 AM, Evan Donahue wrote:
> Yes, that's right. As long as I don't "store settings" everything is
> ok, but if I do find myself wanting to change a global setting of some
> kind, and I hit "store," it /also/ stores the metacello paths, which
> will then be incorrect for the next new image I create. Also, even if
> I delete them, it seems to autogenerate one (but not both) of the
> paths incorrectly (with that crazy /build) path.
>
> More generally though, all I was trying to do was use Pharo launcher
> and keep repositories separate, which I was advised to do by the list.
Hi Evan,
yes exactly. the default  if i dont change & _store_ settings is: i make
via launcher a pharo6.1blabla, it has its own repository-directory; i
make the next one, pharo6.1blabla-01, open monticello and it has another
package-cache. i did not test this, but i guess it could be possible
that if you store settings just once even _without_ changing anything,
the local cache directory will be stored, as the class-var-accessor
produced a valid path, and from then on this setting will not change
anymore for new builds via launcher.

you either reset the settings via deleting the monticello records in the
settings file found via StartupPreferencesLoader
preferencesVersionFolder. or if you need to store changed settings in a
general way eg for all 6.1 versions, you do that deleting afterwards.

i agree that the 2 monticello-settings behave differently and that this
is either irritating or probably a bug (because the second behaviour can
make storing other settings difficult), but then  i
have to admit i was never bothered by this behaviour.
werner



Re: [Pharo-users] Pharo Launcher & Stored Settings

2018-08-07 Thread Tim Mackinnon
The settings that you save will apply to all images - so you need to clear out 
those settings for shared repo’s etc.

I think what is confusing is that using the  Save button - means apply the 
settings to all images. If you change the setting locally in your image and 
don’t press save, it persists just in that image (is you can try something out).

If you want most images to share a setting and just a few to not do it - then 
you would save the main setting - and just adjust locally when needed - or 
could have some startup script that recognised certain image names and applied 
something programmatically.

Tim

> On 7 Aug 2018, at 02:03, Evan Donahue  wrote:
> 
> Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and
> 2) have each new image keep its repositories separate, as advised by others
> on the list, so that different images can check out different branches. Does
> that set up require custom scripting to adjust the repo path? 
> 
> The cache path does seem to do the required adjusting on its own, but the
> 'metacello default directory' path defaults to that crazy thing that's not a
> path on my computer:
> 
> /builds/workspace/Pharo-6.0-Update-Step-1-Tracker
> 
> PS, Is the 'store settings' button in the settings menu the standard way to
> configure cross-image preferences, because that seems to also save things
> like these paths that should be generated anew with each new image. Maybe I
> should stick with one single place for repos and just configure these paths
> to be global?
> 
> Thanks
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 




Re: [Pharo-users] Pharo Launcher & Stored Settings

2018-08-06 Thread Evan Donahue
Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and
2) have each new image keep its repositories separate, as advised by others
on the list, so that different images can check out different branches. Does
that set up require custom scripting to adjust the repo path? 

The cache path does seem to do the required adjusting on its own, but the
'metacello default directory' path defaults to that crazy thing that's not a
path on my computer:

/builds/workspace/Pharo-6.0-Update-Step-1-Tracker

PS, Is the 'store settings' button in the settings menu the standard way to
configure cross-image preferences, because that seems to also save things
like these paths that should be generated anew with each new image. Maybe I
should stick with one single place for repos and just configure these paths
to be global?

Thanks



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



Re: [Pharo-users] Pharo Launcher & Stored Settings

2018-08-04 Thread Sean P. DeNigris
Evan Donahue wrote
> Is there a way to handle settings that should be different for every
> image…

Startup script?



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



Re: [Pharo-users] Pharo Launcher multiplicated PhLDeploymentScript

2018-06-29 Thread Peter Uhnák
PhLStartupManager class>>addToLauncherStartUpList: aClass
self startUpClasses addIfNotPresent: aClass

seems to be enough.

Peter

On Fri, Jun 29, 2018 at 9:58 AM, Peter Uhnák  wrote:

> Hi,
>
> I've noticed that when I save Pharo Launcher image (ctrl+shift+s), because
> I was changing something, then PhLDeploymentScript is added to the the
> startup classes list.
>
> PhLStartupManager startUpClasses "a SortedCollection(
> PhLDirectoryBasedImageRepository PhLSettingBrowser PhLDeploymentScript
> PhLDeploymentScript ...(atm 34x)... PhLDeploymentScript)"
>
> PhLStartupManager startUpClasses asSet "a Set(
> PhLDirectoryBasedImageRepository PhLDeploymentScript PhLSettingBrowser)"
>
> I didn't notice any impact on functionality or speed (although for some
> reason there is a significant delay between clicking on the PhL icon and
> the image opening), but nevertheless it probably should be deduplicated.
>
> Thanks.
>
> Peter
>


Re: [Pharo-users] [Pharo-Launcher] call for tests on Windows

2018-04-19 Thread Richard Sargent
The good news is that the same version of Pharo Launcher worked essentially
perfectly under Windows 10.

As expected, the launcher was installed in AppData\Local.
However, I continue to find an AppData\Roaming\pharo directory created when
the launcher was installed. Its contents are as I described in the issue
created for the Windows 7 installation.


Suggestion:
Some of the lists are quite long. It might be useful to be able to sort
them by e.g. name or date of last change, both ascending and descending.



On Mon, Apr 16, 2018 at 9:54 AM, Richard Sargent <
richard.sarg...@gemtalksystems.com> wrote:

> I ran the launcher against my Windows 7 office computer and have created
> an issue with my feedback.
> https://github.com/pharo-project/pharo-launcher/issues/93
>
>
>
> On Mon, Apr 16, 2018 at 7:13 AM, Christophe Demarey <
> christophe.dema...@inria.fr> wrote:
>
>> Hi,
>>
>> Regarding the various problems Pharo Launchers had on Windows, we worked
>> on a new installer based on Advanced Installer [1] to avoid UAC (User
>> Account Control) and write permissions problems. This new installer now
>> installs Pharo Launcher in the user’s local app data folder (where for
>> sure, he has write permissions). Pharo Launcher also now have its own icon
>> and use its own name instead of Pharo. Also, the uninstaller now works as
>> expected. Last but not least, the installer is now signed to avoid warning
>> of Windows Defender.
>> Thanks to Ben Coman who did the first version of the packaging using
>> Advanced Installer (was NSIS).
>> This version should also improve the launch of Pharo images on Windows.
>>
>> So, please could you install and test this new version: and report any
>> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/
>> We do not have windows users around so it’s hard to know if it works
>> outside our tests boxes.
>>
>> Thanks,
>> Christophe
>>
>> [1] https://www.advancedinstaller.com/
>>
>
>


Re: [Pharo-users] Pharo Launcher

2018-04-18 Thread Stephane Ducasse
I'm in 10.12.6

On Wed, Apr 18, 2018 at 11:34 PM, Ben Coman  wrote:
> A while ago I experienced similar behavior, but I'm not on Mac at the
> moment.
> Maybe it depends on OS version?
>
> cheers -ben
>
>
> On 19 April 2018 at 04:35, Stephane Ducasse  wrote:
>>
>> sean
>>
>> I do not have this behavior.
>> I can use the launcher to open multiple images from the launcher.
>>
>>
>> On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris 
>> wrote:
>> > Ben Coman wrote
>> >> I *prefer* never to close PharoLauncher.
>> >
>> > That's the way I work as well, especially because I found that on Mac
>> > apparently you have to close all open images before Launcher will open
>> > again
>> > from the Dock.
>> >
>> >
>> >
>> > -
>> > Cheers,
>> > Sean
>> > --
>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>> >
>>
>



Re: [Pharo-users] Pharo Launcher

2018-04-18 Thread Ben Coman
A while ago I experienced similar behavior, but I'm not on Mac at the
moment.
Maybe it depends on OS version?

cheers -ben


On 19 April 2018 at 04:35, Stephane Ducasse  wrote:

> sean
>
> I do not have this behavior.
> I can use the launcher to open multiple images from the launcher.
>
>
> On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris 
> wrote:
> > Ben Coman wrote
> >> I *prefer* never to close PharoLauncher.
> >
> > That's the way I work as well, especially because I found that on Mac
> > apparently you have to close all open images before Launcher will open
> again
> > from the Dock.
> >
> >
> >
> > -
> > Cheers,
> > Sean
> > --
> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> >
>
>


Re: [Pharo-users] Pharo Launcher

2018-04-18 Thread Stephane Ducasse
sean

I do not have this behavior.
I can use the launcher to open multiple images from the launcher.


On Tue, Apr 17, 2018 at 1:00 PM, Sean P. DeNigris  wrote:
> Ben Coman wrote
>> I *prefer* never to close PharoLauncher.
>
> That's the way I work as well, especially because I found that on Mac
> apparently you have to close all open images before Launcher will open again
> from the Dock.
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>



Re: [Pharo-users] Pharo Launcher

2018-04-17 Thread Sean P. DeNigris
Ben Coman wrote
> I *prefer* never to close PharoLauncher.

That's the way I work as well, especially because I found that on Mac
apparently you have to close all open images before Launcher will open again
from the Dock.



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



Re: [Pharo-users] [Pharo-Launcher] call for tests on Windows

2018-04-16 Thread Esteban A. Maringolo
On 16/04/2018 11:13, Christophe Demarey wrote:

> So, please could you install and test this new version: and report any 
> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/

I'm downloading it, but something is wrong with that fileserver, it's
downloading at vry slow speeds.

Can't we use something like AWS S3 to store the files of files.pharo.org?

> We do not have windows users around so it’s hard to know if it works outside 
> our tests boxes.

Once it finishes I'll let you know. I'm one the few out there still
using Windows 7 Pro.

Regards,

-- 
Esteban A. Maringolo



Re: [Pharo-users] [Pharo-Launcher] call for tests on Windows

2018-04-16 Thread Paul DeBruicker
Microsoft allows devs to download VMs for Windows 7, 8, & 10 that work with
VirtualBox, Vagrant, VmWare, Parallels, & HyperV here:


https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/



They last 90 days and you can install Pharo on them.  Their real purpose is
to test websites on IE.







demarey wrote
> Hi,
> 
> Regarding the various problems Pharo Launchers had on Windows, we worked
> on a new installer based on Advanced Installer [1] to avoid UAC (User
> Account Control) and write permissions problems. This new installer now
> installs Pharo Launcher in the user’s local app data folder (where for
> sure, he has write permissions). Pharo Launcher also now have its own icon
> and use its own name instead of Pharo. Also, the uninstaller now works as
> expected. Last but not least, the installer is now signed to avoid warning
> of Windows Defender.
> Thanks to Ben Coman who did the first version of the packaging using
> Advanced Installer (was NSIS).
> This version should also improve the launch of Pharo images on Windows.
> 
> So, please could you install and test this new version: and report any
> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/
> We do not have windows users around so it’s hard to know if it works
> outside our tests boxes.
> 
> Thanks,
> Christophe
> 
> [1] https://www.advancedinstaller.com/





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



Re: [Pharo-users] Pharo Launcher

2018-04-16 Thread Ben Coman
On 17 April 2018 at 00:11, Peter Uhnák  wrote:

>
>
> On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman  wrote:
>
>> On 16 April 2018 at 16:55, Peter Uhnák  wrote:
>> >> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.
>> The
>> >> app vanished.
>> >
>> > As I've mentioned in several other threads, the way new images are
>> opened
>> > (the lib that executes the command) seems to be very unreliable and
>> > sometimes opening image just doesn't work, and I have to open PL again
>> and
>> > try again.
>> >
>> > My guess is that there's a race condition and PL closes faster, and
>> before
>> > the subprocess manages to be disowned.
>>
>> I untick the box "Quit on Launch"
>>
>
>
> That just turns the problem of "I sometimes have to do extra steps" to "I
> always have to do extra steps" (i.e. close PL)
>

You misunderstand.  I *prefer* never to close PharoLauncher.
Particularly when I dig deep into stuff that is likely to hang an Image,
Needing to *again* click the start menu, then click PharoLauncher,
to get to the Image I want are two extra steps I like to avoid.

I guess thats why I added that feature to PharoLauncher ;)

cheers -ben


Re: [Pharo-users] [Pharo-Launcher] call for tests on Windows

2018-04-16 Thread Richard Sargent
I ran the launcher against my Windows 7 office computer and have created an
issue with my feedback.
https://github.com/pharo-project/pharo-launcher/issues/93



On Mon, Apr 16, 2018 at 7:13 AM, Christophe Demarey <
christophe.dema...@inria.fr> wrote:

> Hi,
>
> Regarding the various problems Pharo Launchers had on Windows, we worked
> on a new installer based on Advanced Installer [1] to avoid UAC (User
> Account Control) and write permissions problems. This new installer now
> installs Pharo Launcher in the user’s local app data folder (where for
> sure, he has write permissions). Pharo Launcher also now have its own icon
> and use its own name instead of Pharo. Also, the uninstaller now works as
> expected. Last but not least, the installer is now signed to avoid warning
> of Windows Defender.
> Thanks to Ben Coman who did the first version of the packaging using
> Advanced Installer (was NSIS).
> This version should also improve the launch of Pharo images on Windows.
>
> So, please could you install and test this new version: and report any
> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/
> We do not have windows users around so it’s hard to know if it works
> outside our tests boxes.
>
> Thanks,
> Christophe
>
> [1] https://www.advancedinstaller.com/
>


Re: [Pharo-users] Pharo Launcher

2018-04-16 Thread Peter Uhnák
On Mon, Apr 16, 2018 at 12:30 PM, Ben Coman  wrote:

> On 16 April 2018 at 16:55, Peter Uhnák  wrote:
> >> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.
> The
> >> app vanished.
> >
> > As I've mentioned in several other threads, the way new images are opened
> > (the lib that executes the command) seems to be very unreliable and
> > sometimes opening image just doesn't work, and I have to open PL again
> and
> > try again.
> >
> > My guess is that there's a race condition and PL closes faster, and
> before
> > the subprocess manages to be disowned.
>
> I untick the box "Quit on Launch"
>


That just turns the problem of "I sometimes have to do extra steps" to "I
always have to do extra steps" (i.e. close PL)


Re: [Pharo-users] Pharo Launcher

2018-04-16 Thread Ben Coman
On 16 April 2018 at 16:55, Peter Uhnák  wrote:
>> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  The
>> app vanished.
>
> As I've mentioned in several other threads, the way new images are opened
> (the lib that executes the command) seems to be very unreliable and
> sometimes opening image just doesn't work, and I have to open PL again and
> try again.
>
> My guess is that there's a race condition and PL closes faster, and before
> the subprocess manages to be disowned.

I untick the box "Quit on Launch"

cheers -ben



Re: [Pharo-users] Pharo Launcher

2018-04-16 Thread Peter Uhnák
> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  The
app vanished.

As I've mentioned in several other threads, the way new images are opened
(the lib that executes the command) seems to be very unreliable and
sometimes opening image just doesn't work, and I have to open PL again and
try again.

My guess is that there's a race condition and PL closes faster, and before
the subprocess manages to be disowned.

Peter

On Mon, Apr 16, 2018 at 3:39 AM, Ben Coman  wrote:

> On 16 April 2018 at 06:02, Benoit St-Jean  wrote:
> > "What path did you install to?"
> >
> >
> > The installer put it in:
> >
> > C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>
>
> To work around the special character in your path, try copying that
> whole folder to C:\BCPharoLauncher
> and directly double-click Pharo.exe.  Then click the Settings tool
> icon and change the Image & VM paths.
>
> Hopefully that will get you going for now, until we sort out a proper fix.
>
> cheers -ben
>
>


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Ben Coman
On 16 April 2018 at 06:02, Benoit St-Jean  wrote:
> "What path did you install to?"
>
>
> The installer put it in:
>
> C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>

To work around the special character in your path, try copying that
whole folder to C:\BCPharoLauncher
and directly double-click Pharo.exe.  Then click the Settings tool
icon and change the Image & VM paths.

Hopefully that will get you going for now, until we sort out a proper fix.

cheers -ben



Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Benoit St-Jean via Pharo-users
--- Begin Message ---
It would be nice if I could uninstall the previous version...  :(
https://pharo.fogbugz.com/f/cases/21705/Pharo-Launcher-cannot-uninstall-on-Windows-10
- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein) 

On Sunday, April 15, 2018, 6:07:15 p.m. EDT, p...@highoctane.be 
 wrote:  
 
 Go to 
http://files.pharo.org/pharo-launcher/bleedingEdge/ 

Install using the MSI, the laucher should go into %APPDATA% and images/vms to 
%DOCUMENTS%/Pharo/...
This is the observed behavior of that new version.
Older versions worked differently on Windows 10.
Best,Phil
On Mon, Apr 16, 2018 at 12:02 AM, Benoit St-Jean via Pharo-users 
 wrote:



-- Forwarded message --
From: Benoit St-Jean 
To: Ben Coman 
Cc: Any question about pharo is welcome , Esteban 
Lorenzano 
Bcc: 
Date: Sun, 15 Apr 2018 22:02:35 + (UTC)
Subject: Re: Pharo Launcher
"What path did you install to?"

The installer put it in:
C:\Users\Benoît St-Jean\AppData\Local\ Programs\Pharo\ BCPharoLauncher>


- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein)


  --- End Message ---


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Benoit St-Jean via Pharo-users
--- Begin Message ---
Tried it, doesn't work.
Changing the .js file didn't change anything.  The problem occurs in the 
image...

Problem seems to be (in my case)
1) the accentuated "Î" which cannot be handled properly in a path FileReference 
(expecting UTF-8 encoding but the string is seen as a Latin-1
2) PlatformResolver>>launcherUserFilesLocation that defaults to my "Documents" 
folder, namely "C:\Users\Benoît St-Jean\Documents", hence the path string 
encoding problem





- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein) 

On Sunday, April 15, 2018, 6:04:22 p.m. EDT, p...@highoctane.be 
 wrote:  
 
 Install the bleeding edge thing, it works for me on win 10. 
I also noticed that the launcher runs images with VMs that do have a weird 
management of cursors in the dark themes, it seems that there the masks are not 
used properly and so, the dark arrow has no white border making it impossible 
to see.It was not like that before, so I suspect a VM thing.
Phil
On Sun, Apr 15, 2018 at 9:00 PM, Hilaire  wrote:

Can you make a search for your PharoDebug.log, because I can see, at least on 
P7 and Linux, this file is not always located nearby the image but at the user 
root directory.

Hilaire


Le 15/04/2018 à 20:52, Benoit St-Jean via Pharo-users a écrit :

Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  The app 
vanished.

Also tried on a brand-new-and-fresh-Windows-10 -machine-with-nothing-previous 
ly-installed and same thing.

The app doesn't even show in the task manager.

And no error file was created.



-- 
Dr. Geo
http://drgeo.eu






  --- End Message ---


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread p...@highoctane.be
Go to

http://files.pharo.org/pharo-launcher/bleedingEdge/

Install using the MSI, the laucher should go into %APPDATA% and images/vms
to %DOCUMENTS%/Pharo/...

This is the observed behavior of that new version.

Older versions worked differently on Windows 10.

Best,
Phil

On Mon, Apr 16, 2018 at 12:02 AM, Benoit St-Jean via Pharo-users <
pharo-users@lists.pharo.org> wrote:

>
>
> -- Forwarded message --
> From: Benoit St-Jean 
> To: Ben Coman 
> Cc: Any question about pharo is welcome ,
> Esteban Lorenzano 
> Bcc:
> Date: Sun, 15 Apr 2018 22:02:35 + (UTC)
> Subject: Re: Pharo Launcher
> "What path did you install to?"
>
>
> The installer put it in:
>
> C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>
>
>
> -
> Benoît St-Jean
> Yahoo! Messenger: bstjean
> Twitter: @BenLeChialeux
> Pinterest: benoitstjean
> Instagram: Chef_Benito
> IRC: lamneth
> Blogue: endormitoire.wordpress.com
> "A standpoint is an intellectual horizon of radius zero".  (A. Einstein)
>
>


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread p...@highoctane.be
Install the bleeding edge thing, it works for me on win 10.

I also noticed that the launcher runs images with VMs that do have a weird
management of cursors in the dark themes, it seems that there the masks are
not used properly and so, the dark arrow has no white border making it
impossible to see.
It was not like that before, so I suspect a VM thing.

Phil

On Sun, Apr 15, 2018 at 9:00 PM, Hilaire  wrote:

> Can you make a search for your PharoDebug.log, because I can see, at least
> on P7 and Linux, this file is not always located nearby the image but at
> the user root directory.
>
> Hilaire
>
>
> Le 15/04/2018 à 20:52, Benoit St-Jean via Pharo-users a écrit :
>
>> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  The
>> app vanished.
>>
>> Also tried on a brand-new-and-fresh-Windows-10
>> -machine-with-nothing-previously-installed and same thing.
>>
>> The app doesn't even show in the task manager.
>>
>> And no error file was created.
>>
>>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>
>


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Benoit St-Jean via Pharo-users
--- Begin Message ---
"What path did you install to?"

The installer put it in:
C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>


- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein)--- End Message ---


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Ben Coman
On 16 April 2018 at 02:52, Benoit St-Jean  wrote:

> "To be clear, the problem was heavily influenced by the constraints of an
> external tool.
> Get PharoLauncher installed in the right location and it works like a
> dream.
> Did you try the proof-of-concept installer I posted previously to the
> list...
> http://www.mediafire.com/file/3g579bmzqspt8e1/BCPharoLauncher.msi
> "
>
> Downloaded it.  Installed it.
>

What path did you install to?

cheers -ben



> Started it.  Selected an image.  Bam.  The app vanished.
>
> Also tried on a 
> brand-new-and-fresh-Windows-10-machine-with-nothing-previously-installed
> and same thing.
>
> The app doesn't even show in the task manager.
>
> And no error file was created.
>
> If that helps, both machines have Windows in French installed.
>


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Benoit St-Jean via Pharo-users
--- Begin Message ---
I looked for it : isn't there.


- 
Benoît St-Jean 
Yahoo! Messenger: bstjean 
Twitter: @BenLeChialeux 
Pinterest: benoitstjean 
Instagram: Chef_Benito
IRC: lamneth 
Blogue: endormitoire.wordpress.com 
"A standpoint is an intellectual horizon of radius zero".  (A. Einstein) 

On Sunday, April 15, 2018, 3:01:30 p.m. EDT, Hilaire  
wrote:  
 
 Can you make a search for your PharoDebug.log, because I can see, at 
least on P7 and Linux, this file is not always located nearby the image 
but at the user root directory.

Hilaire


Le 15/04/2018 à 20:52, Benoit St-Jean via Pharo-users a écrit :
> Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  
> The app vanished.
>
> Also tried on a 
> brand-new-and-fresh-Windows-10-machine-with-nothing-previously-installed 
> and same thing.
>
> The app doesn't even show in the task manager.
>
> And no error file was created.
>

-- 
Dr. Geo
http://drgeo.eu



  --- End Message ---


Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Marten Feldtmann
After a long time I wanted to have a look at the current Pharo situation.

I just downloaded the Linux 64bit version of Pharo from the web site:

-> I opened "pharo" (via a double click on the pharo application) and
got a list of possible templates I could load.

-> I selected Pharo 6.1 template, created an image and wanted to start
that image - the initial application disappeared - but nothing happened
after that.

If I start the initial pharo app from a shell by hand and I want to
start the selected image it seems to work.

My system: Linux Mint 18.1, 64 bit




-- 
Marten Feldtmann



Re: [Pharo-users] Pharo Launcher

2018-04-15 Thread Hilaire
Can you make a search for your PharoDebug.log, because I can see, at 
least on P7 and Linux, this file is not always located nearby the image 
but at the user root directory.


Hilaire


Le 15/04/2018 à 20:52, Benoit St-Jean via Pharo-users a écrit :
Downloaded it.  Installed it.  Started it.  Selected an image.  Bam.  
The app vanished.


Also tried on a 
brand-new-and-fresh-Windows-10-machine-with-nothing-previously-installed 
and same thing.


The app doesn't even show in the task manager.

And no error file was created.



--
Dr. Geo
http://drgeo.eu





Re: [Pharo-users] Pharo Launcher in Windows and Linux

2018-03-26 Thread Stephane Ducasse
I added this issue

https://github.com/pharo-project/pharo-launcher/issues/80

Stef

On Mon, Mar 26, 2018 at 8:09 PM, Stephane Ducasse
 wrote:
> Thanks for the report.
>
>
> On Mon, Mar 26, 2018 at 3:09 PM, horrido  wrote:
>> I've encountered some issues with Pharo Launcher in Windows and Linux. First,
>> in Windows 7, upon starting Pharo Launcher, you get this:
>>
>> *primitive #createDirectory: in WindowsStore failed*
>>
>> If you push through and create an image and then try to launch the image,
>> you get this:
>>
>> *primitive #primSize: in MultiByteFileSystem failed*
>>
>> Completely unusable.
>>
>> Second, in Linux (Manjaro), if you create an image for *Pharo 6.1 (stable)*,
>> and then launch it, you get this:
>>
>> *FT2Error: Freetype2 primitive failed [error -1][can't get error string]*
>>
>> It seems to be usable, though. The issue does not occur with Pharo 6.0.
>>
>> All of this comes from the latest Pharo download at pharo.org/web/download.
>>
>>
>>
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>



Re: [Pharo-users] Pharo Launcher in Windows and Linux

2018-03-26 Thread Stephane Ducasse
Thanks for the report.


On Mon, Mar 26, 2018 at 3:09 PM, horrido  wrote:
> I've encountered some issues with Pharo Launcher in Windows and Linux. First,
> in Windows 7, upon starting Pharo Launcher, you get this:
>
> *primitive #createDirectory: in WindowsStore failed*
>
> If you push through and create an image and then try to launch the image,
> you get this:
>
> *primitive #primSize: in MultiByteFileSystem failed*
>
> Completely unusable.
>
> Second, in Linux (Manjaro), if you create an image for *Pharo 6.1 (stable)*,
> and then launch it, you get this:
>
> *FT2Error: Freetype2 primitive failed [error -1][can't get error string]*
>
> It seems to be usable, though. The issue does not occur with Pharo 6.0.
>
> All of this comes from the latest Pharo download at pharo.org/web/download.
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>



Re: [Pharo-users] Pharo Launcher name

2017-12-17 Thread Sean P. DeNigris
Mariano Martinez Peck wrote
> I also find having it called Pharo quite disturbing. PharoLauncher should
> be much better…

+1. IIRC the original idea was that the launcher would be *the* way new
users would experience Pharo, so it should simply be called "Pharo", but the
term already has a meaning to many people, so IMHO it created more confusion
than anything.



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



Re: [Pharo-users] Pharo Launcher name

2017-12-17 Thread Alexandre Bergel
+1

Envoyé de mon iPhone

> Le 17 déc. 2017 à 15:01, Mariano Martinez Peck  a 
> écrit :
> 
> I also find having it called Pharo quite disturbing. PharoLauncher should be 
> much better. Something that also disturbing is to see the same icon as all my 
> pharo images / VMs. It would be much better if aside from having a different 
> name, it could have a different icon. 
> 
> Cheers,
> 
>> On Sun, Dec 17, 2017 at 2:55 PM, Stephane Ducasse  
>> wrote:
>> I agree with you and we should rename it PharoLauncher.
>> 
>> Stef
>> 
>> On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker  wrote:
>> > I love the Pharo Launcher.  But, I find it confusing to have an application
>> > called “Pharo.app”. Nothing in that name suggests it is a launcher.  It is
>> > also very confusing to have an application called “Pharo.app” next to one
>> > called “Pharo6.1.app” when they are very different things (at least from a
>> > users perspective).
>> >
>> > Has changing the name of the Pharo Launcher to “Pharo Launcher” ever been
>> > considered?
>> >
>> > Just a thought. Most of all, thanks for the wonderful tool.
>> >
>> > Glenn
>> 
> 
> 
> 
> -- 
> Mariano
> http://marianopeck.wordpress.com


Re: [Pharo-users] Pharo Launcher name

2017-12-17 Thread Mariano Martinez Peck
I also find having it called Pharo quite disturbing. PharoLauncher should
be much better. Something that also disturbing is to see the same icon as
all my pharo images / VMs. It would be much better if aside from having a
different name, it could have a different icon.

Cheers,

On Sun, Dec 17, 2017 at 2:55 PM, Stephane Ducasse 
wrote:

> I agree with you and we should rename it PharoLauncher.
>
> Stef
>
> On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker  wrote:
> > I love the Pharo Launcher.  But, I find it confusing to have an
> application
> > called “Pharo.app”. Nothing in that name suggests it is a launcher.  It
> is
> > also very confusing to have an application called “Pharo.app” next to one
> > called “Pharo6.1.app” when they are very different things (at least from
> a
> > users perspective).
> >
> > Has changing the name of the Pharo Launcher to “Pharo Launcher” ever been
> > considered?
> >
> > Just a thought. Most of all, thanks for the wonderful tool.
> >
> > Glenn
>
>


-- 
Mariano
http://marianopeck.wordpress.com


Re: [Pharo-users] Pharo Launcher name

2017-12-17 Thread Stephane Ducasse
I agree with you and we should rename it PharoLauncher.

Stef

On Sun, Dec 17, 2017 at 12:32 AM, Glenn Hoetker  wrote:
> I love the Pharo Launcher.  But, I find it confusing to have an application
> called “Pharo.app”. Nothing in that name suggests it is a launcher.  It is
> also very confusing to have an application called “Pharo.app” next to one
> called “Pharo6.1.app” when they are very different things (at least from a
> users perspective).
>
> Has changing the name of the Pharo Launcher to “Pharo Launcher” ever been
> considered?
>
> Just a thought. Most of all, thanks for the wonderful tool.
>
> Glenn



Re: [Pharo-users] Pharo Launcher name

2017-12-16 Thread Alexandre Bergel
+1

Envoyé de mon iPhone

> Le 16 déc. 2017 à 20:32, Glenn Hoetker  a écrit :
> 
> I love the Pharo Launcher.  But, I find it confusing to have an application 
> called “Pharo.app”. Nothing in that name suggests it is a launcher.  It is 
> also very confusing to have an application called “Pharo.app” next to one 
> called “Pharo6.1.app” when they are very different things (at least from a 
> users perspective).
> 
> Has changing the name of the Pharo Launcher to “Pharo Launcher” ever been 
> considered?
> 
> Just a thought. Most of all, thanks for the wonderful tool.
> 
> Glenn


Re: [Pharo-users] Pharo Launcher name

2017-12-16 Thread Cyril Ferlicot D.
Le 17/12/2017 à 00:32, Glenn Hoetker a écrit :
> I love the Pharo Launcher.  But, I find it confusing to have an
> application called “Pharo.app”. Nothing in that name suggests it is a
> launcher.  It is also very confusing to have an application called
> “Pharo.app” next to one called “Pharo6.1.app” when they are very
> different things (at least from a users perspective).
> 
> Has changing the name of the Pharo Launcher to “Pharo Launcher” ever
> been considered?
> 
> Just a thought. Most of all, thanks for the wonderful tool.
> 
> Glenn

Hi,

I agree. I found it confusing on linux to have a "pharo" script to
launch the pharo launcher.

https://github.com/pharo-project/pharo-launcher/issues/59

-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France



signature.asc
Description: OpenPGP digital signature


Re: [Pharo-users] Pharo Launcher Source

2017-10-05 Thread Stephane Ducasse
Hi Steven

Let us know your progress.

Stef

On Tue, Oct 3, 2017 at 9:57 PM, Steven R. Baker  wrote:
>
>
> On 03/10/17 21:51, Sven Van Caekenberghe wrote:
>>
>>> On 3 Oct 2017, at 21:30, Steven R. Baker  wrote:
>>>
>>> Heya,
>>>
>>> I'm trying to build a Pharo Launcher of my own, but I can't find the
>>> code. This says it's on SmalltalkHub:
>>> https://github.com/pharo-project/pharo-launcher, but the link doesn't
>>> show anything.
>> As it says there: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher
> Sigh. Apologies. I had an overzealous blocker. :(
>
> Thanks!
>
> -Steven
>
>>> I tried looking on CI for the build script, but I can't find the build
>>> script, just build results. What I'm looking for is how to check out,
>>> build, and run Pharo Launcher from scratch. Can someone help me with this?
>>>
>>> Thanks!
>>>
>>> -Steven
>>>
>>>
>>>
>>
>
>



Re: [Pharo-users] Pharo Launcher Source

2017-10-03 Thread Steven R. Baker


On 03/10/17 21:51, Sven Van Caekenberghe wrote:
>
>> On 3 Oct 2017, at 21:30, Steven R. Baker  wrote:
>>
>> Heya,
>>
>> I'm trying to build a Pharo Launcher of my own, but I can't find the
>> code. This says it's on SmalltalkHub:
>> https://github.com/pharo-project/pharo-launcher, but the link doesn't
>> show anything.
> As it says there: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher
Sigh. Apologies. I had an overzealous blocker. :(

Thanks!

-Steven

>> I tried looking on CI for the build script, but I can't find the build
>> script, just build results. What I'm looking for is how to check out,
>> build, and run Pharo Launcher from scratch. Can someone help me with this?
>>
>> Thanks!
>>
>> -Steven
>>
>>
>>
>




Re: [Pharo-users] Pharo launcher on Linux Mint

2017-08-01 Thread Sebastian Heidbrink via Pharo-users
--- Begin Message ---

Hi Christophe,

Thank you for your reply!
I downloaded the latest stable version.
You are right! Not all pharo executable are made executable after 
unzipping again.


I created an issue in Github on this yesterday.

Maybe we have a fix on this soon. I assume that non of the linux 
installations work right now.


Cheers!
Sebastian


Am 01.08.2017 um 00:57 schrieb Christophe Demarey:

Hi Sebastian,

Le 30 juil. 2017 à 18:12, Sebastian Heidbrink via Pharo-users 
> a 
écrit :



*De: *Sebastian Heidbrink >
*Objet: **Pharo launcher on Linux Mint*
*Date: *30 juillet 2017 18:12:07 UTC+2
*À: *Any question about pharo is welcome >


Hi!

I used Pharo launcher on Windows and Ubuntu before and never had any 
troubles.


Now, I am trying to used it on Linux Mint without success.

Once I start the freshly created image the appropriate VM is 
downloaded but the image is not started.



Which version do you use?


A PharoDebug.log is created in the image folder complaining that it 
can't find the PharoVXX.sources files in the 
"pharo/bin/lib/pharo/5.0-201707201942" folder.


After I copy the missing file into that folder the image is still not 
opened and no further logs are created or updated.


I had this problem when updating the launcher because the downloaded 
zip file is unzipped by Pharo itself but ZipArchive does not preserve 
permissions attributes.
To fix that, I 
added PhLVirtualMachineManager>>#ensureIsExecutable:that is called 
right after the Launcher fetch a new VM. It does an OsProcess call to 
add executable permissions.

Has Pharo executable write permissions?

Christophe



--- End Message ---


Re: [Pharo-users] Pharo launcher on Linux Mint

2017-08-01 Thread Christophe Demarey
Hi Sebastian,

> Le 30 juil. 2017 à 18:12, Sebastian Heidbrink via Pharo-users 
>  a écrit :
> 
> 
> De: Sebastian Heidbrink 
> Objet: Pharo launcher on Linux Mint
> Date: 30 juillet 2017 18:12:07 UTC+2
> À: Any question about pharo is welcome 
> Hi!
> 
> I used Pharo launcher on Windows and Ubuntu before and never had any troubles.
> 
> Now, I am trying to used it on Linux Mint without success.
> 
> Once I start the freshly created image the appropriate VM is downloaded but 
> the image is not started.
> 
Which version do you use?
> A PharoDebug.log is created in the image folder complaining that it can't 
> find the PharoVXX.sources files in the "pharo/bin/lib/pharo/5.0-201707201942" 
> folder.
> 
> After I copy the missing file into that folder the image is still not opened 
> and no further logs are created or updated.
> 
I had this problem when updating the launcher because the downloaded zip file 
is unzipped by Pharo itself but ZipArchive does not preserve permissions 
attributes.
To fix that, I added PhLVirtualMachineManager>>#ensureIsExecutable:that is 
called right after the Launcher fetch a new VM. It does an OsProcess call to 
add executable permissions.
Has Pharo executable write permissions?

Christophe

Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-05 Thread Dimitris Chloupis
I'm using 64bit OS for quite some time (aka years) and consider it's
> good sign of some technology to help me avoding fiddling with 32bit
> setup.
>
>
Yeap no doubt there, 64 bit programming languages are pretty much the
standard. I am definitely a supporter of moving to 64 bit and from the
looks of it , maybe I should give 64 bit pharo a try myself, I thought it
was not quite ready yet. Glad I am wrong.


> Do you mind to list some?
>
> Well the ones I care is lack for documentation or outdated documentation,
lack of class method comments and lack of libraries which are the usual
problems for small communities like pharo. I am coming from common lisp
which was not very different. But then there are always pros and cons with
every choice and nonetheless coding in pharo is still a joy for me :)

"
I never heard of this disadvantage of 64 bits before. Are you basically
saing you can't run multiple instances of a 64-bit VM/Image on a
multicore machine?
Can you elaborate?


Joachim
"

Yeah I should have been more clear, no I am not saying that 64-bit VM
cannot do this. I was talking about multiple 32 bit pharo instances against
a single 64 bit pharo instance. A unfair comparison but I was just trying
to make a point.

This ability of multiple instances running on multiple cores is not even a
VM feature, its just normal process handling of the OS. The OS assign each
process to a different core to take better advantage of the processing
power of the CPU.


Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-04 Thread jtuc...@objektfabrik.de

Dimitris,

On Sun, 04 Dec 2016 21:08:20 +

Dimitris Chloupis 
wrote:


The big advantage that 64 bit gives is more memory access , 32 bit has
access to 2 GBs of memory. Even in memory its not such a big deal
because you can launch multiple instances of pharo and take advantage
of your entire memory , the advantage also doing like this  is that
will give you the ability to run pharo on multiple cores something
that a 64 bit VM by itself cannot do anyway, pharo / python / ruby
etc.


I never heard of this disadvantage of 64 bits before. Are you basically 
saing you can't run multiple instances of a 64-bit VM/Image on a 
multicore machine?

Can you elaborate?


Joachim




Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-04 Thread Gour
On Sun, 04 Dec 2016 21:08:20 +
Dimitris Chloupis 
wrote:

> why you care about 64 bit ?

I'm using 64bit OS for quite some time (aka years) and consider it's
good sign of some technology to help me avoding fiddling with 32bit
setup.

> I dont think Pharo is 64 bit ready but it should be soon

OK.

> The big advantage that 64 bit gives is more memory access , 32 bit has
> access to 2 GBs of memory. Even in memory its not such a big deal
> because you can launch multiple instances of pharo and take advantage
> of your entire memory , the advantage also doing like this  is that
> will give you the ability to run pharo on multiple cores something
> that a 64 bit VM by itself cannot do anyway, pharo / python / ruby
> etc.

I admit that I was not thinking about those advantages...

> Lack of 64 bit is definetly not a good reason not to use pharo, 

I agree...it is just curiosity if it is ready for 64bit...

> there are good reasons not to use pharo, but this one is not one of
> them.
 
Do you mind to list some?


Sincerely,
Gour

-- 
Even a man of knowledge acts according to his own nature, for
everyone follows the nature he has acquired from the three modes.
What can repression accomplish?





Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-04 Thread Gour
On Mon, 5 Dec 2016 07:43:51 +0100
Sven Van Caekenberghe  wrote:

> There are some download links in the first post.
> 
> Remember, it is not yet finished, there will be issues.

Thank you...Esteban Lorenzano helped me on the Slack...


Sincerely,
Gour

-- 
One who sees inaction in action, and action in inaction,
is intelligent among men, and he is in the transcendental position,
although engaged in all sorts of activities.





Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-04 Thread Sven Van Caekenberghe
Hi Gour,

See this thread:

http://forum.world.st/Breaking-the-4GB-barrier-with-Pharo-6-64-bit-tt4922305.html

There are some download links in the first post.

Remember, it is not yet finished, there will be issues.

Regards,

Sven

> On 4 Dec 2016, at 14:04, Gour  wrote:
> 
> Hello,
> 
> I was playing with Pharo some time ago, but postponed it a bit until
> seeing 64bit version...on Slack got info that 64bit VM is "very usable
> (as far as you do not use athens)" so I'd appreciate if someone can
> point me to some clear instructions how to install it (I'm on Fedora
> Linux)?
> 
> Is it possible to have PharoLaucnher along with 64bit VM?
> 
> 
> Sincerely,
> Gour
> 
> -- 
> One who is not disturbed in mind even amidst the threefold
> miseries or elated when there is happiness, and who is free
> from attachment, fear and anger, is called a sage of steady mind.
> 
> 
> 




Re: [Pharo-users] Pharo Launcher and 64bit VM

2016-12-04 Thread Dimitris Chloupis
why you care about 64 bit ?
I dont think Pharo is 64 bit ready but it should be soon

The big advantage that 64 bit gives is more memory access , 32 bit has
access to 2 GBs of memory. Even in memory its not such a big deal because
you can launch multiple instances of pharo and take advantage of your
entire memory , the advantage also doing like this  is that will give you
the ability to run pharo on multiple cores something that a 64 bit VM by
itself cannot do anyway, pharo / python / ruby etc.

Lack of 64 bit is definetly not a good reason not to use pharo, there are
good reasons not to use pharo, but this one is not one of them.


On Sun, Dec 4, 2016 at 3:05 PM Gour  wrote:

> Hello,
>
> I was playing with Pharo some time ago, but postponed it a bit until
> seeing 64bit version...on Slack got info that 64bit VM is "very usable
> (as far as you do not use athens)" so I'd appreciate if someone can
> point me to some clear instructions how to install it (I'm on Fedora
> Linux)?
>
> Is it possible to have PharoLaucnher along with 64bit VM?
>
>
> Sincerely,
> Gour
>
> --
> One who is not disturbed in mind even amidst the threefold
> miseries or elated when there is happiness, and who is free
> from attachment, fear and anger, is called a sage of steady mind.
>
>
>
>


Re: [Pharo-users] Pharo Launcher

2016-07-13 Thread Tim Mackinnon
Hi - thanks of the detailed answer, I had to take a break from my investigation 
but I am keen to get it working again.

Its a shame I didn’t spot the survey on the name nomenclature because I liked 
the old system as it makes it much more obvious from the name exactly what you 
are getting - e.g. a Moose Build , vs Pharo 4.0 -  (I would say this, 
as I implemented it). Its a shame you didn’t make it a feature switchable thing 
as I think you’ve lost useful functionality.  I will probably put it back and 
propose it as an option (if it’s veto’d I’ll maintain my own version - but a 
switch should hopefully satisfy everyone).

I’ll also see if we can make it look nice again - as Launcher used to be a good 
showcase of how to make a Pharo app look beautiful.

Tim

> On 28 Jun 2016, at 13:59, Christophe Demarey  
> wrote:
> 
> Hi Tim,
> 
>> Le 27 juin 2016 à 22:12, Tim Mackinnon  a écrit :
>> 
>> Hi guys - I finally got some free time to take a look at Pharo-5 and wanted 
>> Launcher back as well - I just downloaded it on my mac and I’m wondering if 
>> something is wrong?
>> 
>> The UI doesn’t look right (compared to the older 4.x version) - the top 
>> panel is white, and there is a grey run button next to the green one (the 
>> triangle) that seems to be missing transparency - so it all looks quite 
>> ugly. Have I downloaded something that is wrong?
> 
> No, is the current state of Pharo Launcher UI. I did not touch to this part 
> but, yes, could be improved.
> 
>> I also notice, that when I go to create a new image from a template - the 
>> name prompt isn’t as good as the old version which used to include the 
>> parent node in the suggested name so you got something like “Pharo 6.0 
>> (beta) 123455” as a descriptive name - it now just seems to offer “1234456” 
>> as the name now?
> 
> I did this change after a small survey on pharo launcher users that were, 
> like me, bothered with previous proposed names: in most cases, they only want 
> the name of their project. That could be discussed but now, in your example, 
> you get 60121 that is still descriptive. Here, we should find the best 
> proposition for most users, will not for to all.
> 
>> I don’t understand the how the paths work now - it seems that my old images 
>> launch fine, but a 5.x image doesn’t? Do I set the spur path for this - or 
>> is it the other way around (vm-path should be the new vm)? The floating help 
>> isn’t very descriptive on this.
> 
> Pharo launcher is now shipped with both vm (pre-spur and spur). The cog-spur 
> vm now powered PharoLauncher and should be used to run spur images. If not, 
> maybe you have a wrong setting for it. If you remove settings for both VM it 
> should work. Maybe I should remove these settings since both VMs are now 
> shipped with the launcher app. I do not know if it is relevant to some of you 
> to use another VM than the default ones.
> 
> Thanks for the feedback.
> Christophe
> 
>> 
>> Thanks,
>> 
>> Tim
>> 
>> 
>> 
>> Sent from my iPhone
>>> On 17 Jun 2016, at 13:10, Christophe Demarey  
>>> wrote:
>>> 
>>> Now fixed. I replaced the DMG on files.pharo.org.
>>> Thanks for the report
>>> 
> Le 17 juin 2016 à 13:34, Christophe Demarey  
> a écrit :
> 
> 
> Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
> écrit :
> 
> On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
>  wrote:
>> Hi,
>> 
>> I just updated Pharo Launcher. A new version 0.2.11 is available.
>> Here are the change log:
> 
> Great ! Thank you for the update.
> 
>> move Pharo Launcher to the latest stable pharo image: pharo 5.0. It 
>> implies
>> That Pharo Launcher is now shipped with Spur VM.
>> allow an easy download of the new beta image: pharo 6.0
>> the Launcher now comes with 2 VMs:
>> 
>> Spur VM (pharo 5.0 and Pharo 6.0)
>> Non-Spur VM (to be able to run old images)
> 
> I dl the mac version. I was not able to run non-spur VM images: the
> launcher crash or do nothing ...
 
 Indeed, I think it’s a side effect of latest changes I did after testing 
 on Windows.
 I take a look at it now
>> 
>> 
>> 
> 
> 




Re: [Pharo-users] Pharo Launcher

2016-07-13 Thread Tim Mackinnon
I also recall that on OSX (at least some later versions), Apple introduced a 
change whereby if you try and launch another vm from the same vm, it wouldn’t 
open. You had to have a different vm on a different path for it to work 
correctly. 

I will try and resolve my original problem and see if this is still the case.

Tim

> On 28 Jun 2016, at 17:13, Damien Cassou  wrote:
> 
> Christophe Demarey  writes:
>> Pharo launcher is now shipped with both vm (pre-spur and spur). The
>> cog-spur vm now powered PharoLauncher and should be used to run spur
>> images. If not, maybe you have a wrong setting for it. If you remove
>> settings for both VM it should work. Maybe I should remove these
>> settings since both VMs are now shipped with the launcher app. I do
>> not know if it is relevant to some of you to use another VM than the
>> default ones.
> 
> it is at least relevant for me because I cannot use the shipped VMs: I
> have to use the ones of my Linux distribution.
> 
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
> 
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
> 




Re: [Pharo-users] Pharo Launcher

2016-06-28 Thread Damien Cassou
Christophe Demarey  writes:
> Pharo launcher is now shipped with both vm (pre-spur and spur). The
> cog-spur vm now powered PharoLauncher and should be used to run spur
> images. If not, maybe you have a wrong setting for it. If you remove
> settings for both VM it should work. Maybe I should remove these
> settings since both VMs are now shipped with the launcher app. I do
> not know if it is relevant to some of you to use another VM than the
> default ones.

it is at least relevant for me because I cannot use the shipped VMs: I
have to use the ones of my Linux distribution.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill



Re: [Pharo-users] Pharo Launcher

2016-06-28 Thread Christophe Demarey
Hi Tim,

> Le 27 juin 2016 à 22:12, Tim Mackinnon  a écrit :
> 
> Hi guys - I finally got some free time to take a look at Pharo-5 and wanted 
> Launcher back as well - I just downloaded it on my mac and I’m wondering if 
> something is wrong?
> 
> The UI doesn’t look right (compared to the older 4.x version) - the top panel 
> is white, and there is a grey run button next to the green one (the triangle) 
> that seems to be missing transparency - so it all looks quite ugly. Have I 
> downloaded something that is wrong?

No, is the current state of Pharo Launcher UI. I did not touch to this part 
but, yes, could be improved.

> I also notice, that when I go to create a new image from a template - the 
> name prompt isn’t as good as the old version which used to include the parent 
> node in the suggested name so you got something like “Pharo 6.0 (beta) 
> 123455” as a descriptive name - it now just seems to offer “1234456” as the 
> name now?

I did this change after a small survey on pharo launcher users that were, like 
me, bothered with previous proposed names: in most cases, they only want the 
name of their project. That could be discussed but now, in your example, you 
get 60121 that is still descriptive. Here, we should find the best proposition 
for most users, will not for to all.

> I don’t understand the how the paths work now - it seems that my old images 
> launch fine, but a 5.x image doesn’t? Do I set the spur path for this - or is 
> it the other way around (vm-path should be the new vm)? The floating help 
> isn’t very descriptive on this.

Pharo launcher is now shipped with both vm (pre-spur and spur). The cog-spur vm 
now powered PharoLauncher and should be used to run spur images. If not, maybe 
you have a wrong setting for it. If you remove settings for both VM it should 
work. Maybe I should remove these settings since both VMs are now shipped with 
the launcher app. I do not know if it is relevant to some of you to use another 
VM than the default ones.

Thanks for the feedback.
Christophe

> 
> Thanks,
> 
> Tim
> 
> 
> 
> Sent from my iPhone
>> On 17 Jun 2016, at 13:10, Christophe Demarey  
>> wrote:
>> 
>> Now fixed. I replaced the DMG on files.pharo.org.
>> Thanks for the report
>> 
 Le 17 juin 2016 à 13:34, Christophe Demarey  
 a écrit :
 
 
 Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
 écrit :
 
 On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
  wrote:
> Hi,
> 
> I just updated Pharo Launcher. A new version 0.2.11 is available.
> Here are the change log:
 
 Great ! Thank you for the update.
 
> move Pharo Launcher to the latest stable pharo image: pharo 5.0. It 
> implies
> That Pharo Launcher is now shipped with Spur VM.
> allow an easy download of the new beta image: pharo 6.0
> the Launcher now comes with 2 VMs:
> 
> Spur VM (pharo 5.0 and Pharo 6.0)
> Non-Spur VM (to be able to run old images)
 
 I dl the mac version. I was not able to run non-spur VM images: the
 launcher crash or do nothing ...
>>> 
>>> Indeed, I think it’s a side effect of latest changes I did after testing on 
>>> Windows.
>>> I take a look at it now
> 
> 
> 




Re: [Pharo-users] Pharo Launcher

2016-06-27 Thread Tim Mackinnon
Hi guys - I finally got some free time to take a look at Pharo-5 and wanted 
Launcher back as well - I just downloaded it on my mac and I’m wondering if 
something is wrong?

The UI doesn’t look right (compared to the older 4.x version) - the top panel 
is white, and there is a grey run button next to the green one (the triangle) 
that seems to be missing transparency - so it all looks quite ugly. Have I 
downloaded something that is wrong?

I also notice, that when I go to create a new image from a template - the name 
prompt isn’t as good as the old version which used to include the parent node 
in the suggested name so you got something like “Pharo 6.0 (beta) 123455” as a 
descriptive name - it now just seems to offer “1234456” as the name now?

I don’t understand the how the paths work now - it seems that my old images 
launch fine, but a 5.x image doesn’t? Do I set the spur path for this - or is 
it the other way around (vm-path should be the new vm)? The floating help isn’t 
very descriptive on this.

Thanks,

Tim



Sent from my iPhone
> On 17 Jun 2016, at 13:10, Christophe Demarey  
> wrote:
> 
> Now fixed. I replaced the DMG on files.pharo.org.
> Thanks for the report
> 
>>> Le 17 juin 2016 à 13:34, Christophe Demarey  a 
>>> écrit :
>>> 
>>> 
>>> Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
>>> écrit :
>>> 
>>> On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
>>>  wrote:
 Hi,
 
 I just updated Pharo Launcher. A new version 0.2.11 is available.
 Here are the change log:
>>> 
>>> Great ! Thank you for the update.
>>> 
 move Pharo Launcher to the latest stable pharo image: pharo 5.0. It implies
 That Pharo Launcher is now shipped with Spur VM.
 allow an easy download of the new beta image: pharo 6.0
 the Launcher now comes with 2 VMs:
 
 Spur VM (pharo 5.0 and Pharo 6.0)
 Non-Spur VM (to be able to run old images)
>>> 
>>> I dl the mac version. I was not able to run non-spur VM images: the
>>> launcher crash or do nothing ...
>> 
>> Indeed, I think it’s a side effect of latest changes I did after testing on 
>> Windows.
>> I take a look at it now





Re: [Pharo-users] Pharo Launcher

2016-06-17 Thread Serge Stinckwich
Thank you Christophe ! Works now.

But I have some stability problems, after launching some images,
PharoLauncher freeze ...
But this is not a new problems. I had the same issue before.

Regards

On Fri, Jun 17, 2016 at 1:10 PM, Christophe Demarey
 wrote:
> Now fixed. I replaced the DMG on files.pharo.org.
> Thanks for the report
>
>> Le 17 juin 2016 à 13:34, Christophe Demarey  a 
>> écrit :
>>
>>>
>>> Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
>>> écrit :
>>>
>>> On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
>>>  wrote:
 Hi,

 I just updated Pharo Launcher. A new version 0.2.11 is available.
 Here are the change log:
>>>
>>> Great ! Thank you for the update.
>>>
 move Pharo Launcher to the latest stable pharo image: pharo 5.0. It implies
 That Pharo Launcher is now shipped with Spur VM.
 allow an easy download of the new beta image: pharo 6.0
 the Launcher now comes with 2 VMs:

 Spur VM (pharo 5.0 and Pharo 6.0)
 Non-Spur VM (to be able to run old images)
>>>
>>> I dl the mac version. I was not able to run non-spur VM images: the
>>> launcher crash or do nothing ...
>>
>> Indeed, I think it’s a side effect of latest changes I did after testing on 
>> Windows.
>> I take a look at it now
>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/



Re: [Pharo-users] Pharo Launcher

2016-06-17 Thread Christophe Demarey
Now fixed. I replaced the DMG on files.pharo.org.
Thanks for the report

> Le 17 juin 2016 à 13:34, Christophe Demarey  a 
> écrit :
> 
>> 
>> Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
>> écrit :
>> 
>> On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
>>  wrote:
>>> Hi,
>>> 
>>> I just updated Pharo Launcher. A new version 0.2.11 is available.
>>> Here are the change log:
>> 
>> Great ! Thank you for the update.
>> 
>>> move Pharo Launcher to the latest stable pharo image: pharo 5.0. It implies
>>> That Pharo Launcher is now shipped with Spur VM.
>>> allow an easy download of the new beta image: pharo 6.0
>>> the Launcher now comes with 2 VMs:
>>> 
>>> Spur VM (pharo 5.0 and Pharo 6.0)
>>> Non-Spur VM (to be able to run old images)
>> 
>> I dl the mac version. I was not able to run non-spur VM images: the
>> launcher crash or do nothing ...
> 
> Indeed, I think it’s a side effect of latest changes I did after testing on 
> Windows.
> I take a look at it now




Re: [Pharo-users] Pharo Launcher

2016-06-17 Thread Christophe Demarey

> Le 17 juin 2016 à 12:00, Serge Stinckwich  a 
> écrit :
> 
> On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
>  wrote:
>> Hi,
>> 
>> I just updated Pharo Launcher. A new version 0.2.11 is available.
>> Here are the change log:
> 
> Great ! Thank you for the update.
> 
>> move Pharo Launcher to the latest stable pharo image: pharo 5.0. It implies
>> That Pharo Launcher is now shipped with Spur VM.
>> allow an easy download of the new beta image: pharo 6.0
>> the Launcher now comes with 2 VMs:
>> 
>> Spur VM (pharo 5.0 and Pharo 6.0)
>> Non-Spur VM (to be able to run old images)
> 
> I dl the mac version. I was not able to run non-spur VM images: the
> launcher crash or do nothing ...

Indeed, I think it’s a side effect of latest changes I did after testing on 
Windows.
I take a look at it now


Re: [Pharo-users] Pharo Launcher

2016-06-17 Thread Serge Stinckwich
On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey
 wrote:
> Hi,
>
> I just updated Pharo Launcher. A new version 0.2.11 is available.
> Here are the change log:

Great ! Thank you for the update.

> move Pharo Launcher to the latest stable pharo image: pharo 5.0. It implies
> That Pharo Launcher is now shipped with Spur VM.
> allow an easy download of the new beta image: pharo 6.0
> the Launcher now comes with 2 VMs:
>
> Spur VM (pharo 5.0 and Pharo 6.0)
> Non-Spur VM (to be able to run old images)

I dl the mac version. I was not able to run non-spur VM images: the
launcher crash or do nothing ...

Regards,
-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/



Re: [Pharo-users] Pharo launcher in homebrew cask

2016-03-22 Thread Damien Pollet
FYI I was also thinking of creating a homebrew tap for pharo (VM etc).
Still at the draft stage, unfortunately.

On 22 March 2016 at 13:00, Damien Cassou  wrote:

> Filip Krikava  writes:
>
> > I find Pharo launcher incredibly useful and I was surprised not to find
> it
> > in homebrew cask [1]. Pharo itself is there. I have therefore created a
> PR:
> > https://github.com/caskroom/homebrew-cask/pull/19956
>
> I don't know homebrew-cask but I imagine that it is better to reference
> stable files on the web rather than continuously changing files. At
> least, that's true for the package manager I package(d) for. If that's
> also the case here, I would recommend to use a file from:
>
> http://files.pharo.org/platform/launcher/blessed/
>
> Files there don't change. If you are interested, I can move OS X releases
> there the same way I do it for Linux releases.
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
>
>


Re: [Pharo-users] Pharo launcher in homebrew cask

2016-03-22 Thread Damien Cassou
Filip Krikava  writes:

> I find Pharo launcher incredibly useful and I was surprised not to find it
> in homebrew cask [1]. Pharo itself is there. I have therefore created a PR:
> https://github.com/caskroom/homebrew-cask/pull/19956

I don't know homebrew-cask but I imagine that it is better to reference
stable files on the web rather than continuously changing files. At
least, that's true for the package manager I package(d) for. If that's
also the case here, I would recommend to use a file from:

http://files.pharo.org/platform/launcher/blessed/

Files there don't change. If you are interested, I can move OS X releases
there the same way I do it for Linux releases.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill



Re: [Pharo-users] Pharo launcher in homebrew cask

2016-03-21 Thread Serge Stinckwich
Great !
Thank you Filip

On Mon, Mar 21, 2016 at 9:09 PM, Filip Krikava  wrote:
> Hi,
>
> I find Pharo launcher incredibly useful and I was surprised not to find it
> in homebrew cask [1]. Pharo itself is there. I have therefore created a PR:
> https://github.com/caskroom/homebrew-cask/pull/19956
>
> /cheers
> Filip
>
> [1] https://github.com/caskroom/homebrew-cask



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/



Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread Ronie Salgado
I think that we should have a Pharo-bugs mailing list that gets notified
for each bug that is filled in fogbugz

2015-03-21 4:54 GMT-03:00 kilon alios kilon.al...@gmail.com:


 Bottom line is that reporting a problem in the mailing list first makes
 much more sense because

 a) Way more likely to get an answer
 b) Avoid adding to the list on non existent bugs in fogbugz
 c) Bring the bug if it really exists to the attention of more people,
 hence increase that chance of the bug getting a fix.
 d) Far easier to remind people of the bug later on by just bumping on the
 thread which everyone on the list will get notified compared to fogbugz
 that if you are not subscribed to a bug you wont be notified.

 So yes definitely want to discourage people from starting from fogbugz.
 Also personally I dont like fogbugz because its so isolated.

 On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com wrote:







 On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de
 wrote:

 Hi,

 I recently mentioned issues with the installation of the pharo-launcher
 on Windows 8.1

 Turned out I just needed to download the PharoV30.sources file and
 place into the installation folder.

 Now everything seems fine.

 Is this also a topic for the pharo bug list, or is there another place
 where I can mention this?

 Sebastian



 On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com
  wrote:

 there is also an options in settings that downloads and install sources
 for you automagically.

 This is the right place to report issues and if you are 100% sure its a
 bug you can report it also in the pharo fogbuz



 100% is a bit strong and sounds a bit discouraging :).As long as you
 can list the detailed steps reproduce the problem, then its worth putting
 in fogbugz.  However fogbugz has a lot of old issues and sometimes a new
 issue is like a lost tree in the forrest.   Its generally beneficial if you
 socialise it on the mail list as well.

 A good workflow is:
 1. Search fogbugz for similar issues.
 2. Ask on the mail list if its a known issue, or if you should create a
 new one. List your steps to reproduce and ideally a solution.
 3. Log a new issue on fogbugz, copying the mail list discussion there.
 Paste the link back to the mail list thread.

 So in general:
 * the mail list has a broader audience and gets a better triage
 * fogbugz tracks history to ensure it doesn't get lost - and nothing
 happens except what goes through the tracker.  (btw, set Project=Launcher)

 cheers -ben





Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread kilon alios
Bottom line is that reporting a problem in the mailing list first makes
much more sense because

a) Way more likely to get an answer
b) Avoid adding to the list on non existent bugs in fogbugz
c) Bring the bug if it really exists to the attention of more people, hence
increase that chance of the bug getting a fix.
d) Far easier to remind people of the bug later on by just bumping on the
thread which everyone on the list will get notified compared to fogbugz
that if you are not subscribed to a bug you wont be notified.

So yes definitely want to discourage people from starting from fogbugz.
Also personally I dont like fogbugz because its so isolated.

On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com wrote:







 On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de
 wrote:

 Hi,

 I recently mentioned issues with the installation of the pharo-launcher
 on Windows 8.1

 Turned out I just needed to download the PharoV30.sources file and place
 into the installation folder.

 Now everything seems fine.

 Is this also a topic for the pharo bug list, or is there another place
 where I can mention this?

 Sebastian



 On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com
  wrote:

 there is also an options in settings that downloads and install sources
 for you automagically.

 This is the right place to report issues and if you are 100% sure its a
 bug you can report it also in the pharo fogbuz



 100% is a bit strong and sounds a bit discouraging :).As long as you
 can list the detailed steps reproduce the problem, then its worth putting
 in fogbugz.  However fogbugz has a lot of old issues and sometimes a new
 issue is like a lost tree in the forrest.   Its generally beneficial if you
 socialise it on the mail list as well.

 A good workflow is:
 1. Search fogbugz for similar issues.
 2. Ask on the mail list if its a known issue, or if you should create a
 new one. List your steps to reproduce and ideally a solution.
 3. Log a new issue on fogbugz, copying the mail list discussion there.
 Paste the link back to the mail list thread.

 So in general:
 * the mail list has a broader audience and gets a better triage
 * fogbugz tracks history to ensure it doesn't get lost - and nothing
 happens except what goes through the tracker.  (btw, set Project=Launcher)

 cheers -ben



Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread stepharo

Nice idea!
I think that we should have a Pharo-bugs mailing list that gets 
notified for each bug that is filled in fogbugz


2015-03-21 4:54 GMT-03:00 kilon alios kilon.al...@gmail.com 
mailto:kilon.al...@gmail.com:



Bottom line is that reporting a problem in the mailing list first
makes much more sense because

a) Way more likely to get an answer
b) Avoid adding to the list on non existent bugs in fogbugz
c) Bring the bug if it really exists to the attention of more
people, hence increase that chance of the bug getting a fix.
d) Far easier to remind people of the bug later on by just bumping
on the thread which everyone on the list will get notified
compared to fogbugz that if you are not subscribed to a bug you
wont be notified.

So yes definitely want to discourage people from starting from
fogbugz. Also personally I dont like fogbugz because its so isolated.

On Sat, Mar 21, 2015 at 2:15 AM, Ben Coman b...@openinworld.com
mailto:b...@openinworld.com wrote:





On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink
shei...@yahoo.de mailto:shei...@yahoo.de wrote:

Hi,

I recently mentioned issues with the installation of
the pharo-launcher on Windows 8.1

Turned out I just needed to download the
PharoV30.sources file and place into the installation
folder.

Now everything seems fine.

Is this also a topic for the pharo bug list, or is
there another place where I can mention this?

Sebastian

On Sat, Mar 21, 2015 at 1:46 AM, kilon alios
kilon.al...@gmail.com mailto:kilon.al...@gmail.com wrote:

there is also an options in settings that downloads
and install sources for you automagically.

This is the right place to report issues and if you
are 100% sure its a bug you can report it also in the
pharo fogbuz



100% is a bit strong and sounds a bit discouraging :).As
long as you can list the detailed steps reproduce the problem,
then its worth putting in fogbugz.  However fogbugz has a lot
of old issues and sometimes a new issue is like a lost tree in
the forrest.   Its generally beneficial if you socialise it on
the mail list as well.

A good workflow is:
1. Search fogbugz for similar issues.
2. Ask on the mail list if its a known issue, or if you should
create a new one. List your steps to reproduce and ideally a
solution.
3. Log a new issue on fogbugz, copying the mail list
discussion there. Paste the link back to the mail list thread.

So in general:
* the mail list has a broader audience and gets a better triage
* fogbugz tracks history to ensure it doesn't get lost - and
nothing happens except what goes through the tracker.  (btw,
set Project=Launcher)

cheers -ben







Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread Alain Rastoul

Le 21/03/2015 14:08, stepharo a écrit :

Nice idea!

I think that we should have a Pharo-bugs mailing list that gets
notified for each bug that is filled in fogbugz


Yes that would be nice, when you look at bugs on fogbugz site, you do 
not always see that it is discussed in the list (lot of threads)



--
Regards,

Alain




Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread Ben Coman
On Sat, Mar 21, 2015 at 9:55 PM, Alain Rastoul alf.mmm@gmail.com
wrote:

 Le 21/03/2015 14:08, stepharo a écrit :

 Nice idea!

 I think that we should have a Pharo-bugs mailing list that gets
 notified for each bug that is filled in fogbugz


 Yes that would be nice, when you look at bugs on fogbugz site, you do not
 always see that it is discussed in the list (lot of threads)


It would be nice, but btw will not address that situation.  Parties
interested in the issue woudl still need to copy mail list discussion
there, or link to the mail archive of the discussion.  Fogbugz should hold
case history.
cheers -ben


Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-21 Thread Alain Rastoul

Le 22/03/2015 03:36, Ben Coman a écrit :

It would be nice, but btw will not address that situation.  Parties
interested in the issue woudl still need to copy mail list discussion
there, or link to the mail archive of the discussion.  Fogbugz should
hold case history.
cheers -ben


You are right if you see the discussion in the list.
I recently added a note to a case without seeing it was discussed in the 
list and think it was not the good place.
A separate list for bugs (threads in the list do not allways clearly 
link to the bugs and they are lot of various threads) may have helped.

With a tag in the title in case of opened bugs.
I agree that fogbugz should hold the history.

--
Regards,

Alain




Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-20 Thread Ben Coman

 On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de
 wrote:

 Hi,

 I recently mentioned issues with the installation of the pharo-launcher
 on Windows 8.1

 Turned out I just needed to download the PharoV30.sources file and place
 into the installation folder.

 Now everything seems fine.

 Is this also a topic for the pharo bug list, or is there another place
 where I can mention this?

 Sebastian



 On Sat, Mar 21, 2015 at 1:46 AM, kilon alios kilon.al...@gmail.com
  wrote:

 there is also an options in settings that downloads and install sources
 for you automagically.

 This is the right place to report issues and if you are 100% sure its a
 bug you can report it also in the pharo fogbuz



100% is a bit strong and sounds a bit discouraging :).As long as you
can list the detailed steps reproduce the problem, then its worth putting
in fogbugz.  However fogbugz has a lot of old issues and sometimes a new
issue is like a lost tree in the forrest.   Its generally beneficial if you
socialise it on the mail list as well.

A good workflow is:
1. Search fogbugz for similar issues.
2. Ask on the mail list if its a known issue, or if you should create a new
one. List your steps to reproduce and ideally a solution.
3. Log a new issue on fogbugz, copying the mail list discussion there.
Paste the link back to the mail list thread.

So in general:
* the mail list has a broader audience and gets a better triage
* fogbugz tracks history to ensure it doesn't get lost - and nothing
happens except what goes through the tracker.  (btw, set Project=Launcher)

cheers -ben


Re: [Pharo-users] Pharo-Launcher Windows 8.1

2015-03-20 Thread kilon alios
there is also an options in settings that downloads and install sources for
you automagically.

This is the right place to report issues and if you are 100% sure its a bug
you can report it also in the pharo fogbuz

On Fri, Mar 20, 2015 at 7:04 PM, Sebastian Heidbrink shei...@yahoo.de
wrote:

 Hi,

 I recently mentioned issues with the installation of the pharo-launcher on
 Windows 8.1

 Turned out I just needed to download the PharoV30.sources file and place
 into the installation folder.

 Now everything seems fine.

 Is this also a topic for the pharo bug list, or is there another place
 where I can mention this?

 Sebastian




Re: [Pharo-users] Pharo-Launcher does not launch image in Ubuntu

2015-02-27 Thread Damien Cassou
Could you please try to download the launcher image from Jenkins and start
this image manually? This will help us understand if the problem comes from
the launcher or the Ubuntu package
On Feb 26, 2015 7:26 AM, nacho 0800na...@gmail.com wrote:

 Hi,
 pharo-launcher starts perfectly, I can even download i.e. the latest Pharo
 4
 beta, but when trying to launch that image I receive the following error
 200
 times or more until pharo closes

 *** stack smashing detected ***: /usr/lib/pharo-vm/pharo-vm terminated
 output file stack is full.

 I did some chowns to /usr/lib/pharo-vm /usr/share/pharo-vm and
 /usr/share/pharo-launcher
 Even run pharo as root
 But nothing seems to work
 I loaded ppa:pharo/unstable
 I'm using Netrunner 15 x86_64 (which is based in Ubuntu Utopic)
 Thanks in advance for any help.
 Nacho




 -
 Nacho
 Smalltalker apprentice.
 Buenos Aires, Argentina.
 --
 View this message in context:
 http://forum.world.st/Pharo-Launcher-does-not-launch-image-in-Ubuntu-tp4807805.html
 Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.




Re: [Pharo-users] pharo-launcher ppa - 32-bit OS problem

2014-08-01 Thread Damien Cassou
Hi Ben,

On Fri, Aug 1, 2014 at 5:47 AM, Ben Coman b...@openinworld.com wrote:
 I successfully used the Ubuntu ppa instructions at
 http://pharo.org/download


could you please try a ppa-purge for ppa:pharo/stable and then
add-apt-repository ppa:pharo/unstable (not the *unstable* part that is
different from the standard instructions). I hope it works better.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

Success is the ability to go from one failure to another without
losing enthusiasm.
Winston Churchill



Re: [Pharo-users] pharo-launcher ppa - 32-bit OS problem

2014-08-01 Thread Ben Coman




Damien Cassou wrote:

  Hi Ben,

On Fri, Aug 1, 2014 at 5:47 AM, Ben Coman b...@openinworld.com wrote:
  
  
I successfully used the "Ubuntu ppa" instructions at
http://pharo.org/download

  
  

could you please try a ppa-purge for ppa:pharo/stable and then
add-apt-repository ppa:pharo/unstable (not the *unstable* part that is
different from the standard instructions). I hope it works better.

  

# There was a minor problem with the purge which I cleaned up manually.
Note 'qiana' is the Linux Mint 17 release.
$ sudo apt-get purge pharo-launcher-test
$ pharo
bash: /usr/bin/pharo: No such file or directory

$ sudo ppa-purge ppa:pharo/stable
PPA to be removed: pharo stable
Package revert list generated:
 pharo-vm-core/qiana pharo-vm-desktop/qiana
Disabling pharo PPA from
/etc/apt/sources.list.d/pharo-stable-trusty.list
E: Release 'qiana' for 'pharo-vm-core' was not found
E: Release 'qiana' for 'pharo-vm-desktop' not found

$ dpkg --get-selections | grep pharo
pharo-vm-core install
pharo-vm-desktop install
$ sudo apt-get purge pharo-vm-core pharo-vm-desktop 
$ dpkg --get-selections | grep pharo
# nothing

$ sudo add-apt-repository ppa:pharo/unstable
$ sudo apt-get update
$ sudo apt-get install pharo-launcher
$ pharo
# works like a charm

Thanks Damien.

btw...
$ dpkg --get-selections | grep pharo
pharo-launcher install
pharo-sources-files install
pharo-vm-core install
pharo-vm-core-i386 install
pharo-vm-desktop install

cheers -ben





Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

2014-07-25 Thread Tim Mackinnon
I've tried it at home and it works fine, yesterday it didn't work in the
office (just 4.0 and 2.0) - some there must be some weird networking going
on in that office.

Anyway - glad I can use it at home, as its a very handy launcher!

Thanks for creating it, and to those helping maintain it.

Tim



--
View this message in context: 
http://forum.world.st/Pharo-launcher-network-error-for-Pharo-4-0-beta-tp4769383p4770061.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.



Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

2014-07-25 Thread Damien Cassou
On Fri, Jul 25, 2014 at 1:17 PM, Tim Mackinnon tamackin...@gmail.com wrote:
 I've tried it at home and it works fine, yesterday it didn't work in the
 office (just 4.0 and 2.0) - some there must be some weird networking going
 on in that office.


if there is anything you can do to the source code to make it work at
your office, please do and share. Thank you

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

Success is the ability to go from one failure to another without
losing enthusiasm.
Winston Churchill



Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

2014-07-22 Thread Damien Cassou
On Tue, Jul 22, 2014 at 4:59 PM, Tim Mackinnon tamackin...@gmail.com wrote:
 I was quite enjoying using Pharo Launcher - but today I am getting network 
 error for the Pharo4.0 (beta) and Pharo 2.0 (old) trees?

 Has something changed?


I'm very surprised, it works for me. Could you please try again? Can
you download from http://files.pharo.org/image/40/ manually ?

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

Success is the ability to go from one failure to another without
losing enthusiasm.
Winston Churchill



Re: [Pharo-users] Pharo launcher network error for Pharo 4.0 (beta)?

2014-07-22 Thread Tim Mackinnon
Yes its weird - I can view  http://files.pharo.org/image/40/ fine in a web
browser. It seems to affect 4.0 and 2.0.

3.0 and RModJenkins etc all expand correctly.

The status bar was saying 4 network errors (although checking now, it says
7).

It could be connectivity in this office, so I can check it from home - but
it seems weird that some work and others don't.

Tim



--
View this message in context: 
http://forum.world.st/Pharo-launcher-network-error-for-Pharo-4-0-beta-tp4769383p4769414.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.