Hi Pablo, A detailed problem report is the first step towards getting a bug fixed.
It?s possible that some of the problems you are finding have already been fixed if you are using an old version. Which version are you using? (The version is in the Help | About menu.) Peter On 3 Jun 2014, at 14:52, pablo pazos <pazospablo at hotmail.com<mailto:pazospablo at hotmail.com>> wrote: Hi Thomas, sorry for the delay, I'm moving out and the process is taking a lot of time. That's great! Maybe before open source it, I can help to improve robustness doing formal QA. With a robust TD we (the community) don't need an open source tool, but a free to use tool that we can rely on. Maybe after that, going open source is a good way to look for improvements. Also releasing design documentation (i.e. open architecture) so we can write our own ports to different technologies, that would be nice but I don't want to lose focus here! Going back to the current TD. IMO it would be good to have a robust TD with support to ADL 1.4, I think it should support current developments better before supporting next-gen standards like ADL 1.5. Of course, the focus is defined by Ocean and not by the community, just want to make a point that most of our platforms are 1.4 and may not support 1.5 in a while. In my case, I know that 1.5 will work for archetypes and OPTs, but since all my tooling is 1.4 and I'm just taking the next step into OPT, I see support for 1.5 archetypes and templates a little far away, mainly for my lack of resources and how slow I'm doing progress. Without knowing what's going on in the internals, my guess it most of the problems are related to missing validations at the GUI that violate internal constraints, with a mix of poor error handling (maybe not catching all the exceptions from the logic) so the app crashes very often. I really don't know if it's a lot of work to check out where the issues are if the test cases are fully reported (I can compromise myself on doing that if someone from Ocean can take a look at the code internally). Maybe this can take a couple of days and we can find/fix some dummy bugs that bother users with unhandled exceptions. If this is possible, we can coordinate to work on this, as I say, just for a couple of days to fix simple bugs and document more complex bugs. For QA I can make a video via Google hangout and show what I do step by step to get the errors and some issues I faced in the past about archetypes translation and OPT language. What do you think? -- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com<http://cabolabs.com/es/home><http://twitter.com/ppazos> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140603/556d3fe1/attachment.html>
