ExtReact Component inside Plain HTML

[jchris]

Just checked this with 6.6.3. No change. When will this be fixed?

Chris

[ricardo.lgr]

Has someone been able to do it? i have this example code. Im still getting incorrect casing.

While it works, the button is not rendering. It falls back to default button, i guess thats why it works with onClick instead of handler

renderActions = (value, record) => {
return<Buttontext="Buy"onClick={()=>console.log("hi")}ui="round"className="x-item-no-select"/>
}

<Grid store={this.store} >
<Column text="Name" dataIndex="name" flex={2} type="string" />
<Column text="idRoute" dataIndex="idRoute" flex={2} />
<Column renderer={this.renderActions} />
</Grid>

[jiwayProgrammer]

Was there some fix on this from ExtReact 7.0.0? Because on ExtReact 7.0.0 it is still bugging.

[jfconde]

Any updates on this? We have everything ready to update to 7.0, as we had with 6.7, but we cannot do it if this is not solved. It is unacceptable for this bug to be corrected. I know it has todo with the way React fiber renders components, but please tell us if this is going to be solved or not.

Also, to further enlighten, if you had column renderers which returned ExtReact JSX, that does not work anyway. ItemTpl does not let you return JSX and add listeners, and the WidgetCell is just plain absurd: instead of forcing you to write JSX or HTML, you would have to code your cell bodies using ExtJS, and most of our jr. developers don't even know what a xtype is.

We have been waiting to renew our license but we are already seeing the light at the end of the tunnel: Sencha is leaving ExtReact for dead (it was just ExtJS with a quirky "reactify" anyway), and now we will have to rewrite our whole app using our own (or other 3rd party) UI toolkit.

You guys were amazing until you released Ext 6 and Embarcadero bought you. From that moment on you have been on a free fall, a neverending free fall.

[jfconde]

Attachment 58122