• Page
|
• Edit

FAQ: Developer Console Webinar FAQ

General Questions

Q: Will the webinar be available online?
A: View the webinar information page.

Q: Is the purpose of the new console to replace the Force.com IDE?
A: No. We are exposing a public tooling API, which is leveraged by the Developer Console.  We are planning to rewrite the Eclipse plugin on this API and open-source it.

Q: How do I activate the dev log? As I move through my apps/org right now, nothing shows in the log. Is there something that must be "activated"? 
A: First, you must open the Developer Console. Then you need to enable 'Author Apex' and 'View all data.' Once these permissions are enabled, you can open it in the header navigation.

Q: Can multiple people edit the same class in the Developer Console or are there blocks to prevent this? 
A: Yes, anyone editing the class will be notified that the file has been edited, and it will not allow you to save until you refresh the source.

Q: Where can editing be done? in a development or sandbox org, but not in production?
A: Yes, editing in development and sandbox org - but you can view logs and create heap dumps in a production org.

Q: You mentioned "next execution" captures a heap dump when you set a simulated breakpoint.  Is it *only* the next exec, or is it persistent until specifically disabled? 
A: Persisted until disabled, or the Developer Console is closed.

Q: Does the break point work similar to the one in Netbeans or Eclipse? Does it stop the execution while debugging?  
A: No, it does not stop the execution. It is all post request.

Q: Can I use other languages in the console or just Apex ? 
A: Just Apex and Visualforce.

Q: With the old developer mode, I noticed that indenting code looks good there, but when put into Eclipse, the tabs turn into spaces and some characters don't translate. Does this new console make the look of the code consistent across this tool, Eclipse, etc.? 
A: There is no current plan to make the code appear consistent between tools.

Open Raw Log

Q: I submitted a bug for the "Open Raw Log" that has two issues:  1- Once you open the debug in the Execution Log, you can't open the Raw Log; it's ignored.  2- When the Raw Log is opened in IE, it doesn't line feed properly, but does in Chrome.
A: 1- Currently, you can only open one instance of the log. If you want to open the Raw Log, you need to close the interactive view. 2- This has been reported, but is currently in our backlog.

Q: Sometimes it says the log will only open in Raw Log. How we can see that without the Raw Log?
A: Right now, the only way is to view it in Raw Log mode. We will be increasing that limit as time goes on.

Q: In the past version, the Developer Console hangs in IE if the log is huge. Any improvement there? 
A: Right now, we enable the Raw Log mode to prevent the console from hanging. You can increase filters or use class filtering to reduce the size of the logs. We have some large stories to improve the performance in future releases.

Q: Is there any way to go back to old system log window?
A: The system log was removed since the Developer Console can now view Raw Logs.

Future Releases

Q: This is awesome!  I'm going to have to buy a bigger monitor!  Will the new console allow you to undock items to other areas of your screen? 
A: Stay tuned. We are working on that for a future release.

Q: is there any pre/private release of the 'tooling api' for developers interested in writing tools for it earlier for the community? 
A: Yes, stay tuned for this.  We will probably kick off the pilot in the second half of this year.

Q: Any work being done on console performance? 
A: Yes. We are constantly working to improve performance.

Q: Refactoring would be wonderful! 
A: We now save in bulk using the Developer Console, so you can change all the references and save it all at once. As for automatically doing that, stay tuned. This is planned for future releases.

Q: What happened to the Download button for logs? 
A: That was removed with the addition of Raw Log mode. Although, we have been hearing this from multiple customers and will consider adding it back in.