On May 31, 2015, at 11:11 AM, Hitesh Sofat <sofathit...@gmail.com> wrote:
> I am waiting your response. I have evaluated the A-F option like you > told. Please help me finalize the things soon. I wish to start coding > but I have not been able to do so this week. > > brlcad.org/wiki/User:Hitesh/option_for_docbook Hitesh, I have read through your write-up in detail. Good work on the pros/cons discussion. There is apparently still communication misunderstanding, however, as what you wrote was not what was asked. You did not define what the options “are" (i.e., A-F). You talk about current limitations — which is not relevant. Writing code to overcome a limitation is always an option. The question that needed to be answered for each potential option was to briefly describe how / what that option entailed from an implementation standpoint. Any options that do not explain a way to support one of the A-F questions inherently are non-options because they're incomplete — they don't address requirements. That means the items you listed as #1, #2, #3, and #6 are inadequate and would need to be redefined. I can tell this is frustrating for both. You were asked to complete a design task for which you probably don't have much experience, and that’s not fair to you. Instead of revisiting options, talking about code design further, fixing the page writeup, or evaluating options further, I suggest we simply proceed with the safest path that builds on our existing infrastructure. I’d characterize it as: Option #0: Custom Incremental A: add new xslt stylesheet for wordpress-themed output. cron compiles checkout. B: cron script moves compiled docs into web root, moves prior docs to backup dir. C: docs are theme-wrapped but static, similar to https://el-tramo.be/blog/integrating-docbook-with-wordpress/ and https://github.com/remko/docbook-kit/blob/master/style/wordpress/docbook.xsl D: web visitor custom edits the raw docbook. preview is rendered/compiled by backend. E: edited files are saved by web server to a holding directory (queue). F: developers log in to server and manually review queued changes. Basically, we can just host static content like we already have, but modify the stylesheet used during compile so that the theme used will be our wordpress theme. Then you can focus on implementing a simple custom edit form. Getting that working will be the most effort. Providing a preview option will be tricky, but you can probably just embed a link to the actual docbook file in the static output, with edited version rendered on-demand by server-side php. One cron script will be needed to actually publish docs. When you get that all done, we can then talk about how to best support multilingual translations. Please ask questions if any of that is unclear. Going this route will let us leverage some of the work you already did later (e.g., multilingual) and keep things as simple as possible. No complex integration/plugin limitations or issues. I should be available to discuss on Monday via IRC. Thank you for your efforts and continued patience. Cheers! Sean
------------------------------------------------------------------------------
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
