Request 23?

[Jim Locker]

Any analog of this SBL requester?

[Michael]

Jim wrote:
> Any analog of this SBL requester?
>

In uisyshelp.sml (see project source code), there is a function called
getuserinput() that has an optional parameter: passwordstyle.

Ciao, Neil

[Jim Locker]

Sorry, I said request 23 when I meant request 20.

Hey! you don't expect me to say what I mean, now do you?

So, is there a request 20 analog?

[Michael]

Jim wrote:
> Sorry, I said request 23 when I meant request 20.
>
> Hey! you don't expect me to say what I mean, now do you?
>
> So, is there a request 20 analog?
>

NO, not yet. I have been intending to build one along the lines of
either 20/24/25 or else along the lines of the drilldown versions that I
did, but I just haven't gotten to it yet. If you want to make a run at
one, and contribute it back, I would certainly welcome it (I could use
it myself).

Ciao, Neil

[Jim Locker]

I guess I'm going to have to. I suppose I'll make it page rather than try
to load the entire database contents at one time; could take a long time
to load tens of thousands of entries…

[Michael]

Jim wrote:
> I guess I'm going to have to. I suppose I'll make it page rather
> than try to load the entire database contents at one time; could take
> a long time to load tens of thousands of entries…
>

Paging is the right approach. What I did with the drilldown is to use
the characters typed by the user as the basis for a query. I also
limited the maximum number of results.

Ciao, Neil

[Jim Locker]

Well, I now have a working request 20. It accepts an array of fields to
display, so the old 4 field limitation is gone. It has no filtering
capability because there is no generalized query engine for this database,
so I pass a function reference to a function that gets called after the
dataset is returned and before it is displayed. This permits that data to
be post-processed as necessary. If the function is not needed, it still
has to be present but can be a stub.

The requester will filter on a selectkey.

My basic design philosophy has me completely separating the gui from the
database, and I am adhering to that philosophy here. The return from the
database functions is an array of results, not record objects or anything
like that, and the requester works with the arrays.

In fact, my entire system decomposes into three functional components:
those that work with the database on one side and arrays on the other
side, those that work with forms on one side and arrays on the other side,
and those that work with arrays on both sides.

In any case, the code for this requester needs to be cleaned up and needs
a bit of generalization (size of window is currently fixed and that needs
to be variable), and I sure would like to integrate that query engine you
have promised.

But it works, and after I have cleaned it up a bit and move it to a
library I'll make it available.

[Michael]

Jim wrote:
> Well, I now have a working request 20. It accepts an array of fields
> to display, so the old 4 field limitation is gone. It has no
> filtering capability because there is no generalized query engine for
> this database, so I pass a function reference to a function that gets
> called after the dataset is returned and before it is displayed. This
> permits that data to be post-processed as necessary. If the function
> is not needed, it still has to be present but can be a stub.
>
> The requester will filter on a selectkey.
>
> My basic design philosophy has me completely separating the gui from
> the database, and I am adhering to that philosophy here. The return
> from the database functions is an array of results, not record
> objects or anything like that, and the requester works with the
> arrays.
>
> In fact, my entire system decomposes into three functional
> components: those that work with the database on one side and arrays
> on the other side, those that work with forms on one side and arrays
> on the other side, and those that work with arrays on both sides.
>
> In any case, the code for this requester needs to be cleaned up and
> needs a bit of generalization (size of window is currently fixed and
> that needs to be variable), and I sure would like to integrate that
> query engine you have promised.
>
> But it works, and after I have cleaned it up a bit and move it to a
> library I'll make it available.

Cool! Good to hear it. There is always room for any number of these
types of popup, so even if somebody wants it to do something different,
they can use yours as a template for where to start.

I look forward to the finished one.

Ciao, Neil

[Author]

Posts