September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Image and bootstrap dependencies

by Christophe Demarey

Le 10 sept. 2015 Ã 15:31, Tudor Girba a Ã©crit : > Hi, > > Ok, I understand that part, but my question was: what code relationships does the analyzer take into account? Supported dependencies are: inheritance: you inherit from a class of another package reference: there is an explicit reference to a class of another package in a method trait: your class use a trait from another package method extension: you have in your package methods extending a class hosted in another package message sends (through manuallyResolvedDependencies): you code sends a message that is not implemented in your package nor in its declared dependencies. It misses slot dependencies but as it is not yet used a lot, it is not a problem.

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Stephan Eggermont

On 10-09-15 14:57, Aliaksei Syrel wrote: > Are you Apple's advertisment agent? :D No that is a direct quote. I'm just happy that Apple very slowly seems to move in the right direction. It will probably need a lot of pressure from EU to keep going in that direction. That makes them rather similar to Facebook, Microsoft and Google, and earlier IBM. Stephan

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Tudor Girba

Hi, Ok, I understand that part, but my question was: what code relationships does the analyzer take into account? Cheers, Doru On Thu, Sep 10, 2015 at 9:43 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > The data comes from the dependency analyzer analysis (re-compute each time > to avoid wrong information) + the information given in Manifests : > manuallyResolvedDependencies (potential dependencies needing a human > decision) and ignoredDependencies. > > Le 9 sept. 2015 Ã 23:32, Tudor Girba a Ã©crit : > > Hi, > > Very interesting. > > Could you detail which information you use for building the edges? > > Cheers, > Doru > > > > On Wed, Sep 9, 2015 at 11:33 AM, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > >> Hi, >> >> We now have a best overview of bootstrap dependencies. >> You can check the latest report at >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> . >> With Max, we reused Dijkstra algo in Moose to help finding dependencies >> leading to Morphic and co. >> It is now possible to have a visualization that is usable (there is also >> a button to open it in the report): >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> >> Next steps are to cut dependencies in red in the report table. >> >> Christophe. >> >> ps: by the way the dependency analyzer (with fixes asked) will be >> introduced soon in the image. >> >> <Capture dâÃ©cran 2015-09-09 Ã 11.33.02.png> >> >> Le 4 sept. 2015 Ã 15:13, Christophe Demarey a Ã©crit : >> >> Hi, >> >> I created a job to automatically generate a report of the Pharo image >> dependencies as well as current bootstrap dependencies. >> You can find them here: >> >> - >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> - >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> >> >> There are a lot (too many) dependencies but you can focus on some of them >> with the search field. >> Dependencies inside orange boxes are dependencies that are there but that >> we ignore (for example, an example method adds an extra-dependency). It >> should be fixed later but is not a problem for now. Ignored dependencies >> are declared in the package manifest in #ignoredDependencies. >> Dependencies inside red boxes are dependencies we want to remove for the >> bootstrap. For now, they are listed in the bootstrap dependency report. >> >> People that are willing to help to have a more modular Pharo could first >> take a look at the bootstrap dependency report and check dependencies that >> we should cut. >> Once we know, we can open issues on fogbugz in the 'bootstrap category' >> and update manifests accordingly. >> To investigate more deeply dependencies, you can use the >> DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies >> (inheritance, reference, extension, traits, message send). >> >> Regards, >> Christophe. >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Christophe Demarey

Hi Craig, Le 9 sept. 2015 Ã 11:53, Craig Latta a Ã©crit : > > Hoi Christophe-- > >> We now have a best overview of bootstrap dependencies. > > That's a pretty grim picture. :) Can you post a movie of you > picking through that ball of connections? (E.g., with the search feature > as you described, or any with any other UI affordance that you have with > this system.) Maybe a misunderstanding, the search feature is for the able only and not the graph itself. Yes, it is still a bit difficult to get the information because there are a lot of links between nodes. I will try Highlighting (http://www.coppelia.io/2014/07/an-a-to-z-of-extra-features-for-the-d3-force…) as suggested by Ben. Christophe.

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Aliaksei Syrel

On Thu, Sep 10, 2015 at 2:51 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Now everyone can get their app on their Apple device. > Xcode 7 and Swift now make it easier for everyone to build apps and run > them directly on their Apple devices. Simply sign in with your Apple ID, > and turn your idea into an app that you can touch on your iPad, iPhone, or > Apple Watch. Download Xcode 7 beta and try it yourself today. Program > membership is not required. > *Download Xcode 7 beta and try it yourself today.* Are you Apple's advertisment agent? :D

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Stephan Eggermont

On 10-09-15 14:26, Dimitris Chloupis wrote: > It would have to be a closed version, since Apple does not allow for apps > that can load third party code. Or did this change ? It changed. https://developer.apple.com/xcode/ Now everyone can get their app on their Apple device. Xcode 7 and Swift now make it easier for everyone to build apps and run them directly on their Apple devices. Simply sign in with your Apple ID, and turn your idea into an app that you can touch on your iPad, iPhone, or Apple Watch. Download Xcode 7 beta and try it yourself today. Program membership is not required. Stephan

Sept. 10, 2015

Re: [Pharo-dev] FreeType hinting: any way to get a grayscale version for the subpixel rendering?

by Nicolai Hess

2015-09-10 13:24 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > No, already tried that, still hinting with RGB artefacts. > What platform ? (on windows, setting the montor type to CRT, this works) (and morphic or bloc?, because bloc uses Athens and athens does not care about this freetype setting) > > Any command I can type in a workspace|playground in case the dropdown > doesn't do anything? > > FreeTypeSettings current subPixelAntiAliasing: false. FreeTypeCache current removeAll. World restoreMorphicDisplay > Phil > > On Thu, Sep 10, 2015 at 1:17 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> Try Setting -> Appeareance -> Use Free type ... -> Monitor type "CRT" >> >> 2015-09-10 12:51 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> >>> Is there a way to hint without having the subpixels rendered with the >>> RGB artifacts? >>> Just getting grayscale for the font? >>> >>> I ask because it is getting disturbing for me with larger fonts. >>> >>> I saw some monoHinting in FreeTypeSettings but there doesn't seem a way >>> to set that up. >>> >>> TIA >>> Phil >>> >> >> >

Sept. 10, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 10, 2015

[pharo-project/pharo-core] 4cfe70: 50317

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4cfe70b2c80c49214510341c61034174732b4633 https://github.com/pharo-project/pharo-core/commit/4cfe70b2c80c49214510341c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-10 (Thu, 10 Sep 2015) Changed paths: M Morphic-Base.package/MenuMorph.class/definition.st M Morphic-Base.package/MenuMorph.class/instance/accessing/stayUp_.st M Morphic-Base.package/MenuMorph.class/instance/construction-title/addStayUpIcons.st M Morphic-Base.package/MenuMorph.class/instance/construction-title/addStayUpItem.st M Morphic-Base.package/MenuMorph.class/instance/construction-title/addTitle_.st M Morphic-Base.package/MenuMorph.class/instance/construction-title/addTitle_icon_.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/buildTitle_.st A Morphic-Base.package/MenuMorph.class/instance/construction-title/createTitleMorph.st R Morphic-Base.package/MenuMorph.class/instance/construction-title/newTitleIconCalling_form_helpText_.st M Morphic-Base.package/MenuMorph.class/instance/events/updateColor.st R Morphic-Base.package/MenuMorph.class/instance/invoking/informUserAt_during_.st R Morphic-Base.package/MenuMorph.class/instance/menu/removeStayUpBox.st R Morphic-Base.package/MenuMorph.class/instance/private/setTitleParametersFor_.st A Morphic-Base.package/MenuTitleMorph.class/README.md A Morphic-Base.package/MenuTitleMorph.class/definition.st A Morphic-Base.package/MenuTitleMorph.class/instance/construction/font_.st A Morphic-Base.package/MenuTitleMorph.class/instance/construction/icon_.st A Morphic-Base.package/MenuTitleMorph.class/instance/construction/title_.st A Morphic-Base.package/MenuTitleMorph.class/instance/construction/withCloseBox.st A Morphic-Base.package/MenuTitleMorph.class/instance/construction/withPinBox.st A Morphic-Base.package/MenuTitleMorph.class/instance/event handling/closeBoxClicked.st A Morphic-Base.package/MenuTitleMorph.class/instance/event handling/pinBoxClicked.st A Morphic-Base.package/MenuTitleMorph.class/instance/initialization/defaultBorderColor.st A Morphic-Base.package/MenuTitleMorph.class/instance/initialization/defaultColor.st A Morphic-Base.package/MenuTitleMorph.class/instance/initialization/initialize.st A Morphic-Base.package/MenuTitleMorph.class/instance/private-creation/iconButtonCalling_withForm_helpText_.st M Morphic-Base.package/PluggableMenuSpec.class/instance/morphic/asMenuMorph.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50316.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50317.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50316.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50317.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/SyntaxErrorDebugger.class/instance/initialization/release.st Log Message: ----------- 50317 16541 type relase vs release in SyntaxErrorDebugger https://pharo.fogbugz.com/f/cases/16541 16526 CubeHelix class example throws assertion error https://pharo.fogbugz.com/f/cases/16526 16509 MenuTitleMorph for MenuMorph https://pharo.fogbugz.com/f/cases/16509 http://files.pharo.org/image/50/50317.zip

Sept. 10, 2015

Re: [Pharo-dev] Pharo on iPad Pro

by Dimitris Chloupis

It would have to be a closed version, since Apple does not allow for apps that can load third party code. Or did this change ? Are there other IDEs on iPad ? It has been sometime since the last time I used my G1 ipad, I own an android tablet but I am very tempted to switch back to iPad. On Thu, Sep 10, 2015 at 1:15 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > ;) > > > On 10 Sep 2015, at 11:36, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > > Now we have to make the first IDE tailored specially for iPad Pro :) > > > > Uko > > > > >

Sept. 10, 2015