Note - I found a really cool feature in the latest version of Caché:
http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls…
So I could use a marker of &html[<my text here>] and it should work because a single > will not a an ending bracket.
However, I am currently stuck on Caché 2012.2. Does anyone know a way to do this on an older version?
Stefan - thanks for the feedback. I originally tried > but the problem is that then it writes out to the page as exactly as > so it is not a valid CSS selector.
I need it unescaped in my CSS in order to make it valid. So is there a way to have it not break the compiler but still print out in the source as ">"?
Thank you both!
Derek - Your second solution doesn't compile for some reason (that was my next try after I saw that > didn't work). Your first solution is what I had (temporarily) settled for but it put the > on a new line so it was really ugly in the source (and I wasn't sure if line breaks in CSS selectors was valid)
Fabian - your solution works very nicely, thank you!!
Tom - you need to click the "Favorite" tag at the top of the topic page, and that will subscribe you to that particular topic (the label will siwch to "Unsubscribe" once you).
It's not intuitive but it works (sort of - you can't do anything but digest subscription which leaves quite a bit to be desired)
I completely agree. This needs to be made much more clear
I completely agree!!
Confirmed - I see Tim's name in the tab title in Chrome when I go to that page (but I see my own points)
To echo what Tom said, this is becoming more and more critical for me as well. I really don't have time to click a link every time I get a Community update in order to see if its something I am interested in (or can contribute to) or not.
I also agree with the removal of the decoration, etc. Just the content with a link to the thread at the bottom of the email please.
Bravo - thank you Evgeny :)
+1 for this suggestion.
Scott - FYI, you can subscribe to the general forums so you automatically get notification on all new posts rather than having to manually mark something as Favorite to get new emails on that. Just a thought.
+1
I think that members should own their own content and be able to edit or delete it (just like Facebook)
Scott,
Code.InterSystems.com was launched but then not advertised because of the Developer Community effort. It is still supported and will remain open and available until such time as all functionality is available on the Developer Community and all content has been moved to make it accessible here. Feel free to make use of that site until you see announcements about it being moved. It works with InterSystems SSO so you can use your existing account.
Ben
Bravo Luca - this is great news for our customer base!
(moved)
Timur - what did you use for an RSS client? I usually use Thunderbird and I am told the feed is invalid.... :(
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 :)
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).
Benjamin,
You might be running into some security issues (check the audit DB to confirm). Or, you might not have it working because you have "Lock CSP Name" set to "Yes" in one of the web applications (ref: http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls…).
I just did a quick test as follows in my 2015.1 instance:
1) Created a SAMPLES2 namespace with new SAMPLES2 DB
2) Package mapped "csp" from SAMPLES namespace to SAMPLES2 namespace
3) Edited /csp/samples2 web application as follows:
- added Unauthenticated
- added %DB_SAMPLES Application Role
- Unchecked "Lock CSP Name" AND "Autocompile" (this should be done in both /csp/samples and /csp/samples2)
- pointed "CSP Files Physical Path" to c:\intersystems\e20151\csp\samples\
After this I was then able to see /csp/samples2/form.csp (although with errors because I didn't map the Samples.* package to the Samples Namespace).
So it appears to work - you just need to figure out which of the above pieces you missed :)
HTH!
Ben
Kenneth,
Check out /csp/samples/upload.csp
Does this cover what you need?
Great :)
Great article Stefan! I look forward to playing with this :)
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.
+1 :)
See https://community.intersystems.com/post/enterprise-manager-20162 and the attachment
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.
2016.1 is scheduled for release extremely soon (barring the last minute discovery of show-stopper bugs)
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 ;)
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!
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.
In fact, most COS programming guidelines that I have seen expressly forbid the use of GOTO since it makes the code harder to support.