I was hoping to see a demo/documentation and the homepage seems a bit
scarce.

After a 10-second glance at the code my first question is why are
try...catch blocks covering so much? This construct has a significant
performance penalty and much of the code contained in the block will
not throw an exception. It would be better if it was more fine tuned
around specific errors. Along these same lines, how do you envision
the consumer of your library handling failure?

Why are you sniffing the user agent?

el.clear seems bound to fail as you're using typeof to determine if
the argument is an "object". Since this can be any arbitrary object,
obj.fire can throw. instanceof would be the best choice but method
querying could also work.  When would typeof obj ever equal "form"?

Once again, this is just a quick glance

On Jan 2, 7:40 am, jmulligan <[email protected]> wrote:
> Hi,
>
> I'm currently working on a library that focuses on REST/HATEOAS for
> GUIs built purely on JS/CSS/Web Services; and that implies tying a
> state machine to an observer. I did this with the observer.replace()
> method and a hook in client.response() that looks for a user defined
> header, ideally set in the 'ready' event, and of course you can also
> trigger a state change based on any event without a request. This
> requires all of the listeners created on ready, or at least before the
> initial URI request is made.
>
> The beta is available on github athttp://github.com/avoidwork/abaaso
> ... I'm hoping to have v1.0.0 out before the end of February, which
> will have the core code to build business widgets on top (like ExtJS,
> without the bloat). I'm planning the usual gambit of widgets/fx, with
> a focus on physics in the near future.
>
> I probably have a few regressions in the code right now, so consider
> the broader picture if you're going to give me a critique.
>
> Thanks!

-- 
To view archived discussions from the original JSMentors Mailman list: 
http://www.mail-archive.com/[email protected]/

To search via a non-Google archive, visit here: 
http://www.mail-archive.com/[email protected]/

To unsubscribe from this group, send email to
[email protected]

Reply via email to