Re: [Pharo-users] [ANN] Pharo Pomodoro now on GitHub

Thanks Torsten! Is it pure morphic or you’ve updated it to spec? This could be a nice little example to show the mechanisms to do async ui update. > El 13 ago 2019, a las 12:10, Torsten Bergmann escribió: > > I migrated my Pomodoro timer project to GitHub now: > >

Re: [Pharo-users] Information on Spec development

Thanks for pushing this Cyril! This will let us move forward with Iceberg too :) > El 13 ago 2019, a las 12:15, Cyril Ferlicot > escribió: > > On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot > wrote: >> >> Hello everyone! >> >> This is an important update

Re: [Pharo-users] [ANN] Pharo Chip Designer

haha looks fun :) > El 10 ago 2019, a las 13:15, Pavel Krivanek > escribió: > > Hi, > > I have created a little program based on an old educational game by > Zachtronics (KOHCTPYKTOP: Engineer of the People[1]) named Pharo Chip > Designer. > > It is an inaccurate and highly simplified

Re: [Pharo-users] Following Git(Hub) History

> El 6 ago 2019, a las 0:48, Sean P. DeNigris escribió: > > Does anyone have any strategies for following git histories past code > reorganizations (see steps #2 and #5 below)? > > My typical experience is: > 1. Do blame or history on a file > 2. Follow it back to the inevitable "convert to

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

I’ve created an issue: https://github.com/pharo-vcs/iceberg/issues/1251 <https://github.com/pharo-vcs/iceberg/issues/1251> > El 18 jun 2019, a las 9:30, Guillermo Polito > escribió: > > Hi Esteban, > > It seems like a bug in Iceberg. If you click on debug, you’ll see

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

Hi Esteban, It seems like a bug in Iceberg. If you click on debug, you’ll see that although you’ve said the project is in tonel format, it’s trying to use a Filetree reader This is due to some missing metadata in the commit (iceberg is relying on commit information there and not working copy

Re: [Pharo-users] Smalltalk-Bolivia at ICSE SRC 2019

Super news :) congratulations! > El 4 jun 2019, a las 19:42, Ben Coman escribió: > > This is really great to hear people's success. Thanks for sharing. > cheers -ben > > On Wed, 5 Jun 2019 at 00:34, Juan Pablo Sandoval Alcocer > wrote: > Hi, > > We would like to

Re: [Pharo-users] Pharo 7 minimal or headless

Hola Bruno, The full archive of Pharo7 images is in http://files.pharo.org/image/70/. There you'll find latest-minimal-[arch].zip for 64 and 32 bits. On Wed, May 8, 2019 at 7:03 PM BrunoBB wrote: > Hi Esteban, > > I'm looking for Pharo 64 minimal (to use in Linux) but i can not find any > at >

Re: [Pharo-users] Getting example images - https://picsum.photos

This makes me remember when I was working doing android mobile apps: there is a kitten placeholder service too. https://placekitten.com/ And status codes too https://http.cat/ ZnEasy getJpeg: 'https://placekitten.com/200/300'. :) On Wed, May 1, 2019 at 10:41 AM Franz Josef Konrad wrote:

Re: [Pharo-users] What's wrong with latest Pharo?

Hi Tim, Looking at the resolution of the libgit library, I see that in pharo7 the following: LGitLibrary >> unixModuleName | pluginDir | pluginDir := Smalltalk vm binary parent. #('libgit2.so' 'libgit2.so.0') detect: [ :each | (pluginDir / each) exists ] ifFound: [ :libName | ^ libName ]. self

Re: [Pharo-users] Screencasts on Debugger driven development

Thanks! we need more of this :) On Tue, Apr 9, 2019 at 5:49 PM stephan wrote: > Some work Vincent Blondeau and I have been doing on the Taskbar > has inspired me to make some screencasts showing how to do > debugger driven development, and take the first steps towards > refactoring the

Re: [Pharo-users] Smalltalk CI - anyone have any luck excluding tests?

Hi Tim, I got something like what you describe that working for pillar and OSSubprocess, but putting different tests in different packages, not tags. https://github.com/pillar-markup/pillar https://github.com/pharo-contributions/OSSubprocess On Tue, Mar 12, 2019 at 6:00 PM Tim Mackinnon wrote:

Re: [Pharo-users] What does mean "Detached Working Copy" in Iceberg ?

Hi Bruno, Take a look at the glossary here: https://github.com/pharo-vcs/iceberg/wiki/Iceberg-glossary Any feedback (I'm sure many improvements can be done!) is super welcome! Guille On Thu, Feb 21, 2019 at 2:18 PM BrunoBB wrote: > Hi, > > We have in our server Gitolite instance running. >

Re: [Pharo-users] How do you avoid loading master code which is indirectly referenced by a version in the baseline?

Hi Sabine, maybe you want to have a look at metacello lock. https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloScriptingAPI.md On Tue, Feb 19, 2019 at 1:06 PM Tim Mackinnon wrote: > Hi Sabine - you raise an important point, and I am interested in us > getting better

Re: [Pharo-users] Iceberg working with forks - can it be easier?

ects all (static) dependencies in the same branch, and proposes you doing a commit/merge of that. I don't know how far are we from this, but it would be super nice to do easy backporting between branches (think pharo8 -> pharo7). Guille Thanks in advance. > > Tim > > On 18 Feb

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 7:50 AM Konrad Hinsen wrote: > Am 18.02.19 um 01:19 schrieb Tim Mackinnon: > > > Hey Ben - I’m not sure that this actually does the same thing. I just > > tried it now, and it resulted in an extra merge in my forked repo - as I > > think this effectively pulls down from

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 2:45 AM Sean P. DeNigris wrote: > Tim Mackinnon wrote > > wouldn’t it be helpful if this was a command in Iceberg? > > Yes! This is a super common task and for easy cases would be great to > automate > https://help.github.com/articles/syncing-a-fork/ > > > That's useful

Re: [Pharo-users] Iceberg working with forks - can it be easier?

On Mon, Feb 18, 2019 at 1:19 AM Tim Mackinnon wrote: > Hey Ben - I’m not sure that this actually does the same thing. I just > tried it now, and it resulted in an extra merge in my forked repo - as I > think this effectively pulls down from upstream into pharo and then if you > have any

Re: [Pharo-users] Iceberg working with forks - can it be easier?

Hi! On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon wrote: > Hi guys - I’ve spent a few hours scratching my head trying to understand > why some of my Pull Requests to a project I had forked kept showing my > previous commits when I thought I was all caught up. > > It suddenly dawned on me, that

Re: [Pharo-users] Porting Github packages to Pharo 7

at 10:29 AM Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > Hi Guillermo > > El jue., 31 ene. 2019 a las 6:08, Guillermo Polito (< > guillermopol...@gmail.com>) escribió: > >> Hi Hernán, >> >> On Thu, Jan 31, 2019 at 8:20 AM Hernán Morale

Re: [Pharo-users] Porting Github packages to Pharo 7

Hi Hernán, On Thu, Jan 31, 2019 at 8:20 AM Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > I would like your advice on this: What's the effortless way to migrate > Github repository from Pharo 6 to Pharo 7? > Can you give us some more detail? Do you already have your project in

Re: [Pharo-users] [ANN] P3 version 1.1

--- Begin Message --- Thanks Sven :) On Tue, Jan 1, 2019 at 11:54 PM Tudor Girba via Pharo-users < pharo-users@lists.pharo.org> wrote: > Very cool. Thanks! > > Doru > > > > On Dec 31, 2018, at 12:33 PM, Sven Van Caekenberghe > wrote: > > > > Hi, > > > > I created a new release of P3, the

Re: [Pharo-users] Some issues with Pharo and Ubuntu

Hi, On Mon, Dec 17, 2018 at 4:38 PM Vitor Medina Cruz wrote: > Hello, > > I am trying Pharo with Docker and I will leave here some issues I had > since I am unsure where I should report them. > http://bugs.pharo.org should be the correct place. > The command I am running is: > > Metacello

Re: [Pharo-users] Usage of String and FileLocator to reference files in ZipArchive (and probably other places)

Hi Hans, Sorry for the late reply. On Sun, Nov 25, 2018 at 9:30 PM Hans-Martin wrote: > I found a related problem which indicates that the depreciation of > StandardFileStream in favor of File is incomplete and probably premature: > When a ZipArchive is written, in 7.0 it uses >

Re: [Pharo-users] chooseExistingFileReference:extensions:path:preview returning wrong FileReference?

Hi all, I've created issue https://pharo.fogbugz.com/f/cases/22772/chooseExistingFileReference-extensions-path-preview-returning-wrong-FileReference And proposed a single-line fix: https://github.com/pharo-project/pharo/pull/2075 I've tested those scenarios and it was working but some more

Re: [Pharo-users] [pharo7] loading mcz files

PR with fix: https://github.com/pharo-project/pharo/pull/2062 On Wed, Dec 12, 2018 at 3:46 PM Guillermo Polito wrote: > I've opened an issue here: > > > https://pharo.fogbugz.com/f/cases/22754/Exception-while-opening-a-MCSubDirectoryRepository > > The reason is that several p

Re: [Pharo-users] [pharo7] loading mcz files

Hi Hans, I'm trying to reproduce this one. It seems it happens only with a "Directory with subdirectories" kind of repository. Can you confirm? I do now know exactly what this should do, never used it before. I'll check it and come back to you. Guille On Wed, Dec 12, 2018 at 12:46 PM Baveco,

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo v7.0.0-rc1 released!

On Wed, Nov 14, 2018 at 3:50 PM Baveco, Hans wrote: > On windows 7 the 32bits version opens with an error: “PrimitiveFailed: > primitive #fileDescriptorType: in File class failed.” > > When discarding the error and saving & quitting the image, subsequent > startups (via the launcher) do not

Re: [Pharo-users] problem when running without changes file (on windows)

Hi Hans, On Wed, Nov 14, 2018 at 2:56 PM Baveco, Hans wrote: > Ok, thanks for this crucial information! Would backporting be as simple as > filing out the class and the single method from Pharo7 and filing in in > Pharo6.1 ? (probably not) > While not completely sure, I think they actually

Re: [Pharo-users] problem when running without changes file (on windows)

Still, in Pharo6 the absense of changes and sources files means also that FFI calls cannot be done. UFFI uses the method source code to map arguments, and if no source code is available, FFI calls cannot be resolved. This is solved in Pharo7 thanks to Vincent Blondeau by embedding argument names

Re: [Pharo-users] using latest iceberg with Pharo 6.1 / 7.0

On Fri, Nov 2, 2018 at 6:25 PM Sanjay Minni wrote: > If I want to use iceberg then should I first update pharo image as > mentioned > on github iceberg homepage (https://github.com/pharo-vcs/iceberg) > I'd also insist here with Sven. Could you please explain better what are you trying to

Re: [Pharo-users] finding dependees of a package

On Sun, Oct 7, 2018 at 10:06 PM Cyril Ferlicot D. wrote: > Le 07/10/2018 à 21:44, Peter Uhnak a écrit : > > Hi, > > > > I know I can "Browse Dependencies" of a particular package, but this > > only shows me the dependencies of the selected package X. > > > > What I am looking for is a list of

Re: [Pharo-users] Iceberg - better control of project name?

On Tue, Oct 2, 2018 at 6:54 PM Ben Coman wrote: > > > On Tue, 2 Oct 2018 at 15:52, Guillermo Polito > wrote: > >> - Maybe, for old projects that don't have a name, we could initialize a >> project's name as it's repository name? >> > > In any case, I'd

Re: [Pharo-users] Metacello load baselines/configurations only

On Wed, Oct 3, 2018 at 9:28 AM Norbert Hartl wrote: > > > > Am 03.10.2018 um 08:34 schrieb Peter Uhnak : > > > > Hi, > > > > is there a way to instruct Metacello to only install > BaselineOfs/ConfigurationOfs instead of the entire project? For the > purposes of analyzing dependencies. > > >

Re: [Pharo-users] Iceberg - better control of project name?

Issue: https://github.com/pharo-vcs/iceberg/issues/1009 On Tue, Oct 2, 2018 at 10:02 AM Guillermo Polito wrote: > Aaand the mail got sent before :) > > Then two other comments that are related or I'd like to discuss: > - So far we can allow in iceberg several projects with t

Re: [Pharo-users] Iceberg - better control of project name?

n Tue, Oct 2, 2018 at 9:51 AM Guillermo Polito wrote: > Yes, I agree with most of the comments here. I'll try to summarize: > > - we should be able to specify the name of a project independently of > their location/repository name > - Maybe, for old projects that don't have a

Re: [Pharo-users] Iceberg - better control of project name?

Yes, I agree with most of the comments here. I'll try to summarize: - we should be able to specify the name of a project independently of their location/repository name - Maybe, for old projects that don't have a name, we could initialize a project's name as it's repository name? On Tue, Oct

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

everone to take care. I need to take care more > about what I write. But people that get easily offended should see that is > the other part of the problem. > > Norbert > > > Am 29.09.2018 um 01:13 schrieb Cyril Ferlicot D. < > cyril.ferli...@gmail.com>: > > >

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

On Sat, Sep 29, 2018 at 1:05 AM Guillermo Polito wrote: > I'm sorry if I offended somebody. I've deleted the repository (it was > under pharo-repository, not under my name). With it the changes I made to > make it work on Pharo7. > > I understand that Peter's tool is easy, i've

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

, Sep 28, 2018 at 9:19 PM Norbert Hartl wrote: > > > Am 28.09.2018 um 10:14 schrieb Guillermo Polito >: > > > > On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann wrote: > >> Hi Guille, >> >> Yes, thanks. But it looks like the history is gone n

Re: [Pharo-users] [ANN] Migrated Artefact to GitHub

On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann wrote: > Hi Guille, > > Yes, thanks. But it looks like the history is gone now - as you seem to > load and then commited > with Iceberg only. > Yes, that's what I did. > > By using Peters "STHub -> Git migration tool" the history of the changes

[Pharo-users] [ANN] Migrated Artefact to GitHub

Hi all, I've moved the Artefact library to GitHub ( https://github.com/pharo-contributions/Artefact). I've also made some changes to it in the way and made a 1.7.0 version with: - support for Pharo7 streams - a baseline So, people using Artifact, you can contribute through pull requests ^^,

Re: [Pharo-users] MIDI IO

Hi Manuel, I don't know the state of the Midi Plugin, but for sure it would not be difficult to make some bindings to an existing library with uFFI. Check for example http://jedi.ks.uiuc.edu/~johns/projects/midid/ Guille On Fri, Sep 21, 2018 at 1:34 PM Manuel Leuenberger wrote: > Hi, > > I am

Re: [Pharo-users] is class-side name setter used by the system

Hi Peter, On Mon, Sep 17, 2018 at 9:57 AM Peter Uhnak wrote: > Hi, > > is the class-side "name:" setter used by the system itself? > Because I remember many times overriding it for my own needs and it never > broke anything as far as I know... which makes it strange why it even > exists

Re: [Pharo-users] Internet of Things in Smalltalk - meeting proposal

I'll be there :) On Mon, Sep 10, 2018 at 4:09 PM Cédrick Béler wrote: > Hi, > > We will have a meeting Tuesday afternoon on IoT at esug. > > More info later to see how we organize that. > > Should be after « show us your project » around 5 or 6 am. > > More info later especially on where the

Re: [Pharo-users] Pharo 6 snap package

Hi all, Nope, I'm not maintaining my package. I was experimenting with it at some point (2 years ago?) and then saw somebody else started with a more complete solution so I've not continued working on it. Personally, I've experienced the same sandboxing problems stated by Alistair, plus the fact

Re: [Pharo-users] Why is there no #assert:notEquals: or #shouldnt:equal: or #deny:equals: method?

Personally I think that SUnit needs love. - The API is clearly not clear (just see: the command line handler, smalltalk ci, calypso and the test runner tool use different APIs that are not equivalent and do not go through the same hooks) - The existing hooks are not enough and not well

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

On Thu, Aug 9, 2018 at 11:18 AM Norbert Hartl wrote: > > > Am 08.08.2018 um 14:12 schrieb Herbert Vojčík : > > > > Damien Pollet wrote on 8. 8. 2018 13:53: > > First of all, quick stupid question: I'm currently loading my code with > gitlocal://./src as the repository URL (my workflow starts in

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

> > [SNIP] > I think I can see what is the rationale behind it but I’m not sure this > can be the way to go: > > - I don’t think there can be a „standard way“ of defining source > directory. And I don’t think that a tool should enforce this however. I > keep frontend and backend code in some

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

Hi Marcus, Is it wise to backport things that may break things like this? I'd prefer to put the energy on backporting the workaround to avoid the infinite debuggers... On Thu, Aug 9, 2018 at 10:50 AM Marcus Denker wrote: > > 2) when coding - if you want reference a missing class, why don’t we

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

Hi Tim, I can only tell you that I agree with you ^^. Last year we worked with Stef and Luc on the idea of undefined classes ( https://hal.archives-ouvertes.fr/hal-01585305/document). The code is available in smalltalkhub if I remember well (check the links in the paper). We did not integrate

Re: [Pharo-users] [Pharo-dev] New Iceberg Version 1.2.1

Hi, I'll write down some of the reasons of the project's design, like that I can afterwards copy paste it in the wiki :). First, this design did not came up from an egg. We worked on it for about two months. And it is thought to be backwards compatible and manage lots of metacello

Re: [Pharo-users] safely determining whether ProcessWrapper process is running

Hi, Sorry for the delay On Sat, Jun 30, 2018 at 7:38 PM Peter Uhnák wrote: > Hi, > > I feel like I am missing something obvious, but is there a _safe_ way to > test if PW is still running? > I don't think so. ProcessWrapper primitives are not safe. If they are not called in the right order,

Re: [Pharo-users] BS Web and Pharo

+1 I don't know how to solve it, but I agree it bothers me... Of course at some point I started ignoring it, but I imagine it can create a bad impression for people from outside the community. On Thu, Aug 2, 2018 at 6:15 PM Tim Mackinnon wrote: > > Hey guys - when reading about the BS web

Re: [Pharo-users] Pharo 7 file streams guideline

On Wed, Aug 1, 2018 at 11:19 AM Guillermo Polito wrote: > > > On Tue, Jul 31, 2018 at 6:41 PM Damien Pollet < > damien.pollet+ph...@gmail.com> wrote: > >> On Tue, 31 Jul 2018 at 18:28, Damien Pollet < >> damien.pollet+ph...@gmail.com> wr

Re: [Pharo-users] Pharo 7 file streams guideline

On Tue, Jul 31, 2018 at 6:41 PM Damien Pollet wrote: > On Tue, 31 Jul 2018 at 18:28, Damien Pollet > wrote: > >> Hi Sven… a couple questions: >> > > For context, I'm considering options in Clap, for providing accessors to > Stdio that: > - are convenient in most cases > - discourage users from

Re: [Pharo-users] Pharo 7 file streams guideline

On Tue, Jul 31, 2018 at 6:29 PM Damien Pollet wrote: > Hi Sven… a couple questions: > > - is there a preferred order of composition between the encoding and > buffering streams ? If yes, it the same for read and write stream, or > reversed ? > E.g. if Stdio binaryStdin was implemented, Stdio

Re: [Pharo-users] Using Icerberg programmatically.

Hi Arturo, First, I would not recommend too much to use the version on Pharo 6.1. That version is a preview version that is >6 months older than the new one in Pharo 7. This does not mean you cannot write a script, but we do not guarantee it will work in more recent version :). If you then

Re: [Pharo-users] Changing a BaselineOf... to include one more package

Hi Andrew, Sorry for the late reply, On Wed, Jul 11, 2018 at 4:31 PM Andrew P. Black wrote: > Hi Guillermo, > > Thanks for the explanation. I guess that I really don't have much idea > how this baseline stuff is supposed to work, so when it fails, I don't know > where to look. > > My initial

[Pharo-users] Tonel class comments

Hi all, Since people have been asking how to use Tonel, I've took a look at it and have written down two class comments for both the reader and the writer. I'll push them to Tonel and schedule soon a patch release with it. Here are the class comments so people can see them/discusses them. Please,

Re: [Pharo-users] Changing a BaselineOf... to include one more package

:29 AM Guillermo Polito wrote: > Hi Andrew, > > I'd say you got almost everything right. Let me try to guide you to fix > what's not so well and see if you can make it work. > > On Sun, Jul 8, 2018 at 4:19 PM Andrew P. Black wrote: > >> I have a baselineOfGrace that has

Re: [Pharo-users] Changing a BaselineOf... to include one more package

Hi Andrew, I'd say you got almost everything right. Let me try to guide you to fix what's not so well and see if you can make it work. On Sun, Jul 8, 2018 at 4:19 PM Andrew P. Black wrote: > I have a baselineOfGrace that has been working fine for some time: > > baseline: spec > > > spec for:

Re: [Pharo-users] Pharo stable version with git support

Hi Dario, > i'm interested to port all my code to new Pharo version that >> manage git support. >> >> I found information in pharo.org news, it talk of Pharo 6.1. >> >> But it run only on macOS 64bits o i can run it on Linux Ubuntu >> 16.04 LTS System? >> >> New

Re: [Pharo-users] Instance of IceUnknownBranch did not understand #id

I'd like to add that I don't think that plain Metacello will work with private repositories. Metacello will try to load a zip ball from your project and I really doubt that github/bitbucket/gitlab provide you with that anonymously... On Fri, Jul 6, 2018 at 5:08 PM Hernán Morales Durand <

Re: [Pharo-users] Instance of IceUnknownBranch did not understand #id

Hi Hernán, On Wed, Jul 4, 2018 at 7:57 PM Hernán Morales Durand < hernan.mora...@gmail.com> wrote: > I wonder if anyone could help here. I am installing a BaselineOf in > Pharo 6.1 (Windows) Unfortunately this version of Iceberg is too old... I'd go with what Esteban describes and try to see

Re: [Pharo-users] Code porting to Pharo 6.1-64

Hi Dario, Have you defined those methods in the class side? a) propertyAt: aKey ifAbsent: aBlock >^ self properties at: aKey ifAbsent: aBlock > b) propertyAt: aKey ifAbsentPut: aBlock >^ self properties at: aKey ifAbsentPut: aBlock > c)

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

> You mentioned a Calypso plugin for versions - where is that? I loaded a recentish P7 image and I don’t see those icons? Is this something I can easily load to try out? As soon as a class is inside a package that is managed by iceberg, you should see in Calypso a new button and menu item on

Re: [Pharo-users] pharo bash script with startup

That's strange, is this a new problem or you always had it? I've just tested it, pharo 61 64 bits. $ wget -O - https://get.pharo.org/64/61+vm | bash [SNIP] $ ./pharo Pharo.image eval 1+1 2 Maybe the so called starter scripts (pharo, pharo-ui) are not the same using zeroconf and by downloading

[Pharo-users] [Ann] OSSubprocess v1.0.1

Hi all, There is a new version of OSSubprocess available. This is a Bugfix release. This release fixes a problem with waitpid that happened regularly and randomly in OSSubprocess users mostly in the CI. For those interesting, the details of the bug can be read in:

Re: [Pharo-users] Pharo 7, Iceberg, Proxy and Windows

Hi Vitor, I've created an issue with your problem. https://github.com/pharo-vcs/iceberg/issues/885 I encourage you to do so too, because following the mailing list is sometimes hard :) About your second issue, you should know that libgit ( libgit2.github.com/libgit2) will mostly bypass git and

Re: [Pharo-users] How to contribute to Calypso when it relies on pharo-core editors?

On Wed, Jun 20, 2018 at 1:47 PM Ben Coman wrote: > > > On 20 June 2018 at 15:38, Guillermo Polito > wrote: > >> Hi Tim, >> >> Yes, there you're experiencing the limits of our current process. We were >> studying the usage of git subtrees/submodules/subrepo

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

read it using Tonel? I don't know exactly how to use tonel directly, I'll let others answer better. > > Tim > > Sent from my iPhone > > > > Sent from my iPhone > On 14 Jun 2018, at 08:52, Guillermo Polito > wrote: > > Hi, > > Regarding history, right now

Re: [Pharo-users] How to contribute to Calypso when it relies on pharo-core editors?

Hi Tim, Yes, there you're experiencing the limits of our current process. We were studying the usage of git subtrees/submodules/subrepos but none of them seem a satisfying solution for what would give us a smooth contribution process. Now, we can enhance a bit the current status by adding

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

menu too, for experienced users that want to avoid an extra click. On Tue, Jun 19, 2018 at 5:57 PM Guillermo Polito wrote: > Ah! Yes, in the Pharo plugin you have just that option. > What we were saying with Esteban is that if you go to the *Repair* and > then *Create new Branch* you sh

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

using my caught up branch) - when I right click on the detached > pharo - there is the Pharo menu item and inside that there is only the > option to create a new branch for an issue? > > Am I missing something (or is this something recently broken?) > > Tim > > On 19 Jun 2018,

Re: [Pharo-users] Project dependency management with Iceberg

Hi, On Tue, Jun 19, 2018 at 3:16 PM Vitor Medina Cruz wrote: > Hello, > > How do I do project dependency management with Iceberg? > This is still Metacello. > I tried sometime ago but I was unable to understand how it work together > with Metacello, is there some tutorial available? > Well,

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

r now, I found a bug and created an issue, and so can experiment with > that - but I think it is handy to create a generic branch so that you can > experiment (while easily tracking your changes)? > > Tim > > On 19 Jun 2018, at 14:01, Guillermo Polito > wrote: > > Hi, > > On Tue,

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl wrote: > Hi, > > let me wear the project manager hat for a moment. > let me too, because the fact that I'm younger does not mean I don't know, right? :) > > Am 19.06.2018 um 10:59 schrieb Guillermo Polito >: > &

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Hi, On Tue, Jun 19, 2018 at 2:26 PM Tim Mackinnon wrote: > Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the > instructions seemed to work really well. > > I’ve since come back to try and do some more over lunch (I was thinking > I’d like to dig out the changes I worked out for

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

lle On Mon, Jun 18, 2018 at 9:12 PM Torsten Bergmann wrote: > Great - thank you! Might be a small patch release - but nonetheless > important. > > BTW: the links in your mail are pointing to PR's of Pharo and not Iceberg. > If you used > a template you might want to consid

[Pharo-users] [Ann] Iceberg v1.1.1

Hi everybody, This week we have a small patch release of Iceberg, version v1.1.1. This version will be available in the next Pharo build. In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. Below you will find the

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

Hi Tim, On Fri, Jun 15, 2018 at 10:31 AM Tim Mackinnon wrote: > > In many parts of the dev world - every commit should be shippable, meaning > atomic - particularly with the use of CI systems (Travis, Gitlab etc) that > build on every commit. > > Of course you can choose to work a different way

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

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

could jump to IntelliJ and do the final commit >> there and use its tools to manage non Pharo stuff (until we can build more)? >> >> Does this make sense? >> >> As an aside - I’d really like to checkin in the play-xxx directories (the >> .ph files) as there is

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

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.0

someone would like to help on that front, making use of ProcessWrapper in the tests should not be difficult (it was done before but that code rot because of the lack of CI in the past...) > > Cheers, > > Hernán > > > 2018-06-11 14:04 GMT-03:00 Guillermo Polito : > > Time for th

[Pharo-users] [Ann] Iceberg v1.1.0

Time for the weekly Iceberg update. Thanks to all brave users, issue reporters and contributors :). Key changes: we have introduced some tag support, a new credential manager to manage keys and passwords per host or repository, a new version of tonel, and made a first step towards a simplified

Re: [Pharo-users] Problem to use GZIPReadStream

Hi Serge, What Pharo version are you on? What is your `file` object? If `file` is a FileReference, you need to know that by default, using `readStream` provides now an encoded file (to keep backwards compatibility with what most users were doing until now). And I think that GZip should just

Re: [Pharo-users] Loading Local Repositories with Iceberg

On Tue, Jun 5, 2018 at 8:20 AM, Norbert Hartl wrote: > > > > Am 04.06.2018 um 15:59 schrieb Esteban Lorenzano : > > > > hi, > > > >> On 4 Jun 2018, at 12:57, Stephan Eggermont wrote: > >> > >> Evan Donahue wrote: > >>> I have "Share repositories between images" checked in both images, > >> >

Re: [Pharo-users] [ANN] Iceberg v1.0.0

the only difference is you have to change “0.7.?” with “1.0.?” (I need to > update that). > Done https://github.com/pharo-vcs/iceberg/commit/acd66a0b5cc22ffe1317434f9bc41b809b70571c > > Esteban > > > Thanks! > Andrei > > On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito &l

[Pharo-users] [ANN] Iceberg v1.0.0

Hi all, Time for a new Iceberg update, that will be available in the next Pharo build. This time, there are lots of cleanups and enhancements. On the big highlights: - Tonel migration plugin is available in the "Other menu item" - Tests are green on 64 bits! (meaning iceberg can be safely used

Re: [Pharo-users] pharo location include korean charactor then look is not good.

On Fri, May 25, 2018 at 10:49 AM, Sven Van Caekenberghe wrote: > We looked at this before, but came to no conclusion. > > The problem lies with OS environment variable decoding. > I don't think that the window title comes from an OS env var. This should be some encoding missing in

Re: [Pharo-users] pharo location include korean charactor then look is not good.

That's probably that the font used to render window titles is different than the one used for text... Check here: http://pharo.org/contribute All the information for issue reporting should be there :) Tx! On Fri, May 25, 2018 at 4:09 AM, peter yoo wrote: > so..

Re: [Pharo-users] Reverting changes in Iceberg

Hi Even, what Pharo version are you using? What Iceberg version (the one that comes by default)? If you're in Pharo 6 with the default iceberg version, I'd suggest you to: - update iceberg - or just fix it from the command line $ git reset --hard HEAD~1 should do what you want. If you

Re: [Pharo-users] im using pharo in wayland system.

Hi Peter, would you mind testing latest Pharo7 also and telling us if you see some similar problem? Several things were improved in the freetype bindings since Pharo6, and probably this is fixed?. Tx, Guille On Thu, May 24, 2018 at 2:06 PM, peter yoo wrote: > hello! im

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

Aaand, I've updated https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo On Thu, May 24, 2018 at 11:34 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > https://github.com/pharo-vcs/iceberg/wiki/The-Working-Copy(ies) > https://github.com/pharo-vcs/

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

https://github.com/pharo-vcs/iceberg/wiki/The-Working-Copy(ies) https://github.com/pharo-vcs/iceberg/wiki/Branching-and-Merging On Thu, May 24, 2018 at 11:30 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi, > > I'll take some minutes to provide an answer as detai

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

Hi, I'll take some minutes to provide an answer as detailed as possible to all questions in this mail, and to the ones in the mails before. But first, since I know most people only read the first lines of mails :P, if you find any concrete iceberg issues, please report them in

Re: [Pharo-users] [Pharo-dev] [Ann] Some new iceberg videos

/iceberg/wiki/Branching-and-Merging On Thu, May 24, 2018 at 10:06 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > > > On Thu, May 24, 2018 at 9:51 AM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> Hi Tim, >> >> On Wed, May 23, 201

<    1   2   3   4   >