PharoLauncher as the default Pharo download on pharo.org?

On 23 Dec 2013, at 01:17, Johan Fabry <[hidden email]> wrote:

This is wrong. A mac user not ever touch his songs directly, it uses iTunes, yet his music files are at "Music/iTunes Music”, not hidden.  
Same applies for pharo images. Even if you are not going to touch them, you still want them in a visible place (for copying, backing, sharing, etc.). Or just because.
The default folder has to be Documents/Pharo, not some hard to access place.

A pharo image is NOT an obscure configuration library. Is much more like a document or a song than a preference.  

On 23 Dec 2013, at 14:05, Esteban Lorenzano <[hidden email]> wrote:

Ah… and vmware and parallels also keep their images by default at Documents folder.

On Fri, Dec 20, 2013 at 11:45 AM, Sven Van Caekenberghe <[hidden email]> wrote:
> I would start by featuring it more prominently on the download page while explaining clearly what it does. Maybe it also needs its own documentation/promotion web page.


that's a chicken and egg problem. If nobody uses it, we can't make it
very visible on the pharo.org website but if we don't, nobody will use
it.

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

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

On Fri, Dec 20, 2013 at 1:34 PM, Mark Bestley <[hidden email]> wrote:
> 1) Setting of the default directories - these should be more Apple standard
> i.e. images not in preferences and even better in a Sandbox so eventually
> could be available via App Store which would increase the number of people
> who would see it. (I have use the settings to change the directory for me.)


I changed the default directories on all systems:

- mac: ~/Library/Application Support/Pharo/images
- win: %APPDATA%\Pharo\images
- unix: ~/.local/share/Pharo/images

And everyone can change these values to what they want like a dropbox
folder (just go to the launcher settings, change the path, and save).


> 2) Dealing with saved images. If you do a save as.. the this new image does
> not show in the launcher.
> I think there are two ways of fixing this
> i) don't put images and source in sub directories
> ii) Make the save as in Pharo create a sub directory


agree. I think I will try another solution

iii) when launching an image, if multiple ones are present, let the
user select with a drop-down. These ways, the concept of a "launcher's
image" can still be seen as a project whereas the .image files can be
seen as versions of this project.


> Point ii) leads onto making the save of an image save to an OSX bundle (i.e.
> a directory containing several files that OSX can see as one unit)


I don't understand that


> 3) The icons need to have more responsive pop-overs to explain what they
> do.(I almost wrote any pop-over but after a minute I can get them 30% of the
> time)


I don't understand that as well


> 4) For first time users I think the right pane needs a look at - users will
> not know which is the correct template to use. I would suggest making the
> Pharo latest stable a top level entry and highlighting that.


agree, I will fix that

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

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

On 27 Jan 2014, at 17:12, Damien Cassou <[hidden email]> wrote:

I already told you: I think this is conceptually wrong. Images has to go (by default) into "~/Documents/Pharo Images". (Same as VMWare virtual machines go into "~/Documents/Virtual Machines" and parallels into “~/Documents/Parallels"
al the rest: +1 :)

Esteban

On Fri, Dec 20, 2013 at 3:28 PM, kilon alios <[hidden email]> wrote:
> A problem I have with pharoLaunher is that I want to help out to improve it
> but I cant for the life of me figure out the code. I think the most
> important thing is to document it so it will allow people like me to improve
> it easier. I dont expect anyone to tell me exactly how each method works but
> at least how the overall code works should be a good start. Because I dont
> want to fight with the code to understand it. I spend many hours with it,
> still cant figure it out .


I don't know how to help. Please tell me where are the problems. What I did:

- comment nearly all classes
- rename each method at least 3 times
- categorize all methods
- write unit-tests
- answer all questions I got about the code

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

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

2014-01-27 Esteban Lorenzano <[hidden email]>
> On 27 Jan 2014, at 17:12, Damien Cassou <[hidden email]> wrote:
> > I changed the default directories on all systems:
> >
> > - mac: ~/Library/Application Support/Pharo/images
> > - win: %APPDATA%\Pharo\images
> > - unix: ~/.local/share/Pharo/images
>
> I already told you: I think this is conceptually wrong. Images has to go (by default) into "~/Documents/Pharo Images". (Same as VMWare virtual machines go into "~/Documents/Virtual Machines" and parallels into “~/Documents/Parallels"
> al the rest: +1 :)

+1 on this.

%APPDATA% is for data that the end user would never have to access
directly. Remember that such dir is hidden.

I remember this discussion in the Dolphin Smalltalk newsgroup almost a
decade ago, when somebody asked why Dolphin installed the images in
the "My Documents" folder. At that time Andy Bower pointed to a
guideline doc with the proper reasons (which I happen to not
remember).

On the other hand, the executable was installed in the %ProgramFiles%
directory, and some commons in the "%ProgramFiles%\Common Files", that
were shared between different versions of Dolphin.

Regards,

Esteban.

On Jan 27, 2014, at 2:20 PM, Esteban A. Maringolo <[hidden email]> wrote:

>>> - mac: ~/Library/Application Support/Pharo/images
>>> - win: %APPDATA%\Pharo\images
>>> - unix: ~/.local/share/Pharo/images
>>
>> I already told you: I think this is conceptually wrong. Images has to go (by default) into "~/Documents/Pharo Images". (Same as VMWare virtual machines go into "~/Documents/Virtual Machines" and parallels into “~/Documents/Parallels"
>> al the rest: +1 :)
>
> +1 on this.

+1 as well

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile