[Pas2js] Cases

[Michael Van Canneyt]

> My questions: how lazarus core see the pas2js project? what is the path
> that
> this project will follow a component (ide plugin), or a lcl interface
> (Gtk,
> Win, Web)? the compiler (pas2js) will be integrated into the compiler
> (FPC)?
> are many doubts!

Ideally, pas2js is just another FPC platform and a lazarus LCL Widgetset.
The problem is that then the LCL must be compilable by pas2js.
This is not yet the case.

A lazarus LCL widgetset is based on a 'native' widgetset (Qt, Gtk etc)
That means  that first these native widgets must be created for Web.
Both your and warleyalex efforts can be used as a starting point, later
the LCL integration can be done on top of these widgets.

> Which approaches are better mine or warleyalex, neither of the 2 are
> private
> ... the best approach would be a new one from the community.

I didn't take a detailed look yet at the architecture of both approaches,
so I cannot yet comment on this in a detailed manner:
After my superficial look at the code, warleyalex' approach with the J*
units seems OK, but I still need to compare it with your files.

So, from my perspective: both your and his code can serve as a basis for a
set of web widgets, on which a LCL widgetset can be built.

At the same time, there is nothing stopping you from using the custom
designer approach in the IDE to design a HTML form today. or as an
alternative, the embedded chromium approach could be used to design the
form.

There are many possible roads: which one is the best is still up for
discussion, I think.

Michael.