[Pharo-dev] Charting in Roassal2

2018-07-27 Thread Shaping
Hi Folks. Can anyone tell me whether we have candlestick-charting ability in Roassal2? Shaping

Re: [Pharo-dev] Charting in Roassal2

2018-07-31 Thread Shaping
Thank you , Alexandre. That's exactly what I needed to know. Adapting the whisker plots should be straightforward. Shaping From: Alexandre Bergel [mailto:alexandre.ber...@me.com] Sent: Tuesday, July 31, 2018 3:47 PM To: Pharo Development List Cc: Any question about pharo is welcome

Re: [Pharo-dev] [ANN] The STON Specification

2018-11-03 Thread Shaping
Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -Original Message- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List Subject: Re: [Pharo-dev] [ANN

[Pharo-dev] Pharo 7 speed compared to VW (was: The STON Specification, Cog speed, and namespaces/modules)

2018-11-12 Thread Shaping
better. I’ve spend more time with it last few weeks than during the previous decade. Thanks to everyone for the effort and improvements. Shaping From: Shaping [mailto:shap...@uurda.org] Sent: Wednesday, November 7, 2018 00:41 To: 'Pharo Development List' Subject: RE: [Pharo-dev] [ANN

Re: [Pharo-dev] [ANN] The STON Specification, Cog speed, and namespaces/modules

2018-11-06 Thread Shaping
? Or, I could just load every package I can find, before I check names. But that little experiment has never gone well in the past. Is the Pharo-with-namespaces issue dead or merely suspended, awaiting a more fitting idea than what VW currently offers? Shaping On Tue, Nov

[Pharo-dev] Zinc Websockets

2018-11-05 Thread Shaping
Hi all. What is the easiest way to port Zinc Websockets to VW? Has this been done? Shaping

[Pharo-dev] Porting from VW to Pharo

2018-11-05 Thread Shaping
of avoiding class-name collisions, which is mostly what I need it for, and I can control exactly how imports work. Any suggestions are welcome. Thanks. Shaping

[Pharo-dev] [ANN] The STON Specification

2018-11-05 Thread Shaping
(Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -Original Message- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org

Re: [Pharo-dev] [ANN] The STON Specification

2018-11-06 Thread Shaping
of the c-type FFIFloats. Any Float classes of this size and larger for the Smalltalk heap on 64-bit Pharo? Cheers, Shaping Le 6 nov. 2018 à 06:58, Shaping mailto:shap...@uurda.org> > a écrit : (Having domain problems recently. Please excuse this posting if you hav

[Pharo-dev] Pharo 7 speed compared to VW

2018-11-19 Thread Shaping
(Second try in 6 days. Does anyone have recent performance data for Pharo 7 relative to VW 7.10 or later?) From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Shaping Sent: Tuesday, November 13, 2018 00:33 To: 'Pharo Development List' Subject: [Pharo-dev] Pharo 7 speed

Re: [Pharo-dev] Version control of Playground scripts

2018-12-01 Thread Shaping
/Iceberg-glossary.md looks like a good place to start, but I can probably find much better guidance here on the list than from a Google search. Thanks. Shaping From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Norbert Hartl Sent: Thursday, November 29, 2018 04:32

Re: [Pharo-dev] Versioning with Iceberg

2019-05-31 Thread Shaping
On Wed, 29 May 2019 at 23:08, Shaping mailto:shap...@uurda.org> > wrote: I’m finding 7.0.3 to be more stable. How do I load a specific baseline/version with Iceberg? I’m getting 8.0 by default from the cloned local repo, and I prefer not to merge 7.0.3 with 8.0. There ar

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-05-30 Thread Shaping
they are. The fragmented versioning-technologies will persist then indefinitely. Shaping From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben Coman Sent: Thursday, May 30, 2019 08:45 To: Pharo Development List Subject: Re: [Pharo-dev] FW: Versioning with Iceberg On Thu, 30

Re: [Pharo-dev] VM crash in Pharo 8.0 during save

2019-05-31 Thread Shaping
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben Coman Sent: Friday, May 31, 2019 04:39 To: Pharo Development List Subject: Re: [Pharo-dev] VM crash in Pharo 8.0 during save On Wed, 29 May 2019 at 21:21, Shaping mailto:shap...@uurda.org> >

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-05-31 Thread Shaping
h book are you referring to here? Did you check the wiki and the documentation? Yes, some. I’m thinking it’s Smalltalk and shouldn’t be that hard in any case. But there is a lot of Git here, and that is complicating things somewhat. Shaping

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-05-31 Thread Shaping
orward with Git and an option to access legacy code with Monticello. Is Metacello going away? Shaping From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org <mailto:pharo-dev-boun...@lists.pharo.org> ] On Behalf Of Ben Coman Sent: Thursday, May 30, 2019 08:45 To: Pharo Deve

Re: [Pharo-dev] Versioning with Iceberg

2019-05-31 Thread Shaping
On 30 May 2019, at 11:55, Shaping mailto:shap...@uurda.org> > wrote: 7.0.3. It loaded after a fresh clone of pharo, but with a detached head. So are you trying to actually contribute to Pharo? You don’t normally need to reload pharo (if I’ve understood what you are doing). I

Re: [Pharo-dev] Versioning with Iceberg

2019-05-29 Thread Shaping
. Its not completely clear what you want. You can right-click a repo > Metacello > Install baseline of. Or right-click a repo > Repository > Remotes and select one of those branches to check out. The baselines look specialized. I want Pharo 7.0.3, not just one package. Shaping

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-05-30 Thread Shaping
. The problems may be related to not using default install folders. I’m not sure yet. Shaping On 30 May 2019, at 02:07, Shaping mailto:shap...@uurda.org> > wrote: Sorry, I meant progress bar, not histo…. From: Shaping [mailto:shap...@uurda.org] Sent: Wednesday, May 29, 2019

Re: [Pharo-dev] Versioning with Iceberg

2019-05-29 Thread Shaping
…Trying to have 7.0.3 as my base, not 8.0. I’m not sure what happened with the VM crash, but I can do without the latest version for now. How do I specify the commit with Iceberg? Shaping From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of ducasse Sent

Re: [Pharo-dev] Versioning with Iceberg

2019-05-29 Thread Shaping
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben Coman Sent: Wednesday, May 29, 2019 10:58 To: Pharo Development List Subject: Re: [Pharo-dev] Versioning with Iceberg On Wed, 29 May 2019 at 23:08, Shaping mailto:shap...@uurda.org> > wrote: I’m f

[Pharo-dev] FW: Versioning with Iceberg

2019-05-29 Thread Shaping
Sorry, I meant progress bar, not histo…. From: Shaping [mailto:shap...@uurda.org] Sent: Wednesday, May 29, 2019 20:05 To: 'Pharo Development List' Subject: RE: [Pharo-dev] Versioning with Iceberg From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Ben Coman

Re: [Pharo-dev] Versioning with Iceberg

2019-05-29 Thread Shaping
. Shaping

[Pharo-dev] VM crash in Pharo 8.0 during save

2019-05-29 Thread Shaping
elated files left in the user account/Documents area. I see something in the attached .dmp about a stack overflow. I would enter this bug at https://pharo.fogbugz.com/, but I’m not sure it would get quick attention there. Shaping crash.dmp Description: Binary data

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-06-01 Thread Shaping
approach and some backward compatibility with Monticello (without encouraging new use of Monticello)? Shaping

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-06-01 Thread Shaping
[...] Tonel (and FileTree) are representations and models of code. Okay. Is one preferred? > For now, I’ll settle for getting Iceberg to work reliably in 7.0.3. Are the > best references on Iceberg the Pharo books or the Iceberg GitHub site? Which > Iceberg material is most

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-06-01 Thread Shaping
of Monticello)? No because the distance is too large. We cannot burn our two engineers on “nice to have” when the “must have” is not yet done. Now migrating to iceberg is super easy and configurations are a lot simpler than with monticello. Stef Shaping

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-06-01 Thread Shaping
is in an \images subfolder. I currently keep all my Git repos on a separate RAID drive. Now on windows the state of the libraries to run scripts is making us trouble Can you give more details on that? What are the problems? and we will have to fix it. Shaping

[Pharo-dev] Environments

2019-06-01 Thread Shaping
Does anyone have experience with Squeak Environments? This came up in the Cuis list. Environments are Squeak’s attempt at a module or namespace system. Does this exist for Pharo? Has anyone worked with it, and found it to be usable? Shaping

Re: [Pharo-dev] Versioning with Iceberg

2019-06-01 Thread Shaping
nection might also explain some of your PharoLauncher "identifying VM version" issues. > I also got the error: > > LGit_GIT_EEXISTS: Failed to stat file ' > F:/_personal/Pharo/images/Shaping 7.0 - 64bit > (stable)/pharo-local/iceberg/dionisiydk/Mocketry/Mo

[Pharo-dev] Iceberg: No Project Founds

2019-06-02 Thread Shaping
e result. Shaping

Re: [Pharo-dev] Versioning with Iceberg

2019-06-02 Thread Shaping
[…] I prefer the more detailed syntax highlighting in VW. Check the styler look for

Re: [Pharo-dev] Environments

2019-06-02 Thread Shaping
- many many cleans - Introduction of application and more. Okay, sounds good. Shaping

[Pharo-dev] automatic field-size adjustment to font-change

2019-06-02 Thread Shaping
ore the font-change must be re-opened. The font does visibly change before the reopening, but the field-size adjustment needed to see all the text does not happen until after reopening. Will Spec fix this? Thanks. Shaping

Re: [Pharo-dev] Environments

2019-06-02 Thread Shaping
n to deal with Iceberg. Shaping

Re: [Pharo-dev] Environments

2019-06-02 Thread Shaping
grity checks. I'm happy they are there, but they are not nearly enough to make humans extremely productive and powerful at shaping machine behaviors. I think we are overworked and that our machines are hardly being used. There is a science to increasing reading speed and comprehension in a program

Re: [Pharo-dev] Environments

2019-06-02 Thread Shaping
have a formal definition for Environment. I tend to think in terms of a VW namespace. Shaping No, I missed it. Thanks for that. I have a lot of algorithmic meat in domain classes. Those are easy to port, even if I must manually trip over the minor VW/Pharo differences

Re: [Pharo-dev] FW: Versioning with Iceberg

2019-06-02 Thread Shaping
64-bit Pharo. So tonel is a must for you else you will die. Agreed. I see the bad effects of the Windows 260-character limit with FileTree. Shaping

[Pharo-dev] FW: [Pharo-users] Latest PharoJS Success Story; Wasm/WASI; very keen on Pony for the Pharo VM

2020-04-05 Thread Shaping
I should have initially posted this to the Pharo-dev list, as well. From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Shaping Sent: Friday, 3 April, 2020 14:05 To: 'Any question about pharo is welcome' Subject: Re: [Pharo-users] Latest PharoJS Success Story; Wasm

Re: [Pharo-dev] Squeak and Pharo: why the fork

2020-05-17 Thread Shaping
On Sat, 16 May 2020 at 16:57, Shaping mailto:shap...@uurda.org> > wrote: You also had personality differences and disagreements which developed over years. Eventually the Pink plane community forked and created Pharo. The foundational community of Squeak (Blue plane) did not want t

Re: [Pharo-dev] Squeak and Pharo why the fork

2020-05-17 Thread Shaping
istic and more sustainable. Shaping

Re: [Pharo-dev] Squeak and Pharo why the fork

2020-05-16 Thread Shaping
that for all the simplifications and Spartan approach. The main appeal is simplified code/framework study. Shaping On Sat, 16 May 2020, 10:57 Shaping, mailto:shap...@uurda.org> > wrote: Hi Jimmie. On 5/15/20 5:26 AM, Shaping wrote: I don’t understand the split. It

[Pharo-dev] Squeak and Pharo why the fork

2020-05-16 Thread Shaping
Hi Jimmie. On 5/15/20 5:26 AM, Shaping wrote: I don’t understand the split. It looks silly. Maybe someone can explain the split in terms of technical/architectural advantages, if any exist. I began using Squeak about 20 years ago. And then Pharo when it started. I will explain

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-16 Thread Shaping
procedure you like to use when benchmarking the VW VM? Shaping

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-16 Thread Shaping
. Shaping Hi Eliot. Generally, comparing VisualWorks to either Squeak or Pharo or both, what are the most pressing speed problems? 1. Double-click text selection in both Squeak and Pharo shows a 75-100 ms latency (eye-balled, estimated) between end of double click

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-18 Thread Shaping
state except to collect all garbage. Shaping

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-18 Thread Shaping
RSION) 71 the vmProxyMinorVersion (the interpreterProxy VM_MINOR_VERSION)" Shaping

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-15 Thread Shaping
in the same image, and configured as desired in GUI sections of Settings? Shaping On Fri, May 15, 2020 at 12:48 PM Shaping mailto:shap...@uurda.org> > wrote: Hi all. Squeak 5.3: Time millisecondsToRun: [ 10 factorial ] 6250 Pharo 8: Time millisecond

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-15 Thread Shaping
Arithmetic changes proposed in Squeak have no relationships to VM. The question below is about both the VM and a common basic class-set. Math-related classes/methods are assumed to be part of that common class-set. Why is that not so? Shaping On Fri, May 15, 2020 at 2:09 PM Shaping

Re: [Pharo-dev] Squeak and Pharo speed differences

2020-05-15 Thread Shaping
e to make the change. It’s very simple. I figure someone knows it because they’ve tweaked it already. That would save some time. I think I made the change myself in an older Pharo. I forgot where I did it. Cheers, Shaping

[Pharo-dev] Pharo Launcher 3.0 does not open ( was: RE: Re: [ANN] Pharo Launcher 3.0 released!)

2022-04-27 Thread Shaping
My newly installed Pharo Launcher 3.0 doesn’t open. Starting the Launcher creates a VM, but no GUI. Every time I start it, TaskMan shows another VM instance, but no GUI appears. I ran the installer twice after a complete uninstall. Anyone having this problem? Shaping From

[Pharo-dev] Pharo Launcher 3.0.1: no GUI

2022-05-11 Thread Shaping
From: Shaping Sent: Wednesday, 4 May, 2022 02:46 To: 'Pharo Development List' Cc: 'Pharo-users' Subject: [Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released! On May 3, 2022, at 6:03 PM, Shaping < <mailto:shap...@uurda.org> shap...@uurda.org> wrote: > > This is

[Pharo-dev] Re: Pharo Launcher 3.0 does not open ( was: RE: Re: [ANN] Pharo Launcher 3.0 released!)

2022-04-27 Thread Shaping
I’m running an updated Windows 10 Pro, and let the Pharo Launcher installer use all the defaults. The uninstalls were thorough and done with CCleaner and Revo Uninstaller. Is everyone able to get Pharo Launcher 3.0 to work? I’ve never had this problem. Shaping --- My

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-04-29 Thread Shaping
PL 3.0.1 is still failing to open on Windows. The VM instance appears in TaskMan. Shaping From: Christophe Demarey Sent: Friday, 29 April, 2022 03:50 To: Pharo Development List ; Pharo-users Subject: [Pharo-dev] [ANN] Pharo Launcher 3.0.1 released! Hi all, Pharo Launcher 3.0.1

[Pharo-dev] Re: Pharo Launcher 3.0 does not open

2022-04-28 Thread Shaping
Hi Christophe. I tried installing the version below (after uninstalling the old PL 3.0), but I get the same problem. Double clicking the PL icon will create VM instances but no GUI. The Windows Event Viewer says the install completed successfully. Shaping From: Christophe

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-03 Thread Shaping
Hi Christophe. Is PL still broken? The PL download page still shows version 3.0.1, which does not open for me on Windows. Did you test the latest build successfully on Windows? Shaping --- PL 3.0.1 is still failing to open on Windows. The VM instance appears in TaskMan

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-03 Thread Shaping
? No, just an ordinary event log: Windows Installer installed the product. Product Name: PharoLauncher. Product Version: 3.0.1. Product Language: 1033. Manufacturer: Pharo project. Installation success or error status: 0. Is everyone else able to open PL 3.0.1 on Windows? Shaping

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-04 Thread Shaping
On May 3, 2022, at 6:03 PM, Shaping < <mailto:shap...@uurda.org> shap...@uurda.org> wrote: > > This is strange. I tested PharoLauncher 3.0.1 on Windows 10 and had no > problems. > Did you try to uninstall the previous launcher first? > > Yes, I did th

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-04 Thread Shaping
From: Shaping Sent: Wednesday, 4 May, 2022 02:46 To: 'Pharo Development List' Cc: 'Pharo-users' Subject: [Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released! On May 3, 2022, at 6:03 PM, Shaping < <mailto:shap...@uurda.org> shap...@uurda.org> wrote: > > This is

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-10 Thread Shaping
From: Shaping Sent: Wednesday, 4 May, 2022 02:46 To: 'Pharo Development List' Cc: 'Pharo-users' Subject: [Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released! On May 3, 2022, at 6:03 PM, Shaping < <mailto:shap...@uurda.org> shap...@uurda.org> wrote: > > This is

[Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released!

2022-05-05 Thread Shaping
From: Shaping Sent: Wednesday, 4 May, 2022 02:46 To: 'Pharo Development List' Cc: 'Pharo-users' Subject: [Pharo-dev] Re: [ANN] Pharo Launcher 3.0.1 released! On May 3, 2022, at 6:03 PM, Shaping < <mailto:shap...@uurda.org> shap...@uurda.org> wrote: > > This is

[Pharo-dev] FW: [Pharo-users] Porting from VW 8.3 to Pharo

2022-08-03 Thread Shaping
fully contained test package with no external dependencies as a first test, probably my Magnitude or Collection packages. Suggestions are welcome. Thanks for doing this and sharing it. Shaping From: christian.haider mailto:christian.hai...@smalltalked-visuals.com> > Sent: Wednesd

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: pdftalkPackageChanges

2022-08-04 Thread Shaping
? Shaping From: Shaping Sent: Thursday, 4 August, 2022 22:02 To: 'Pharo Development List' ; 'Pharo Development List' Subject: [Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: pdftalkPackageChanges The confusing thing is that PDFtalk is treated

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: pdftalkPackageChanges

2022-08-04 Thread Shaping
notation. The method reads ‘….Project’, but returns a ProjectChange instance. I’ll go with the stricter notation, and call my method ShapingProjectChange (I have one large Shaping bundle containing all pundles). The Transformer doesn’t seem to have the notion of a project, anyway, just

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: pdftalkPackageChanges

2022-08-04 Thread Shaping
yourself)) but it’s not the PDFtalk project. Bundle ‘PDFtalk Project’ is Why leave out the true top-level bundle? There’s no doubt that it’s the project bundle because its name include ‘Project’. Shaping From: Shaping Sent: Thursday, 4 August, 2022 20:26 To: 'An

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: pdftalkPackageChanges

2022-08-04 Thread Shaping
used to all the correct, yet dangling VW methods that are useless in VW, but which will become new code in the target image and there no longer appear to be dangling (with syntax highlighting aberrations). Odd looking but completely by design. Shaping From: Shaping Sent: Thursday, 4

[Pharo-dev] Re: [Pharo-users] Re: FW: Porting from VW 8.3 to Pharo

2022-08-03 Thread Shaping
his for many years. Thanks again. Shaping From: christian.haider mailto:christian.hai...@smalltalked-visuals.com> > Sent: Wednesday, 22 June, 2022 05:42 To: pharo-us...@lists.pharo.org <mailto:pharo-us...@lists.pharo.org> Subject: [Pharo-users] [PDFtalk] second fileOut for

[Pharo-dev] Re: [Pharo-users] Porting from VW 8.3 to Pharo

2022-08-03 Thread Shaping
sponsoring. Still let us know. Shaping about the spec questions esteban is on vacation and when he will reappear he will check the libgit change impacting us. Then the spec aspects. I’m trying to get by with the smaller fonts for labels and an 11 pt. Fira Code in the code pane. That doesn’t

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: doing first run soon

2022-08-05 Thread Shaping
it loads completely on the next run. That could take a while. Is that what you do in practice? I’m assuming the code writer is taking into account inter-package dependencies in order to get the load order right. Shaping From: christian.hai...@smalltalked-visuals.com Sent: Friday, 5

[Pharo-dev] Pharo's syntax highlighter

2022-08-05 Thread Shaping
my stuff from VW, with Christian's help. Thanks Christian. Here's the issue sketching what I want to do in the highlighter: https://github.com/pharo-project/pharo/issues/11505 Shaping

[Pharo-dev] Pharo's syntax highlighter

2022-08-05 Thread Shaping
this and porting my stuff from VW, with Christian's help. Thanks Christian. Here's the issue sketching what I want to do in the highlighter: https://github.com/pharo-project/pharo/issues/11505 Shaping

[Pharo-dev] Re: [Pharo-users] Re: [Pharo-users]Porting from VW 8.3 to Pharo: doing first run soon

2022-08-05 Thread Shaping
inter-package dependencies in order to get the load order right. Yes. Shaping From: christian.hai...@smalltalked-visuals.com <mailto:christian.hai...@smalltalked-visuals.com> mailto:christian.hai...@smalltalked-visuals.com> > Sent: Friday, 5 August, 2022 05:53 To: '

[Pharo-dev] Re: [Pharo-users]Porting from VW 8.3 to Pharo: Pharo100 fileOutValues

2022-08-04 Thread Shaping
className: #Color instanceChanges: (Array with: (Add method: #asColorValue code: #_ph_asColorValue))) is replacing #asColorValue with #_ph_asColorValue because some special Pharo-color conversion needs to happen. But how does #_ph_asColorValue get defined? It’s neither in VW nor in Pha