Re: [Pharo-dev] OS-Windows and UnifiedFFI

Example in chapter please :) Le 24/6/16 à 14:05, Esteban Lorenzano a écrit : On 24 Jun 2016, at 09:53, Nicolai Hess > wrote: I’m sorry… I do not understand. This is solved in UFFI since some months, and Torsten’s OSWindow uses it. Sorry then it is my

Re: [Pharo-dev] Having comments for pragma?

+1. I can't stress enough how useful it is to make pragmas real selectors with implementations and to try and apply them using perform:withArguments:. That's when their real power comes in. For example, if you have some method that wants to be added to some tool, make its pragma a message

Re: [Pharo-dev] Having comments for pragma?

Ben Coman wrote > On Fri, Jun 24, 2016 at 10:55 PM, Clément Bera < > bera.clement@ > > > wrote: > >> Hi. >> >> Pragmas are selectors hence they're browsable. You can implement a method >> somewhere with the pragma selector name that includes the documentation. >> In >> VW they were careful about

Re: [Pharo-dev] Reordering working directory mess

On 24/06/16 18:14, Nicolas Passerini wrote: I don't see why it couldn't be the default behavior. I think that it would be a reasonable default, don't you? Not with our current Monticello/Metacello, it won't. You'll never be able to resolve configuration problems. Stephan

Re: [Pharo-dev] OS-Windows and UnifiedFFI

Yes! That is much better, thanks 2016-06-24 17:16 GMT+02:00 Esteban Lorenzano : > > On 24 Jun 2016, at 16:43, Nicolai Hess wrote: > > > > 2016-06-24 16:03 GMT+02:00 Esteban Lorenzano : > >> if you send me the code, I can take a look. >> > > Sorry if this sounds rude, but > did you actually read

Re: [Pharo-dev] Reordering working directory mess

Can't this be accomplished today with a symbolic link to a package directory somewhere on your HD? e.g. rm -rf package-cache ln -s /path/to/my/common/package/repo package-cache Works for me at least. Nicolas Passerini wrote > I agree with Javier, it would be much nicer to have only one

Re: [Pharo-dev] Reordering working directory mess

> On 24 Jun 2016, at 18:14, Nicolas Passerini wrote: > > I agree with Javier, it would be much nicer to have only one shared package > cache and, while I understand that there might be people not wanting that, I > don't see why it couldn't be the default behavior. I think that it would be a >

Re: [Pharo-dev] Having comments for pragma?

On Fri, Jun 24, 2016 at 10:55 PM, Clément Bera wrote: > Hi. > > Pragmas are selectors hence they're browsable. You can implement a method > somewhere with the pragma selector name that includes the documentation. In > VW they were careful about that and most, if not all, of their pragmas are > ca

Re: [Pharo-dev] Having comments for pragma?

> On Jun 24, 2016, at 7:55 AM, Clément Bera wrote: > > Hi. > > Pragmas are selectors hence they're browsable. You can implement a method > somewhere with the pragma selector name that includes the documentation. In > VW they were careful about that and most, if not all, of their pragmas are

Re: [Pharo-dev] Reordering working directory mess

I agree with Javier, it would be much nicer to have only one shared package cache and, while I understand that there might be people not wanting that, I don't see why it couldn't be the default behavior. I think that it would be a reasonable default, don't you? On Fri, Jun 24, 2016 at 3:54 PM, Jav

[Pharo-dev] debuggerCompleteToSender (was Re: Having comments for pragma?)

On Fri, Jun 24, 2016 at 9:54 PM, Alexandre Bergel wrote: > Hi! > > A pragma may be very obscure. For example, I do: > Pragma allInstances anyOne > => > > If I want to know more about this is actually > quite challenging. > I see many methods having that pragma, but not idea what it is for. > I

Re: [Pharo-dev] OS-Windows and UnifiedFFI

> On 24 Jun 2016, at 16:43, Nicolai Hess wrote: > > > > 2016-06-24 16:03 GMT+02:00 Esteban Lorenzano >: > if you send me the code, I can take a look. > > Sorry if this sounds rude, but > did you actually read my mail, I mean the first one. well… after search, it

Re: [Pharo-dev] Having comments for pragma?

Hi. Pragmas are selectors hence they're browsable. You can implement a method somewhere with the pragma selector name that includes the documentation. In VW they were careful about that and most, if not all, of their pragmas are carefully commented this way. For example, if you have the pragma a

Re: [Pharo-dev] OS-Windows and UnifiedFFI

2016-06-24 16:03 GMT+02:00 Esteban Lorenzano : > if you send me the code, I can take a look. > > Sorry if this sounds rude, but did you actually read my mail, I mean the first one. If you don't have the time to look at this, it is ok. I will just try to find it out myself, or maybe torsten has an

Re: [Pharo-dev] Impossible to delete a class

> On 24 Jun 2016, at 16:18, Valentin Ryckewaert > wrote: > > Hello everyone, > > I just downloaded the last Pharo version and I found a bug when I tried to > delete a class. > The last version deprecated a method "name" and it looks like > SmalltalkImage>>errorReportOn: doesn't like this. Wh

[Pharo-dev] Impossible to delete a class

Hello everyone, I just downloaded the last Pharo version and I found a bug when I tried to delete a class. The last version deprecated a method "name" and it looks like SmalltalkImage>>errorReportOn: doesn't like this. When you try to delete a class there is an infinite loop everytime. Valentin

Re: [Pharo-dev] OS-Windows and UnifiedFFI

if you send me the code, I can take a look. > On 24 Jun 2016, at 15:06, Nicolai Hess wrote: > > > > 2016-06-24 14:52 GMT+02:00 Esteban Lorenzano >: > >> On 24 Jun 2016, at 14:40, Nicolai Hess > > wrote: >> >> >> >> 2016-06-24 14:32

Re: [Pharo-dev] Reordering working directory mess

This is optional (some people want it, others not) System settings > Monticello > Local cache directory MCCacheDirectory class>>#cacheDirectory: > On 24 Jun 2016, at 15:54, Javier Pimás wrote: > > I don't know for the new directories, but I always thought that it would be > nice to have packa

Re: [Pharo-dev] Reordering working directory mess

This is already possible to have a shared directory for all the *.mcz of your images. On 6/24/16, Javier Pimás wrote: > I don't know for the new directories, but I always thought that it would be > nice to have package-cache in ~/.pharo or a place shared by all images, to > avoid redownloading a

Re: [Pharo-dev] catalog will be down 1hr

When informations in the catalog are updated ? I made some modifications yesterday and apparently they didn't appear, but maybe I just have to wait more :-) On 6/21/16, Esteban Lorenzano wrote: > Hi, > > I will apply some updates to catalog (backend, they will not be visible) > > cheers, > Esteba

[Pharo-dev] Having comments for pragma?

Hi! A pragma may be very obscure. For example, I do: Pragma allInstances anyOne => If I want to know more about this is actually quite challenging. I see many methods having that pragma, but not idea what it is for. I see that Halt>>signalerContext and Process>>complete: that use that pragm

Re: [Pharo-dev] Reordering working directory mess

I don't know for the new directories, but I always thought that it would be nice to have package-cache in ~/.pharo or a place shared by all images, to avoid redownloading all .MCZs from other projects each time you launch pharo from a different directory. Cheers! Pocho On Thu, Jun 23, 2016 at 12:

[Pharo-dev] [pharo-project/pharo-core] b637cf: 60112

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b637cf9547873482910a1cf6159b60d220b6e0c9 https://github.com/pharo-project/pharo-core/commit/b637cf9547873482910a1cf6159b60d220b6e0c9 Author: Jenkins Build Server Date: 2016-06-24 (Fri, 24 Jun 2016

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] Reordering working directory mess

> On 24 Jun 2016, at 14:36, Esteban Lorenzano wrote: > > so, pharo-local will be. > but regular convention is to store this kind of data into a hidden directory > (hence it would be .pharo-local, maybe)… but I understand the opposition I > will let it visible and we can re-check later. My he

Re: [Pharo-dev] OS-Windows and UnifiedFFI

2016-06-24 14:52 GMT+02:00 Esteban Lorenzano : > > On 24 Jun 2016, at 14:40, Nicolai Hess wrote: > > > > 2016-06-24 14:32 GMT+02:00 Esteban Lorenzano : > >> … and I enhanced the example to not induce to confusion anymore :) >> >> Esteban >> > > Sorry, I must be stupid, it still does not work ( an

Re: [Pharo-dev] OS-Windows and UnifiedFFI

ah, and which VM are you using? > On 24 Jun 2016, at 14:40, Nicolai Hess wrote: > > > > 2016-06-24 14:32 GMT+02:00 Esteban Lorenzano >: > … and I enhanced the example to not induce to confusion anymore :) > > Esteban > > Sorry, I must be stupid, it still does not

Re: [Pharo-dev] OS-Windows and UnifiedFFI

> On 24 Jun 2016, at 14:40, Nicolai Hess wrote: > > > > 2016-06-24 14:32 GMT+02:00 Esteban Lorenzano >: > … and I enhanced the example to not induce to confusion anymore :) > > Esteban > > Sorry, I must be stupid, it still does not work ( and it actually looks th

Re: [Pharo-dev] OS-Windows and UnifiedFFI

2016-06-24 14:32 GMT+02:00 Esteban Lorenzano : > … and I enhanced the example to not induce to confusion anymore :) > > Esteban > Sorry, I must be stupid, it still does not work ( and it actually looks the same as with the existing WinHandle type). > > On 24 Jun 2016, at 14:27, Nicolai Hess w

Re: [Pharo-dev] Reordering working directory mess

so, pharo-local will be. but regular convention is to store this kind of data into a hidden directory (hence it would be .pharo-local, maybe)… but I understand the opposition I will let it visible and we can re-check later. now, tool makers, please take into account the new FileLocator localD

Re: [Pharo-dev] OS-Windows and UnifiedFFI

… and I enhanced the example to not induce to confusion anymore :) Esteban > On 24 Jun 2016, at 14:27, Nicolai Hess wrote: > > > > 2016-06-24 14:05 GMT+02:00 Esteban Lorenzano >: > >> On 24 Jun 2016, at 09:53, Nicolai Hess > > wrote:

Re: [Pharo-dev] OS-Windows and UnifiedFFI

2016-06-24 14:05 GMT+02:00 Esteban Lorenzano : > > On 24 Jun 2016, at 09:53, Nicolai Hess wrote: > > > > I’m sorry… I do not understand. This is solved in UFFI since some months, >> and Torsten’s OSWindow uses it. >> > > Sorry then it is my fault. I know that Torsten already ported OSWindow to >

[Pharo-dev] [pharo-project/pharo-core] b67123: 60111

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b67123481cfacd8b11c33802fdacc9fc7d182137 https://github.com/pharo-project/pharo-core/commit/b67123481cfacd8b11c33802fdacc9fc7d182137 Author: Jenkins Build Server Date: 2016-06-24 (Fri, 24 Jun 2016

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] OS-Windows and UnifiedFFI

On 24 Jun 2016, at 09:53, Nicolai Hess wrote:I’m sorry… I do not understand. This is solved in UFFI since some months, and Torsten’s OSWindow uses it. Sorry then it is my fault. I know that Torsten already ported OSWindow to UFFI, and that most things are already working. UF

Re: [Pharo-dev] Reordering working directory mess

Hi, > On Jun 23, 2016, at 10:18 PM, stepharo wrote: > > What is the difference between play-cache play-stash - play-cache is populated automatically when you work in the playground. - play-stash stores only the pages that you gave concrete names to. You can double click on the tab with the nam

[Pharo-dev] [pharo-project/pharo-core] d93829: 60110

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d938291183988224940621c636ddf2f55c792165 https://github.com/pharo-project/pharo-core/commit/d938291183988224940621c636ddf2f55c792165 Author: Jenkins Build Server Date: 2016-06-24 (Fri, 24 Jun 2016

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] Reordering working directory mess

play-cache contains history from default playground. play-stash contains state of playground pages (if you rename "playground” tab into something else it becomes a custom page. You can look it up with spotter) Uko > On 23 Jun 2016, at 22:18, stepharo wrote: > > What is the difference between p

Re: [Pharo-dev] OS-Windows and UnifiedFFI

I’m sorry… I do not understand. This is solved in UFFI since some months, > and Torsten’s OSWindow uses it. > Sorry then it is my fault. I know that Torsten already ported OSWindow to UFFI, and that most things are already working. UFFI provides FFIConstantHandle type to deal with windows HANDLE

Re: [Pharo-dev] OS-Windows and UnifiedFFI

> On 24 Jun 2016, at 09:26, Nicolai Hess wrote: > > > > 2016-05-30 14:59 GMT+02:00 Nicolai Hess >: > > > 2016-05-19 8:56 GMT+02:00 Nicolai Hess >: > > > 2016-04-25 10:17 GMT+02:00 Nicolai Hess >: >

Re: [Pharo-dev] OS-Windows and UnifiedFFI

2016-05-30 14:59 GMT+02:00 Nicolai Hess : > > > 2016-05-19 8:56 GMT+02:00 Nicolai Hess : > >> >> >> 2016-04-25 10:17 GMT+02:00 Nicolai Hess : >> >>> >>> >>> 2016-04-25 9:28 GMT+02:00 Esteban Lorenzano : >>> Hi Nicolai, On 25 Apr 2016, at 09:14, Nicolai Hess wrote: >>