WAML - Web Application Markup Language

• About this group
• Forums

• Home
• Groups
• WAML - Web Application Markup Language
• Forums
• Lounge
• Updates

• 
  Evgenios Skitsanos    Group moderator

  The company name is only visible to registered members.

  Updates

  Hi there everyone,
  
  Sorry for being quiet for quite a while, was badly busy lately. Finally i've got married! Me and Cristina been waiting for this moment really long time. Finally we made it...
  
  Guess getting married brings something new to our life, even new ideas. Last few days i spent digging WAML, build 1.4 i've made long time ago. I've tried to compare server-based and browser-based XSLT transformation techniques and seems i managed to convince myself that the way i went in a first place with server side transformation is the right one.
  
  When i use browser-side transformation, i wont have all "extensions" and 100% functions that can be available under server-based transformation. Another problem is that XSL-T implementation varies from browser to browser and instead keeping client side nice and fast, i would load it with heavy "try-to-support-any-browser" crap.
  
  With server side, i don't have all this nightmare. Even more, i can run WAML applications under IIS and Apache Tomcat both, with no problem.
  
  And, by the way, i've solved problem of cross-browser JavaScript includes. Each time new resource added via Waml.Utils.includeJs, reference to it also stored to Waml.Application.modules.
  
  As you probably got noticed i've introduced additional "namespaces" in WAML, now i have:
  * Waml.Application
  * Waml.Browser
  * Waml.Utils
  * Waml.Events
  
  To work with events i took JSBroadcaster.js library by Timothy Groves. His library, very few lines of code, but allows to handle events in Flex/ActionScript way, with broadcasters and listeners.
  
  The rest details, docs and samples i will post a little bit later. If you have any questions or comments, - you are very welcome.
  
  Cheers,
  Evgenios.
  
  • 26 Aug 2007, 9:56 pm
  Evgenios Skitsanos wrote: > Hi there everyone, > > Sorry for being quiet for quite a while, was badly busy lately. > Finally i've got married! Me and Cristina been waiting for this > moment really long time. Finally we made it... > > Guess getting married brings something new to our life, even new > ideas. Last few days i spent digging WAML, build 1.4 i've made long > time ago. I've tried to compare server-based and browser-based XSLT > transformation techniques and seems i managed to convince myself that > the way i went in a first place with server side transformation is > the right one. > > When i use browser-side transformation, i wont have all "extensions" > and 100% functions that can be available under server-based > transformation. Another problem is that XSL-T implementation varies > from browser to browser and instead keeping client side nice and > fast, i would load it with heavy "try-to-support-any-browser" crap. > > With server side, i don't have all this nightmare. Even more, i can > run WAML applications under IIS and Apache Tomcat both, with no > problem. > > And, by the way, i've solved problem of cross-browser JavaScript > includes. Each time new resource added via Waml.Utils.includeJs, > reference to it also stored to Waml.Application.modules. > > As you probably got noticed i've introduced additional "namespaces" > in WAML, now i have: > * Waml.Application > * Waml.Browser > * Waml.Utils > * Waml.Events > > To work with events i took JSBroadcaster.js library by Timothy > Groves. His library, very few lines of code, but allows to handle > events in Flex/ActionScript way, with broadcasters and listeners. > > The rest details, docs and samples i will post a little bit later. If > you have any questions or comments, - you are very welcome. > > Cheers, > Evgenios.