Community
Participate
Working Groups
To reduce complexity and maintenance code, we could investigate possibility to replace php explorer by common project explorer. Off course not today, not tomorrow. Benefits: 1. Common stable api for tree extensions. For example bug 344253 and bug 356629 will be fixed out of box. 2. Code will be reduced to small content extensions. 3. Better usability for those who work on many languages. 4. Hierarchical project presentation 5. "Project Explorer" is better name than "PHP Explorer" What we sacrifice: 1. Full content control 2. I'm not sure, but probably buildpath/library icons. Things to do: 1. Current refactoring support have to be migrated to common 2. Introduce group by namespace in Project Explorer 3. Add "PHP Include Path" and "PHP Language Library" and related to tree
I agree. There is similar discussion in JDT (bug 427897). Maybe we can divide it into smaller tasks and later just change default explorer for PHP perspective?
Big +1 from me.
(In reply to Michal Niewrzal from comment #1) > I agree. There is similar discussion in JDT (bug 427897). Yes, and some problems aren't linked. For example project explorer haven't 'Window Working Sets' indicator. > Maybe we can divide it into smaller tasks and later just change default > explorer for PHP perspective? We have to and this bug should be umbrella for Project Explorer extensions. Initial integration was done in bug 353453. If DLTK members are interested, would be good to keep most of things on DLTK Core side. Or backport later.
How about: 1. Switch to Project Explorer on fresh installs since 4.2 (if bug 494821 will be resolved). 2. Drop in 5.0 if no blockers?
Project Explorer still miss more then drag&drop: * Group by namespaces * Default 'Other Projects' working set (useful in my opinion) * I remember smaller issues in Project Explorer itself but I don't remember numbers I think we can make an experiment and switch to Project Explorer after fixing bug 494821 and after release 4.1. About dropping PHP Explorer completely we can think later :) Btw, are you using Project Explorer on daily basis?
(In reply to Michal Niewrzal from comment #5) > Project Explorer still miss more then drag&drop: > * Group by namespaces Group by namespaces is still very buggy and on larger project useless in dalily work. Should be rewritten after bug 472758 fix. > * Default 'Other Projects' working set (useful in my opinion) You mean "Window Working Set"? This inconsistency driving me crazy sometimes. > * I remember smaller issues in Project Explorer itself but I don't remember > numbers I also have something in my mind. When one of them appear I always checking "perspectives" :P > I think we can make an experiment and switch to Project Explorer after > fixing bug 494821 and after release 4.1. About dropping PHP Explorer > completely we can think later :) +1 > Btw, are you using Project Explorer on daily basis Yes, when I forgot switch from JavaScript perspective, and I don't need PDT cmd+shift+t. In general, after select "window working set" in all views, I mostly use cmd+shift+r / cmd+shift+t to navigate and mylyn task list to manipulate visible projects.
Hmm I think we are more or less good to go ;) I'm still thinking about bug 501049 because after removing ISourceModule and IScriptFolder binding is working mainly for PHP Editor only ;) but I think is not critical. Any comments, objections?
New Gerrit change created: https://git.eclipse.org/r/83299
Gerrit change https://git.eclipse.org/r/83299 was merged to [master]. Commit: http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=3b63ef11b27bfd3e685f66b2e1d8e66a7ff42737
New Gerrit change created: https://git.eclipse.org/r/89510
Gerrit change https://git.eclipse.org/r/89510 was merged to [master]. Commit: http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=85b706e4a4fcfaf843dd79fdb82be3e0241a5b08
New Gerrit change created: https://git.eclipse.org/r/120541
Gerrit change https://git.eclipse.org/r/120541 was merged to [master]. Commit: http://git.eclipse.org/c/pdt/org.eclipse.pdt.git/commit/?id=ed920cf66333e7f006b1924d7f65a36578bc1c92
Created attachment 274401 [details] Problem in project explorer
I find Project Explorer buggy (see attachment https://bugs.eclipse.org/bugs/attachment.cgi?id=274401 ). I had it in Eclipse Oxygen, but upgrading to Photon RC2 didn't solved this issue. Where should I report this bug?
Please open fresh bug for PDT in bugzilla. It's related to PDT common explorer content provider, similar is bug 512222. I'll try introduce hotfix without revolution, revolution will be in 6.1 ;P
> Please open fresh bug for PDT in bugzilla. It's related to PDT common explorer content provider, similar is bug 512222. Thanks! I wasn't sure if it was a PDT problem or a platform problem. Here it is: https://bugs.eclipse.org/bugs/show_bug.cgi?id=535736
