Hi If in the process you discover easy changes on the pharo side that can be either integrated in Pharo or packages from the Pharo side to help migration let us know. We would like to help but we are really really super full. I tried to help to package values but I did not understand the process (I know the pharo way for sure to define baseline). Now a part of the team is really concentrated to improve the VM (we would like to have a 1.5 speed up) but it requires work and concentration. We are also working on permanent space and better memory management thanks for lifeware 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. S > On 3 Aug 2022, at 16:03, Shaping <shap...@uurda.org> wrote: > > Hi Christian. > > I’m trying to port from VW 8.3 to Pharo. Is there a detailed algorithm in > addition to the Workflow section mentioned here?: > > https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout > <https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout> > > generate the source for the target dialect from VisualWorks with the defined > code transformations. Fix problems so that there are no errors or warnings. > … > > How does one generate the source (run the transformation)? Where are the > aforementioned “defined code transformations”, Is there an example of how > to setup the declarative template needed to map VW namespace names to Pharo > class prefixes? > > I loaded the following packages into my VW 8.3 image: > > Values Project > Values > Values Fileout Pharo > Values Testing > Values Tools > Values Tools Testing > > Pharo Fileout Values > Pharo Transform > > Smalltalk Transform Project > Smalltalk Transform TestBundle > Smalltalk Transform Tests > Smalltalk Transform > Smalltalk Transform Model > Smalltalk Transform Testing > Smalltalk Transform TestPackage > Smalltalk Transform Tools > > Any package not updated recently (in the last few months) I didn’t load. > Did I miss anything? > 2. Port the Values package. This is easy, since no namespaces are involved. > > > This first instruction after VW package setup says to port the contents of > the Values package from VW to Pharo. Do you mean manually? Probably not. > > I feel like I’ve missed the main details of how to start the transformation. > I’d like to do a small 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 <christian.hai...@smalltalked-visuals.com > <mailto:christian.hai...@smalltalked-visuals.com>> > Sent: Wednesday, 22 June, 2022 05:42 > To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: [Pharo-users] [PDFtalk] second fileOut for Squeak and Pharo > > With help from the community some issues were fixed which improved the test > statistics nicely. > Check it out: > https://wiki.pdftalk.de/doku.php?id=portingblog#second_pdftalk_fileout_for_squeak_and_pharo > > <https://wiki.pdftalk.de/doku.php?id=portingblog#second_pdftalk_fileout_for_squeak_and_pharo> > > > Thanks to everybody involved! > > Happy hacking, > Christian
