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

[Christian Haider]

All references disentangled. Everything should be clean now.

 

Happy hacking,

Christian

 

Von: Steffen Märcker  
Gesendet: Freitag, 5. Mai 2023 10:15
An: Any question about pharo is welcome 
Betreff: [Pharo-users] Re: Porting from VW to Pharo

 

Dear Christian,

 

I just gave it a try with a virgin 64 Bit 8.3 image and loaded

* Smalltalk Transform Project

* PDFtalk Project

* Pharo FileOut PDFtalk

 

The code loaded fine but I had a few hiccups with the tests.

* Many tests use #assert:equals: which SUnitToo (loaded automatically) 
surprisingly does not provide.

* After adding this method to TestCase, all but four test run. The Pattern that 
is used to match in

  - testVASmalltalkAddTimeAndVersion

  - testSqueakAddTimeAndVersion

  - testPharoAddTimeAndVersion

  - testGemstoneAddTimeAndVersion

  Did not take PUL into account. This works: '# From VisualWorks®*, * of * on * 
at *'

* In the following tests, some selectors cannot be found:

  - testMethodAddsForValuemap - #_gs_printvalueWith:

  - testMethodAddsForObject - #_gs_Symbol_literalString

  - testWriteSystemExtensionMethods - #_gs_printvalueWith:

 

Btw, I switched to SUnit to ease Porting to Pharo. I'll have a look into the 
#category parameter today.

 

OT PDFtalk: Do you have plans to support verifying signatures in PDF files or 
singing using a certificate?

 

Kind regards,

Steffen

 

 

Christian Haider schrieb am Mittwoch, 12. April 2023 21:07:05 (+02:00):

Hi Steffen,

 

thanks for trying and asking!

 

I was loading the code needed into a 8.3, 64bit virgin image and realized that 
loading is not that straight forward and described too briefly.

First, you need a non-default setting for the store prerequisites. I added this 
to the store access page:   
https://wiki.pdftalk.de/doku.php?id=storeaccess . It is critical to load the 
prereqs from store and not from parcels!

 

The first thing to load is the bundle {Smalltalk Transform Project}.

To see examples you need to load the subject of transformation: PDFtalk.

You need to load to top bundle {PDFtalk Project} which includes the test 
classes you are missing in your image.

At last, load the [Pharo Fileout PDFtalk] package.

I improved the landing page  
 
https://wiki.pdftalk.de/doku.php?id=smalltalktransform a bit to make this 
clearer.

 

I just tried and this loads without errors or warnings.

 

(Actually good that the load did not work for you, because I added a mistake in 
January which causes a 8.3 image to crash when you open a browser. Sorry for 
that.)

 

Now you should be all set for generating a fileout of PDFtalk for Pharo (in the 
current unfinished state).

 

Thanks for spotting the problems with the documentation. I will get over it 
tomorrow.

I am quick in renaming and making structural changes when things are not 
working as I want… But the docs should be correct, of course.

 

 

About the project structure.

Currently, everything belonging to a project, need to be transformed in one go. 
This is not a big deal, because all code transformations are described on the 
package level and can be easily recombined as the bundle structure changes.

 

The last piece of the transformation puzzle is to make the transformations 
modular, so that the renamings of prerequisite packages can be used without the 
need to transform the prereqs as well. I hope to get at that soon…

In the meantime, I would start with your Core project to get a feel for the 
mechanics. I am sure the rest will fall nicely into its places.

 

About how to structure your code in Pharo with Git, I don’t know much about 
that. Actually, I would also be interested in some guidelines to bake them into 
the transformations…

 

If you are seriously interested, we could have an online session to hack around 
with it…

 

Cheers,

Christian

 

 

Von: Steffen Märcker mailto:merk...@web.de> > 
Gesendet: Dienstag, 11. April 2023 17:52
An: Any question about pharo is welcome mailto:pharo-users@lists.pharo.org> >
Betreff: [Pharo-users] Re: Porting from VW to Pharo

 

Dear Christian and Richard,

 

thanks for your answers. I'll try to go through the process step by step and 
come back with questions to the list if that's okay.

 

First, after loading the "Pharo Fileout PDFTalk", VW (8.3, 64 Bit) shows two 
unloadable definitions:

- PostscriptInterpreterTests>>_ph_testOperatorNotFound
- ColorValueTest>>_ph_testBridgedNamedColors

Both classes are not loaded

 

 

 

Second, it appears that some of the selectors mentioned on  
 
https://wiki.pdftalk.de/doku.php?id=smalltalktransformdocumentation have been 
renamed, e.g., PackageChanges>>unusedClasses

 

More general, regarding project structure. What is the best approach to port a 
project that consists of multiple loosely coupled packages (not in a

[Pharo-users] Re: [Pharo-dev] Pharo VM Release - v10.0.5

[Noury Bouraqadi]

Many thanks to the Pharo team!

Noury
On May 5 2023, at 7:22 pm, teso...@gmail.com wrote:
> Hello,
> we have released a new version of the Pharo VM for Pharo 11. This VM is 
> accessible right now from Zero-Conf, updating it in the Pharo Launcher or 
> using the usual downloads (as described in pharo.org/download 
> (http://pharo.org/download)). Also, OBS packages are ready to be updated 
> using your distribution package manager.
>
> This is the new VM that will be stable for Pharo 11 release and Pharo 12 
> alpha, it is also compatible with Pharo 10 images but it is not the default 
> for Pharo 10.
> Changelog
>
> * Testing scavenger tenuring by @PalumboN in 
> https://github.com/pharo-project/pharo-vm/pull/588
> * Deleting Pharo image from the VM repo by @jordanmontt in 
> https://github.com/pharo-project/pharo-vm/pull/591
> * Cleaning Up Third Party Libraries by @tesonep in 
> https://github.com/pharo-project/pharo-vm/pull/581
>
> **Full Changelog**: 
> https://github.com/pharo-project/pharo-vm/compare/v10.0.4...v10.0.5
>
> Thanks a lot, and any doubt please let us know.
> Cheers,
>
> Pablo on behalf of the whole Pharo team.
> --
>
> Pablo Tesone.
> teso...@gmail.com (mailto:teso...@gmail.com)
>
>