Curtain never opens

[rkorach]

The loading page stays forever. Please fix asap. Or if it comes from something in my computer, do I have a way to clean manually the database, and relaunch everything properly?

[moutard]

I need more feed back. Right click on the page -> Inspect element -> console -> send red lines. (error)

[rkorach]

here is a screenshot. Not many red lines, only a image that does not exist. However localStorage['CottonFirstOpening'] in installation.js (line 84) is declared as undefined. Could that be the problem ?

On Fri, Jun 8, 2012 at 9:36 AM, Raphael Moutard < reply@reply.github.com

wrote:

I need more feed back. Right click on the page -> Inspect element -> console -> send red lines. (error)

---

Reply to this email directly or view it on GitHub: https://github.com/fwouts/SubZoom-Proto1/issues/26#issuecomment-6196155

[rkorach]

oh no sorry I read the code, it is normal as it is not the first instal. still, nothing happens afterwards..

On Fri, Jun 8, 2012 at 9:40 AM, Raphaël Korach raphael.korach@gmail.comwrote:

here is a screenshot. Not many red lines, only a image that does not exist. However localStorage['CottonFirstOpening'] in installation.js (line 84) is declared as undefined. Could that be the problem ?

On Fri, Jun 8, 2012 at 9:36 AM, Raphael Moutard < reply@reply.github.com

wrote:

I need more feed back. Right click on the page -> Inspect element -> console -> send red lines. (error)

---

Reply to this email directly or view it on GitHub: https://github.com/fwouts/SubZoom-Proto1/issues/26#issuecomment-6196155

[Julihan]

I have the same problem. I see a popup every time, I open a new tab: "An old database has been found. Do you want to clear it ?"

[moutard]

On my side it takes 67s to open the curtain i's very long and I don't know why yet. What is "never" for you ? Do you wait more than 120s or did you kill the page before ?

[rkorach]

Yep, I usually wait for 3 minutes before killing it. At least once at every commit.

On Fri, Jun 8, 2012 at 6:29 PM, Raphael Moutard < reply@reply.github.com

wrote:

On my side it takes 67s to open the curtain i's very long and I don't know why yet. What is "never" for you ? Do you wait more than 120s or did you kill the page before ?

---

Reply to this email directly or view it on GitHub: https://github.com/fwouts/SubZoom-Proto1/issues/26#issuecomment-6207105

[moutard]

Solved. I don't understand exactly why, but it's not the algorithm that take time. But exchange with the database. We will have to refactor to use singleton. I tried yesterday but I didn't succeed so I will do that after the MVP. @rkorach try to pull the code. If it works close this issue. If not send me all the log in the console and your version of Chrome.

[rkorach]

It works perfectly for me. But oddly it worked since your 9d27e4 commit, 'Refactor : add console debug'

[moutard]

Just a last question : is it faster ? (less than 15s)

[rkorach]

Sorry I forgot to mention it, it is much faster ! (it was more about 20-25 seconds for me) What did you do?

On Sun, Jun 10, 2012 at 4:00 PM, Raphael Moutard < reply@reply.github.com

wrote:

Just a last question : is it faster ? (less than 15s)

---

Reply to this email directly or view it on GitHub: https://github.com/fwouts/SubZoom-Proto1/issues/26#issuecomment-6228503

[Julihan]

Sorry, but it's not fix (at least for me). I remove cT for my computer (files and on Chrome) and re-clone the last version, but that did change anything. Moreover, now use cT make my computer burns.

[moutard]

I need log in the console. And your version of chrome.

[Julihan]

Ok, my mistake! I didn't update chrome (I didn't close it for more than a week actually).

[moutard]

No worries, but it's a big relief for me ;)

[rkorach]

How does chrome version can affect that much cT behavior ????? Le 10 juin 2012 20:00, "Raphael Moutard" < reply@reply.github.com> a écrit :

No worries, but it's a big relief for me ;)

---

Reply to this email directly or view it on GitHub: https://github.com/fwouts/SubZoom-Proto1/issues/26#issuecomment-6230352

[moutard]

We can talk about it. But sometimes Chrome is delivered with some bugs, or with deprecated method. It's always a frustration to work on a non stable platform. But maybe we do something wrong.