Hi Steffen,
2017-06-06 7:44 GMT-03:00 Steffen Märcker <[hidden email]>: > I assumed so. I used file-outs only to get something working quickly. =) > Properly published code will follow as soon as I am more familiar with code > management in Pharo. I'm coming back to this. What was the choosen tool? I tried FileOuterNG but it doesn't work in VW PUL 8.2, and I don't understand the reasoning behind the "bindings" mappings (it fails when building the default mappings). The FileOut30 package doesn't seem to respect encodings at all. Thanks! Esteban A. Maringolo |
I think I used FileOut30 and encodings were part of the adhoc fixing before loading into Pharo (using iconv certainly, but I don't recall) On 21 March 2018 at 14:29, Esteban A. Maringolo <[hidden email]> wrote: Hi Steffen, |
In reply to this post by Steffen Märcker
On Fri, Jun 2, 2017, 17:05 Steffen Märcker <[hidden email]> wrote: Dear all, #beReadOnlyObject. Pharo 6.1 and onwards. #beWritable to revert.
|
In reply to this post by Esteban A. Maringolo
Hi esteban
It was to manage namespace (from memory). Stef On Wed, Mar 21, 2018 at 2:29 PM, Esteban A. Maringolo <[hidden email]> wrote: > Hi Steffen, > > 2017-06-06 7:44 GMT-03:00 Steffen Märcker <[hidden email]>: >> I assumed so. I used file-outs only to get something working quickly. =) >> Properly published code will follow as soon as I am more familiar with code >> management in Pharo. > > I'm coming back to this. What was the choosen tool? I tried > FileOuterNG but it doesn't work in VW PUL 8.2, and I don't understand > the reasoning behind the "bindings" mappings (it fails when building > the default mappings). > > The FileOut30 package doesn't seem to respect encodings at all. > > Thanks! > > Esteban A. Maringolo > |
Free forum by Nabble | Edit this page |