The documentation system is being constructed while the code base is
debugged; so there's just not much to look at yet. It will be a tech
demo in it's own right, as a RESTful app which builds itself from the
lib with only 1 state (read-only), and it will a good amount of
samples.

I went heavy with the try/catch at this point mostly for debugging,
it's still in beta and those catches helped iron out the IE .. issues.
It's not tuned for performance yet, I'll be revisiting those before I
push out 1.0.0.

The error handling is really on a per case basis. Right now it's
silently logging, or dumping to a console if present. At this point,
it's pretty open ended without a clear goal of what the error
collection will do, beyond (eventually) providing a call stack of what
went wrong. Regarding the user agents, people need to know what
they're working with, and those ops are not cycle heavy.

el.clear is definitely not done, it needs to more granularity to
handle all cases (elements, properties, etc). I actually changed that
from instanceof just yesterday as I was doing sweeping changes,
however it wasn't ideal and most likely I'll be combining it with
method querying. The form case is at this point a regression that
hasn't been removed, because the current implementation is flawed, and
it will eventually be corrected over the coming weeks.

Thanks for the quick look! I know the state today looks, a little odd.
I had to remove some case specifics to nail the IE execution; which I
can correct going forward. _My main issue today is how I'm executing
the .init() for IE and everything that isn't Chrome/Safari/FF. I don't
like it, and it's not consistent firing_.

v1.0.0 won't be amazing per say, it'll just offer automatic REST/
HATEOAS with state changes. The following major release will be
fleshed out with a more feature complete fx class which should support
gaming, and business widgets for constructing admin dashboards (data
grids, etc); which is really the main focus of the lib.

What do you think of the observer/state machine coupling?

-- 
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