New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeScript support #9324

Open
adrelino opened this Issue May 7, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@adrelino
Contributor

adrelino commented May 7, 2017

Basic TypeScript support would be of great benefit for static syntax checking as well as IDE integration.

E.g. @pdfisk announced yesterday in [qooxdoo-devel] that he is using Qooxdoo with TypeScript extensions to ease development of his pdfisk/vista-basic framework. In particular, Qooxdoo classes are mapped to TypeScript, which allows for easy IDE integration.
vb-client-typescript

Above is some TypeScript code extending the Qooxdoo framework. Qooxdoo is a fantastic JavaScript framework that should be much more popular than it seems to be at the moment.

from: http://vistabasic.com/index.php/2017/05/06/in-praise-of-qooxdoo/

However, the repository above did not (yet) contain the TypeScript extensions mentioned. After some more research, I stumbled upon @jbaron's work on Code Assistant for Type Script (CATS) at jbaron/cats which is basically a full TypeScript IDE. Its extension jbaron/qx-parser allows to generate a qooxdoo.d.ts typings file by reading qooxdoo's API documentation.

It would be great if @pdfisk and @jbaron could help us to integrate the TypeScript Definition files into the main qooxdoo repository as I am sure many (especially new) qooxdoo users will benefit from it!

@pdfisk

This comment has been minimized.

Show comment
Hide comment
@pdfisk

pdfisk May 7, 2017

I will make the TypeScript extensions available.

They were originally generated by "qx-parser" and I have been adding in missing typings as needed.

pdfisk commented May 7, 2017

I will make the TypeScript extensions available.

They were originally generated by "qx-parser" and I have been adding in missing typings as needed.

@pdfisk

This comment has been minimized.

Show comment
Hide comment

pdfisk commented May 8, 2017

Vista Basic client code is now on GitHub.
https://github.com/pdfisk/vista-client

The typings file is here:
https://github.com/pdfisk/vista-client/tree/master/src/qkwidgets/types

@tcsaddul

This comment has been minimized.

Show comment
Hide comment
@tcsaddul

tcsaddul May 9, 2017

tcsaddul commented May 9, 2017

@johnspackman

This comment has been minimized.

Show comment
Hide comment
@johnspackman

johnspackman May 9, 2017

Member

Looking at the jbaron's qooxdoo.d.ts it should be quite straightforward to build a target for qxcompiler that provides this; I'll add an issue

Member

johnspackman commented May 9, 2017

Looking at the jbaron's qooxdoo.d.ts it should be quite straightforward to build a target for qxcompiler that provides this; I'll add an issue

@tcsaddul

This comment has been minimized.

Show comment
Hide comment
@tcsaddul

tcsaddul May 27, 2017

I hope the qooxdoo team will consider adding "official" support for TypeScript and make it easily accessible to newcomers.

Here is another UI framework I've been following the following for years which is very much like qooxdoo: www.webix.com which has now also supports TypeScript: https://blog.webix.com/typescript-types-in-webix-ui-framework/

Here is their typescript definition: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/webix

tcsaddul commented May 27, 2017

I hope the qooxdoo team will consider adding "official" support for TypeScript and make it easily accessible to newcomers.

Here is another UI framework I've been following the following for years which is very much like qooxdoo: www.webix.com which has now also supports TypeScript: https://blog.webix.com/typescript-types-in-webix-ui-framework/

Here is their typescript definition: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/webix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment