For ext 5 developpment, we will include in the html headers every javascript ressources
incrementally, so we can bypass the "make install" step.
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
Provided you symlink the manager5 directory to your git repository,
this will allow to test javascript changes by simply reloading
the page, without calling "make install" in between.
For instance, if you have your pve-manager code in $HOME/pve/pve-manager,
you can do
ln -s $HOME/pve/pve-manager/www/manager5 /usr/share/pve-manager/manager5
and you can serve javascript files directly from your copy of the source repo
curl -k -s -o /dev/null -w "%{http_code}" https://localhost:8006/pve2/manager5/Utils.js && printf "\n"
200
Not that at the momment this is only meant for Ext 5 development
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
Developement of the ext5 version of the pve-manager will take place
in the www/management5 directory of the git repo.
We start the initial import with Utils.js, who contains variables and
static functions used by all other components.
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
Calling the pveproxy with https://localhost:8006/?ext5=1 will
load the web ui with the extjs 5 js libs.
Please note that at the momment the workspace does not load with
extjs 5.
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
The use of the HTML doctype is recommended for Ext4 and Ext5, and is supported by all
post 2008 browsers.
Basically it tells the browser to interpret the HTML according to standards, and not
according to what IE6 might have thought of it.
This will also drop support for IE6 and IE7, which are anyway not supported by ext5.
The HTML doctype will make all browsers switch to their standard
compliant mode, hence we don't need anymore to toggle this specifically for IE.
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
This commit only installs the required javascript / css files for ext js 5.1
in /usr/share/pve-manager/ext5, but does not use it by default, as we have to sort out
the upgrade issues between 4.0 and 5.1 before.
Signed-off-by: Emmanuel Kasper <e.kasper@proxmox.com>
avoid to init the rrd with default timeframe,
then reload with timefrom state manager
this avoid to reload twice the rrds
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
