The main reasons I'm not discussing why I need the solution fall into various categories that usually result in a thread going way off course very fast:
1) user interface design has nothing to do with the matter at hand. There is a technical problem at hand, and the discussion should be constrained within that scope. A UI design is one thing, and the lower level implementation blocks to achieve it are another. In the most simplistic explanation: if the task can be achieved by the browser, why aren't there standard ways for accessing that feature?
2) Once the flood gate is opened on whether any given choice for a UI element is appropriate, the real meat of the problem ((1)) is never discussed, and the thread goes so far afield, that the topic is never really settled. This, not to mention, a rapid growth of apathy from the readership.
3) While I certainly agree that only warranted uses should warrant in-depth discussion, it doesn't apply here. There is already strong precedent for the need and use of a "prompt box" found in applications in every facet of computers, platforms, and applications; its use and presence in javascript already illustrate that point, as well as similar UI features in Tk, et al.
4) Lastly, from a mere matter of pragmatism: one cannot and should not have to suddenly change their entire platform for development because of something as simple as a prompt box. That is, rewriting what could already be a huge undertaking in javascript "just because it has a promptbox" isn't justifiable. (whereas, rewriting the internals of a large program to take advantage of the speed and processing power of a major database backend may have justification.)
In reply to Re: Re: "alert" or prompt box from perl cgi script
by argv
in thread "alert" or prompt box from perl cgi script
by argv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |