[Contrib] Request for repo for a LaTeX Renderer/Export + architecture/plans

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Contrib] Request for repo for a LaTeX Renderer/Export + architecture/plans

vmassol
Administrator
Hi devs,

I’d like to work on a LaTeX Renderer + on an Export action for it. Thus I’m asking for a “latex” repo on contrib.

What I’m planning to do:

Step 1:

* Remove the "tex/1.0” syntax from xwiki-rendering. I don’t think it’s necessary to move it to xwiki-attic since it’s always been more of a quick POC than something usable
* Add a new “latex/1.0” syntax inside a new “latex” contrib repo: “latex/latex-syntax-10/“

Step 2:
* Idea: Implement a FilterStream app export filter for “latex”

Step 3:
* Provide an export URL for LaTeX that would use the FilterStream filter. Not sure yet about the implementation. Several ideas:
** Introduce a component role for the Exports we have (PDF, HTML, XAR, etc) to make them pluggable so that it’s possible to add new “export” actions. Or more generally, time permitting, refactor the “export” action as a EntityResourceAction component plugged in EntityResourceReferenceHandler
** Don’t use the “export” action and instead introduce a new type with a ResourceReferenceHandler (see https://www.xwiki.org/xwiki/bin/view/Documentation/DevGuide/Architecture/URL%20Architecture/).
** Don’t provide an “export” URL

Step 4:
* Integrate the export in the UI, using the “Export” menu UI. Would need a UIXP/XClass to make that extensible if that doesn’t already exist. Needs: be able to select page order, toc, list of tables, list of figures, page numbering, etc
* Other possibility (less nice): Don’t provide an “export” URL and instead tell users to use the generic FilterStream app when needing to export and if need be, in the future, provide a UI for it. However not sure how to ask the user for the list of pages to export, and the various questions (toc, list of tables, list of figures, page numbering, etc).

Thanks
-Vincent

Reply | Threaded
Open this post in threaded view
|

Re: [Contrib] Request for repo for a LaTeX Renderer/Export + architecture/plans

vmassol
Administrator


> On 17 Feb 2018, at 10:06, Vincent Massol <[hidden email]> wrote:
>
> Hi devs,
>
> I’d like to work on a LaTeX Renderer + on an Export action for it. Thus I’m asking for a “latex” repo on contrib.

I’ll create it.

Thanks
-Vincent

>
> What I’m planning to do:
>
> Step 1:
>
> * Remove the "tex/1.0” syntax from xwiki-rendering. I don’t think it’s necessary to move it to xwiki-attic since it’s always been more of a quick POC than something usable
> * Add a new “latex/1.0” syntax inside a new “latex” contrib repo: “latex/latex-syntax-10/“
>
> Step 2:
> * Idea: Implement a FilterStream app export filter for “latex”
>
> Step 3:
> * Provide an export URL for LaTeX that would use the FilterStream filter. Not sure yet about the implementation. Several ideas:
> ** Introduce a component role for the Exports we have (PDF, HTML, XAR, etc) to make them pluggable so that it’s possible to add new “export” actions. Or more generally, time permitting, refactor the “export” action as a EntityResourceAction component plugged in EntityResourceReferenceHandler
> ** Don’t use the “export” action and instead introduce a new type with a ResourceReferenceHandler (see https://www.xwiki.org/xwiki/bin/view/Documentation/DevGuide/Architecture/URL%20Architecture/).
> ** Don’t provide an “export” URL
>
> Step 4:
> * Integrate the export in the UI, using the “Export” menu UI. Would need a UIXP/XClass to make that extensible if that doesn’t already exist. Needs: be able to select page order, toc, list of tables, list of figures, page numbering, etc
> * Other possibility (less nice): Don’t provide an “export” URL and instead tell users to use the generic FilterStream app when needing to export and if need be, in the future, provide a UI for it. However not sure how to ask the user for the list of pages to export, and the various questions (toc, list of tables, list of figures, page numbering, etc).
>
> Thanks
> -Vincent
>