February 2017 - Pharo-users

Re: [Pharo-users] Data Encryption

by sergio ruiz

Now that i think about it.. this will contain a list of passwords for servers, etc.. each user will need to access about a dozen company passwords.. trying to thing about how to keep this buttoned down.. On February 22, 2017 at 9:19:05 AM, Alexandre Bergel (alexandre.bergel(a)me.com) wrote: If it help Iâm using NaCl to do secure the passwords. You should not store the passwords of your users, not even encrypted. ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 23, 2017

Re: [Pharo-users] Voyage: Unique vs Multiple repo

by Hilaire

Thanks Esteban for your detailed answer. Le 23/02/2017 Ã 13:23, Esteban Lorenzano a Ã©crit : > Voyage will not handle that kind of problem. Voyage will not know anything about instance A being saved in repo1 AND repo2. > Also, I do not think it should :) Thanks to clarify, it helps to understand Voyage's boundaries. > - if one object can be on repo1 and repo2, then probably you need to join those repositories This put me back at my initial questioning: is there any reason to have several repositories for one application domain? > - if that duplicated value is an enum type (like enum objects), then you do not want to persist that: what you do is to persist a reference, then on materialisation you refer to your enum (I do that a lot, in some apps)\ > - if you want to have for example, your list of organisations in one repository and then one repository for each organisation, you can still apply same pattern as before, but instead enums you persist a reference to your organisation and then on materialisation you can repoint to it. Indeed, I was thinking about storing reference. Thanks Hilaire -- Dr. Geo http://drgeo.eu

Feb. 23, 2017

Re: [Pharo-users] Voyage: Unique vs Multiple repo

by Esteban Lorenzano

Hi Hilaire, Voyage will not handle that kind of problem. Voyage will not know anything about instance A being saved in repo1 AND repo2. Also, I do not think it should :) I think you have a design problem if you want something like that to workâ¦ letâs explore the consequence of implementing something that would automatise that: - you could have a âmeta-cacheâ in the image with the objects in all repos, then on save you first check if is there and to which repository it belongs - but that will not solve the problem, because object could be in repoX but not at the moment in the image, so you need to go to the repository to verify if is already there - and that, for each repository you will want to handle. So, how to handle this? Not to having the problem :) - if one object can be on repo1 and repo2, then probably you need to join those repositories - if that duplicated value is an enum type (like enum objects), then you do not want to persist that: what you do is to persist a reference, then on materialisation you refer to your enum (I do that a lot, in some apps)\ - if you want to have for example, your list of organisations in one repository and then one repository for each organisation, you can still apply same pattern as before, but instead enums you persist a reference to your organisation and then on materialisation you can repoint to it. For example, this lates approach would be defined something like this: We have objects Organisation, User (with organisation as attribute). in repo1 you want to keep all organisations in repo2 you want all users then you do something like this: User class>>mongoOrganisation <voyageDescription> ^ VOToOneDescription new attributeName: âorganisationâ; accessor: (MAPluggableAccessor read: [ :user | repo1 keyOf: user organisation ] write: [ :user :value | user organisation: (repo1 selectOne: Organisation where: { â_idâ -> value } asDictionary ) ] ); yourself Something like that. Esteban > On 22 Feb 2017, at 19:57, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > It looks like Voyage will duplicate in repo A the instance saved in repo > B in the first place. These two instances of an identical object will > have different ID. > > The following script shows this behaviour: > > | orga repo1 repo2| > repo1 := VOMongoRepository host: 'localhost' database: 'test1'. > repo2 := VOMongoRepository host: 'localhost' database: 'test2'. > orga := 'Pharo' -> 13. > repo1 save: orga. > repo2 save: ('Hilaire' -> orga). > > repo2 selectAll: Association. > > => an OrderedCollection('Hilaire'->'Pharo'->13 'Pharo'->13) > > How do you guys avoid such duplication of identical instances in two > different repo? > > Let's say you want to have in one repository a collection of reference > data, but these data are used by other instanced saved in another repo. > Then from time to time this data may need to be edited, copy of these > data will then be obsolete. > > Thanks > > Hilaire > > > Le 20/02/2017 Ã 19:26, Hilaire a Ã©crit : >> 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? > > -- > Dr. Geo > http://drgeo.eu > >

Feb. 23, 2017

Re: [Pharo-users] Crash in Athens

by Alexander Samoylovich

Hello. I can reproduce the bug "semi-automatically". The tree classes I use to crash are attached. Run AthensFlyingStickMorph new openInWorld and wait. Sometimes it crashes immediately. Sometimes I have to wait a couple of minutes. If I done not resize the crash never or almost never happens. Thank you, Alex On Wed, Feb 22, 2017 at 11:56 AM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Hello, > > http://forum.world.st/Too-frequent-crashes-td4927143i20.html#a4934027 > > Try changing AthensCairoSurface >> asForm into the following method: > > asForm > > "create a form and copy an image data there" > | form | > self checkSession. > > self flush. > form := Form extent: (self width@self height) depth: 32. > form unhibernate. > LibC memCopy: self getDataPtr to: form bits size: self width*self > height*4. > ^ form > > This seems to improve the stability a lot. I have already told Esteban to > take a better look. > > Best regards, > Ronie > > 2017-02-22 13:47 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > >> Dear Alexander, >> >> Sine the new FFI of Pharo, using Athens has become unreliable. This is a >> pity, but fixing this is not trivial at all (we have been trying for years). >> >> What exactly are you doing with Athens? >> >> Alexandre >> >> >> > On Feb 22, 2017, at 12:55 AM, Alexander Samoylovich < >> samoylovich(a)gmail.com> wrote: >> > >> > Hello >> > >> > I am writing graphic demo programs using Athens on Mac Sierra. >> > Time by time Pharo VM crashes. Programs not using Athens work reliably. >> > I believe the behavior is reproducible. >> > How should I report a bug? >> > >> > Alex >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >

Feb. 23, 2017

Re: [Pharo-users] Data Encryption

by sergio ruiz

Hi, Alejandro.. yes, they are looking to encrypt the entire database.. youâre right, i think securing the OS and running over SSL is sufficient.. BUT.. i do appreciate you writeup on NaCl.. I am DEFINITELY using this on my next project.. Thanks! On February 22, 2017 at 9:19:05 AM, Alexandre Bergel (alexandre.bergel(a)me.com) wrote: Hi! If it help Iâm using NaCl to do secure the passwords. You should not store the passwords of your users, not even encrypted. ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 22, 2017

Re: [Pharo-users] Voyage: Unique vs Multiple repo

by Hilaire

Hi, It looks like Voyage will duplicate in repo A the instance saved in repo B in the first place. These two instances of an identical object will have different ID. The following script shows this behaviour: | orga repo1 repo2| repo1 := VOMongoRepository host: 'localhost' database: 'test1'. repo2 := VOMongoRepository host: 'localhost' database: 'test2'. orga := 'Pharo' -> 13. repo1 save: orga. repo2 save: ('Hilaire' -> orga). repo2 selectAll: Association. => an OrderedCollection('Hilaire'->'Pharo'->13 'Pharo'->13) How do you guys avoid such duplication of identical instances in two different repo? Let's say you want to have in one repository a collection of reference data, but these data are used by other instanced saved in another repo. Then from time to time this data may need to be edited, copy of these data will then be obsolete. Thanks Hilaire Le 20/02/2017 Ã 19:26, Hilaire a Ã©crit : > 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? -- Dr. Geo http://drgeo.eu

Feb. 22, 2017

Re: [Pharo-users] Data Encryption

by sergio ruiz

OH!Â Sorry.. they donât want to do the crypto stuff on our own.. just the CRUD stuff of managing the passwords.. but those were some really good links! On February 22, 2017 at 9:19:05 AM, Alexandre Bergel (alexandre.bergel(a)me.com) wrote: are they aware of Schneier's Law... *Â https://www.schneier.com/blog/archives/2011/04/schneiers_law.html *Â https://www.schneier.com/essays/archives/1999/03/cryptography_the_imp.html ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 22, 2017

Re: [Pharo-users] Crash in Athens

by Ronie Salgado

Hello, http://forum.world.st/Too-frequent-crashes-td4927143i20.html#a4934027 Try changing AthensCairoSurface >> asForm into the following method: asForm "create a form and copy an image data there" | form | self checkSession. self flush. form := Form extent: (self width@self height) depth: 32. form unhibernate. LibC memCopy: self getDataPtr to: form bits size: self width*self height*4. ^ form This seems to improve the stability a lot. I have already told Esteban to take a better look. Best regards, Ronie 2017-02-22 13:47 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Dear Alexander, > > Sine the new FFI of Pharo, using Athens has become unreliable. This is a > pity, but fixing this is not trivial at all (we have been trying for years). > > What exactly are you doing with Athens? > > Alexandre > > > > On Feb 22, 2017, at 12:55 AM, Alexander Samoylovich < > samoylovich(a)gmail.com> wrote: > > > > Hello > > > > I am writing graphic demo programs using Athens on Mac Sierra. > > Time by time Pharo VM crashes. Programs not using Athens work reliably. > > I believe the behavior is reproducible. > > How should I report a bug? > > > > Alex > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Feb. 22, 2017

Re: [Pharo-users] Crash in Athens

by Alexandre Bergel

Dear Alexander, Sine the new FFI of Pharo, using Athens has become unreliable. This is a pity, but fixing this is not trivial at all (we have been trying for years). What exactly are you doing with Athens? Alexandre > On Feb 22, 2017, at 12:55 AM, Alexander Samoylovich <samoylovich(a)gmail.com> wrote: > > Hello > > I am writing graphic demo programs using Athens on Mac Sierra. > Time by time Pharo VM crashes. Programs not using Athens work reliably. > I believe the behavior is reproducible. > How should I report a bug? > > Alex -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 22, 2017

Re: [Pharo-users] Strange behavior

by HernÃ¡n Morales Durand

Mmmm not really... below two examples of widely used software with complete search UI and used by millions of people (not even developers). They are TotalCommander and Notepad++, maybe we can learn something from them. It's a matter of learning how to design a nice UI, not reducing the features or inventing something completely new. Cheers, HernÃ¡n 2017-02-22 7:07 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > Martin's idea of sorting exact matches to the top should satisfy this > in practice, > without needing another checkbox. The less modes the better. > > cheers -ben > > On Wed, Feb 22, 2017 at 10:46 AM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > > > This is unfriendly. A Regex checkbox for the two people in the world who > can > > memorize regular expression patterns... > > > > Wouldn't be easier to add a "Exact match" check box? > > There are also uppercase and lowercase issues there. > > > > Cheers, > > > > HernÃ¡n > > > > > > 2017-02-19 12:37 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > >> > >> You might tick Regexp and search for... now$ > >> cheers -ben > >> > >> On Sun, Feb 19, 2017 at 7:24 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > >> wrote: > >> > Because 'now' is a case insensitive substring of each of those > selectors > >> > (like ..known.. or ..nOwner.. , both seem quite common). > >> > > >> >> On 19 Feb 2017, at 12:20, Mark Neagu <mark(a)mneagu.fr> wrote: > >> >> > >> >> Hi everybody, > >> >> > >> >> The Finder has answered my question but the proper answers were sort > of > >> >> hidden in a heap of apparently insignificant answers. > >> >> > >> >> I'm sure it's useful and I would like to understand how, if someone > is > >> >> gentle enough to tell me. > >> >> > >> >> Cheers, > >> >> Mark<Finder does strange things.jpg> > >> > > >> > > >> > > > >

Feb. 22, 2017