- Pharo-users - lists.pharo.org

Re: [Pharo-users] Loading and saving packages to filetree repos

by Thierry Goubier

Hi Luke, ok, it's a high tech solution, this is more because I could not on the spot remember what you would need as a script (and also because your 'no metadata' requirement makes the filetree solution problematic). But I'd suggest still one bit of advice that is implicit in my solution: create at least a baseline for your project (covering say all packages in your repository); instead of hacking around with Monticello and FileTree, it will allow you to use a simple Metacello command to load everything and prepare correct, long term use of your project. And you will have the save everything as well. Regards, Thierry Le 20/08/2017 Ã 10:36, Luke Gorrie a Ã©crit : > Hi Thierry, > > I am really looking for a "low-tech" solution here - five line > Monticello code snippet - that will be easy for me to understand (as a > newbie) and also easy for new contributors to my project to understand > (who will have no prior exposure to Pharo.) > > I don't know what AltBrowser is, but just as a user I need to get a bit > more "winnage" before I am ready to take another iteration at learning > more tools. The tools currently represent barriers in the way of solving > my problems. I am sure this will change over time with more gradual > learning and experience. > > > On 18 August 2017 at 16:28, Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>> wrote: > > Hi Luke, > > if you use gitfiletree with AltBrowser and configurations/baselines, > then you'll see that you have a command to do the writing for you, > without metadata and with a single git commit. > > Regards, > > Thierry > > > Le 17/08/2017 Ã 13:25, Luke Gorrie a Ã©crit : > > Hoi, > > I want to have a quick "cheat mode" for loading and saving the > Smalltalk packages in my project. This is to make life easy for > newbies who are not very familiar with Monticello and Metacello. > > The "cheat" is to assume that there is one filetree:// > repository that contains all of the relevant packages, and all > we need to do is load or save each of those packages in that > repository. > > I have the loading part working already: > > repo := MCFileTreeRepository new directory: '/foo/bar/baz' > asFileReference. > repo allFileNames do: [ :file | > (repo versionFromFileNamed: file) load. > ]. > > but now I am wondering how to do the saving part? That is, given > a path to a filetree repo like '/foo/bar/baz', how do I save > each package in that repo i.e. export the code in the image? > > Ideally I would like the same operation to skip metadata that is > likely to cause conflicts when the code is checked into Git > later e.g. package timestamps and versions. > > Tips would be appreciated :). > > > > > >

Aug. 20, 2017

[ANN] Pharo wiki , is here

by Torsten Bergmann

>> Many seemed to like the idea of a Pharo wiki , I like it too. I created >> one, can be found here and super easy to contribute to. >> >> https://github.com/SquareBracketAssociates/PharoWiki I still prefer to have one based on Smalltalk and as there never was an official one maintain my own private hosted Pharo wiki since 2015 http://wiki.astares.com/pharo including lots of useful informations. It us a Swiki server ("Winterlong" release) - so it is based on Squeak + Comanche. http://wiki.squeak.org/swiki/ I once offered it to the community but there were doubts as Swiki is not more maintained and a Pharo solutions would be preferable. Unfortunately there never was a Pharo based wiki implementation although we have all the bits and pieces (Pillar, Teapot/Tealight, Zinc, ...) to write one. I have several swikis running over the years and all of them run very very stable and without any problems. Even in case of trouble they are easy to repair and extend as the content is written into XML files. Also it has an UNZIP and go concept - so it is easy to install/run and maintain or move to a different server. Squeak community is running their swiki for years already. The only problem there is that it is not well maintained and lost of pages are outdated - but this is a problem independent from the wiki technology used. So creating a wiki is quick and easy - be able to maintain up to date infos another issue. Thanks T.

Aug. 20, 2017

Re: [Pharo-users] [ANN] Pharo wiki , is here

by Stephane Ducasse

I added some links to books and blogs. On Sat, Aug 19, 2017 at 11:20 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I also turned it to be published as a webpage, its can be viewed from this > link > > https://squarebracketassociates.github.io/PharoWiki/ > > On Sat, Aug 19, 2017 at 11:54 PM Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: >> >> Many seemed to like the idea of a Pharo wiki , I like it too. I created >> one, can be found here and super easy to contribute to. >> >> https://github.com/SquareBracketAssociates/PharoWiki >> >> Will keep this thread for alerting for important updates to wiki. Have fun >> :)

Aug. 20, 2017

Pharo on the SqueakJS virtual machine

by Torsten Bergmann

Craig Latta wrote >The next big step is getting a WebAssembly version of Cog running. Anyone known already to work on such a beast? Or is this question better asked on vm-dev? Another path could be to run on a Linux booting in the browser: https://bellard.org/jslinux/ Regards T.

Aug. 20, 2017

Re: [Pharo-users] Loading and saving packages to filetree repos

by Luke Gorrie

Hi Thierry, I am really looking for a "low-tech" solution here - five line Monticello code snippet - that will be easy for me to understand (as a newbie) and also easy for new contributors to my project to understand (who will have no prior exposure to Pharo.) I don't know what AltBrowser is, but just as a user I need to get a bit more "winnage" before I am ready to take another iteration at learning more tools. The tools currently represent barriers in the way of solving my problems. I am sure this will change over time with more gradual learning and experience. On 18 August 2017 at 16:28, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Luke, > > if you use gitfiletree with AltBrowser and configurations/baselines, then > you'll see that you have a command to do the writing for you, without > metadata and with a single git commit. > > Regards, > > Thierry > > > Le 17/08/2017 Ã 13:25, Luke Gorrie a Ã©crit : > >> Hoi, >> >> I want to have a quick "cheat mode" for loading and saving the Smalltalk >> packages in my project. This is to make life easy for newbies who are not >> very familiar with Monticello and Metacello. >> >> The "cheat" is to assume that there is one filetree:// repository that >> contains all of the relevant packages, and all we need to do is load or >> save each of those packages in that repository. >> >> I have the loading part working already: >> >> repo := MCFileTreeRepository new directory: '/foo/bar/baz' >> asFileReference. >> repo allFileNames do: [ :file | >> (repo versionFromFileNamed: file) load. >> ]. >> >> but now I am wondering how to do the saving part? That is, given a path >> to a filetree repo like '/foo/bar/baz', how do I save each package in that >> repo i.e. export the code in the image? >> >> Ideally I would like the same operation to skip metadata that is likely >> to cause conflicts when the code is checked into Git later e.g. package >> timestamps and versions. >> >> Tips would be appreciated :). >> >> >> >> > >

Aug. 20, 2017

Re: [Pharo-users] Tealight (similar to Teapot) installs fine in Pharo 6.1

by Torsten Bergmann

Hi Hannes, thanks, glad you like it. All that would not have been possible without Teapot and Zinc, so again a big thanks from my side to Attila and Sven! Bye T. > Gesendet: Samstag, 19. August 2017 um 15:06 Uhr > Von: "H. Hirzel" <hannes.hirzel(a)gmail.com> > An: "Torsten Bergmann" <astares(a)gmx.de> > Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Betreff: Tealight (similar to Teapot) installs fine in Pharo 6.1 > > Hello Torsten > > Tealight installs very fine into the latest Pharo release (6.0 / 6.1). > > It is easy to use and the documentation is great! > > --Hannes

Aug. 20, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Craig Latta

Hi Sean-- > > https://tinyurl.com/y727fz4a > > Cool! > > A few things: > - There is a very noticeable lag (e.g. ~5 seconds to open an "About" > window). Any idea what it would take to deliver performance levels > that feel more native? The next big step is getting a WebAssembly version of Cog running. Until then, we're riding the performance improvements in the web browser JavaScript engines. At the moment, Chrome seems a lot faster than the others. Bert's just-in-time translation of compiled methods to JS (which the web browser's JS engine then translates to native code) helped a lot. > - I wonder how Tether compares to Denis' Seamless I think Tether's serialization takes more advantage of the fact that the participants are live Smalltalk systems with many of the same objects already in all locations. Tether also attempts to allow remote messages with parameters from multiple object memories (e.g., in a context on machine A, a message is sent to an object on B, with parameters on C and D). > - I was going to ask the same question for Naiad vs Epicea, but after > reading on your blog, it seems Naiad is much more ambitious than > simply tracking changes Yes, Naiad is ultimately a deployment vehicle, enabling the accurate construction and deconstruction of systems. I want a coherent way to release apps and work in teams, livecoding all the time. > - I got a few errors off the bat > - UnixResolver>>#cantFindOriginError from #getEnvViaFFI > - "The primitiveFetchMourner is missing. Please upgrade your virtual > machine..." Mm, I haven't delved into any of the non-fatal Pharo errors yet. :) thanks! -C -- Craig Latta Black Page Digital Amsterdam :: San Francisco craig(a)blackpagedigital.com voice through 2017-09-12: + 1 510 833 5799 (SMS ok) +31 20 893 2796 (no SMS)

Aug. 20, 2017

[Ann] [Grafoscopio] New release with major improvements

by Offray Vladimir Luna CÃ¡rdenas

Hi, In Grafoscopio, we follow a rolling release model, so we don't make a lot of noise about new versions, but this one has several features worthy to mention: a. Pharo 6 & 6.1 support, with out of the box 64 bits support on Mac and Gnu/Linux. b. Improved support for documentation: Now we have a GrafoscopioDocumentation object that defines documentation as a (Fossil) repository with a list of documents inside and is able to download and update them to their last version using the standard Fossil JSON API. c. Improved traceability: The usual document workflow in Grafoscopio is to create a notebook (i.e notebook.ston), export it as Markdown (notebook.markdown) and convert it to PDF (notebook.pdf) or HTMl (notebook.html). Now in the notebook.ston --> notebook.markdown --> notebook.pdf workflow, the exported/derived file contains the checksum of the last saved source file where it comes from. So, notebook.markdown contain the checksum of notebook.ston in the YAML metadata block [1][2], and notebook.pdf can show the checksum of the notebook.markdown, as exemplified in the User Manual [3]. [1] http://pandoc.org/MANUAL.html#extension-yaml_metadata_block [2] http://mutabit.com/repos.fossil/grafoscopio/artifact?name=99778d46ef034389&… [3] http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/ma… d. Metadata config nodes: Now notebook internalizes the environment (as Smalltalkers and Lispers[4] like ;-)). "%medatata" nodes (see image below) allow a Grafoscopio notebook to define and control the command line options used by the operative system to export the notebook to other formats and enables the notebook to feedback such options with information provided/calculated by the notebook itself. This improves reproducibility greatly, because notebook now describes even the external operations to it, to create other derived files (Markdown, PDF, LaTeX and so on) and to interact with the operative system where it resides (currently this only works on Unix like operative systems like Mac and Gnu/Linux). Such configuration options are defined in plain Pharo, using just dictionaries and dynamic arrays, with some special keys. [4] https://youtu.be/JnczIyPXGfc?t=2548 e. Support for multiple tags in a node: Until now the only allowed tag was 'cÃ³digo' (code), but now tags can be almost arbitrary. This will open new ways to process and display the notebook document tree, once the proper GUI features and interactions are developed. f. Updated and corrected documentation: English User Manual has been improved to reflect new features and several typos and errors have been corrected. Last stable Grafoscopio version is available from the Pharo Catalog, and remember to run the update, frequently. Enjoy, Offray

Aug. 20, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Sean P. DeNigris

Craig Latta wrote > For more details, see https://tinyurl.com/y727fz4a Cool! A few things: - There is a very noticable lag (e.g. ~5 seconds to open an "About" window). Any idea what it would take to deliver performance levels that feel more native? - I wonder how Tether compares to Denis' Seamless - I was going to ask the same question for Naiad vs Epicea, but after reading on your blog, it seems Naiad is much more ambitious than simply tracking changes - I got a few errors off the bat - UnixResolver>>#cantFindOriginError from #getEnvViaFFI - "The primitiveFetchMourner is missing. Please upgrade your virtual machine..." ----- Cheers, Sean -- View this message in context: http://forum.world.st/Re-PharoJS-tp4952267p4962614.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-users] [ANN] Pharo wiki , is here

by Dimitris Chloupis

I also turned it to be published as a webpage, its can be viewed from this link https://squarebracketassociates.github.io/PharoWiki/ On Sat, Aug 19, 2017 at 11:54 PM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Many seemed to like the idea of a Pharo wiki , I like it too. I created > one, can be found here and super easy to contribute to. > > https://github.com/SquareBracketAssociates/PharoWiki > > Will keep this thread for alerting for important updates to wiki. Have fun > :) >

Aug. 19, 2017