While there are ways to try to work around the limitations of loading a large database into a browser, ultimately a large data set that's overloading browser resources should probably move to a server side solution. That's why we're working on Backstage.
https://github.com/zepheira/backstage/ It's not production ready, but it might be worth looking into instead of trying to find hack workarounds. On 2012-03-07 05:04 , Janick wrote: > Did someone managed to get rid of the "Stop running this script" alert in > IE. > > Here is a suggestion: > http://www.picnet.com.au/blogs/Guido/post/2010/03/04/How-to-prevent-Stop-running-this-script-message-in-browsers.aspx > > > > I searched alot but unfortunately I dont know where this changes need to be > implemented. > > Thanks > > On Monday, February 27, 2012 2:24:41 PM UTC+1, Janick wrote: >> >> I see your point, thanks for the reply! >> >> The amount of records is giving us problems that's why we thought to >> group and paginate. >> People are getting the warning "Stop running this script?" in IE, I >> have read this can be solved by changing a setting in IE but for us >> this would not be a solution. >> Other solution would be to insert a timeout when the loop is made, >> unfortunately we are not able to find where to place this. >> >> Maybe another way, is it possible to not show any records in the start >> of the page and when someone selects a facets the json will be >> filtered? >> >> On Feb 25, 2:07 am, Ryan Lee <ryan...@zepheira.com> wrote: >>> On 2012-02-23 07:15 , Janick wrote: >>> >>>> Hi All, >>> >>>> Is it possible to have pagination and items being grouped? >>>> For me it's only one of the two, but not both. >>> >>>> Thanks! >>> >>> It isn't implemented to allow both, no. There are a couple ways that >>> come to mind to address problems with having both, but as-is it would be >>> confusing - do you show the group heading if the grouping is split >>> between pages on both (or more) pages, or not (it wouldn't now)? You >>> probably should, but that could make it hard to comprehend. Do you show >>> the total count on both? Again, should, but that would also muddle >>> things. The biggest issue would be not being able to see the aggregate >>> grouping across all of the selected data, which is part of what the >>> grouping feature is for. >>> >>> I imagine retooling the grouping implementation to recognize paging and >>> display a sensible split-page header (e.g., "Group 1 (21 through 40 of >>> 55) on this page)" and show across split pages would make this more >>> feasible. >>> >>> (Long answer in case someone feels like breaking out their hacker hat.) > > > On Monday, February 27, 2012 2:24:41 PM UTC+1, Janick wrote: >> >> I see your point, thanks for the reply! >> >> The amount of records is giving us problems that's why we thought to >> group and paginate. >> People are getting the warning "Stop running this script?" in IE, I >> have read this can be solved by changing a setting in IE but for us >> this would not be a solution. >> Other solution would be to insert a timeout when the loop is made, >> unfortunately we are not able to find where to place this. >> >> Maybe another way, is it possible to not show any records in the start >> of the page and when someone selects a facets the json will be >> filtered? >> >> On Feb 25, 2:07 am, Ryan Lee <ryan...@zepheira.com> wrote: >>> On 2012-02-23 07:15 , Janick wrote: >>> >>>> Hi All, >>> >>>> Is it possible to have pagination and items being grouped? >>>> For me it's only one of the two, but not both. >>> >>>> Thanks! >>> >>> It isn't implemented to allow both, no. There are a couple ways that >>> come to mind to address problems with having both, but as-is it would be >>> confusing - do you show the group heading if the grouping is split >>> between pages on both (or more) pages, or not (it wouldn't now)? You >>> probably should, but that could make it hard to comprehend. Do you show >>> the total count on both? Again, should, but that would also muddle >>> things. The biggest issue would be not being able to see the aggregate >>> grouping across all of the selected data, which is part of what the >>> grouping feature is for. >>> >>> I imagine retooling the grouping implementation to recognize paging and >>> display a sensible split-page header (e.g., "Group 1 (21 through 40 of >>> 55) on this page)" and show across split pages would make this more >>> feasible. >>> >>> (Long answer in case someone feels like breaking out their hacker hat.) > -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to simile-widgets@googlegroups.com. To unsubscribe from this group, send email to simile-widgets+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en.
