IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
if we use a component with cbind in a static declaration,
we do not want to traverse the 'config' property, as this can lead
to properties of base classes which produce errors on copying
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we renamed them in the helpButton, we also have to rename them here
this prevented the help button to show up in the vm/ct creation wizard
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
allow to access sub elements of configuration items for binding.
E.g., if the following configuration is present:
foo: {
bar: true
}
one could do:
xtype: 'displayfield',
cbind {
value: '{foo.bar}'
}
[...]
This mirrors the abillity of ExtJS's 'bind', which can do this also.
Simple implementation mirroring the surrounding code.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
since the Task is in the widget-toolkit, passing
a renderer/list a few levels of components down is not nice
and there are not *that* many strings in the task_desc_table,
we put it here, so that either pve and pmg can use them
port commit
851c032d69ad5ae23725dd1add9e4084ebc12650
from pve-manager
commit message:
ComboBoxes provided by UI frameworks normally show their selection
possibilities once focused, ExtJS does this too but not on editable
(and thus filterable) input fields. Add a logic which allows this too
and streamlines the behavior of ComboGrid/Box like components.
To avoid a glitch, where clicking the "picker trigger" (the down
arrow which normally toggles the selection picker) would first focus
the element - thus expanding it - and only then causing a toggle
which collapses it again, we overwrite the 'Ext.form.trigger.Trigger'
onMouseDown so that we can skip a expansion on this event.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
port commit
bff876ecb5f3388b7d65c491680b9a40574e4744
from pve-manager
commit message:
This allows child classes to use another default, the initialConfig
didn't allowed that.
This is also the ExtJS like way to set defaults.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
this is a port of the change for the Edit window from
pve-manager commit:
ff740ccbeed1e7e2131b14c9ce50f300f24201f6
which passes the given defaults to the items
this is a workaround for scrolling in toolbars, etc. in firefox with
the mouse.
while the result is not very "pretty", it maintains the old behaviour
for all other browsers and makes it work in firefox
we may drop this when we update to a new extjs release
commit 484bf3f29e58d0f96c65e6dca6b5dd95eaea180c from pve-manager
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
adds a workaround, so that we restore the scroll position when we
restore the focus. Fixies an annoying issue where, if a user had an
ellemtn selected, scrolled down and then a store refresh re-rendered
the view it was scrolled back to the selected item and the user lost
his scrolling position.
Add also the 'jumpToFocus' flag to allow enabling the old behaviour
commit e6f2a94f4fff3c125e8406a21d8d6159aca1421e from pve-manager
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
by default, extjs submits the language dependent decimal separator,
e.g., ',' (comma) for german and '.' (dot) for english.
We always want the dot.
commit 5c660b6d1302a5fbb3dcf477cf8b5adc9f798530 from pve-manager
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
The parent method does this already in ExtJS 6
commit d19ffc1bb078e42a042c5c73797d713aa9cf9bcc from pve-manager
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
pve-doc-generator used pveOnlineHelp as variable name while the
widget toolkit expects proxmoxOnlineHelp, allow both for now.
As its not quite clear when the switch to the widget toolkit happens
this is more flexible than changing the generator and adding a
versioned build dependency in pve-manager for it.
We normally do not bump pve-docs during releases either.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
CC: Dominik Csapak <d.csapak@proxmox.com>
commit acc9bf4752972ffd79af1c78510fcce24c2db959 (Close#1268: Show
migration start server and migration end server) introduced the
possibility to display additional information in the TaskViewer
window title. This change happened after the widget toolkit formed
and seems reasonable to have here, thus port it over.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
since all modern browsers can properly handle multiple
xmlhttprequests, we do not need to serialize them ourselves, but
leave it to the browser
this fixes an issue wehre a canceled request of an updatestore
blocks all other updatestores until refresh
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this mirrors the changes from Emmanuel in commit
9af71828d42c67b13144b568eee828b215054399
of pve-manager
where he renamed the 'create' parameter of the Edit Window to
isCreate, to avoid countless jslint errors regarding type confusion
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
