Hans Wurst
added a comment - 21/Nov/11 6:23 AM the solution i found is to add .module etc. files at
Preferences->General->Content Types->Text->PHP
and at
Preferences->General->Editors->File Associations with
PHP Source Editor
Text Editor (Studio)
Text Editor
and have
Project->Properties->Project Natures like
PHP - Primary
Web
maybe aptana could be a bit more drupal friendly

Shalom Gibly
added a comment - 13/Jan/12 8:02 AM - edited Accepted your suggestion
Added default support for .module and .install extensions.
As for not indexing some of the .inc file - You have to make sure the files are in a project that has a 'PHP Nature'. Only files that exist in those type of project will be indexed.
Cheers

The problem here is that it causes a conflict with PDT (see APSTUD-4668), the result being you actually can't use PDT with Aptana as of this fix. This is a big issue for Drupal developers because all the Drupal-Eclipse plugins out there are built for PDT, not Aptana's PHP (Drupal Eclipse, Drupal PDT Templates, and DrupalCS AFAIK).

I suggest reversing this fix – users can add .module, *.profile, etc to Content Types as desired if not already there, but if it *is already there (as of this fix) the association becomes locked and you can't use PDT. I must revert back to previous version of Aptana.

Tyler Renelle
added a comment - 19/Apr/12 2:26 AM The problem here is that it causes a conflict with PDT (see APSTUD-4668 ), the result being you actually can't use PDT with Aptana as of this fix. This is a big issue for Drupal developers because all the Drupal-Eclipse plugins out there are built for PDT, not Aptana's PHP ( Drupal Eclipse , Drupal PDT Templates , and DrupalCS AFAIK).
I suggest reversing this fix – users can add .module, *.profile, etc to Content Types as desired if not already there, but if it *is already there (as of this fix) the association becomes locked and you can't use PDT. I must revert back to previous version of Aptana.