I tried to use it in Sencha Architect in the last version, that is: 2.1.0 build 637.

I found some problems:

I am using groupingfeature and summaryfeature so I already have a "features" configuration for the grid, plus it is read-only, I just can add the components that are available. Filtering is none of them.

After adding the

Code:

requires: [
'Ext.ux.grid.FiltersFeature'
],

I had to copy the ux folder in my application so now the application finds the javascript required and loads the application.appstructure.png

According to the example, the way to add the filtering to a grid is like the following:

But using Sencha Architect, you cannot add the filtering feature in the code (unless you override) without creating your own "property" then you will have a duplicated property if you use groupingfeature or summaryfeature,etc.

So, what should I do to make the filtering feature to work using Sencha Architect, how can you use any UX component from Sencha Architect ?

Use an override to add the additional feature. Anytime that there is a custom thing/user extension that is not included out of the box with Architect you can always add it by adding the appropriate JS Resources and adding it via an override and/or event handler.

Your suggestion is to add the code like in the example -see the code above-,
then put my features property using the filters ?

Sencha Architect is for developers, not advanced users... imho, and as a developer, I can say that if it is supposed to be so easy I think should documentation should exist to add all this ux features that are very nice and widely used (as you do in your examples without using Sencha Architect).

Maybe there is some documentation on the topic that I am missing that illustrates how to solve it. Point me to it if that is the case.

I will appreciate additional information, as I am new to Sencha Architect and ExtJS4, and if some tutorial is made and put online other users will definitively find it very useful.

Thanks for your support.

Originally Posted by aconran

Use an override to add the additional feature. Anytime that there is a custom thing/user extension that is not included out of the box with Architect you can always add it by adding the appropriate JS Resources and adding it via an override and/or event handler.

If you are only using standard Ext JS/Sencha Touch components (no overrides), you will be able to create everything without dipping into overrides. We are working on 3rd party component support, but its not quite there yet.

I've created a ticket for us to create an example of grid and filter feature being used within Architect.

By adding a JS Resource I mean go to the top right of the inspector, click + then go to JS Resource and then configure the url appropriately.

I understand, but filtering is a feature that should be built-in. And there is lot of important components that anyone should be able to integrate in Sencha Architect as something "usual".

I appreciate the ticket and your support, according to your previous reply seems it should be really easy stuff. For me, a zip in this thread will work, or a brief explanation, code.

The only thing I don't understand is why do I need to add the JS Resource (never used the overrides from Sencha Architect, sorry). What I expect is just:

In Application edit the requires property.

Put the ux code in the folder so the application can get the code for the ux in the requires property.

Create override (panel grid).

Put additional code in the override.

Works with the grid.

But I see that I have to do something else.

Thanks again.

Originally Posted by aconran

If you are only using standard Ext JS/Sencha Touch components (no overrides), you will be able to create everything without dipping into overrides. We are working on 3rd party component support, but its not quite there yet.

I've created a ticket for us to create an example of grid and filter feature being used within Architect.

By adding a JS Resource I mean go to the top right of the inspector, click + then go to JS Resource and then configure the url appropriately.

What I did to make it work was editing the code generated instead of the override. But it is not the correct way (even if it is working), and I had problems trying to put the code in the override (probably a javascript error).

Regarding the JS Resource, I did nothing, just copy the ux folder. With the requires the javascript loads.

I look forward to have the example or some javascript code of the override in the right way.

Thank you.

Originally Posted by aconran

If you do the above, this will work fine. Using the requires property is simply an alternative to directly including a JS Resource.

When you include a JS Resource it will generate an additional script tag linking the file.

When you use requires, it will dynamically load the resource. Note you will probably have to additional configure the loader to tell it where Ext.ux should be loaded from.