On 10/01/2021 17:23, TimS wrote:
> On 10 Jan 2021 at 15:35:20 GMT, Ahem A Rivet's Shot 
> wrote:
>
>> On 10 Jan 2021 15:13:39 GMT
>> TimS  wrote:
>>
>>>   On 10 Jan 2021 at 12:33:26 GMT, Ahem A Rivet's Shot 
>>>   wrote:
>>>
>>>   > On Sun, 10 Jan 2021 12:15:58 +0000
>>>   > The Natural Philosopher  wrote:
>>>   >
>>>   >>  So PHP is not equivalent to JavaScript. PHP is fine at interrogating
>>>   >>  databases and doing a lot of server side stuff, but for popup
>>>   >> dialogues and menus that expand you need Javascript.
>>>   >
>>>   >  I thought those could be done in HTML and CSS these days.
>>>
>>>   Not if you have a sequence of popups, where the content of a subsquent
one
>>>   depends on the choice made in the previous one. And the choices in them,
>>>   or even whether they are presented at all, depends on what you read out
>>>   of your databases server-side.
>>
>>  I'd think sending the whole decision tree up front should work, it
>> worked fine back when I was doing directory trees in early JavaScript on
>> Netscape 2.
>
> Er no. It will get out of hand when you have 30 in the first popup, 40 in the
> second, and 30 again in the third. When I did the front end to an assets
> database at my last job, that's how I started it. I could see it wasn't going
> to scale.
>
Actually it doesn't get out of hand,
As I said in order to have a rapidly navigable store inventory I sent
the whole bloody stock list down sorted by category as a giant series of
hidden  and used javascript to open up the parts of the tree the
user wanted to view.

And to invoke a page load for an individual stock item.

The whole thing was only about 50kB. And worked perfectly reasonably
over a 48k modem, too.

Loaded far faster than my banking software does these days.

--
WOKE is an acronym... Without Originality, Knowledge or Education.

--- SoupGate-Win32 v1.05