Wrote their own GWT Serialization using SDATA (SDATA similar to GDATA).

XML UI def passed to Client which renders the "view".
But each page still has some custom code delivered to the Client.

Used Incubator Table, now moved to Cell Table.

http://css3pie.com/

Utilizing Hidden Fields (Top, Bottom, and some in the middle which were used to redirect tabs to newly enabled fields).

Use Client Bundles to reduce RTs during initial load.

Framework deriving and injecting Widget IDs for Selenium/Fitnesse.

Using versions in the URL to control GWT Version.  Users can configure when they switch to new versions by module.

------------------------------------------------------------------------------------------------------------------------------------
Vertafore password: 1a9f2b1e6e8d4d1c1eb1f7434
------------------------------------------------------------------------------------------------------------------------------------

SeaSPIN - 4 Oct 2011

The Ambiguities of Experience - James G. March

Three types of systems:

   1) Ordered system (Sense, Analyze/Categorize, Respond - Good / Best Practice)
        System constrains all agent behavior
        Agent behavior is predictable & obvious
   2) Chaotic system (Act, Sense, Respond - Novel)
        No system cause/effect between system & agent
        Agent behavior predictable w/ probability & statistics
   3) Complex system (Probe,Sense, Respond - Emergent)
        System ...
        Agent ...

Great Slides!

Col. John Byod

Gary Klein - Pre-Mortem

Wired Magazine - How to tell if your boss is a psychopath.

Book: Psychopath Test

------------------------------------------------------------------------------------------------------------------------------------

Wednesday:

    7:15am - 8:00am

    x:00pm - x:00pm

------------------------------------------------------------------------------------------------------------------------------------

The Primary purpose of this app was to demonstrate how to use the GWT concepts of Place/Activity/View with the RunAsync mechanism of GWT.
Thus allowing for splitting up the GWT generated JavaScript into a Core chunk and a number of load on demand (or Lazy Loaded) chunks.

It is my understanding that direct calls between Lazy Loaded chunks (and from the Core to the Lazy Loaded chunks) was not possible, but
that once a Lazy Loaded chunk had registered an implimention of a Core interface with the Core, then either the Core or any Lazy Loaded chunk's
code could call the interface whenever the registered interface can be retrieved.  This suggests that an optimal "fracture point" between the Core
and the Lazy Loaded code is the Activity.  This is exactly what the GWT Large Application best practices documentation suggests (specifically
bundling a Place's Activity/View pair behind a RunAsync method).  Obviously, this means that any Lazy Loaded Activity/View pair is NOT
available for direct synchronous calls.  Unfortunately, this implication at the end of the GWT Large Application best practices documentation
invalidates the author's earlier recomendation to have all the Views sychroniosly accessable in the ClientFactory.

The recogmended start up infrastructure code when using the Place/Activity/View approach is:

xxx

With GWT providing these classes:

xxx

And the App developer providing concrete implimentations of these classes/interfaces:

xxx

However, the ActivityMapper's getActivity( Place ) method expects to return an Activity sychronously (it does not utilize a Call Back
mechanism to support asynchronous creation of the Activity).