Re: [Pharo-dev] Cannot extract stable VM on Window

Le 29/09/2019 à 16:35, Brainstorms a écrit : > Hi Cyril, > > I downloaded it and tried it on Win7 Pro 64bit (running in Virtualbox), and > was able to open as expected. > > However, looking in the zip file itself, I noticed about two dozen > "*_Zone.Identifier" files that I was not expecting to

Re: [Pharo-dev] Cannot extract stable VM on Window

Le 29/09/2019 à 18:32, Christopher Fuhrman a écrit : > I reported an intermittent problem with pharo-launcher transferring > images that are detected as corrupted on my Windows 10. What happens > when you retry?  > > See https://github.com/pharo-project/pharo-launcher/issues/359 > I already saw

Re: [Pharo-dev] Cannot extract stable VM on Window

Le 29/09/2019 à 15:53, Cyril Ferlicot D. a écrit : > Hi, > > Today I tried to extract the stable windows VM for Pharo 8 64bits on > Windows 7 but I get an error saying the file is corrupted. > > Link: http://files.pharo.org/vm/pharo-spur64/win/stable-20190916.zip > &g

[Pharo-dev] Cannot extract stable VM on Window

Hi, Today I tried to extract the stable windows VM for Pharo 8 64bits on Windows 7 but I get an error saying the file is corrupted. Link: http://files.pharo.org/vm/pharo-spur64/win/stable-20190916.zip Can someone reproduce it? -- Cyril Ferlicot https://ferlicot.fr signature.asc Description:

[Pharo-dev] Why do we have 2 VTermOutputDriver?

Hi, In the image we currently have two VTermOutputDriver. The second one is not used but I have the impression that it was a WIP. Does someone knows what it the state of this class? Should we remove the second? Should the second be used instead of the first? -- Cyril Ferlicot

[Pharo-dev] Changes proposal on Pre debugger

Hi, After talking with Steven (in copy) we agreed on possible improvements around the pre debugger. I would like to share our vision and check if the community agrees. Context: The pre debugger is the window opening when an exception is signalled and not catched. This window currently has two

Re: [Pharo-dev] [Pharo-users] Information on Spec development

Spec 2 was integrated in Pharo. Here is the changelog: https://github.com/pharo-project/pharo/pull/3667 We will wait a few weeks before reverting all the changes to Spec 1 in order to let people who started to develop in Spec in Pharo 8 migrate to this version. -- Cyril Ferlicot

Re: [Pharo-dev] Pharo Launcher failing in Windows 10

Le 30/05/2019 à 14:43, casimiro.barr...@gmail.com a écrit : > Recently installed (clear install). > > Apparently OSPluginWrapper.dll memory faulting. > Hi, I already got this problem and the only fix I know for now is to restart the computer. It is planned to improve the system command

Re: [Pharo-dev] how implement isAbstract?

Le 30/03/2019 à 19:35, Denis Kudriashov a écrit : > Hello. > > We did recently several cleanups by marking abstract classes as abstract > using #isAbstract method > (https://github.com/pharo-project/pharo/pull/3087,  > https://github.com/pharo-ide/Calypso/pull/462) > . > > I would like to

Re: [Pharo-dev] File problems in Pharo 8

Le 12/02/2019 à 18:56, Alistair Grant a écrit : > Hi Cyril, > > I'm glad you're able to commit now. :-) > > A few comments on the performance: > > I haven't done a performance comparison for a while, and there have been > a few changes in the plugin, so I'll keep it qualitative for now and try

Re: [Pharo-dev] [ANN] Pharo open documentation

Le 30/01/2019 à 21:25, Hernán Morales Durand a écrit : > Hi Cyril, > > Nice project! > I think you forgot to add the URL : > https://github.com/pharo-open-documentation/awesome-pharo > > Note: the Zinc entry has a reference to Cytoscape.js? > Good catch! Just an error of copy past when I

Re: [Pharo-dev] Contribute to pharo8.0 ?

Le 29/01/2019 à 23:47, Sven Van Caekenberghe a écrit : > Hi, > > I am trying my first contribution / PR to pharo8.0 > > I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and > made a new one. > > But repairing the repository by fetching does not bring it to the detached

Re: [Pharo-dev] wish for p8: parserewriter UI

Le 15/01/2019 à 20:25, Stéphane Ducasse via Pharo-dev a écrit : Wasn't it the work of Mark Rizun? -- Cyril Ferlicot https://ferlicot.fr signature.asc Description: OpenPGP digital signature

Re: [Pharo-dev] Release test for unused temps and other

Le 06/09/2018 à 17:50, Torsten Bergmann a écrit : > Hi, > > the very nice contribution on GIFReadWriter/animated images (see > https://pharo.manuscript.com/f/cases/22137) > unfortunately introduced some methods that had no sender, were uncategorized > and had unused temporary variables, etc. >

Re: [Pharo-dev] Auto-completion of methods names

Le 05/09/2018 à 10:00, Marcus Denker a écrit : > > I will add a simpler version by default back (today). > > The old version tried to be clever and replace whole methods… which was > extremely confusing (and not really > helping). It complicated the model, too. > (We got even bug report > >

[Pharo-dev] Auto-completion of methods names

Hi, Today I tried to launch a Pharo 7 image and I just saw that one of my setting was failing. The setting is from NEC and allow to auto-complete the method name and could be enable like this: NECPreferences overrideModel: true In the recent Pharo 7, #overrideModel: and all the code depending

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

Le 24/08/2018 à 19:03, Sean P. DeNigris a écrit : > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > > > This seems to usually signal that a crash is not far away. It's doubly >

Re: [Pharo-dev] Win10/Launcher/Pharo7.1122--ZdcPluginMissing: SSL/TLS plugin initailization failed (VM plugin missing ? OS libraries missing ?)

Le 11/07/2018 à 19:35, Ben Coman a écrit : > I just just downloaded and installed the latest PharoLauncher > and running build 7.1122. > > After enabling Custom SSH Keys and opening Iceberg, > doing "Repair repository" on "iceberg" repo, > clicking "Clone again this repository" > Clone from

Re: [Pharo-dev] Commenting test classes?

Le 04/07/2018 à 00:39, Tim Mackinnon a écrit : > Au contraire - when looking at a Test - seeing inline the comment of the > class to remind me what I’m supposed to be testing is actually quite > helpful. I fully expect this is where GtDocumentor is going to take us > (if we integrate it into our

Re: [Pharo-dev] [CI] Cause of the random failures in the CI

On 19/06/2018 17:02, Alistair Grant wrote: > Hi Cyril, > Great work! > Thank you. Also thanks to Guille, Vincent, Marcus that helped to find the problem. > It would be nice if all the temporary files were in a single folder. > Cleaning the environment then becomes a matter of deleting that one

[Pharo-dev] [CI] Cause of the random failures in the CI

Hi, Since months now there are a lot of random failure on the CI making it hard to work. There is different kind of failures: - Network problems - Failing tests - Incomprehensible problems Now I don't see much failure due to Network. I suppose the Inria infrastructure improved. Failing tests

Re: [Pharo-dev] Debugger Button Positioning

Le 14/06/2018 à 20:13, Eliot Miranda a écrit : > Hi All, > Hi, >      I've been using Pharo intensively for the first time, Pharo 7. > Forgive me for starting with a complaint, but I don't have time to state > all the things that are great about it; you already now ;-) > No problem. It's

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

Le 13/06/2018 à 22:58, Sean P. DeNigris a écrit : > Ha ha, okay. > > > IIUC this is however the way people coming from the git world are used to > working (because they usually don't have awesome GUI tools/environments like > we do :) ) > I think it really depend on the IDE or tool you use.

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

On 13/06/2018 12:57, Tim Mackinnon wrote: > Hi I’m a bit confused by what is described below - when it says "This is > already in latest Pharo build. If you want to try it in a Pharo 6.1 ….” > - does that mean its already in the latest Pharo 7 (emphasis on 7?) > build (and I can see it in Pharo 7)

Re: [Pharo-dev] Window groups and Calypso Browser

On 12/06/2018 13:41, Torsten Bergmann wrote: > Hi Denis, > > when I open a Pharo window (like Playground) and select "Create window group" > I can > drag and drop other windows onto it. So one can group several windows into > one, each > one shown with an own tab. > > This works for most of

Re: [Pharo-dev] Annoying frame around ToolDockingBarMorph

On 09/06/2018 16:43, Hilaire wrote: > Hi Cyril, > > From what I read in an older P7 image > DockingBarMorph>>defaultBorderWidth was not implemented, and inherited, > from AlignmentMorph which defaultBorderWidth returns 0. > It was here but in a different hook. It was in setDefaultParameters as

Re: [Pharo-dev] The menu bar in question

soon: https://github.com/pharo-project/pharo/pull/1499 > > Hilaire > > Le 07/06/2018 à 14:23, Cyril Ferlicot D. a écrit : >> There is something bad here... >> >> I see in your image that it's managed via Gettext, but get text totaly >> replace some cl

Re: [Pharo-dev] The menu bar in question

On 07/06/2018 13:53, Cyril Ferlicot D. wrote: > I'm looking at this one and I would like to have more informations. > > The problem is that the menu is created before the current language is > set. So it translate in the wrong language. (It works if you do > "MenubarMor

Re: [Pharo-dev] The menu bar in question

On 07/06/2018 10:36, Hilaire wrote: > Hi, > > I made a Dr. Geo build with today P7. > > There are several issues: > > - The menu bar items are not translated (see screenshot1) > I'm looking at this one and I would like to have more informations. The problem is that the menu is created before

Re: [Pharo-dev] The menu bar in question

On 07/06/2018 10:36, Hilaire wrote: > Hi, > Hi Hilaire, > I made a Dr. Geo build with today P7. > > There are several issues: > > - The menu bar items are not translated (see screenshot1) > I'll take a look: https://pharo.fogbugz.com/f/cases/22083/Menubar-is-not-translated > - The menu

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

On 05/06/2018 17:16, Martin Dias wrote: > Hello, > > The new "official" repository for Epicea*, Ombu* and Hiedra* packages > in Pharo >= 7 is just Pharo's github > (https://github.com/pharo-project/pharo/). > > This will ease to fix a bug or add a feature on those packages. At > least, will be

Re: [Pharo-dev] Quick menubar tweak

On 05/06/2018 13:41, Pavel Krivanek wrote: > In the current menu bar in Pharo 7 I miss launcher icons. This is a > quick ad-hoc tweak how to add them: > > > > MenubarMorph reset. > > World menubar submorphs second delete. > > World menubar addMorph: (SimpleButtonMorph new  > label: '|'; >

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

On 01/06/2018 15:25, Peter Uhnák wrote: > Hi, > > I really love this idea. I've already added (hacked together) something > similar for some of my projects so I am happy to see this is going into > Pharo. > >> - Make it parametrizable to allow users to build a bar with their own menu >> builder

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

On 01/06/2018 15:18, Alistair Grant wrote: > Hi Guille & Cyril, > > Thanks for this. Along with being able to maximise windows > completely, making the task-bar distinct at the bottom, these are > great changes. > Yes, I did not see the problem because I use backgrounds and it was visible :)

[Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

Hi everyone, With Guille we are trying to improve the usability of the WorldMenu. The world menu is by large un-intuitive: - Users are not used to click on a background to open a menu - For those that "get it" they try to do it with right click (Of course, it looks like a context menu!) and

[Pharo-dev] New taskbar design proposal

Hi, I always had some problems with Pharo taskbar. The first one is that it is trasparent. It takes the whole width of Pharo but only the taskbar items are visible. This is bad because we have impression that we can click on the world at the bottom right of Pharo, but we cannot. Also I did not

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

Le 21/05/2018 à 14:58, Alistair Grant a écrit : > Hi Everyone, > > Does anyone know the history behind FileDoesNotExist and > FileDoesNotExistException? > > Both classes exist in 6.1, and as far as I can tell, both are intended > to do the same thing, i.e. the class comments are: > >

Re: [Pharo-dev] [Seaside-dev] Seaside loading broken in Pharo 7

Le 18/05/2018 à 21:42, Sean P. DeNigris a écrit : > Tim Mackinnon wrote >> Hi what does it mean “Iceberg does not manage yet upgrade of the local >> clones” > > This is most commonly encountered when one enables shared repository > location in Iceberg. Say you already have a local clone of Zinc

Re: [Pharo-dev] who redefined the #balloonBackgroundColor for dark theme?

On 09/05/2018 14:32, Hilaire wrote: > well... For me the hight contrast makes it very visible, as should be a > tooltip, and helpfull to discover feature in drgeo. > > Maybe themes could use a dictionary storing all the colors for the theme. Like that each theme should only define the default

Re: [Pharo-dev] [Ann] Iceberg 0.7.5

On 03/05/2018 17:16, Guillermo Polito wrote: > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. > Thanks to all brave users, issue reporters and contributors :). > > Key improvements:  >  - Several improvements in metacello integration. (see #625, #664,

Re: [Pharo-dev] Do we kill the catalog?

Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit : > > >> On 20 Apr 2018, at 11:01, Thierry Goubier > > wrote: >> >> Le 20/04/2018 à 09:09, Stephane Ducasse a écrit : >>> The underlying questions (sorry for people that need subtitles)

Re: [Pharo-dev] [ANN] New Pharo 6.1 version

On 05/04/2018 17:14, Alexandre Bergel wrote: > When there is a new version of Pharo 6.1, how can I make the launcher > know about it? > Hi, In "official distributions", just download a new Pharo 61 version from the launcher and it will be this version by default. It should be build 60540 I

Re: [Pharo-dev] SSL error on windows 7

Le 02/04/2018 à 23:49, Sven Van Caekenberghe a écrit : > Well, it works for me on macOS and Ubuntu with [version] 'Pharo7.0' > 'Pharo-7.0+alpha.build.660.sha.2eb9bd2f41e7b0bd8f9f4190906910f83c178ab1 (32 > Bit)' > > Both socket(stream) code as well as SSL plugin code is different between the >

[Pharo-dev] SSL error on windows 7

Hi! I have some trouble with SSL in Pharo 7. If I execute this code: ZnClient new url: 'https://google.com'; get. I get a result. If I execute this code: ZnClient new url: 'https://github.com'; get. I get this error: Error: SSL Exception: connect failed [code:-5] I tried with both stable

Re: [Pharo-dev] Migrator: to help you migrating to latest version of Pharo :)

On 30/03/2018 22:30, Stephane Ducasse wrote: > Hi > > Today during the Pharo sprint I went over all the deprecated methods > in Pharo 70 and Pharo 60 and I checked if I could convert the > deprecated ones into deprecated:transformWith: so that the conversion > is done automatically to help people

Re: [Pharo-dev] [Testers Required] New FreeType implementation using FFI

Le 30/03/2018 à 14:42, teso...@gmail.com a écrit : > I have implemented the backend of FreeType using only FFI calls.  > So the whole implementation is in the image side, the current plugin has > a lot of problems handling the release of the pointers. The new > implementation is using the

Re: [Pharo-dev] Released versions in Pharo Bootstrap

Le 19/03/2018 à 18:49, Stephan Eggermont a écrit : > Then why bother releasing? > Hi, For people using Pharo 7 to not get the same bugs for more than 1 year, to get the new functionalities and to be able to detect new bugs introduced in releases. > Stephan > > > > > -- Cyril Ferlicot

Re: [Pharo-dev] cannot write to the changes file

Le 13/01/2018 à 18:03, Ben Coman a écrit : > > Great! That was quick work (thanks Pavel.) > Do you have an issue for me to follow, or should I create it? > > cheers -ben > It seems that the problem was corrected today (probably the change in File usage). Can someone else confirm? -- Cyril

[Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

Hello! I have a Jenkins build for MaterialDesignLite and the Pharo 7 build never end. I load the code via the command line "eval" with the "--save" parameter and a Metacello command. While adding some log I found the problem. It comes from this method: EvaluateCommandLineHandler>>evaluate:

[Pharo-dev] Problems with Epicea on Pharo 7

Hi, I have a little problem with Epicea and there is some things I would like to discuss. My problem is that I have a Jenkins job downloading a Pharo 7 image, loading inside a little project via an eval command launching a Metacello script. Then I launch tests. And then I archive the image.

Re: [Pharo-dev] [ANN] 64 bits support preview

Le 06/03/2018 à 04:19, Mariano Martinez Peck a écrit : > Hi guys, > Hi! > Thanks for Guillermo Polito we now have 64 bits support for > OSSubprocess. You can see the required changes in this PR [1]. Cool :) I made a > branch called `support64bits` so that you can help us test it even if CI >

[Pharo-dev] Metacello locking system

> Cyril, > > For development I tend to use Metacello locking instead of hard-wired > dependencies in the BaselineOf and that works very well --- it > completely avoids the need to edit a baseline for development purposes > and this approach works really well for me ... perhaps we can discuss >

Re: [Pharo-dev] [Ann] Commander shortcuts in Settings Browser

Le 06/03/2018 à 17:05, Denis Kudriashov a écrit : > Hi. > > With latest version of Commander and Calypso we will have all shortcuts > explorable and configurable in Settings Browser: > > > ​ > Currently it uses command class name and class comment for presentation. > We can improve it in future

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

Le 25/02/2018 à 23:07, Cyril Ferlicot D. a écrit : > Hi! > > This support is in this PR: > > https://github.com/pharo-project/pharo/pull/950 > > It was not added in Pharo 7 during the last sync but was in Pharo 6.1. > > I hope in the future we will depend on Me

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

Le 20/02/2018 à 14:29, Juraj Kubelka a écrit : > Hi, > > > In the following email [1], Dale Henrichs explains that there was an update > to support correctly GitFileTree metadata-less mode. While I can see the > mentioned class MetacelloCypressBaselineProject in Pharo 6.1, I cannot find > it

Re: [Pharo-dev] VMs build process restored

Le 06/02/2018 à 17:58, Esteban Lorenzano a écrit : > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip > •

Re: [Pharo-dev] Protocol names convention

Le 13/01/2018 à 13:46, Norbert Hartl a écrit : > > Sounds great! In which class is the code that does the decision about the > right name? I think I find my convention here.+ > There is MethodClassifier with pragma, prefix and suffix map class side. > Norbert > -- Cyril Ferlicot

Re: [Pharo-dev] cannot write to the changes file

Le 13/01/2018 à 12:36, Cyril Ferlicot D. a écrit : > > Hi, > > For my part it inform that the source file cannot be written at launch > but in the end it is written. > > This problem comes from a refactoring in the location system I think. > Pavel located the problem w

Re: [Pharo-dev] cannot write to the changes file

Le 13/01/2018 à 05:43, Ben Coman a écrit : > Before creating an Issue, can someone confirm the following behaviour on > Windows 10 ? > Downloaded and unzipped into the same folder... > *  > http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip > *  >

Re: [Pharo-dev] ZnClient issue: ZdcPlugin Missing

Le 12/01/2018 à 19:48, Photon a écrit : > Hello, > > I was just following along this book: > and it told me to get some data via ZnClient like this, I tried them both > with a dot inbetween and independantly like in the picture below. Does > someone got an idea what`s wrong? > Hi, Are you on

[Pharo-dev] Flexibility of ZnUrl (For Metacello evolution)

Hi, In order to improve the usage of Pharo and the git integration there is some discussions around Metacello in order to be able to: - Load a private git project from Metacello API - Load a project hosted on a private server from Metacello API - Load a project hosted on a private server with

Re: [Pharo-dev] New Year Wishlist (2018) ?

On 12/23/2017 06:57 PM, Cyril Ferlicot D. wrote: > On 12/23/2017 05:58 PM, Esteban Lorenzano wrote: >> Hi everybody, >> > > Hi :) > >> This looks like a good moment of the year to ask all of you what would you >> want to see in Pharo next year. >> Fe

Re: [Pharo-dev] New Year Wishlist (2018) ?

On 12/23/2017 05:58 PM, Esteban Lorenzano wrote: > Hi everybody, > Hi :) > This looks like a good moment of the year to ask all of you what would you > want to see in Pharo next year. > Features, improvements, radical changes, etc…. whatever you want. > I'll list the things I wanted the

Re: [Pharo-dev] Linux vm packages

Le 21/12/2017 à 21:17, Stephane Ducasse a écrit : > Someone install and using Pharo on Linux should maintain this page. > I would simply remove it because this is just a pain to maintain a > description for system that we cannot even > use. > > > This is one of the most important page of the

Re: [Pharo-dev] Is there some progress on the 64bit Metacello loading segfault problem?

On 12/20/2017 10:48 AM, Thierry Goubier wrote: > Hi Cyril, > > as said before, those are solved by using a more recent vm, such as the > 201710221351 linux 64bits vm. You're using an older one in the CI > (the 201707201942), and, unless they have been updated, both stable and > latest pharo vms

[Pharo-dev] Is there some progress on the 64bit Metacello loading segfault problem?

Hi, There was a bug reported multiple times about segfaults during Metacello loadings in Pharo. This week I setup some Jenkins builds for 64bits products and I still see a lot of segfault. I cannot get a way to reproduce it 100% but it appears pretty often. Today we got 3 crash out of around 15

[Pharo-dev] Drag and drop of methods

Hi, In the latest Pharo 7 I cannot drag and drop methods anymore in Nautilus. Pharo version: Pharo-7.0+alpha.build.389.sha.e642e96a93951b2765dc808a512b81dc3d52e150 (32 Bit) Stack: TransferMorph(Object)>>doesNotUnderstand: #buildWithSpec

Re: [Pharo-dev] Pharo6.1 World menu order

Le 13/11/2017 à 20:37, Aliaksei Syrel a écrit : > Hi, > > I find world menu order in Pharo 6.1. with enable Iceberg a little bit > awkward :) > > Inline images 1 > > Any thought on why Iceberg is the first? It breaks muscle memory. > It is first because other items does not have any order.

Re: [Pharo-dev] Publishing a book with Pillar

Le 13/11/2017 à 21:01, Stephane Ducasse a écrit : > Hi guys > > we are working on pillar and we will probably release a new alph version soon. > I'm updating the doc. But I found that the doc I was writing can help > some of you. > Cool! Don't forget to focus a little on Windows for the next

Re: [Pharo-dev] Baseline/Configuration loading bars

Le 02/11/2017 à 20:01, Stephane Ducasse a écrit : > Super tx Cyril > Tx dale. I think that Camillo back then introduced Job. > Stef > > Hi, The issue is corrected in Metacello/metacello on github and Dale updated the Pharo 6.1/7.0 tags. (Thank you) Now, how should I integrate it in Pharo?

Re: [Pharo-dev] Preferences location on linux and windows?

Le 29/10/2017 à 21:19, Stephane Ducasse a écrit : > Hi guys > > I'm about to release a new booklet and I need the following information. > What are the preferences location on linux and windows? > > TX > Hi, For windows: C:\Users\Name_Of_Your_User\AppData\Roaming You can also describe it

Re: [Pharo-dev] Launcher: VM Problem

Le 20/10/2017 à 20:51, Sean P. DeNigris a écrit : > I have a recent working VM in ~/Documents/Pharo/vms/60. Instead of using it, > the last Launcher release downloaded another one to > ~/Documents/Pharo/vms/60-x86. However, this seems to be an older one which > does not support Iceberg (I get a

[Pharo-dev] Management of ctrl + shift in windows

Hi, I have a weird problem on Windows and shortcuts. For the context I use a keyboard which is not of the AZERTY/QWERTY layout but BÉPO.[1] I have a problem with the fact that some `ctrl + shift + ?` shortucts does not works. But some works. For example in Nautilus I cannot do a format (`ctrl

Re: [Pharo-dev] shameless request: please star pharo-project/pharo in GitHub :)

Le 09/10/2017 à 22:32, Esteban A. Maringolo a écrit : > Thanks Paul. > > Esteban: Shouldn't the repo be marked as "Smalltalk" language? > > Performing a search on repos of "Smalltalk" there are several ones > with less stars than Pharo, and it doesn't show up. > >

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

Le 07/10/2017 à 00:34, Cyril Ferlicot D. a écrit : > Le 06/10/2017 à 21:56, Mariano Martinez Peck a écrit : >> >> Weird that package is not being loaded...  sure I can explicitly >> load it ... but I think we must fix the baseline... but the baseline >> looks

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

Le 06/10/2017 à 21:56, Mariano Martinez Peck a écrit : > > Weird that package is not being loaded...  sure I can explicitly > load it ... but I think we must fix the baseline... but the baseline > looks correct doesnt it ? I don't understand. > >   I think I found the way to correct this

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

Le 06/10/2017 à 23:34, Tim Mackinnon a écrit : > Gosh - It actually work quite well to be able to easily browse code > online in a more traditional format of seeing an entire class. Hopefully > this leads to us being able to share solutions to common language > agnostic problems. > > One small

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

Le 06/10/2017 à 21:34, Mariano Martinez Peck a écrit : > I followed the instructions to update Iceberg from in a 6.1 image. When > I tried to clone the repository, I have the attached error (DNU on > #dangerTextColor). I workedaround that by doing: > > IceAbstractModel >> colorError > ^ Color red

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

Le 06/10/2017 à 18:32, Stephane Ducasse a écrit : > both now I do not see what we can do if a third party tools consider > that we are a virus. > > Done. I don't know how to not be detected but Windows Defender is the default anti-virus on windows. The majority of windows user use it now. If

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

Le 06/10/2017 à 13:02, kmo a écrit : > I was trying to Soup on Windows 7 and found I could not access https sites > > On windows 7 and 10 the following code fails: > > ZnEasy get:'https://genius.com/Alice-nuvole-lyrics'. > > This works fine in Pharo 5 on Windows. Also works fine with Pharo 6.1

Re: [Pharo-dev] argh, tests are failing!

Le 10/09/2017 à 18:24, Stephane Ducasse a écrit : > Yes we know but have no idea how to recategorise Iceberg protocols  > The protocol is already recategorised in Iceberg dev branch. Now we need a new stable release of Iceberg and to integrated this release in Pharo. -- Cyril Ferlicot

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Le 31/08/2017 à 00:06, Nicolai Hess a écrit : > Hi, > > I am now able to use iceberg on windows, thanks for the help. > > But I am still a bit unsure about how the review and contribution > workflow should work. > > up to pharo 6 I just load a latest image, > - load the slice from a fogbugz

Re: [Pharo-dev] AbstractFileReference>>ensureDelete when directory has children

Le 20/08/2017 à 19:53, Peter Uhnák a écrit : > > +1 > > The only problem may be that even the VM doesn't actually know the > reason (it could just trigger the delete at vm-level which will just > return a failure state). > > Peter The fact that is touch the vm is a reason I post here. It would

[Pharo-dev] AbstractFileReference>>ensureDelete when directory has children

Hello, I often was surprise to get primitive failures while calling #ensureDelete. I saw that when a folder has children, we should not call #ensureDelete but #ensureDeleteAll, at least on Windows. I think we should raise an other error than "Primitive Failure" when we are in that case.

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Le 10/08/2017 à 23:58, Nicolai Hess a écrit : > > What does "clone using sourcetree" mean? > > IIRC SourceTree is a Git GUI available on Windows, as GitKraken, SmartGit, GitExtensions, TortoiseGit… -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01,

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Le 08/08/2017 à 23:40, Nicolai Hess a écrit : > Thanks for the info, cyril. > > What do you use for the ssh username in pharo setting and what username > did you use for creating the ssh-key ? > I tried both, my github-email and my github-username, I didn't get it to > work. > I did not use

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Le 08/08/2017 à 23:37, Nicolai Hess a écrit : > > > Like I described above. > > I followed this howto ( the first mail from pavel). > > But I get this error: > > 'LGit_GIT_ERROR: Failed to authenticate SSH session: Callback returned > error' > > > Now I enabled the setting for "Use custom

Re: [Pharo-dev] Pharo 7 provisional HOWTO

Le 08/08/2017 à 20:40, Nicolai Hess a écrit : > > Any news on howto use iceberg / libgit on windows. > Does no one else use windows ? > Hi, I can use Iceberg on Windows 7 but not to participate to Pharo (or any project with file name longer than 255chars). So I can work on my projects or on

Re: [Pharo-dev] fixing the tab morph

Le 07/08/2017 à 17:47, Esteban Lorenzano a écrit : > Hi, > > So… summer project (to do when there is too much hot to go outside): fix > some minor things that are inside the image that annoys me since some time. > > First issue: the tab morph we have is horrible (and makes horrible > anything

[Pharo-dev] Epicea: Revert the removal of a class

Hi, Today I tried to remove a class, go in Epicea and revert the removal of the class. At the end the class was here but with no methods. Is that the normal behaviour? I think it is a bug but since I don't really use Epicea a lot for know I am not sure. Have a nice day. -- Cyril Ferlicot

Re: [Pharo-dev] how to issue a PR that changes package structure?

Le 08/07/2017 à 20:15, Stephane Ducasse a écrit : > Hi guys > > I would like to split or/and create packages. > Should I update the Pharo baseline. > > Stef > I saw Pavel doing PR to remove packages by removing them from the baselines. Example:

Re: [Pharo-dev] wrong file on the download

Le 08/07/2017 à 20:21, Stephane Ducasse a écrit : > http://pharo.org/web/download > > Pharo 7.0 image & changes > > latest donwloads a Pharo 60 image > This is maybe like that because the Pharo 7 images are not uploaded at files.pharo.org for now. So the latest image is the latest Pharo 6

Re: [Pharo-dev] Github package management beta

cy...@ferlicot.me Le 07/06/2017 à 06:32, Eliot Miranda a écrit : > Hi All, > >I've been invited to participate in github's Bera test of their new > package management support. I don't know much, if anything, about the > software except that it supports RubyGems (Ruby), Maven (Java) and

Re: [Pharo-dev] Abstract test classes are not managed well in SUnit

Le 04/06/2017 à 21:26, Cyril Ferlicot D. a écrit : > For this problem I would like to see all the smalltalks using SUnit > change this behaviour. I really do not want to break compatibility and I > think this change is important for the usability of SUnit. I don't have > much contac

Re: [Pharo-dev] Abstract test classes are not managed well in SUnit

Le 04/06/2017 à 18:20, Eliot Miranda a écrit : > Hi Cyril, > Hi Eliot, > > As Minty points out, this unintuitive behaviour exists fur a reason and there > is a work around. > > SUnit is a community wide package existing in all the dialects of Smalltalk > I'm aware of. If you change the

Re: [Pharo-dev] New and richer halt messages

Le 04/06/2017 à 11:40, Peter Uhnak a écrit : > But then I wouldn't be able to write 1halt. :( > > Peter > You can still add some startup script :) I have one compiling a "h" method in object calling halt to be able to write "1h" :) -- Cyril Ferlicot https://ferlicot.fr

Re: [Pharo-dev] Abstract test classes are not managed well in SUnit

Le 04/06/2017 à 12:38, monty a écrit : > I agree with you, and I would rather subclasses inherit tests by default, but > be aware that this isn't a bug[1], and changing it will temporarily break > some test hierarchies. > > [1] >

Re: [Pharo-dev] Abstract test classes are not managed well in SUnit

Le 04/06/2017 à 02:26, monty a écrit : > I've seen this before, and I'm not sure it's a bug. > > A testless, non-abstract subclass of a TestCase is useless unless it inherits > test methods. But if it defines its own test methods, then it isn't clear if > it was made a subclass to inherit test

[Pharo-dev] Abstract test classes are not managed well in SUnit

Hi, Today I found a bug in SUnit. Sometimes when you have an abstract test class and you override it the tests will be inherit or not. If a subclass has other tests, the tests will not be inherited. If the subclass has no other tests, the tests will be inherited. Here is a little script

Re: [Pharo-dev] [Vm-dev] multiple crashes on macOS Sierra

Le 28/05/2017 à 10:50, Esteban Lorenzano a écrit : > > > yes, but I never had it (and I use mac and I type fairly fast too). > Same, never had it and I type fast. > Esteban > > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve

  1   2   >