February 2017 - Pharo-users

Loading Seaside via Bootstrap in Pharo 6

by Torsten Bergmann

Hi, regarding the problem Sven mentioned on http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2017-February/… here are my findings: When I use latest Pharo 6 (Image 60404) and run Metacello new smalltalkhubUser: 'Seaside' project: 'MetacelloConfigurations'; configuration: 'Seaside3'; version: #'release3.2'; load it loads the latest release 3.2 (which internally loads 3.2.1). The package is "ConfigurationOfSeaside3-JohanBrichau.323.mcz" This loads fine in Pharo 6 except that after installation the "Tools" -> "Seaside control panel" is not working anymore as "NewListModel" is not found anymore. So the control panel is broken. Dont know what the migration path is for UI's who used the removed "NewListModel" class. So yes - one can (by using the above script) use Seaside but currently has to start the server with a script until this is fixed. This is good to know - but does not solve the "loading from catalog" issue. ----------------------------------------------------------------------------------------------------------------------------------------- So (in a fresh image 60404) I loaded "Bootstrap" from catalog and I received the error Sven reported. But ConfigurationOfBootstrap itself is not the problem I guess. Because it is also only referencing the "release3.2" version of Seaside and also "ConfigurationOfSeaside3-JohanBrichau.323.mcz" is loaded. The Transcript shows the following error output: Loaded -> ConfigurationOfSeaside3-JohanBrichau.323 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/Error: Name not found: Seaside-Pharo-Development Also when you try to open the ConfigurationOfSeaside3 using Versionner I receiver an error "Name not found: Seaside-Pharo-Development". So there must be something wrong with the Seaside config I thought - or (what would be worse) with the newer Metacello version included in Pharo 6. At least the config looks OK and in both situations "ConfigurationOfSeaside3-JohanBrichau.323" is used. Additionally I tried: - when I load the Bootstrap config in a fresh Pharo 5.0 image (50769) from Catalog all loads fine. - when I manipulate the Pharo 6 image to have a version 5 signature SystemVersion newVersion: 'Pharo5.0'. SystemVersion current inspect. and load from catalog afterwards it also does not work. So I guess a Pharo 5.x specific config rule could not be the cause. Now I checked how Catalog loads the configs. And in class CatalogProject you will notice that for the catalog we still use Gofer for loading installStableVersion Gofer it url: self repositoryUrl; configurationOf: self name; loadStable when I change it to Metacello API installStableVersion Metacello new repository: self repositoryUrl, '/',self name; configuration: self name; version: #'stable'; load what a surprise: anything loads fine. I still wonder and do not know about the difference why Gofer and Metacello loading in Pharo 6 makes a difference now. So we could fix it for the catalog ... still I have no glue about the Gofer/Metacello API difference ... https://pharo.fogbugz.com/f/cases/19736/Catalog-should-use-Metacello-API-in… Thanks T.

Feb. 21, 2017

Re: [Pharo-users] Data Encryption

by Mariano Martinez Peck

As for single username/pass encryption (not the whole DB), and assuming you want two-way encrypt (that you want to decrypt), I have used both, Rijndael and Blowfish, both in combination with SpsSplitPasswordStore. Cheers, On Tue, Feb 21, 2017 at 8:20 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > On Mon, Feb 20, 2017 at 05:34:41AM -0800, sergio ruiz wrote: > > I have been tasked with throwing together a small web app that will hold > > the passwords to different projects for my company. > > Here is a collection for reference. If one of these is suitable you can > skip the > implementation and just deploy. > > http://opensourcepasswordmanager.com/ > > > - encrypt the entire database, so that if the machine was compromised > > physically, the data would be useless. > > The NativeBoost version of my SQLite library supports SQLcipher which adds > transparent full database encryption to SQLite. It is not in the UFFI > version > yet though. > > http://sqlcipher.net > > > - encrypt the username and password fields to facilitate the above, also. > > If you are already familiar with using crypto API like OpenSSL or NaCl then > Pharo's FFI is easy to get this done too. > > Pierce > > > -- Mariano http://marianopeck.wordpress.com

Feb. 21, 2017

Re: [Pharo-users] Data Encryption

by Pierce Ng

On Mon, Feb 20, 2017 at 05:34:41AM -0800, sergio ruiz wrote: > I have been tasked with throwing together a small web app that will hold > the passwords to different projects for my company. Here is a collection for reference. If one of these is suitable you can skip the implementation and just deploy. http://opensourcepasswordmanager.com/ > - encrypt the entire database, so that if the machine was compromised > physically, the data would be useless. The NativeBoost version of my SQLite library supports SQLcipher which adds transparent full database encryption to SQLite. It is not in the UFFI version yet though. http://sqlcipher.net > - encrypt the username and password fields to facilitate the above, also. If you are already familiar with using crypto API like OpenSSL or NaCl then Pharo's FFI is easy to get this done too. Pierce

Feb. 21, 2017

Re: [Pharo-users] Loading Seaside via Bootstrap in Pharo 6

by Sven Van Caekenberghe

Hi Johan, I depend on Bootstrap from my Config's baseline: project: 'Bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; versionString: #stable ]; Which depends on Seaside in its baseline: spec project: 'Seaside3' with: [ spec className: 'ConfigurationOfSeaside3'; versionString: #'stable'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ]. This used to work (but in Pharo 4). > On 20 Feb 2017, at 20:37, Johan Brichau <johan(a)inceptive.be> wrote: > > Hi Sven, > > I have (not yet) tried Pharo6, but I saw some people did update the configuration for that. > How are you loading the project? Are you using the Metacello load API ? > > Johan > >> On 20 Feb 2017, at 19:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> In my main project I depend on Torsten's Bootstrap project which then loads Seaside. I tried this today on Pharo 6 and it did not work (some internal Seaside dependency could not be resolved). I also noticed that the last commits on Bootstrap were from April 2016. >> >> My question now is: is this supposed to work on Pharo 6 ? >> >> Thx, >> >> Sven > >

Feb. 20, 2017

Re: [Pharo-users] Loading Seaside via Bootstrap in Pharo 6

by Johan Brichau

Hi Sven, I have (not yet) tried Pharo6, but I saw some people did update the configuration for that. How are you loading the project? Are you using the Metacello load API ? Johan > On 20 Feb 2017, at 19:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > In my main project I depend on Torsten's Bootstrap project which then loads Seaside. I tried this today on Pharo 6 and it did not work (some internal Seaside dependency could not be resolved). I also noticed that the last commits on Bootstrap were from April 2016. > > My question now is: is this supposed to work on Pharo 6 ? > > Thx, > > Sven

Feb. 20, 2017

Re: [Pharo-users] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

by Jigyasa Grover

Many thanks for your valuable vote Hayatou :) - Jigyasa -- View this message in context: http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-I… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 20, 2017

Loading Seaside via Bootstrap in Pharo 6

by Sven Van Caekenberghe

Hi, In my main project I depend on Torsten's Bootstrap project which then loads Seaside. I tried this today on Pharo 6 and it did not work (some internal Seaside dependency could not be resolved). I also noticed that the last commits on Bootstrap were from April 2016. My question now is: is this supposed to work on Pharo 6 ? Thx, Sven

Feb. 20, 2017

Voyage: Unique vs Multiple repo

by Hilaire

Hi, I have three questions regarding these two options. As a matter of analogy to what I know, for me a Voyage repo is like a database and collections like tables in relational db world. So what is the argument to use multiple repo for an application domain? When using two repo A and B, is it ok to have instances saved in A with attributes saved in B? When fetching instances from A, will these instances get their attributes saved in B right? Thanks Hilaire -- Dr. Geo http://drgeo.eu

Feb. 20, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

Dale, I try out the lock feature on an archived image, the seaside uprade was still operating :( I updated this image with latest Metacello, then I locked it as: Metacello image configuration: 'Seaside3'; version: '3.1.4.2'; "most recent 3.1.x version" lock. It was the version returned by this command: ConfigurationOfSeaside3 new project currentVersion By the way it will make sense, and will be easily discoverable to have a short cut as "ConfigurationOfSeaside3 currentVersion" I don't remember how I installeed Seaside in the first place, I think it was from the configuration browser. Hilaire Le 19/02/2017 Ã 18:50, Dale Henrichs a Ã©crit : > I mentioned last night that I thought that there was a better solution > to your problem and I think that if you load the latest Metacello and > then lock Seaside3: > > Metacello image > configuration: 'Seaside3'; > version: '3.1.5'; "most recent 3.1.x version" > lock. > > Then load Voyage, you shouldn't have the problem with Seaside being > updated to 3.2. Seaside does not support upgrade across minor version > numbers like 3.1 to 3.2 ... if the upgrade to 3.2 was allowed, you > wouldn't have this particular problem. -- Dr. Geo http://drgeo.eu

Feb. 20, 2017

Re: [Pharo-users] Coding XPath as Smalltalk

by monty

An improved ?? construct is part of the public API now. It can be used to attach predicates to node tests: xmlNode / 'foo' / ('bar' ?? 10). or to filter result node sets like this: (xmlNode / 'foo' / 'bar') ?? 10. xmlNode / 'foo' / 'bar' ?? 10. "same because of precedence" The first is equivalent to this: 'foo/bar[10]' asXPath in: xmlNode. The others are equivalent to this: '(foo/bar)[10]' asXPath in: xmlNode. Block predicates take the context node, position, and size as optional (cull:) arguments. Multiple predicates are done by giving ?? an Array argument or chaining ?? sends like this: xmlNode / 'foo' / ('bar' ?? [:each | each includesAttribute: 'name'] ?? 1). Number predicates are faster than blocks and an initial number predicate attached to a node test (like in the first example) optimizes the node test by limiting the number of matching nodes it enumerates. > Sent: Saturday, September 03, 2016 at 11:08 AM > From: PBKResearch <peter(a)pbkresearch.co.uk> > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > Hi Monty > > Just to say that I have obtained the Moose 6.0 image (Pharo5.0 Latest update: #50761) and installed the XMLHTMLParser, and I seem able to reproduce the nucleus of the results I had from my old image. Some of my old XPath strings do not work (e.g. it did not recognise [1]), but I have worked my way round that, and I should soon have worked out the new syntax. Thanks for your suggestions for the variable case; I can now see the way ahead for that. Thanks for all the help. > > @stef > > I have loaded the same version of TextLint as I had in the previous image. It was accepted with no problems. I have tested it for the limited uses I make of it (just the parsers, not the rules) and everything seems OK. So now I am upgraded to Pharo 5, so far with no problems! > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty > Sent: 03 September 2016 13:00 > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > > > > Sent: Saturday, September 03, 2016 at 5:30 AM > > From: PBKResearch <peter(a)pbkresearch.co.uk> > > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > > > Hi Monty > > > > Many thanks. I have picked up a project that I had not worked on for a while, which explains why I am using an old image. I shall try the latest Moose image, as you suggest. My only anxiety is that I need to be able to use a rather ancient package called TextLint, and I do not know whether it will load OK in a new Pharo. If not, I shall try to update my existing image. > > If you'd looked at CI job, you'd see that XPath builds on Pharo 5 through 3 (but should work back to 1.4). You can always start fresh with a clean, old image from http://files.pharo.org/image/ or the Moose website if TextLint doesn't work anymore. > > > With the latest XPath, will it be clear how to use the binary syntax to carry out node tests like the example of '//div[@id=''catlinks'']//' that I cited below? The case I am interested in is where the actual identifier ('catlinks' in this case) is a variable rather than a constant. It would be possible to do it in standard XPath by assembling the XPath string with a variable component, but it might be more convenient in the binary syntax. > > > > You could do this: > ((doc // 'div') select: [:each | (each attributeAt: 'id') = catlinks]) // 'li' // 'text()' > > where "catlinks" is a var. Or you could use xPath:context: with an XPath var that you dynamically bind using custom contexts: > doc > xPath: '//div[@id=$catlinks]//li//text()' > context: (XPathContext variables: {'catlinks' -> catlinks}) > > The advantage over this: > doc xPath: '//div[@id=''', catlinks, ''']//li//text()' > > is that the xPath: expression string is the same each time, so it's only compiled once, the first time, and cached for later uses (inspect 'XPath compiledXPathCache') instead of being compiled each time the xPath: expression string arg changes. > > > Many thanks for your help. > > > > Peter Kenny > > > > -----Original Message----- > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty > > Sent: 03 September 2016 06:54 > > To: pharo-users(a)lists.pharo.org > > Subject: Re: [Pharo-users] Coding XPath as Smalltalk > > > > Peter, you're using an ancient version with bugs that were fixed last fall. The newest version has more tests and correct behavior (checked against a reference implementation). Just download a new Moose image and you'll get it, along with an up to date XMLParser. (But if you insist on upgrading in your old image, run "XPath initialize" after) > > > > The binary syntax (there are keyword equivalents now) officially only supports XPath axis selectors like #/ and #// that take node test arguments where the node tests can be name tests like 'name,' '*', 'prefix:*' or type tests like 'text()', 'comment()', 'element(name)'. > > > > Filters aren't officially supported with that syntax, but you can always use select: on the result. ?? was removed, but I might add it back as shorthand. Filters are implemented differently now. > > > > > From: PBKResearch <peter(a)pbkresearch.co.uk> > > > To: pharo-users(a)lists.pharo.org > > > Subject: [Pharo-users] Coding XPath as Smalltalk > > > > > > Hello > > > > > > I am using XPath as a way of dissecting web pages, especially from Wiktionary. Generally I get good results, but I could get useful extra flexibility by using the binary Smalltalk operators to represent XPath, as mentioned at the end of the class comment for XPath. However, the description there is very terse, and I am having difficulty seeing how to include more complex expressions, especially attribute tests. I have put some of my XPath expressions through the XPath compiler and looked at the output, and out of that I have found expressions which work but look very clumsy. As an example, I have used the fragment: > > > > > > document xPath: '//div[@id=''catlinks'']//li//text()' > > > > > > and found that an equivalent is: > > > > > > document //'div' ?? [:node :x :y|(node attributeAt: 'id') = 'catlinks']//'li'//[:n| n isStringNode]]. > > > (I had to put two dummy arguments in the three-argument block to get it to work.) > > > > > > Is there a more extensive explanation of the use of these binary operators? If not, could some kind person show me the most concise translation of the sample XPath above, to give me a start in working out more complex cases? > > > > > > Many thanks for any help. > > > > > > Peter Kenny > > > > > > > > >

Feb. 20, 2017