On the Web Layout and Function

[Dr. Evil]

Is it common to create separate layouts just for web?

Some items do not look nice on the web as they do in native FM environment. Mostly the portals, scroll buttons are forced into the area.

Also think separate web layouts are a good idea because I will design them with little to no graphics for quick loading.

I would like to have a fully functional database on the web, this may mean I need to upgrade my FileMaker to Server or...?

I am at the final stages of creating my DB and do not want to redo layouts and have functions not work in web.

P.S. In the web world, value list only show the first field. This will not work due to the fact that it is only a ss# that means nothing to the user. Is there a simple fix, or do i need to replace ss# with name? Uhg..!

Any tips, advice or comments on this topic is much encouraged.

Thank you all in advance!!

[CyborgSam]

I gave a presentation on IWP, here are some hilites. Eventually I'll finish the demo file and upload it here...

The same layouts can be used by following a few guidelines.

Convert external graphics to .GIF format before using Insert>Picture.. to get them on a layout or in a field. IWP converts ALL graphics except GIF to a low quality JPG.

Make sure there's enough room for the quirks of checkboxes, radio buttons, and popup menus/lists.

The common trick of putting a transparent graphic over a portal row to allow clicking won't work in IWP, a visible graphic is necessary (I use a right facing arrow).

Web users cannot enter nor modify data in Container fields.

Set Error Capture [On] is a must in IWP Finds & similar functions, since IWP will not display the “No records found.” dialog.

Web characters in field names (e.g. # and ?) cause problems using IWP’s sorting. It’s best to avoid them, as helpful as they can be.

When a repeating field’s repetition is specified on a layout to a range of 1 (e.g. rep 3 to 3 in a field with 6 reps), the field always shows the first repetition. Showing all repetitions works OK, sub-ranges were not tested.

Setting the tab order does not affect IWP, the front-to-back arrangement of the fields does. The last field on the layout must be the frontmost object, with other fields going back in order. Note that all graphics, lines, rectangles, text, etc. are to the back of the fields. One way to do this: select all fields, bring to front, deselect first field, bring to front, repeat for remaining fields.

IWP in FileMaker Pro only displays a limited set of records in List view (the latest update raised the view as List limit from 5 to 25). FM 7 Server Advanced allows full lists, but costs $$$. To get around this, make your own scroll bar graphics & assign to the buttons scripts that get the record # and add/subtract some amount to make scrolling realistic. Be sure to check for 1st & last records...

[Dr. Evil]

Hello CyborgSam,

Thanks for all the helpful tips!

Your mention of the script scrolling list's, can this method work for portal scrolling in IWP as well?

Also, sometime if you could explain this scripted scrolling "how to" that would be great!

I look forward to the demo file!!

[CyborgSam]

Yes, portals can be scrolled through the use of graphics. The script will use the step Go to Portal Row with a calculation based on Get (PortalRowNumber) with some value added/subtracted. To mimic an up/down arrow, add or subtract 1. To mimic clicking in the scroll area, add or subtract the # rows (less one for good GUI design). In all cases, check to make sure the calculated value is within the range from 1 to the last portal row. To calculate the last row: when the script is called, freeze window, and first do a Go to Portal Row [Last] and then Get (PortalRowNumber).

Does anyone have a better way to do this?

[comment]

I know nothing about IWP, but surely the last row = Count(related) ?

[CyborgSam]

Yes. I thought I read somewhere thast Count was slower to do this. Anyone know for sure?