Hi Pavel,
New to both seaside and SeasideXUL, my questions should be in a (xul)Seaside newbies list... I have a small test application that has a SearchResultComponent. The Search performs a Search action that finds data, puts them in the ResultComponent's model (ResultComponent is rendered as editable tree); ResultComponent is then rerendered by calling "SearchResultComponent refresh". Next I want the application user be able to edit cells in the editable ResultComponent tree, move the modified values into the ResultComponent model and save. I am trying to achieve moving the values by registering a callback with a "Save" menu item on the ResultComponent, which would obtain updated data from the edited tree. If the description above is somewhat clear, a few questions: is moving modified data from the XUL tree doable without wrapping the Result into a form; and in either case, is there an example or code I can look at? I did look at the XULPeriodicTableForms and tried to get "Save" in my example work a similar way (with and without form) but failed so far. I can paste my code experiments but I thought I should first ask for high level suggestions and help, Thanks Milan _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi,
the standard solution of this (see Firefox bookmarks manager) is to use the tree/table only for selection and then display a form for item editing. Unfortunately the standard XUL components are not ready behavior you want. Maybe a grid of edit boxes but you will lost the advantages of the tree view this way... Cheers, -- Pavel On Sun, Jun 22, 2008 at 4:52 PM, Milan Zimmermann <[hidden email]> wrote: > Hi Pavel, > > New to both seaside and SeasideXUL, my questions should be in a (xul)Seaside > newbies list... > > I have a small test application that has a SearchResultComponent. The Search > performs a Search action that finds data, puts them in the ResultComponent's > model (ResultComponent is rendered as editable tree); ResultComponent is then > rerendered by calling "SearchResultComponent refresh". > > Next I want the application user be able to edit cells in the editable > ResultComponent tree, move the modified values into the ResultComponent model > and save. I am trying to achieve moving the values by registering a callback > with a "Save" menu item on the ResultComponent, which would obtain updated > data from the edited tree. > > If the description above is somewhat clear, a few questions: is moving > modified data from the XUL tree doable without wrapping the Result into a > form; and in either case, is there an example or code I can look at? I did > look at the XULPeriodicTableForms and tried to get "Save" in my example work > a similar way (with and without form) but failed so far. > > I can paste my code experiments but I thought I should first ask for high > level suggestions and help, > > Thanks Milan > > > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi Pavel,
Thanks. I will give it a few weeks and try to build a mini-framework around the tree that would allow move changed cells (well, will start will the whole tree) back to server via XMLHttpRequest, and merge changes back to the Component that generated it. I may ask some questions how to integrate what I plan to do. If I fail, I can do a form per edited row... I am trying to use SeasideXUL on my next project, and most likely will need a editable table. Thanks Milan On 2008 June 24, Pavel Krivanek wrote: > Hi, > > the standard solution of this (see Firefox bookmarks manager) is to > use the tree/table only for selection and then display a form for item > editing. Unfortunately the standard XUL components are not ready > behavior you want. Maybe a grid of edit boxes but you will lost the > advantages of the tree view this way... > > Cheers, > -- Pavel > > On Sun, Jun 22, 2008 at 4:52 PM, Milan Zimmermann > > <[hidden email]> wrote: > > Hi Pavel, > > > > New to both seaside and SeasideXUL, my questions should be in a > > (xul)Seaside newbies list... > > > > I have a small test application that has a SearchResultComponent. The > > Search performs a Search action that finds data, puts them in the > > ResultComponent's model (ResultComponent is rendered as editable tree); > > ResultComponent is then rerendered by calling "SearchResultComponent > > refresh". > > > > Next I want the application user be able to edit cells in the editable > > ResultComponent tree, move the modified values into the ResultComponent > > model and save. I am trying to achieve moving the values by registering a > > callback with a "Save" menu item on the ResultComponent, which would > > obtain updated data from the edited tree. > > > > If the description above is somewhat clear, a few questions: is moving > > modified data from the XUL tree doable without wrapping the Result into a > > form; and in either case, is there an example or code I can look at? I > > did look at the XULPeriodicTableForms and tried to get "Save" in my > > example work a similar way (with and without form) but failed so far. > > > > I can paste my code experiments but I thought I should first ask for high > > level suggestions and help, > > > > Thanks Milan > > > > > > > > _______________________________________________ > > seaside mailing list > > [hidden email] > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 2008 June 24, Milan Zimmermann wrote:
> Hi Pavel, > > Thanks. I will give it a few weeks and try to build a mini-framework around > the tree that would allow move changed cells After looking at this approach I moved it to a "medium term", - toot much Javascript and unknowns... Now I want to just show a read-only table(tree), and display a form for editing, but having fundamental problems. First problem, I am trying to add a button on each row of the tree, in #renderContentOn: using xml treeCell with: [xml button; label: 'Detail' onCommand: [...] but doing thjis the button does not even show in the cell. I guess I am doing something very wrong here? Next, once the button shows, how would I display ("call") the detail form? I need a seasideXU: newbies list :) Thanks Milan > (well, will start will the > whole tree) back to server via XMLHttpRequest, and merge changes back to > the Component that generated it. I may ask some questions how to integrate > what I plan to do. If I fail, I can do a form per edited row... I am > trying to use SeasideXUL on my next project, and most likely will need a > editable table. > > Thanks Milan > > On 2008 June 24, Pavel Krivanek wrote: > > Hi, > > > > the standard solution of this (see Firefox bookmarks manager) is to > > use the tree/table only for selection and then display a form for item > > editing. Unfortunately the standard XUL components are not ready > > behavior you want. Maybe a grid of edit boxes but you will lost the > > advantages of the tree view this way... > > > > Cheers, > > -- Pavel > > > > On Sun, Jun 22, 2008 at 4:52 PM, Milan Zimmermann > > > > <[hidden email]> wrote: > > > Hi Pavel, > > > > > > New to both seaside and SeasideXUL, my questions should be in a > > > (xul)Seaside newbies list... > > > > > > I have a small test application that has a SearchResultComponent. The > > > Search performs a Search action that finds data, puts them in the > > > ResultComponent's model (ResultComponent is rendered as editable tree); > > > ResultComponent is then rerendered by calling "SearchResultComponent > > > refresh". > > > > > > Next I want the application user be able to edit cells in the editable > > > ResultComponent tree, move the modified values into the ResultComponent > > > model and save. I am trying to achieve moving the values by registering > > > a callback with a "Save" menu item on the ResultComponent, which would > > > obtain updated data from the edited tree. > > > > > > If the description above is somewhat clear, a few questions: is moving > > > modified data from the XUL tree doable without wrapping the Result into > > > a form; and in either case, is there an example or code I can look at? > > > I did look at the XULPeriodicTableForms and tried to get "Save" in my > > > example work a similar way (with and without form) but failed so far. > > > > > > I can paste my code experiments but I thought I should first ask for > > > high level suggestions and help, > > > > > > Thanks Milan > > > > > > > > > > > > _______________________________________________ > > > seaside mailing list > > > [hidden email] > > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > _______________________________________________ > > seaside mailing list > > [hidden email] > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On 2008 July 4, Milan Zimmermann wrote:
> On 2008 June 24, Milan Zimmermann wrote: > > Hi Pavel, > > > > Thanks. I will give it a few weeks and try to build a mini-framework > > around the tree that would allow move changed cells > > After looking at this approach I moved it to a "medium term", - toot much > Javascript and unknowns... Now I want to just show a read-only table(tree), > and display a form for editing, but having fundamental problems. > > First problem, I am trying to add a button on each row of the tree, in > #renderContentOn: using > > xml treeCell with: [xml button; label: 'Detail' onCommand: [...] > > but doing thjis the button does not even show in the cell. I guess I am > doing something very wrong here? Ah, now I know that treecell cannot show anything except perhaps a checkbox. Milan > > Next, once the button shows, how would I display ("call") the detail form? > > I need a seasideXU: newbies list :) > > Thanks Milan > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |