My recent Ensemble posting here contains a wink emoji in its first sentence, but when rendered on the DC homepage summary list it shows as the text "wink".
Would it be possible to include more lines, and maybe even replace line breaks with a space, to allow you to view the posts that are made more efficiently?
For example, I clicked on Caché and noticed that almost everyone began with "Hi", which ended up not really allowing you to review any of the posts before diving deeper.
I was trying to find an article today that I knew had been posted about Wireshark installations causing problems with Studio and other Caché components. If I search the community for 'Wireshark install', the article I'm looking for does not even show up. I found it eventually in the text of one of the Digest post, but this is the article:
I know this has been suggested before but I wanted to bring it up again.
It would be very nice if we could "accept" an answer to our questions which would result in the question showing "answered" in the index and possibly move the "accepted answer" to the top of the answer chain.
I don't feel strongly enough about it to hate it, but I prefer the typical auto-complete, free-form tagging system seen on most sites (see StackOverflow for the perfect example). The nested dropdowns are just too cumbersome in my opinion.
On the "My Collaborations" tab of the "MY CONTENT" view I'm seeing some posts that I don't think I've commented on or even flagged as a favorite. So I'm wondering why they're there. Is Developer Community attempting some kind of AI? Or is there a data leak that's making it use comeone else's history?
Since yesterday the Google Group has started receiving postings from a user called intersystems.dc. These postings look like they're trying to replicate DC postings, though images don't appear. Nor are there any links leading across to DC, which is where the follow-up comments and answers are likely to appear.
Hi! I know that we have a layout for mobile devices, but it's broken on the pages with code snippets and another unfixed width content. Screenshots are attached.
I found that overflow property has 'auto' value, but the width (and max-width) property doesn't set for <pre>. Could you set max-width property for pre and other elements?
For example, these modified styles work fine for me on any screens for <pre> and <img> (with your media queries):
Since it took me a while to find the correct place to reply to a specific comment and not the post itself, I thought I'd make this observation an 'improvement request'.
Currently a comment has only the small grey arrow at the bottom, next to the 'favorite' button. The 'favorite' button has color and text which make it way more prominent. The 'reply' button on the other hand is gray and has no text. It's easy to miss.
I suggest adding at least text and perhaps also some color to the 'reply' button to make it stand out more. Even a tooltip would be useful.
I can view my own profile just fine, but if I try to view anyone else's, whether they're my friend or not, there's an HTTP 503 response and the following message shows up:
"Temporarily Unavailable
The website that you're trying to reach is having technical difficulties and is currently unavailable.
We are aware of the issue and are working hard to fix it. Thank you for your patience."
When looking at a single post there is no easy navigation to the overview of the category containing the post. I.e. having clicked on a single feedback post, there is no link back to the Feedback category overview.
I create a new blank post. Then I choose a group (I picked Caché). Next I click int the "Related Topics" field. At this point Firefox stops responding. It happens with FF 45.0.1 on 32-bit Windows and with 46.0.b7 on 64-bit Windows.
on the intersystems-data-platform-blog group as well as the developer-community-feedback group are more articles referenced than shown on the first page. But it is not possible to see further articles when going to the next page. After the click the page shows 'no content found' and the back button does not work anymore. This behaviour can be tricked adding '?page=1' after the url. On the main page community.intersystems.com the next page buttons work.
By replies
.png)
