Greetings,

Thank you for contacting us with this.

May I please clarify with you if you get the color highlighting of your code when you work with files which are part of TWS project?

The absent syntax coloring for one separate file is the way how it is implemented - in this case, there is not enough data for properly highlighting.

If you have any other questions or some suggestion, please contact us. We will be happy to assist.

Also, you can use TWS Documentation for exploring the IDE.

Regards,

Kate

Yes - I just went to File menu > open file (not project) and opened a .cls file.

I would have expected that the IDE would know what syntax color coding to apply based on the file extension (.html, .js, .cls ...)

Hi,

Thank you for your response.

We will consider which way we can implement this.

Right now I cannot tell you any estimate for this, however, we will investigate possibilities for adding this feature.

Regards,

Kate

Looked at this a little more - if you just do an open file on a .js .html .css - it does the syntax color coding right, it just appears that if you open a .cls file there is no syntax color coding. An apex class (.cls) file happen to be the first file I opened. Seems like an oversight or a bug in the software. 

Hi afitch,

Thank you for shring your opinion with us - we will consider making changes in that direction.

The reason why right now the syntax highlighting for "detached" files (opened separately from the project) is now available, is because our engine is using not only lexer for coloring, but it also uses parser. Parser at the same time requires as much information about the "surroundings" as possible - all other classes in the org, information about sObjects and Custom Setiings, a bit later it will also work with the information about the Labels. All this information is needed to properly highlight different entities in your code.

While we technically can implement the simpler highlighting specifically for this cases, we believe that we rather focus our efforts on improving other code assistance related features or on adding new ones - refactoring, for example.

At the same time opening the full project instead of just a file is not significantly longer - usually projects are opened pretty fast, and we believe that the situation when developer needs to look at only one file of a huge project (yup, huge project will open far slower than just a single file) without looking at anything else is almost an exception of the general use-case.

Hope this helps.

Thank you,

Vladimir