lebobitz.wordpress.com
Synchronizing WatiN and Ajax with jQuery | Lebobitz
https://lebobitz.wordpress.com/2011/03/06/synchronizing-watin-and-ajax-with-jquery
Musings of a .Net developer. Synchronizing WatiN and Ajax with jQuery. Synchronizing WatiN and Ajax with jQuery. March 6, 2011. We maintain hundreds of test cases against our web application. We chain team builds so that when the app build finishes building successfully, it kicks off another build which ships and runs mstest against the WatiN solution. There’s a dedicated build agent running in interactive mode which runs the tests. I’ll cover this setup in a future post. Test] public void SearchForWatiN...
claudiomeschini.blogspot.com
Dominando el Dominio?: agosto 2007
http://claudiomeschini.blogspot.com/2007_08_01_archive.html
31 de agosto de 2007. Hoy, luego de asistir a una charla en el "MUG". Dictada por el "maestro" Angel. Sobre generación de código y su excelente "ajgenesis",. Por otro lado, habitualmente para generar un template en alguna herrmienta de generación de código lo que hago es reemplazar las partes "variables" de un codigo en el lenguaje original que estoy trabajando y lo reemplazo por los token que me da el generador. O sea algo así:. Se transforma en "Edit ${NombreEntidad}. Lo ideal sería entonces que:.
robokit.info
Robokit Resource Site
http://www.robokit.info/History.html
The History of Robokit - Part 1. Atari Robokit was designed by Personal Robots Ltd (PRL) in the late 1980s and licensed to Atari Corp. PRL was formed in January 1985 by Julian Allason and me - as Chairman and Managing Director respectively. Earliest visualisations of the product - working to my brief - including the presentation box (this was before we had alighted on the name Robokit):. It was largely on the strength of Doug’s superb illustrations (we had no working prototype at that point) that J...
en.wikipedia.org
Naked objects - Wikipedia, the free encyclopedia
https://en.wikipedia.org/wiki/Naked_objects
From Wikipedia, the free encyclopedia. Is an architectural pattern. Used in software engineering. Relationship to other ideas. The naked objects pattern is defined by three principles:. Should be encapsulated onto the domain objects. This principle is not unique to naked objects: it is just a strong commitment to encapsulation. Should be a direct representation of the domain objects, with all user actions explicitly consist in the creating or the retrieving of domain objects and/or invoking methods.
