Hi Pablo Ocean does work on the TD, but also intends to open source it. The only barrier to this is that some code has to be removed that connects to internal Ocean tools, also we need to check on any non-open source libs that might have been used. We are being slower on this than we should, but it should happen in the next few weeks. Agree with all your comments below.
With respect to rewriting the TD, the intention is to create a new tool that replaces the Archetype Editor and Template Designer, and implements all the logic of the ADL 1.5 workbench. Some work has been done on the core compiler, but not much on the tool. I have done some work estimates on this in the past, and believe it is a fairly serious piece of work that needs to be project-managed properly (i.e. by its developers) and componentised properly. A project will be announced fairly soon to do this, and all interested developers are invited to take part. Early discussions will centre on a component roadmap, team structure, and exact technology (e.g. Eclipse, Groovy, .... ). As a stopgap, the imminent open source availability of the TD should help with dealing with bugs like the one you report. hope this helps. - thomas On 31/05/2014 07:00, pablo pazos wrote: > Hi all (mostly Ocean guys :), in the last couple of months I've been > actively working to add support to OPTs in my software instead of > using archetypes directly as I was doing before. > > I'm very close to the full support for OPTs in software and I want to > get a smooth process from the creation/use of archetypes, creation of > templates, generation of OTPs and use of OTPs for UI generation, DB > schema generation, data validation and data querying. > > The only problem I have right now to get a smooth process is that the > Template Designer crashes from time to time. A while ago I asked why > the TD was crashing, and I think it was something about configuring > the archetype repos. I think the tool should be robust enough to not > crash and ask the user for the needed information. > > My main question here is if Ocean right now has any interest of > improve the TD (I think is a great tool and with little work it can be > very robust), because I want to use it as a reference tool for my > courses & workshops. What I can offer is to do detailed QA of all the > functionalities on the tool and report all the problems I can find. > > The other question would be if the TD source is open, because in the > case Ocean can't have someone fixing bugs on the TD, I can propose a > project in my university for students that can (re)write the TD with > Java technologies (I'm good with C# but I'm creating an open source > technology stack based on Java/Groovy/Grails). > > That second option will require more time for sure and the results > might not be 100% satisfactory. With the 1st option I think all the > community will benefit from it, but it will depend on the available > resources. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140531/fe80f0ec/attachment.html>
