[Pharo-users] [launcher] Re: PharoLauncher howto (was: SimplePersistence ...)

[btc]

Norbert Hartl wrote: Am 21.11.2013 um 17:01 schrieb Torsten Bergmann <asta...@gmx.de>: Hope this helps a little bit Yeah, thanks for your effort. I saw what you were mentioning but I needed confirmation that I didn’t miss the most important feature :) Ok, so it is just not a tool for me. I have a project folders containing not only smalltalk stuff but also documentation and other files. The project folders are grouped by companies I work for. So central storage of images is a no-go. I do it the other way round. I have one directory where I symlink all current projects folders into. And this directory I put in the MacOS bar to have quick access. Then I open an image once and save a new version regularly using „save as“. This is a must for me because I experience a lot of image instability and the changes is broken so too easy to loose code. And it wouldn’t work the way you told me because I save images often so copying _before_ opening an image is not an option. My workflow just needs manual setup of the projects folder which I would like to be solved somewhat more clever. But as I can see it now I need to stick to my stuff. Sad. I think PharoLauncher is nice. Norbert Sounds like you need PharoLauncher to have features like: * open the newest image in a project folder and maybe also clean out the project folder by moving older images into an archive folder. * tree structured Images pane, with roots each having a different directory * tracking branches in the sequence of image saves. Do you backtrack much to a previous image?  Another feature that I contemplate is synchronizing between PharoLauncher on different machines. For example, for when you want to push a new release to your client.  You would right-click on an image, choose 'Send to client' which would upload to some web location (perhaps just dropbox).  PharoLauncher at the client would set up to refresh/poll that location, and automate download and launching the image.  This might also work in reverse...  if a problem occurs in the application, they might SaveAs the image including the error and use PharoLauncher to upload the image to somewhere you poll then download it.   btw, How often to you create new company folders and project folders?  cheers -ben