Fixed widget iterator going out of range with ui.Tree

[Nican]

Hey!

I would like to thank you for porting over the awesomeness of GWT to Dart, I was really can not get used to how limited WebUI is.

One question that I have is, did you really have to port the exact event system from GWT? One thing that I hated about GWT is the fact you had 3 different classes for every event; Would it not just be easier to use Dart's Stream feature?

[akserg]

Hi Nican.
Thank you very much.
About you question regarding event mechanism - we planning make changes in
DWT event system. Please, have a look our new community Dart Web
Toolkithttps://plus.google.com/u/0/communities/100328499012805124876on
G+.

On 6 May 2013 03:36, Nican notifications@github.com wrote:

Hey!

I would like to thank you for porting over the awesomeness of GWT to Dart,
I was really can not get used to how limited WebUI is.

One question that I have is, did you really have to port the exact event
system from GWT? One thing that I hated about GWT is the fact you had 3
different classes for every event; Would it not just be easier to use

Dart's Stream feature?

You can merge this Pull Request by running

git pull https://github.com/Nican/dart_web_toolkit master

Or view, comment on, or merge it at:

#87
Commit Summary

• Fixed widget iterator going out of range with ui.Tree

File Changes

• M lib/src/ui/widget_iterators.darthttps://github.com/Fixed widget iterator going out of range with ui.Tree #87/files#diff-0(2)

Patch Links:

• https://github.com/akserg/dart_web_toolkit/pull/87.patch
• https://github.com/akserg/dart_web_toolkit/pull/87.diff