August 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Minimizing an Application

by Dimitris Chloupis

I still dont know what opening has to do with transmitting, even when you do it remotely , a socket / websocket connection should be all you need. For me transmitting the entire image would be necessary only in the case you want to install it remotely and that remote location has no immediate access to the installation. On Fri, Aug 25, 2017 at 7:14 AM Ben Coman <btc(a)openinworld.com> wrote: > I understand that to mean effectively that you are "opening" the image > across the net - so eventually you need to whole image transmitted, but you > don't have to wait for the whole thing before you start running it. > cheers -ben > > > On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > >> Indeed that can be a barrier but why you would want to transmit an >> entire image instead of portion of it using something like fuel files or >> other binary formats ? It would dramatically reduce the size of data you >> transmit. >> >> On Thu, Aug 24, 2017 at 8:10 PM Craig Latta <craig(a)blackpagedigital.com> >> wrote: >> >>> >>> > ...10mbs which is the size pharo image can be reduced to is nothing >>> > for todays TBs hard drives and GBs flash drives and online storage. >>> > Unless you do an embedded app and 10 mbs are huge for your limited >>> > storage. >>> >>> Or you want to minimize initial startup time, including the time it >>> takes to transmit the entire system over the net. >>> >>> >>> -C >>> >>> -- >>> Craig Latta >>> Black Page Digital >>> Amsterdam :: San Francisco >>> craig(a)blackpagedigital.com >>> voice through 2017-09-12: >>> + 1 510 833 5799 <(510)%20833-5799> (SMS ok) >>> +31 20 893 2796 <+31%2020%20893%202796> (no SMS) >>> >>> >>> >

Aug. 25, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by Norbert Hartl

> Am 24.08.2017 um 22:34 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > In Pharo 60 (and not in Pharo 50) I extracted the command line logic > into a specific object so that we do not have to be bound to use the > command line. You can have a look in the CLI package. > > This is good that there is Section 7 this in the doc. We started to > build a simple Morphic renderer for Pillar. > We should continue. If someone wants to have fun. This would be nice > to have see it coming to live. > A morphic renderer? Wouldn't it be fun to do one for bloc? I think we should slowly collect some tools that use bloc in order to get the tension making it the "default" thingie. > On my todo: I also want to use mustache inside Pharo and not > generating files on the disk. > That should be doable by deleting some code. Norbert > Stef > > On Fri, Aug 18, 2017 at 10:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Exactly. >> >> Section 7 of >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> has an example >> >> >> | wiki | >> wiki := '!My Document'. >> PRPillarParser parse: wiki >> >> >> Or >> >> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >> readStream >> >> >> and then >> >> >> PRHTMLWriter write: document >> >> >> This put together gives >> >> PRHTMLWriter write: ( >> PRPillarParser parse: (FileSystem workingDirectory / 'welcome.pillar') >> ) >> >> >> If I inspect the result of this expression I get the HTML string. >> >> Thank you Cyril. This is what I was looking for. >> >> --Hannes >> >> >> >> >> On 8/18/17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> On ven. 18 aoÃ»t 2017 at 21:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> >>>> Thank you Cyril for the link to the tutorial. >>>> >>>> >>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>>> >>>> I see that Pillar is a command line tool. The welcome example taken >>>> from this tutorial is: >>>> >>>> Pharo.exe Pillar.image pillar export --to=html >>>> --outputFile=welcome welcome.pillar >>>> >>>> How can I run a command like this from within Pharo in a "playground" >>>> (former workspace)? >>>> >>>> Later on I plan to construct a simple GUI with text boxes for Pillar >>>> sources and have some buttons executing these commands. >>>> >>>> --Hannes >>>> >>>> >>> >>> I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it >>> is still up to date but you can try to check part 7 of the doc I sent. >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> http://www.synectique.eu >>> 2 rue Jacques PrÃ©vert 01, >>> 59650 Villeneuve d'ascq France >>> >>

Aug. 25, 2017

Re: [Pharo-users] SmartTest - ESUG 2017 - Trailer

by Tudor Girba

The bar is getting higher :) Doru > On Aug 24, 2017, at 10:18 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > :) > Ready for the ESUG innovation award competition. > > > On Thu, Aug 24, 2017 at 6:49 PM, Dimitris Chloupis > <kilon.alios(a)gmail.com> wrote: >> lol by far the most funny pharo teaser I have watched and the tool looks >> extra useful , well done :) >> >> On Thu, Aug 24, 2017 at 6:33 PM Benoit Verhaeghe <benoit.verhaeghe(a)inria.fr> >> wrote: >>> >>> Hi everyone, >>> >>> I'm glad to present you the trailer of SmartTest for ESUG >>> https://www.youtube.com/watch?v=jAvfdN2z5-s >>> >>> BenoÃ®t Verhaeghe > -- www.tudorgirba.com www.feenk.com "No matter how many recipes we know, we still value a chef."

Aug. 25, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by john pfersich

I don't know if it matters, but on my Retina 5K, 27 inch, Late 2015 iMac, AMD Radeon R9 M395 wirh 2048 MB running MacOS 10.12.6 I don't have a problem resizing or maximizing Pharo 6.1. On Mon, Jul 31, 2017 at 6:28 AM, Ted F.A.van Gaalen <tedvga(a)gmail.com> wrote: > > > > Hi, I reverted to 5.0 because Pharo 6.0 and 6.1 64 bit hangs on > my Mac Mini with UDH 4K screen (may that has to do with?) > with its maiden image (at first start after download > when: I resize or go to full screen. Maybe VM problem? > my mac Mini metrics: > *Hardware Overview:* > > Model Name: Mac mini > Model Identifier: Macmini6,2 > Processor Name: Intel Core i7 > Processor Speed: 2,6 GHz > Number of Processors: 1 > Total Number of Cores: 4 > L2 Cache (per Core): 256 KB > L3 Cache: 6 MB > Memory: 4 GB > Boot ROM Version: MM61.0106.B1F > SMC Version (system): 2.8f0 > > maybe this problem was already reported, but could find it. > > > Kind Regards > TedvG > > > >

Aug. 25, 2017

Re: [Pharo-users] Object>>#name deprecated in Pharo 6 -- what do I need to do?

by Ben Coman

I don't have an Image to check, but I believe Object>>name just does "^self printString", so by default, in your application send #printString instead of #name. cheers -ben P.S. Perhaps this would be a good candidate for automated rewrite? On Thu, Aug 24, 2017 at 8:49 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello > > In the last days there was a discussion that > > Object>>#name > > > should no longer be used. I did not follow the discussion in detail. > What was decided how #name should be replaced? > > What do I need to do if I get a deprecation warning [1]? > > > Thanks for the answer in advance > > Hannes > > > > > [1] > The method Object>>#name called from PPCMNode>>#gtTreeViewIn: has been > deprecated. > Implement your own domain representation of an object, or use > #asString or #printString instead. > > Select Proceed to continue, or close this window to cancel the operation. > >

Aug. 25, 2017

Re: [Pharo-users] Minimizing an Application

by Ben Coman

I understand that to mean effectively that you are "opening" the image across the net - so eventually you need to whole image transmitted, but you don't have to wait for the whole thing before you start running it. cheers -ben On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Indeed that can be a barrier but why you would want to transmit an entire > image instead of portion of it using something like fuel files or other > binary formats ? It would dramatically reduce the size of data you > transmit. > > On Thu, Aug 24, 2017 at 8:10 PM Craig Latta <craig(a)blackpagedigital.com> > wrote: > >> >> > ...10mbs which is the size pharo image can be reduced to is nothing >> > for todays TBs hard drives and GBs flash drives and online storage. >> > Unless you do an embedded app and 10 mbs are huge for your limited >> > storage. >> >> Or you want to minimize initial startup time, including the time it >> takes to transmit the entire system over the net. >> >> >> -C >> >> -- >> Craig Latta >> Black Page Digital >> Amsterdam :: San Francisco >> craig(a)blackpagedigital.com >> voice through 2017-09-12: >> + 1 510 833 5799 <(510)%20833-5799> (SMS ok) >> +31 20 893 2796 <+31%2020%20893%202796> (no SMS) >> >> >>

Aug. 25, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by Ben Coman

What happens if you untick "Use FreeType" in System > Settings? cheers -ben On Thu, Aug 24, 2017 at 10:06 PM, TedVanGaalen <tedvga(a)gmail.com> wrote: > yes, after full screen -> normal window -> minimise -> reshow it did. > (not in any particular order, tried al those before as well) > > TedvG > > > On 24. Aug 2017, at 15:46, EstebanLM [via Smalltalk] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4963891&i=0>> wrote: > > and image still freezing? > > Esteban > > On 24 Aug 2017, at 15:28, TedVanGaalen <<a href="x-msg://3/user/ > SendEmail.jtp?type=node&node=4963878&i=0" target="_top" > rel="nofollow" link="external" class="">[hidden email]> wrote: > > Hi Esteban, > unfortunately that doesnât make any difference. > What I did: > extension temporarily renamed to â¦..wasAdylib > Started Pharo app by clikcing on it (gets the downloaded maiden image) > then: > âFT2Error:Freetype2 primitive failed [error -1][canât get error string]â > > >

Aug. 25, 2017

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

by Dimitris Chloupis

On Thu, Aug 24, 2017 at 11:32 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > You have Netstyle/Workflow too. > done "Why are you using markup documents to create the wiki when you could use Github wiki itself? For portability?" good question. Yes for flexibility , another reason however is that Github wiki is a separate repo and I did not want that because in the very back of my head I am considering the option of creating software to allow access to wiki from inside Pharo and I wanted to be all (content and code) in the same repo. Its a very low priority for now. Also Github wiki is basically the same as I am doing with some extra format (table of contents) , in my case I dont care because Github allows me to define HTML templates that will format the wiki webpage and make it look a a lot more polished that pharo wiki looks like. Generally there are some cool stuff you can do with Markdown and Github , plus the fact that markdown can embed HTML etc. There is also the option of Gitbook which has some nice features for generating polished and well structured documentation. So I like to keep my options open. For now I am focusing 100% on content.

Aug. 24, 2017

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

by Esteban A. Maringolo

Why are you using markup documents to create the wiki when you could use Github wiki itself? For portability? Esteban A. Maringolo 2017-08-24 9:59 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Actually I have already done this > > https://github.com/SquareBracketAssociates/PharoWiki/blob/master/contents/p… > > when he announced the project on the mailing list, but thanks for trying to > inform me, I appreciate it. I will try to update the wiki each time > something new pops up in the mailing list that is usable which means > a) new project > b) some kind of news of general interest about pharo > c) some kind of documentation (article, pdf, power point, blog post etc) > about pharo or third party library/tool > > On Thu, Aug 24, 2017 at 3:38 PM H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Another thing to add >> >> link to >> https://github.com/dionisiydk/TelePharo >> >> with short description >> >> Complete toolset for remote development of Pharo images. It includes: >> >> remote playground >> remote browser >> remote debugger >> remote inspector >> remote process browser >> >> >> >> On 8/22/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> > absolutely >> > >> > done ! >> > >> > >> > https://github.com/SquareBracketAssociates/PharoWiki/blob/master/contents/p… >> > >> > On Tue, Aug 22, 2017 at 10:28 PM Stephane Ducasse >> > <stepharo.self(a)gmail.com> >> > wrote: >> > >> >> You should add the script that generate the list of catalog items so >> >> that we can update it. >> >> >> >> On Tue, Aug 22, 2017 at 8:18 PM, Dimitris Chloupis >> >> <kilon.alios(a)gmail.com> wrote: >> >> > Ok I restructured the wiki , giving it a table of contents. >> >> > >> >> > Added Pharo 6 Catalog projects >> >> > Added PettitParser2 >> >> > Added a sections for How tos , and a couple of them >> >> > Added a news section >> >> > Added a link to Grafoscopio homepage at its Catalaog section >> >> > Added a wikis section with a link to Astares Pharo wiki >> >> > >> >> > Keep your suggestions coming , thank you Hirzel >> >> > >> >> > https://squarebracketassociates.github.io/PharoWiki/ >> >> > >> >> > >> >> > On Mon, Aug 21, 2017 at 7:19 PM H. Hirzel <hannes.hirzel(a)gmail.com> >> >> wrote: >> >> >> >> >> >> Please add the reference to the PetitParser2 book >> >> >> >> >> >> https://kursjan.github.io/petitparser2/pillar-book/build/book.html >> >> >> >> >> >> On 8/21/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> >> > And this one produces a catalog list in markdown format >> >> >> > >> >> >> > "Produce a list of Pharo 6 catalog entries (tag: 'Pharo 6.0')" >> >> >> > | catalog | >> >> >> > catalog := CatalogProvider default retrieveProjects select: [ :x >> >> >> > | >> >> >> > (x at: 'repositoryUrl') = >> >> >> > 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]. >> >> >> > >> >> >> > Transcript show: '# Pharo 6 catalog list'; cr. >> >> >> > >> >> >> > (catalog asSortedCollection: [ :a :b | (a at: 'name') < (b at: >> >> >> > 'name') >> >> >> > ]) do: [ :entry | Transcript show: '## ', (entry at: 'name') ; cr; >> >> >> > show: (entry at: 'description'); cr;cr. >> >> >> > Transcript show: 'keywords: '. >> >> >> > (entry at: 'keywords') sorted do: [ :keyword | Transcript >> >> >> > show: >> >> >> > keyword; space ]. >> >> >> > Transcript cr; cr]. >> >> >> > >> >> >> > Transcript show: '# Pharo 6 catalog list - description is >> >> >> > missing'; >> >> cr. >> >> >> > >> >> >> > (catalog asSortedCollection: [ :a :b | (a at: 'name') < (b at: >> >> >> > 'name') >> >> >> > ]) >> >> >> > do: [:entry | (entry at: 'description') ifNil: [ Transcript show: >> >> >> > '- >> >> >> > ', (entry at: 'name'); cr ] >> >> >> > ]. >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> ................................................................................................ >> >> >> > >> >> >> > >> >> >> > # Pharo 6 catalog list >> >> >> > ## Animation >> >> >> > Adds a delay operator turning any message send into a smooth >> >> transition. >> >> >> > >> >> >> > keywords: animation fun time >> >> >> > >> >> >> > ## Artefact >> >> >> > Artefact is a library to generate PDF documents. It provides a >> >> >> > document model and support the generation of PDF >> >> >> > >> >> >> > keywords: PDF document layout >> >> >> > >> >> >> > ## AstaresDistribution >> >> >> > Several Pharo goodies like Pomodoro, DesktopManager, QuickAccess, >> >> >> > HubCap, ScriptManager, ... written by Torsten Bergmann >> >> >> > (astares.com) >> >> >> > bundled for easy installation >> >> >> > >> >> >> > keywords: custom distribution goodies pharo >> >> >> > >> >> >> > ## Atlas >> >> >> > A Python bridge (IPC - stream sockets) for Pharo, allowing Pharo >> >> >> > to >> >> >> > use Python libraries , mix with Python code and vice versa >> >> >> > >> >> >> > keywords: Atlas IPC atlas pharo python sockets >> >> >> > >> >> >> > ## BitmapCharacterSet >> >> >> > BitmapCharacterSet is a set for characters that uses a bitmap for >> >> >> > storing wide characters and an array of truth values for byte >> >> >> > characters. Used by XMLParser. >> >> >> > >> >> >> > keywords: character collection set unicode >> >> >> > >> >> >> > ## Bootstrap >> >> >> > "Bootstrap for Seaside" is a project combining Seaside and Twitter >> >> >> > Bootstrap and easily use them to write professional looking web >> >> >> > applications. >> >> >> > >> >> >> > keywords: Bootstrap HTML Seaside query web >> >> >> > >> >> >> > ## Bugzilla >> >> >> > Pharo wrapper for Bugzilla REST API >> >> >> > >> >> >> > keywords: api bugzilla rest >> >> >> > >> >> >> > ## CPPBridge >> >> >> > CPP is a library that allows Pharo to share memory with a C++ >> >> >> > application. This means that both can share the exact same data >> >> >> > and >> >> >> > modify it. This also can allow Pharo and C++ to exacute one >> >> >> > another >> >> >> > library and code. Example provided >> >> >> > >> >> >> > keywords: ++ ++ C IPC bridge c cpp file mapped memory shared >> >> >> > >> >> >> > ## Calypso >> >> >> > Calypso is a new system browser based on new navigation model >> >> >> > >> >> >> > keywords: IDE systemBrowser >> >> >> > >> >> >> > ## CheatSheet >> >> >> > >> >> >> > Pharo Cheat Sheet. >> >> >> > >> >> >> > Project main page: >> >> >> > *http://www.smalltalkhub.com/#!/~PharoExtras/CheatSheet* >> >> >> > >> >> >> > keywords: examples syntax >> >> >> > >> >> >> > ## ChronosManager >> >> >> > ChronosManager is a time managment tool based on the pomodoro >> >> >> > technique offering a stopwatch and timer for keeping track of time >> >> >> > with tasks and goals >> >> >> > >> >> >> > keywords: ChronosManager managment pomodoro time >> >> >> > >> >> >> > ## Citezen >> >> >> > Citezen is a library to parse, query and manage bibtex scientific >> >> >> > citations. >> >> >> > >> >> >> > keywords: bibtex latex parser printer query >> >> >> > >> >> >> > ## CommandShell >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## Commander >> >> >> > Commander models application actions as first class objects. >> >> >> > >> >> >> > Every action is implemented as separate command class (subclass of >> >> >> > CmdCommand) with #execute method and all state required for >> >> >> > execution. >> >> >> > >> >> >> > Commands are reusable objects and applications provide various >> >> >> > ways >> >> >> > to >> >> >> > access them. Such information is attached to command classes as >> >> >> > activator objects. Currently there are three types of activators: >> >> >> > - CmdShortcutCommandActivator >> >> >> > - CmdContextMenuCommandActivator >> >> >> > - CmdDragAndDropCommandActivator >> >> >> > >> >> >> > Activators are declared in command class side methods marked with >> >> >> > pragma #commandActivator. For example following method will allow >> >> >> > RenamePackageCommand to be executed by shortcut in possible system >> >> >> > browser: >> >> >> > RenamePackageCommand class>>packageBrowserShortcutActivator >> >> >> > <commandActivator> >> >> >> > ^CmdShortcutCommandActivator by: $r meta for: >> >> >> > PackageBrowserContext >> >> >> > And for context menu: >> >> >> > RenamePackageCommand class>>packageBrowserMenuActivator >> >> >> > <commandActivator> >> >> >> > ^CmdContextMenuCommandActivator byRootGroupItemFor: >> >> >> > PackageBrowserContext >> >> >> > Activators are always declared with application context where they >> >> >> > can >> >> >> > be applied (PackageBrowserContext in example). Application should >> >> >> > provide such contexts as subclasses of CmdToolContext with >> >> >> > information >> >> >> > about application state. Every widget can bring own context to >> >> >> > interact with application as separate tool. For example system >> >> >> > browser >> >> >> > shows multiple panes which provide package context, class context >> >> >> > and >> >> >> > method context. And depending on context browser shows different >> >> >> > menu >> >> >> > and provides different shortcuts >> >> >> > >> >> >> > keywords: command command pattern tools >> >> >> > >> >> >> > ## Community >> >> >> > Community is a project to add some world menues to easily access >> >> >> > some >> >> >> > community pages >> >> >> > >> >> >> > keywords: community pharo >> >> >> > >> >> >> > ## Complex >> >> >> > Math-Complex brings back to Pharo the complex numbers like (1+2i) >> >> >> > which used to be in Squeak Kernel. >> >> >> > >> >> >> > keywords: complex math number >> >> >> > >> >> >> > ## DacapoEnergyConsumption >> >> >> > This project run the Dacapo benchmarks, and monitor the energy >> >> >> > consumption of the CPU. It is for research purposes. >> >> >> > >> >> >> > keywords: consumption energy java >> >> >> > >> >> >> > ## DarkMetalTheme >> >> >> > An alternative to DarkTheme, DarkMetalTheme offers "metalic" >> >> tonalities >> >> >> > :) >> >> >> > >> >> >> > keywords: theme ui >> >> >> > >> >> >> > ## DebuggerCritiques >> >> >> > Add inlined critiques into Pharo debugger >> >> >> > >> >> >> > keywords: critiques debugger smallLint >> >> >> > >> >> >> > ## DesktopManager >> >> >> > A goodie to be able to manage multiple desktops in Pharo. >> >> >> > >> >> >> > keywords: desktop goodie pharo tools >> >> >> > >> >> >> > ## DiscordSt >> >> >> > DiscordSt is a library for Discord service, see >> >> https://discordapp.com >> >> >> > for basic information about Discord and >> >> >> > https://discordapp.com/developers/docs/intro for developer >> >> >> > information. >> >> >> > >> >> >> > The stable version supports Discord Webhooks. See >> >> >> > https://github.com/JurajKubelka/DiscordSt for examples. >> >> >> > >> >> >> > keywords: api chat client discord rest web webhook >> >> >> > >> >> >> > ## EventRecorder >> >> >> > Record and replay screen events. >> >> >> > >> >> >> > keywords: recording screen >> >> >> > >> >> >> > ## FamixDiff >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## FlatQA >> >> >> > Hi, I'm your personal quality assistant. I run Smalllint rules on >> >> >> > the >> >> >> > code that you modify, and notify you about quality changes. >> >> >> > https://github.com/Uko/QualityAssistant#qualityassistant >> >> >> > >> >> >> > keywords: automatic critics quality smallint validation >> >> >> > >> >> >> > ## FogBugz >> >> >> > Access to FogBugz from within Pharo environment. >> >> >> > >> >> >> > keywords: fun web >> >> >> > >> >> >> > ## Garage >> >> >> > Garage is the relational database driver for Pharo. Garage >> >> >> > provides >> >> >> > a >> >> >> > common API to connect with several database servers in a coherent >> >> >> > way >> >> >> > (JDBC like). Along with Garage, we provide implementations of >> >> >> > several >> >> >> > database drivers. >> >> >> > >> >> >> > keywords: api database drivers >> >> >> > >> >> >> > ## GarageGlorp >> >> >> > This configuration loads the Garage database drivers along with >> >> >> > the >> >> >> > Glorp Object-Relational Mapper. It is a convenience configuration >> >> >> > used >> >> >> > to load both projects using a single config. >> >> >> > >> >> >> > keywords: database driver orm persistence >> >> >> > >> >> >> > ## Gettext >> >> >> > Gettext is an implementaion of >> >> >> > https://www.gnu.org/software/gettext, >> >> >> > the standard l17n package. >> >> >> > >> >> >> > keywords: gettext i18n internationalization l10n localization >> >> >> > >> >> >> > ## Ghost >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## GitFileTree >> >> >> > GitFileTree is an integration of Git commands below Monticello, >> >> >> > allowing a very simple and powerfull integration with a git >> >> >> > repository >> >> >> > for tracking Monticello packages, allowing for example one to work >> >> >> > from github.com (including with configurations support) without >> >> >> > any >> >> >> > use of the command line and with perfect support of whatever is >> >> >> > the >> >> >> > structure of the project under git. >> >> >> > >> >> >> > Works with any possible organisation of the git repository related >> >> >> > to >> >> >> > the package (single language, multi language, single package, >> >> >> > multiple >> >> >> > packages, single remote repo, multiple remote repositories, >> >> >> > branches, >> >> >> > you name it). >> >> >> > >> >> >> > GitFileTree: is integrated into FileTree, but not easily >> >> >> > available. >> >> >> > This configuration allow for a one step loading with the >> >> >> > dependencies. >> >> >> > >> >> >> > keywords: FileTree Monticello OSProcess OSSubprocess Packages >> >> >> > Pharo5 >> >> >> > Pharo6 >> >> >> > git >> >> >> > >> >> >> > ## GitHubAPI >> >> >> > A GitHub API Wrapper for Pharo to easily access informations from >> >> >> > GitHub right from your Pharo image. >> >> >> > >> >> >> > keywords: api git github >> >> >> > >> >> >> > ## GitHubcello >> >> >> > Have it happened to you that you have your project on GitHub and >> >> >> > it >> >> >> > has a baseline but now you have to write down the Metacello script >> >> >> > to >> >> >> > load it? Not any more! Simply paste your repo URI into GTSpotter, >> >> >> > wait >> >> >> > a bit, select the baseline you want to load, and you're done! >> >> >> > https://github.com/Uko/GitHubcello#githubcello- >> >> >> > >> >> >> > keywords: github metacello spotter >> >> >> > >> >> >> > ## GlorpSQLite >> >> >> > GlorpSQLite is the integration of Glorp with SQLite. This >> >> >> > configuration loads UDBC, which contains SQLite, then loads Glorp. >> >> >> > Once GlorpSQLite is loaded, provided Pharo can find the SQLite >> >> >> > so/dylib/dll file on your system, start Test Runner and run the >> >> >> > tests. >> >> >> > >> >> >> > keywords: database orm persistence relational >> >> >> > >> >> >> > ## Grafoscopio >> >> >> > Grafoscopio is a tool to create interactive notebooks and >> >> >> > documentation for computer narratives and data visualization. >> >> >> > They are structured as outlines/trees containing textual and >> >> code >> >> >> > nodes that can be exported to several formats: LaTeX, HTML >> >> >> > and pdf (via pandoc). >> >> >> > It can be used in several endeavors like: reproductible open >> >> >> > research >> >> >> > and science, data journalism, data activism among others >> >> >> > >> >> >> > keywords: data-activism data-journalism data-science >> >> >> > data-visualization documentation interactive-notebook markdown >> >> >> > markup >> >> >> > open-data open-research open-science reproducible-research >> >> >> > >> >> >> > ## Grease >> >> >> > The Grease Portability Library >> >> >> > >> >> >> > keywords: framework portability >> >> >> > >> >> >> > ## Grid >> >> >> > This package provides a grid (2D array) implementation. >> >> >> > >> >> >> > keywords: 2D-array collection container matrix >> >> >> > >> >> >> > ## Hashids >> >> >> > Hashids allow you to create URL friendly ids from sequential >> >> >> > integer >> >> >> > ids. NB it is should not be considered as encryption but it does >> >> >> > provide a lightweight obfuscation of the underlying id. >> >> >> > https://github.com/alacap/hashids-pharo >> >> >> > >> >> >> > keywords: hashing >> >> >> > >> >> >> > ## Hubcap >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## INIFile >> >> >> > A Parser for .INI files (as usually used on Windows) >> >> >> > >> >> >> > keywords: configurations ini settings windows >> >> >> > >> >> >> > ## Iceberg >> >> >> > Iceberg is a set of tools that allow one to handle git >> >> >> > repositories >> >> >> > directly from a Pharo image. >> >> >> > >> >> >> > keywords: git vcs version control >> >> >> > >> >> >> > ## LightPhaser >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## MacroRecorder >> >> >> > MacroRecorder is a tool that allows the developer to >> >> >> > (i) record a sequence of transformations while they are >> >> >> > applied >> >> a >> >> >> > first time, either manually or with the assistance of refactoring >> >> >> > tools; >> >> >> > (ii) store and parameterize the transformations to allow >> >> >> > their >> >> >> > generalization; and >> >> >> > (iii) apply automatically the sequence of transformations >> >> >> > afterwards >> >> >> > on different code locations. >> >> >> > >> >> >> > For the last step, the developer could explicitly point to >> >> >> > the >> >> >> > entities to transform. >> >> >> > >> >> >> > keywords: code change code manipulation programming by >> >> >> > demonstration >> >> >> > source code transformations >> >> >> > >> >> >> > ## MatchTool >> >> >> > MatchTool is a simple UI for experimenting with the matching >> >> >> > functionality of pattern code. >> >> >> > MatchTool can be open from the World Menu > Tools category. More >> >> >> > information can be read from within the tool by pressing help >> >> >> > button. >> >> >> > >> >> >> > keywords: code inspect match pattern rewrite rules >> >> >> > >> >> >> > ## MessageFlowBrowser >> >> >> > A message flow browse to browser senders, implementors and >> >> >> > messages >> >> >> > of >> >> >> > methods in a single window and folow the message flow >> >> >> > >> >> >> > keywords: browser messageflow methods tools >> >> >> > >> >> >> > ## Mocketry >> >> >> > Mocketry is mock objects framework. It provides simplest way to >> >> >> > stub >> >> >> > any message to any object and to verify any occurred behaviour. >> >> >> > >> >> >> > mock := Mock new. >> >> >> > mock stub someMessage willReturn: 1000. >> >> >> > >> >> >> > mock someMessage should be: 1000. >> >> >> > mock should receive someMessage. >> >> >> > >> >> >> > rect := 0@0 corner: 2@3. >> >> >> > rect stub width willReturn: 1000. >> >> >> > >> >> >> > rect area should be: 3000 "area = width * height". >> >> >> > rect should receive width. >> >> >> > >> >> >> > keywords: BDD SUnit TDD framework mocks >> >> >> > >> >> >> > ## MooseProject >> >> >> > MooseProject is a library to store many differents versions for a >> >> >> > project. It will persist everything on the disk and allow you >> >> >> > easily >> >> >> > to recover the model associated to the desired version >> >> >> > >> >> >> > keywords: Moose project version >> >> >> > >> >> >> > ## Mustache >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## NPMJS >> >> >> > Spotter search of NPM packages >> >> >> > >> >> >> > keywords: javascript nodejs >> >> >> > >> >> >> > ## Neo4reSt >> >> >> > Neo4reSt is a rest client of Neo4j graph database. >> >> >> > (http://neo4j.org/ >> >> ) >> >> >> > >> >> >> > Neo4reSt will provide: >> >> >> > >> >> >> > - Raw rest client >> >> >> > - Wrapper client which handles JSON well >> >> >> > - Object level wrapper classes (Node, Relationship, Property) >> >> >> > >> >> >> > >> >> >> > keywords: Neo4j database graph persistence >> >> >> > >> >> >> > ## NeoCSV >> >> >> > CSV (Comma Separated Values) is a popular data-interchange format. >> >> >> > NeoCSV is an elegant and efficient standalone framework to read >> >> >> > and >> >> >> > write CSV converting to or from Smalltalk objects. >> >> >> > >> >> >> > keywords: ascii comma-separated-values csv fields format input >> >> >> > output >> >> >> > records rfc-4180 tab-separated-values tabular-data text tsv >> >> >> > >> >> >> > ## NeoJSON >> >> >> > JSON (JavaScript Object Notation) is a popular data-interchange >> >> >> > format. NeoJSON is an elegant and efficient standalone Smalltalk >> >> >> > framework to read and write JSON converting to or from Smalltalk >> >> >> > objects. >> >> >> > >> >> >> > keywords: encoding format input javascript json output >> >> >> > serialization >> >> >> > text >> >> >> > >> >> >> > ## Nginx >> >> >> > Utility project to work with nginx from Pharo image (Windows only >> >> >> > so >> >> >> > far) >> >> >> > >> >> >> > keywords: nginx server web windows >> >> >> > >> >> >> > ## OSLinuxCentOS >> >> >> > A part of the OS-XXX series to easier work with native operating >> >> >> > system platforms. Here for using CentOS Linux environments in >> >> >> > Pharo. >> >> >> > >> >> >> > keywords: centos linux native os unix >> >> >> > >> >> >> > ## OSLinuxUbuntu >> >> >> > A part of the OS-XXX series to easier work with native operating >> >> >> > system platforms. Here for using Ubuntu Linux environments in >> >> >> > Pharo. >> >> >> > >> >> >> > keywords: linux native os ubuntu unix >> >> >> > >> >> >> > ## OSOSX >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## OSProcess >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## OSRaspbian >> >> >> > A part of the OS-XXX series to easier work with native operating >> >> >> > system platforms. Here for using Raspbian environments in Pharo. >> >> >> > >> >> >> > keywords: linux native os raspbian unix >> >> >> > >> >> >> > ## OSUnix >> >> >> > A part of the OS-XXX series to easier work with native operating >> >> >> > system platforms. Here for using Unix environments in Pharo. >> >> >> > >> >> >> > keywords: native os unix >> >> >> > >> >> >> > ## OSWindows >> >> >> > API wrappers and tools for the Windows operating system >> >> >> > >> >> >> > keywords: api native win32 windows >> >> >> > >> >> >> > ## ObjectStatistics >> >> >> > ObjectStatistics is tool to analyse set of objects by computing >> >> >> > different kind of metrics and look at them from different angles. >> >> >> > Imaging that we have collection of message sends and we want to >> >> >> > know >> >> >> > number of message sends in dimension of receiver, receiver class >> >> >> > and >> >> >> > message selector. We have different angles to look at this data: >> >> >> > from >> >> >> > receiver class to selector and receiver or from selector to >> >> >> > receiver >> >> >> > class and receiver or any other combination. >> >> >> > We also could analyze different kind of metrics which could be >> >> >> > computed on given objects. It could be number of unique receivers, >> >> >> > execution time, executed lines of code, etc. >> >> >> > This package implements computation of object statistics over >> >> >> > declared >> >> >> > metrics and dimensions space. >> >> >> > Described example could be look like: >> >> >> > >> >> >> > stat := ObjectStatistics. >> >> >> > stat >> >> >> > countAllAs: 'sends'; >> >> >> > countDifferent: [ :message | message receiver ] as: >> >> >> > 'instances'. >> >> >> > stat >> >> >> > dimension: [ :message | message receiver class ] >> >> >> > named: >> >> >> > 'classes'; >> >> >> > with: [ >> >> >> > stat dimension: [ :message | message >> >> >> > selector >> >> >> > ] >> >> >> > named: 'msgs'; >> >> >> > with: [ >> >> >> > stat >> >> >> > dimension: [ :r | r ] named: >> >> >> > 'receivers'; >> >> >> > ignoreMetrics: >> >> >> > #('instances')]]; >> >> >> > dimension: [ :message | message selector ] named: >> >> 'msgs'; >> >> >> > with: [ >> >> >> > stat dimension: [ :message | message >> >> >> > receiver >> >> >> > class ] named: 'classes'; >> >> >> > with: [ >> >> >> > stat >> >> >> > dimension: [ :r | r ] named: >> >> >> > 'receivers']]. >> >> >> > >> >> >> > stat accumulateAll: messageSends. >> >> >> > >> >> >> > >> >> >> > >> >> >> > keywords: analysis framework >> >> >> > >> >> >> > ## ObjectTravel >> >> >> > ObjectTravel implements traversal of full object graph. It >> >> >> > enumerates >> >> >> > each reference in breadth-first direction and visit every >> >> >> > reference >> >> >> > only once. >> >> >> > >> >> >> > traveler := ObjectTraveler on: 10@30. >> >> >> > traveler moveToNextReference. "true". >> >> >> > traveler currentReference. "10" >> >> >> > traveler nextReference. "30" >> >> >> > >> >> >> > traveler := ObjectTraveler on: #(10 20 30). >> >> >> > traveler nextReference "10" >> >> >> > traveler nextReference "20" >> >> >> > >> >> >> > Also ObjectTravel can replace references with new values: >> >> >> > >> >> >> > traveler replaceCurrentReferenceWith: #newReference. >> >> >> > >> >> >> > >> >> >> > keywords: objectsTraversal stream tool >> >> >> > >> >> >> > ## Octopus >> >> >> > A pharo tool that utilises Pillar library to process pillar text >> >> >> > copied to the clipboard and convert it to HTML >> >> >> > >> >> >> > keywords: HTML markdown pillar >> >> >> > >> >> >> > ## OrderPreservingDictionary >> >> >> > This package has two ordered dictionary classes that behave like >> >> >> > OrderedDictionary and OrderedIdentityDictionary in Pharo but are >> >> >> > portable to Squeak and Gemstone, and other ordered dictionary >> >> >> > classes >> >> >> > needed by XMLParser. >> >> >> > >> >> >> > keywords: collection dictionary order-preserving ordered >> >> >> > >> >> >> > ## Orion >> >> >> > Orion is an interactive prototyping tool for reengineering, to >> >> >> > simulate changes and compare their impact on multiple versions of >> >> >> > software source code models. >> >> >> > >> >> >> > keywords: Moose delta model versioning >> >> >> > >> >> >> > ## Pastell >> >> >> > Pastell is an add-on for XMLParser which adds some methods that >> >> >> > make >> >> >> > navigation of an XML DOM tree much easier, it is a XMLPath-like >> >> >> > library. >> >> >> > >> >> >> > keywords: xml xpath >> >> >> > >> >> >> > ## PharoSprint >> >> >> > The Pharo community regularly organize Pharo Sprint events. The >> >> >> > Pharo >> >> >> > Sprint is a regular (monthly) event when developers and users meet >> >> >> > together to fix bugs. This usually takes place in a physical >> >> >> > location, >> >> >> > but people are welcomed to participate from any place. This is a >> >> >> > great >> >> >> > opportunity for novices to get involved and learn from experts! >> >> >> > >> >> >> > For more information: http://bit.ly/SprintWeb and >> >> >> > http://pharo.org/contribute-events >> >> >> > >> >> >> > keywords: Bug Discord FogBugz PharoSprint Sprint SprintDay >> >> >> > >> >> >> > ## Pillar >> >> >> > Pillar is a wiki-like syntax, its document model, a parser for it, >> >> >> > and >> >> >> > a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is >> >> >> > primarily used as the wiki syntax behind the *Pier >> >> >> > CMS>http://piercms.com*. Pillar is also being used to write books: >> >> >> > e.g., *the Enterprise Pharo book>http://books.pharo.org/*. >> >> >> > >> >> >> > keywords: book document html latex markdown pier wiki >> >> >> > >> >> >> > ## PlotMorph >> >> >> > PlotMorph is a nice plotting system. It can plot multiple series >> >> >> > with >> >> >> > different graphical attributes. >> >> >> > >> >> >> > keywords: Morph UI graph plotting point series >> >> >> > >> >> >> > ## PolyMath >> >> >> > Tools for scientific computation in Smalltalk >> >> >> > >> >> >> > keywords: ODE mathematics science >> >> >> > >> >> >> > ## Pomodoro >> >> >> > A pomodoro timer >> >> >> > >> >> >> > keywords: GTD morphic pomodoro >> >> >> > >> >> >> > ## PunQLite >> >> >> > UnQLite binding for Pharo Smalltalk. UnQLite is a fast, >> >> >> > lightweight, >> >> >> > portable, embedded KVS with a simple scripting engine (Jx9). By >> >> >> > using >> >> >> > PunQLite, you can store/load lots of data as if just using a >> >> >> > normal >> >> >> > Dictionary. >> >> >> > >> >> >> > PunQLite uses UnQLite shared library. If you have no time to >> >> >> > compile, >> >> >> > just get pre-built binary from the github project page >> >> >> > (https://github.com/mumez/PunQLite) >> >> >> > >> >> >> > >> >> >> > >> >> >> > keywords: KVS NoSQL UFFI UnQLite database persistence >> >> >> > >> >> >> > ## QualityAssistant >> >> >> > Hi, I'm your personal quality assistant. I run Smalllint rules on >> >> >> > the >> >> >> > code that you modify, and notify you about quality changes. >> >> >> > https://github.com/Uko/QualityAssistant#qualityassistant >> >> >> > >> >> >> > keywords: automatic critics quality smallint validation >> >> >> > >> >> >> > ## QuickAccess >> >> >> > A manager for scripts with Quick access. >> >> >> > >> >> >> > keywords: fun web >> >> >> > >> >> >> > ## RProjectConnector >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## RediStick >> >> >> > RediStick is a redis client which supports auto-reconnecting. >> >> >> > >> >> >> > Other features: >> >> >> > - Minimum dependencies (runs on Pharo without other libraries) >> >> >> > - Supports unicode strings >> >> >> > >> >> >> > >> >> >> > keywords: KVS NoSQL Redis database persistence >> >> >> > >> >> >> > ## ReferenceFinder >> >> >> > Finds reference paths between objects to help find memory leaks. >> >> >> > >> >> >> > keywords: memory objects references tracing >> >> >> > >> >> >> > ## RegexTools >> >> >> > A tool to test and verify regular expressions >> >> >> > >> >> >> > keywords: regex utilities >> >> >> > >> >> >> > ## Roassal2 >> >> >> > Roassal is an agile visualization engine. Roassal graphically >> >> >> > renders >> >> >> > objects using short and expressive Smalltalk expressions. A large >> >> >> > set >> >> >> > of interaction facilities are provided for a better user >> >> >> > experience. >> >> >> > Painting, brushing, interconnecting, zooming, drag and dropping >> >> >> > will >> >> >> > just make you more intimate with any arbitrary object model. >> >> >> > >> >> >> > keywords: charting data visualization >> >> >> > >> >> >> > ## SRT2VTT >> >> >> > This package convert SRT to VTT (subtitles for videos plugins) >> >> >> > >> >> >> > keywords: browser plugin srt videos vtt web >> >> >> > >> >> >> > ## ScriptManager >> >> >> > A simple tool to manage scripts. Still based on Morphic. We would >> >> >> > recommend users to switch to QuickAccess which is a better script >> >> >> > manager than this tool. >> >> >> > >> >> >> > keywords: fun script >> >> >> > >> >> >> > ## Seaside3 >> >> >> > The framework for developing sophisticated web applications in >> >> >> > Smalltalk. See http://www.seaside.st >> >> >> > >> >> >> > keywords: framework seaside web >> >> >> > >> >> >> > ## SimilarityFlooding >> >> >> > This project is an implementation of a FAMIX model difference >> >> >> > algorithm based on Similarity Flooding algorithm as defined by >> >> >> > Sergey >> >> >> > Melnik, Hector Garcia-Molina, and Erhard Rahm in 'Similarity >> >> >> > flooding: >> >> >> > A versatile graph matching algorithm and its application to schema >> >> >> > matching' and in the technical report associated. >> >> >> > Check the github repository for documentation >> >> >> > [https://github.com/juliendelplanque/SFDiff] >> >> >> > >> >> >> > keywords: FAMIX SFDiff difference model similarity similarity >> >> >> > flooding >> >> >> > >> >> >> > ## Spy2 >> >> >> > Spy2 is a profiling framework. You can easily create profilers. >> >> >> > You >> >> >> > can have a look at a description >> >> >> > http://bergel.eu/download/papers/Berg10f-Spy.pdf >> >> >> > >> >> >> > The Hapao test coverage tool is included. >> >> >> > >> >> >> > keywords: Hapao Memory Performance Profiling Roassal Spy >> >> >> > >> >> >> > ## Stamp >> >> >> > Stamp is an implementation of STOMP 1.2, a protocol to access >> >> >> > message >> >> >> > oriented middleware like RabbitMQ. >> >> >> > >> >> >> > keywords: client format messaging middleware queueing rabbitmq >> >> >> > stomp >> >> >> > >> >> >> > ## StateSpecs >> >> >> > StateSpecs is object state specification framework. It describes >> >> >> > particular object states by first class specifications. For >> >> >> > example >> >> >> > there are SpecOfCollectionItem, SpecOfObjectClass and >> >> >> > SpecOfObjectSuperclass. They can match and validate given objects. >> >> >> > In >> >> >> > case when object is not satisfied specification you will get >> >> >> > failure >> >> >> > result with detailed information about problem. >> >> >> > >> >> >> > spec matches: anObject. >> >> >> > spec validate: anObject. "it returns validation result which >> >> >> > can >> >> >> > be >> >> >> > success or particular failure" >> >> >> > >> >> >> > To easily create specifications and validate objects by them >> >> >> > StateSpecs provides two kind DSL: should expressions and "word" >> >> >> > classes. >> >> >> > First allows you to write "assertions": >> >> >> > >> >> >> > 1 should be: 2 >> >> >> > 1 should equal: 10 >> >> >> > >> >> >> > And second allows you to instantiate specs by natural readable >> >> >> > words: >> >> >> > >> >> >> > Kind of: Number >> >> >> > Instance of: String >> >> >> > Equal to: 'test' >> >> >> > >> >> >> > keywords: BDD SUnit TDD framework validation >> >> >> > >> >> >> > ## Ston >> >> >> > Smalltalk Object Notation (STON) is a lightweight, text-based, >> >> >> > human-readable data interchange format for class-based >> >> >> > object-oriented >> >> >> > languages like Smalltalk. It can be used to serialize domain level >> >> >> > objects, either for persistency or network transport. As its name >> >> >> > suggests, it is based on JSON (Javascript Object Notation). It >> >> >> > adds >> >> >> > symbols as a primitive value, class tags for object values and >> >> >> > references. >> >> >> > >> >> >> > keywords: encoding format input json output serialization ston >> >> >> > text >> >> >> > >> >> >> > ## SublimishTheme >> >> >> > >> >> >> > A dark theme for Pharo. If you like Sublime then you'll like >> >> >> > Sublimish >> >> >> > theme. >> >> >> > Project main page: * >> >> https://github.com/sebastianconcept/SublimishTheme* >> >> >> > >> >> >> > keywords: GUI IDE >> >> >> > >> >> >> > ## Tarantalk >> >> >> > Tarantalk is a Tarantool (Lua with DBMS) connector. >> >> >> > >> >> >> > You can: >> >> >> > - Store/load tuples. >> >> >> > - Find tuples by multiple indices >> >> >> > - Evaluate Lua programs >> >> >> > >> >> >> > >> >> >> > keywords: KVS Lua NoSQL Tarantool Tuple database persistence >> >> >> > >> >> >> > ## Tarantube >> >> >> > Tarantool message queue wrapper based on Tarantalk. >> >> >> > >> >> >> > - Supporting FIFO queue with priority, TTL, TTR, delay and sub >> >> >> > queues. >> >> >> > - Need to install Tarantool + Tarantool queue module >> >> >> > (https://github.com/tarantool/queue) >> >> >> > >> >> >> > >> >> >> > >> >> >> > keywords: Lua MQ NoSQL Tarantalk Tarantool queue >> >> >> > >> >> >> > ## Tealight >> >> >> > Tealight is a project defining a few extensions to the Teapot >> >> >> > framework to make the (tea) time you spend with the Pharo Teapot >> >> >> > system even easier.. >> >> >> > >> >> >> > keywords: api git github >> >> >> > >> >> >> > ## Teapot >> >> >> > Teapot is micro web framework on top of the Zinc HTTP components, >> >> >> > that >> >> >> > focuses on simplicity and ease of use. >> >> >> > >> >> >> > keywords: framework http micro sinatra web >> >> >> > >> >> >> > ## TestsUsageAnalyser >> >> >> > nil >> >> >> > >> >> >> > keywords: >> >> >> > >> >> >> > ## Trie >> >> >> > This package provides a trie implementation (as developed by >> >> >> > Benoit >> >> >> > St-Jean. See https://en.wikipedia.org/wiki/Trie >> >> >> > >> >> >> > keywords: collection containers retrieval trie >> >> >> > >> >> >> > ## Units >> >> >> > Units is a simple and powerful library to manage different units. >> >> >> > >> >> >> > keywords: Comparison Meter Points Units >> >> >> > >> >> >> > ## VMProfiler >> >> >> > VMProfiler is a sampling profiler tracking down where the time is >> >> >> > spent in the VM when executing a specific portion of code. It >> >> >> > computes >> >> >> > where the time is spent in the compiled C code of the VM, in the >> >> >> > VM >> >> >> > plugins and in the native functions. >> >> >> > The results are available as a statistical report. >> >> >> > >> >> >> > keywords: cog jit profiling virtual machine >> >> >> > >> >> >> > ## VerStix >> >> >> > A Vert.x TCP EventBus client for Pharo Smalltalk. >> >> >> > >> >> >> > You can: >> >> >> > - interact with various Vert.x components (Web, Auth, DB, MQ, >> >> >> > etc). >> >> >> > - interact with other Smalltalk images >> >> >> > - interact with various languages which support Vert.x EventBus >> >> >> > >> >> >> > >> >> >> > keywords: microservices network vertx >> >> >> > >> >> >> > ## VistaCursors >> >> >> > Provide a better looking cursor (similar to Windows Vista). >> >> >> > >> >> >> > keywords: cursor theming ui windows >> >> >> > >> >> >> > ## VoyageMongo >> >> >> > Voyage-Mongo is an object persistence layer made for easy the work >> >> >> > with *MongoDB>http://www.mongodb.org*. It is an "ODM" >> >> (Object-Document >> >> >> > Mapper), in the same spirit of the ORMs for relational approaches. >> >> >> > >> >> >> > keywords: database mongodb nosql persistence >> >> >> > >> >> >> > ## VoyageUnqlite >> >> >> > Voyage-UnQLite is an object persistence layer made for easy the >> >> >> > work >> >> >> > with *UnQLite>https://unqlite.org*. It is an "ODM" >> >> >> > (Object-Document >> >> >> > Mapper), in the same spirit of the ORMs for relational approaches. >> >> >> > >> >> >> > keywords: database nosql persistence unqlite >> >> >> > >> >> >> > ## WKHTML2PDF >> >> >> > Render HTML into PDF and various image formats using the >> >> >> > (external) >> >> >> > Qt >> >> >> > WebKit rendering engine directly from Pharo. >> >> >> > >> >> >> > keywords: html pdf reporting >> >> >> > >> >> >> > ## WebBrowser >> >> >> > General and platform independent WebBrowser access for Pharo 4.0 >> >> >> > onwards based on NativeBoost, for Pharo 5.0 onwards based on UFFI >> >> >> > >> >> >> > keywords: internet platform url utility web webbrowser >> >> >> > >> >> >> > ## XMI >> >> >> > A XMI wrapper for Pharo to easily access XML Metadata >> >> >> > informations. >> >> >> > >> >> >> > keywords: omg uml xmi xml >> >> >> > >> >> >> > ## XMLParser >> >> >> > XMLParser provides validating SAX and DOM parsers for well-formed >> >> >> > XML >> >> >> > documents on Pharo, Squeak, and Gemstone. It also provides a DOM >> >> >> > API >> >> >> > for manipulating documents, namespace support, and an optional >> >> >> > XMLWriter for writing documents. Validation and namespace checking >> >> >> > are >> >> >> > enabled by default, but not resolution of external entities. >> >> >> > >> >> >> > Implements: >> >> >> > http://www.w3.org/TR/REC-xml/ >> >> >> > http://www.w3.org/TR/REC-xml-names/ >> >> >> > http://www.w3.org/TR/xml-id/ >> >> >> > http://www.w3.org/TR/xmlbase/ >> >> >> > https://www.w3.org/TR/xml-c14n >> >> >> > >> >> >> > >> >> >> > keywords: DOM DTD HTML SAX XHTML XML document markup parser >> >> >> > validation >> >> >> > web >> >> >> > >> >> >> > ## XMLParserHTML >> >> >> > XMLParserHTML provides SAX and DOM parsers for HTML that convert >> >> >> > possibly malformed HTML into well-formed XML. >> >> >> > >> >> >> > keywords: DOM HTML SAX document markup parser web >> >> >> > >> >> >> > ## XMLParserStAX >> >> >> > XMLParserStAX is a pull parser for XMLParser that provides a >> >> >> > streaming >> >> >> > interface for "pulling" XML events and also supports pull-style >> >> >> > DOM >> >> >> > parsing for dynamically converting events into DOM nodes. >> >> >> > >> >> >> > keywords: DOM DTD HTML StAX XHTML XML XMLPullParser document >> >> >> > markup >> >> >> > parser pull pull-parser validation web >> >> >> > >> >> >> > ## XMLWriter >> >> >> > XMLWriter allows you to generate well-formed XML documents using >> >> >> > an >> >> >> > API based on Seaside's canvas and tag brushes so all tags will be >> >> >> > nested properly and not left unclosed. >> >> >> > >> >> >> > keywords: HTML XHTML XML document markup web writer >> >> >> > >> >> >> > ## XPath >> >> >> > An XPath library for Pharo, Squeak, and Gemstone leveraging the >> >> >> > XML >> >> >> > parsing capabilities of XMLParser. Supports XPath 1.0 syntax with >> >> >> > extensions. >> >> >> > >> >> >> > keywords: DOM HTML XHTML XML XPath document markup parser query >> >> >> > web >> >> >> > >> >> >> > ## ZTimestamp >> >> >> > The ZTimestamp project groups a number of classes that form an >> >> >> > addition/alternative to DateAndTime/Timestamp. The core ZTimestamp >> >> >> > class represents a point in time, with second precision and always >> >> >> > in >> >> >> > the UTC/GTM/Zulu timezone. It is faster and smaller. >> >> >> > ZTimestampFormat >> >> >> > is a formatter and parser that is example based. ZTimezone uses >> >> >> > the >> >> >> > standard Olsone timezone database to compute the offset for local >> >> >> > time >> >> >> > at specific points in time for a specified timezone. >> >> >> > ZTimestampSNTPClient is an SNTP client to check the local clock >> >> >> > against network time servers. This project is small and has no >> >> >> > further >> >> >> > dependencies. It runs in Pharo 2 and 3. >> >> >> > >> >> >> > keywords: chronology date formatting parsing sntp time timestamp >> >> >> > timezone >> >> >> > >> >> >> > ## ZincHTTPComponents >> >> >> > Zinc HTTP Components is an open source Smalltalk framework to deal >> >> >> > with HTTP. It models most concepts of HTTP and its related >> >> >> > standards >> >> >> > and offers both client and server functionality. One of its key >> >> >> > goals >> >> >> > is to offer understandability (Smalltalkâs design principle number >> >> >> > one). Anyone with a basic understanding of Smalltalk and the HTTP >> >> >> > principles should be able to understand what is going on and >> >> >> > learn, >> >> >> > by >> >> >> > looking at the implementation. >> >> >> > >> >> >> > keywords: character-encoding client http internet mime-type >> >> >> > networking >> >> >> > request response server url >> >> >> > >> >> >> > # Pharo 6 catalog list - description is missing >> >> >> > - CommandShell >> >> >> > - FamixDiff >> >> >> > - Ghost >> >> >> > - Hubcap >> >> >> > - LightPhaser >> >> >> > - Mustache >> >> >> > - OSOSX >> >> >> > - OSProcess >> >> >> > - RProjectConnector >> >> >> > - TestsUsageAnalyser >> >> >> > >> >> >> > >> >> >> > On 8/21/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> >> >> This code snippet below gives a list of all Pharo 6.0 catalog >> >> >> >> entries >> >> >> >> >> >> >> >> >> >> >> >> CatalogProvider default retrieveProjects select: [ :x | >> >> >> >> (x at: 'repositoryUrl') = >> >> >> >> 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main' ]. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On 8/21/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> >> >> >>> absolutely , I will add Torsten's wonderful wiki and Grafoscopio >> >> >> >>> details, >> >> >> >>> keep them coming :) >> >> >> >>> >> >> >> >>> Anything I miss, please alert me as Hizrel just did , I want to >> >> >> >>> link >> >> >> >>> to >> >> >> >>> anything Pharo related ,lets bring everything under one roof ;) >> >> >> >>> >> >> >> >>> On Mon, Aug 21, 2017 at 9:15 AM H. Hirzel >> >> >> >>> <hannes.hirzel(a)gmail.com> >> >> >> >>> wrote: >> >> >> >>> >> >> >> >>>> And add the overview to Grafoscopio >> >> >> >>>> >> >> >> >>>> Aug 20, 2017 >> >> >> >>>> [Pharo-users] [Ann] [Grafoscopio] New release with major >> >> improvements >> >> >> >>>> >> >> >> >>>> On 8/21/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> >> >>>> > On 8/20/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> >> >> >>>> > ...... >> >> >> >>>> >> >> >> >> >>>> >> you make any submission you want here in this thread and I >> >> >> >>>> >> will >> >> >> >>>> >> port >> >> >> >>>> >> it >> >> >> >>>> >> to >> >> >> >>>> >> wiki with copy paste and a bit of structuring :) >> >> >> >>>> >> >> >> >> >>>> > Dimitris, >> >> >> >>>> > >> >> >> >>>> > Could you please do add a link in >> >> >> >>>> > https://github.com/SquareBracketAssociates/PharoWiki >> >> >> >>>> > >> >> >> >>>> > to Torsten's wiki >> >> >> >>>> > >> >> >> >>>> > http://wiki.astares.com/pharo >> >> >> >>>> > >> >> >> >>>> > It has over 500 pages with good content I was not aware >> >> >> >>>> > of.... >> >> >> >>>> > >> >> >> >>>> > >> >> >> >>>> > Thanks, >> >> >> >>>> > Hannes >> >> >> >>>> > >> >> >> >>>> >> >> >> >>>> >> >> >> >>> >> >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >

Aug. 24, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by Stephane Ducasse

In Pharo 60 (and not in Pharo 50) I extracted the command line logic into a specific object so that we do not have to be bound to use the command line. You can have a look in the CLI package. This is good that there is Section 7 this in the doc. We started to build a simple Morphic renderer for Pillar. We should continue. If someone wants to have fun. This would be nice to have see it coming to live. On my todo: I also want to use mustache inside Pharo and not generating files on the disk. Stef On Fri, Aug 18, 2017 at 10:08 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Exactly. > > Section 7 of > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > has an example > > > | wiki | > wiki := '!My Document'. > PRPillarParser parse: wiki > > > Or > > PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') > readStream > > > and then > > > PRHTMLWriter write: document > > > This put together gives > > PRHTMLWriter write: ( > PRPillarParser parse: (FileSystem workingDirectory / 'welcome.pillar') > ) > > > If I inspect the result of this expression I get the HTML string. > > Thank you Cyril. This is what I was looking for. > > --Hannes > > > > > On 8/18/17, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> On ven. 18 aoÃ»t 2017 at 21:43, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >>> Thank you Cyril for the link to the tutorial. >>> >>> >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> I see that Pillar is a command line tool. The welcome example taken >>> from this tutorial is: >>> >>> Pharo.exe Pillar.image pillar export --to=html >>> --outputFile=welcome welcome.pillar >>> >>> How can I run a command like this from within Pharo in a "playground" >>> (former workspace)? >>> >>> Later on I plan to construct a simple GUI with text boxes for Pillar >>> sources and have some buttons executing these commands. >>> >>> --Hannes >>> >>> >> >> I remember writing a part "Pillar from Pharo" in this doc. I'm not sure it >> is still up to date but you can try to check part 7 of the doc I sent. >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> >

Aug. 24, 2017