-
5 May 2011 12:55 AM #91
-
5 May 2011 1:05 AM #92
-
6 May 2011 1:26 AM #93
Hi Brian,
i got the two previous mentioned bugs
- [DEPRECATED][4.0][Ext.form.field.ComboBox] loadingText (config): Use listConfig.loadingText instead.
- [DEPRECATED][4.0][Ext.form.field.ComboBox] shadow (config): Use listConfig.shadow instead.
These are not errors from my code, they come if you include another language (in this case ext-lang-de.js):
Maybe this errors/warning can be excluded from error output (or maybe the lang files have to be changed?).Code:if(Ext.form.field.ComboBox){ Ext.apply(Ext.form.field.ComboBox.prototype, { loadingText : "Lade Daten ...", valueNotFoundText : undefined }); }
I do not know hwo to find the second shadow error?
Cheers
Holger
-
6 May 2011 3:40 AM #94
Managed Iframe
Managed Iframe
http://www.sencha.com/learn/Extension:ManagedIframe
Is there a workarround or a new feature do operate with IFrames? The MIf does not match the Ext 4 Class System and i don't want to rewrite this Plugin ;-)
In spite of using the compat.js Ext 4/MIF throws an Exception:
cls.override is not a function
[IMG]chrome://firebug/content/blank.gif[/IMG] return cls.override(overrides);
ext-all-debug.js (Line 165)
-
6 May 2011 5:31 AM #95
First of all thank you for the migration guide! It got me a long way, but I am now stuck with a proxy problem that I can't seem to find a solution to...
I get the following error in firebug:
msg: "You are using a ServerProxy but have not supplied it with a url."
sourceClass: "Ext.data.proxy.Server"
sourceMethod: "buildUrl"
We use a lot of Ext.Ajax.request calls, are they the problem? And what can I do to fix the problem?
-
6 May 2011 6:47 AM #96
This is clear but also deprecate.
I think he is talking about the ref-attribute within the configuration of a component to build a reference path for nested objects. Not the Ext.ref to setup a xtype
I'm missing it, too:
This one: http://dev.sencha.com/deploy/ext-3.3....Component-ref
-
6 May 2011 11:56 AM #97
Help with tree loader
Help with tree loader
In our Extjs 3 application, we have a tree loader function that looks like this:
In our TreePanel config, we pass use this treeLoader function to create the "loader" config option:Code:treeLoader: function(node, callback, passNode) { // do ajax call... MG.metadata.getExplorerFolder({ parentFolder: node, loaderCallback: callback, // on success, pass ajax results to loader callback success: function(response) { var result = MG.getMethodResult(response); if (MG.methodSucceeded(result)) callback(result.payload, response); } });
That works great, and I would like to the same/similar in extjs4...but I've been messing around for over a day now with the TreeStore and various proxy types and settings with no luck. Is there a way to accomplish this using a similar technique in 4, without having to rework my server side?Code:loader: new Ext.tree.TreeLoader({ directFn: this.treeLoader })
Thanks
-
6 May 2011 12:21 PM #98
You can use this
Code:Ext.override(Ext.AbstractComponent, { initRef: function() { if(this.ref && !this.refOwner){ var levels = this.ref.split('/'), last = levels.length, i = 0, t = this; while(t && i < last){ t = t.ownerCt; ++i; } if(t){ t[this.refName = levels[--i]] = this; this.refOwner = t; } } }, recursiveInitRef: function() { this.initRef(); if (Ext.isDefined(this.items)) { Ext.each(this.items.items, function(item){ item.recursiveInitRef(); }, this); } if (Ext.isFunction(this.child)) { var tbar = this.child('*[dock="top"]'); if (tbar) { tbar.recursiveInitRef(); } var bbar = this.child('*[dock="bottom"]'); if (bbar) { bbar.recursiveInitRef(); } } }, removeRef: function() { if (this.refOwner && this.refName) { delete this.refOwner[this.refName]; delete this.refOwner; } }, onAdded: function(container, pos) { this.ownerCt = container; this.recursiveInitRef(); this.fireEvent('added', this, container, pos); }, onRemoved: function() { this.removeRef(); var me = this; me.fireEvent('removed', me, me.ownerCt); delete me.ownerCt; } });
-
6 May 2011 12:32 PM #99
Ext.reg is not a function??
Ext.reg is not a function??
I am quite surprised that Ext.reg is no longer a function. Especially considering that Ext.preg still is
The docs note that Ext.preg is a shortcut to Ext.PluginManager.registerType so I tried to search the docs for "registerType" on the chance that that is also the name of the function aliased to by the (former) Ext.reg, albeit possibly Ext.Component.registerType?!
(As it turns out, looking into Ext3.3, it's "Ext.ComponentMgr.registerType", but the concern below still holds....)
Anyway, using the new documentation search system, you can't even find the known-to-exist Ext.PluginManager.registerType; you type in "registerT" and all your results disappear.
-
7 May 2011 11:21 AM #100
Ed Spencer promised to include a desktop example in ExtJS 4.0. And yes he did. Very nice. Now I tried to migrate the Desktop from ExtJS 3.3.1 into ExtJS 4.0. In the ExtJS 4.0 HTML example 1 file is used that combines all *.js files. This file is minified. Not all javascript files in the classes.js are present as separate unminified files. Now its impossible for me to migrate the desktop.
Please mister Spencer put the missing unminified files or the unminified classes.js in the example Desktop.
Thanks
You found a bug! We've classified it as
a bug in our system.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
Similar Threads
-
Migration to 3.0
By tillda in forum Community DiscussionReplies: 5Last Post: 17 Aug 2009, 7:19 AM -
Migration to 2.0
By scaswell1 in forum Ext GWT: Help & Discussion (1.x)Replies: 1Last Post: 7 Jul 2009, 9:56 PM -
migration 1.0 to 3.0
By alien3d in forum Ext 3.x: Help & DiscussionReplies: 2Last Post: 1 Jun 2009, 5:38 AM -
Migration GXT 1.2.4 to 2.0
By G.edwin in forum Ext GWT: Help & Discussion (1.x)Replies: 2Last Post: 15 May 2009, 6:26 AM



Reply With Quote