Re: [Pharo-users] [ann] gt documenter

Hi, I am happy you like it. Fonts should work with a Pharo 64b installation on Linux, including Manjaro. Can you confirm that you use a Pharo 64bit and that it does not work? If yes, can you describe how you are installing Pharo and GToolkit? Markdown is certainly interesting, but it is not

Re: [Pharo-users] How to contribute to Pharo Launcher?

Le 14/06/2018 à 21:04, Esteban Lorenzano a écrit : > > > The main maintainer is Christophe, which I know feels a lot more confortable > with git than with monticello. > So, I guess reason of not moving it is other :) > > Maybe is time for moving it? > If there is no other reason than "nobody

Re: [Pharo-users] How to contribute to Pharo Launcher?

> On 14 Jun 2018, at 20:56, Cyril Ferlicot D. wrote: > > Le 14/06/2018 à 18:48, Tim Mackinnon a écrit : > > Hi, > > >> Is PharoLauncher using git - there is a note saying the StHub repo is about >> to be moved? >> > > For now it is still on STHub. Maybe because the main maintainers are

Re: [Pharo-users] How to contribute to Pharo Launcher?

Le 14/06/2018 à 18:48, Tim Mackinnon a écrit : Hi, > Is PharoLauncher using git - there is a note saying the StHub repo is about > to be moved? > For now it is still on STHub. Maybe because the main maintainers are more efficient with Monticello than with github? Maybe the main maintainers

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

2018-06-14 15:39 GMT+02:00 Tim Mackinnon : > Yes - I’m a fan of small checkins (not always great at it, but I strive > for it) - and yes, the issue I’ve had is the same as what Thierry mentions > - my Smalltalk code is tied to an external file which has some rewrite > rules that depend on the

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Yes - I’m a fan of small checkins (not always great at it, but I strive for it) - and yes, the issue I’ve had is the same as what Thierry mentions - my Smalltalk code is tied to an external file which has some rewrite rules that depend on the classes I have in my image. I could possibly

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi Norbert, Tim, 2018-06-14 11:33 GMT+02:00 Norbert Hartl : > > > Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : > > Hi - yes I’m pleased you check out the entire tree, although currently > it’s a bit confusing that you do (fortunately this does give the > possibility that we can checkout images

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : > > Hi - yes I’m pleased you check out the entire tree, although currently it’s a > bit confusing that you do (fortunately this does give the possibility that we > can checkout images and other resources that an Pharo application might rely >

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

BTW, addFilesToIndex: will not add files to the git index immediately, it will do it just before a commit only. On Thu, Jun 14, 2018 at 11:03 AM Guillermo Polito wrote: > addFileToIndex: and addFilesToIndex: are still there... > > We of course have support for changing and committing arbitrary

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

addFileToIndex: and addFilesToIndex: are still there... We of course have support for changing and committing arbitrary files (actually, pharo code at the end are just arbitrary files!). The difficult part is to bring a consistent UI to life for it... On Thu, Jun 14, 2018 at 10:43 AM Tim

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Ooooh - I didn’t know about #addToIndex: that sounds like a possible workaround to my problem (but not a generic solution though). BTW - I don’t want this to be a criticism, I’m loving the tools and their possibilities! Tim Sent from my iPhone > On 14 Jun 2018, at 09:36, Peter Uhnák wrote:

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Wait... so it is no longer possible to #addtoIndex: external files from Pharo? I thought that this functionality was supposed to be preserved. Peter On Thu, Jun 14, 2018 at 10:30 AM, Tim Mackinnon wrote: > Hi - yes I’m pleased you check out the entire tree, although currently > it’s a bit

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi - yes I’m pleased you check out the entire tree, although currently it’s a bit confusing that you do (fortunately this does give the possibility that we can checkout images and other resources that an Pharo application might rely on - without having to resort to the Seaside FileLibrary

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi Guille - I have tried the repo browser with the new iceberg loaded in Pharo 6.1 and I couldn’t see how it helps me? (I will make a firm point of using 7 now as I think I’ve now got a reasonable grasp of how things should work). From the threads below - how would I find the commit with my

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Just to complement Esteban's answer: - Iceberg checks out in disk more than the src directory because you **may** want to edit files from the command line, and after long discussions we did not want to forbid that. Actually, just to put everybody in perspective, at first the idea was to not have

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

Hi, Regarding history, right now we have a history browser implemented as a Calypso plugin, that is open using context menu => history or the little box button on the top right of the method pane (second button from the left in the picture): [image: Screen Shot 2018-06-14 at 09.34.24.png] That