This is on the Atelier team's radar. There is an internal bug report to get this implemented. It is currently categorized as a low priority and targeted for Atelier 1.5. I just noted in that report that a customer requested this feature and linked to this DC post.

If you (or any of you other customers out there) would like to discuss changing the priority on this report, I'd suggest filing a new WRC case with Support. Our Support team can have a conversation with you about your specific needs then make the case with development.

The Atelier/Eclipse equivalent for jumping to a class/routine/macro referenced in the code you are looking at is F3 (or Open Declaration in the right-click context menu):

I don't know of an exact Eclipse equivalent for Studio's bookmarks. An Eclipse bookmark can be set on the line your cursor is at by going to Edit > Add Bookmark. Then you can open the Bookmarks View (Window > Show View > Bookmarks) to see a list of your bookmarks and double-click them to navigate to that line in the code:

The go to tag+offset feature is still in development for Atelier. It is a very high priority and should be coming in an upcoming version soon.

Here are another couple of keyboard shortcuts that I often use for Eclipse/Atelier navigation:

Ctrl+O (or cmd+O on a Mac) shows Atelier's Quick Outline, where you can see a list of members for a given class/routine. Hitting ctrl/cmd+O again shows the inherited members. You can start typing in this view to narrow down the members listed:

I also use Eclipse's go back and forward navigation commands to jump back and forth as I'm viewing/editing code. To go back you can use Navigate > Back, ctrl+[ on Windows or cmd+[ on Mac. To go forward it's Navigate > Forward, ctrl+] or cmd+].

Ctrl+Shift+R and Ctrl+Shift+T (again, cmd instead of ctrl on a Mac) can be used to open a resource or an Atelier class/routine, respectively, that exists in a local project. The "Open Atelier Class/Routine" dialog (Ctrl+Shift+T) will show server-side files in an upcoming version of Atelier.

There is also a page in the documentation on Atelier equivalents for Studio actions here.

Thanks for checking in, Wolf. You are correct - the bug is with the recognition of the end of a class query. This can present itself in many ways and cause other parser issues throughout the code.

This has been corrected starting with Atelier 1.2. The fix will therefore be available with the next beta update, which we expect to be coming in February.

Thanks for pointing this out, William. I'm going to report it to the Atelier development team to see what we can do.

You can also see this information in the Atelier Documentation view as you are moving focus within a class. If you do not see this view you can launch it by selecting Window > Show View > Other > Atelier > Atelier Documentation > Open.

For example, I opened Sample.Person on my local Atelier client, selected the tab at the bottom for Atelier Documentation, then clicked on "%Populate" in the list of superclasses. Now I can see this in the Atelier Documentation view:

Hi Fabio, thanks for the detailed information on using the Atelier debugger to attach to a process!

It looks like you posted this as a question instead of as an article. So it will show up as an unanswered question until an "answer" is posted. I'm adding this as an answer to fix that.

Vivek, if Fabian's suggestion is the solution that works for you can you mark that as the correct answer here? Thanks!

John - I'm going to create a WRC case for you and link the associated enhancement requests so that you can see the status as these progress.

The way to test out Atelier is to install Eclipse and download the Atelier plug-in. Then you can connect that to any 2016.2+ instance. As Eduard mentioned you can do that by following the instructions here: www.intersystems.com/atelier.

If you want to learn more about Atelier without installing, there are a number of InterSystems docs where you can read about the new development environment.

The Atelier documentation has a lot of information on getting started:

http://docs.intersystems.com/atelier/latest/index.jsp?topic=%2Fcom.intersys.eclipse.help%2Fhtml%2Fgettingstarted%2FintroAtelier.html&cp=1_0_0

The Atelier release notes outlining bug fixes and new features can be found here:

https://docs.intersystems.com/documentation/atelier/index.html

The Caché documentation has a number of sections that mention Atelier, such as:

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GSTD_atelier

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCRN_new20172_atelier

There is also an Atelier playlist on the InterSystems Developer Community YouTube channel with a mix of introductory and more advanced/targeted videos:

https://www.youtube.com/playlist?list=PLKb2cBVphNQT11WwvAN59idx2CZTkK9CA

This error can occur for a number of reasons. It could have to do with a firewall, a proxy server, etc. on your system. This is an Eclipse error, outside of InterSystems technologies - your best bet will probably be to Google the error.

I assume that by the droppins version you mean the standalone Atelier client? Starting with the 1.1.386 release, we dropped support for the standalone Atelier client. There was an announcement in the Developer Community here.

You will need to install Eclipse OXYGEN and add the Atelier plug-in. Detailed instructions can be found in the article linked above, or on the Atelier download site, intersystems.com/atelier.

If you are still having trouble installing the Atelier plug-in, I would suggest opening a WRC case with Support (by emailing support@intersystems.com or calling 617-621-0700) to investigate what is going wrong on your system.

Thanks for the update, Fred. This question was answered in Fred's comment. Adding this so the post shows up as answered.

I'd suggest filing a new case with Support (email support@intersystems.com or call 617-621-0700). That way an advisor can dial in and help troubleshoot your specific case. Then you or the advisor can come back to this post and give an update on the resolution.

Glad you found the source of the issue so quickly. I'm posting this as an answer so that your question will be marked as answered in the Developer Community.