On Tue, Oct 06, 2020 at 09:41:21PM +0100, Tim Mackinnon wrote:
> Anyway, that login screen… oh crap I have to write one of those…

For Seaside, there is TF-Login. And oh, it rolled its own file-based
versioning object persistence.

Version that I ported to Pharo 7 and Seaside 3.3:

- https://github.com/PierceNg/TF-Login/tree/pharo7

Feature branch for better security:

- https://github.com/PierceNg/TF-Login/tree/password

Some of the classes are too tightly coupled IMO. Also I'm tending
towards an API-first approach, which needs OAuth2 and OpenID Connect,
meaning either more pieces to integrate or totally not using this.

Pierce

Reply via email to