Kilon wrote:

would it not be better to have the html / css and js code outside the image ? so instead to load files instead of return strings ?

Only for the things that are really static. All other parts should be in the image, and be generated, just like the seaside canvas does for html. Working with files just kills my productivity, especially if I have to switch out of Pharo. For deployment, you can generate files, but then you don't serve them with Pharo. Of course, if you start out with files like in this example, it takes some time to refactor towards a sensible model. Stephan