I think mockup-extra objective is to provide interesting/generic patterns
that might be useful for add-ons developers, but not to gather all the
bundle definitions for all the packages that need a bundle.
So yes I agree, the way to go is to make sure each package needing a
specific bundle can compi
On Mon, 2014-11-24 at 09:47 +0100, Eric Bréhault wrote:
> Thank you for the advice Nathan , I will try that.
>
> So, does it mean that any package that will need its own bundle will
> define it in the mockup package so it can be compiled and then copied
> into the package itself ?
It should be po
On Sun, 2014-11-23 at 21:30 -0600, Nathan Van Gheem wrote:
> Nevertheless, something is still missing: I need
> mockup-patterns-filemanager and mockup-patterns-thememapper to
> be loaded.
> For dev purpose, I have include them manually in plone.js, but
> of
Thank you for the advice Nathan , I will try that.
So, does it mean that any package that will need its own bundle will define
it in the mockup package so it can be compiled and then copied into the
package itself ?
It would be probably saner that each package contains its bundle
definition, and I
On Sun, Nov 23, 2014 at 11:10 AM, Eric Bréhault wrote:
> Hello,
>
> The existing theming editor is totally broken in Plone 5.
> So, during the Ploneconf sprint, I started working on migrating it to the
> appropriate mockup patterns, and fixing the corresponding backend views.
>
> It is now workin
Hello,
The existing theming editor is totally broken in Plone 5.
So, during the Ploneconf sprint, I started working on migrating it to the
appropriate mockup patterns, and fixing the corresponding backend views.
It is now working fine, I have made several pull requests containing my
changes:
http
