Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
October 2010
- 130 participants
- 1604 messages
Re: [Pharo-project] Anyone has seen Dale?
by Norbert Hartl
On 20.10.2010, at 22:35, Alexandre Bergel wrote:
> hi!
>
> Do you know where Dale is ? In holidays or something? I sent him an email a few days ago...
>
As far as I know he is really busy with the gemstone 3.0 release.
Norbert
Oct. 20, 2010
Re: [Pharo-project] [ANN] ImageMap PharoKernel-12196
by Pavel Krivanek
And here is the PDF version of the first 2000 objects
file:///home/krivanek/Dokumenty/pharo/12196/graphviz/1/imageGraph.pdf
-- Pavel
On Wed, Oct 20, 2010 at 10:53 PM, Pavel Krivanek
<pavel.krivanek(a)gmail.com> wrote:
> Hi Lukas,
>
> you can try it:
> http://www.grandjihlava.cz/tmp/ImageGraph/ImageMap.st
>
> the command that generates the graph is
> dot -Tsvg imageGraph.dot > imageGraph.svg
>
> Unfortunatelly my laptop has only 2GB so I have not enough RAM to
> generate the graph for whole PharoKernel image ;-) The input file for
> GraphViz has 67MB ;-)
>
> This is the resultant graph for the first 500 objects
> http://www.grandjihlava.cz/tmp/ImageGraph/imageGraph.svg
>
> Cheers,
> -- Pavel
>
> On Tue, Oct 19, 2010 at 9:15 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
>> Wow, this is really cool.
>>
>> Did you also try to visualize the object-graph using GraphViz?
>>
>> Lukas
>>
>> On 19 October 2010 20:49, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote:
>>> Hi,
>>>
>>> I generated the PharoKernel ImageMap (hypertext representation of the
>>> image content). You can see it here:
>>>
>>> http://goo.gl/nY2o
>>>
>>> The source code is here: http://goo.gl/J4T0
>>> CSS style is here: http://goo.gl/Pxw2
>>>
>>> Use it carefully, for 2,2MB image it generates 77,6MB of HTML files :-)
>>>
>>> Cheers,
>>> -- Pavel
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project(a)lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
>>
>> --
>> Lukas Renggli
>> www.lukas-renggli.ch
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
Oct. 20, 2010
[Pharo-project] [update 1.2] #12202
by Stéphane Ducasse
12202
-----
- Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!!
Oct. 20, 2010
Re: [Pharo-project] [ANN] ImageMap PharoKernel-12196
by Pavel Krivanek
Hi Lukas,
you can try it:
http://www.grandjihlava.cz/tmp/ImageGraph/ImageMap.st
the command that generates the graph is
dot -Tsvg imageGraph.dot > imageGraph.svg
Unfortunatelly my laptop has only 2GB so I have not enough RAM to
generate the graph for whole PharoKernel image ;-) The input file for
GraphViz has 67MB ;-)
This is the resultant graph for the first 500 objects
http://www.grandjihlava.cz/tmp/ImageGraph/imageGraph.svg
Cheers,
-- Pavel
On Tue, Oct 19, 2010 at 9:15 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
> Wow, this is really cool.
>
> Did you also try to visualize the object-graph using GraphViz?
>
> Lukas
>
> On 19 October 2010 20:49, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote:
>> Hi,
>>
>> I generated the PharoKernel ImageMap (hypertext representation of the
>> image content). You can see it here:
>>
>> http://goo.gl/nY2o
>>
>> The source code is here: http://goo.gl/J4T0
>> CSS style is here: http://goo.gl/Pxw2
>>
>> Use it carefully, for 2,2MB image it generates 77,6MB of HTML files :-)
>>
>> Cheers,
>> -- Pavel
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
[Pharo-project] [update 1.2] #12201
by Stéphane Ducasse
12201
-----
- Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!!
Oct. 20, 2010
[Pharo-project] Anyone has seen Dale?
by Alexandre Bergel
hi!
Do you know where Dale is ? In holidays or something? I sent him an email a few days ago...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Oct. 20, 2010
Re: [Pharo-project] Plug-in Licensing
by Schwab,Wilhelm K
Paolo,
Thanks for the reference. I will give it a good look.
Bill
________________________________________
From: Paolo Bonzini [paolo.bonzini(a)gmail.com] On Behalf Of Paolo Bonzini [bonzini(a)gnu.org]
Sent: Wednesday, October 20, 2010 2:13 PM
To: Schwab,Wilhelm K
Subject: Fwd: Re: Plug-in Licensing
I found a reference to GPL-compatible vs. GPLv3 in the GCC mailing list
from today.
It is the same situation as you, with "GCC plugin" being your library
and "GCC" being GSL in your case.
Hope this helps a fellow Smalltalker.
Paolo
------------------
Justin Seyster <jrseys(a)gmail.com> writes:
> I'm getting ready to release plug-in code, and I want to have a very
> clear idea about licensing before I release. I'm leaning towards
> releasing everything as GPLv3, but I do want to know exactly what is
> and isn't allowed.
GPLv3 is fine.
> I know this issue was debated quite intensely before plug-in support
> got added, but my understanding is that there was a final consensus.
> I can't find one document though that explains exactly what this
> consensus was.
The document is here:
http://www.gnu.org/licenses/gcc-exception.html
See also the rationale and FAQ that it links to.
Basically, if you use a plugin with gcc, and the plugin is not
GPL-compatible, then the resulting compiled code is covered by the GPL.
> I vaguely remember a proposal that there would be no restriction on
> plug-in licensing but that non-free plug-ins could only be used to
> compile Free software, but that's not documented anywhere I can find.
That's pretty much it.
> GCC itself now requires that plug-ins export a
> plugin_is_gpl_compatible symbol, which implies that the plug-in's
> license need only be compatible with the GPL. Is it ok to release
> LGPL- or BSD-licensed plug-ins?
Sure, both of those licenses are GPL-compatible.
> My understanding is that, in general, only GPLv3 code can link against
> GPLv3 code, which would imply that my plug-in code must be GPLv3.
That is incorrect. You can link code under any GPL-compatible license
with GPLv3 code, and the resulting executable will be covered the union
of both licenses. Since GPLv3 tends to be stricter than any
GPL-compatible license, this generally means that the result is under
GPLv3. There is a (non-exhaustive) list of GPL-compatible licenses
here:
http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses
Ian
Oct. 20, 2010
Re: [Pharo-project] ^ character in ubuntu
by Diogenes Moreira
Thank you..
2010/10/20 Roberto Sapiain <rsapiain(a)gmail.com>
> Hello.
>
> Well, In my case I just have a simple workaround: in a terminal put the
> keyboard in english (with
> # setxkbmap us ; there with shift+6 you get the 'hat' ^ ; to go back to
> your normal layout setxkbmap latam if its latinamerican or es if its
> spanish keyboard type; once you get the character printed, do a copy &
> paste, or memorize the layout of an english keyboard ;))
>
> cheers, and hello to everyone in the list as well :)
>
> 2010/10/20 Diogenes Moreira <diogenes.moreira(a)gmail.com>
>
>> hi falks.
>>
>> I'm using Pharo 1.1 OneClick Package in Ubuntu 10.4 with the follow
>> locale.
>> when press ^ character in the pharo editor i get "?" symbol..
>>
>> What configuration I need change?
>>
>> Other data, if i using the cut & paste from othe application, that work
>> fine.
>>
>> Thank in advance.
>>
>> iogenes@diogenes-desktop:~$ locale
>> LANG=es_AR.utf8
>> LC_CTYPE="es_AR.utf8"
>> LC_NUMERIC="es_AR.utf8"
>> LC_TIME="es_AR.utf8"
>> LC_COLLATE="es_AR.utf8"
>> LC_MONETARY="es_AR.utf8"
>> LC_MESSAGES="es_AR.utf8"
>> LC_PAPER="es_AR.utf8"
>> LC_NAME="es_AR.utf8"
>> LC_ADDRESS="es_AR.utf8"
>> LC_TELEPHONE="es_AR.utf8"
>> LC_MEASUREMENT="es_AR.utf8"
>> LC_IDENTIFICATION="es_AR.utf8"
>> LC_ALL=
>>
>> cat /etc/lsb-release
>> DISTRIB_ID=Ubuntu
>> DISTRIB_RELEASE=10.04
>> DISTRIB_CODENAME=lucid
>> DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS
>>
>> diogenes@diogenes-desktop:~$ uname -a
>> Linux diogenes-desktop 2.6.32-25-generic-pae #44-Ubuntu SMP Fri Sep 17
>> 21:57:48 UTC 2010 i686 GNU/Linux
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> -* Amn El Ith Tir Sol - Honour *-
> Roberto Iván Sapiain Caro (RISC).
> Estudiante Ing. Civil en Computación.
> Universidad de Chile
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
Re: [Pharo-project] ^ character in ubuntu
by Roberto Sapiain
Hello.
Well, In my case I just have a simple workaround: in a terminal put the
keyboard in english (with
# setxkbmap us ; there with shift+6 you get the 'hat' ^ ; to go back to
your normal layout setxkbmap latam if its latinamerican or es if its
spanish keyboard type; once you get the character printed, do a copy &
paste, or memorize the layout of an english keyboard ;))
cheers, and hello to everyone in the list as well :)
2010/10/20 Diogenes Moreira <diogenes.moreira(a)gmail.com>
> hi falks.
>
> I'm using Pharo 1.1 OneClick Package in Ubuntu 10.4 with the follow locale.
> when press ^ character in the pharo editor i get "?" symbol..
>
> What configuration I need change?
>
> Other data, if i using the cut & paste from othe application, that work
> fine.
>
> Thank in advance.
>
> iogenes@diogenes-desktop:~$ locale
> LANG=es_AR.utf8
> LC_CTYPE="es_AR.utf8"
> LC_NUMERIC="es_AR.utf8"
> LC_TIME="es_AR.utf8"
> LC_COLLATE="es_AR.utf8"
> LC_MONETARY="es_AR.utf8"
> LC_MESSAGES="es_AR.utf8"
> LC_PAPER="es_AR.utf8"
> LC_NAME="es_AR.utf8"
> LC_ADDRESS="es_AR.utf8"
> LC_TELEPHONE="es_AR.utf8"
> LC_MEASUREMENT="es_AR.utf8"
> LC_IDENTIFICATION="es_AR.utf8"
> LC_ALL=
>
> cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=10.04
> DISTRIB_CODENAME=lucid
> DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS
>
> diogenes@diogenes-desktop:~$ uname -a
> Linux diogenes-desktop 2.6.32-25-generic-pae #44-Ubuntu SMP Fri Sep 17
> 21:57:48 UTC 2010 i686 GNU/Linux
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
--
-* Amn El Ith Tir Sol - Honour *-
Roberto Iván Sapiain Caro (RISC).
Estudiante Ing. Civil en Computación.
Universidad de Chile
Oct. 20, 2010
Re: [Pharo-project] Decompiling method body returns as block?
by Stéphane Ducasse
if you refactor the method send it to us in a bug entry :)
Stef
On Oct 20, 2010, at 5:49 AM, Hernán Morales Durand wrote:
> Wonderfull, thanks Lukas and Eliot!
>
> 2010/10/19 Eliot Miranda <eliot.miranda(a)gmail.com>:
>> Hi Hernán,
>>
>> On Tue, Oct 19, 2010 at 1:37 PM, Hernán Morales Durand
>> <hernan.morales(a)gmail.com> wrote:
>>>
>>> Hi list,
>>> I'm using Pharo1.1rc2 #11400 and I want to extract the body part (the
>>> String without the selector) of a CompiledMethod, but I'm getting a
>>> BlockNode after sending #body and a MNU afterwards. This is what I do
>>>
>>> aCompiledMethod decompileWithTemps ---> a BytecodeAgnosticMethodNode
>>> which is displayed like:
>>>
>>> 'renderContentOn: aRenderer
>>> aRenderer form id: ''horizontalForm'';
>>> with: [aRenderer
>>> fieldSet: [ ... blablabla ]]'
>>>
>>> and is ok. Then
>>>
>>> aCompiledMethod decompileWithTemps body ---> a BlockNode displayed as:
>>>
>>> {[:aRenderer |
>>> aRenderer form id: 'horizontalForm';
>>> with: [aRenderer
>>> fieldSet: [... blablabla]]]}
>>>
>>> I've expected the code string (sending #decompileString) without
>>> "[:aRenderer |" part (used to work that way).
>>> The thing is if I send #code to the BlockNode I get a
>>> "MessageNotUnderstood: CascadeNode>>code".
>>> I'd appreciate any hint to solve this.
>>
>> An alternative to Lukas' suggestion would be to refactor
>> MethodNode>>printOn: into
>> printOn: aStream
>> self
>> printSignatureOn: aStream;
>> printBodyOn: aStream
>> and then use aCompiledMethod decompileWithTemps printBodyOn:
>> best,
>> Eliot
>>>
>>> Cheers,
>>>
>>>
>>> --
>>> Hernán Morales
>>> Information Technology Manager,
>>> Institute of Veterinary Genetics.
>>> National Scientific and Technical Research Council (CONICET).
>>> La Plata (1900), Buenos Aires, Argentina.
>>> Telephone: +54 (0221) 421-1799.
>>> Internal: 422
>>> Fax: 425-7980 or 421-1799.
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project(a)lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Hernán Morales
> Information Technology Manager,
> Institute of Veterinary Genetics.
> National Scientific and Technical Research Council (CONICET).
> La Plata (1900), Buenos Aires, Argentina.
> Telephone: +54 (0221) 421-1799.
> Internal: 422
> Fax: 425-7980 or 421-1799.
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Oct. 20, 2010
[Pharo-project] Crytography package.
by Diogenes Moreira
Hi falk.
1. Squeaksource is down :(
2. Anybody can send me the Crytography packages from your local package
cache..or
3. Anybody knows a mirror of squeaksource for obtain this package.
Thank in advance..
Oct. 20, 2010
[Pharo-project] non-modal FillInTheBlankMorph code?
by Eliot Miranda
Hi All,
has anyone already written the handful of methods to provide a non-modal
FillInTheBlankMorph (a way of opening that doesn't enter the doOneCycle loop
in FillInTheBlankMorph>>getUserResponse) they can let me have or point me
to? If so, let me know. Thanks.
best
Eliot
Oct. 20, 2010
Re: [Pharo-project] Resize pharo window
by Eliot Miranda
Hi Levente,
2010/10/20 Levente Uzonyi <leves(a)elte.hu>
> On Wed, 20 Oct 2010, Alexander LazareviÄ wrote:
>
> So you gonna remove the call to ioSetDisplayMode of the specific vm
>>
> display plugin from primitiveSetDisplayMode?
>
> Alex
>
>
> No, the idea is to replace the current implementation of ioSetDisplayMode:
>
> return 0;
>
> to another which saves the display size:
>
> setSavedWindowSize((w << 16) + (h & 0xFFFF));
> return 1;
>
This may or may not be related. We do headless builds at Teleplace and
everything worked fine until we moved to Mac. There-on the issue for us was
that ioScreenSize was defined to answer 16@16 for the screen size when run
headless, and so images built headless on the Mac used to come up with a
tiny screen. The fix was to use the saved window size. See
http://www.squeakvm.org/svn/squeak/branches/Cog/platforms/Mac%20OS/vm/sqMac…
.
As far as setting the image size in image we discussed all this on this list
back on May 16th, right? e.g. save the image (but don't quit) open the
just-saved image and modify the screen size there-in. Is this what you're
doing?
best
Eliot
>
>
> Levente
>
>
> 2010/10/19 Levente Uzonyi <leves(a)elte.hu>:
>
>> On Tue, 19 Oct 2010, Max Leske wrote:
>>
>> The script used to be bash but some people had problems with it on other
>>> systems so Lukas rewrote it.
>>>
>>> That patch might be nice to have in an official VM...
>>>
>>
>> It may be in the next release. See the following thread:
>> http://lists.squeakfoundation.org/pipermail/vm-dev/2010-August/005253.html
>>
>>
>> Levente
>>
>>
>>> Max
>>>
>>> On 19.10.2010, at 22:07, Levente Uzonyi wrote:
>>>
>>> On Tue, 19 Oct 2010, Max Leske wrote:
>>>>
>>>> We can't... I wrote a script (Lukas rewrote it in C) which is active on
>>>>> his build server and replaces the relevant bits in the image after the
>>>>> build
>>>>> process.
>>>>> Check it out at github:
>>>>> http://github.com/renggli/builder/blob/master/tools/build-resize.c
>>>>>
>>>>
>>>> We were using the following bash script for this:
>>>>
>>>> $ cat resize-squeak.sh
>>>> #!/bin/bash
>>>>
>>>> if [ $# -ne 3 ]
>>>> then
>>>> echo "Usage: `basename $0` <image> <width> <height>"
>>>> exit 1
>>>> fi
>>>> echo -ne \\x$(printf "%02X" $[$3%256])\\x$(printf "%02X"
>>>> $[$3/256])\\x$(printf "%02X" $[$2%256])\\x$(printf "%02X" $[$2/256]) |
>>>> dd
>>>> of="$1" obs=1 seek=24 conv=block,notrunc cbs=4
>>>>
>>>> But we patched our VMs, so nowadays we do it from the image. :)
>>>>
>>>>
>>>> Levente
>>>>
>>>>
>>>>> Cheers,
>>>>> Max
>>>>>
>>>>>
>>>>> On 19.10.2010, at 20:35, Stéphane Ducasse wrote:
>>>>>
>>>>> I'm not sure that we can do that from the system and if this is not
>>>>>> something that can only set up by the OS.
>>>>>>
>>>>>> Stef
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>>
>>>>>>> I try to understand how I can change the size of the Pharo window.
>>>>>>>
>>>>>>> I tried this: Display setExtent: 1000@700 depth: 32; beDisplay.
>>>>>>>
>>>>>>> That seems to work ... but only a few milliseconds. After this delay,
>>>>>>> the window returns back to its previous size.
>>>>>>>
>>>>>>> Any suggestions? :)
>>>>>>>
>>>>>>> Adrien.
>>>>>>> _______________________________________________
>>>>>>> Pharo-project mailing list
>>>>>>> Pharo-project(a)lists.gforge.inria.fr
>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Pharo-project mailing list
>>>>>> Pharo-project(a)lists.gforge.inria.fr
>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> Pharo-project(a)lists.gforge.inria.fr
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> Pharo-project(a)lists.gforge.inria.fr
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project(a)lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
[Pharo-project] ^ character in ubuntu
by Diogenes Moreira
hi falks.
I'm using Pharo 1.1 OneClick Package in Ubuntu 10.4 with the follow locale.
when press ^ character in the pharo editor i get "?" symbol..
What configuration I need change?
Other data, if i using the cut & paste from othe application, that work
fine.
Thank in advance.
iogenes@diogenes-desktop:~$ locale
LANG=es_AR.utf8
LC_CTYPE="es_AR.utf8"
LC_NUMERIC="es_AR.utf8"
LC_TIME="es_AR.utf8"
LC_COLLATE="es_AR.utf8"
LC_MONETARY="es_AR.utf8"
LC_MESSAGES="es_AR.utf8"
LC_PAPER="es_AR.utf8"
LC_NAME="es_AR.utf8"
LC_ADDRESS="es_AR.utf8"
LC_TELEPHONE="es_AR.utf8"
LC_MEASUREMENT="es_AR.utf8"
LC_IDENTIFICATION="es_AR.utf8"
LC_ALL=
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS
diogenes@diogenes-desktop:~$ uname -a
Linux diogenes-desktop 2.6.32-25-generic-pae #44-Ubuntu SMP Fri Sep 17
21:57:48 UTC 2010 i686 GNU/Linux
Oct. 20, 2010
Re: [Pharo-project] Resize pharo window
by Levente Uzonyi
On Wed, 20 Oct 2010, Alexander LazareviÄ wrote:
> So you gonna remove the call to ioSetDisplayMode of the specific vm
display plugin from primitiveSetDisplayMode?
Alex
No, the idea is to replace the current implementation of ioSetDisplayMode:
return 0;
to another which saves the display size:
setSavedWindowSize((w << 16) + (h & 0xFFFF));
return 1;
Levente
2010/10/19 Levente Uzonyi <leves(a)elte.hu>:
> On Tue, 19 Oct 2010, Max Leske wrote:
>
>> The script used to be bash but some people had problems with it on other
>> systems so Lukas rewrote it.
>>
>> That patch might be nice to have in an official VM...
>
> It may be in the next release. See the following thread:
> http://lists.squeakfoundation.org/pipermail/vm-dev/2010-August/005253.html
>
>
> Levente
>
>>
>> Max
>>
>> On 19.10.2010, at 22:07, Levente Uzonyi wrote:
>>
>>> On Tue, 19 Oct 2010, Max Leske wrote:
>>>
>>>> We can't... I wrote a script (Lukas rewrote it in C) which is active on
>>>> his build server and replaces the relevant bits in the image after the build
>>>> process.
>>>> Check it out at github:
>>>> http://github.com/renggli/builder/blob/master/tools/build-resize.c
>>>
>>> We were using the following bash script for this:
>>>
>>> $ cat resize-squeak.sh
>>> #!/bin/bash
>>>
>>> if [ $# -ne 3 ]
>>> then
>>> Â Â Â echo "Usage: `basename $0` <image> <width> <height>"
>>> Â Â Â exit 1
>>> fi
>>> echo -ne \\x$(printf "%02X" $[$3%256])\\x$(printf "%02X"
>>> $[$3/256])\\x$(printf "%02X" $[$2%256])\\x$(printf "%02X" $[$2/256]) | dd
>>> of="$1" obs=1 seek=24 conv=block,notrunc cbs=4
>>>
>>> But we patched our VMs, so nowadays we do it from the image. :)
>>>
>>>
>>> Levente
>>>
>>>>
>>>> Cheers,
>>>> Max
>>>>
>>>>
>>>> On 19.10.2010, at 20:35, Stéphane Ducasse wrote:
>>>>
>>>>> I'm not sure that we can do that from the system and if this is not
>>>>> something that can only set up by the OS.
>>>>>
>>>>> Stef
>>>>>
>>>>>
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I try to understand how I can change the size of the Pharo window.
>>>>>>
>>>>>> I tried this: Display setExtent: 1000@700 depth: 32; beDisplay.
>>>>>>
>>>>>> That seems to work ... but only a few milliseconds. After this delay,
>>>>>> the window returns back to its previous size.
>>>>>>
>>>>>> Any suggestions? :)
>>>>>>
>>>>>> Adrien.
>>>>>> _______________________________________________
>>>>>> Pharo-project mailing list
>>>>>> Pharo-project(a)lists.gforge.inria.fr
>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> Pharo-project(a)lists.gforge.inria.fr
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> Pharo-project(a)lists.gforge.inria.fr
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project(a)lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
Pharo-project(a)lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Oct. 20, 2010
Re: [Pharo-project] ExpectedFailures in SUnit
by Stéphane Ducasse
+1
the problem is that we should sync with nial for SUNit but since brest I do not know what really make progress.
I still want to know the status of a test. what is red or not when it was packaged and shipped or is is my system the problem
Stef
On Oct 20, 2010, at 1:41 PM, Mariano Martinez Peck wrote:
>
>
> On Wed, Oct 20, 2010 at 12:15 PM, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote:
> Hi,
>
> Currently, to mark a test as an expected failure, `expectedFailures`
> should be overwritten
> (http://stackoverflow.com/questions/3976596/how-to-mark-expected-failures-in…)
> That's a bit tricky to figure out, so I added a comment to the method:
> SUnit-NikoSchwarz.114. However, I think it's still a usability bug:
> marking something as an expectedFailure isn't visible inside the test.
>
> I think expectedFailures should look through the pragmas of its tests
> and return an array of all method names that contain the pragma
> <expectedFailure>.
>
> Yes, that's better. But in addition, sometimes we need conditions. For example:
>
> Smalltalk listPlugins contains: 'blahhh' ifFalse[ expectedFailures add: 'testBlah' ]
>
> or whatever condition. Can you do that with pragmas?
>
> the other problem is that we don't have expectedErrors as well. This is bad and confusing.
>
> cheers
>
> mariano
>
>
>
>
>
> Cheers,
>
> Niko
>
> --
> http://scg.unibe.ch/staff/Schwarz
> twitter.com/nes1983
> Tel: +41 076 235 8683
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Oct. 20, 2010
Re: [Pharo-project] Faster access for refactoring commands
by Stéphane Ducasse
On Oct 20, 2010, at 1:32 PM, Martin Dias wrote:
> Hi,
>
> I really like to use refactoring commands in OmniBrowser, but I would like to access them faster. I think that it would be nice to have:
>
> - A shortcut that popups a menu with the refactor commands only.
> - A unique shortcut for rename (which target is the current selection: categories, class, method, class variable, instance variable, temporary)
>
> What do you think about it?
> Do you know if there is something like that already available to use?
Yes I would love to have a better organization with the most used refactoring actions also on the top of the menu.
I know lukas does not like that. Now what we can do it to have a package to add these items on top of
OB and we load it, after OB-RB and everybody is happy.
Can you provide that code?
> Martin
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Oct. 20, 2010
Re: [Pharo-project] TextLint questions and feedback
by Mariano Martinez Peck
Thanks Fabrizio and Jorge. Right now I have no time at all, but I promise
that for my next paper writing/revision I will check all that :)
Thanks a lot
mariano
2010/10/20 Fabrizio Perin <fabrizio.perin(a)gmail.com>
> Hi all,
> we did some modifications to the TextLint interface to address some of your
> requests:
>
> - now the wizard panel to select the file is bigger and resizable.
> - The selection of the style is embedded into the result panel below the
> file list
>
> Cheers,
>
> Fabrizio
>
> 2010/10/1 Jorge Ressia <jorge.ressia(a)gmail.com>
>
> Hi,
>>
>> We did a change in the way the files are opened.
>> We could not reproduce the same issue but we could manage to reproduce
>> other encoding issues.
>> So, please try your file again and let us know.
>>
>> Cheers,
>>
>> 2010/9/30 Mariano Martinez Peck <marianopeck(a)gmail.com>:
>> >
>> >
>> > On Thu, Sep 2, 2010 at 5:13 PM, Mariano Martinez Peck
>> > <marianopeck(a)gmail.com> wrote:
>> >>
>> >> Sorry, I forgot another bug. A piece of my latex is like this:
>> >>
>> >> \authorinfo{
>> >> Mariano Martinez Peck\affINRIA\affEMD \and
>> >> Noury Bouraqadi\affEMD \and
>> >> Marcus Denker\affINRIA \and
>> >> St\'ephane Ducasse\affINRIA \and
>> >> Luc Fabresse\affEMD
>> >> }{
>> >> $^1$RMoD Project-Team, Inria Lille--Nord Europe / Universit\'e
>> Lille 1
>> >> \\
>> >> $^2$Universit\'e Lille Nord de France, Ecole des Mines de Douai
>> >> }{marianopeck(a)gmail.com,
>> >> \{stephane.ducasse,marcus.denker\}(a)inria.fr
>> ,\\\{noury.bouraqadi,luc.fabresse\}(a)mines-douai.fr}
>> >> \maketitle
>> >>
>> >>
>> >> I don't know why...but once I saved the file, the image "frezzed" for a
>> >> long time, and then, if finished and that part was replaced by this:
>> >>
>> >>
>> >> \authorinfo{
>> >> Mariano Martinez Peck\affINRIA\affEMD \and
>> >> Noury Bouraqadi\affEMD \and
>> >> Marcus Denker\affINRIA \and
>> >> St\'ephane Ducasse\affINRIA \and
>> >> Luc Fabresse\affEMD
>> >> }{
>> >> $^1$RMoD Project-Team, Inria Lille--Nord Europe /
>> >>
>> UniversitâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâé
>> >> de Lille 1 \\
>> >> $^2$Universit\'e Lille Nord de France, Ecole des Mines de Douai
>> >> }{marianopeck(a)gmail.com,
>> >> \{stephane.ducasse,marcus.denker\}(a)inria.fr
>> ,\\\{noury.bouraqadi,luc.fabresse\}(a)mines-douai.fr}
>> >> \maketitle
>> >>
>> >
>> > Hi. TextLint is being used now even for non-smalltalkers :)
>> > Here my coworker is using it for his papers. THe problem he had, is the
>> same
>> > as mine. Without trying to do it, we put accents characters like é or è
>> or
>> > things like that in the TextLint pane. I don't know why but TextLint
>> starts
>> > to loop and writes all those characters (for example Ãâì) a lot of
>> times.
>> > For example, the file of my friend, went to 5MB!!!
>> >
>> > I know this is not TextLint fault, and probably Pharo, but avoiding this
>> > would be great.
>> >
>> > Cheers
>> >
>> > Mariano
>> >
>> >
>> >
>> >
>> >>
>> >> So...it seems something related to encoding...but no idea...
>> >>
>> >> thanks
>> >>
>> >> mariano
>> >>
>> >>
>> >> On Thu, Sep 2, 2010 at 3:42 PM, Mariano Martinez Peck
>> >> <marianopeck(a)gmail.com> wrote:
>> >>>
>> >>> Hi. First, please let me know if this is the correct place to talk
>> about
>> >>> TextLint. I've just used for one paper I am writing and I have some
>> >>> questions/feedback. I am using the one click image.
>> >>>
>> >>> 1) The "An Rule" could be a little more smart and detects commands.
>> For
>> >>> example, in my latex I have " an \emph{inner object}" and that was
>> detected
>> >>> by the rule, althought I shouldn't. So...detecting the slash and
>> ignore what
>> >>> it surrounded by {} would be nice for this rule.
>> >>>
>> >>> 2) When I edit the code inside TextLint and I save it, two bad things
>> >>> happens:
>> >>> 2.a) I lost focus of the text, as it moves when it finishing
>> >>> saving. The line I edited goes to the end of the text area. It would
>> be
>> >>> great if nothing moves nor to loose focus when saving.
>> >>> 2.b) sometimes (I cannot reproduce) the order of the rules
>> >>> changes...and this is not good because I was going in order, one by
>> one, and
>> >>> suddenly they are re-ordered. Maybe you are using a Set for that?
>> using a
>> >>> simple OrderedCollection could help.
>> >>>
>> >>> 3) If you edit the text (and it differs in the amount of characters),
>> and
>> >>> DO NOT save it, the following color highlighting are moved. It seems
>> you
>> >>> keep the position in the file, and until it is saved, rules results
>> are
>> >>> pointing to "unupdated" file. Of course, when I save the file, they
>> are
>> >>> correct. I guess this is from a performance point of view, but maybe
>> you
>> >>> have a little hack to do and make it better.
>> >>>
>> >>> 4) The rule "no white space before punctuation mark" showed me things
>> I
>> >>> didn't understand. For example, it says this line there is a ","
>> (comma) :
>> >>>
>> >>> \item[ Shared object ] In the case of the \emph{shared objects}, it
>> is
>> >>> almost the same as in the \emph{inner objects}. An .....
>> >>>
>> >>> 5) Rules comments clearer. For example, when you say "Avoid using a
>> lot,
>> >>> it weakens the sentence" It would be better to put "Avoid using "a
>> lot", it
>> >>> weakens the sentence"
>> >>> or "Avoid using *a lot*, it weakens the sentence"
>> >>> or something to clearly mark the words not to use. Because sometimes
>> the
>> >>> words are confused with the context. Or this one:
>> >>>
>> >>> "After an only words beginning with a vowel are allowed. "
>> >>> should be "After "an" only words beginning with a vowel are allowed."
>> >>>
>> >>> 6) For the rules of long sentences/paragraph it would be nice to
>> ignore
>> >>> \fotenote{}
>> >>>
>> >>> 7) Maybe this link is of interest for you:
>> >>>
>> http://matt.might.net/articles/shell-scripts-for-passive-voice-weasel-words…
>> >>>
>> >>> Apart from all these things, the tool is very useful and I like it.
>> >>>
>> >>> thanks
>> >>>
>> >>> Mariano
>> >>>
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > Pharo-project mailing list
>> > Pharo-project(a)lists.gforge.inria.fr
>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> >
>>
>>
>>
>> --
>> Jorge Ressia
>> www.jorgeressia.com
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
[Pharo-project] [ANN] Continue working in SimpleLogger
by Mariano Martinez Peck
Hi guys (German).
Today I needed to add some real log to something I am developing and I found
that SimpleLogger missed those functionalities I was needing. So...I
implemented them. It is 3 hours effort, so don't expect too much. But I just
wanted to shared with you in case you need it.
What I did basically is to define SimpleLogger like the public API. But
then, this class delegates to a LoggerStrategy. I created the following
implementations: TranscriptLoggerStrategy, NullLoggerStrategy,
FileLoggerStrategy and FixesFileNameLoggerStrategy. In addition, I created
a superclass for them, marking the API with SimpleLogger. This class is
LoggerStrategy.
So, now you can:
- Enable and disable easily the logging (thanks to NullLoggerStrategy).
- Change on runtime WHERE or HOW to log (just change the strategy).
- Be able to write into a File, a Transcript, a FixedFileName, or nothing.
- Extend to you own strategy (FileAppendLoggerStrategy??
SocketLoggerStrategy? etc...)
I did these changes today morning so I didn't have time to write tests nor
class comments. However, I wrote some class side example methods in
SimpleLogger.
Finally, for my own projects I want:
- to use a FixedFileName (very similar to the way PharoDebug.log is used).
- to only do "self log:" in my classes.
The solution I did is that somewhere (maybe in a class of your project or
maybe in a special class that holds this) in a class side variable I hold a
Singleton with the Logger. So that you can always do for example:
MyAppLogger logger log: 'zaraza'.
And finally, I implemented Object >> log: (with category *MyAppPackage)
log: anObject
MyAppLogger logger log: anObject.
With this, anywhere in the classes of my app I can do: self log:
'something'.
The code is temporally commited in http://www.squeaksource.com/Marea
German: if you think I should commit directly to SimpleLogger repo, just let
me know. In addition, be completely free to change it as you want and commit
it there too.
Cheers
mariano
Oct. 20, 2010
Re: [Pharo-project] Little change for Objects As Methods
by Noury Bouraqadi
Yes. An "object as method" is a placeholder. It should support the same API as CompiledMethods.
Noury
On 19 oct. 2010, at 13:14, Stéphane Ducasse wrote:
> Hi mariano
>
> I do not really like your solution. Implementing flushCache is not that bad in your class. It is not a bad compromise.
> May be it should be better documented.
>
> Stef
>
>
>> When you are using Objects as methods, MethodWrappers, or whatever with run:with:in, you have to implement not only that method, but also flushCache doing nothing because it is used in:
>>
>> MethodDictionary >> at: put:
>>
>> at: key put: value
>> "Set the value at key to be value."
>> | index |
>> index := self findElementOrNil: key.
>> (self basicAt: index) == nil
>> ifTrue:
>> [tally := tally + 1.
>> self basicAt: index put: key]
>> ifFalse:
>> [(array at: index) flushCache].
>> array at: index put: value.
>> self fullCheck.
>> ^ value
>>
>>
>> Ok, I can implement that in my classes, and in MethodWrappers, but I think it would be nicer and cleanly if you only have to implement run:with:in: since flushChache doesn't make sense for normal objects.
>>
>> So, I would like to change that code to
>>
>> at: key put: value
>> "Set the value at key to be value."
>> | index |
>> index := self findElementOrNil: key.
>> (self basicAt: index) == nil
>> ifTrue:
>> [tally := tally + 1.
>> self basicAt: index put: key]
>> ifFalse:
>> [(array at: index) isCompiledMethod ifTrue: [flushCache]].
>> array at: index put: value.
>> self fullCheck.
>> ^ value
>>
>>
>> Yes, yes, I know the if is ugly, but it gives us a cleaner way to define objects as methods.
>> The other option is to implement flushCache in Object doing nothing but I like it less than this.
>>
>> opinions?
>>
>> thanks
>>
>> mariano
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project(a)lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Oct. 20, 2010
Re: [Pharo-project] TextLint questions and feedback
by Fabrizio Perin
Hi all,
we did some modifications to the TextLint interface to address some of your
requests:
- now the wizard panel to select the file is bigger and resizable.
- The selection of the style is embedded into the result panel below the
file list
Cheers,
Fabrizio
2010/10/1 Jorge Ressia <jorge.ressia(a)gmail.com>
> Hi,
>
> We did a change in the way the files are opened.
> We could not reproduce the same issue but we could manage to reproduce
> other encoding issues.
> So, please try your file again and let us know.
>
> Cheers,
>
> 2010/9/30 Mariano Martinez Peck <marianopeck(a)gmail.com>:
> >
> >
> > On Thu, Sep 2, 2010 at 5:13 PM, Mariano Martinez Peck
> > <marianopeck(a)gmail.com> wrote:
> >>
> >> Sorry, I forgot another bug. A piece of my latex is like this:
> >>
> >> \authorinfo{
> >> Mariano Martinez Peck\affINRIA\affEMD \and
> >> Noury Bouraqadi\affEMD \and
> >> Marcus Denker\affINRIA \and
> >> St\'ephane Ducasse\affINRIA \and
> >> Luc Fabresse\affEMD
> >> }{
> >> $^1$RMoD Project-Team, Inria Lille--Nord Europe / Universit\'e Lille
> 1
> >> \\
> >> $^2$Universit\'e Lille Nord de France, Ecole des Mines de Douai
> >> }{marianopeck(a)gmail.com,
> >> \{stephane.ducasse,marcus.denker\}(a)inria.fr
> ,\\\{noury.bouraqadi,luc.fabresse\}(a)mines-douai.fr}
> >> \maketitle
> >>
> >>
> >> I don't know why...but once I saved the file, the image "frezzed" for a
> >> long time, and then, if finished and that part was replaced by this:
> >>
> >>
> >> \authorinfo{
> >> Mariano Martinez Peck\affINRIA\affEMD \and
> >> Noury Bouraqadi\affEMD \and
> >> Marcus Denker\affINRIA \and
> >> St\'ephane Ducasse\affINRIA \and
> >> Luc Fabresse\affEMD
> >> }{
> >> $^1$RMoD Project-Team, Inria Lille--Nord Europe /
> >>
> UniversitâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâìÃâé
> >> de Lille 1 \\
> >> $^2$Universit\'e Lille Nord de France, Ecole des Mines de Douai
> >> }{marianopeck(a)gmail.com,
> >> \{stephane.ducasse,marcus.denker\}(a)inria.fr
> ,\\\{noury.bouraqadi,luc.fabresse\}(a)mines-douai.fr}
> >> \maketitle
> >>
> >
> > Hi. TextLint is being used now even for non-smalltalkers :)
> > Here my coworker is using it for his papers. THe problem he had, is the
> same
> > as mine. Without trying to do it, we put accents characters like é or è
> or
> > things like that in the TextLint pane. I don't know why but TextLint
> starts
> > to loop and writes all those characters (for example Ãâì) a lot of
> times.
> > For example, the file of my friend, went to 5MB!!!
> >
> > I know this is not TextLint fault, and probably Pharo, but avoiding this
> > would be great.
> >
> > Cheers
> >
> > Mariano
> >
> >
> >
> >
> >>
> >> So...it seems something related to encoding...but no idea...
> >>
> >> thanks
> >>
> >> mariano
> >>
> >>
> >> On Thu, Sep 2, 2010 at 3:42 PM, Mariano Martinez Peck
> >> <marianopeck(a)gmail.com> wrote:
> >>>
> >>> Hi. First, please let me know if this is the correct place to talk
> about
> >>> TextLint. I've just used for one paper I am writing and I have some
> >>> questions/feedback. I am using the one click image.
> >>>
> >>> 1) The "An Rule" could be a little more smart and detects commands. For
> >>> example, in my latex I have " an \emph{inner object}" and that was
> detected
> >>> by the rule, althought I shouldn't. So...detecting the slash and ignore
> what
> >>> it surrounded by {} would be nice for this rule.
> >>>
> >>> 2) When I edit the code inside TextLint and I save it, two bad things
> >>> happens:
> >>> 2.a) I lost focus of the text, as it moves when it finishing
> >>> saving. The line I edited goes to the end of the text area. It would be
> >>> great if nothing moves nor to loose focus when saving.
> >>> 2.b) sometimes (I cannot reproduce) the order of the rules
> >>> changes...and this is not good because I was going in order, one by
> one, and
> >>> suddenly they are re-ordered. Maybe you are using a Set for that? using
> a
> >>> simple OrderedCollection could help.
> >>>
> >>> 3) If you edit the text (and it differs in the amount of characters),
> and
> >>> DO NOT save it, the following color highlighting are moved. It seems
> you
> >>> keep the position in the file, and until it is saved, rules results are
> >>> pointing to "unupdated" file. Of course, when I save the file, they are
> >>> correct. I guess this is from a performance point of view, but maybe
> you
> >>> have a little hack to do and make it better.
> >>>
> >>> 4) The rule "no white space before punctuation mark" showed me things I
> >>> didn't understand. For example, it says this line there is a ","
> (comma) :
> >>>
> >>> \item[ Shared object ] In the case of the \emph{shared objects}, it
> is
> >>> almost the same as in the \emph{inner objects}. An .....
> >>>
> >>> 5) Rules comments clearer. For example, when you say "Avoid using a
> lot,
> >>> it weakens the sentence" It would be better to put "Avoid using "a
> lot", it
> >>> weakens the sentence"
> >>> or "Avoid using *a lot*, it weakens the sentence"
> >>> or something to clearly mark the words not to use. Because sometimes
> the
> >>> words are confused with the context. Or this one:
> >>>
> >>> "After an only words beginning with a vowel are allowed. "
> >>> should be "After "an" only words beginning with a vowel are allowed."
> >>>
> >>> 6) For the rules of long sentences/paragraph it would be nice to ignore
> >>> \fotenote{}
> >>>
> >>> 7) Maybe this link is of interest for you:
> >>>
> http://matt.might.net/articles/shell-scripts-for-passive-voice-weasel-words…
> >>>
> >>> Apart from all these things, the tool is very useful and I like it.
> >>>
> >>> thanks
> >>>
> >>> Mariano
> >>>
> >>>
> >>
> >
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project(a)lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
>
>
>
> --
> Jorge Ressia
> www.jorgeressia.com
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
Re: [Pharo-project] Comment in Behavior >> allMethods is wrong ?
by Luc Fabresse
Yes, the comment does not match the implementation.
#Luc
2010/10/19 Mariano Martinez Peck <marianopeck(a)gmail.com>
> It says:
>
> Behavior >> allMethods
> "Return the collection of compiled method I am defining"
> "asArray is used to not bump into a bug when comparing compiled
> methods."
>
> ^ self allSelectors asArray collect: [ :s | self lookupSelector: s ]
>
>
> However...it answer not only the ones defined by itself, but also from
> superclasses. So...the comment is confusing for me. I am the only one ?
>
> cheers
>
> mariano
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
Re: [Pharo-project] ExpectedFailures in SUnit
by Mariano Martinez Peck
On Wed, Oct 20, 2010 at 12:15 PM, Niko Schwarz
<niko.schwarz(a)googlemail.com>wrote:
> Hi,
>
> Currently, to mark a test as an expected failure, `expectedFailures`
> should be overwritten
> (
> http://stackoverflow.com/questions/3976596/how-to-mark-expected-failures-in…
> ).
> That's a bit tricky to figure out, so I added a comment to the method:
> SUnit-NikoSchwarz.114.
Did you open a ticket? otherwise will be forgoten and nobody will integrate
it.
Cheers
Mariano
> However, I think it's still a usability bug:
> marking something as an expectedFailure isn't visible inside the test.
>
> I think expectedFailures should look through the pragmas of its tests
> and return an array of all method names that contain the pragma
> <expectedFailure>.
>
> Cheers,
>
> Niko
>
> --
> http://scg.unibe.ch/staff/Schwarz
> twitter.com/nes1983
> Tel: +41 076 235 8683
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
Re: [Pharo-project] ExpectedFailures in SUnit
by Mariano Martinez Peck
On Wed, Oct 20, 2010 at 12:15 PM, Niko Schwarz
<niko.schwarz(a)googlemail.com>wrote:
> Hi,
>
> Currently, to mark a test as an expected failure, `expectedFailures`
> should be overwritten
> (
> http://stackoverflow.com/questions/3976596/how-to-mark-expected-failures-in…
> ).
> That's a bit tricky to figure out, so I added a comment to the method:
> SUnit-NikoSchwarz.114. However, I think it's still a usability bug:
> marking something as an expectedFailure isn't visible inside the test.
>
> I think expectedFailures should look through the pragmas of its tests
> and return an array of all method names that contain the pragma
> <expectedFailure>.
>
Yes, that's better. But in addition, sometimes we need conditions. For
example:
Smalltalk listPlugins contains: 'blahhh' ifFalse[ expectedFailures add:
'testBlah' ]
or whatever condition. Can you do that with pragmas?
the other problem is that we don't have expectedErrors as well. This is bad
and confusing.
cheers
mariano
>
> Cheers,
>
> Niko
>
> --
> http://scg.unibe.ch/staff/Schwarz
> twitter.com/nes1983
> Tel: +41 076 235 8683
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010
Re: [Pharo-project] [ANN] ImageMap PharoKernel-12196
by Mariano Martinez Peck
On Wed, Oct 20, 2010 at 12:29 PM, Pavel Krivanek
<pavel.krivanek(a)gmail.com>wrote:
> No, but I'll try...
>
>
If you are going to do that, you should see the Graig Latta work. I copy
paste an email from me and him:
----------
Hi Graig. First, let me apologize for sending you this private email. Please
tell me if it is correct.
I am quite interested in having a system similar to Spoon. Actually, I want
something more related to LOOM, but Spoon is also part of my "state of the
art" ;)
I saw that your visualizations are very very cool. I saw this video:
http://www.youtube.com/watch?v=xCwidGFkn4Q
and then I see this link: http://www.caida.org/tools/visualization/walrus/
and finally I see
http://netjam.org/spoon/objects.graph.gz
I am working with Pharo for the moment. I wanted to ask if do you think it
is possible to make your kind of visualizations for a PharoCore image. Do I
need a specific VM? what should I do/code in the image side? Any hints is
more than welcome.
regarding the objects.graph.gz, you autogenerated that from the smalltlak
image and then use it as input for walrus ?
Thank you very much in advance,
Mariano
-------------
Sorry but walrus says "Walrus is a standalone application and not an API. It
cannot be incorporated into other applications."
So...how could you do it? maybe because the graph are text files, you
checked them and then tried to autogenerate one from an smalltalk image?
thanks again.
----------
Hi Mariano!
Yes, I learned the Walrus file format, and generated Walrus files
from the Smalltalk virtual machine simulator. It's odd that you couldn't
load the objects.graph into Walrus... perhaps Walrus has changed in the
meantime?
Making these files from the simulator doesn't require any special
virtual machine. I believe I included the Walrus support in the last
Spoon release. Please let me know if you can't find it.
thanks for writing!
> -- Pavel
>
> On Tue, Oct 19, 2010 at 9:15 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
> > Wow, this is really cool.
> >
> > Did you also try to visualize the object-graph using GraphViz?
> >
> > Lukas
> >
> > On 19 October 2010 20:49, Pavel Krivanek <pavel.krivanek(a)gmail.com>
> wrote:
> >> Hi,
> >>
> >> I generated the PharoKernel ImageMap (hypertext representation of the
> >> image content). You can see it here:
> >>
> >> http://goo.gl/nY2o
> >>
> >> The source code is here: http://goo.gl/J4T0
> >> CSS style is here: http://goo.gl/Pxw2
> >>
> >> Use it carefully, for 2,2MB image it generates 77,6MB of HTML files :-)
> >>
> >> Cheers,
> >> -- Pavel
> >>
> >> _______________________________________________
> >> Pharo-project mailing list
> >> Pharo-project(a)lists.gforge.inria.fr
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >>
> >
> >
> >
> > --
> > Lukas Renggli
> > www.lukas-renggli.ch
> >
> > _______________________________________________
> > Pharo-project mailing list
> > Pharo-project(a)lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
Oct. 20, 2010