The next build has now morphed into a new minor release, due to some
significant changes in the way that the framework handles/dispatches control
events.  This was a first, and necessary, step towards opening up the
framework for 3rd party components, and I needed to get it done ASAP.  I
just finished up the last bit of changes for it yesterday, and things are
looking really good.  The new event manager in the framework allows one to
code controls and have all of the browser DOM event management automatically
handled for the controls without binding event handlers to every control's
DOM element(s).  This is especially important for ironing out some
significant differences in the focus model under IE vs.
FF/Chrome/Safari/Opera, as well as making key and mouse handling much easier
to deal with.  It also decreases the memory consumption and load time even
further, and allowed me to chop out some fairly large sections of
(very-confusing) code.  Finally, it takes the framework one step closer to
universal drag/drop and gives controls the ability to capture the mouse in
the same way across all browsers.

There's a lot of internal "plumbing" like this that will be necessary over
the next couple of months, and all of it is laying the groundwork for 3rd
party controls/components in the IDE.

I'm now working on finishing up the rest of the small improvements and bug
fixes now, and hopefully I'll have something ready by Monday of next week.

Thanks for your patience,

Tim Young
Elevate Software
www.elevatesoft.com

On 03/04/13 22:55, Tim Young [Elevate Software] wrote:
> The next build has now morphed into a new minor release...
>
> I'm now working on finishing up the rest of the small improvements and
> bug fixes now, and hopefully I'll have something ready by Monday of next
> week.

Tim, this update sounds really good. Improvements in efficiency and
performance are always welcome ... looking forward to it.

Now that it has become release 1.02 will it also include those items on
the current roadmap (e.g. canvas support, notebook and menu control, etc)?

--
Rick

"Tim Young [Elevate Software]" wrote:

<< The next build has now morphed into a new minor release...>>

I've been hanging out for the next build.  This sounds like it will be worth the wait.

Steve

Looking forward to it. I shall be revamping my web-apps with it, and then trying a
PhoneGap type system to see if I can embed them. I realise it isn't officially
supported yet, but if anyone has tips on such please let me know. Our existing
jQuery Mobile app is being a complete pain with bits broken, and being able to use
EWB instead would make it so much better!

/Matthew Jones/

Sounds very "tasty" Tim.

Thank you for the update.  I'm looking forward to this, and many more, releases!  Long live EWB!!!

Walter

Rick,

<< Now that it has become release 1.02 will it also include those items on
the current roadmap (e.g. canvas support, notebook and menu control, etc)?
>>

The canvas support will be finished up in the WebDOM unit, but the other
components will get bumped forward to the next minor release.  1.02 will
also include an option to specify what level of HTML5 support you want, and
will output the proper meta tags so that the IE version will track properly
with this setting.  Right now EWB tags everything as IE8, which prevents
proper use of the canvas tags and other IE9+ supported tags.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< Our existing jQuery Mobile app is being a complete pain with bits broken,
and being able to use EWB instead would make it so much better! >>

Just curious: what bits are broken ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

We have a "toolbar" that is supposed to be fixed to the bottom. On the iPhone, the
bar jumps to the wrong position. Trying other versions just breaks different things
(like it works on iPhone, but not Android).
https://github.com/jquery/jquery-mobile/issues/4113 has the details - it has been
fixed a few times, and broken again. Due to it being separately packaged, we have
to decide what to do, or learn more, or maybe just wait until EWB. Usual horrible
dilemma!

/Matthew Jones/

Will command line support be included? Only it just struck me that I can do
different modes for different targets just by changing the source a bit (sort of
conditional compile but run-time determined) and rebuilding. That would be quite
handy.

/Matthew Jones/