[Q] [Scriptaculous and Comet] SUStream related question

>> In SUStream class method encode:to: the character is encoded using
>> asInteger. But I think this seems wrong. Should it be asUnicode instead
>> of asInteger?
>
> I don't remember exactly, but it is certainly a spot where we have to
> take care with VisualWorks compatibility. What is the difference
> between #asUnicode and #asInteger? Is #asUnicode available in 3.7?
>
> Lukas
>

> On
> 3.7, I'm not sure this method exists or not. But at least for me, who
> need to use UTF-8(for korean), asInteger makes the application not work.
>
> Thanks.
>
> Lukas Renggli wrote:
> >> In SUStream class method encode:to: the character is encoded using
> >> asInteger. But I think this seems wrong. Should it be asUnicode instead
> >> of asInteger?
> >
> > I don't remember exactly, but it is certainly a spot where we have to
> > take care with VisualWorks compatibility. What is the difference
> > between #asUnicode and #asInteger? Is #asUnicode available in 3.7?
> >
> > Lukas
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFL4yoQqspS1+XJHgRAoncAKCb+upu1iH9o8OeS2DQIpzwO2mUPACfbAkd
> LsUMU9wMm82TVcIYEcl8Ojk=
> =hbl5
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> 2006/10/13, Sungjin Chun <[hidden email]>:
> asUnicode returns unicode value of a given character, asInteger returns
> (rather meaningless) squeak only definition of value of character.
>
>> Oh no. On >= 3.8 #asInteger returns the unicode code point. Which is
>> _exactly_ what you need.
>
>> Philippe
>
> On
> 3.7, I'm not sure this method exists or not. But at least for me, who
> need to use UTF-8(for korean), asInteger makes the application not work.
>
> Thanks.
>
> Lukas Renggli wrote:
>>> In SUStream class method encode:to: the character is encoded using
>>> asInteger. But I think this seems wrong. Should it be asUnicode
> instead
>>> of asInteger?
>
>> I don't remember exactly, but it is certainly a spot where we have to
>> take care with VisualWorks compatibility. What is the difference
>> between #asUnicode and #asInteger? Is #asUnicode available in 3.7?
>
>> Lukas
>
>

>   Philippe,
>
> > > asUnicode returns unicode value of a given character, asInteger returns
> > > (rather meaningless) squeak only definition of value of character.
> >
> > Oh no. On >= 3.8 #asInteger returns the unicode code point. Which is
> > _exactly_ what you need.
>
>   asInteger doesn't return the unicode code point.  Since Unicode is a
> 21-bit character set, we have otherwise unused bits in a word.  At the
> same time, bare Unicode character lacks the information (basically)
> how to present themselves.  So, we put a few more bits there to
> distinguish some "unified" characters.
>
>   There is a method called #charCode, that gives you the bare Unicode
> code point.  #leadingChar returns the upper bits that denotes the
> "language tag".

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> No, from my experiment, two values are difference. For example, Korean
> syllable Kiyoek has code value of 16r3131 in unicode table;
>
> ch _ Character leadingChar: 255 code: 16r3131.
> ch inspect. "you can sea angle like character if you have korean font"
> ch asInteger. "1069560113"
> ch asUnicode. "12593"
>
> This difference makes Comet example chat does not work with
> korean/japanese/chinese like languages.

> Philippe Marschall wrote:
> > 2006/10/13, Sungjin Chun <[hidden email]>:
> > asUnicode returns unicode value of a given character, asInteger returns
> > (rather meaningless) squeak only definition of value of character.
> >
> >> Oh no. On >= 3.8 #asInteger returns the unicode code point. Which is
> >> _exactly_ what you need.
> >
> >> Philippe
> >
> > On
> > 3.7, I'm not sure this method exists or not. But at least for me, who
> > need to use UTF-8(for korean), asInteger makes the application not work.
> >
> > Thanks.
> >
> > Lukas Renggli wrote:
> >>> In SUStream class method encode:to: the character is encoded using
> >>> asInteger. But I think this seems wrong. Should it be asUnicode
> > instead
> >>> of asInteger?
> >
> >> I don't remember exactly, but it is certainly a spot where we have to
> >> take care with VisualWorks compatibility. What is the difference
> >> between #asUnicode and #asInteger? Is #asUnicode available in 3.7?
> >
> >> Lukas
> >
> >
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> >>
> > _______________________________________________
> > Seaside mailing list
> > [hidden email]
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMBMkQqspS1+XJHgRAoxaAKClB+QHg5yO7fRQCXI/Zf5mq3vNNgCfcfp+
> Vk3av+xHuZD/SmBQLPJ1inQ=
> =xgBy
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Philippe Marschall wrote:
>
> >
> >> Also the form example in SUAllTests seems to be broken on 3.9 for
> >> WAListener for non-ASCII characters. Even Latin1 characters break it.
> >> #asUnicode does not fix this.
>
> Don't know 3.9 case, but for 3.8, it seems work (at least with Korean
> characters, UTF-8 encoding).

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMJudQqspS1+XJHgRAmTAAJ4lkSV7KPqIzBRjK612IVbx+91TDQCgiZD5
> 6n+BKlrL+/y/rb9C6lJHw0k=
> =YP/J
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Philippe Marschall wrote:
>
> >> Well it's actually the same bug that broke WAKom and WAKomEncoded in
> >> 3.9 for non-ASCII characters: String >> #unescapePercents.
> >
> >> A fix would be more annoying because of the Squeak Stream hierarchy.
> >
> >> Philippe
>
> Is this bug is related to only mentioned method or more fundamental
> differences between 3.8 and 3.9?

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMKuhQqspS1+XJHgRAtMHAJ4muSCZd46vi2IHXvXEnWFlt6RJYwCg0JL9
> BoE5AZgcYmeIQzFFU5MMvGs=
> =8ouq
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> >
> >> I talke it that you need a WAListenerEncoded that has the same
> >> semantics as WAKomEncoded. What seaside version do you use 2.6b1?
> >
> >> Philippe
>
> Yes, I'm using 2.6b1 and 3.8 image(as I said before). Till now, we do
> not have to use WAListener because we do not have seaside application
> using Comet like technology currently. But we do like test/suvery this
> technology and Comet seems promising for our specific needs, we do want
> to use this too.

> Thanks.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMM+iQqspS1+XJHgRAogpAJ9cdTUJUqElk/eQ1tAZD6D3TlrDygCfasmY
> 4L8NWsYKLUNJauASk62wylM=
> =T1kB
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

>> Can you one of those:
>> Seaside2.6b1-pmm.87
>> Seaside2.6b1-pmm.101
>
>> There is now a class called WAListenerEncoded that has the same
>> semantics as WAKomEncoded.
>
>> Don't forget to stop your old adapters first.
>
>> Philippe
>
> Thanks.

> OOPS!, I encountered a severe problem. After I saved image(with
> WAListenerEncoded Running) and reopen, the image just freezed and I
> cannot access to the service(seaside application) nor tools.
>
> Is there any relationship between new version of seaside and this problem?
>
> Thanks in advance.
>
> Sungjin Chun wrote:
>>> Wow, it works great (at least till now :-). I've choosed pmm.101
>>> version. Previously I've used mb.99 version.
>>>
>>> Thanks.
>>>

> Thanks in advance.
>
> Sungjin Chun wrote:
> > Wow, it works great (at least till now :-). I've choosed pmm.101
> > version. Previously I've used mb.99 version.
> >
> > Thanks.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMQA3QqspS1+XJHgRAlfsAKCdzpGBMUENO9ibUoNnmJZBv/tMWQCgn7ja
> Mmy0v0i7+m4kF7k2tNkSv5g=
> =KOve
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> 2006/10/14, Sungjin Chun <[hidden email]>:
> OOPS!, I encountered a severe problem. After I saved image(with
> WAListenerEncoded Running) and reopen, the image just freezed and I
> cannot access to the service(seaside application) nor tools.
>
> Is there any relationship between new version of seaside and this
> problem?
>
>> Don't know yet, but I can confirm the problem :(
>> Squeak image is taking up 100 % CPU.
>
>> gdb seems to indicate that it's constantly in
>> in WAListener>listenLoop
>
>> I'd say it's either WALinstener* or Comet related.
>
>> Philippe
>
> Thanks in advance.

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Philippe Marschall wrote:
> > 2006/10/14, Sungjin Chun <[hidden email]>:
> > OOPS!, I encountered a severe problem. After I saved image(with
> > WAListenerEncoded Running) and reopen, the image just freezed and I
> > cannot access to the service(seaside application) nor tools.
> >
> > Is there any relationship between new version of seaside and this
> > problem?
> >
> >> Don't know yet, but I can confirm the problem :(
> >> Squeak image is taking up 100 % CPU.
> >
> >> gdb seems to indicate that it's constantly in
> >> in WAListener>listenLoop
> >
> >> I'd say it's either WALinstener* or Comet related.
> >
> >> Philippe
> >
> > Thanks in advance.
>
> It seems that this problem is related to WAListener*, not Comet, though
> I'm not sure. What I've tested is that stop the Comet's ping process and
>  keep the WAListener* running, this problem just happens, even though
> ping process(which is related to Comet) not running.
>
> Is this related to network initialization in squeak? I cannot figure out
> what's wrong.

> Thanks.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFMQd5QqspS1+XJHgRAi8JAKCKPSN0mo1545mEZLdDrZ0g/Flc6gCfdW6a
> Wyojoa8Z6LhIQDSPXhbShFM=
> =hOXU
> -----END PGP SIGNATURE-----
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>