Feedback on "Atelier Explorer" vs "Server Explorer"

Article

John Murray · Apr 10, 2016 1m read

My comments here relate to Atelier 1.0.137 on Windows connecting to Ensemble 2016.2 FT build 627.

I've been looking at what the Atelier Explorer view (hereafter AE), whose root elements are projects, lets us do with the contents of the namespace that the project is connected to:

versus what the Server Explorer view (here after SE) gives us:

Here are my observations so far.

1. CSP files are only accessible in SE. I'm guessing this is because Atelier's support for CSP files is so new as not to have propagated yet to everywhere that it's planned to cover.

2. SE hides items that are mapped to the namespace from databases other than the default code database of the namespace. For example SE shows:

and AE shows:

IMO, most of the time the mapped code isn't wanted in these lists. So I prefer SE's behaviour.

3. "Copy to Project" is available on the context menu of a document in SE (e.g. a class) but is not offered on the context menu I get for the same document in AE. I think we need it on AE too as a convenient way of adding existing items to a project.

Joyce Zhang · Apr 11, 2016

Hi John,

Thanks for your feedback!

1. Yes, you're right - we're currently implementing the features to support for CSP files.

2 & 3. They're planned features - I will let you know when they're ready.

Best,

Joyce

2 0

John Murray · Oct 18, 2016

Any news on 2 and 3 yet? No sign of them in the latest build, 1.0.255.

0 0

Herman Slagman · Oct 18, 2016

I think your findings are very worrying.

I must confess I didn't do any Atelier testing myself (I don't like Eclipse, too premature, not enough time).

But six to four months later that some of these issues you reported still have no sign of progress...

Also that there is no 'formal' feedback of issues or roadmaps on Atelier.

Personally I think that ISC jumped on the Eclipse bandwagon five years too late. My choice in these days would have been Electron/Atom/MS VC but also keeping in mind that it could be totally different in four to five years time.

John Murray · Sep 22, 2017

Still hoping for 2 and 3. They haven't made it into the current public beta, 1.1.351.

John Murray · Jan 3, 2018

Congratulations to the Atelier team for releasing 1.1. However I'm still disappointed that suggestions #2 and #3 which I made more than 18 months ago haven't (yet) been taken up. IMO they'd significantly improve the usability of part of the Atelier Explorer (AE).

Nicole Aaron · Jan 3, 2018

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.

Thanks Nicole. I'll watch out for it.

John Murray · Feb 15, 2018

For the record, my original #2 is logged at ATL-3359 and currently slated for Atelier 1.5. My original #3 is logged as ATL-1934, also slated for Atelier 1.5.

Bill McCormick · Oct 31, 2016

Herman - there is a place to report issues. Its the same as anything else with our product. The WRC is fully supporting Atelier and issues are tracked in the same manner as any other part of the product. We are encouraging general conversation here because it is of benefit to everyone and not specific to Atelier as a policy point.

As for choosing Eclipse. It boils down to ecosystem. The editors you mention are all nice but none of them support the entire range of features we can get from Eclipse. You will note that by adopting a REST api we left it open for ourselves or anyone else to expand the functionality of any popular IDE on the market for use with our products.

3 0