custom components and MVC in ST2

[gkatz]

where do custom components go in the MVC structure?
thanks

[mitchellsimoens]

It depends on the namespace you have. Say you are using my Ext.ux.touch.grid extension. I put them in the assets/ux folder

/
--app/
--assets/
----ux/
------touch/
--------grid/
----------View.js
--app.js
--index.html

And I then set a path:

Ext.Loader.setPath({
    'Ext.ux' : 'assets/ux/'
});

So now the Ext.ux namespace points to the assets/ux/ folder.

[gkatz]

thanks
how does the css of a custom component fits here?
for example;
in your Ux.ImageLoader component there is an accompanied by a css file.
how does this css file loaded? should I explicitly load it in the index.html?
thanks
BTW : is this component go to go? seem like its working...

[mitchellsimoens]

Yes, the CSS file will need it's own <link> tag in your index.html although if you are using SASS you could put the style in a scss file and it will compile together.

I just developed it last night when I was working on Chapter 8 of Sencha Touch in Action. It works and works great. I do have another idea to make it better and will maybe get to it tonight but may decide not to do it tonight but another day.

[gkatz]

nice...
I think Jarvus needs something like this for the PinchZoom carousel component he has.
his ST1 component uses something like this and I think he is just about to port it to ST2...

[themightychris]

I'm on it =] Aiming to release next week

[gkatz]

yeah chris!
I think I have asked this before.
would looooove to see the ability to zoom beyond the original image size. I might be mistaken but I think the ST1 version had that limitation
anyways guys thanks for helping and sharing

[mrsunshine]

@gkatz may the image zoom example helps you http://www.sencha.com/forum/showthre...rollable-Image to implement your own solution, i faced the same problem

[gkatz]

Hi;
Today, I still think the docs lack the explanation for component developers on how package/submit custom components and how components users should incorporate those components. looking at the components people submit there is no coherent structure/naming convention that unifies all components. this makes reduces readability of the component.
I think the docs should address this issue to make things easier both on developers and component users... I guess the guidelines would be simple to provide and I see a big benefit here.
thanks for your time.