> What takes so long there?

It's the compute of the full tokens when file content is a very big. You
can start the main
https://github.com/angelozerr/textmate.java/blob/master/fr.opensagres.language.textmate/src/fr/opensagres/language/textmate/Main3.java
which tokenize angular.js and you will see the problem. But VSCode has the
same problem. When you open the angular.js file at first it is not
colorized. After few seconds it is colorized. When you close and reopen it,
the editor is already colorized (I think a cache must be done).

> Eclipse-Text is bleezing fast for lexical highlighting.

It's slow the first time when you open an editor.

> Is it just slow up-front or also slow while typing?

No typing is very quick.

> That seems quite interesting, and goes beyong WTP. It can be a pretty
good way to set up decent editors for any language.

Exactly! Glad this idea please you:)

> Would you be interested in contributing it to the org.eclipse.e4.ui
repository.

Yes sure, I will try to do that when I will find time. But to be honnest
with you, I would like to know before if there are really people who could
be interested with this project (and help me for contribution). I'm very
busy with typescript.java, so I have a little time.

More I have done a lot of copied/pasted from vscode-textmate that I have
updated to have Java syntax. VSCode is MIT, I don't know what I must set as
header in my Java files.

Regard's Angelo


2016-03-25 11:39 GMT+01:00 Mickael Istria <mist...@redhat.com>:

> Hey Angelo,
>
> On 03/25/2016 11:27 AM, Angelo zerr wrote:
>
> IMHO, I think Eclipse text editor should provide TextMate support for
> syntax coloration, because it exists a lot and lot of textmate grammar.
>
> That seems quite interesting, and goes beyong WTP. It can be a pretty good
> way to set up decent editors for any language.
> Would you be interested in contributing it to the org.eclipse.e4.ui
> repository. I believe you're already a committer there, and it would be
> mostly a matter of checking some IP consistency. I believe that making it
> available somewhere at Eclipse could really boost the adoption of that tool.
> Then, when this code reaches a good maturity, we may be able to consider
> it as a "standalone" Eclipse.org project, or even to include it in Platform
> Text.
>
> Cheers,
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>
>
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to