opening new windows in OPS

>-----Original Message-----
>From: Duane Gran [mailto:[hidden email]]
>Sent: 05 November 2006 02:16
>To: [hidden email]
>Subject: [ops-users] opening new windows in OPS
>
>If I read the documentation correctly, there is an f:url-type="new"  
>attribute on xforms:load which will spawn a new window when a
>trigger is activated.  I tried this and it didn't work.  There
>appear to be no included examples which make use of this
>functionality.  Questions:
>
>1) Am I correct in my understanding of f:url-type="new"?
>2) Is there a best practice for opening an existing instance
>in another window for further editing?
>
>To amplify on the second question, In order to manage space
>for data entry I want to open a new window for editing a
>portion of the document.
>
>Duane
>
>

>>
>>> 2) Is there a best practice for opening an existing instance in
>>> another window for further editing?
>>
>> By instance, do you mean an XForms instance? We now have a brand new
>> xxforms:dialog control that allows you to create nice dialogs (modal
>> or modeless) in XForms pages. Would that be a possibility for you?
>> What's your use case?
>>
>
> I need the new window to access the same XForms instance for editing a
> portion of the document.  The form is getting quite large and it would
> make things simpler to pop open a new window for further editing.  The
> dialog sounds nice, but I need something of arbitrary size.  If I use
> @show="new" on xforms:load will I have access to the same instance?

> Duane,
> you should be able to do xforms:load/@show="new"
>
> Ryan
>
> Ryan Puddephatt
> Software Engineer
>
> Teleflex Group - IT UK
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotland
> EH54 7DP
>
> e> [hidden email]
> t> +44(0)1506 407 110
> f> +44(0)1506 407 108
>
>
>
>> -----Original Message-----
>> From: Duane Gran [mailto:[hidden email]]
>> Sent: 05 November 2006 02:16
>> To: [hidden email]
>> Subject: [ops-users] opening new windows in OPS
>>
>> If I read the documentation correctly, there is an f:url-type="new"
>> attribute on xforms:load which will spawn a new window when a
>> trigger is activated.  I tried this and it didn't work.  There
>> appear to be no included examples which make use of this
>> functionality.  Questions:
>>
>> 1) Am I correct in my understanding of f:url-type="new"?
>> 2) Is there a best practice for opening an existing instance
>> in another window for further editing?
>>
>> To amplify on the second question, In order to manage space
>> for data entry I want to open a new window for editing a
>> portion of the document.
>>
>> Duane
>>
>>
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws

>>>
>> I need the new window to access the same XForms instance for  
>> editing a portion of the document.  The form is getting quite  
>> large and it would make things simpler to pop open a new window  
>> for further editing.  The dialog sounds nice, but I need something  
>> of arbitrary size.  If I use @show="new" on xforms:load will I  
>> have access to the same instance?
>
> I assume that you want to keep the source window open, right?
>
> @show="new" will open a new windows that is completely separate  
> from the window that opened it. The new XForms page will not share  
> anything with the origin XForms page, except if you go through lots  
> of manual hoops to get there (like storing the instance in the  
> session in the source page, then loading it from the session in the  
> new page, then passing back information to the source page). My  
> opinion on this kind of things is that using new windows as dialogs  
> is generally bad anyway.
>
> Dialogs can be about as big as the size of your browser window.

>
> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>
>>>>
>>> I need the new window to access the same XForms instance for  
>>> editing a portion of the document.  The form is getting quite  
>>> large and it would make things simpler to pop open a new window  
>>> for further editing.  The dialog sounds nice, but I need  
>>> something of arbitrary size.  If I use @show="new" on xforms:load  
>>> will I have access to the same instance?
>>
>> I assume that you want to keep the source window open, right?
>>
>> @show="new" will open a new windows that is completely separate  
>> from the window that opened it. The new XForms page will not share  
>> anything with the origin XForms page, except if you go through  
>> lots of manual hoops to get there (like storing the instance in  
>> the session in the source page, then loading it from the session  
>> in the new page, then passing back information to the source  
>> page). My opinion on this kind of things is that using new windows  
>> as dialogs is generally bad anyway.
>>
>> Dialogs can be about as big as the size of your browser window.
>
> Actually, it sounds like dialogs are the way to go.  Can you point  
> me to an example of this?  I see the blog announcement, but I'm not  
> sure how to implement this.
>
> Duane
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws

>-----Original Message-----
>From: Alexander Zatko [mailto:[hidden email]]
>Sent: 06 November 2006 17:04
>To: [hidden email]
>Subject: Re: [ops-users] opening new windows in OPS
>
>I implemented a dialog window by enclosing a "piece" of page
>that I let "float above" the page from which it was launched
>(using DHTML) within xforms:group that becomes relevant (and
>thus the content of the group becomes exposed as a dialog
>window) when a button is clicked. The beauty of this approach
>is that the content of the dialog window is still a part of
>the page, so it has "visibility" of the form instance... I can
>send you the code if you are interested.
>
>A.
>
>On Nov 6, 2006, at 5:00 PM, Duane Gran wrote:
>
>>
>> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>>
>>>>>
>>>> I need the new window to access the same XForms instance
>for editing
>>>> a portion of the document.  The form is getting quite large and it
>>>> would make things simpler to pop open a new window for further
>>>> editing.  The dialog sounds nice, but I need something of
>arbitrary
>>>> size.  If I use @show="new" on xforms:load will I have
>access to the
>>>> same instance?
>>>
>>> I assume that you want to keep the source window open, right?
>>>
>>> @show="new" will open a new windows that is completely
>separate from
>>> the window that opened it. The new XForms page will not share
>>> anything with the origin XForms page, except if you go through lots
>>> of manual hoops to get there (like storing the instance in the
>>> session in the source page, then loading it from the session in the
>>> new page, then passing back information to the source page). My
>>> opinion on this kind of things is that using new windows as dialogs
>>> is generally bad anyway.
>>>
>>> Dialogs can be about as big as the size of your browser window.
>>
>> Actually, it sounds like dialogs are the way to go.  Can you
>point me
>> to an example of this?  I see the blog announcement, but I'm
>not sure
>> how to implement this.
>>
>> Duane
>>
>>
>> --
>> You receive this message as a subscriber of the ops-
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
>> wws
>
>
>

> I implemented a dialog window by enclosing a "piece" of page that I let
> "float above" the page from which it was launched (using DHTML) within
> xforms:group that becomes relevant (and thus the content of the group
> becomes exposed as a dialog window) when a button is clicked. The beauty
> of this approach is that the content of the dialog window is still a
> part of the page, so it has "visibility" of the form instance... I can
> send you the code if you are interested.
>
> A.
>
> On Nov 6, 2006, at 5:00 PM, Duane Gran wrote:
>
>>
>> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>>
>>>>>
>>>> I need the new window to access the same XForms instance for editing
>>>> a portion of the document.  The form is getting quite large and it
>>>> would make things simpler to pop open a new window for further
>>>> editing.  The dialog sounds nice, but I need something of arbitrary
>>>> size.  If I use @show="new" on xforms:load will I have access to the
>>>> same instance?
>>>
>>> I assume that you want to keep the source window open, right?
>>>
>>> @show="new" will open a new windows that is completely separate from
>>> the window that opened it. The new XForms page will not share
>>> anything with the origin XForms page, except if you go through lots
>>> of manual hoops to get there (like storing the instance in the
>>> session in the source page, then loading it from the session in the
>>> new page, then passing back information to the source page). My
>>> opinion on this kind of things is that using new windows as dialogs
>>> is generally bad anyway.
>>>
>>> Dialogs can be about as big as the size of your browser window.
>>
>> Actually, it sounds like dialogs are the way to go.  Can you point me
>> to an example of this?  I see the blog announcement, but I'm not sure
>> how to implement this.
>>
>> Duane
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> Duane,
> You can view example code at
> http://cvs.forge.objectweb.org/cgi-bin/viewcvs.cgi/*checkout*/ops/ 
> orbeon/src
> /examples/xforms/dialog.xhtml?rev=1.6&only_with_tag=MAIN&content-
> type=text/p
> lain
>
> Which is included with the CVS dl of OPS if you use that
>
> Ryan
>
> Ryan Puddephatt
> Software Engineer
>
> Teleflex Group - IT UK
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotland
> EH54 7DP
>
> e> [hidden email]
> t> +44(0)1506 407 110
> f> +44(0)1506 407 108
>
>
>
>> -----Original Message-----
>> From: Alexander Zatko [mailto:[hidden email]]
>> Sent: 06 November 2006 17:04
>> To: [hidden email]
>> Subject: Re: [ops-users] opening new windows in OPS
>>
>> I implemented a dialog window by enclosing a "piece" of page
>> that I let "float above" the page from which it was launched
>> (using DHTML) within xforms:group that becomes relevant (and
>> thus the content of the group becomes exposed as a dialog
>> window) when a button is clicked. The beauty of this approach
>> is that the content of the dialog window is still a part of
>> the page, so it has "visibility" of the form instance... I can
>> send you the code if you are interested.
>>
>> A.
>>
>> On Nov 6, 2006, at 5:00 PM, Duane Gran wrote:
>>
>>>
>>> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>>>
>>>>>>
>>>>> I need the new window to access the same XForms instance
>> for editing
>>>>> a portion of the document.  The form is getting quite large and it
>>>>> would make things simpler to pop open a new window for further
>>>>> editing.  The dialog sounds nice, but I need something of
>> arbitrary
>>>>> size.  If I use @show="new" on xforms:load will I have
>> access to the
>>>>> same instance?
>>>>
>>>> I assume that you want to keep the source window open, right?
>>>>
>>>> @show="new" will open a new windows that is completely
>> separate from
>>>> the window that opened it. The new XForms page will not share
>>>> anything with the origin XForms page, except if you go through lots
>>>> of manual hoops to get there (like storing the instance in the
>>>> session in the source page, then loading it from the session in the
>>>> new page, then passing back information to the source page). My
>>>> opinion on this kind of things is that using new windows as dialogs
>>>> is generally bad anyway.
>>>>
>>>> Dialogs can be about as big as the size of your browser window.
>>>
>>> Actually, it sounds like dialogs are the way to go.  Can you
>> point me
>>> to an example of this?  I see the blog announcement, but I'm
>> not sure
>>> how to implement this.
>>>
>>> Duane
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the ops-
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/
>>> wws
>>
>>
>>
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws

> Alex,
>
> This is pretty much what xxforms:dialog does, except you don't have  
> to worry about the details (like styling, centering, making it  
> modal or modeless, etc.).
>
> -Erik
>
> Alexander Zatko wrote:
>> I implemented a dialog window by enclosing a "piece" of page that  
>> I let "float above" the page from which it was launched (using  
>> DHTML) within xforms:group that becomes relevant (and thus the  
>> content of the group becomes exposed as a dialog window) when a  
>> button is clicked. The beauty of this approach is that the content  
>> of the dialog window is still a part of the page, so it has  
>> "visibility" of the form instance... I can send you the code if  
>> you are interested.
>> A.
>> On Nov 6, 2006, at 5:00 PM, Duane Gran wrote:
>>>
>>> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>>>
>>>>>>
>>>>> I need the new window to access the same XForms instance for  
>>>>> editing a portion of the document.  The form is getting quite  
>>>>> large and it would make things simpler to pop open a new window  
>>>>> for further editing.  The dialog sounds nice, but I need  
>>>>> something of arbitrary size.  If I use @show="new" on  
>>>>> xforms:load will I have access to the same instance?
>>>>
>>>> I assume that you want to keep the source window open, right?
>>>>
>>>> @show="new" will open a new windows that is completely separate  
>>>> from the window that opened it. The new XForms page will not  
>>>> share anything with the origin XForms page, except if you go  
>>>> through lots of manual hoops to get there (like storing the  
>>>> instance in the session in the source page, then loading it from  
>>>> the session in the new page, then passing back information to  
>>>> the source page). My opinion on this kind of things is that  
>>>> using new windows as dialogs is generally bad anyway.
>>>>
>>>> Dialogs can be about as big as the size of your browser window.
>>>
>>> Actually, it sounds like dialogs are the way to go.  Can you  
>>> point me to an example of this?  I see the blog announcement, but  
>>> I'm not sure how to implement this.
>>>
>>> Duane
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the ops-
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://
>>> www.objectweb.org/wws
>> ---------------------------------------------------------------------
>> ---
>> --
>> You receive this message as a subscriber of the ops-
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://
>> www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws

> Erik,
>
> That's good news. I wanted to take a look at the sample Ryan provided a
> link for and it is not running in the ops sandbox at
> http://www.orbeon.com/ops/. I assume that the OPS version you have there
> does not understand the xxforms:dialog?
>
> A.
>
> On Nov 6, 2006, at 6:52 PM, Erik Bruchez wrote:
>
>> Alex,
>>
>> This is pretty much what xxforms:dialog does, except you don't have to
>> worry about the details (like styling, centering, making it modal or
>> modeless, etc.).
>>
>> -Erik
>>
>> Alexander Zatko wrote:
>>> I implemented a dialog window by enclosing a "piece" of page that I
>>> let "float above" the page from which it was launched (using DHTML)
>>> within xforms:group that becomes relevant (and thus the content of
>>> the group becomes exposed as a dialog window) when a button is
>>> clicked. The beauty of this approach is that the content of the
>>> dialog window is still a part of the page, so it has "visibility" of
>>> the form instance... I can send you the code if you are interested.
>>> A.
>>> On Nov 6, 2006, at 5:00 PM, Duane Gran wrote:
>>>>
>>>> On Nov 6, 2006, at 10:36 AM, Erik Bruchez wrote:
>>>>
>>>>>>>
>>>>>> I need the new window to access the same XForms instance for
>>>>>> editing a portion of the document.  The form is getting quite
>>>>>> large and it would make things simpler to pop open a new window
>>>>>> for further editing.  The dialog sounds nice, but I need something
>>>>>> of arbitrary size.  If I use @show="new" on xforms:load will I
>>>>>> have access to the same instance?
>>>>>
>>>>> I assume that you want to keep the source window open, right?
>>>>>
>>>>> @show="new" will open a new windows that is completely separate
>>>>> from the window that opened it. The new XForms page will not share
>>>>> anything with the origin XForms page, except if you go through lots
>>>>> of manual hoops to get there (like storing the instance in the
>>>>> session in the source page, then loading it from the session in the
>>>>> new page, then passing back information to the source page). My
>>>>> opinion on this kind of things is that using new windows as dialogs
>>>>> is generally bad anyway.
>>>>>
>>>>> Dialogs can be about as big as the size of your browser window.
>>>>
>>>> Actually, it sounds like dialogs are the way to go.  Can you point
>>>> me to an example of this?  I see the blog announcement, but I'm not
>>>> sure how to implement this.
>>>>
>>>> Duane
>>>>
>>>>
>>>> --You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>> ------------------------------------------------------------------------
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>>
>> --Orbeon - XForms Everywhere:
>> http://www.orbeon.com/blog/
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> Duane,
>
>> Thank you for passing this along.  The dialog looks well-suited to  
>> what I want to do, but I believe I found a bug where it doesn't  
>> work if enclosed inside an xforms:repeat.  I'm attaching a  
>> modified version of the linked sample below.  Maybe I'm  
>> overlooking something obvious.
>> I tried to run it in the sandbox at orbeon.com, but it appears to  
>> not be running the nightly build with xxforms:dialog support.  
>> Suggestions are most welcome on this, as I need to enclose this  
>> inside a repeat.
>
> Dialogs have to be at the top-level: they can't be in any other  
> XForms controls. You control their appearance of disappearance with  
> two actions xxforms:show/@dialog="dialogId" and xxforms:hide/
> @dialog="dialogId".
>

>-----Original Message-----
>From: Duane Gran [mailto:[hidden email]]
>Sent: 06 November 2006 20:31
>To: [hidden email]
>Subject: Re: [ops-users] opening new windows in OPS
>
>
>On Nov 6, 2006, at 3:11 PM, Erik Bruchez wrote:
>
>> Duane,
>>
>>> Thank you for passing this along.  The dialog looks well-suited to
>>> what I want to do, but I believe I found a bug where it
>doesn't work
>>> if enclosed inside an xforms:repeat.  I'm attaching a modified
>>> version of the linked sample below.  Maybe I'm overlooking
>something
>>> obvious.
>>> I tried to run it in the sandbox at orbeon.com, but it appears to  
>>> not be running the nightly build with xxforms:dialog support.  
>>> Suggestions are most welcome on this, as I need to enclose this
>>> inside a repeat.
>>
>> Dialogs have to be at the top-level: they can't be in any
>other XForms
>> controls. You control their appearance of disappearance with two
>> actions xxforms:show/@dialog="dialogId" and xxforms:hide/
>> @dialog="dialogId".
>>
>I see.  Let me amplify a little on my use case and maybe you
>can tell me if a dialog will still work.  I have an XML
>document which defines  
>a series of "volumes", each of which has dozens of child elements.  
>For every volume I want a link in the user interface which
>opens up a window for editing the given volume.  Additionally,
>I want a button to create a new volume.
>
>Does this make sense?
>
>Duane
>
>

> Duane,
> You could use one dialog, which is linked to an instance only used
> by the dialog. Then when you open the dialog from within ur repeat  
> you could
> set the values of the dialog instance from the selected repeat.  
> Does that
> make sense? Either that or you could try and create an xpath for  
> the a group
> within the dialog that returns the selected repeat, then you could  
> ignore
> the setvalues etc. :-)
>
> Ryan
>
> Ryan Puddephatt
> Software Engineer
>
> Teleflex Group - IT UK
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotland
> EH54 7DP
>
> e> [hidden email]
> t> +44(0)1506 407 110
> f> +44(0)1506 407 108
>
>
>
>> -----Original Message-----
>> From: Duane Gran [mailto:[hidden email]]
>> Sent: 06 November 2006 20:31
>> To: [hidden email]
>> Subject: Re: [ops-users] opening new windows in OPS
>>
>>
>> On Nov 6, 2006, at 3:11 PM, Erik Bruchez wrote:
>>
>>> Duane,
>>>
>>>> Thank you for passing this along.  The dialog looks well-suited to
>>>> what I want to do, but I believe I found a bug where it
>> doesn't work
>>>> if enclosed inside an xforms:repeat.  I'm attaching a modified
>>>> version of the linked sample below.  Maybe I'm overlooking
>> something
>>>> obvious.
>>>> I tried to run it in the sandbox at orbeon.com, but it appears to
>>>> not be running the nightly build with xxforms:dialog support.
>>>> Suggestions are most welcome on this, as I need to enclose this
>>>> inside a repeat.
>>>
>>> Dialogs have to be at the top-level: they can't be in any
>> other XForms
>>> controls. You control their appearance of disappearance with two
>>> actions xxforms:show/@dialog="dialogId" and xxforms:hide/
>>> @dialog="dialogId".
>>>
>> I see.  Let me amplify a little on my use case and maybe you
>> can tell me if a dialog will still work.  I have an XML
>> document which defines
>> a series of "volumes", each of which has dozens of child elements.
>> For every volume I want a link in the user interface which
>> opens up a window for editing the given volume.  Additionally,
>> I want a button to create a new volume.
>>
>> Does this make sense?
>>
>> Duane
>>
>>
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws

>-----Original Message-----
>From: Duane Gran [mailto:[hidden email]]
>Sent: 07 November 2006 13:28
>To: [hidden email]
>Subject: Re: [ops-users] opening new windows in OPS
>
>Ryan,
>
>Thank you for the suggestions.  Because I'm dealing with a
>non- trivial amount of elements and form controls (>35) I
>think the first approach may be tedious, unless there is a
>simple way to copy all values from one subtree to another.
>
>I'm intrigued by the second approach, but I don't really understand it.
>
>Duane
>
>On Nov 6, 2006, at 6:35 PM, Ryan Puddephatt wrote:
>
>> Duane,
>> You could use one dialog, which is linked to an
>instance only used by
>> the dialog. Then when you open the dialog from within ur repeat you
>> could set the values of the dialog instance from the selected repeat.
>> Does that
>> make sense? Either that or you could try and create an xpath
>for the a
>> group within the dialog that returns the selected repeat, then you
>> could ignore the setvalues etc. :-)
>>
>> Ryan
>>
>> Ryan Puddephatt
>> Software Engineer
>>
>> Teleflex Group - IT UK
>> 1 Michaelson Square
>> Livingston
>> West Lothian
>> Scotland
>> EH54 7DP
>>
>> e> [hidden email]
>> t> +44(0)1506 407 110
>> f> +44(0)1506 407 108
>>
>>
>>
>>> -----Original Message-----
>>> From: Duane Gran [mailto:[hidden email]]
>>> Sent: 06 November 2006 20:31
>>> To: [hidden email]
>>> Subject: Re: [ops-users] opening new windows in OPS
>>>
>>>
>>> On Nov 6, 2006, at 3:11 PM, Erik Bruchez wrote:
>>>
>>>> Duane,
>>>>
>>>>> Thank you for passing this along.  The dialog looks
>well-suited to
>>>>> what I want to do, but I believe I found a bug where it
>>> doesn't work
>>>>> if enclosed inside an xforms:repeat.  I'm attaching a modified
>>>>> version of the linked sample below.  Maybe I'm overlooking
>>> something
>>>>> obvious.
>>>>> I tried to run it in the sandbox at orbeon.com, but it appears to
>>>>> not be running the nightly build with xxforms:dialog support.
>>>>> Suggestions are most welcome on this, as I need to enclose this
>>>>> inside a repeat.
>>>>
>>>> Dialogs have to be at the top-level: they can't be in any
>>> other XForms
>>>> controls. You control their appearance of disappearance with two
>>>> actions xxforms:show/@dialog="dialogId" and xxforms:hide/
>>>> @dialog="dialogId".
>>>>
>>> I see.  Let me amplify a little on my use case and maybe
>you can tell
>>> me if a dialog will still work.  I have an XML document
>which defines
>>> a series of "volumes", each of which has dozens of child elements.
>>> For every volume I want a link in the user interface which
>opens up a
>>> window for editing the given volume.  Additionally, I want a button
>>> to create a new volume.
>>>
>>> Does this make sense?
>>>
>>> Duane
>>>
>>>
>>
>>
>>
>> --
>> You receive this message as a subscriber of the ops-
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
>> wws
>
>
>

> Duane,
> it all depends on the structure of your XML, but if you had
> something like :
>
> <instance>
> <item>
> <field1/>
> <field2/>...
> </item>...
> </instance>
>
> And your repeat iterates the <item>. You could create a group in your
> xxforms:dialog like so
>
> <xforms:group ref="/instance/item[position() = index('repeat-id')]">
>
> Which will give you the context of the currently selected repeat  
> item, then
> all you need is a button on each line that opens the dialog.
>
> Ryan
>
> Ryan Puddephatt
> Software Engineer
>
> Teleflex Group - IT UK
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotland
> EH54 7DP
>
> e> [hidden email]
> t> +44(0)1506 407 110
> f> +44(0)1506 407 108
>
>
>
>> -----Original Message-----
>> From: Duane Gran [mailto:[hidden email]]
>> Sent: 07 November 2006 13:28
>> To: [hidden email]
>> Subject: Re: [ops-users] opening new windows in OPS
>>
>> Ryan,
>>
>> Thank you for the suggestions.  Because I'm dealing with a
>> non- trivial amount of elements and form controls (>35) I
>> think the first approach may be tedious, unless there is a
>> simple way to copy all values from one subtree to another.
>>
>> I'm intrigued by the second approach, but I don't really  
>> understand it.
>>
>> Duane
>>
>> On Nov 6, 2006, at 6:35 PM, Ryan Puddephatt wrote:
>>
>>> Duane,
>>> You could use one dialog, which is linked to an
>> instance only used by
>>> the dialog. Then when you open the dialog from within ur repeat you
>>> could set the values of the dialog instance from the selected  
>>> repeat.
>>> Does that
>>> make sense? Either that or you could try and create an xpath
>> for the a
>>> group within the dialog that returns the selected repeat, then you
>>> could ignore the setvalues etc. :-)
>>>
>>> Ryan
>>>
>>> Ryan Puddephatt
>>> Software Engineer
>>>
>>> Teleflex Group - IT UK
>>> 1 Michaelson Square
>>> Livingston
>>> West Lothian
>>> Scotland
>>> EH54 7DP
>>>
>>> e> [hidden email]
>>> t> +44(0)1506 407 110
>>> f> +44(0)1506 407 108
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Duane Gran [mailto:[hidden email]]
>>>> Sent: 06 November 2006 20:31
>>>> To: [hidden email]
>>>> Subject: Re: [ops-users] opening new windows in OPS
>>>>
>>>>
>>>> On Nov 6, 2006, at 3:11 PM, Erik Bruchez wrote:
>>>>
>>>>> Duane,
>>>>>
>>>>>> Thank you for passing this along.  The dialog looks
>> well-suited to
>>>>>> what I want to do, but I believe I found a bug where it
>>>> doesn't work
>>>>>> if enclosed inside an xforms:repeat.  I'm attaching a modified
>>>>>> version of the linked sample below.  Maybe I'm overlooking
>>>> something
>>>>>> obvious.
>>>>>> I tried to run it in the sandbox at orbeon.com, but it appears to
>>>>>> not be running the nightly build with xxforms:dialog support.
>>>>>> Suggestions are most welcome on this, as I need to enclose this
>>>>>> inside a repeat.
>>>>>
>>>>> Dialogs have to be at the top-level: they can't be in any
>>>> other XForms
>>>>> controls. You control their appearance of disappearance with two
>>>>> actions xxforms:show/@dialog="dialogId" and xxforms:hide/
>>>>> @dialog="dialogId".
>>>>>
>>>> I see.  Let me amplify a little on my use case and maybe
>> you can tell
>>>> me if a dialog will still work.  I have an XML document
>> which defines
>>>> a series of "volumes", each of which has dozens of child elements.
>>>> For every volume I want a link in the user interface which
>> opens up a
>>>> window for editing the given volume.  Additionally, I want a button
>>>> to create a new volume.
>>>>
>>>> Does this make sense?
>>>>
>>>> Duane
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the ops-
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/
>>> wws
>>
>>
>>
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws