|
Type:
|
New Feature
|
|
Priority:
|
Medium
|
|
Severity:
|
Trivial
|
|
Status:
|
Closed
|
|
Resolution:
|
Complete
|
|
Resources:
|
Bob Denny
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Desktop Browser Help Content, RTML 2.3 .NET Assembly, RTML 2.3 Importer
|
|
Versions Affected:
|
3.7
|
|
Start Date:
|
11/18/2014
|
| Created: |
11/17/2014 10:19:47 AM |
| Revised: |
12/8/2014 2:12:20 PM
|
| Closed: |
12/4/2014 11:09:02 AM |
| Resolved: |
12/4/2014 11:08:59 AM |
|
This needs consideration. I developed a native .NET RTML generator in SCHEDULER-1243. This should eventually replace the XML_RTML23 because both it and the RTML Importer share the same Liquid-Generated object model. Well should I take the next step and make the Liquid model a separate assembly and reference it from a single common importer/generator assembly. How about one single assembly that does it all?
|
|
|
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?
