Chrome is optimized for javascript processing. I believe it has a new javascript engine the other browsers don't (yet). Makes sense that Chrome would work well with any application heavy in javascript/json. IE seems to have the slowest javascript engine.
- John On Thu, Mar 4, 2010 at 11:56 AM, Michael Andersen <[email protected]>wrote: > What I do for some of my stuff (I'm tracking server incidents in our data > center), is create my json file on the fly from a php script that goes > against a monitoring database (SQL server)... > > I read all the data I need, naming the columns as I want them right in my > SQL. Then in a loop, I add each row to an array. If I need to pre-process > the data, I do it in the loop. > > Once all rows are read, (5000 rows about), I use phps json_encode to give > me a json string... And that is my feed for exhibit. > > Works well, and is fast, other than taking a while to load the fat data > set. > > Interesting to note that Chrome works better than FF or IE in my case, with > big data. > > I'm about to do a similar thing to monitor oracle events and jobs (I'm a > dba, but otherwise ok) > > Michael > > Sent from my iPhone > > > On 4-Mar-10, at 10:21 AM, kumarachi <[email protected]> wrote: > > hi David, >> >> indeed! i saw this announcement just after posting my question and >> thought that was awful weird as well... >> your editable exhibit looks great, and i will try something similar >> for now. >> >> Thank you all for the ideas about a DB backend, though i would prefer >> to keep it lightweight and persist to JSON file instead if i can (the >> updates are from a single person, no concurrency for now). DB would >> be handy though if we were to expand to allow data updates from all >> our admin users, to handle locking and concurrency issues... >> >> thanks >> -k >> >> On Mar 2, 2:09 pm, David Karger <[email protected]> wrote: >> >>> funny, i just posted an announcement yesterday of a new tool for a >>> "WYSIWYG editable exhibit":http://projects.csail.mit.edu/Exhibit/Dido/ >>> >>> It supports dynamic update of simile exhibits. You can edit the data >>> right in the page exhibit view, then save the file to persist the >>> changes. Right now, the data is stored in the file with the exhibit, >>> which may or may not fit your purposes. Managing a separate data file >>> is definitely on the todo list. >>> >>> Another approach some people have taken is to keep their data in a >>> google spreadsheet. Exhibit can read those directly, and you can edit >>> the spreadsheet to change your data (and add items using a google form). >>> >>> On 3/2/2010 8:56 AM, kumarachi wrote: >>> >>> Hi, >>>> >>> >>> we have been using Simile Exhibit and Timeline internally at my >>>> company for a year now, and everyone's pleased with these. However, i >>>> may be the only one not so pleased with things because I maintain the >>>> tools, and the data -- and as the tools have become more widely used, >>>> i am having to update the data more and more frequently - which leads >>>> me to wonder if there has ever been built a tool or online form to >>>> either dynamically or otherwise update the JSON or XML data? >>>> >>> >>> My current workflow is a little painful: i enter data into an excel >>>> sheet, then send that manually to Babel (tried the Babel service >>>> version, but it makes the first display quite slow), and then ftp my >>>> result JSON file over to the host machine. >>>> >>> >>> SO -- I would like to develop an interface to directly add to the JSON >>>> or XML data file from an online form. >>>> Has anyone done this or can share some thoughts and ideas about how >>>> to? >>>> >>> >>> thanks >>>> -k >>>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "SIMILE Widgets" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<simile-widgets%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/simile-widgets?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "SIMILE Widgets" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<simile-widgets%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/simile-widgets?hl=en. > > -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en.
