It would be nice to have the renderer capability for Ext.grid.column.Number within Architect 2.1.0. It isn't listed in the Config area, so I'm going to have to use a regular column instead and do the number conversion myself. Not a huge thing, but very annoying.
I can't add the renderer option, since it the datatype of "function" isn't available for added options. It's an option within ExtJS 4, but not Architect.
Since a renderer can do many things, it has more use than just making the column look one way or another. The specific way I wanted it to work is to add two columns in a record together and display the total, without the requirement of having a separate column for the total then doing the math and adding that total to the record. Another thing I wanted to accomplish is to deal with old data in the database, and display it in a more understandable way without changing the information, and without needing yet another column in the record to handle it, by simply pointing the column to the one record and rendering it using other columns I can make it much simpler than what I have to do now. I thought the whole idea of an IDE like this was to make things easier for the programmer, not more difficult by removing functionality of the language or library they are using and requiring them to work around the limitations of the IDE. This isn't the first time I've run into limitations like this.
I don't need Architect to "protect me from myself." I need it to do what the language and library are capable of doing.<br><br>If the column uses the renderer, then provide a way to extend the renderer to do more things. As it is, the number column is so narrowly defined as to be nearly useless, unless you want to display a number from a model that should already be a number type, and do nothing else with it. This lack of functionality isn't helpful. We can do the same thing by adding a render to a standard function to "return value.toFixed(#);".<br><br>It's like offering me a choice between a nose hair clipper or hedge clippers when I want to cut my hair. I either don't have the capability to do what I want, or I have to be very careful and specific and then maybe I can get done what I want.<br><br>As for using a function to do what I want, I can't find any documentation on how to use it, what can be done with it, when it fires, if it fires, if I have to call the function, or how to call the function if it's not automatic. If there's this total lack of info, why would I waste my time on trying to deal with it if I don't have any idea if it will do what I would like to do. Then again, about half of Architect and ExtJS is trying to figure out what non-obvious anything will actually do or what something should do but doesn't.<br><br>I'm not going to argue anymore about how something should work compared to how Sencha thinks it should maybe work. It's just that some of the things that should be easy are really difficult to do and it doesn't seem as if anything is being or going to be done about it.
I had figured that out before my first post in this thread. I was hoping to explain that the number column is so severely limited in functionality to be nearly useless, except in a single instance, and to convey that it would be more useful if there weren't so many restrictions on it's use. Unfortunately I have not been clear to you, or Sencha doesn't actually listen to what their users say. Either way, I'm not going to post on this useless forum again. I'm also going to continue to push my boss to use something other than Architect to build our software.
It appears as if we just had a misunderstanding as to where you posted this... Architect replicates exactly what Ext JS or Sencha Touch exposes.
Number column in Ext JS should use your renderer and then post process it with its own renderer OR it should do the standard number processing and then use your own renderer. This ability would cover several potential use cases. We should enhance the framework to handle this.
This forum is for bugs within Sencha Architect, not for bugs within the Ext JS. Would you like me to move your post for the Ext JS team to take a look at?