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

Re: [Pharo-dev] ANNC: QRCode Generator

by StÃ©phane Ducasse

Nice. I will read the website you rmention in the class comment. Stef On Nov 30, 2013, at 9:21 AM, "J.F. Rick" <self(a)je77.com> wrote: > http://smalltalkhub.com/#!/~JochenRick/QRCode > > Enjoy! > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Nov. 30, 2013

Re: [Pharo-dev] Nautilus unload...

by StÃ©phane Ducasse

Pavel I tried your scripts (see below) UnReloader unloadNautilusRefactoring UnReloader switchToOldBrowser. UnReloader unloadNautilus2 and I get unloadNautilus2 | deletePackages | deletePackages := [:packageNames | SystemNavigation default removeAllButPackages: ((MCWorkingCopy allManagers collect: #packageName) asSortedCollection copyWithoutAll: packageNames). packageNames do: [:pn | (ScriptLoader new workingCopyFromPackageName: pn) unregister. (RPackage named: pn) unregister]]. #Nautilus asClass cleanUp. #NautilusUI asClass allInstances do: [ :inst | SystemAnnouncer uniqueInstance unsubscribe: inst]. Smalltalk garbageCollect. deletePackages value: #('NautilusRefactoring' 'NautilusCommon' 'Nautilus' 'Refactoring-Critics' 'Refactoring-Changes' 'Refactoring-Core' 'Refactoring-Environment' 'GroupManager' 'Manifest-Core' 'Manifest-CriticBrowser'). KMRepository reset. KMPragmaKeymapBuilder release. Smalltalk resetTools. 5 timesRepeat:[Smalltalk garbageCollect.]. Smalltalk fixObsoleteReferences. SystemNavigation default obsoleteClasses. Undeclared. On Nov 30, 2013, at 9:06 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > did not work either :( > Really I wonder if we will succeed to have a modular system one day. > If we do not exercise it it will never happen. > Stef > > > unloadNautilus > > #Nautilus asClass cleanUp. > KMRepository reset. > KMPragmaKeymapBuilder release. > #NautilusUI asClass allSubInstances do: [ :inst | > SystemAnnouncer uniqueInstance unsubscribe: inst]. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > {Nautilus. PackageTreeNautilus} do: #resetGroups. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > Smalltalk garbageCollect. > (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. > (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload. > (MCWorkingCopy forPackage: (MCPackage named: 'GroupManager')) unload. > >

Nov. 30, 2013

ANNC: QRCode Generator

by J.F. Rick

http://smalltalkhub.com/#!/~JochenRick/QRCode Enjoy! Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Nov. 30, 2013

Re: [Pharo-dev] Added shop page

by Christoph Wysseier

Hi Phil Am 29.11.13 11:45, schrieb phil(a)highoctane.be: > Thanks. > > One problem I do have is how the hell can I change some look and feel > pieces. That's more a general thing for the presentation framework than > the content. The look and feel is predefined by the designer. You then only characterize the content which adopts automatically the predefined styles. Cmsbox was created to manage CONTENT not STYLE as we address a specific, non-technical target group. Therefore you cannot change styles anywhere. > My main "surprise" was that I needed blocks for everything. And that > doing italics was hard, when I wanted to do a citation. Or is it another > way? HTML5 was created with some new semantic tags such as article, sections, ... We anticipated this development by introducing "Articles" which keep the content semantically together which is also the basis for good SEO. Besides, yes, you really need for each paragraph a new text element as this allows us to create semantically and standard compliant HTML code which is on of the main goals. Each element at the represents an HTML tag or set of tags at the end. Hint: You should not want to format content but to adjust its function. Each element has therefore properties which are always context-sensitive within the black toolbar on the righten side. Hint2: Use the element "Table" for the links to the Shops at http://www.pharo-project.org/community/shop. Besides, link can have a description and a link action. You do not need to show the whole link within the content again if you do not want too. > As I am a Tiki Wiki CMS Groupware team member, this is indeed a > different way to look at things (https://tiki.org/Communications+Team) > But I guess the codebase there is 100% non Pharo. And most of you on > this list would, well, run away :-) > But the community is quite working well. Check > https://tiki.org/Monthly+Team+Meetings Of course, Tiki Wiki and Cmsbox do not have anything in common beside the content management goal. This is due to the target group which is completely different. I would not want to explain wiki syntax to the secretary of a Swiss carpenter. ;) > The Pharo site looks somewhat dated by today's standards (Have a look at > the AngularJS site to see what I mean http://angularjs.org/, ). +1. An example using Responsive Design would even be better as Stef tends to force mobile devices. > Next week, I have a meeting w/ a young designer who will be proposing me > new looks, we'll see if we get traction with the community and if yes, > get a new look on. +100. If the community accepts your proposal we would love to adopt the styles to new design. We are programmers and therefore dependant on designers input... but if we get it, we can do almost everything your want: http://www.cmsbox.com/en/showcase/our-websites Cheers, Chris -- Christoph Wysseier netstyle.ch GmbH, CEO

Nov. 30, 2013

Re: [Pharo-dev] Nautilus unload...

by StÃ©phane Ducasse

did not work either :( Really I wonder if we will succeed to have a modular system one day. If we do not exercise it it will never happen. Stef unloadNautilus #Nautilus asClass cleanUp. KMRepository reset. KMPragmaKeymapBuilder release. #NautilusUI asClass allSubInstances do: [ :inst | SystemAnnouncer uniqueInstance unsubscribe: inst]. Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. {Nautilus. PackageTreeNautilus} do: #resetGroups. Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. Smalltalk garbageCollect. (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload. (MCWorkingCopy forPackage: (MCPackage named: 'GroupManager')) unload.

Nov. 30, 2013

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by Igor Stasenko

On 30 November 2013 02:36, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > No pb, I think I know how to fix this > > feel free to commit fix to Athens SVG package. Any help is welcome. > Alexandre > > > > Le 29-11-2013 Ã 17:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a > Ã©crit : > > > > > >> So far you cannot import, but only export SVG in Roassal. I know Athens > has an SVG importer, but I have faced some problems with it. > > > > and do not expect it to be fixed soon. Because we have other priorities. > > > > Stef > > -- Best regards, Igor Stasenko.

Nov. 30, 2013

Re: [Pharo-dev] Athens-Cairo is part of Pharo?

by Igor Stasenko

On 30 November 2013 08:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > May be igor can simply do not use it and we remove it directly. > > well, it would be easy if it just about me, but it was part of API for a while, which i deprecated not long ago (by changing to better name). > Hi all, > > There's a deprecated method in Athens-Cairo. > method: AthensCairoSurface>>#createLinearGradient:origin:corner: > category: #paints > package: RGPackage(Athens-Cairo) > > Should i move it to Deprecated package? > > https://pharo.fogbugz.com/f/cases/11668/Move-all-deprecated-method-to-Depre… > > Thanks. > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > > > -- Best regards, Igor Stasenko.

Nov. 30, 2013

Re: [Pharo-dev] Athens-Cairo is part of Pharo?

by Igor Stasenko

On 30 November 2013 00:32, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com > wrote: > Hi all, > > There's a deprecated method in Athens-Cairo. > method: AthensCairoSurface>>#createLinearGradient:origin:corner: > category: #paints > package: RGPackage(Athens-Cairo) > > Should i move it to Deprecated package? > > https://pharo.fogbugz.com/f/cases/11668/Move-all-deprecated-method-to-Depre… > > Good question. The problem is, that this method has 3 implementors.. and it is a deprecated protocol in Athens API.. not all 3 of them deprecated yet. i fixed them (by deprecating as well), but for moving them to another package doesn't fits well with my guts. By moving this method outside of scope of Athens, you make Athens non-portable. That's maybe not a big deal in this concrete case.. since Athens is part of Pharo now, but i have a feeling that such practice is anti-modular, because it marries specific version of Athens with specific version of Pharo image then, and doing it implicitly.. feels like good old monolithic image ways .. I am not sure what would be better way to go.. any good ideas? Thanks. > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. > -- Best regards, Igor Stasenko.

Nov. 30, 2013

Re: [Pharo-dev] Athens-Cairo is part of Pharo?

by StÃ©phane Ducasse

May be igor can simply do not use it and we remove it directly. > Hi all, > > There's a deprecated method in Athens-Cairo. > method: AthensCairoSurface>>#createLinearGradient:origin:corner: > category: #paints > package: RGPackage(Athens-Cairo) > > Should i move it to Deprecated package? > https://pharo.fogbugz.com/f/cases/11668/Move-all-deprecated-method-to-Depre… > > Thanks. > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America.

Nov. 30, 2013

Re: [Pharo-dev] Similarity Matrix

by StÃ©phane Ducasse

Really nice. In fact it would be ****great**** if we can plug the comparison between the x and y cells (which can be different). Because like that we get a simple matrix based comparator similar to the one of early paper of prejinshight work. > <Screen Shot 2013-11-29 at 6.12.39 PM.png>

Nov. 30, 2013