Re: [Pharo-users] Why do I not see the transactions when opening a customer

2019-08-19 Thread Diego Lont
hange their own > password without call centre or administrator intervention. > > Do you know of any implementations of user/password stores that are resilient > to malevolent or broken code? > > Cheers, > > J > >> On 19 Aug 2019, at 5:40 pm, Diego Lont >

Re: [Pharo-users] Why do I not see the transactions when opening a customer

2019-08-19 Thread Diego Lont
The best way to implement a password security is to never store the password, but only a hashed password. This way, you never can have a security leak for your passwords: because you don’t have them. And for hashing you use a standard modern hashing algorithm, so it cannot be easily rolled back.

Re: [Pharo-users] Magritte seaside save

2018-12-30 Thread Diego Lont
Hi Vitor, It has been a while that I really used Magritte, but basically the problem that you encounter is that the save is not called on MyObject, but on the component that is created from MyObject (in the method asComponent). The save method calls the save on the component, and in Magritte th

Re: [Pharo-users] PetitParser: Building composed (dependent) parsers and isolating productions code

2018-02-02 Thread Diego Lont
Hi, I have never used dependents (^ (self dependencyAt: StatementBParser) ruleB), but here are my thoughts when reading this. When parsing it makes sense to make a separation between syntax and semantics. Applying this functional distinction in your technical design usually makes sense. In pr

Re: [Pharo-users] QCMagritte on Github

2017-10-29 Thread Diego Lont
Hi, It was somewhere on my todo list to migrate to Github, but not very high… but I guess if someone else does this for me, I should be happy about this. So thank you, I will look up my gut hub account and also change the job. I hope to do this somewhere next week. I know there a different co

Re: [Pharo-users] Web stack practices (Glorp / QCMagritte)

2017-09-22 Thread Diego Lont
uration, but this will be next week. Regards, Diego P.S. QC stands for the company it was originally build for. I do not know exactly where the initials stand for … as it was already an historic name at that time. > On 22 Sep 2017, at 13:35, H. Hirzel wrote: > > On 9/22/17,

Re: [Pharo-users] Web stack practices (Glorp / QCMagritte)

2017-09-22 Thread Diego Lont
There is actually a tutorial included in the framework itself. One you have it loaded, you can start the webpage to localhost:8080 and there you have your tutorial. But this tutorial should be on a external webpage … one of the things on my todo list. > On 22 Sep 2017, at 12:55, H. Hirzel wrot

Re: [Pharo-users] Web stack practices (Glorp / QCMagritte)

2017-09-22 Thread Diego Lont
Hi Laurent, I am happy that you like QCMagritte. I wrote quite some parts of it, but it also has been a while since I last used it. I try to support it in my spare time, so I will look into the issue that prevents it from loading into pharo 6. Here some ideas that I think of, QCMagritte is a s

Re: [Pharo-users] object serialization, STON & PharoJS

2017-07-20 Thread Diego Lont
Hi, What I remember of STON is that it simply puts out the entire tree. So it might include things you don’t want (like thisContext), and also does not handle loops well. But that is from memory, I might be wrong there. For serialisation you could also look into the Magritte serialisation. It h

Re: [Pharo-users] Some Metacello issue

2017-06-08 Thread Diego Lont
> On 08 Jun 2017, at 09:36, Diego Lont wrote: > > Hi all, > > To keep the common projects in smalltalkhub stable, we agreed that those > should use symbolic versions like release3 // release3.5 etc. This way we can > add bug fixes and avoiding loading of different versi

Re: [Pharo-users] Some Metacello issue

2017-06-08 Thread Diego Lont
Hi all, To keep the common projects in smalltalkhub stable, we agreed that those should use symbolic versions like release3 // release3.5 etc. This way we can add bug fixes and avoiding loading of different versions through different projects. But I might have done something stupid to the confi

Re: [Pharo-users] Magritte extension

2017-03-22 Thread Diego Lont
> On 22 Mar 2017, at 20:36, p...@highoctane.be wrote: > > Magritte is nice but the amount of work is just too much for my taste. Simple > forms are better handled with somethibg like Mold. > > And this especially when components interact with a ton of Js. Then I want you to challenge you: try

Re: [Pharo-users] Magritte extension

2017-03-22 Thread Diego Lont
> On 23 Mar 2017, at 04:27, Ben Coman wrote: > > On Thu, Mar 23, 2017 at 5:25 AM, Diego Lont wrote: >> >>> First of all I want to advertise QCMagritte: This framework is easy to use. >>> It has a seaside like tutorial, that every developer should be able to &

Re: [Pharo-users] Magritte extension

2017-03-22 Thread Diego Lont
> First of all I want to advertise QCMagritte: This framework is easy to use. > It has a seaside like tutorial, that every developer should be able to > follow without any significant problems and shows all significant features > of both Magritte, Seaside and QCMagritte. Although it lacks document

Re: [Pharo-users] Magritte extension

2017-03-22 Thread Diego Lont
> On 22 Mar 2017, at 00:46, Ben Coman wrote: > > On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont wrote: >> It has been a while that I was really involved in developing on (QC)Magritte >> and doing stuff on the web ... > > btw, what does the "QC" represent? QC is a reference back to the company fo

[Pharo-users] Improving Magritte

2017-03-21 Thread Diego Lont
Hi all, Recently there was a question about Magritte extensions on the Pharo users list. It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web, but on my todo list, there is feeding back the improvements on Magritte I have made for QCMagritte to