An article by Robert

In this article we want to describe an issue with the clearGrouping method of the GridPanels in ExtJS 3.3.1 which is not saving the grouping state in the State Provider. Considering you have a grouped stateful grid, if you attempt to clear the grouping externally (via a button, for example), the state is not updated accordingly and on the next load, the grid will still be grouped. In other words, calling groupBy() method is updating the state, while clearGrouping() method does not.

This article will show you how to save the state when externally calling the clearGrouping() method.

There are quite a few versions of PagingMemoryProxy on the Internet, and the one from Sencha forums is not updated.

When deciding to use this extension in your project, make sure you have the following piece of code in it, code required by our mutual friend - Internet Explorer.

un articol scris de Robert

Gridurile ExtJS ne ofera o gama foarte variata de functionalitati native. Printre ele, se numara si filtrarea dupa valori ale anumitor coloane. Desi neintuitiva, aceasta metoda are limitarile ei - si anume se limiteaza la valorile din grid (sau cu alte cuvinte, criteriul nostru de filtrare ar trebui sa fie o coloana in grid).

O problema interesanta apare atunci cand incercam sa aplicam un filtru extern asupra store-ului gridului. Spre exemplu, avem un grid cu utillizatori (nume, prenume, id, nivel si domeniu) si dorim sa aplicam un filtru dintr-un combo-box dupa nivelul angajatului.

Desigur, am fi putut activa filtrarea nativa ExtJS, dar acest exemplu se doreste a fi o alternativa la filtrarea nativa ExtJS. Sa presupunem ca intr-un alt exemplu, am fi dorit sa filtram inregistrarile din grid dupa un alt criteriu, care nu am fi dorit sa fie in grid.

an article by Dumitru

In today’s modern web applications it is typical to include many libraries, widgets and snippets of code from many different sources. You must be mindful that other developers may be interacting with your code simply by both sets of code being included on the same page. It is not a safe assumption that you have the entire global namespace at your disposal.

Why use namespaces?

In our example we see managed some tasks which are differenced by received and created tasks. It is important that code in received_tasks.js and created_tasks.js can have the same objects, variables and functions identifiers – this can create some real problems in big applications.