SOFEA/TSA application developers are going to face a new set of
challenges. We should have some ideas on how to address them.
I'd like to start a discussion on best practices for the engineering
issues developers will face as they push more logic onto the client.
I'm hoping that by addressing these concerns with practical and tried
solutions, we'll be able to make SOFEA/TSA a little less scary.
The following are a few issues that I've come up with. Please share
your experience and the techniques you use.
DOM Building - How do you build HTML?
Event Handling - How do you organize event handling, and attaching
event handlers?
Ajax/Service - Do you have a layer that handles data transport? What
does that look like?
File Structure - Do you have a standard file structure? What does it
look like?
Programming Paradigms & Architectural Patterns - Does Aspect Oriented
Programming, Functional Programming, MVC, SOA have a home in your
application? Do you use simulated classes or stick with prototype
based inheritance? What layers do you use to abstract application
technologies. Do you use OpenAjax to publish/subscribe?
Testing - What do you use to test?
Compression / Build - How you you combine and load JS for faster
download.
Development Methods - Waterfall, Agile, V, Story based development,
Requirement based development.
Logging - How do you log data from the client. Do you report errors?
Tools/Libraries - Which tools and libraries do you use? Obviously
Firebug, but is there something good for IE?
> justin...@gmail.com <mailto:justin...@gmail.com>
> AOL: jusbarmey
>
> >
> <http://www.xucia.com/?mode=html&noscript=true>. In this case
> all the HTML is fully rendered. The templating engine I used on these
> sites is abandoned technology, but I think it is a similar paradigm to
> the templating engines like PURE, JMVC, and Dojo's DTL engine, which
> could probably all leverage this.
> Kris
>
> Justin Meyer wrote:
> > No, I haven't. Thanks for sharing. I'll read up about it and share
> > it with the group.
> >
> > On Sat, Oct 25, 2008 at 8:14 AM, Kris Zyp <kri...@gmail.com
> <mailto:kri...@gmail.com>
> > <mailto:kri...@gmail.com <mailto:kri...@gmail.com>>> wrote:
> >
> >
> >
> > > But, I've just recently (1 hour ago) added what could be
> it's best
> > > features - command line testing. Using a beefed up version of
> > Resig's
> > > simulated FF2 environment for Rhino, any javascriptmvc
> application
> > > will run its unit tests automatically in a command line.
> > Have you tried HTMLUnit? It is built on Rhino and provides
> pretty
> > extensive browser environment emulation, and I think even
> has decent
> > support for emulating the different browsers out there.
> > Kris
> >
> >
> >
> >
> >
> > --
> > Justin Meyer
> >
> > Jupiter IT Solutions
> > 847-924-6039
> > justin...@gmail.com <mailto:justin...@gmail.com>
> <mailto:justin...@gmail.com <mailto:justin...@gmail.com>>
> > AOL: jusbarmey
> >
> > >
>
>
>
>
>
> --
> Justin Meyer
>
> Jupiter IT Solutions
> 847-924-6039
> justin...@gmail.com <mailto:justin...@gmail.com>
> AOL: jusbarmey
>
> >