NT607 Wizard General Comments

[terryd]

Windows7 64 Clarion8.8778 Nettalk607
Hi Bruce
Using the wizard I found the following. I hven't seen a roadmap so I am not sure if this what is intended.
1. Menus are created but the browses are not attached to the menus (They used to in 605)
2. A lot of recursives caused by the browses being used as lookups. Is it your intention in the future to automatically create select lookups or possibly drop lookups with the wizard
3. The browses locators are now set by default above the browse whereas the netwebbrowse defaults to below the browse. No big deal but maybe one of the settings on the wizard could be a default location?
4. I used the wizard and the issue with (only) Chrome not sizing the form correctly still persists. I use the same version of Chrome that you do.

[Bruce]

Hi Terry,

There are some changes happening under the skin for the wizard - primarily to try and work around some limitations in the IDE (which may indeed in turn be created by me. time will tell.)

>> 1. Menus are created but the browses are not attached to the menus (They used to in 605)

that's a bug - I'll fix that.

>> 2. A lot of recursives caused by the browses being used as lookups.

 This is itself is not a problem. The Webtemplates have hooks for "parent" procedures, which the IDE sees as "children" in the app tree. It marks it as recursive (which it usually isn't) but either way it's fine.

>> Is it your intention in the future to automatically create select lookups or possibly drop lookups with the wizard

no, probably not. Creating a separate browse for a lookup is unnecessary. It bloats the code, and makes long-term a maintenance a pain. there's no reason the same browse (optionally with conditions) ca't do both roles.

Drops are easy to change-to if the field is set as a lookup - and there's no way to automatically make a good decision (that I can see) of when to use one, and when the other, so I'll leave that as something you can change after the wizard generates. Unless you can think of something?

>> 3. The browses locators are now set by default above the browse whereas the netwebbrowse defaults to below the browse. No big deal but maybe one of the settings on the wizard could be a default location?

sure, I do plan to offer more browse, and form, options as we go.

Cheers
Bruce

[peterH]

Drops are easy to change-to if the field is set as a lookup - and there's no way to automatically make a good decision (that I can see) of when to use one, and when the other, so I'll leave that as something you can change after the wizard generates. Unless you can think of something?

It _could_ be an option in the wiz: generate lookups as button/drop. JAT

Peter

[terryd]

I wasn't really excited about drops since to me they normally depend on the  number of records in the lookup table and whether I want to show whoever is doing the lookup just the description field.
 

[Bruce]

>> It _could_ be an option in the wiz: generate lookups as button/drop.

It wouldn't be a good idea to do this on a "global" level Peter, ie in the wizard, because Drops are "file loaded". Which means that if the list of options is long the page would basically take a long time to load, and be very "expensive" from a server effort point of view.

Some lookups definitely could be set as drops, but unfortunately there's no way for the wizard to tell which is which. Only the programmer will have some feel for how many records are likely to be in the lookup.

cheers
Bruce