Hello,
Le 7 août 2013 à 06:51, Pon Saravanan Bhoopathy a écrit :
> Hi,
>
> I completely new to this process, basically from VB.Net World.
>
> I have saw the sample pages, and downloaded the package from the web site. I have couple couple questions.
>
> 1. How can I install the package? Any step by step guide.
You can do XTiger XML template writing and testing directly from the file system as explained in :
http://ssire.github.io/axel/docs/AXEL-beta-userman.html
(the demo editor UI has changed a little since the explanations were written but it should be still applicable)
To install on a server see the last section Deploying the library (basically you just need to copy the files in the axel directory onto your server)
To understand how to write XTiger XML template you can start from this executive summary:
http://ssire.github.io/axel/docs/xtiger-summary.html
The AXEL project is still in its infancy concerning documentation and demos, it has a huge potential everywhere you need to edit structured data (aka XML) w/o exposing XML intricacies to the users. I am trying to do my best to keep progressing both at the code level and at the documentation level : )
> 2. Is that anyway to add inline formatting tags, like, bold, italic, superscript, spell check etc? I did not find any sample regarding this. Please suggest.
Currently when I need this type of formatting in production I use the 'wiki' filter on top of the 'text' plugin.
This is explained in this self-describing template :
http://ssire.github.io/axel/editor/editor.xhtml#filters/Wiki
For instance that's what is used to write the articles about AXEL such as:
http://ssire.github.io/axel/editor/editor.xhtml#samples/Article+../data/article/final.xml
> 3. Should need to build toolbar for this, or is that readyily available? Please suggest
The perfect solution would be to select a Rich Text Editor library and to embed it into AXEL as a plugin understanding / using the plugin API:
http://ssire.github.io/axel/docs/howto-plugins.html
However I must mention that I am still evolving the plugin API to make it easier for Javascript developers to create new plugins.
For instance I will submit soon a version with this Issue solved:
https://github.com/ssire/axel/issues/35 and I have a few other changes in mind. However nothing prevent somebody to code a Rich Text Editor plugin if needed, that would be very helpful. I just have delayed this because in all my customer's project at the moment we want a strict control other formatting and not let users typeset themselves documents, which is one incentive for using structured documents.
> Anciously waiting for your response.
Do not hesitate if you have questions, and to share your project with us,
Regards,
Stéphane S.
---