November 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3248 in pharo: Bad error message for non existing changes file.

by pharo＠googlecode.com

Updates: Status: Started Labels: -Milestone-1.2 Comment #6 on issue 3248 by marcus.denker: Bad error message for non existing changes file. http://code.google.com/p/pharo/issues/detail?id=3248 Can not find a fix. --> Status Started Not a showstopper --> remove Milestone 1.2

Nov. 25, 2010

Re: [Pharo-project] Issue 3267 in pharo: MultiNewParagraphWithSelectionColor depracted

by pharo＠googlecode.com

Updates: Status: Invalid Comment #4 on issue 3267 by marcus.denker: MultiNewParagraphWithSelectionColor depracted http://code.google.com/p/pharo/issues/detail?id=3267 (No comment was entered for this change.)

Nov. 25, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Comment #2 on issue 3291 by marcus.denker: Missing text field with completion http://code.google.com/p/pharo/issues/detail?id=3291 Not for 1.2?

Nov. 25, 2010

Re: [Pharo-project] Issue 3189 in pharo: Changes not working since update 12220

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3189 by marcus.denker: Changes not working since update 12220 http://code.google.com/p/pharo/issues/detail?id=3189 can not reproduce

Nov. 25, 2010

Re: [Pharo-project] Issue 3181 in pharo: PharoCorePackageDependenciesTests failure and error

by pharo＠googlecode.com

Updates: Status: Fixed Comment #3 on issue 3181 by marcus.denker: PharoCorePackageDependenciesTests failure and error http://code.google.com/p/pharo/issues/detail?id=3181 (No comment was entered for this change.)

Nov. 25, 2010

Re: [Pharo-project] Issue 3255 in pharo: It should be possible to print text from help browser to printer

by pharo＠googlecode.com

Updates: Status: Started Labels: -Milestone-1.2 Comment #5 on issue 3255 by marcus.denker: It should be possible to print text from help browser to printer http://code.google.com/p/pharo/issues/detail?id=3255 No. Does not work on the Mac.

Nov. 25, 2010

Re: [Pharo-project] Issue 3292 in pharo: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97'

by pharo＠googlecode.com

Comment #1 on issue 3292 by johanbri...(a)me.com: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97' http://code.google.com/p/pharo/issues/detail?id=3292 Amongst other missing things, all timestamp cases were indeed not covered yet. A fix is coming up...

Nov. 25, 2010

[Pharo-project] Issue 3293 in pharo: UITheme examples broken

by pharo＠googlecode.com

Status: Fixed Owner: gazzaguru2 CC: nicolas.cellier.aka.nice, marcus.denker Labels: Milestone-1.2 New issue 3293 by gazzaguru2: UITheme examples broken http://code.google.com/p/pharo/issues/detail?id=3293 Due to Color>>wheel: refactoring. Fix CS attached. Attachments: ThemeExampleFixes.1.cs 8.8 KB

Nov. 25, 2010

Re: [Pharo-project] [squeak-dev] [ANN] Exif

by Alexander LazareviÄ

Thanks. It should work also in Pharo.now. Alex 2010/11/25 Lukas Renggli <renggli(a)gmail.com> > Very cool, thanks a lot for sharing this! > > Lukas > > On 25 November 2010 08:47, Alexander LazareviÄ <laza(a)blobworks.com> wrote: > > Hi! > > > > I just uploaded a first hack of an Exif package to squeaksource. > > > > http://www.squeaksource.com/Exif.html > > > > MIT License. Any contributions are welcome (see current limitations). > > Haven't tested it on Pharo yet. But there shouldn't be anything special > > about it. > > > > Have fun, > > Alex > > > > From the project description: > > > > This provides code to extract/modify the Exif (Exchangeable image file > > format) information from/inside media files. > > > > Current limitations: > > > > Works only for TIFF-, JPEG-files > > Can't write Exif information > > Can't read/write GPS information > > Can't read/write Interoperability information > > Can't read/write any vendor specific MakerNote > > Can't read/write UserComments > > Most methods for cooked information (like dateTime) are missing > > > > Examples: > > "Dump all Exif information from a JPEG-file to the Transcript" > > Transcript show: (Exif readFromJPEGNamed: 'p2.jpg') printAll; cr. > > > > "Get raw Exif content for DateTime (a String)" > > (Exif readFromJPEGNamed: 'p2.jpg') atTagName: #DateTime. "#('2010:11:10 > > 16:56:33')" > > > > "Get cooked Exif content for DateTime (a DateAndTime object)" > > (Exif readFromJPEGNamed: 'p2.jpg') dateTime. "2010-11-10T16:56:33+01:00" > > > > Specs: > > Exif and TIFF > > > > Disclaimer: > > This software is provided as is. It is in a very early stage and there > are > > no guaranties that the software will work as expected or advertised. > > Be sure to use only image files with this software that you have backed > up > > before. I refuse any responsibility for any data lost while using this > > software. > > > > > > > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Nov. 25, 2010

Re: [Pharo-project] Some question about categories, packages and extensions

by StÃ©phane Ducasse

Hi cyrille On Nov 25, 2010, at 1:04 PM, Cyrille Delaunay wrote: > Hello > > I am currently writing some tests about all that and some questions comed in mind :) > > => If I create a category named: 'Category' from the classic browser, it does not create a package in the monticello browser. > Is that behavior something clearly wanted or is it just resulting from something I don't know ? for now there is no direct mapping from category to package. We have to declare a package with the category name and it will match the subcategories. > => I define a class in this category, still nothing in the monticello browser > > => I defined in any class a category named: '*cAtEGorY', still nothing. because it is empty? > => If I define a method in this category, monticello browser display the package and merge the extension and the existing category. But the name of the monticello package generated is: 'CAtEGorY. Should'nt it have the name of the smalltalk category instead ? Even if no package are defined. this is strange I would have thought that we would not get anything if the package is not defined. > > Then about extensions, what are the rule applied to consider a class category as an extension. > I guess there is > => no distinctions about the case of the name (*cAteGory should be consider as an extension of Category) indeed > => if the name of the class category match with the beginning of an existing package ('*CategorySubCategory should be consider as an extension of Category ?? ) > Is there something more ? pay attention that you can have multiple package starting with the same name. Stef

Nov. 25, 2010