Hi,
The only thing I don't really like is that we need fuel-web code to build
plugin. But we have can do nothing with it, as typical UI plugin by design
is tightly coupled with the core. If plugin want to reuse core libraries,
utils, controls then it has to declare them as dependencies and if ther
On 12/15/2014 02:26 PM, Anton Zemlyanov wrote:
The building of the UI plugin has several things I do not like
1) I need to extract the UI part of the plugin and copy/symlink it to
fuel-web
This is required, the UI part should live somewhere in statics/js. This
directory is served by nginx a
The building of the UI plugin has several things I do not like
1) I need to extract the UI part of the plugin and copy/symlink it to
fuel-web
2) I have to run grunt build on the whole fuel-web
3) I have to copy files back to original location to pack them
4) I cannot easily switch between developm
First of all, compiling of statics shouldn't be a required step. No one
does this during development.
For production-ready plugins, the compiled files should already be
included in the GitHub repos and installation of plugin should just be a
matter of downloading it. The API should then take car
My experience with building Fuel plugins with UI part is following. To
build a ui-less plugin, it takes 3 seconds and those commands:
git clone https://github.com/AlgoTrader/test-plugin.git
cd ./test-plugin
fpb --build ./
When UI added, build start to look like this and takes many minutes:
git c
