Aaron,
thanks! Actually I could extend the user class easily, without a need to make a
generic interface. Nevertheless I don't think either would help: in this
particular case, the „canSeePage“ ability does not depend on the user, but only
on whether the application has been connected to normal
Markus,
thanks!
> On 9 Jan 2022, at 17:27, Markus Ruggiero wrote:
> When you create your page inheriting from OCSComponent you inherit all the
> methods including all managing your currentUser. Just override those. I would
> think that solves your problem without too much of legwork.
Alas, th
OC, your idea will work, but here’s another to consider.
Make an interface for user objects, call it “UserInterface”
You are now free to have multiple types of user objects that all implement a
common interface. You can make your current User implement the interface and
now make a brand new Us
When you create your page inheriting from OCSComponent you inherit all the
methods including all managing your currentUser. Just override those. I would
think that solves your problem without too much of legwork.
Have fun
---markus---
> On 9 Jan 2022, at 10:21, ocs--- via Webobjects-dev
> wro
Hi there,
I've got a pretty old application, the standard structure: there's Session
which (among others) contains a property currentUser containing the user who
has logged in and in whose account changes are performed. There is an
OCSComponent extends ERXComponent with generic component servic
