Dear all,

I'm trying out Willow which looks very interesting, however I'm struggling with simple examples ...��

I basically follow the blogs (here). I loaded Willow with Bootstrap and prepared the To-Do app as described in blog series. This works OK, however when I try to do something more, like

�� �� button := AsynchronicButtonWebView labeled: 'Now it''s time to click'.
�� �� button onTrigger executeOnClient: [ :canvas | canvas javascript alert: 'You just clicked a button' ]

the browser's javascript gives no response, and its console reports some errors:


It looks like problems with libraries. I checked the examples in WillowPlayground (which works OK, BTW), and found out that some basic things are way richer than described in the blogs. For instance, component supplier is not just

componentSupplierForApplication
�� �� ^ Bootstrap4ComponentSupplier online

as in the blog, but:

componentSupplierForApplication
�� �� ^ BootstrapComponentSupplier
�� �� �� �� withBootstrapLibrary: (self deploymentMode libraryFor: Bootstrap3MetadataLibrary) withoutOptionalTheme
�� �� �� �� selectLibrary: ((self deploymentMode libraryFor: BootstrapSelectLibrary) using: self language)
�� �� �� �� datepickerLibrary: ((self deploymentMode libraryFor: BootstrapDatepickerLibrary) using: self language)
�� �� �� �� typeaheadLibrary: (self deploymentMode libraryFor: BootstrapTypeaheadLibrary) new

My question is - is there a better documentation available for Willow? It's quite hard to study all bits and pieces from scratch.

The second question is about the suggested "architecture" or design pattern that should be followed when using Willow. The blog mixes Seaside components (e.g. #PendingTask as a subclass of WAPainter) that engages Seaside rendering elements (e.g. ��html paragraph:) on one hand, with the components supplier's components (e.g. singleLineTextField ...) implemented directly in the Willow Application on the other hand. This probably isn't the way things should be done :-)

Best wishes,
Tomaz