- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40204 Home: https://github.com/pharo-project/pharo-core

Sept. 5, 2014

[pharo-project/pharo-core] 6e121d: 40204

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6e121dedd980671460a13d092867a28dce002371 https://github.com/pharo-project/pharo-core/commit/6e121dedd980671460a13d09… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-05 (Fri, 05 Sep 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script204.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40204.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Announcements.package/MethodAdded.class/definition.st R System-Announcements.package/MethodAdded.class/instance/accessing/method.st M System-Announcements.package/MethodAdded.class/instance/accessing/methodClass.st R System-Announcements.package/MethodAdded.class/instance/accessing/method_.st M System-Announcements.package/MethodAdded.class/instance/accessing/protocol.st M System-Announcements.package/MethodAdded.class/instance/accessing/selector.st A System-Announcements.package/MethodAnnouncement.class/README.md A System-Announcements.package/MethodAnnouncement.class/definition.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/method.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/methodAffected.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/methodClass.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/methodOrigin.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/method_.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/protocol.st A System-Announcements.package/MethodAnnouncement.class/instance/accessing/selector.st A System-Announcements.package/MethodAnnouncement.class/instance/testing/isProvidedByATrait.st M System-Announcements.package/MethodModified.class/class/instance creation/methodChangedFrom_to_selector_inClass_oldProtocol_newProtocol_requestor_.st M System-Announcements.package/MethodModified.class/definition.st M System-Announcements.package/MethodModified.class/instance/accessing/methodClass.st M System-Announcements.package/MethodModified.class/instance/accessing/newMethod.st M System-Announcements.package/MethodModified.class/instance/accessing/newMethod_.st M System-Announcements.package/MethodModified.class/instance/accessing/newProtocol.st M System-Announcements.package/MethodModified.class/instance/accessing/selector.st M System-Announcements.package/MethodRecategorized.class/class/instance creation/method_selector_class_newProtocol_oldProtocol_.st M System-Announcements.package/MethodRecategorized.class/definition.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/methodClass.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/methodRecategorized.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/methodRecategorized_.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/newProtocol.st M System-Announcements.package/MethodRecategorized.class/instance/accessing/selector.st M System-Announcements.package/MethodRemoved.class/class/instance creation/methodRemoved_selector_protocol_class_origin_.st M System-Announcements.package/MethodRemoved.class/definition.st M System-Announcements.package/MethodRemoved.class/instance/accessing/methodClass.st M System-Announcements.package/MethodRemoved.class/instance/accessing/methodOrigin.st M System-Announcements.package/MethodRemoved.class/instance/accessing/methodRemoved.st M System-Announcements.package/MethodRemoved.class/instance/accessing/methodRemoved_.st M System-Announcements.package/MethodRemoved.class/instance/accessing/selector.st Log Message: ----------- 40204 13953 Clean method announcements - step 1 https://pharo.fogbugz.com/f/cases/13953 http://files.pharo.org/image/40/40204.zip

Sept. 5, 2014

Re: [Pharo-dev] AppeX

by phil＠highoctane.be

Maybe we can start small. I've current needs that could well be handled in the environment. The FileBrowser is in my view quite not used enough. When doing web applications, I deal with Javascript, CSS, content files etc all the time. The FileBrowser allows to edit files in its content pane. Doing an Accept (Alt-S) on the pane saves the file. So, instead of starting an external edit session in Vim, I mostly work there for some smaller changes (like tweaking CSS). Now, if we could have a syntax highlighter in there it would be nice. For CSS it wouldn't be too damn hard I think. Phil On Fri, Sep 5, 2014 at 3:35 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi Torsten, Phil, > > On Thu, 2014-09-04 at 14:18 +0200, Torsten Bergmann wrote: > > Hi Phil, > > > > if there is something I would like to see our Pharo ecosystem and ST in > general moving > > towards is to such a "multilanguage"/"multisourcecode"/"flexible > ressources" kind of > > thing. Even when this could not be a short term goal I would like to see > this > > in the long term. > > I've been working in this area for many years now. And have learned a > good deal while doing that :-) > Making one language to execute within other's environment is the easy > part, though it could be a lot of work (especially, if you care about > performance). Making tools to be aware of different languages is not > hard too, thought it is "just" a huge amount of work that has to be > done. The tricky part is to allow one to talk to each other, preserving > each other's semantics and still stay intuitive, clear and free of > unnecessary boilerplate code. Another tricky bit is to make other > workflows and ways of coding things in other languages work nicely with > the way Smalltalk way we do it in Smalltalk. These are tough bits. > That's where a real research has yet to be done... > > > - running Java inside of Smalltalk/X > > Well, Smalltalk/X can do much more with Java than "just" run it. > Java has been fully integrated into development tools supporting full > development cycle :-) > > >

Sept. 5, 2014

Re: [Pharo-dev] #canUnderstand: and #canPerform: issue

by Yuriy Tymchuk

I second this idea. But maybe there are some other points of view (the method was changed for some reason after all) Uko On 05 Sep 2014, at 15:26, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 5 sept. 2014, at 15:12, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi everyone, >> >> I think that itâs essential to solve this, please take a look: https://pharo.fogbugz.com/f/cases/13962/canPerform-same-as-canUnderstand > > Before #canUnderstand was checking if the class understands a selector and canPerform: was also checking if the method has an implementation (it is not a shouldBeImplemented, subclassResponsibility or explicitRequirement). When it changed some critic rules got crazy, raising critics that should not have been. > I think we should just rollback to that old behavior, for ex with: > > canUnderstand: aSymbol > ^ (self lookupMethod: aSymbol) notNil > > canPerform: aSymbol > ^ (self lookupMethod: aSymbol) > ifNil: [ false ] > ifNotNil: [ :m | m isProvided ] > > Camille > >> Uko > >

Sept. 5, 2014

Re: [Pharo-dev] AppeX

by Jan Vrany

Hi Torsten, Phil, On Thu, 2014-09-04 at 14:18 +0200, Torsten Bergmann wrote: > Hi Phil, > > if there is something I would like to see our Pharo ecosystem and ST in general moving > towards is to such a "multilanguage"/"multisourcecode"/"flexible ressources" kind of > thing. Even when this could not be a short term goal I would like to see this > in the long term. I've been working in this area for many years now. And have learned a good deal while doing that :-) Making one language to execute within other's environment is the easy part, though it could be a lot of work (especially, if you care about performance). Making tools to be aware of different languages is not hard too, thought it is "just" a huge amount of work that has to be done. The tricky part is to allow one to talk to each other, preserving each other's semantics and still stay intuitive, clear and free of unnecessary boilerplate code. Another tricky bit is to make other workflows and ways of coding things in other languages work nicely with the way Smalltalk way we do it in Smalltalk. These are tough bits. That's where a real research has yet to be done... > - running Java inside of Smalltalk/X Well, Smalltalk/X can do much more with Java than "just" run it. Java has been fully integrated into development tools supporting full development cycle :-)

Sept. 5, 2014

Re: [Pharo-dev] Pharo-contribution down

by Marcus Denker

Ok, I restarted On Fri, Sep 5, 2014 at 3:20 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Can anyone restart? :) > > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Sept. 5, 2014

Re: [Pharo-dev] #canUnderstand: and #canPerform: issue

by Camille Teruel

On 5 sept. 2014, at 15:12, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone, > > I think that itâs essential to solve this, please take a look: https://pharo.fogbugz.com/f/cases/13962/canPerform-same-as-canUnderstand Before #canUnderstand was checking if the class understands a selector and canPerform: was also checking if the method has an implementation (it is not a shouldBeImplemented, subclassResponsibility or explicitRequirement). When it changed some critic rules got crazy, raising critics that should not have been. I think we should just rollback to that old behavior, for ex with: canUnderstand: aSymbol ^ (self lookupMethod: aSymbol) notNil canPerform: aSymbol ^ (self lookupMethod: aSymbol) ifNil: [ false ] ifNotNil: [ :m | m isProvided ] Camille > Uko

Sept. 5, 2014

Pharo-contribution down

by Yuriy Tymchuk

Can anyone restart? :)

Sept. 5, 2014

#canUnderstand: and #canPerform: issue

by Yuriy Tymchuk

Hi everyone, I think that itâs essential to solve this, please take a look: https://pharo.fogbugz.com/f/cases/13962/canPerform-same-as-canUnderstand Uko

Sept. 5, 2014

Re: [Pharo-dev] Any changes with fonts?

by Juraj Kubelka

I will check it. Thanks for the report. Juraj El 05-09-2014, a las 4:17, Nicolai Hess <nicolaihess(a)web.de> escribiÃ³: > 2014-09-05 9:41 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Uhâ¦ am I the only one stuck with Bitmap DejaVu Sans? Is everybody else able to change fonts? > > Uko > > No , me too. This happens since: > > 40195 > 13185 Move embedded fonts from Freetype package into separate package > https://pharo.fogbugz.com/f/cases/13185 > > > > > > On 02 Sep 2014, at 20:47, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Hi, > > > > when I cannot see system fonts anymore after selecting Free Type font checkbox in settings. Are there any changes to fonts? Of something broke down? > > > > Uko > > >

Sept. 5, 2014