GUI Front Ends - the discussion

[Bruce Easton]

(inline responses [<<<] - Bruce Easton, STN, Inc.)

-----Original Message-----
From: Richard Hane
Sent: Friday, March 21, 2008 11:29 AM

I would like to start this as a discussion thread. A couple of ground rules.
1. No one is right and no one is wrong; we are all just voicing our
opinions. 2. Although my O/S of choice is Windows this certainly can include
*nix systems.  Please let's not turn this in to a discussion of operating
systems.

I have a couple of large projects coming up and have to make some decisions.
These are the same decisions I think many on this list either have made or
will be making in the near future.  These new applications will require a
"GUI-like" front end for input, updates and searches.  Some MAY involve use
over the web. However, that is not an immediate requirement. Most important
I want all processing to be handled by filePro. We are currently using
fpODBC 1.0.13 on 16 workstations under Windows 2003.

The question to be answered: What to use to create the GUI front end?

<<< (and what to run under! [especially if you are considering
<<< something outside of the filePro area altogether])

1. Do we use another database program like MySQL, Miscrosft SQL Server,
Access, Oracle, etc.? If so, which one and why?

<<< Ah, there it is. [re: main ?? above] :) I can't really speak to
<<< things outside of filePro on this.

2. Or rather do we use a browser on an intranet initially and maybe port to
the web later?

<<< Could be a good idea in terms of becoming comfortable and feeling
<<< safe about the app. before turning it (or parts of it) on to
<<< the outside.

3. If we use the browser what do we use; FPCGI, fpWeb, One Gate, etc?

<<< I would recommend looking at any documentation and contact the
<<< various vendors involved in this arena for starters, Rick to
<<< learn more about what each product is supposed to do and how
<<< they view their product differing from the others.
<<<
<<< In case you are not aware of the basic differences in basic
<<< category of products, here is sort of a functional breakdown
<<< the way I see it (others please clarify if you see differently):
<<<
<<< --OneGate/fpCGI-based-------
<<< fPageBuilder(TM) (STN's upcoming product) runs ontop of
<<< OneGate specifically against filePro [and can utilize OneBridge].
<<< (Already in use and available via STN services, but not quite yet
<<< as off-the-shelf.)
<<<
<<< Other developers offering custom programming services that are
<<< intended to run against filePro ontop of either OneGate
<<< and/or fpCGI.
<<<
<<< --non-OneGate/fpCGI-based---
<<< fPWeb, I believe, is specifically meant to work against
<<< filePro and is a development environment and cgi platform
<<< all in one.
<<<
<<< Other developers that may be running custom cgi apps.
<<< against filePro using some other kind of cgi platform
<<< using Perl, etc.
<<<
<<< Did I forget or mis-represent anything???

4. Or is fpGUI a possibility?  What ever happened to fpGUI?  I own one of
the first copies but you never hear anyone discussing it.

<<< (Since Richard spoke to this, I don't think I need or want to
<<< say too much on this, but I would stress that you consider
<<< parallel functionality, price, installation & configuration
<<< between the web-based options and the *whole* filePro GI
<<< product including the Dev. Tool Kit in relation to your needs.)

We are not concerned with output at this time as we have decided to use (and
we own) Print Wizard. Nice program Bob.

<<< Nice program indeed.

OK, so there is our delema.  Which way to go.  We really don't want to start
down one path and the later turn around and reinvent the wheel.

<<< Understood.

<<< Rick, since you are asking about GUI and browser-based at the
<<< same time, here are a couple of things to consider in terms of
<<< your options when staying with filePro databases.
<<<
<<< 1. Security - what are your needs for this?  Where will the
<<< 'GUI' parts of your application reside?  If making parts of your
<<< application browser-based, do you think it will it necessitate
<<< a different approach to security for the entire app.?
<<<
<<< 2. Expected Look and Feel - you say "These new applications will
<<< require a "GUI-like" front end for input".  How much is really
<<< expected?  Does your client expect to sit with you and try out
<<< different color schemes, font and border-sizes, etc?
<<< And, more importantly, what is expectation for how the new
<<< front end should behave.  Not just how things may be better
<<< located, appl. normalized, etc., but can the program be used in
<<< a reasonably efficient manner as the character-based app.?
<<< [I know you say "new applications", but I'm stressing this
<<< for those considering updates to existing character-based
<<< software.]  In other words, does the development software
<<< and runtime platform you are using for this give you the
<<< tools to give your end-user useful tools and short-cuts to
<<< save time in data entry/udpate.  I believe things, by nature
<<< are slower under any 'GUI' solution, so I feel it is
<<< important that a.  the client understands how things will
<<< change (and I think it really has to be demonstrated
<<< before it sinks in), but
<<< b. you can compensate (or should be able to
<<< under the development and runtime environment you choose)
<<< and often improve upon the experience, via shortcuts,
<<< end-user tools, customizations and via being able to
<<< bring some of the best features of character-based
<<< filePro right into the web environment.

I look forward to the thoughts of all you wise and noble users of the fp.

Thank you in Advance,
Rick Hane,
Controller
Deluxe Stitcher Company Inc
www.deluxestitcher.com
773-777-6500