Hello Soufiane, although your thank you is appreciated, an acceptance check is even more, because it alerts users with the same issue as you that a solution has been provided already.
You'll also help us if you use the same thread whenever you think about making a similar post. Don't create new threads if your subject is the same as the one you already created, or the community will start downvoting you.
Remember that downvoted threads have less chance of getting attention.
Keep creating posts with similar meaning and you'll get downvoted quickly. Although we are here to help you, you could at least try using the search feature and also recompensate us by checking the correct answer.
This is one of the reasons that I asked to bring some highlight to tutorials, since most of tutorials are related to community efforts or newer ISC technologies.
I think the community as a whole take some blame as well. Since Caché is robust enough to make us think that we can only use features provided and audited by ISC themselves., you can see that when comparing the number of questions with articles/anouncements.
So far, my impressions are that most of Caché developers prefer to take the safest route instead of trying what the community provides. There're exceptional projects as well, like WebTerminal but such projects still represent a minor part of us using it.
This subsequently results in open-source projects being abandoned due to the lack of interest as user and developer (maintainers). My proof when saying that is the amount of replies and attention a thread that presents a new project gets.
Also, if you don't want to lose time trying to convince your boss about open-sourcing a tool, do it outside and bring it to where you work. This way you'll be able to say that the project is your initiative and not something on behalf of the company you work. Just remember to design it in a way that won't use any business code.
Nice, but to prevent flooding the OP's e-mail inbox you could introduce an internal timer that gets triggered when a new answer is posted.
e.g., if I post a new thread asking for help with something. And someone posts an anwer, as I'm the OP I'll be notified by e-mail if I don't see the thread again within 15 minutes. If I still don't see the thread, wait another day and send the e-mail again.
Well, something like that.
Actually... forget my idea, I guess it would complicate and annoy OPs even more needlessly.
No. 5 means that instead of showing the editor that creates a reply, leave it hidden untill the user clicks Add new comment. This way this editor won't appear before the one that creates an answer.
Doing that, it's possible to prevent replies that should be an answer, so that they can be checked by the OP.
No 7. is simple, but I'll elaborate it to explain the why. I have noticed that the community contributes a lot with tutorials (including mine), but there's no way to classify them in that way, leaving them mixed with unrelated threads. Several times, these tutorials get lost because they disappear from the user's visibility, since they get pushed down by newer threads.
So if you introduce a tag or even a group to correlate them, it would make easier to search them.
As far as I know, VueJS uses property accessors to ovewrite set/get behavior. When AngularJS came out there wasn't an estabilished way of reproducing that, so who takes the blame here was the slower JavaScript development, untill ECMAScript 5 came out. Mostly because IE of course.
Not that I'm against using e-mail, however I think it's more resourceful if we keep the discussion opened for whoever has interest on participating. We could use the community forum as a start point and as the project expands into something solid we migrate to a github issue.
go to post
Kyle, https://community.intersystems.com/post/extract-string-value
go to post
And he goes and creates another one...
go to post
My first idea is to use a captcha service straight from China.
Something like this:
http://www.yinxiangma.com/
Maybe if you use some flag to fallback to this service instead of reCaptcha when the consumer originates from mainland China.
The only issue is that you might need a translator for support.
go to post
Hello Evgeny! Got it!
I'll leave it here.
go to post
Nope! Click on the check right before the "ANSWER" and you'll mark this answer as accepted. Remember that only you, the OP, can do it!
Accepting answers will move the answers counter up!
This way you don't even need to reply with a thanks, as we consider checking an answer and upvoting a post the same as that.
go to post
Hello Soufiane, although your thank you is appreciated, an acceptance check is even more, because it alerts users with the same issue as you that a solution has been provided already.
https://community.intersystems.com/post/convert-timestamp-its-correspond...
You'll also help us if you use the same thread whenever you think about making a similar post. Don't create new threads if your subject is the same as the one you already created, or the community will start downvoting you.
Remember that downvoted threads have less chance of getting attention.
go to post
Oh, ok. Should I update the https://community.intersystems.com/post/dc-improvement-ideas-not-official to use the Feedback group as well?
go to post
* Sighs *
Keep creating posts with similar meaning and you'll get downvoted quickly. Although we are here to help you, you could at least try using the search feature and also recompensate us by checking the correct answer.
go to post
You're referring that what you see as an OP, which is not the one who suffers with this problem.
Hide the editor that is X marked. Untill the user clicks Add new comment.
This way the circulated one is shown before.
And I just noticed that this gets worse when a question has many replies as each reply pushes the answer editor further below.
go to post
This is one of the reasons that I asked to bring some highlight to tutorials, since most of tutorials are related to community efforts or newer ISC technologies.
go to post
I think the community as a whole take some blame as well. Since Caché is robust enough to make us think that we can only use features provided and audited by ISC themselves., you can see that when comparing the number of questions with articles/anouncements.
So far, my impressions are that most of Caché developers prefer to take the safest route instead of trying what the community provides. There're exceptional projects as well, like WebTerminal but such projects still represent a minor part of us using it.
This subsequently results in open-source projects being abandoned due to the lack of interest as user and developer (maintainers). My proof when saying that is the amount of replies and attention a thread that presents a new project gets.
Also, if you don't want to lose time trying to convince your boss about open-sourcing a tool, do it outside and bring it to where you work. This way you'll be able to say that the project is your initiative and not something on behalf of the company you work. Just remember to design it in a way that won't use any business code.
go to post
Nice, but to prevent flooding the OP's e-mail inbox you could introduce an internal timer that gets triggered when a new answer is posted.
e.g., if I post a new thread asking for help with something. And someone posts an anwer, as I'm the OP I'll be notified by e-mail if I don't see the thread again within 15 minutes. If I still don't see the thread, wait another day and send the e-mail again.
Well, something like that.Actually... forget my idea, I guess it would complicate and annoy OPs even more needlessly.
go to post
Hello Evgeny! Sure!
No. 5 means that instead of showing the editor that creates a reply, leave it hidden untill the user clicks Add new comment. This way this editor won't appear before the one that creates an answer.
Doing that, it's possible to prevent replies that should be an answer, so that they can be checked by the OP.
No 7. is simple, but I'll elaborate it to explain the why. I have noticed that the community contributes a lot with tutorials (including mine), but there's no way to classify them in that way, leaving them mixed with unrelated threads. Several times, these tutorials get lost because they disappear from the user's visibility, since they get pushed down by newer threads.
So if you introduce a tag or even a group to correlate them, it would make easier to search them.
go to post
Have you ever heard about Open Collective?
go to post
Whoa! This is even better than what I suggested. Thank you whoever you are!
go to post
As far as I know, VueJS uses property accessors to ovewrite set/get behavior. When AngularJS came out there wasn't an estabilished way of reproducing that, so who takes the blame here was the slower JavaScript development, untill ECMAScript 5 came out. Mostly because IE of course.
go to post
In-depth comparison.
Note that I'm not saying what one has that other misses, I'm just exposing its strong points.
go to post
Added demo explaining stream usage. This ends the Part 1.
P.S.: No tag for tutorials?
go to post
Hello, sorry for the bump again.
I have updated the original post to include a tutorial. This is only the Part 1!
go to post
Hello Maks.
Not that I'm against using e-mail, however I think it's more resourceful if we keep the discussion opened for whoever has interest on participating. We could use the community forum as a start point and as the project expands into something solid we migrate to a github issue.