- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] Continue working in SimpleLogger
by Mariano Martinez Peck Oct. 21, 2010

Oct. 21, 2010

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

2 2

[Pharo-project] [update 1.2] #12201
by StÃ©phane Ducasse Oct. 21, 2010

Oct. 21, 2010

12201 ----- - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!!

3 3

[Pharo-project] non-modal FillInTheBlankMorph code?
by Eliot Miranda Oct. 21, 2010

Oct. 21, 2010

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

2 1

Re: [Pharo-project] [ANN] Continue working in SimpleLogger
by Mariano Martinez Peck Oct. 20, 2010

Oct. 20, 2010

On Thu, Oct 21, 2010 at 12:26 AM, GermÃ¡n Arduino <garduino(a)gmail.com> wrote: > Thanks you very much Mariano! > > Sound very interesting. > > I only read the mail by now (not time, as usual) but as soon as I have > a bit of free time, will try and make my comments. > > Of course, not problem in that you commit on the SimpleLogger repo, I > added you as Developer. > > Cheers. > GermÃ¡n. > > > 2010/10/20 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > 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 > > >

1 0

[Pharo-project] Anyone has seen Dale?
by Alexandre Bergel Oct. 20, 2010

Oct. 20, 2010

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

[Pharo-project] [update 1.2] #12202
by StÃ©phane Ducasse Oct. 20, 2010

Oct. 20, 2010

12202 ----- - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!!

1 0

Re: [Pharo-project] Plug-in Licensing
by Schwab,Wilhelm K Oct. 20, 2010

Oct. 20, 2010

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

1 0

Oct. 20, 2010

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

1 0

[Pharo-project] Crytography package.
by Diogenes Moreira Oct. 20, 2010

Oct. 20, 2010

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..

1 0

Oct. 20, 2010

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

6 8