exception_e

Please read about our groundbreaking v5 release here: https://medium.com/openemr/complete-meaningful-use-certifica...

It's an issue with Source forge. We're working on this.

matthewvita48 at gmail dot com

Hi. Appreciate your honest take.

> every feature made part of the page UI

OpenEMR is currently a web application that doesn't have an independent API (e.g.: REST API). There is a ticket in my modernization project to look into an old PR that adds a REST API (hasn't been touched in a while, but it appears to be on the right path... would love to have a volunteer for this... hint hint :) ). For now, the only way to use OpenEMR via a REST API would be to go through one of the professional vendors (http://open-emr.org/wiki/index.php/Professional_Support).

> Perhaps small clinics are not the intended en-users of OpenEMR?

OpenEMR is actually used in small clinics all over the world. Perhaps it's not suitable for every use case though (for example, I believe there is a lack features/modules for neurology specialists). Also depends on the version and what you have it configured to do (you have to do a good amount of reading and setup yourself. May even have to touch some code!).

Maybe it's not a bad idea in the long run. I would have a meeting with the team and talk about "stages":

1) Start to split out monolith in separate packages ("services")

2) Use RabbitMQ to "talk" between the services / Simply have one package that is the REST portion and reference the other packages inside of it (which aren't REST... just libraries, basically)

3) Patch up design flaws

4) Slowly move towards true microservices

Step 2 would be deploying everything as monolith but at least it's split up.

This gradual approach may just work for your team!

+1 on your point about React making progressive enhancement easier. This repo and related technologies are rather neat!

> The biggest argument seems to be laziness: "Progressive enhancement is hard, here's a term that I can apply liberally to give myself an excuse not to bother".

It's always going to come down to the requirements and an understanding of who is using your web app.

In some cases, you should absolutely optimize for PWA... Facebook, for example, is a webapp that considers users in developing countries with shotty networks. They also optimize for those with blindness.

Implementing those features in a webapp like Kibana (visualizer for elasticsearch data) would be a wasted effort given the user demographic and the purpose of the app.

TL;DR: "It depends"

EDIT: I just realized I may not have addressed your point " I don't see why it necessarily applies to webapps but not to websites.". I think the answer is simply "Webapps are inherently more complex than websites, therefore, more strict web requirements need to be met". This is an easy way to compartmentalize it, but isn't an absolute.

Correct. https://en.wikipedia.org/wiki/Betteridge's_law_of_headlines :)

I do see your point, but I personally like the delineation of "web app" being something that has higher modern web requirements and "website" being something that should work on something like IE9.

That is not to say that UX should be thrown out of the window for the former, of course.

I do agree that something like NYT shouldn't be a web app.

EDIT: I should mention that a lot of these things come down to requirements, of course. I don't think it's fair to say that every web app must be PWA compliant... it depends!

Could use some more people on a code modernization project I'm running for OpenEMR (free EHR solution that is used all over the world).

www.open-emr.org

Feel free to email me.

Believe me, I'm the first person to kindly point out that something is "Googlable" or, in the case of programming, direct someone to the docs. With this, I couldn't believe that Wikipedia would engage in such a unethical practice - didn't even search for it considering that Wikipedia is generally a great org.

Thanks for the info.

The thing that makes Wikipedia so special is the fact that the community strives to follow the guidelines they have set forth:

- https://en.wikipedia.org/wiki/Wikipedia:Your_first_article

- https://en.wikipedia.org/wiki/Wikipedia:Notability

- https://en.wikipedia.org/wiki/Wikipedia:Be_bold

I'm not saying that every Wikipedia article adheres to them, but generally speaking, the quality is good and bias is severely frowned upon. "Random" web pages on any given topic miss out on these guidelines and are generally non-collaborative.

Full disclosure: I'm a big fan/consumer of Wikipedia... absolutely love the philosophy behind it.

source?

Might not be a bad idea to mark this as "beta" on the website and list some of the roadmap ideas being worked on: https://github.com/ro31337/libretaxi#technical-roadmap-unord... to ease public concerns.

This is a _great_ idea, but it is really early on and needs a safety and open-source-friendly CC integration before being advertised in my opinion.

Thanks sz4kerto. I'm glad I got some thoughts here before posting that in their PR (I obviously won't post it now because of the points you brought up).

I guess a user that would be comfortable with b2d or vbox would just have those running anyways!

Note: for you question about X, please check out https://blog.jessfraz.com/post/docker-containers-on-the-desk...

It is very interesting. I don't want to intrude on their thread, but if others here vouch for this technique I'll politely ask them to look into the following:

- https://blog.jessfraz.com/post/docker-containers-on-the-desk...

- http://boot2docker.io/

...has anyone here ever used this approach with nix apps that need to run on Windows "natively"? Writing a powershell script to silently install boot2docker with this special docker image wouldn't be too difficult. The DarkTable folks don't seem interesting in maintaining Win builds so this may be the perfect workaround.

NOTE: I realize that `File > Open Image` may be non-trivial, but surely there's a way to mount a host<->guest folder (e.g.: When using the application, the workspace is located in `C:\Users\$whoami\Documents\DarkTable\.jpg`)

React is just the UI piece of the puzzle. Here's a nice description of when to use Redux:

"[Redux is justified when] you have a piece of data that needs to be used in multiple places in your app, and passing it via props makes your components break the single-responsibility principle (i.e. makes their interface make less sense)" (https://github.com/petehunt/react-howto/issues/12#issuecomme...)

This comment was written for Flux, but it is completely applicable for Redux.

When building something non-trivial, there are other pieces you'll want to pull in with React such as routing, messaging, etc.

E̶l̶l̶e̶n̶ ̶P̶a̶o̶ Spez should step down!

More than a little for my LG G3

Last sentence makes me a bit sick :)

I was keeping it high level because the person asking the question is a non-programmer. To your point though, I should have prefixed "correctly written" in front of C++.

Interesting aside: I just installed/ran Minetest and then compared it to Minecraft and Minecraft feels/looks a lot smoother on my basic HP laptop.

Sorry for the very literal answer. I honestly thought you were interested in how the coverage was calculated.

As an aside, I've worked on projects where coverage wasn't used and the rule was to "test the important bits" and I've also been on projects where coverage had to be >= ~98%. I wonder if a middle-ground approach would be effective.

The poster was commenting on the maintainability of the C++ code. Unfortunately, poorly written/structured code can still be as performant as well designed code.

As for your C++ vs Java question... put very simply, C++ will be faster than languages like Java when it comes to graphics and any software that is close to the hardware.

He/she probably used a tool to capture the coverage %.

Most people use Babel to write ES2015/ES7 code that turns into ES5 compatible code: http://babeljs.io/

You just "pied pipered" it :)

I encourage folks to stop wasting time on this flame war sub-thread and focus on choosing the right tool for the job.

...hopefully that quiets down the nonsense :)

I like Johnson (I agree with him about 70% of the time and think he has good character). There's no way he has a chance now that he wasn't included in the debates.

Effectively, there is no 3rd party this year :(

No, I'm saying that the "contribution activity" timeline thing is leaning towards information overload (hard to follow; there is a lot to look at). I felt that the last implementation (which focused on the high-level activities that one could click into) made sense.

I'm not a designer or anything so take my feedback with a grain of salt.

I'm liking the recent design changes, however, I don't like the new implementation of contrib. activity... information overload!