ref inline support (was Re: new configuration)

2 views

Skip to first unread message

Ashok Hariharan

unread,

Dec 14, 2012, 2:53:24 AM12/14/12

to bungeni...@googlegroups.com

I will be using this model for all inlines ... currently I make use of a mix of odf links etc in marking up (e.g. in tabled documents links in the debate ) ... but this is non-standard .. it makes more sense to use the core types everywhere.

On 13 December 2012 15:56, Ashok Hariharan <as...@parliaments.info> wrote:

Ok - i updated the middleware in r2813 ... but the following three updates fixed inline types :

http://code.google.com/p/bungeni-editor/source/detail?r=2813
http://code.google.com/p/bungeni-editor/source/detail?r=2812
http://code.google.com/p/bungeni-editor/source/detail?r=2811

So if you look at :
http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/inline_types/debaterecord.xml -- there is an example "ref" inline implementation there :

<?xml version="1.0" encoding="UTF-8"?>
<inlineTypes for="debaterecord" xmlns:an="#an">
<inlineType name="from">
<output>
<content>
<an:from />
</content>
</output>

</inlineType>

<inlineType name="ref">
<output>
<metadatas>
<metadata name="BungeniRefURI" />
</metadatas>
<content>
<an:ref href="$BungeniRefURI" />
</content>
</output>
</inlineType>

</inlineTypes>

The correspnding action configuration :

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/actions/doc_actions/debaterecord.xml
    <action name="mark_reference" source="inlineType" metadata="ref">
        <router class="org.bungeni.editor.actions.routers.routerInputReference" 
                dialog="refinline"
            />
    </action>
Which refers to a configured dialog set :
http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/actions/selector_dialogs.xml
  <dialog id="refinline" class="org.bungeni.editor.selectors.general.Main" >
        <dialog
            class="org.bungeni.editor.selectors.general.ref.RefURI"
             />
    </dialog>



The dialog for the "ref" markup provides a text field where you can input a URI / URL and thats implemented here :

org.bungeni.editor.selectors.general.ref.RefURI

The entry point for the action is in toolbar_actions/debaterecord.xml : 




          <action name="ref.general" mode="TEXT_SELECTED_INSERT" target="mark_reference"
          visible="true"
          condition="textSelected:true"
          title="REF_INLINE" tooltip="MARK_SELECTION_AS_INLINE_REF"> </action>
        

The output for the markup looks like this  : 

<speech bodf:sourceId="speech1" as="#MemberOfParliament" asText="MemberOfParliament" by="#JamesMuendo">



            <from bodf:sourceId="id687910772">Mr. James</from>
            <p>
               <ref bodf:sourceId="id1847723105" href="http://www.google.com">This</ref>is the speech</p>



         </speech>
On 13 December 2012 13:39, Samar Ayesh <smr....@gmail.com> wrote:

So it will be working fine after fixing middleware, right ?

On Thu, Dec 13, 2012 at 12:32 PM, Ashok Hariharan <as...@parliaments.info> wrote:

I actually realized yesterday that the implementation for inlineTypes
was only partially done .. I committed a part of the fix yesterday ...
there is a small bit remaining related to the middleware which i will
fix today.

If you notice yesterday the dialogs structure was changed slightly :

https://code.google.com/p/bungeni-editor/source/diff?spec=svn2812&r=2812&format=side&path=/BungeniEditor_configs/development_configs/actions/doc_actions/debaterecord.xml

the action router configuration does not directly refer to a dialog
class , earlier :
<action name="markup_bill">
<router class="org.bungeni.editor.actions.routers.routerSelectBill"
dialog="org.bungeni.editor.selector.dialogs.Bill.Main"/>
</action>

now :

<action name="markup_bill">
<router class="org.bungeni.editor.actions.routers.routerSelectBill"
dialog="billsMain"/>
</action>

You have to refer to the id of the dialog ...

On 12 December 2012 10:18, Samar Ayesh <say...@birzeit.edu> wrote:
> I found only one example for inlineType it's in debaterecord under core
> section but it didn't work ..
>
>
> On Tue, Dec 11, 2012 at 1:40 PM, Ashok Hariharan <as...@parliaments.info>
> wrote:
>>
>> Sure let me check and get back to you ... perhaps its broken ...
>>
>>
>> On 11 December 2012 14:31, Samar Ayesh <smr....@gmail.com> wrote:
>>>
>>> Ok, I'll see ..
>>> I'm asking about inline types .. like ref .. is there any implemented
>>> example?
>>>
>>>
>>> On Tue, Dec 11, 2012 at 1:21 PM, Ashok Hariharan <as...@parliaments.info>
>>> wrote:
>>>>
>>>> Sure .. proprietary was implemented last week :
>>>>
>>>>
>>>> https://groups.google.com/group/bungeni-editor/browse_thread/thread/1da6487200d203cb
>>>>
>>>> What issue were you having with inline types ?
>>>>
>>>> I am getting around to implementing an exampel for the TLC Organization
>>>> you had asked about ..
>>>>
>>>> Also see my note on this email :
>>>> https://groups.google.com/group/bungeni-editor/browse_thread/thread/10ed7aeff470780d
>>>>
>>>>
>>>>
>>>>
>>>> On 11 December 2012 13:36, Samar Ayesh <smr....@gmail.com> wrote:
>>>>>
>>>>> Hello Ashoke,
>>>>> is there a ready updates for proprietary metadata, any documentations?
>>>>> and what about inline section types?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Dec 5, 2012 at 10:21 AM, Samar Ayesh <smr....@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> OK :)
>>>>>>
>>>>>>
>>>>>> On Wed, Dec 5, 2012 at 9:27 AM, <as...@parliaments.info> wrote:
>>>>>>>
>>>>>>> Hang on .. I am going to commit it today ... the documentation is
>>>>>>> still not complete !
>>>>>>>
>>>>>>> Ashok
>>>>>>>
>>>>>>>
>>>>>>> On 5 December 2012 10:15, Samar Ayesh <say...@birzeit.edu> wrote:
>>>>>>>>
>>>>>>>> Hello Ashok,
>>>>>>>>
>>>>>>>> I just read the documentation about new namespaces (i.e:Proprietary)
>>>>>>>> http://code.google.com/p/bungeni-editor/source/detail?r=2785
>>>>>>>>
>>>>>>>> every thing there is clear..
>>>>>>>> but Is there any documentation explaining how can I deal with
>>>>>>>> section-types folder?? so that I can add "Proprietary" as a metadata,
>>>>>>>> or for this case we have to edit on system folder ??
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Dec 4, 2012 at 12:53 PM, <as...@parliaments.info> wrote:
>>>>>>>>>
>>>>>>>>> Hi Samar --
>>>>>>>>>
>>>>>>>>> I am testing it at the moment ... I hope to commit it today and
>>>>>>>>> update the documentation (this is for proprietary metadata support )
>>>>>>>>>
>>>>>>>>> Ashok
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 4 December 2012 13:07, Samar Ayesh <say...@birzeit.edu> wrote:
>>>>>>>>>>
>>>>>>>>>> Hello Ashok ,
>>>>>>>>>> Sorry for bothering you ... but is there any updates for the new
>>>>>>>>>> configuration?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>>>> The information contained in this communication is intended solely
>>>>>>>>>> for the use of the individual or entity to whom it is addressed and others
>>>>>>>>>> authorized to receive it. It may contain confidential or legally privileged
>>>>>>>>>> information. If you are not the intended recipient you are hereby notified
>>>>>>>>>> that any disclosure, copying, distribution or taking any action in reliance
>>>>>>>>>> on the contents of this information is strictly prohibited and may be
>>>>>>>>>> unlawful. If you have received this communication in error, please notify us
>>>>>>>>>> immediately by responding to this email and then delete it from your system.
>>>>>>>>>> The University is neither liable for the proper and complete transmission of
>>>>>>>>>> the information contained in this communication nor for any delay in its
>>>>>>>>>> receipt.
>>>>>>>>>>
>>>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>> The information contained in this communication is intended solely
>>>>>>>> for the use of the individual or entity to whom it is addressed and others
>>>>>>>> authorized to receive it. It may contain confidential or legally privileged
>>>>>>>> information. If you are not the intended recipient you are hereby notified
>>>>>>>> that any disclosure, copying, distribution or taking any action in reliance
>>>>>>>> on the contents of this information is strictly prohibited and may be
>>>>>>>> unlawful. If you have received this communication in error, please notify us
>>>>>>>> immediately by responding to this email and then delete it from your system.
>>>>>>>> The University is neither liable for the proper and complete transmission of
>>>>>>>> the information contained in this communication nor for any delay in its
>>>>>>>> receipt.
>>>>>>>>
>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ___________________________
>>>>>> Samar Ayesh
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ___________________________
>>>>> Samar Ayesh
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> ___________________________
>>> Samar Ayesh
>>>
>>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify us
> immediately by responding to this email and then delete it from your system.
> The University is neither liable for the proper and complete transmission of
> the information contained in this communication nor for any delay in its
> receipt.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--

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

--
___________________________
Samar Ayesh

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

Reply all

Reply to author

Forward

0 new messages