X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,f491412c50af9dd8 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2001-12-06 18:38:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!130.133.1.3!fu-berlin.de!uni-berlin.de!213.242.128.42!not-for-mail From: "Joaquim Almgren G�ndara" Newsgroups: alt.ascii-art Subject: Re: JavE3.0: beta testers wanted Date: Fri, 7 Dec 2001 03:38:41 +0100 Lines: 27 Message-ID: <9upa3n$9n0ou$1@ID-102694.news.dfncis.de> References: <3C0F4F3E.61AC9C87@rz.uni-karlsruhe.de> <9uou62$a1tgr$2@ID-102694.news.dfncis.de> NNTP-Posting-Host: 213.242.128.42 X-Trace: fu-berlin.de 1007692728 10191646 213.242.128.42 (16 [102694]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Xref: archiver1.google.com alt.ascii-art:12251 One more thing... I was playing around with the camelizer and accidentally chose an animated gif. And the ASCII art animated! No, it didn't, but JavE acted quite strangely for a while, by which I mean to say that it didn't do anything at all. It froze for half a minute (or something) and then it went back to normal. I noted that the resulting camelized picture was rather large and that it was impossible to scroll in JavE since the camelizer dialog is modal. This does make sense, but I still found it a bit irritating that I couldn't see the entire picture. I then played around with the brightness settings and noticed that between -1.0 and -0.7, the camelization was nearly instantaneous. However, at high settings, the image grew large (and unscrollable), in which case the camelization was slow. I concluded that the long response time I had experienced earlier might be a result of the amount of white space in the animated gif, and not at all the fact that the gif was animated. My next step was to try loading a very bright picture; a blue-pencil sketch on white paper. JavE hasn't spoken to me since. I started writing this when it froze, and it's still frozen. I have a feeling that the complexity of the camelizer algorithm is at least exponential... Maybe JavE should issue a warning if the user is dumb enough to try a very bright picture? -- [WHY NO SIG? BECAUSE! I LOST IT!]