Hi Jacek, I've just updated my proposal (only the wiki version for now) to incorporate your suggestions [1]. Please take a look.
I think it'd be nice to integrate two implementations of syntax highlighting - one server-side (the service), and one totally client-side. From the perspective of Orion, they would be interchangeable and accessible under exactly same interface. It'd be also a proof of "switchability" of layer 1 you described. This would also eliminate the requirement to embed the first solution with Orion (which could be problematic) - in case it'd be too slow the user can switch to latter, "standard" solution. For server-side, I think about using GeSHi [2] (it's GPL too, but I wouldn't embed it with Orion at all). For client-side, Ace [3] (is MPL compatibile with EPL?). Then I plan to work on syntax validation as you said - would it be useful to make it as a service too? The last part is code autocompletion (a little bit simpler than in previous version of the proposal). Please let me know what you think. > We need some umbrella bug like "PHP support for Orion", it could live in > PDT.Incubator or Orion, I'm not sure yet what's better. OK. I'd go for PDT.Incubator, but this work seems to be a little bit Out of Scope, isn't it? [1] - http://wiki.eclipse.org/User:Karol.gusak.eu/GSoC_Proposal_Orion_Web_IDE_PHP_Editor [2] - http://qbnz.com/highlighter/index.php [3] - http://ace.ajax.org/ Regards, Karol _______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev
