Re: cost estimate for a GUI pilot

I think that makes a lot more sense than say adding a unit testing

framework to an application framework or scripting environment.

Unit testing can cover many areas other than just data validation. For
example, a unit test can verify that if an invalid login occurs does the
browser display "invalid login". Or when a user submits the "forgot my
password" form does the resulting email produce a URL that resolves as
expected.

Aaron Bartell

On Wed, Nov 5, 2014 at 12:36 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Regarding Bidi, the w3 standard suggests that you specify the direction of
text (left-to-write, right-to-left) in each HTML element by using the "dir"
attribute - not using CSS styles. So if you are comfortable with using an
HTML editor (we use Dreamweaver) and HTML templates for page layout, you
should be fine. You might run into trouble with tools that generate HTML
for you, or which generate / deploy JavaScript to manipulate the browser's
DOM instead of using HTML.

Regarding restructuring code, I recently began working on a framework that
facilitates the placement of code pertaining to data validation,
referential integrity constraints, and business rules "behind" database
triggers, instead of placing that type of logic in "applications".

So logic that affects the integrity of the database or logic which is
cascaded from database updates is automatically "inherited" by any type of
application, whether that be ILE, or Java, or any of the scripting language
environments which run under IBM i.

I think that makes a lot more sense than say adding a unit testing
framework to an application framework or scripting environment. Let
applications handle workflow, browser I/O, and actions which "request"
database updates. But handle database integrity and business rules inside
the database (so to speak), using ILE RPG, as opposed to coding that type
of logic in an application or scripting environment.

So data validation and RI constraints might run in "before" triggers, while
cascading operations and things like transaction and database I/O logging
might run in "after" triggers.

Also adopt a design pattern whereby workflow, browser I/O, and database I/O
are placed in separate source members, thus making application code easier
to maintain, too.

Nathan.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.