Francis, I think the idea of the "Developer Community Feedback" community/group is to discuss the behaviour of this community.intersystems.com website software.
I think your posting belongs better in the "Caché" community/group because that is the base product from InterSystems in which COS is implemented, and upon which Ensemble, HealthShare and DeepSee (which each have a separate community/group) are built.
No, it even happens when I have no source control class set for the namespace (and have restarted my Studio after confirming that).
Odd then that when I click the Compile button the suffix disappears while compiling but then reappears afterwards, even though the Output tab reports successful compilation.
Here's what the Properties tab shows when I select my Samples project in Project Explorer:
Is yours not doing this? If not, what Atelier version do you have? Mine is 1.0.128
Atelier projects aren't really created in namespaces. But if you expand the project in the Atelier Explorer tab you'll see information about the connection it's associated with. An attribute of the connection is which namespace it connects to on the target server:
I updated to 1.0.123 today and things are starting to function in this area. I understand it's a work-in-progress, but I'm glad to start testing it.
The Tools menu now offers two options, "Add-Ins" and "Templates". Both lead to a dialog titled "AddIn Template Wizard". First wizard page asks me to choose which connection to use. Second page has subtrees titled "Recently Used", "Custom Used" and "Stanard Add-Ins" (sic).
"Stanard Add-Ins" lists the same entries as I get from the equivalent Studio dialog, which is cool!
Some of my own add-ins that appear in this list seem to work without requiring any changes - also cool!
I have one that fails in Atelier but works in Studio, so I've opened a WRC ticket.
Keep up the good work.
Understood. Consider me a beta tester of this feature, which is important to us at George James Software.
Thanks Jamie. That did the trick.
Thanks all. I enjoyed taking part, and am looking forward to Global Summit.
What's the $ZV of your cloud server?
When I tested debugging from Atelier 1.0.116 onto a local 2016.2FT Build 605 earlier today it wasn't working for me. So I upgraded the server to the latest build they're publishing (613) and that seems to have fixed the issue.
Excellent. Don't forget to get the 2016.1 FT section removed from https://wrc.intersystems.com/wrc/BetaPortal.csp
If I'd realized that I wonder if I could've used it to boost my score in the competition that just ended 
You mean we used to be able to post an article into more than one group? From my recollection of the previous UI it certainly wasn't obvious, but perhaps the list was multiselect. Either way it's now irrelevant since you've replaced that list with radiobuttons.
It happens to me too. For example, these four are showing on the enigmatic "My collaborations" page for me:
Adding to this, I'm not 100% clear on the relationship between Communities/Groups and Tags. Some tags seem to correspond to communities/groups, other tags don't. When I look at an arbitrary post and want to know what Community/Group it belongs to, how do I tell? Look for a tag that is also a community? What if more than one tag qualifies?
Good suggestion, though you somehow managed to post it in the Developer Community Feedback community/group rather than the Atelier one. There's still room for improvement in the DC's user interface.
I think you can edit your post and change what's selected in the Group list, setting it to "Atelier" instead of "Developer Community Feedback".
How about adding a DC version identifier somewhere? Perhaps in the page footer?
Checking for myself whether this is corrected. If after adding this comment the post date still displays correctly then it is.
I've been told that they're intending to offer Atelier as a plugin to an existing Eclipse IDE as well as giving us the standalone Atelier IDE. Just wondering how close that day is.
Great link Scott. Thanks!
How realtime is the leaderboard? My post from earlier today hasn't turned up there yet. Wondering if yesterday's DC update could have affected the data feed to it.
It'd be useful if "My Content" entries also showed info about number of answers, comments etc. in the usual place (highlighted below):
This is a good move.
Interesting that my browsers (FF and Chrome) stack the two "Related Topic" fields vertically:
Maybe your screenshot is from a newer version of DC?
That's certainly a useful tip. I wonder if it would have helped in a situation we assisted an Ensemble site with last year. They'd upgraded their DEV and QA environments from 2013.1 to 2015.1 but their LIVE was still on 2013.1. Then they amended an HL7 schema in DEV, exported it, imported it to QA, verified it worked, and finally loaded it to LIVE, where it broke the production.
The cause turned out to be a change made in 2014.1 and documented in a bullet point here. Yes, they had been unwise not to retain a QA or pre-live staging environment on the exact Ensemble version that LIVE was running.
I take your point about keeping up with the technology curve, but it's no good the next release of your app using all the whizzy new features of the latest Caché version if you're not able to deploy it to your customers until they can be coaxed to upgrade. Yes, you can use the new features as a carrot to entice them to upgrade, but meanwhile you probably have support commitments to them that mean occasionally patching the app release they're currently using.
I'm not advocating making your live environment the first one you upgrade. Upgrade a QA environment initially, and do enough testing there to be confident that your app works.
I have fixed the XS whitepaper link. Thanks for reporting that.
At analysis time you can choose which packages to include. The webapp whose time-based graphical output I showed above doesn't let you filter a whole-namespace analysis to view only the stats for a single package. But the Structure101g Studio tool gives a lot more power. For example, here's a drilldown into the top-level packages:
Overall bar length is code size. The red portion is the XS of the package.