Plans for Designer support for EXT JS 4.0?

[Carun]

Starting to develop an Ext JS based proof of concept and having the designer work with JS 4 will be of immense help.

Any update on the timeline?

[ssamayoa]

I bought Designer last year and didn't used for real because I'm using ExtJS 4 + MVC so I'm anxious to see if 1.2 will be helpfull or not.

Sencha's people were talking about august but I would like to see early (alpha even pre-alpha) version.


Regards.

[CaliLuke]

I bought Designer last year and didn't used for real because I'm using ExtJS 4 + MVC so I'm anxious to see if 1.2 will be helpfull or not.

Sencha's people were talking about august but I would like to see early (alpha even pre-alpha) version.


Regards.

your prayers have been answered ;-)

http://www.sencha.com/forum/showthre...er-1.2-Preview

[CaliLuke]

Starting to develop an Ext JS based proof of concept and having the designer work with JS 4 will be of immense help.

Any update on the timeline?

I was wondering if you already started using Designer 1.2 preview. Please let us know how you're doing with it, and if there's anything not working for you.

[ssamayoa]

I was wondering if you already started using Designer 1.2 preview. Please let us know how you're doing with it, and if there's anything not working for you.

I played a little with it early this morning but still not helping because I'm using MVC and "custom" properties like "action" in buttons (I use it to find in controller which button was pressed), non "hierarchied" export (AKA namespace / package), cant edit some properties like "tbar" and so.

To be usable as design tool for me I need:

1. Export files using namespace as folder, ex:

pp.store.empleado.Editar

pp/
pp/store/
pp/store/empleado/Editar.js

2. Config option to generate only UI without "ui" suffix, ex:

pp.view.empleado.Editar will be exported as
pp.view.empleado.Editar.js
pp.view.empleado.Editar.ui.js

With a project config option "export UI only" will generate just pp.view.empleado.Editar.js containing the UI.

NIve if is for top component basis.

3. Allow "custom" properties like "action".

and

4. "Nice to have", edit tbar and bbar (I can live without that).

With those modifications I will be happy but with just #1 I can use designer again with my MVC code.

Regards.

[CaliLuke]

I played a little with it early this morning but still not helping because I'm using MVC and "custom" properties like "action" in buttons (I use it to find in controller which button was pressed), non "hierarchied" export (AKA namespace / package), cant edit some properties like "tbar" and so.

To be usable as design tool for me I need:

1. Export files using namespace as folder, ex:

pp.store.empleado.Editar

pp/
pp/store/
pp/store/empleado/Editar.js

2. Config option to generate only UI without "ui" suffix, ex:

pp.view.empleado.Editar will be exported as
pp.view.empleado.Editar.js
pp.view.empleado.Editar.ui.js

With a project config option "export UI only" will generate just pp.view.empleado.Editar.js containing the UI.

NIve if is for top component basis.

3. Allow "custom" properties like "action".

and

4. "Nice to have", edit tbar and bbar (I can live without that).

With those modifications I will be happy but with just #1 I can use designer again with my MVC code.

Regards.

This is very valuable. While full blown support for MVC is in the works for 2.0, some small tweaks to make the lives of people like you easier might be considered for the next 1.2.1 release that will focus on fixing minor UX annoyances.

Thanks for the feedback.