The words are well received by me. I have only been a developer for the past 5 years and still have a lot to learn. I do agree that the design is incomplete. I remember when one would have to manually go out of the calendar appointment and enter the patient then come back to the calendar and enter the appointment. I don’t know who built the incomplete process but it is better than it was but still not complete as you so pointed out.
Not being funny. It is people like you who come into the project and lend a helping hand which keeps the project moving forward. If you could implement the design and architectural changes. It would benefit everyone in the community and beyond.
I do wish to be a better developer but that, I have learned, takes time for some of use that are not gifted. I have seen some gifted people come into the project and then leave. I hope you stay around for a while. I could learn some good things from conversations like this.
When I am developing a process, I try to think of how an end user would use the program after I am done no matter my intent or thoughts. Some times I can and most time people end up doing things I could not imagine them doing.
The Weno module is one of those things that needs more safeguards in place. I see how people are using it and there are simple little things that are keeping user from having a great first experience but time and resources keep me from getting around to fixing the code. Most of the developers that contribute to the project are part timers. There are some that are full time but won’t commit work because we are all trying to have unique feature sets to attract customers. So, a lot of the good stuff gets held back because there is no money in giving everything away.
So, that is how we end up with the calendar like it is.
Thanks for writing back and hope to see you around.