Hi Turker, Thanks for your efforts to extend hackyEclipse to support C/C++. I am especially interested in your development, as I am currently building a benchmark written in C++ using CDT/Eclipse and therefore will probably be your first test subject in CSDL. Already, I have some opinions I think should be put into effect early in the development.
> 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. For a number of developers, the above strategy would work with minimal overhead. However, in my current development, I am building a benchmark in C++ as well as a parser-based code counter, written in Java. If I understand the above statement correctly, this means I will have to edit the ECLIPSE_PROJECT_NATURE property every time I switch between C++ and Java. I am currently switching contexts on a daily (if not hourly) basis and do not want to pay the overhead to configure the sensor property (and restart the Eclipse workbench) at this frequency. Can you think of making this property more dynamic? For instance, based on the file type of one being edited or based on the Eclipse perspective. I am quite interested in your views and wish you luck on the development. Best regards, Mike ----- Original Message ----- From: Turker Keskinpala <[EMAIL PROTECTED]> Date: Wednesday, September 1, 2004 9:44 am Subject: [HACKYSTAT-DEV-L:10] CDT and hackyEclipse > 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 > >
