RE: [flexcoders] Modeless editing
You could have your edit form in a modal popup window. That would prevent navigation until the popup form is closed/saved? From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Richard Rodseth Sent: Thursday, 5 March 2009 10:50 a.m. To: flexcoders@yahoogroups.com Subject: [flexcoders] Modeless editing Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes?
Re: [flexcoders] Modeless editing
Thanks, but I'm specifically looking for an alternative to modal dialogs. On Wed, Mar 4, 2009 at 2:33 PM, Wildbore, Brendon b.j.wildb...@massey.ac.nz wrote: You could have your edit form in a modal popup window. That would prevent navigation until the popup form is closed/saved? -- *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On Behalf Of *Richard Rodseth *Sent:* Thursday, 5 March 2009 10:50 a.m. *To:* flexcoders@yahoogroups.com *Subject:* [flexcoders] Modeless editing Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes?
Re: [flexcoders] Modeless editing
What i do is track user changes by setting some flags (plural because i need to save bits of changes not everything on the form in one go). If the user tries to get away from the tab/form, i stop the event and throw a confirm alert box saying that there are changes that need to be saved. If he clicks i do not care for lost changes i let the navigation continue, else you can either just hide the alert box, or save any changes and then move to the new area... On Wed, Mar 4, 2009 at 11:50 PM, Richard Rodseth rrods...@gmail.com wrote: Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes? -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com,
Re: [flexcoders] Modeless editing
So your basic approach is capturing all events elsewhere in the app, and stopping them. I was thinking along the lines of a navigationmanager which knows about a current editing context, and could also be tied into deep linking support. View state (selected tab, selected child of view stack) would be derived from properties of the navigation manager. When the NM receives a nav request (via bubbling event) it would check if the current editing context was valid and not proceed with the nav. Doing all this with the help of Mate dependency injection shouldn't be too hard. At the same time, since time is limited, I wish there was a simple way to apply an event mask the way popup manager does, while still allowing resizing layout to occur. Or alternatively, grab a kind of focus for a container that the framework would try to request if the user clicked elsewhere. In other words, make a component modal in place without popping up a new window. I haven't actually studied FocusManager, so I don't know if it supports any sort of nested focus. On Wed, Mar 4, 2009 at 2:54 PM, Fotis Chatzinikos fotis.chatzini...@gmail.com wrote: What i do is track user changes by setting some flags (plural because i need to save bits of changes not everything on the form in one go). If the user tries to get away from the tab/form, i stop the event and throw a confirm alert box saying that there are changes that need to be saved. If he clicks i do not care for lost changes i let the navigation continue, else you can either just hide the alert box, or save any changes and then move to the new area... On Wed, Mar 4, 2009 at 11:50 PM, Richard Rodseth rrods...@gmail.comwrote: Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes? -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com,
Re: [flexcoders] Modeless editing
I have not tried this, but if you are able to catch the hide event of the 'editing area' and cancel it, it would be far easier to implement what you describe...I do not have access to my builder at the moment so i do not know if what i suggest is doable... Have a go if you like :-) On Thu, Mar 5, 2009 at 1:19 AM, Richard Rodseth rrods...@gmail.com wrote: So your basic approach is capturing all events elsewhere in the app, and stopping them. I was thinking along the lines of a navigationmanager which knows about a current editing context, and could also be tied into deep linking support. View state (selected tab, selected child of view stack) would be derived from properties of the navigation manager. When the NM receives a nav request (via bubbling event) it would check if the current editing context was valid and not proceed with the nav. Doing all this with the help of Mate dependency injection shouldn't be too hard. At the same time, since time is limited, I wish there was a simple way to apply an event mask the way popup manager does, while still allowing resizing layout to occur. Or alternatively, grab a kind of focus for a container that the framework would try to request if the user clicked elsewhere. In other words, make a component modal in place without popping up a new window. I haven't actually studied FocusManager, so I don't know if it supports any sort of nested focus. On Wed, Mar 4, 2009 at 2:54 PM, Fotis Chatzinikos fotis.chatzini...@gmail.com wrote: What i do is track user changes by setting some flags (plural because i need to save bits of changes not everything on the form in one go). If the user tries to get away from the tab/form, i stop the event and throw a confirm alert box saying that there are changes that need to be saved. If he clicks i do not care for lost changes i let the navigation continue, else you can either just hide the alert box, or save any changes and then move to the new area... On Wed, Mar 4, 2009 at 11:50 PM, Richard Rodseth rrods...@gmail.comwrote: Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes? -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com, -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com,
Re: [flexcoders] Modeless editing
What i am doing at the moment sounds much like you are describing. My app contains several window like components. Each one has an expand button. On click a bubbling 'expand' event is dispatched. This in turn is caught in the main app and processed in a 'expander' function. This checks for any editable flag and expands the component that request so or cancels the event if a user decides that he needs to save first. On Thu, Mar 5, 2009 at 1:23 AM, Fotis Chatzinikos fotis.chatzini...@gmail.com wrote: I have not tried this, but if you are able to catch the hide event of the 'editing area' and cancel it, it would be far easier to implement what you describe...I do not have access to my builder at the moment so i do not know if what i suggest is doable... Have a go if you like :-) On Thu, Mar 5, 2009 at 1:19 AM, Richard Rodseth rrods...@gmail.comwrote: So your basic approach is capturing all events elsewhere in the app, and stopping them. I was thinking along the lines of a navigationmanager which knows about a current editing context, and could also be tied into deep linking support. View state (selected tab, selected child of view stack) would be derived from properties of the navigation manager. When the NM receives a nav request (via bubbling event) it would check if the current editing context was valid and not proceed with the nav. Doing all this with the help of Mate dependency injection shouldn't be too hard. At the same time, since time is limited, I wish there was a simple way to apply an event mask the way popup manager does, while still allowing resizing layout to occur. Or alternatively, grab a kind of focus for a container that the framework would try to request if the user clicked elsewhere. In other words, make a component modal in place without popping up a new window. I haven't actually studied FocusManager, so I don't know if it supports any sort of nested focus. On Wed, Mar 4, 2009 at 2:54 PM, Fotis Chatzinikos fotis.chatzini...@gmail.com wrote: What i do is track user changes by setting some flags (plural because i need to save bits of changes not everything on the form in one go). If the user tries to get away from the tab/form, i stop the event and throw a confirm alert box saying that there are changes that need to be saved. If he clicks i do not care for lost changes i let the navigation continue, else you can either just hide the alert box, or save any changes and then move to the new area... On Wed, Mar 4, 2009 at 11:50 PM, Richard Rodseth rrods...@gmail.comwrote: Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes? -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com, -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com, -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation fotis.chatzini...@gmail.com,
RE: [flexcoders] Modeless editing
I do this by having all of my change or click or whatever events call a single function that updates the model, and also sets a modified flag. The flag variable, which is bindable controls the enabled property of my Save button. I also can check it if my navigation permits the possibility of navigating away from a modified component. Tracy _ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Richard Rodseth Sent: Wednesday, March 04, 2009 4:50 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Modeless editing Does anyone have any suggestions for (or examples of) forms or other editing environments where navigation away from the editor is prevented when there are unsaved changes?
