Hello! Will you be releasing any updates to the plug-in in the near future? I;m looking to actual move it into a production environment. I would always love to have your latest and greatest.
Thanks,
Jason
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We do have some updates planned to improve the layout and functionality of the reports generated by the plugin. I'm sorry I can't commit to an exact date, but hoping to get them out by the end of the year. I'd love to hear more about how you are using the plugin and any feedback you may have.
Hello! Will you be releasing any updates to the plug-in in the near future? I;m looking to actual move it into a production environment. I would always love to have your latest and greatest.
Cool. We just integrated it with our CMS, and it appears to be working well! We are really excited about your work here.
The one thing that I think you should revisit is the chunk=”to-content" requirement. While I completely understand the technical requirement, from a CMS perspective this change requires us to change and create a new revision of the content itself just to support the plug-in, and this change may not work well with our other output types, which are customer-facing. So my thought is that a content-checking plug-in should not require changes of the content but should rather handle its requirements internally.
Is it possible to pre-process the map file to include chunking as part of the plug-in's transformation?
I'll provide more feedback and we get more experience, but what you have done here is pretty awesome. And we're excited to use it and look forward to future developments.
Thanks,
Jason
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I totally agree that we need a better solution than requiring a specific @chunk value. We've looked at using xmltask (http://www.oopsconsultancy.com/software/xmltask/), but that has its own drawbacks. For another plugin, I used regex against the input file. I might look at that approach again for the QA plugin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello! Will you be releasing any updates to the plug-in in the near future? I;m looking to actual move it into a production environment. I would always love to have your latest and greatest.
Thanks,
Jason
Hi Jason,
We do have some updates planned to improve the layout and functionality of the reports generated by the plugin. I'm sorry I can't commit to an exact date, but hoping to get them out by the end of the year. I'd love to hear more about how you are using the plugin and any feedback you may have.
Patrick
Sent from my iPhone
On Oct 17, 2012, at 7:49 AM, "Jason Holmberg" holmbergius@users.sf.net wrote:
Cool. We just integrated it with our CMS, and it appears to be working well! We are really excited about your work here.
The one thing that I think you should revisit is the chunk=”to-content" requirement. While I completely understand the technical requirement, from a CMS perspective this change requires us to change and create a new revision of the content itself just to support the plug-in, and this change may not work well with our other output types, which are customer-facing. So my thought is that a content-checking plug-in should not require changes of the content but should rather handle its requirements internally.
Is it possible to pre-process the map file to include chunking as part of the plug-in's transformation?
I'll provide more feedback and we get more experience, but what you have done here is pretty awesome. And we're excited to use it and look forward to future developments.
Thanks,
Jason
I totally agree that we need a better solution than requiring a specific @chunk value. We've looked at using xmltask (http://www.oopsconsultancy.com/software/xmltask/), but that has its own drawbacks. For another plugin, I used regex against the input file. I might look at that approach again for the QA plugin.