Re: [Pharo-dev] Updating the CI

This is done. Everything is working well. I closed the issue. https://pharo.fogbugz.com/f/cases/edit/20299/ On Thu, Aug 10, 2017 at 11:56 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi all, > > I'm updating some CI plugins right now. Will notify as soon as everyth

[Pharo-dev] Writeup: how to contribute to Pharo

Hi, I've made some write up for the pharo part (not metacello or external projects) https://github.com/guillep/PharoIntegrationProcess/wiki/ Contribute-a-fix-to-Pharo Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. Guille -- Guille Polito

Re: [Pharo-dev] Impediment to contributing

Hi, I've made some write up for the pharo part (not metacello or external projects) https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. Guille On Thu, Aug 10, 2017

Re: [Pharo-dev] post-download preparation of Pharo 7 image

On Thu, Aug 10, 2017 at 11:55 AM, Pavel Krivanek wrote: > Hi, > > currently we are fighting with several issues that make contributions to > Pharo 7 much more complicated than we would like. Even in case you have no > troubles with long paths (on Windows) nor SSH keys,

[Pharo-dev] Updating the CI

Hi all, I'm updating some CI plugins right now. Will notify as soon as everything is smooth again. The issue related to the update is here: https://pharo.fogbugz.com/f/cases/20299/Update-CI-plugins-to-latest-git-plugins (yes, we have an issue so we can keep track of the plugins we have) --

[Pharo-dev] [ Pharo 70 ] build 24 / PR 188

This PR is only jenkins related, it does not modify any pharo code. https://pharo.fogbugz.com/f/cases/20297/Avoid-deadlocks-in-jenkins https://github.com/pharo-project/pharo/pull/188 It produced build 24. Build artifacts in here: http://files.pharo.org/image/70/ -- Guille Polito Research

Re: [Pharo-dev] [Pharo 70] build 19 / PR-168

Probably you already saw it, but builds are green again. As I told you this afternoon, there are some hiccups that cause failures from time to time. We should chase them one by one :) Le mer. 9 août 2017 à 21:47, Stephane Ducasse a écrit : > >

Re: [Pharo-dev] Pull requests ready to be reviewed

On Wed, Aug 9, 2017 at 11:09 AM, Pavel Krivanek wrote: > We have several pull requests validated successfully by the > infrastructure. They need to be reviewed by humans: > > https://github.com/pharo-project/pharo/pull/75 > This one has a merge coflict. > > >

Re: [Pharo-dev] FileSystem fix integration

Hi Stef, On Tue, Aug 8, 2017 at 7:00 PM, Stephane Ducasse wrote: > Hi Alistair > > I'm going over the green build first. > > - Can you tell me what you think about the PR 92 05723 Default Working > Directory > https://pharo.fogbugz.com/f/cases/5723/ This cannot be

Re: [Pharo-dev] Creating the smallest server runtime footprint

;>>>> "IdentityDictionary(Dictionary)>>at:ifAbsent:", >>>>>>>> "IdentityDictionary(Dictionary)>>at:ifAbsentPut:", >>>>>>>> "FLLightGeneralMapper(FLMapper)>>clusterInstanceOf:keyInBu

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

On Mon, Aug 7, 2017 at 3:17 AM, Ben Coman <b...@openinworld.com> wrote: > > > On Mon, Aug 7, 2017 at 12:25 AM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> >> On Sun, Aug 6, 2017 at 5:46 PM, Ben Coman <b...@openinworld.com> wrote: >

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

On Sun, Aug 6, 2017 at 5:46 PM, Ben Coman <b...@openinworld.com> wrote: > On Sun, Aug 6, 2017 at 3:45 PM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> About tagging... It looks super ackward to me to tag EVERY commit with >> "build informati

Re: [Pharo-dev] About cr and lf

Line put the underlying OS line ending. >> >> Then we should revisit all the cr inside the system and use newline. >> Then we should think about the internal usage of cr by default in >> Pharo (We should change it). >> >> Does it make sense? >> Stef >>

Re: [Pharo-dev] Having green builds

And for the lazy ones, here is the link to the build (that can be also accessed from the PR) https://ci.inria.fr/pharo-ci-jenkins2/job/test%20multibranch%20pipeline/job/PR-184/ On Sun, Aug 6, 2017 at 11:00 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > Hi all, > >

Re: [Pharo-dev] About cr and lf

; Pharo (We should change it). > Yes, and we should teach people (this means documenting :P) the correct usage of streams :). > Does it make sense? > Stef > > Stef > > On Sun, Aug 6, 2017 at 10:36 AM, Sven Van Caekenberghe <s...@stfx.eu> > wrote: > > > >>

[Pharo-dev] Having green builds

Hi all, As you all know, we are now building from github. Integrations are made through pull requests. And pull requests are validated using jenkins (that is back again, Yay!). In this scenario, pull requests validations in github differentiate only between three states: Pased (green) and not

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

se ;)). This means that we can rebuild all images by just iterating the git history and building from scratch. No need to store all images. On Sun, Aug 6, 2017 at 9:40 AM, Guillermo Polito <guillermopol...@gmail.com> wrote: > I made a PR > > https://github.com/pharo-project/pharo/pull/1

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

number available so it does not make much sense Once the PR is accepted/integrated, we should change the build process to use this script. Guille On Sun, Aug 6, 2017 at 9:05 AM, Guillermo Polito <guillermopol...@gmail.com> wrote: > Hi, I created an issue: > > https://pharo.fogbugz

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

Hi, I created an issue: https://pharo.fogbugz.com/f/cases/20290/Add-build-number-to-uploaded-files I propose to keep both the sha and add the build number. Also, to follow semantic version conventions, we should use $- instead of $/. Something like:

Re: [Pharo-dev] About cr and lf

Can somebody propose an implementation besides on top of this discussion? I propose such an implementation should take the form of a stream decorator instead of changing the base implementation. Guille On Sun, Aug 6, 2017 at 12:01 AM, Peter Uhnak wrote: > Hi, > > just to

Re: [Pharo-dev] About cr and lf

Hi all, First, we should not confuse "writing into a stream" with "writing into a text file". Not all streams are to write into a text file. This means that we cannot pretend that the basic stream implementation should always do a conversion. I think that should belong to a text writer, also

Re: [Pharo-dev] About cr and lf

But the question is: what does cr do? - Does it write a platform independent newLine? - Or does it write a (platform dependent) cr ascii character? http://www.theasciicode.com.ar/ascii-control-characters/carriage-return-ascii-code-13.html On Fri, Aug 4, 2017 at 12:50 PM, Jan Vrany

Re: [Pharo-dev] Creating the smallest server runtime footprint

Yes, you should be able to load an mcz in that image by doing: (MCDirectoryRepository new directory: 'where-your-mcz-is') loadVersionFromFileNamed: 'Metacello-GitBasedRepository-Author.1.mcz') load. Guille On Wed, Aug 2, 2017 at 7:57 AM, Pavel Krivanek wrote: > >

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

> architecture). >>>>>> >>>>>> Hermes is using a custom format completely separated from Fuel or any >>>>>> other tool. >>>>>> >>>>>> This is a consequence of the design of Hermes. Hermes has been >>&g

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

On Tue, Aug 1, 2017 at 12:57 PM, philippe.b...@highoctane.be < philippe.b...@gmail.com> wrote: > Massive. > > What is in the super small image? > Is Hermes going to be a generic binary content loader? > There is still work to do in this front. - Hermes only works for 32bits format. We should

Re: [Pharo-dev] [ci-announces] IMPORTANT: Virtual Machines loss

I don't want to be pesimistic, but this means we don't have CI until we restore all slaves. From the Pharo point of view, we lost almost all but 1 or 2 slaves in different ci servers. Check: - https://ci.inria.fr/pharo/ - https://ci.inria.fr/pharo-contribution/ -

[Pharo-dev] Human Reviews of Pull Requests

Hi all, As PRs are starting to stack, I think it would be good to gradually merge them. For that, I think it would be good to have both the automatic and a human review. When you issue a PR to the development branch, you see two validations are launched: - basic validation - full validation

Re: [Pharo-dev] No Metadata in 7.0

On Sun, Jul 9, 2017 at 10:10 PM, Henrik Nergaard wrote: > Hi, > > I had a look at the Pharo 7.0 today and see metadata for methods (Author > and timestamp) has been removed*, what is the reason for this? > > Having the ability to find methods created around the same time

Re: [Pharo-dev] Pull requests reviews

If you don't mind, I'll transform your script into a class and commit it somewhere :) On Wed, Jul 5, 2017 at 8:30 AM, Pavel Krivanek wrote: > So loading of the PR packages is very simple. Do at the end: > > diff := IceDiff from: headCommit to: bootstrapCommit. > diff

Re: [Pharo-dev] The new implementation of current working directory

On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant wrote: > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. > > While I'm in favour of Rajula's proposed changes, scripting in > particular will be much easier,

[Pharo-dev] Early Pull Request Validation Process

Hi all, As some/a lot of you have been asking how to contribute, I'm here to answer some questions :). First of all, integrating fixes in Pharo has been "slowed down" because we missed the Monkey for Pull Request (PR) integration. Some of you have seen a travis job going around and checking.

Re: [Pharo-dev] Flattened traits in Pharo 7

But that's not the case. The only usage of traits in the Kernel is TBehaviour, to share some common behaviour between traits and classes. But Pablo is working on a new modular implementation of traits that would not require TBehavior, and would simplify the code of classes. On Tue, Jun 27, 2017

Re: [Pharo-dev] Doing a pull request

Thanks pavel, I'll copy paste it in the README :) On Thu, Jun 15, 2017 at 10:43 AM, Rajula Vineet wrote: > @abergel I was looking for some basic guidelines for example: creating a > new > branch with the issue name, having the issue number and name while > submitting a

Re: [Pharo-dev] Pharo in a read-only environment survey

:) On Thu, Jun 15, 2017 at 3:32 PM, Jérémie Regnault < jeremie.regna...@outlook.com> wrote: > Hi, I'm working on Pharo deployment in a read-only environment, and I > want to know what behavior you want Pharo to adopt. If you could take > 5-10 minutes to fill my survey, it would be nice : >

Re: [Pharo-dev] Extra shortcut modifier opposite to #meta

But meta does also present problems in linux, doesn't it? I mean, meta in linux and windows means Ctrl. That means that overriding meta+arrows will break the Ctrl+arrows text navigation. What am I missing? I don't think that alternativeMeta means something useful. And I believe in this topic that

Re: [Pharo-dev] Pharo 7 and changes/sources files

On Fri, Jun 9, 2017 at 2:51 PM, Yuriy Tymchuk wrote: > Why cannot we have the sources in the image? > > When I asked it 2 years ago people were like: "oh, but you can just > download 1 sources file and use it by all the images". I don’t care about > that micro space

Re: [Pharo-dev] DiskStore question

tx Ben :) go Rajula go! On Wed, Jun 7, 2017 at 6:07 PM, Ben Coman wrote: > Just an aside (slightly off topic) for GSoC students and other newcomers > to understand the difference between: instance-variables, class-variables, > and class-instance-variables; > my post here

Re: [Pharo-dev] DebugSession: no exception raised when stepping out of the execution?

On Mon, May 29, 2017 at 6:07 PM, Eliot Miranda wrote: > Hi Thomas, > > > On May 29, 2017, at 7:41 AM, Ben Coman wrote: > > > > On Mon, May 29, 2017 at 9:34 PM, wrote: > > [...] > >> Here is my example code. Beware,

Re: [Pharo-dev] basicNew usage pattern

Hi Ben, Just to complete Sven's answer: #new will send #initialize to the new instance. Some frameworks may not want that to avoid extra initializations or side-effects. Think for example about any kind of serializer like Fuel or Glorp: the object they serialize/deserialize already have state,

Re: [Pharo-dev] Class syntax brainstorming

I'd also put in the pot a more declarative, less-smalltalkish-syntax approach: Class { name: 'A', superclass: Object, a: InstVar, b: InstVar, c: InstVar } Of course this could evolve. Some people will say that this is too verbose if you have lots of instance variables. I'd say that

Re: [Pharo-dev] Extending the debugger inspector with a new presentation

Yeah, in any case, it is not clear what we should do: - can't we extend the default debugger presentation? - or should we create a new presentation? - maybe we can do both, but then we have the question: is there a criteria to say "if X, extend the default presentation, if Y, create a new

[Pharo-dev] Pharo-Jenkins github user

Hi everybody, I wanted to create a github user to use for ci integration (pharo-ci), and while configuring it I saw there is already a Pharo-Jenkins user. https://github.com/Pharo-Jenkins Does somebody know who is the user? Guille -- Guille Polito Research Engineer French National

Re: [Pharo-dev] Commenting the Session Manager

2:17 AM, Ben Coman <b...@openinworld.com> wrote: > >> I'm sure I properly understand, you mean to change the behaviour rather >> than the comment? >> My naive understanding and intuition is the current behaviour is fine. >> What do you see wrong with it? >> >> ch

Re: [Pharo-dev] Commenting the Session Manager

ing..." > s3 := SessionManager default currentSession. > s1 == s2. "==> true" > s2 == s3. "==> false" > > So it seems a new session does not start when the image is saved. > With that in minds, can you review my proposed modifications... >

Re: [Pharo-dev] calling methods directly on traits

Traits are instances as classes are instances :) On Wed, Apr 26, 2017 at 3:22 PM, Peter Uhnak <i.uh...@gmail.com> wrote: > But trait is already instance, no? (instance of Trait class) > Or is that like an instance of an instance? > > On Wed, Apr 26, 2017 at 03:03:42PM +0200

Re: [Pharo-dev] calling methods directly on traits

Hi, No, it's the same as in classes. If methods are on the instance side, you cannot call them unless you instantiate the class. Guille On Wed, Apr 26, 2017 at 2:24 PM, Peter Uhnak wrote: > Hi, > > would it be possible to somehow call a method directly on a trait? > > e.g.

Re: [Pharo-dev] Security in the image

Generally speaking, and from my understanding, you will not be able to do: SomeClass compile: 'initialize MyEvilHack dostuff. ^ super initialize ' In newspeak. And that's because you are not able to do: SomeClass compile: '...' Newspeak uses object capabilities, and following those

Re: [Pharo-dev] Epicea should ask before recovering

Yeh, What they mean is that instead of loading the list of "possible stuff to recover" you launch at startup a dialog: "It seems your last Pharo session exited without saving some code. Do you want to recover it?" YES/NO :) On Tue, Apr 18, 2017 at 10:03 AM, Denis Kudriashov

Re: [Pharo-dev] ListModel Menu

Hi Jonathan, If you check users of MenuModel and ListModel in the image, you get a few results that could give you an idea of how to do it. For example: If you look for users of MenuModel you arrive to EpSelection>>filtersSubMenu, which will lead you to EpSelection>>populateMenu: aMenu. And this

Re: [Pharo-dev] [gsoc] Advances in Code Quality

re is. > > Cheers. > Uko > > On 1 Apr 2017, at 15:07, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > Yes! Actually offering fixes and transformations from renraku based on the > selected ast node could be really cool! > > On Fri, Mar

Re: [Pharo-dev] [gsoc] Advances in Code Quality

Yes! Actually offering fixes and transformations from renraku based on the selected ast node could be really cool! On Fri, Mar 31, 2017 at 7:21 PM, Stephane Ducasse wrote: > This is a super topic. > What would be good is to check the smart suggestions because they need

Re: [Pharo-dev] [Gsoc] [FastTable improvements] [Features request]

I understand that the data source we have right now is too low level. I'd prefer to call it "Cell data source" rather than view as it is more specific to the table, unless we want to reuse it in other scenarios Now, maybe part of GSOC could be to provide a higher-level provider able to nicely

[Pharo-dev] Serial Port not working on Mac

Hi all, We are here with Olivier taking a loot at how serial ports work, because he wants to use it to connect to arduino/raspberries. We saw that the serial port works nice in unix, in windows we had a look but we found some problems (and we do not have now a windows machine to test well), and

Re: [Pharo-dev] image not opening.

Yeh, to be more precise, * the problem is that the image somehow got it's display size modified to a very small one. * And that happenned while building an image in the CI in headless mode. * If the same image is built locally in a vm launched in non-headless mode, the issue cannot be reproduced.

Re: [Pharo-dev] New version of Pillar

:) thanks Stef and Maxime. On Wed, Mar 8, 2017 at 10:47 AM, Stephane Ducasse wrote: > Hi > > We are happy to announce a new version of Pillar for Pharo 50 and 60. > Thanks Maxime Roelandt for the help. > > Features > - Now we can rebuild the mooc slides (the

Re: [Pharo-dev] Pharo bootstrap with Ring and Calypso

Hi, yes this is cool :) There is also a new smart student that will work on this infrastructure a bit to make it "normal developer friendly", you know, hiding some implementation details, making maybe a UI for the process and so on. Now, about the questions: - And how much smaller could the

Re: [Pharo-dev] [Pharo-users] Fwd: GSoC 2017: Pharo Consortium has been accepted as a mentor organization!

Thanks :) On Mon, Feb 27, 2017 at 7:22 PM, Hilaire wrote: > Well done! > > Le 27/02/2017 à 18:07, Serge Stinckwich a écrit : > > Great news ! > > > > Thank you Jigyasa, Uko, Peter and Alex for your great work this year ! > > > > -- > Dr. Geo > http://drgeo.eu > > >

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

Thanks Martin :) On Thu, Feb 23, 2017 at 6:18 AM, Martin Dias <tinchod...@gmail.com> wrote: > > > On Wed, Feb 22, 2017 at 9:52 AM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> >> >> On Wed, Feb 22, 2017 at 12:57 AM, Martin Dias &

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

I trust your native english advice :) On Wed, Feb 22, 2017 at 2:11 PM, Ben Coman <b...@openinworld.com> wrote: > On Wed, Feb 22, 2017 at 8:52 PM, Guillermo Polito > <guillermopol...@gmail.com> wrote: > > > > > > On Wed, Feb 22, 2017 at 12:57 AM, Martin

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

On Wed, Feb 22, 2017 at 12:57 AM, Martin Dias wrote: > Hi all > > Phil: > I'm sorry, didn't get what you point with the code snippet. The copy of > the Symbol is the same instance, that I think it's nto GCed. > > Guille: > Yes, I knew the internals of the

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

Everything has a tradeoff. I do not understand the question. On Tue, Feb 21, 2017 at 1:19 PM, Denis Kudriashov <dionisi...@gmail.com> wrote: > > 2017-02-21 13:07 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>: > >> But in any case, whatever the alternativ

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

On Tue, Feb 21, 2017 at 10:37 AM, Denis Kudriashov <dionisi...@gmail.com> wrote: > Hi. > > 2017-02-21 9:44 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>: > >> Hi Dr. Dias, >> >> a WeakValueDictionary get's its values collected if th

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

Hi Dr. Dias, a WeakValueDictionary get's its values collected if they are not referenced strongly. However, the association remains there. This means that when you do: dictionary := WeakValueDictionary with: 'hello' -> nil copy. You'll have something like this: WeakValueDictionary {

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

On Mon, Feb 6, 2017 at 6:54 PM, Peter Uhnak wrote: > 1. Regarding WorkingSession > > The WS' comment claims "On each image startup the current session is > invalidated and a new session is created.", > but in reality WS is reset only save, and not on startup... isn't > that

Re: [Pharo-dev] Segmentation fault while installing Scale

Maybe it's something to do with his gentoo's version of some library? libc? It looks like it's some problem of Pharo in gentoo, not necessarily scale. On Sun, Feb 12, 2017 at 11:05 AM, Sven Van Caekenberghe wrote: > Note that he managed to run the System Report UI, which means his

Re: [Pharo-dev] Catalog loading in Spotter

As far as I remember, the main problem was not bandwidth but a blocking and non-responsive UI. Imagine I'm in the university, or in a company with a proxy. And I forget to set the proxy. Then, while spotter tries to fetch catalog entries, it would block the image and throw a timeout error some

Re: [Pharo-dev] FileTree

nderstand because you can load your project in a Pharo image and > save it as with FileTree. > > Envoyé de mon iPhone > > Le 18 févr. 2017 à 13:09, Guillermo Polito <guillermopol...@gmail.com> a > écrit : > > Hi Serge, > > Jonathan is trying to convert some ol

Re: [Pharo-dev] FileTree

Hi Serge, Jonathan is trying to convert some old code I have in here: https://github.com/guillep/PharoCandle to Filtree. The thing is that at that moment I started that, FileTree was not there, So I made my own format and my own parser based and PetitParser and the Smalltalk petit parser that

Re: [Pharo-dev] 2 seconds default time limit for tests

On Thu, Feb 16, 2017 at 2:31 PM, Denis Kudriashov <dionisi...@gmail.com> wrote: > > 2017-02-16 13:49 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>: > >> I vote for not introducing during code-freeze. >> > > I understand it but th

Re: [Pharo-dev] 2 seconds default time limit for tests

I vote for not introducing during code-freeze. We can discuss it for Pharo 7, I'm not against actually. But I have some concerns: - How does it work when we are debugging? I mean, imagine I'm running a test, a debugger is open, and I start working on it. How do these timeout currently work in

Re: [Pharo-dev] Code Completion in Pharo

Hi Lukas, This is cool and an interesting topic. Something that I would like is to see wether we can merge the auto-completion with the AST-based suggestion mechanism (right click on a piece of code -> suggestions), that provides suggestions for refactorings and code browsing. I mean, you can see

Re: [Pharo-dev] Book farm working again

Thanks! On Wed, Feb 8, 2017 at 6:05 PM, Stephane Ducasse wrote: > Hi > > https://ci.inria.fr/pharo-contribution/view/Books/ > I realised that jenkins dropped the connection to the github repositories > of the books and that they were not updated. > You can find my

Re: [Pharo-dev] Pharo 60 needs help because Removing-a-package-with-extensions-let-the-extensions-in-the-system-and-break-their-reload

I proposed a slice in the inbox for this. - added RPackage>>removeFromSystem - this version removes defined classes and also extension methods defined in the package. - make Nautilus ask the RPackage to remove itself (instead of doing it in the UI) I tested it with the fileout of a package

Re: [Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

I back up Pavel and Esteban here. On Tue, Feb 7, 2017 at 11:18 AM, Esteban Lorenzano wrote: > > On 7 Feb 2017, at 10:57, Pavel Krivanek wrote: > > The uperchase character is the symbol on the key. > > In OS X the uppercase characters are used: >

Re: [Pharo-dev] Segmentation fault while installing Scale

Hi, We are looking at it with Santi. I see in the log that you're using an ubuntu 12? I tried in a debian jessie and Santi in an ubuntu 14 and we could not reproduce it. Also the travis ci of scale uses ubuntu 12 and the installation works in there... Could you give more details about your

Re: [Pharo-dev] Pharo 6 release status

On Mon, Jan 30, 2017 at 5:49 PM, Pavel Krivanek wrote: > Hi all, > > as announced, for the Pharo 6 release we set milestone of almost all low > priority issues to "Later". If you feel that some of the postponed issues > you reported are important and needs to be fixed

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

Avatools only gives ~2k results :) On Mon, Jan 30, 2017 at 1:55 PM, Ben Coman wrote: > On Sun, Jan 29, 2017 at 10:14 PM, stepharong wrote: > > > > Hi guys > > > > Since we will push the remote tools (videos/web...) I would like to get > some ideas for

Re: [Pharo-dev] athens dead code?

In any case, this kind of "dead code that is better said an unused feature could be used and made explicit in the system by implementing a test on it, doesn't it? On Mon, Jan 30, 2017 at 7:42 AM, p...@highoctane.be wrote: > Why do not we have that concept of -contrib like

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

avatar, avatools? Le 29 janv. 2017 20:01, "Torsten Bergmann" a écrit : > Pharo "Revaluator" > > which is an artificial word: > - "Re" for Remote > - "eval" like evaluation of expressions for (remote) work/debugging > - "Revalution" means improvement, increase in value > > So far

Re: [Pharo-dev] CALL for GSoC project proposals

We just add project proposals there? On Wed, Jan 25, 2017 at 11:19 AM, Stephane Ducasse wrote: > But I understand the process. > So I did a pass > > On Wed, Jan 25, 2017 at 11:05 AM, Stephane Ducasse < > stepharo.s...@gmail.com> wrote: > >> Hi yuriy >> >> you could have

Re: [Pharo-dev] [bloc] addressing the moz2d issue

Hi Doru, First, I understand the effort you all made to make this big piece of work. I have however some questions that probably you can help with: 1) I understand Sparta is a library completely independent from Athens. But I also understand that they follow the same reasoning and general design

Re: [Pharo-dev] Collections and Kernel

Hi, First, I'll make a not that is implicit in the conversation: the loading/deployment granularity in Pharo is the package, not the class. And as such, a dependency to a class will require the entire package, because we cannot load half a package. Okok, "yes, we can", but this is not the default

Re: [Pharo-dev] Google summer of code

Hi, I would like to help in cleaning, composing and enhancing the ideas page. I already see some old projects whose mentors either left the community or may not be 100% available for mentoring (like Camille Teruel). We should clean that page. Besides, I'm interested in knowing the official

Re: [Pharo-dev] [Pharo-users] Pharo by Example 50 released!

Yeh, thanks to all who made an effort :) On Sun, Jan 22, 2017 at 5:10 PM, Sven Van Caekenberghe wrote: > Great work, can't wait for the HTML version (to link to when answering > questions). > > Thank you ! > > > On 22 Jan 2017, at 16:53, stepharong wrote: > >

Re: [Pharo-dev] Esteban's ChangeLog week of 16 January 2017

I like the "talk to yourself" format :P On Mon, Jan 23, 2017 at 10:05 AM, Esteban Lorenzano wrote: > > On 23 Jan 2017, at 10:02, Stephane Ducasse > wrote: > > Tx a lot esteban! > This is so great. > > > thanks :) > > Showing what you are doing is

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

No problem ;) BTW, you can find latest `already package` snaps in bintray here: https://bintray.com/pharo-project/pharo/PharoVM-Snap (Also the readme is updated) Guille On Wed, Jan 18, 2017 at 10:28 AM, Alistair Grant <akgrant0...@gmail.com> wrote: > On 17 January 2017 at 00:40,

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

That looks cool, I put it in my todo :) On Tue, Jan 17, 2017 at 3:23 AM, Ben Coman <b...@openinworld.com> wrote: > > > On Mon, Jan 16, 2017 at 11:23 PM, Peter Uhnak <i.uh...@gmail.com> wrote: > > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: &

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

On Mon, Jan 16, 2017 at 4:23 PM, Peter Uhnak <i.uh...@gmail.com> wrote: > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: > > Hi all, > > > > First, Peter. Actually, this package is meant for those people using > > Snapcraft to install packages

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

> > > > I haven't built the VM before, so it will take me a while to track > > this down. If this is a common problem with an easy solution I'd like > > to know :-) > > > > P.S. In the readme under Installing snapcraft, build-essential doesn't > > have an "s", and

[Pharo-dev] [ANN] Snapcraft for Pharo

Hi all, Just wanted to share this: https://github.com/guillep/pharo-snapcraft It is basically the code to generate a snap package of the pharo-vm using snapcraft. Using this, the VM is generated and packaged with all dependencies. This should help in running pharo in different linux

Re: [Pharo-dev] Can anyone explain #asInteger for Strings?

Ugly. And old, really old. I remember at one point in time there was a "squeezeNumberOutOfString" or something like that. Now, I'd like to fix this, because it just introduces noise and probably a lot of strange code. But the problem is not fixing it on itself, but checking all possible users

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

I have some time, I'll check it out this afternoon On Fri, Jan 6, 2017 at 3:01 PM, Ben Coman wrote: > Looks like interesting tech. I can't help for now since I'm out of > town tomorrow on two week family vacation. > (but TGF for smartphone gmail) > > cheers -ben > > On

Re: [Pharo-dev] Deprecations on Smalltalk Image in Pharo 5

On Tue, Jan 3, 2017 at 8:56 PM, Eliot Miranda wrote: > > > On Tue, Jan 3, 2017 at 2:24 AM, Henrik Johansen < > henrik.s.johan...@veloxit.no> wrote: > >> It was my impression there was a procedure in place earlier for moving >> methods from SmalltalkImage to classes with

Re: [Pharo-dev] Redline: Talking Runtime basics ...

Hi Phil, On Sat, Dec 31, 2016 at 10:14 AM, philippe.b...@highoctane.be < philippe.b...@gmail.com> wrote: > Isn't there a typo in the first exptession? > > Also the list contains a lot of RB things. What purpose do they have in a > bootstrap image? > Yes, that is because the bootstrap image

[Pharo-dev] Let's talk with Dr Metacello: Moving Pharo to Github

Hi all, We arranged with Dale a public discussion on discord *this wednesday at 8am PDT (15h Paris)*. The idea is to discuss about the alternatives to store the Pharo sources in Git. Dale is already working on git since a couple of years, - he made has already experimented on a project using

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

On Fri, Oct 28, 2016 at 8:36 PM, Denis Kudriashov <dionisi...@gmail.com> wrote: > > 2016-10-28 18:58 GMT+02:00 Guillermo Polito <guillermopol...@gmail.com>: > >> No, please, kernel test should have the fewer dependencies as possible! >> > I would say this dep

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

No, please, kernel test should have the fewer dependencies as possible! And again i'll hold my position: whoever wants to load it can do it. There is no need to put it there by default. Le 28 oct. 2016 18:52, "Denis Kudriashov" a écrit : > We always said that smalltalk is

Re: [Pharo-dev] GitHub code analytics tools

I would like to have a good code review tool, before having to do one ad-hoc... On Thu, Oct 27, 2016 at 1:50 PM, Denis Kudriashov wrote: > Hi. > > With future transition to github I ask myself what tools we will have out > of the box. > I google a bit and found these nice

Re: [Pharo-dev] [ANN] Scale

Hi all, and thanks Santi for rescuing Scale from the Limbo :). I saw already some discussions pointing to this thread indirectly. I want to answer some philosophical aspects, just to remove some burden from Santi who is the real one that should take credit for pushing this to the light ^^. 1)

Re: [Pharo-dev] SUnit improvements need review and feedback

I mean crash. Somehow my image's processes were killed and I only had the UI process: no delay process, no finalization, no idle process. Then, when the VM tries to suspend the current process and change to a second one, it finds none and it just quits. So it's not a VM problem I think but

<    1   2   3   4   5   6   7   8   >