Scroll-less Portals

[comment]

The file you point at is similar to S

[Lee Smith]

The file you point at is similar to S

[Søren Dyhr]

What advantage would there be to eliminating one global field other then one less field?

The storage isn't on server. Now if calc's aren't adressing them should it be allright ...but if the developer doesn't know to restrain him-/her-self ...a lot of packages is transmitted over the network ...hogging good bandwith - which is one of the goals this thread aims to prevent.

They're (globals and flags) definatly in my book of inadequate means to make databases a "vessel of meaning" ...among repeating fields, copy/paste and the urge for eventtriggers.

--sd

[comment]

What advantage would there be to eliminating one global field other then one less field?

One less field is always good. Next, the script gets much simpler as a result. Less fields, simpler scripts = easier file maintenance. At least that's how I see it.

[Søren Dyhr]

Allthough I use the usual scrolled portal in my new upload, could this be an idea for LaRettas approach to add even more functionality to the set of records shown in her fixed portal:

http://fmforums.com/forum/showtopic.php?fid/27/tid/168000/pid/168511/post/168511/#168511

--sd

[LaRetta]

I will pull these ideas into my scroll-less portal functionality and testing. Thank you, Soren.

These tests have been put on temp hold for another 2-3 weeks because 1) I've been redirected to three other critcal projects which Management deems even more critical and 2) month-end is fast approaching.

I'm simply wearing too many hats. I currently have 8 design aspects in various stages of completion (from half-done to done but not beta tested). I would like to FINISH one darned thing before being moved elsewhere. Because when I then come back to a project, it takes a bit to figure out where I left off and get my head back into it. I heavily comment all calcs and scripts as I work but stepping back into an unfinished piece still takes additional time (I simply don't have) to get back to speed on it. And I'm reaching a point that unfinished projects are bumping into other unfinished projects in my design and I can't finish connecting one project until the other is finished (which is dependent upon ANOTHER piece).

I refuse to throw my hands into the air; I refuse to perform these speed tests half-baked; and I refuse to NOT test all of these options thoroughly to find the best solution. I think I need to learn how to REFUSE a new critical project until the current critical project I'm working on is finished. "Just say no" isn't always an option but I'm getting close to that point ...

LaRetta :)