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

Re: [Pharo-dev] missing packages in the Pharo50 repository

by Pavel Krivanek

I tried to do local repository with all Pharo packages. But I think that itÂ´s reasonable to add repositories of of external integrated projects. -- Pavel Dne ÃºterÃ½ 21. dubna 2015 stepharo <stepharo(a)free.fr> napsal(a): > It means that we should also add the repositories of these projects so > that MC can merge no? > > Le 20/4/15 22:19, Esteban Lorenzano a Ã©crit : > >> they are handled separately, through configurations. >> >> cheers, >> Esteban >> >> >>> On 20 Apr 2015, at 21:02, Pavel Krivanek <pavel.krivanek(a)gmail.com> >>> wrote: >>> >>> Hi, >>> >>> these packages do not have a version in the Pharo50 repository: >>> >>> Athens-Balloon >>> Athens-Cairo >>> Athens-CairoPools >>> Athens-Core >>> Athens-Examples >>> Athens-Morphic >>> Athens-Text >>> ConfigurationOfAthens >>> ConfigurationOfGlamourCore >>> ConfigurationOfGTInspectorCore >>> ConfigurationOfGToolkitCore >>> ConfigurationOfGTPlaygroundCore >>> ConfigurationOfGTSpotter >>> ConfigurationOfOSWindow >>> ConfigurationOfRubric >>> ConfigurationOfShoreLineReporter >>> ConfigurationOfTxText >>> ConfigurationOfVersionner >>> ConfigurationOfZincHTTPComponents >>> Glamour-Announcements >>> Glamour-Browsers >>> Glamour-Core >>> Glamour-Examples >>> Glamour-Helpers >>> Glamour-Morphic-Brick >>> Glamour-Morphic-Brick-Tests >>> Glamour-Morphic-Pager >>> Glamour-Morphic-Renderer >>> Glamour-Morphic-Theme >>> Glamour-Morphic-Widgets >>> Glamour-Presentations >>> Glamour-Rubric-Presentations >>> Glamour-Tests-Core >>> Glamour-Tests-Morphic >>> Glamour-Tests-Resources >>> Glamour-Tests-Rubric >>> GT-Inspector >>> GT-InspectorExtensions-Core >>> GT-Playground >>> GT-Spotter >>> GT-Spotter-EventRecorder >>> GT-SpotterExtensions-Core >>> GT-Tests-Inspector >>> GT-Tests-Playground >>> GT-Tests-Spotter >>> OSWindow-SDL2 >>> OSWindow-VM >>> Rubric >>> ShoreLine-Report-Core >>> ShoreLine-Report-Settings >>> ShoreLine-Report-UI >>> TxText-AthensTests >>> TxText-Model >>> TxText-Styler >>> TxTextTests-Model >>> Versionner-Core-Commands >>> Versionner-Core-Model >>> Versionner-Spec-Browser >>> Versionner-Tests-Core-Model >>> Zinc-HTTP >>> Zinc-Character-Encoding-Core >>> Zinc-Character-Encoding-Tests >>> Zinc-Resource-Meta-Core >>> Zinc-Resource-Meta-Tests >>> Zinc-Tests >>> Zinc-Zodiac >>> Zodiac-Core >>> Zodiac-Tests >>> >>> Cheers, >>> -- Pavel >>> >>> >> >> > >

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by stepharo

It means that we should also add the repositories of these projects so that MC can merge no? Le 20/4/15 22:19, Esteban Lorenzano a Ã©crit : > they are handled separately, through configurations. > > cheers, > Esteban > >> On 20 Apr 2015, at 21:02, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> Hi, >> >> these packages do not have a version in the Pharo50 repository: >> >> Athens-Balloon >> Athens-Cairo >> Athens-CairoPools >> Athens-Core >> Athens-Examples >> Athens-Morphic >> Athens-Text >> ConfigurationOfAthens >> ConfigurationOfGlamourCore >> ConfigurationOfGTInspectorCore >> ConfigurationOfGToolkitCore >> ConfigurationOfGTPlaygroundCore >> ConfigurationOfGTSpotter >> ConfigurationOfOSWindow >> ConfigurationOfRubric >> ConfigurationOfShoreLineReporter >> ConfigurationOfTxText >> ConfigurationOfVersionner >> ConfigurationOfZincHTTPComponents >> Glamour-Announcements >> Glamour-Browsers >> Glamour-Core >> Glamour-Examples >> Glamour-Helpers >> Glamour-Morphic-Brick >> Glamour-Morphic-Brick-Tests >> Glamour-Morphic-Pager >> Glamour-Morphic-Renderer >> Glamour-Morphic-Theme >> Glamour-Morphic-Widgets >> Glamour-Presentations >> Glamour-Rubric-Presentations >> Glamour-Tests-Core >> Glamour-Tests-Morphic >> Glamour-Tests-Resources >> Glamour-Tests-Rubric >> GT-Inspector >> GT-InspectorExtensions-Core >> GT-Playground >> GT-Spotter >> GT-Spotter-EventRecorder >> GT-SpotterExtensions-Core >> GT-Tests-Inspector >> GT-Tests-Playground >> GT-Tests-Spotter >> OSWindow-SDL2 >> OSWindow-VM >> Rubric >> ShoreLine-Report-Core >> ShoreLine-Report-Settings >> ShoreLine-Report-UI >> TxText-AthensTests >> TxText-Model >> TxText-Styler >> TxTextTests-Model >> Versionner-Core-Commands >> Versionner-Core-Model >> Versionner-Spec-Browser >> Versionner-Tests-Core-Model >> Zinc-HTTP >> Zinc-Character-Encoding-Core >> Zinc-Character-Encoding-Tests >> Zinc-Resource-Meta-Core >> Zinc-Resource-Meta-Tests >> Zinc-Tests >> Zinc-Zodiac >> Zodiac-Core >> Zodiac-Tests >> >> Cheers, >> -- Pavel >> > >

April 21, 2015

Re: [Pharo-dev] Seaside One Click Experience on Pharo 4?

by stepharo

Now it can also be the time to start using this description in books. stef Le 20/4/15 22:55, Dmitri Zagidulin a Ã©crit : > Thanks, Torsten. > I will definitely include those instructions in whatever documentation > I can get my hands on. > > But that's *in addition* to advocating that we update our Seaside > One-Click experience image. (For the reasons that I outline earlier in > this thread, namely that the vast majority of existing docs (books, > sites, blog posts) point new users to the One-Click images.) > > On Mon, Apr 20, 2015 at 3:48 PM, Torsten Bergmann <astares(a)gmx.de > <mailto:astares@gmx.de>> wrote: > > Hi Dmitri, > > not directly a one-click but in Pharo 4.0 you can load on your own: > > - open World menu -> "Tools" -> "Configuration Browser" > - load Seaside directly (which as of today is Seaside 3.1.4) > > After loading you can use "Tools" -> "Seaside control panel" to > add an adaptor > (see attached screenshot) and then browse Seaside on the defined > port like > http://localhost:8080 > > > If you like you can also load "Bootstrap" framework directly from > the config browser > - which is a wrapper for twitter bootstrap (see > http://pharo.pharocloud.com/bootstrap) > > There is also work going on for a Seaside 3.2. Dont know about the > timeline. > Ideally you should ask on the seaside-dev list: > > http://lists.squeakfoundation.org/pipermail/seaside-dev > > Bye > T. > > > > Gesendet: Montag, 20. April 2015 um 20:45 Uhr > Von: "Dmitri Zagidulin" <dmitri(a)zagidulin.net > <mailto:dmitri@zagidulin.net>> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org > <mailto:pharo-dev@lists.pharo.org>> > Betreff: Re: [Pharo-dev] Seaside One Click Experience on Pharo 4? > > (Just wanting to make sure this issue doesn't get lost in the > general 4.0 release activity and celebration). > > What's a good place to open an issue, as a reminder/to-do item to > create a Seaside+Pharo4 one-click image? The general Pharo fogbugz? > > Or, who would be the people to talk to? (Sean? :) ) > > > On Fri, Apr 10, 2015 at 3:10 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > It should not be that complex: > putting the vm in the folder and the pharo 40 image + sources > files. > > Stef > > Le 10/4/15 19:51, Dmitri Zagidulin a Ã©crit : > > Are there any plans to update the old Seaside One Click Experience > for Pharo 4.0 (and the latest stable Seaside)? > > And if not, what would be the level of effort required? (And/or, > who would be the people to talk to, to set it up?) > > The reason I ask is, users new to web development on Pharo > overwhelmingly get recommended to use the One Click images. > > - on > http://www.seaside.st/download/pharo[http://www.seaside.st/download/pharo] - > "The Seaside One-Click Experience is the easiest way to get > started with Seaside." Uses Pharo 1.4, I believe. > > - Learning Web Development with Seaside 3 > (http://seaside.gemtalksystems.com/tutorial/chapter01.pdf[http://seaside.gem… ) > also points to the Pharo download link above. Same deal, 1.4. > > - Dynamic Web Development with Seaside > (http://book.seaside.st/book[http://book.seaside.st/book] ) also > points to the One-Click. > > - Countless blog posts / tutorials link to it. > > - And, finally, Updated Pharo By Example (the Seaside chapter), > also recommends the One Click image. > > Given how much work the community has done since Pharo 1.4, would > it not make sense to update the integrated images? > >

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by stepharo

I guess that pavel is asking because of merge problems. Are they all manage under Pharo? > they are handled separately, through configurations. > > cheers, > Esteban > >> On 20 Apr 2015, at 21:02, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> Hi, >> >> these packages do not have a version in the Pharo50 repository: >> >> Athens-Balloon >> Athens-Cairo >> Athens-CairoPools >> Athens-Core >> Athens-Examples >> Athens-Morphic >> Athens-Text >> ConfigurationOfAthens >> ConfigurationOfGlamourCore >> ConfigurationOfGTInspectorCore >> ConfigurationOfGToolkitCore >> ConfigurationOfGTPlaygroundCore >> ConfigurationOfGTSpotter >> ConfigurationOfOSWindow >> ConfigurationOfRubric >> ConfigurationOfShoreLineReporter >> ConfigurationOfTxText >> ConfigurationOfVersionner >> ConfigurationOfZincHTTPComponents >> Glamour-Announcements >> Glamour-Browsers >> Glamour-Core >> Glamour-Examples >> Glamour-Helpers >> Glamour-Morphic-Brick >> Glamour-Morphic-Brick-Tests >> Glamour-Morphic-Pager >> Glamour-Morphic-Renderer >> Glamour-Morphic-Theme >> Glamour-Morphic-Widgets >> Glamour-Presentations >> Glamour-Rubric-Presentations >> Glamour-Tests-Core >> Glamour-Tests-Morphic >> Glamour-Tests-Resources >> Glamour-Tests-Rubric >> GT-Inspector >> GT-InspectorExtensions-Core >> GT-Playground >> GT-Spotter >> GT-Spotter-EventRecorder >> GT-SpotterExtensions-Core >> GT-Tests-Inspector >> GT-Tests-Playground >> GT-Tests-Spotter >> OSWindow-SDL2 >> OSWindow-VM >> Rubric >> ShoreLine-Report-Core >> ShoreLine-Report-Settings >> ShoreLine-Report-UI >> TxText-AthensTests >> TxText-Model >> TxText-Styler >> TxTextTests-Model >> Versionner-Core-Commands >> Versionner-Core-Model >> Versionner-Spec-Browser >> Versionner-Tests-Core-Model >> Zinc-HTTP >> Zinc-Character-Encoding-Core >> Zinc-Character-Encoding-Tests >> Zinc-Resource-Meta-Core >> Zinc-Resource-Meta-Tests >> Zinc-Tests >> Zinc-Zodiac >> Zodiac-Core >> Zodiac-Tests >> >> Cheers, >> -- Pavel >> > >

April 21, 2015

Re: [Pharo-dev] Little fix to MC merge facility

by stepharo

> No, I changed MCMethodDefinition>>= to be more relaxed about > sources and treat two sources that differ only in leading/trailing > spaces as "same". This way, these methods do not occur in merge tool > at all. > This is just a quick fix - much better would be to compare AST's and > treat whitespace-changes specially (i.e., provide a filter to show/hide > whitespace-only-changes). OK now I wonder if we want to have methods with different end of line conventions in the system. I do not remember the discussion we got long time ago. Stef >> Do you think that we should integrate it? > Yes. > >> Stef >> >> Le 20/4/15 12:36, Jan Vrany a Ã©crit : >>> Hi, >>> >>> I just wanted to merge some code in Monticello and the merge tool >>> marked all methods as conflict because their source differ in trailing >>> whitespace (newline). The diff panel on the right does not show any >>> difference. >>> >>> http://smalltalkhub.com/#!/~JanVrany/Misc/versions/Monticello-Fixes-JanVran… >>> >>> Here's a fix for this particular problem in case somebody runs into the >>> same problem. >>> >>> Best, Jan >>> >>> >>> >> > > >

April 21, 2015

Re: [Pharo-dev] GNU/Linux Old libC CI Job

by stepharo

Thanks a lot! We should probably put a link on the web site. Stef Le 20/4/15 20:38, Sean P. DeNigris a Ã©crit : > As part of our "first impressions count" effort to overhaul the download > process, I've created a Jenkins job on Pharo CI to build a VM for GNU/Linux > systems with libc < 2.15 (e.g. Debian 7) - a common gotcha for new users. > This VM used to be built externally by Jan Vrany (thanks!). > > The job is > https://ci.inria.fr/pharo/view/4.0-VM/job/PharoVM-GNU-linux-old_libc/ > The zip is mirrored to > http://files.pharo.org/vm/pharo/linux/old-libc/Pharo-VM-linux-oldLibC.zip > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/GNU-Linux-Old-libC-CI-Job-tp4820686.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 21, 2015

Re: [Pharo-dev] New Download instructions (esp. for GNU/Linux)

by Sean P. DeNigris

Ben Coman wrote > I am seeing some strange characters in some links... (maybe its just at > work I am using an old browser IE9) Yes they are strange, and no they're not due to IE9 (although I'd love to blame MS he he). They are due to a bug in Pillar with internal links [1]. The options were: a) have no internal links, or b) have the links with the funny characters. [1] http://forum.world.st/Pillar-Link-to-anchor-in-same-document-tt4819681.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Download-instructions-esp-for-GNU-Linux-tp4820692… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 21, 2015

Re: [Pharo-dev] New Download instructions (esp. for GNU/Linux)

by Ben Coman

I am seeing some strange characters in some links at http://pharo.org/gnu-linux-installation (maybe its just at work I am using an old browser IE9) cheers -ben On Tue, Apr 21, 2015 at 4:27 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > > On Mon, Apr 20, 2015 at 9:52 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> philippeback wrote >> > Hair splitting comment: CentOS, not Centos. >> >> Fixed. >> >> >> philippeback wrote >> > BTW, CentOS means also RHEL and Oracle Linux. >> >> I wasn't sure if linked libs would be guaranteed to be compatible/in the >> same location so I erred on the conservative side, but if you're sure >> they'll work, I could change it to "RedHat and derivatives" or whatever >> the >> proper term is. >> >> > RHEL 6 is the proper term. > CentOS 6 is built from the same sources, only the graphical assets are > changed. > > > >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/New-Download-instructions-esp-for-GNU-Linux-tp4820692… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > > > >

April 21, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by Sean P. DeNigris

laurent laffont wrote >>> Feel free to create it and give me access I will use this new >>> project as main repo. https://github.com/pharo-project/pharo-archlinux I sent you an invitation... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-ArchLinux-pharo-vm-pharo-launcher-packages-tp4749… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 20, 2015

Re: [Pharo-dev] GNU/Linux Old libC CI Job

by Bernardo Ezequiel Contreras

Thanks! On Mon, Apr 20, 2015 at 2:38 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > As part of our "first impressions count" effort to overhaul the download > process, I've created a Jenkins job on Pharo CI to build a VM for GNU/Linux > systems with libc < 2.15 (e.g. Debian 7) - a common gotcha for new users. > This VM used to be built externally by Jan Vrany (thanks!). > > The job is > https://ci.inria.fr/pharo/view/4.0-VM/job/PharoVM-GNU-linux-old_libc/ > The zip is mirrored to > http://files.pharo.org/vm/pharo/linux/old-libc/Pharo-VM-linux-oldLibC.zip > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/GNU-Linux-Old-libC-CI-Job-tp4820686.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

April 20, 2015