Resource registry control panel still unusable in Plone 5.0.2

[djay (Dylan Jay)]

@hvelarde

@vangheem talking seriously, I really don't know what to do about it; there are so many different/overlapping JS/CSS technologies around that I don't understand what's going on, and I can barely imagine how to fix the JS/CSS story.

you made a choice and pushed on that direction, and that's totally fine; the limitations of that choice are unveiling now; let's see how it evolve with the feedback of users beyond core developers.

my point is about underestimating risks, because obviously they existed from the very beginning; we all have to be open to criticism to not make the same mistakes in the future.

@hvelarde I think your idea of contributing writing up risks to PLIPs as they are written is a great hector and I fully support that.

[hvelarde]

thank you, @djay; I appreciate a lot you always do that on your feature requests.

[rodfersou (Rodrigo Ferreira de Souza)]

@datakurre is webpack compatible with Plone 5 requirejs implementation?

[datakurre (Asko Soukka)]

@rodfersou At least everything builds.

[rodfersou (Rodrigo Ferreira de Souza)]

nice! thanks

but I mean if I can import requirejs variables into webpack.

[datakurre (Asko Soukka)]

@rodfersou

but I mean if I can import requirejs variables into webpack.

What do you mean with requirejs variables?

[rodfersou (Rodrigo Ferreira de Souza)]

I mean modules and global variables from plone site written with requirejs

[datakurre (Asko Soukka)]

@rodfersou No and yes. Webpack works only for filesystem-development. All modules and variables work, but they must be defined in filesystem configuration (as I've done in plonetheme.webpack-baseline). Technically it would be possible to create similar extractor/generator to gruntfile-generator-script in CMFPlone. If I find time to create some, I definitely write about it. But at first, I collect more experience from the current implementation. Only a few sites deployed with that so far.