Hello Kihara, Perhaps we can improve some of the user experience when launching Backstage - right now there really isn't anything at the root. We generally expect Backstage to be proxied or something of a background service. Users aren't visiting it so much as seeing its service output.
Much like using Exhibit in its Scripted form, your page containing a staged Exhibit should probably be served from somewhere other than Backstage. See https://github.com/zepheira/backstage/wiki/Authoring for a bit more. On 12/13/11 00:04 , Kihara Absolomon wrote: > Hi all, > > I am trying to deploy staged version of exhibit3 and I have hit a wall. I > have installled backstage, babel and butterfly, and I think I installed ok. > However, When I try to access backstage using http://localhost:8181/ I get > a "HTTP ERROR 404", Problem accessing /. Reason: Couldn't find the > specified resource. > > Google is not helping, I have tried to change the root folder to something > else, with no luck! > > Anyone with some ideas on how to solve this? > > Regards > Kihara > > On Sat, Dec 3, 2011 at 12:55 AM, Ryan Lee <[email protected]> wrote: > >> Hi Kihara, >> >> Thanks for kind words and interest. We started Exhibit 3 to provide a >> solution for situations where folks wanted to have more than a couple >> thousand items in their collection. That's where Backstage comes in: >> https://github.com/zepheira/backstage >> >> The code base you're using (we're calling it Exhibit 3 Scripted) isn't >> really appropriate for the scale of data you're discussing. Backstage >> should be able to handle it instead. >> >> If you've got some way to reproduce the bug you mentioned in your prior >> email, I'd appreciate seeing it. Maybe you could file an issue in the >> GitHub tracker? >> >> https://github.com/zepheira/exhibit3/issues >> >> Thanks! >> >> On 11/27/11 21:30 , Kihara Absolomon wrote: >>> Dear all, >>> >>> As a follow up to the email I sent out below, I was able to get some >> stats >>> on the javascript execution times per the functions being called. I >> logged >>> the times that it takes to process a file with 1000 items and with 5000 >>> items, as this is where FF starts to experience some drag. >>> >>> I have attached 2 spreadsheets with the results, which I hope can help is >>> optimizing the code. >>> >>> Regards >>> Kihara >>> >>> On Sun, Nov 27, 2011 at 6:59 PM, Kihara Absolomon <[email protected] >>> wrote: >>> >>>> Dear all, >>>> >>>> I start by saying hats off to you guys for the great work that I am >> doing. >>>> >>>> I am trying to implement the exhibit3.0 widget and I am running into two >>>> problems: >>>> >>>> - I have cloned the current release from >>>> https://github.com/zepheira/exhibit3/ and the demos are running ok. >> I >>>> have generated my input file(find attached). However when I point the >>>> source to the offline 'exhibit3/scripted/src/exhibit-api.js' I get >> the >>>> error 'collection is undefined at ' facet.js line 476. When I use the >>>> online sources everything runs fine. >>>> - When I have close to 30,000 items in the input the widget becomes >>>> quite slow(As I would expect it). Is there a way to define which >> fields >>>> should be processed after loading the widget for the first time? Is >> there a >>>> way to have asynchronous fetching of the data when interacting with >> the >>>> widget to prevent the initial loading of all items? >>>> >>>> Thanks in advance. >>>> >>>> >>> >> >> -- >> 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. >> >> > -- 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.
