- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Does Pharo stores original author of methods?

by Marcus Denker

> On 22 Nov 2015, at 20:12, EuanM <euanmee(a)gmail.com> wrote: > > Is there any reason against amending Monticello to store and save all > author's names? It does. *If* you have all the versionsâ¦ but doing anything with âall the versionsâ is so slow (you need to download them, unpack themâ¦) that we do not even have a tool to show the history of a method. (getting the oldest should be simpler, if you have complete history+this .mcz is there). Monticello is meant to be a system to save the complete history of a project (if you keep all the MCZ available), but the idea to save every tiny revision as a complete snapshot, zip compresses, makes it near impossible to do anything with the history in practice. With today disks, a practical SCM would allow anyone to have the *complete* history on the local disk. Monticello does now allow that in any practical way. > > Presumably, we'd also want a tool that could extract amnders' names > all the way back to the first commit of a package? > > How many on-line Monticello repositories are in common use? > > (I know of SqueakSource.com, Smalltalkhub.com and SqueakSource3) > > Are there active administrators for each of those repositories that > would allow us to update the repositories to use the updated > Monticello? > > On 22 November 2015 at 15:42, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On 20 Nov 2015, at 14:35, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> >> 2015-11-20 14:21 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: >>> >>> epicea data is not stored forever. It is seasion based and the shipped >>> image is >>> clean. >> >> >> But current source of this info is changes file (maybe sources). And I >> remember you planned to store current sources in image. And such information >> can be there too. >> Maybe I miss something? >> >> >> The original author is not really that much of information. And storing it >> for every method in the image would take space. >> >> As I said: the whole idea of using a source revision control system is that >> you have the *complete* history available, but >> not wasting RAM. >> >> Marcus >

Nov. 23, 2015

Re: [Pharo-dev] Metacello load script won't update the configuration

by Yuriy Tymchuk

Hi, when Iâm trying to do this now, adding a `get` command causes âproject, baseline, or configuration not specifiedâ error. Is it a but in metacello, or the API changed? Cheers. Uko > On 14 Sep 2015, at 23:10, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Uko, > > The `get` command is used to load a fresh copy of the ConfigurationOf or BaselineOf so the following should do the trick: > > Metacello new > smalltalkhubUser: 'Pharo' > project: 'MetaRepoForPharo40'; > configuration: 'QualityAssistant'; > get; > load > > > I make the loading of the BaselineOf and ConfigurationOf explicit so that the developer can control when and if they want a new copy of the BaselineOf or ConfigurationOf. > > For github urls like github://project/user/project, the `get` command causes the system to invalidate the cache directory so that on the next load, the github cache for the project is freshly downloaded so that you get the latest version of the BaselineOf ... > > Dale > > On 09/14/2015 01:49 PM, Yuriy Tymchuk wrote: >> Hi, >> >> when you use a script like >> >> Metacello new >> smalltalkhubUser: 'Pharo' >> project: 'MetaRepoForPharo40'; >> configuration: 'QualityAssistant'; >> load >> >> and you already have the configuration package loaded, the script is not updating the configuration itself. As the result you cannot update to a newer version. Is there a special expression that has to be used to update the configuration package? If not, maybe it does make sense to update the configuration before loading it? >> >> Cheers! >> Uko >

Nov. 23, 2015

Re: [Pharo-dev] Cleanup of debug requests API

by Denis Kudriashov

Fixed slice in inbox 2015-11-21 13:07 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2015-11-21 10:55 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> The SyntaxErrorDebugger registers itself for Smalltalk tools: >> >> registerToolsOn: registry >> "Add ourselves to registry. See [Smalltalk tools]" >> registry register: self as: #syntaxErrorDebugger >> >> And this is used by MorphicUIManager >> syntaxErrorNotificationDefaultAction: anException >> > > Thank's. I will revert it >

Nov. 23, 2015

Re: [Pharo-dev] red banner and links with safari?

by Sven Van Caekenberghe

> On 23 Nov 2015, at 08:24, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 22-11-15 23:53, Ben Coman wrote: >> I guess the only real fix for the https pages produced to reference >> https stylesheets. >> cheers -ben >> >> On Mon, Nov 23, 2015 at 1:58 AM, Peter UhnÃ¡k >> <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> > The question now is: what do we need to fix to make it work? > > Rewrite all internal links to use https when served over https Better yet, rewrite all links to be properly relative and independent of the scheme used. This can also be done with external resources, for example:  <link href="//fonts.googleapis.com/css?family=Lato:400" rel="stylesheet" type="text/css"> <link href="//fonts.googleapis.com/css?family=Titillium+Web:400" rel="stylesheet" type="text/css">  <link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css"> Note the weird but valid // syntax of the URLs. Sven

Nov. 23, 2015

Re: [Pharo-dev] Digest from slack to the mailing list?

by Yuriy Tymchuk

The problem is, that it is not that easy to create a âdigestâ from Slack, as there is no kind of grouping. Either you have to detect similar words in discussion, or you have to simply export everything. I donât know whether it makes sense to just compose a huge email of all discussions, but we can try to do that. Cheers. Uko > On 23 Nov 2015, at 00:21, EuanM <euanmee(a)gmail.com> wrote: > > I agree - if we can have each 24 hours of chat archived to somewhere > that provides a free-text search, that would be very good. > > Up until now, I've been grabbing, editting and posting chats I find of > interest and importance to me. And it seems to lend itself to design > discussions. What it's not very good at, atm, is discussion > threading. It would be great to be able to set your typing as > belonging to a thread., so that when it get sucked out and archived > that the threads were segregated. > > Does someone have a server that could receive a text dump of all > recent Slack messages every 12 (or 24, or 6) hours, and then make it > available for indexing by Google et al, and querying (via the search > engines) by our dev base? > > > > > > On 22 November 2015 at 13:57, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> Just to clear something up , because I see people in slack saying goodbye, >> or "I cant reply right now I have something to do" . Slack is not just a >> real time chat, it keeps messages inside a history of 10 thousand messages. >> So that means you can log in Slack at any time and not lose a message. There >> is no reason for you to be online all time, no reason to say goodbye, >> goodmorning , goodafternoon. You can come and go as you please the exact >> same way as the mailing list. >> >> The problem arises when we exceed 10k messages, the old ones get lost and I >> think having a place to store them is a good idea. >> >> Also what is important is in the eye of the beholder, for example I dont >> care about any discussion about web development , its just does not interest >> me or database coding or many other things. I have learned to filter out the >> messages I dont care about in the mailing list and just reject them. Slack >> is same story, I quickly glance through its history and I can search the >> messages that interest me using the search bar , I can star messages that I >> want to keep, and I can comment on existing messages / code snippets which >> create a thread about that message. >> >> In the end its impossible to keep the community in one place but to have a >> central hub that collects all the little gems can be quite useful. >> >> On Sun, Nov 22, 2015 at 3:46 PM stepharo <stepharo(a)free.fr> wrote: >>> >>> Yes this would be good. >>> People should understand that important discussions should be via the >>> mailing-list. >>> Emails are good because you can consume them the way you want. >>> I simply cannot be connected all the time. So emails are good because I >>> can process them >>> when I decide. >>> Slack is good for more interactive session around debugger and things >>> like that. >>> >>> Stef >>> >>> >>> Le 21/11/15 18:05, Stephan Eggermont a Ã©crit : >>>> Should we have a digest from slack to a mailing list? >>>> We are already losing messages >>>> >>>> Stephan >>>> >>>> >>>> >>> >>> >> >

Nov. 23, 2015

Re: [Pharo-dev] Refactoring and traitsâ¦

by Nicolai Hess

2015-11-23 9:01 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > But is there an issue or not? Because I was not able to find it. If there > is no issue I will create one. > please create one. There are two other issues about RB and Traits but they don't match this issue - I think > > Cheers. > Uko > > > > On 21 Nov 2015, at 12:15, stepharo <stepharo(a)free.fr> wrote: > > > > > > > > Le 20/11/15 15:01, Yuriy Tymchuk a Ã©crit : > >> Hi guys, > >> > >> is it a known issue that if you are refactoring something (eg. doing a > class rename) and some changes should happen in a method which comes from > trait, then new methods are compiled in concrete classes instead of > changing the trait method? > > > > Yes the problem is just money. > > > > Stef > >> > >> Cheers. > >> Uko > >> > > > > > > >

Nov. 23, 2015

Re: [Pharo-dev] Refactoring and traitsâ¦

by Yuriy Tymchuk

But is there an issue or not? Because I was not able to find it. If there is no issue I will create one. Cheers. Uko > On 21 Nov 2015, at 12:15, stepharo <stepharo(a)free.fr> wrote: > > > > Le 20/11/15 15:01, Yuriy Tymchuk a Ã©crit : >> Hi guys, >> >> is it a known issue that if you are refactoring something (eg. doing a class rename) and some changes should happen in a method which comes from trait, then new methods are compiled in concrete classes instead of changing the trait method? > > Yes the problem is just money. > > Stef >> >> Cheers. >> Uko >> > >

Nov. 23, 2015

Re: [Pharo-dev] red banner and links with safari?

by Stephan Eggermont

On 22-11-15 23:53, Ben Coman wrote: > I guess the only real fix for the https pages produced to reference > https stylesheets. > cheers -ben > > On Mon, Nov 23, 2015 at 1:58 AM, Peter UhnÃ¡k > <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > > The question now is: what do we need to fix to make it work? Rewrite all internal links to use https when served over https Stephan

Nov. 23, 2015

Re: [Pharo-dev] Digest from slack to the mailing list?

by EuanM

I agree - if we can have each 24 hours of chat archived to somewhere that provides a free-text search, that would be very good. Up until now, I've been grabbing, editting and posting chats I find of interest and importance to me. And it seems to lend itself to design discussions. What it's not very good at, atm, is discussion threading. It would be great to be able to set your typing as belonging to a thread., so that when it get sucked out and archived that the threads were segregated. Does someone have a server that could receive a text dump of all recent Slack messages every 12 (or 24, or 6) hours, and then make it available for indexing by Google et al, and querying (via the search engines) by our dev base? On 22 November 2015 at 13:57, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Just to clear something up , because I see people in slack saying goodbye, > or "I cant reply right now I have something to do" . Slack is not just a > real time chat, it keeps messages inside a history of 10 thousand messages. > So that means you can log in Slack at any time and not lose a message. There > is no reason for you to be online all time, no reason to say goodbye, > goodmorning , goodafternoon. You can come and go as you please the exact > same way as the mailing list. > > The problem arises when we exceed 10k messages, the old ones get lost and I > think having a place to store them is a good idea. > > Also what is important is in the eye of the beholder, for example I dont > care about any discussion about web development , its just does not interest > me or database coding or many other things. I have learned to filter out the > messages I dont care about in the mailing list and just reject them. Slack > is same story, I quickly glance through its history and I can search the > messages that interest me using the search bar , I can star messages that I > want to keep, and I can comment on existing messages / code snippets which > create a thread about that message. > > In the end its impossible to keep the community in one place but to have a > central hub that collects all the little gems can be quite useful. > > On Sun, Nov 22, 2015 at 3:46 PM stepharo <stepharo(a)free.fr> wrote: >> >> Yes this would be good. >> People should understand that important discussions should be via the >> mailing-list. >> Emails are good because you can consume them the way you want. >> I simply cannot be connected all the time. So emails are good because I >> can process them >> when I decide. >> Slack is good for more interactive session around debugger and things >> like that. >> >> Stef >> >> >> Le 21/11/15 18:05, Stephan Eggermont a Ã©crit : >> > Should we have a digest from slack to a mailing list? >> > We are already losing messages >> > >> > Stephan >> > >> > >> > >> >> >

Nov. 22, 2015

Re: [Pharo-dev] Does Pharo stores original author of methods?

by EuanM

Is there any reason against amending Monticello to store and save all author's names? Presumably, we'd also want a tool that could extract amnders' names all the way back to the first commit of a package? How many on-line Monticello repositories are in common use? (I know of SqueakSource.com, Smalltalkhub.com and SqueakSource3) Are there active administrators for each of those repositories that would allow us to update the repositories to use the updated Monticello? On 22 November 2015 at 15:42, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 20 Nov 2015, at 14:35, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2015-11-20 14:21 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >> epicea data is not stored forever. It is seasion based and the shipped >> image is >> clean. > > > But current source of this info is changes file (maybe sources). And I > remember you planned to store current sources in image. And such information > can be there too. > Maybe I miss something? > > > The original author is not really that much of information. And storing it > for every method in the image would take space. > > As I said: the whole idea of using a source revision control system is that > you have the *complete* history available, but > not wasting RAM. > > Marcus

Nov. 22, 2015