Hi Frank--
> I see absolutely no sense in this approach for real-world end-user
> applications...
Smalltalk in a web browser (or NodeJS) makes just as much sense as
any other JS framework, like React, Angular, etc. BitBLT, Morphic, and
even the Smalltalk process scheduler are all entirely optional; since
there is full JavaScript connectivity, one can manipulate the DOM (or
shadow DOM) just like any other framework, using JS functions and
promises (and Smalltalk objects which can stand in for those things).
> ...especially if their sources MUST be closely connected with existing
> Smalltalk code, which does not run in the client like all the
> data-driven model definitions etc that I already have
There is no such requirement.
> the Morph UI is out of any question related to what end-users expect
> (pardon, but end-users would regard this as a bad joke)
One need not use Morphic. One can use any JS code one likes.
> the responsivness of such a solution in the browser must always be far
> slower than any "normal" browser UI
That's not true. For example, at the moment my UI is Mozilla's
A-Frame 3D virtual reality framework, at 90 frames per second.
> and it's impossible to port my >10.000 framwork and application
> classes to Squeak.
Caffeine can use Pharo, Squeak, or Cuis.
> Should my view be completely wrong, please let me know.
It actually is. :)
Best of luck with your project!
-C
--
Craig Latta
Black Page Digital
Amsterdam :: San Francisco
[email protected]
+31 6 2757 7177 (SMS ok)
+ 1 415 287 3547 (no SMS)
