This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
I am using Myeclipse for quite sometime now. I really find it very useful and robust. At the same time I also feel that there should be different flavors of MyAEclipse that should be available instead of packaging the whole thing as one. For eg., if my project does not need Webservices etc. Can it be possible maybe in future to have various flavors of MyEclipse so that users may be given specifically what they require for their projects and not the other fetaures. That would also have a cost saving, maybe.
Thank you for being a MyEclipse supporter! To address your question of trimming the product down (as it's gotten fairly large), I'll point you at this thread where a gentleman asked a similar question.
It's actually possible to do it now, and we will further enhance this going forward.
Joined: Nov 26, 2007
Thanks Riyad, for your prompt reply to my query.
I would also want to ask one more question. I have been doing some profiling activities and I feel that the TPTP profiler that is being used has quite a number of bugs. For eg., 1. When we are configuring the agent controller port, it used to give me a success message on any port that I may be giving apart from 10002 or 10006.
2. When I was doing a remote profiling, I was able to connect to a remote machine, but when I started to profile on the remote machine, it did not show the correct packages and processes although the PID was correct.
3. Yet another problwm is that when I try to remotely profile an application running on MyEclipse from another machine having RAD 6.0(which also is eclipse based), i was not able to get the agents listed. maybe there is a problem with the protocol. But both are eclipse based. Do we still have different protocols?
4. Is there any place where we can get a clear picture on how the profiling happens..i mean the internal architecture of TPTP profiler and not the steps for doiing profiling activities.