On Sun, May 3, 2020 at 7:22 PM Craig Russell wrote:
>
> I'd like to start with something that should be trivial:
>
> When the user presses "move to emeritus" or "deceased" the action is
> immediate. I'd like to change these buttons to raise a dialog box with
> (submit) and (cancel) buttons. In g
I'd like to start with something that should be trivial:
When the user presses "move to emeritus" or "deceased" the action is immediate.
I'd like to change these buttons to raise a dialog box with (submit) and
(cancel) buttons. In general, this is my own preference and better UX and I
think muc
On Sun, May 3, 2020 at 5:06 PM Craig Russell wrote:
>
> Next level of architecture:
>
> Most of the work should be done in the front end with a bit of help from the
> server. What we need from the server are:
>
> GET: given the apache id, return the full name, status (boolean: emeritus),
> the c
Next level of architecture:
Most of the work should be done in the front end with a bit of help from the
server. What we need from the server are:
GET: given the apache id, return the full name, status (boolean: emeritus), the
complete document if already filed under emeritus-requests-received
Sounds like a great idea so far!
On Sun, 3 May 2020 at 09:22, Craig Russell wrote:
>
> We will create a new script at members/emeritus.cgi that will use a file
> template [1] at a member-accessible location. This script will be linked from
> the Members whimsy page.
>
> The script will have thr
We will create a new script at members/emeritus.cgi that will use a file
template [1] at a member-accessible location. This script will be linked from
the Members whimsy page.
The script will have three entry points:
Member in good standing
Emeritus request has been submitted
Emeritus Member
M
