jbaron / cats

Code Assistant for TypeScript
Apache License 2.0
408 stars 66 forks source link

Project properties on version 2? #163

Open dtrillo opened 7 years ago

dtrillo commented 7 years ago

Where are they?

After a long time using CATS version 1 (last published), I moved to CATS version 2 (2.0.397), and I am moving back to Version 1.

I have notice that the Project properties is esential for me, or maybe I don't know how to "translate" the config of a project from CATS version 1 to create a workint tsconfig.json. The key is that I can get a project working with CATS 1, and I can't get it working without modifying a single line of code but using CATS 2.

The second aspect I don't like of CATS 2 is the themes, with wierd backgrounds images that make me feel unconfortable. I'm still waiting for some features I think are easy to implement, such as clear the projects, a message after a project have refresh, and I don't need a button for changing theme! Also, CATS setting are now showing correctly because of the colors (disable tab is rare to distinguish). I'm so sorry for my vision of CATS 2, but that's what I feel, and I must admit that CATS is the IDE I'm using for writting TypeScript, but until a better version 2, I'm moving back to version 1. Another feature I notice is that CATS v1 is not working properly when using last updated of NW, while working perfectly with previous NW. So, if you still want to use CATS 1, be sure to use NW of previous versions, while using CATS2 requires on latest of NW.

dtrillo commented 7 years ago

After some time, I realized that compiling on version 2 in dependant on tsconfig.json. So, project properties Windows is not neccesary anymore.

tcsaddul commented 7 years ago

I fear that this project is already dead. I hope not.

jbaron commented 7 years ago

Project is not dead, but spending a lot of time abroad for my work so not too much time right now. Sorry for that.

dtrillo commented 7 years ago

I hope Project can be updated. I know it cost, but keep pushing!!!

I notice that tsconfig.json is not working as expected. I using TypeScript 2.3. The same code, on CATS, give me errors with RequireJS and jQuery. Maybe is the way I code it, but running the compile using tsc gives me no errors! I can send the template files I use (html, ts and js files), including the tsconfig.json file, and you can verify what I got (errors that it shoudn't). I wonder if that errors are because of TypeScript version (I'm using 2.3), or because tsconfig is not working as expected. It could be a good idea to update to TypeScript 2.3.

Also, I "hate" those themes in red, impossible to work with. Keep it simple!!!!! Or at least, give continuos to the themes of version 1. The themes with backgrounds, I dislike them! In version 2, I miss a clean theme: clear background, no image as background. You can avoid the button for change theme (is not neccesary, because there is an option for that).

I also comment the issues to solve: clear LocalStorage for projects, themes with no distractions (this IDE is for working!!), and update to TypeScript 2.3

jbaron commented 7 years ago

Updated to typescript 2.4 in latest version. If you have examples what goes wrong, please do attach a project file (zip format if possible).

dtrillo commented 7 years ago

Have you updated the .nw file for download?

jbaron commented 7 years ago

I did now, it is available as version 2.4

dtrillo commented 7 years ago

static.zip

Hi. Here you have a Flask project I am working on, and it has problems with requireJS, it is not loading jquery correctly, and other libraries.

If you ejecute "tsc" under a console, there is no errors, while under CATS, there is a lot.

I hope it helps

jbaron commented 7 years ago

Thanks for the example. I did some investigation and the problem is with the more (recent) attributes in the tsconfig file that can include or exclude certain files from the project. For example that you can specify a directory for the typings files. CATS right now ignore those attributes and as a consequence doesn't load the typedef files like the one for JQuery.

I guess the only clean solution is to reuse the tsc functionality to map all settings in the tsconfig file to the final list of TS files that are part of the project. The current mechanism is too simple to be able to handle arbitrary tsconfig files.

dtrillo commented 7 years ago

Thanks for your investigation. I am gladd you know where the problem is.