How could I add or edit sectiobType parameters ?

[Samar Ayesh]

Hello Ashok,

  Could you help me how to edit a sectionType parameters ?
 So that I have them compatible with AkomaNtoso version  ..

 Example:     <hcontainer id="">

I need to add a nother parameter "name"

[Ashok Hariharan]

How will the @name attribute be determined ? I guess programatically or via user input ?

so in terms of configuration in the section type, you just need :

     <metadatas>
         <metadata name="hcontainerName" />
     </metadatas>
     <output>
         <content>
            <an:hcontainer name="$hcontainerName" /> 
         </content>
     </output>

Then in the router you will have to set the parameter. So you would extend the routerCreateSection class and create something called, 

routerCreateHcontainer and within that set hcontainerName either via a dialog or via programatic determination ..

--
You received this message because you are subscribed to the Google Groups "bungeni-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bungeni-edito...@googlegroups.com.
To post to this group, send email to bungeni...@googlegroups.com.
Visit this group at http://groups.google.com/group/bungeni-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ashok Hariharan]

But tell me your exact use case ... i.e. how is the @name attribute determined (for e.g. if all the hcontainer types will have the same @name attribute  ? ) if that is the case i can add support for setting the value via configuration so you dont need to write any extended router classes ...

Ashok

[Ashok Hariharan]

See revision 3006 and the comment for that revsion ....added support
for doing this

On 4/4/13, Samar Ayesh <smr....@gmail.com> wrote:
> It's problematically determined .. that if it's hcontainer for chapters
> then @name="chapters" and if articles @name="articles" and so on
> we have the types .. books, parts, chapters, sections, articles .

>
> On Wednesday, April 3, 2013 5:18:06 PM UTC+3, Ashok Hariharan wrote:
>>
>> But tell me your exact use case ... i.e. how is the @name attribute
>> determined (for e.g. if all the hcontainer types will have the same @name
>>
>> attribute ? ) if that is the case i can add support for setting the value
>>
>> via configuration so you dont need to write any extended router classes
>> ...
>>
>> Ashok
>>
>>
>> On 3 April 2013 17:15, Ashok Hariharan

>> <as...@parliaments.info<javascript:>

>> > wrote:
>>
>>> How will the @name attribute be determined ? I guess programatically or
>>> via user input ?
>>>
>>> so in terms of configuration in the section type, you just need :
>>>
>>> <metadatas>
>>> <metadata name="hcontainerName" />
>>> </metadatas>
>>> <output>
>>> <content>
>>> <an:hcontainer name="$hcontainerName" />
>>> </content>
>>> </output>
>>>
>>>
>>> Then in the router you will have to set the parameter. So you would
>>> extend the routerCreateSection class and create something called,
>>> routerCreateHcontainer and within that set hcontainerName either via a
>>> dialog or via programatic determination ..
>>>
>>>
>>>
>>>
>>> On 3 April 2013 13:33, Samar Ayesh <smr....@gmail.com

>>> <javascript:>>wrote:

>>>
>>>> Hello Ashok,
>>>>
>>>> Could you help me how to edit a sectionType parameters ?
>>>> So that I have them compatible with AkomaNtoso version ..
>>>> Example: <hcontainer id="">
>>>>
>>>> I need to add a nother parameter "name"
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "bungeni-editor" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send

>>>> an email to bungeni-edito...@googlegroups.com <javascript:>.

>>>> To post to this group, send email to

>>>> bungeni...@googlegroups.com<javascript:>
>>>> .

>>>> Visit this group at
>>>> http://groups.google.com/group/bungeni-editor?hl=en.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>>
>>>
>>>
>>

--
Sent from my mobile device

[Samar Ayesh]

 Thanks alot Ashok .. I tried it and it worked successfully ...