limiting browse based on login?

[Fairlight]

>From inside the gravity well of a singularity, fpgroups at gmail.com shouted:
> No argument there ... Once done, you usually end up with a better UI at
> least

And no argument there.  But especially in the current economic climate,
people are far less likely to be willing to toss away their current
development, or even to augment it to a side-by-side solution.  They want
to preserve their current programming investment unless they have an
absolute need to do otherwise--something that will bring in more income
than they currently receive.

I'm just saying, while the end product is superiour (assuming a competent
designer/programmer), web development isn't all roses and champaigne.  It
involves usually at least four extra technologies, if not more, and the
development curve is steeper.  The design aspect eats up more time purely
because it can be very slim, very robust, or somewhere between--something
that more often than not leads to feature creep and organic design past a
certain point, unless you put your foot down.

I'm all for a web based UI and its development.  I also don't want to give
anyone any illusions...it costs, either in time or money (or both).  And it
costs a lot more if you don't have a clear design in mind (and on paper!)
from step 1.  Not just a general overview, or just the first part, but the
entire thing, start to finish.  If you're just winging it, you're in for a
long ride, a bunch of changes as things crop up, and a far more costly
organic experience.  Pre-planning is paramount--unless you get something
like fPageBuilder from STN, which can take a lot of the pain out of it.
Anything that's not canned, however, needs major planning.  It's like
carpentry:  measure twice, cut once.

Comparatively, there is a lot less "design" work in native fP.  Of course,
it's a lot less powerful on the UI side (and sometimes under the hood if
you augment fP with other tools).  There's your tradeoff.

mark->