On 10/12/2013 01:57 PM, Adrian Klaver wrote:
...
In the text based systems I am familiar with their where keyboard
shortcuts that took you directly to fields and coding conventions that
allowed direct entry of data. For example at a plumbing supply house I
went to the convention was something
On 10/12/2013 6:15 PM, Chuck Davis wrote:
For those of us who grew up on real computers the only appropriate way
to get from one input field to the next is hitting the enter key. You
Well, I grew up with a real computer. There was no enter key on the 029
key punch; that only came along later
On 13/10/2013, at 9:15 AM, Chuck Davis wrote:
> the only appropriate way to get from one input field to the next is hitting
> the enter key.
Ha, I remember how blazing fast entry could be on old terminals with a field
exit key on the numeric keypad - particularly when standardised on 4-6 dig
On 12/10/2013 23:15, Chuck Davis wrote:
For those of us who grew up on real computers the only appropriate way
to get from one input field to the next is hitting the enter key. You
know what that does in a browser...makes efficient data input
impossible. NOBODY should have to hit the tab key
On 10/12/2013 02:40 PM, David Johnston wrote:
Adrian Klaver-3 wrote
pv150el90 = PVC 1.5" ell 90 degree
abs150el90 = ABS 1.5" ell 90 degree
You can code an interactive command line processor in pretty much any
language - html+javascript included. The issue is likely one generalized to
GUI in p
Hi Chuck,
>
> Could you explain the acronym AP?
>
> I understand that there are lots of situations I have not met yet, so
> this might explain my ignorance, but I don't see what you get from using
> a client-side app over a browser for most databases uses; after all,
> from the user's point of vie
Adrian Klaver-3 wrote
> pv150el90 = PVC 1.5" ell 90 degree
> abs150el90 = ABS 1.5" ell 90 degree
You can code an interactive command line processor in pretty much any
language - html+javascript included. The issue is likely one generalized to
GUI in particular since now that people are used to ha
On 10/12/2013 01:14 PM, Vincent Veyron wrote:
Le samedi 12 octobre 2013 à 12:19 -0700, Chuck Davis a écrit :
Just for an example: If you have 500 clients placing one order a
browser is an "ok" tool -- probably the tool of choice. If you have
one accounts payable clerk entering 500 orders a br
Le samedi 12 octobre 2013 à 12:19 -0700, Chuck Davis a écrit :
> Just for an example: If you have 500 clients placing one order a
> browser is an "ok" tool -- probably the tool of choice. If you have
> one accounts payable clerk entering 500 orders a browser is a very
> mean thing to do the your
On 10/12/2013 12:19 PM, Chuck Davis wrote:
Browsers are fine for displaying informaiton that is already in a
database. They are the ultimate crap for entering data that has to be
typed into a "form" and processed for persistence. It will be a long
time before I ask my users to enter data into a
Browsers are fine for displaying informaiton that is already in a
database. They are the ultimate crap for entering data that has to be
typed into a "form" and processed for persistence. It will be a long time
before I ask my users to enter data into a browser.
Just for an example: If you have
Le samedi 12 octobre 2013 à 15:39 +0200, Wolfgang Keller a écrit :
> "Web mailers" are a particularly illustrative example why "web apps" are
> ridiculous garbage. Just like "web forums" or "Google Apps".
>
> If I had to use those, I would cease to use computers at all.
>
Sure, they suck, but I
On 10/12/2013 06:39 AM, Wolfgang Keller wrote:
Certainly not. Not to mention the issue of end-user productivity. Not
to mention the deployment mess, both server- *and* client-side, with
"web apps". Etc. and so on...
Five years ago I would have agreed with you totally. Web applications
where
> >> Forms these days are written in HTML.
> >
> > Only by clueless/careless morons.
> >
> > HTML has never been, is not and will never be a usable GUI
> > framework.
> >
> > And "web apps" are unusable garbage.
>
> Look -- I appreciate people with strong unorthodox beliefs but your
> statement ab
> My interpretation of "Forms these days are written in HTML" means
> most interfaces are web front ends to the cloud. Not a GUI framework.
"Cloud", "web apps", yet more fashionable trendslang buzzwords.
I am talking about worktools that actually help productive "information
workers" to get usefu
Wolfgang Keller-2 wrote
>> Forms these days are written in HTML.
>
> Only by clueless/careless morons.
>
> HTML has never been, is not and will never be a usable GUI framework.
>
> And "web apps" are unusable garbage.
Yet you have not stated what it is that you find works better.
Lots of softw
On 12/10/13 05:06, Steve Atkins wrote:
On Oct 11, 2013, at 8:57 AM, Bret Stern
wrote:
My interpretation of "Forms these days are written in HTML" means
most interfaces are web front ends to the cloud. Not a GUI framework.
Yup.
But embedding an HTML renderer in your desktop app does allow y
Agreed.
On Fri, 2013-10-11 at 09:06 -0700, Steve Atkins wrote:
> On Oct 11, 2013, at 8:57 AM, Bret Stern
> wrote:
>
> > My interpretation of "Forms these days are written in HTML" means
> > most interfaces are web front ends to the cloud. Not a GUI framework.
>
>
> Yup.
>
> But embedding an H
On Oct 11, 2013, at 8:57 AM, Bret Stern
wrote:
> My interpretation of "Forms these days are written in HTML" means
> most interfaces are web front ends to the cloud. Not a GUI framework.
Yup.
But embedding an HTML renderer in your desktop app does allow you to
use HTML where it's appropriate
My interpretation of "Forms these days are written in HTML" means
most interfaces are web front ends to the cloud. Not a GUI framework.
On Fri, 2013-10-11 at 14:47 +0200, Wolfgang Keller wrote:
> > Forms these days are written in HTML.
>
> Only by clueless/careless morons.
>
> HTML has never bee
With a brief look at the last 15 years of programming for the web, your
comments are a little harsh. Only a short time ago perl and cgi
was the rage.
I've been programming for 30 years...and still have clients who use
Lotus 123 (MS-DOS) based. It's a big world out there, and lots of
solutionsf
On Fri, Oct 11, 2013 at 7:47 AM, Wolfgang Keller wrote:
>> Forms these days are written in HTML.
>
> Only by clueless/careless morons.
>
> HTML has never been, is not and will never be a usable GUI framework.
>
> And "web apps" are unusable garbage.
Look -- I appreciate people with strong unortho
> Forms these days are written in HTML.
Only by clueless/careless morons.
HTML has never been, is not and will never be a usable GUI framework.
And "web apps" are unusable garbage.
Sincerely,
Wolfgang
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to y
On Wed, Oct 9, 2013 at 9:24 PM, Adrian Klaver wrote:
> On 10/09/2013 07:05 PM, Sudhir P.B. wrote:
>>
>> I have developed an application using MS SQL. I have used MS Access for
>> creating forms to enter data into the database. I am thinking of
>> changing over to postgresql and would also like to
24 matches
Mail list logo
