hi Karol, thanks for looking into this! We need to start tracking your work as well. 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. I agree about latency concern. It makes sense to have the service separately and embed it with Orion. Regarding SHJS - is it possible to get it only with PHP highlighting? Under "Download" it says that one can customize it by downloading source package. Btw. be aware, SHJS is in GPL, so it would not be possible to embed with Orion, which is on EPL.
thanks, Jacek ________________________________________ From: [email protected] [[email protected]] on behalf of Karol Gusak [[email protected]] Sent: 16 April 2011 16:03 To: PDT Developers Subject: Re: [pdt-dev] Question regarding GSoC Hi, I think your order of features is better. :-) I'm going to thing about it more. In Ace [1], they have a concept for modes to highlight different parts of code in same file using different highlighters. There is no such thing in Orion yet. They don't highlight JS in HTML yet. I just asked on bugtracker about it. I like the service idea, however I'm concerned about the latency. Coloring syntax in Orion in real time could be problematic, right? Unless the service would be embedded with Orion server-side too. I couldn't find any existing public highlighting service for PHP. However, except what I mentioned in the proposal, I also stumbled upon SHJS [1] which can highlight many languages, including PHP. [1] - http://shjs.sourceforge.net/ Regards, Karol 2011/4/14 Jacek Pospychała <[email protected]>: > ok, > it's been few days and I've got few more comments to the proposal: > > could we start from syntax highlighting? if it starts working, we'll get such > functionality like e.g. Vim - already enough to get noticed by users! > It will also help resolve smaller issues, like detecting php blocks. E.g. php > file can have html, css, php, js mixed together. We want different > highlighers to take their own blocks. (I guess that depends on Orion a lot) > Next - syntax validation and marking errors - this will give us some parser > so it will set us for further work, e.g. on context assist, refactorings etc. > > Implementation should be flexible, to easily change underlying mechanisms. > For example, let's launch highlighting service > (http://www.eclipse.org/pdt/tools/highlighter) with simple text input, that > just shows highlighting. (layer 1) > Next, add API (layer 2) > Next add API-Orion integration (layer 3) > > With such config, it'll be easy to test layer 1 or switch different impls of > layer 1 and we can work on it at the same time as layer 3 (which will require > Orion team interaction). > Maybe even there's already highligher service, so we could avoid implementing > layer 1? :-) > > > > ________________________________________ > From: [email protected] [[email protected]] on behalf of > Wayne Beaton [[email protected]] > Sent: 06 April 2011 19:30 > To: [email protected] > Subject: Re: [pdt-dev] Question regarding GSoC > > I just accepted your mentor request. You're good to go. > > Wayne > > On 04/06/2011 02:30 AM, Jacek Pospychała wrote: >> thanks Karol, >> >> I just requested to become a mentor and will add myself once I'm accepted. >> >> ________________________________________ >> From: [email protected] [[email protected]] on behalf of >> Karol Gusak [[email protected]] >> Sent: 05 April 2011 20:09 >> To: PDT Developers >> Subject: Re: [pdt-dev] Question regarding GSoC >> >> Hi again folks, >> >> sorry for double post, but one of the program administrators asked me >> to call for potential mentors of this idea to comment on the proposal >> in socghop webapp. Could you take a peek? I hope this link works: >> >> http://socghop.appspot.com/gsoc/proposal/review/google/gsoc2011/kgusak/1 >> >> Regards, >> Karol >> _______________________________________________ >> pdt-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> _______________________________________________ >> pdt-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/pdt-dev > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > _______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev _______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev
