If you are planning on exporting to Excel and showing as a web page, I would suggest that you look at using Zen Reports.  It would give you the most control and you could get HTML, PDF and Excel all as output options.

Mike,

The UI, community elements and workflow are very much in flux at the moment - things are changing on a weekly basis as the platform gets refined to be more intuitive and to make it easier for people to connect and get their questions answered.  If you have time to play around and provide feedback, feel free!  But if you don't (and it's understandable) then you can continue to hang out in the Google Groups.  We won't be moving content and users over to the Developer Community until product management feel like it would be an advantageous move and that people will get all of the value that they get from the Google Groups.  

Note that there is a subcommunity which is specifically for providing feedback on the Developer Community so if you see something that you think could be improved, please make a post about it!

great progress Paul!

In fact, most COS programming guidelines that I have seen expressly forbid the use of GOTO since it makes the code harder to support.

Why would you want to limit it as the only formatting language used?  That would make it more difficult for people to add marked-up posts and could be a barrier to entry for people.  Providing different options makes it more accessible for people to  participate.

Stefan,

Is this always strickly the case?  Any web application that wants to add new UI capabilities which rely on REST needs to create a new csp application in order to do so?  

Thanks!

Scott - even though you may not have access to the SAMPLES namespace, you can still look at Caché samples.  Go to download.InterSystems.com and pull down a free single-user version of Caché and then you will have full access to everything that ships with Caché in your own local playspace ;)

2016.1 is scheduled for release extremely soon (barring the last minute discovery of show-stopper bugs)

I believe you can take paramaters for %Installer from a config file so you could make a page which creates the config file with the customer name, etc. 

See https://community.intersystems.com/post/enterprise-manager-20162 and the attachment

+1 :)

Scott - have you looked at %Installer?  That should be the first place that you start for trying to create a deployment from scratch.  This is how Ensemble, HealthShare and TrakCare instances get initialized by the installer and I know a lot of customers have used this with great success.

Also, the Enterprise Manager which is coming out in 2016.2 may be of interest in this area as well.

Great article Stefan!  I look forward to playing with this :)

Great :)

I asume since you used MyPage.csp in your example you are doing tag-based and not class-based CSP development?   

Remember that tag-based .csp files compile into classes within the namespace (by default these are csp.* classes).  So you could package-map csp.* (or whatever package you configure your CSP pages to compile into) from your Readonly namespace to the XYZ namespace, and then you could point the /csp/xyz application to the source directory holding the csp pages.  I think this is likely to do what you want (although I haven't tested it).  

It's a good point Evgeny, however I would still think that the benefit of letting people clarify their question or response outweighs the possibility of someone changing the content completely.

Also, once there is a proper up-vote and down-vote in place, people won't have to add "+1" comments anymore :)

Timur - what did you use for an RSS client?  I usually use Thunderbird and I am told the feed is invalid.... :(

(moved)