Split repo into modules?

[ChALkeR]

Git submodules? npm deps? Not sure yet. I'm not even sure that this has to be done atm.

[ChALkeR]

npm deps looks like a way to go, with splitting these modules:

• qmlweb-parser
• qmlweb-compiler
• qmlweb-runtime
• qmlweb-components
• qmlweb, which just unites them all into one bundle

It should be noted that bare qmlweb-runtime will not be able to load qml files without qmlweb-parser and qmlweb-compiler present.

/cc @akreuzkamp

qmlweb-gulp will depend only on the qmlweb-parser or on qmlweb-parser and qmlweb-compiler — depending on what the target would be — parsed or compiled files. Not sure yet.

[henrikrudstrom]

I think that would be a good idea to do it as part of the post merge cleanup. think it will make the project more manageable and easier to understand for newcomers (like me).

what exactly does the 'qmlweb-compiler' do? and maybe what about combining 'qmlweb-parser' and 'qmlweb-compiler' into one package for simplicitys sake, as they separate out the part that is useful both on server and client side?

Hmm, is there no way to combine submodules and npm? Submodules are much more convenient for developing, but perhaps not so ideal for users of the package.

[henrikrudstrom]

How about we make the parser and parts of the runtime domain independent so that it doesnt contain any html specific code. I think the QML engine has potential to be reused in other context (3d graphics, svg, ...) something like this:

• qml-parser
• qtdeclarative.js (implement Qt Declarative Module)
• qmlweb-runtime --- html specific
• qmlweb-qtquick --- html specific

[igosoft]

Indeed it's good idea.

[ChALkeR]

We probably should keep the core modules in the same repo (this one), but split the package into separate smaller files that are loaded only when imported to reduce the footprint.