Hi all,
Thanks to Philip for adding and introducing me to the list.
I started adding CDT compatibility to hackyEclipse. Currently, I am not particularly interested in FileMetrics. I am focusing on collecting data on the activity of the user on C or C++ files. It does not seem to be a big problem since the window listener, part listener, and resource change listener may all be independent of the programming language. I noticed that the sensor was programmed to record "Open File" activity for any file type but "Close File" activity for only .java files. Is there a specific reason for that?
Two big java dependencies were at detectBuildProblems() method and JavaElementChangedAdapter class. Instead of taking out the java compatibility of hackyEclipse, I decided to configure the behavior depending on the project nature. For this purpose, I added ECLIPSE_PROJECT_NATURE property to my sensor.properties file. This would be either javanature, ccnature, or cnature. So, if the nature is ccnature, the sensor only collects activity data on C++ files. detectBuildProblems() was also changed to detect C++ build errors or java build errors accordingly. I also created CElementChangedAdapter for recording changes on CElement types. However, I am still trying to figure out somethings about that.
Is there anyone else who has an interest on CDT compatible hackyEclipse? Do you have any comments or suggestions on the way I chose to implement the functionality?
Also, I am wondering if it would be a good idea to contribute a PreferencePage to configure the plug-in instead of a sensor.properties file. It could make it easier to configure the sensor. Again, is there a specific reason why we need a sensor.properties file?
Thanks and have a great day, Turker
