On 05/06/11 2:14 AM, Yanni Chiu wrote: Since I've got a free hand, I used a Pier CMS, and loaded JSON from SqueakSource. Then a wrote a PRWidget to get the JSON data, parse, and display. Still some clean up, CSS, and deployment to do. Our group didn't place in the top, but the real point was to be there to talk to people about what they do and how they do it. Here's a wrap up. The code was real simple. One PRWidget subclass, and a model introduced to simplify access to the JSON tree. The real problem came Sunday morning. I had been developing code on localhost, and thought to deploy from home, because the internet access at the conference was saturated. I had built a clean image from scratch (in the wee hours of the morning), tested it locally, uploaded to a server - and ... no response. Oh well, easy fix for the next morning. I was using a set up that I had deployed to already. I knew the tweaks I needed to do - turns out I missed a few. The Apache log let me figure that out. Then the PharoDebug.log told me I needed the .sources and .changes file too. Now the site is up. I navigate to the url I want, and ... no response. Nothing wrong in PharoDebug.log, and now I regret choosing not to install RFB (figuring I've done this deployment thing before, so it's just gonna work). Then I try /tools/screenshot, and I confirm that there's no debug window. I figure out from the debug log that I need some deployment code from some other project. I put that in, and still no go. Well now I have to leave to get to the conference site. We have to go to plan B, and present the demo from localhost. I work on making the page pretty - a combination of renderContentOn: work, and CSS editting on Pier. We're out of time, the team's presenters need to practice, so I can't install it on their machine. Oh well, plac C, I'd sent them printscreens, just in case. While they're practicing, I go back to getting the site working. I hit the link, and it works. Must have been some caching effect in my browser, or even in my ISP. So I upload the latest image and stuff, which takes 15 minutes, due to the internet connection. (Aside, I suspect the slowness was actually due to traffic shaping by the ISPs in our country, because the upload seemed to be throttled in the same manner as at home). The new image works, and we use it in the demo - not quite, because the speakers ran short on time and spent 3 seconds on it. -- Yanni _______________________________________________ Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki