Pete wrote:
> You can specifiy what is in a drop down, or use some simple javascript to
> perform field checking. I've used the "onblur()" function to check an HTML
> field against an array of data once the cursor leaves the field, this would
> be pretty simple to implement if you were using a scripting language like
> PHP. Well...at least when Eloquence support is added to PHP.

It is and we use it for Web projects :-)
Access is currently performed through ODBC.

As far as i remmeber someone recently posted an annoucement to this
list that they added IMAGE database calls to PHP (there was a link
to invent3k) and we are going to take a look at it.
Not sure if it makes sense if the real world but it surely is
interesting.

To contribute something on topic as well :-)

With HP Eloquence A.07.00 we are adding the option to run HP Eloquence
programs with no or only minor changes with a web browser. We added an
Apache module which provides a virtual connection between the user and
the running program. It comes with its own set of problems but works
astonishing well (details available on the web site).

The same can likely be done with VPLUS and (since it works in block
mode which is closer to the Web aproach) likely with less efford.
Exposing some basic validation rules to a Javascript runtime (and
checking them again in the server context) should make it pretty usable.

If you extend on the user interface presented by VPLUS (eg. present
a combo box with choices) you have the option to either embed it in
the page (up to some size) or open a now window and transfer the
result back to the original window (requires some Javascript).
I have used this aproach in Web projects. Of course it is sort of
annoying to pop up new windows all the time so there must be some
added value.

Using the Web as a user interface puts some extra load on the server
but is not necessarily slow. The problems are IMHO more likely
perception and latency. To update a page you have to output it again.
Entirely. Other solutions are tricky and not faster. The user
interface seems less "smooth" then filling fields in a form.
Each "transaction" (client/server exchange, pressing enter) costs
some extra time (transfer the request, parse the results, contact
the application process, translate results to HTML and transmit to
the browser) and we all know that users have a threshold on that.
Bandwidth is probably less of an issue. For one the net access is
getting faster any day and using compression could reduce the size.

But why see this as an either/or type of decision? I would not use
that if had to enter a data all the time (eg. order entry) but this
could be an option for casual users. There is no need the HTML pages
could not look pretty or have additional links to help texts or some
other added value (viewing images, etc). People will find likely
find a good use for it. For example access from a remote site, travelling
or opening parts of the application for partners or customers where
you cannot demand a specific configuration.

Beeing able to use the web also has the benefit that you may get
around re-implementing part of your application. Complex pricing rules
are also complex in PHP ...


Just a few thoughts
Michael

> On November 23, 2001 12:12 pm, Kevin D. Joseph wrote:
> > I know that this has become a discussion to some degree of moving vplus to
> > the web, but to muddy the waters some more the challenges of moving a
> > windows app to the web can introduce some more headaches.  How to handle
> > popup pick/selection lists.  Do you send a list of a 100/1000/? valid
> > values in a dropdown or use a separate window and javascript to have the
> > user select a value, maybe with the ability to filter the list?  Would
> > your users accept a perceived loss of functionality moving from windows
> > (or any stateful gui) to the web?  A whole new world.

--
Michael Marxmeier           Marxmeier Software AG
E-Mail: [log in to unmask]      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *