extjs4.1

ExtJS 4 select multiple CheckColumn checkboxes with checkbox header

淺唱寂寞╮ 提交于 2019-11-30 09:52:54
I have a column of checkcolumn type to enable toggling boolean values. I'd like to be able to toggle all rows for that value at once. Ideally, I'd be able to add a checkbox to the checkcolumn header and listen for changes. Is that possible? I'd like to note that I am not looking for a checkboxmodel to select rows. I have created an updated version of the Ext.ux.CheckColumn for this, just include this code after the extjs code is included: Ext.define('Ext.ux.CheckColumn', { extend: 'Ext.grid.column.Column', alias: 'widget.checkcolumn', disableColumn: false, disableFunction: null,

ExtJs4.1目录结构介绍和使用说明

自古美人都是妖i 提交于 2019-11-29 13:33:44
一、在做ExtJs开发之前首先要到网站上下载ExtJs的开发包,我用的最新版本是4.1.1。此版本相对于之前的版本目录结构发生了一些变化,没有了adapter目录, 目录结构如下 文件/文件夹名的作用: build:文件夹下有一个sdk.jsb3文件,这个文件用于eclipse中spket插件,可以实现ExtJs的代码提示功能; builds:压缩后的ExtJS代码,体积更小,更快; docs:开发文档; examples:官方演示示例; locale:多国语言资源文件; pkgs:ExtJS各部分功能的打包文件; resource:ExtJS所需要的CSS与图片文件; src:未压缩的源代码目录; bootstarp.js:ExtJS库引导文件,可通过参数自动切换ext-all.js与ext-all-debug.js; ext-all.js:ExtJS核心库,需要引用; ext-all-debug.js:ExtJS核心库的调试版,调试时使用。 注:EXTJS文件的区别: ext-all.js:包含所有的EXTJS框架文件,已经混淆 ext-all-debug.js:包含所有的EXTJS框架文件,没有混淆 ext-all-dev.js:包含所有的EXTJS框架文件,没有混淆,且包含调试信息 ext.js:仅包含能让EXTJS运行的最小集合,已经混淆 ext-debug.js

understanding “Layout run failure” error logging

不问归期 提交于 2019-11-28 23:36:53
I am doing some charting work and got a single line message "Layout run failure" when nothing was being created on the chart. Looking into this I found that I have to add some additional script files to generate the log files as covered here : Layout Failures As result of the design for the layout engine in 4.1, it is possible for improper configuration (or a bug) to cause a layout run to fail to complete all of its calculations. When this occurs, the layout simply stops and the partial results that have been flushed to the DOM are all that is visible. In some cases, the layout may be 99%

Store do something after sync with autoSync enabled

▼魔方 西西 提交于 2019-11-28 22:07:33
I'm trying to detect and remove those fields that after a sync are still on the store but are not added to the database (success: false). Then, return an error message to the user (with some error codes). However I can only see a "beforesync" event in store documentation. Are there any possibility to do such a thing? I'm trying with "update" events but they are called after syncing only if the sync is successfull (otherwise they are called only before sync). I can't really find an event that is fired after sync. Any solution for this? Notice that I'm using autoSync, that's why I can't hook to

Store do something after sync with autoSync enabled

落花浮王杯 提交于 2019-11-27 21:04:37
问题 I'm trying to detect and remove those fields that after a sync are still on the store but are not added to the database (success: false). Then, return an error message to the user (with some error codes). However I can only see a "beforesync" event in store documentation. Are there any possibility to do such a thing? I'm trying with "update" events but they are called after syncing only if the sync is successfull (otherwise they are called only before sync). I can't really find an event that

understanding “Layout run failure” error logging

孤者浪人 提交于 2019-11-27 14:52:05
问题 I am doing some charting work and got a single line message "Layout run failure" when nothing was being created on the chart. Looking into this I found that I have to add some additional script files to generate the log files as covered here: Layout Failures As result of the design for the layout engine in 4.1, it is possible for improper configuration (or a bug) to cause a layout run to fail to complete all of its calculations. When this occurs, the layout simply stops and the partial

to initComponent() or not to initComponent()

扶醉桌前 提交于 2019-11-27 06:10:37
I struggle when building an app in ExtJS 4, and part of that is confusion on when to configure something in initComponent() and when not to... For example, in Sencha's own MVC Application Architecture doc, when first creating the grid view, they defined the inline store in the initComponent() method. (See "Defining a View" section) Further down, when they factored out the store into a separate class, they moved the definition outside of initComponent(). There is a helpful comment that draws attention to this fact, but there is no explanation. (See Creating a Model and Store section) I guess

up() and down() versus Ext.getCmp()

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-27 04:13:43
I'm very confused which one I need to use for grep object between up() down() and Ext.getCmp(ID). For me, it is easier that define ID to object and retrieve the object by Ext.getCmp('ID') and the code looks more clean. For example: console.log(this.up('panel').up('panel').down('grid')); console.log(Ext.getCmp('myPanel')); which one is better for performance? dbrin There are severe gotchas with using IDs and getCmp to find your components. The primary issue is that you can not reuse the component safely because in most cases the markup will create HTML elements with duplicate IDs, which is

to initComponent() or not to initComponent()

拈花ヽ惹草 提交于 2019-11-26 11:54:08
问题 I struggle when building an app in ExtJS 4, and part of that is confusion on when to configure something in initComponent() and when not to... For example, in Sencha\'s own MVC Application Architecture doc, when first creating the grid view, they defined the inline store in the initComponent() method. (See \"Defining a View\" section) Further down, when they factored out the store into a separate class, they moved the definition outside of initComponent(). There is a helpful comment that

Best practice for overriding classes / properties in ExtJS?

北战南征 提交于 2019-11-26 08:59:17
问题 I have an Ext.form.field.Text and I want to override the setValue function. What is the recommended way to override this class functionality in ExtJS? Ext.override? 回答1: For clarification: By real class modification I mean a intended permanent modification/extension of a class , which should always be done by extending a class. But it is not a temporary solution for just a specific problem (bug-fix, etc.) . You have at least four options how to override members of (Ext) Classes prototype I