|Subject:||Re: Qbe date parse results - final?
|Date:||Wed, 18 Apr 2018 23:50:45 -0400
|From:||"Larry DiGiovanni" <nospam@nospam>
Bernie van't Hof wrote:
> In my project I originally envisaged the bulk of the app running on the
> server, communicating
> with some sort of simple glass teletype on the web client. Not very
> efficient perhaps, but given
> the nature of the project I really didn't care.
I took a deeper dive into your code this evening (I still can't get it to
run in any useful fashion, which is a barrier to understanding), and I can't
figure out the client event model, but it appears to be driven to the
keystroke. Not sure how mouse interactions are trapped and translated. It
appears that the actual form rendering is not yet implemented (at least as
of my most recent pull in March).
But I'm guessing that the HTML in #PXdata is intended to be well formed,
CSS-driven DOM. If your event capturing doesn't interfere/override the html
events, then you could dynamically inject validation as part of #PXdata.
Was that part of the strategy?
You weren't kidding about the teletype approach as evidenced by this little
gem in your px.css:
/*font-family:Verdana, Geneva, sans-serif;*/
/*font-family: Arial, Helvetica, sans-serif;*/
font-family: "Courier New", Courier, mono;
There's something you don't see every day. :-)