I downloaded the most recent version (4.2.3) of Sencha Architect that I'm licensed to use (we stopped using Ext JS a couple of years ago) and when I try to open an old project it says "This version...
Type: Posts; User: marc.fearby
I downloaded the most recent version (4.2.3) of Sencha Architect that I'm licensed to use (we stopped using Ext JS a couple of years ago) and when I try to open an old project it says "This version...
This is what I get in my developer console when I try to run that grid demo:
57887
I separated my front-ends in Ext JS from the Visual Studio solution directory many years ago. I gave up trying to get them to play nicely together in the one parent folder, and now I quite like...
I downloaded it from the support portal myself and it's fine now
PS, I have noticed a dialog telling me that an update is available, but it continues to fail to download and install. It gets about 1/3 through and apparently hangs, so I kill it and say "not this...
The organisation I work with has separated from a parent entity, and now has its own Active Directory, so therefore I have a new Windows user profile on my computer. I have re-setup everything,...
Actually, the problem was caused by my installing Java 10. Since I uninstalled that and went back to 8 everything is fine. I'll have to limit my learning of Java to version 8 for now and then move to...
I fixed my system PATH so that 6.5.3.6 is the version of Cmd executed in my Command Prompt, rebooted, and get the same error (same again in Architect itself, too)
I am unable to do a build of an app in Sencha Architect today (or even via the command-line myself). Here's the Cmd Output from Architect:
[INF] Processing Build Descriptor : default...
A relevant quote from that article:
The Cmd errors shown in the Log in Sencha Architect are mostly useless, and several of my more complex views won't show a preview because of some indecipherable binding error or null component...
Most software doesn't restrict your ability to still use it in production if you don't renew the license. The version you had at the time your license expired is the version you're stuck with (until...
I wouldn't think that Ext JS is ideal for creating the whole web site as such; it might be OK if you want to have a grid here and a form there, but I wouldn't use viewports, panels, etc, for the...
Their grid row editor is very nice, so that's a definite plus right there.
Oh, and their pricing is non-extortionate, too. I can't believe I didn't know about DevExtreme before :-) Thanks.
I did that to the "checked" property using "process config" in Sencha Architect but the app crashed, complaining that there is no setChecked() method so therefore I can't bind it. But I'm not going...
The docs still don't have a "bindable" flag beside this property in 6.5.2: http://docs.sencha.com/extjs/6.5.2/classic/Ext.form.field.Radio.html#cfg-checked
In any case, I've solved my problem and...
We can't bind the checked property in classic, unfortunately :-(
I've just be tidying up some horrible old code I did 5 years ago, and found this in my search to refresh my memory about links. I've just done what you're trying to do (and have probably figured out...
$249 per month per developer is even worse than Sencha's Premium 5-pack: 12 * $248 * 5 = $14,940. Not having to buy quantities of five is a good thing, but still, one developer license costs $2,976...
I've never heard of WaveMaker but it looks interesting (as do a lot of things these days). But one thing I notice is that there's no pricing anywhere on the web site. If you have to ask how much...
It's been a while now but I think I ended up just compromising and going with a hard-coded reference and made sure I added comments where ever I used it to inform any other poor soul who might have...
Um, perhaps I didn't comprehend your post completely. When my 'nameOfControllerFunction' is called it runs in the scope of the viewcontroller, so I assumed that yours wasn't (even though I now read...
Just specify this config only:
tipText: 'nameOfControllerFunction'
I think the question should be "why?" rather than "why not?" ;-)
True, which is why I've decided to stick with Ext JS for an app I plan to write with Electron. These might be uncertain times at the moment but I still have six years' experience with it and I'll be...