[Pharo-dev] Re: [ANN] Pharo 12 Release !

Congrats!!! Have a good release party :)) пт, 26 апр. 2024 г. в 11:20, Esteban Lorenzano via Pharo-dev < pharo-dev@lists.pharo.org>: > Dear Pharo users and dynamic language lovers: > > We have released Pharo version 12! > What is Pharo? > > Pharo is a pure object-oriented

[Pharo-dev] What did happen with CustomHelp?

Hi. There is no CustomHelp in Pharo 11 anymore. And no Help Browser in the menu. What is the story behind it? Is there any new alternative? Now any external {Project}-Help package is not loadable into the new system. Regards, Denis

[Pharo-dev] Re: [Compiler] Variables in DoIts

Hi. сб, 25 июн. 2022 г. в 13:48, Guillermo Polito : > I’d suggest, for further improvement (but not blocking), that I’d like to > see the entire code and context of the do-it context. > Just showing the selected text makes one lose context. > Instead, it would be super cool to show the entire

[Pharo-dev] Re: [Compiler] Variables in DoIts

Now we can play with other interesting options. We can completely remove reformatting of code for DoIts and make the debugging more "transparent" for users: [image: simpleDoIt.png] Notice there is no DoIt header anymore . What is selected for the DebugIt command is what the user really sees in

[Pharo-dev] Re: [ANN] Pharo 9 released!

, Carlo Teixeira, Carlos > Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, > Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel > Aparicio, David Bajger, David Sánchez i Gregori, Denis Kudriashov, Ellis > Harris, Eric Brandwein, Eric Gade, Er

Re: [Pharo-dev] Tools with Proxy support

Hi Esteban. Try look into Ghost framework: https://github.com/pharo-ide/Ghost. I carefully put GT support methods into a separate package Ghost-GTSupport . It also includes a tool to collect all messages from given scenario (like opening inspector) which could help you: student := GHStudent

[Pharo-dev] What to do with our failing CI?

Hello. We have a failing CI for quite a long time (maybe few months). And out of that there are always new flaky tests failing our PRs time to time. We did fix some of them but I do not think it is possible to avoid them at all. I propose a simple approach/convention to quickly recover CI from

Re: [Pharo-dev] Discoverability

Hi Sean. пт, 5 июн. 2020 г. в 21:16, Sean P. DeNigris : > BTW am I alone in thinking that the class list should be treated as a tree > by default? It basically is a tree *already*, but without the ability to > collapse/expand which limits understanding a large tree where siblings may > be far

Re: [Pharo-dev] Discoverability

Hi Sean. пт, 5 июн. 2020 г. в 16:15, Sean P. DeNigris : > I had a "simple" goal: to change Calypso's class pane to a tree. After an > hour or two, I didn't feel any closer! > I implemented it in very early stages. But I did have time to implement it in a better way. The old code is still there.

Re: [Pharo-dev] Processor>>activeProcess is wrong when a process is stepped by a forked process

Hi Thomas. I think the problem is with concurrent code in your test. I do not see what wrong is going on but test passes when full stepping loop is extracted into single process: s := Semaphore new. done := false. "Create debugged process" debuggedProcess := [p := Processor

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo 8.0 Released!

Teixeira, Guille Polito, Torsten Bergman, Damien Pollet, > Holger Hans Peter Freyther, Julio Ripoll, Carolina Hernandez Phillips, > Julien Delplanque, Hugo Lasnier, James Foster, Will Hensel, Erik Stel, Sven > Van Caekenberghe, Martín Dias, Tomohiro Oda, Konrad Hinsen, Sébastien > Ro

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

PR is here https://github.com/pharo-project/pharo/pull/5470 чт, 19 дек. 2019 г. в 21:51, Denis Kudriashov : > чт, 19 дек. 2019 г. в 21:43, Denis Kudriashov : > >> I checked Squeak. All my examples work consistently there: UnhandledError >> handler is always triggered. >&g

Re: [Pharo-dev] [Mm10s] 2020-01-06

вт, 7 янв. 2020 г. в 20:34, ducasse : > Hello Denis > > > > What is Fluid class parser? > > > This is the name of the class definition we sketched and presented at > Maribor. > The idea is how to fight the combinatory explosion of parameters (tags, > ephemerons, traits, slots, ….) > For now I’m

Re: [Pharo-dev] [Mm10s] 2020-01-06

Hi Sven. It was an example of definition format which new parser targets. вт, 7 янв. 2020 г. в 22:20, Sven Van Caekenberghe : > It sounds wrong to call this a parser, it is a builder, no ? > > It is plain Pharo syntax that builds a representation, IIUC. > > > On 7 Jan 2020, at 21:32, ducasse

Re: [Pharo-dev] [Mm10s] 2020-01-06

Hi Stef. What is Fluid class parser? Is it the name of currently integrated parser? вт, 7 янв. 2020 г. в 19:48, ducasse : > Thanks Pablo > > > Last Week > - Working on concurrent programming booklet > - Enlumineur > - Better iceberg explanation with Pablo > - Fluid class parser > > This week >

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

чт, 19 дек. 2019 г. в 21:43, Denis Kudriashov : > I checked Squeak. All my examples work consistently there: UnhandledError > handler is always triggered. > Even more: signalling new error from the handler block passes it from the > original signallerContext: > > [ >> &g

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

I checked Squeak. All my examples work consistently there: UnhandledError handler is always triggered. Even more: signalling new error from the handler block passes it from the original signallerContext: [ > > [ 1/0 ] on: MyTestError do: [ :e | self halt ] > > ] on: ZeroDivide do: [ :z |

[Pharo-dev] Why UnhandledError is not the only way to open debugger?

Or in other words why Halt and Warning open debugger directly instead of using UnhandledError signalling? In Squeak it's all going though UnhandledError.

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

questions on current exceptions design. чт, 19 дек. 2019 г. в 18:39, Denis Kudriashov : > The solution to problem is to resignal UnhandledError instead of simple > signalling. Resignal uses original signalContext as a starting point for > handlers lookup: > > UnhandledError>&

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

uot;bad" environment. Execute in browser editor "self halt. self methodWithError". And in debugger just Step Through #methodWithError. It will hangs. Proposed change fixes that. I will prepare PR with tests. But it would be nice to find other broken places which will be fixed чт,

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

Hi Alistair чт, 19 дек. 2019 г. в 07:19, Alistair Grant : > On Wed, 18 Dec 2019 at 21:45, Denis Kudriashov > wrote: > > > > Following script demonstrates the difference in the error processing > logic when there is an outer handler: > > > > [ > > > >

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

чт, 19 дек. 2019 г. в 00:42, Denis Kudriashov : > I think this problem could lead to debugger issues with stepOver and > stepThrough. For example: > > Context>>#stepToHome: > ... > context := aContext insertSender: (Context > context

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

Hi Alistair. чт, 19 дек. 2019 г. в 07:10, Alistair Grant : > I think the difference here is that in the playground 'self' is nil, > while in the browser 'self' is the class being inspected. > UndefinedObject>>handleSignal: tells the exception to execute its > #defaultAction, which is to signal

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

introduced in Pharo 6): WorldMorph>>becomeActiveDuring: aBlock ... aBlock on: Error do: [ :ex | ... ex pass ] Any UI event is processed under this method. ср, 18 дек. 2019 г. в 22:31, Denis Kudriashov : > Users of UnhandledError definitely shows that it is a critical bug. > >

Re: [Pharo-dev] Interesting bug or feature in exception processing logic

if you will try to wrap #announce: into handler block the deliver will be interrupted by first error: [ann announce: ValueChanged new] on: ZeroDivide do: [ :err | err logCr. err pass ]. It will open single debugger at first handler error. ср, 18 дек. 2019 г. в 20:44, Denis Kudriashov : > Hi.

[Pharo-dev] Interesting bug or feature in exception processing logic

Hi. I played a bit with exceptions trying to detect that given block will open the debugger. My idea was to simply catch UnhandledError which normally means that no outer code handles given error and therefore debugger is appeared. For my surprise the following example works from playground but

Re: [Pharo-dev] TraitedMetaclass / Behaviour bug?

Hi Guille. ср, 18 сент. 2019 г. в 14:22, Guillermo Polito : > Tools should work against #localMethods and #origin, which hide how the > actual implementation stores the things :). > I am a bit confused by this sentence. My original design of scopes was purely based on #localMethods and #origin

Re: [Pharo-dev] Slot definition API?

Hi. Another option is to not expose slot class names at all and use messages instead: - #first slot lazy default: 5 - #second slot boolean - #instVar3 slot weak lazy - #typedVar slot type: Integer; lazy #slot here will return SlotDefinition. And following messages will configure it or produce

Re: [Pharo-dev] Class definition with slot template is broken

Hi пт, 23 авг. 2019 г., 11:06 Marcus Denker : > > > > On 23 Aug 2019, at 11:49, Cyril Ferlicot > wrote: > > > > Hi, > > > > Since yesterday I get a lot of bugs when I try to edit class > > definitions while having the slot template in class definition > > enabled. (See comment: > >

Re: [Pharo-dev] Calypso idea - inherited tests

Hi guys. Would be nice to see the error stack. Which variable is nil in that case? I really do not see such errors. Is it pharo 7 or 8? чт, 30 мая 2019 г., 11:17 ducasse : > > > On 29 May 2019, at 23:58, Ben Coman wrote: > > > > On Thu, 30 May 2019 at 06:26, Deni

Re: [Pharo-dev] Calypso idea - inherited tests

чт, 30 мая 2019 г. в 04:59, Ben Coman : > > > On Thu, 30 May 2019 at 06:26, Denis Kudriashov > wrote: > >> Hi Ben. >> >> There are already two features that support inherited tests: >> - run all tests using class icon: there will be extra red method group &

Re: [Pharo-dev] Calypso idea - inherited tests

Hi Ben. There are already two features that support inherited tests: - run all tests using class icon: there will be extra red method group "broken tests" which will show failed inherited tests. - toggle inheritance visibility with checkbox in third panel: you will see inherited tests and

Re: [Pharo-dev] [ANN] Pharo 7.0.3

Hi Tim. сб, 13 апр. 2019 г. в 13:51, Tim Mackinnon : > This is great - I’m pleased we can get fixes like this (and keen to get > passed that font issue which was driving me crazy). > > A small related question - how do ensure we get fixes from sub projects > considered too? I’d really like to

Re: [Pharo-dev] how implement isAbstract?

We can also look into it from the other side. All these methods are definitely a kind of code duplication. I think what we need here is an explicit property for classes. It could be even part of class definition. BTW do we plan new class definition in Pharo 8? сб, 30 мар. 2019 г. в 18:35, Denis

Re: [Pharo-dev] how implement isAbstract?

ethod first. > > I don't like how I have to hack around the method lookup but this works > far better from me than the class equality / identity check. > > On 30 Mar 2019, at 19:35, Denis Kudriashov wrote: > > Hello. > > We did recently several cleanups by marking abstr

[Pharo-dev] how implement isAbstract?

Hello. We did recently several cleanups by marking abstract classes as abstract using #isAbstract method (https://github.com/pharo-project/pharo/pull/3087, https://github.com/pharo-ide/Calypso/pull/462) . I would like to discuss here and decide what the right way to implement this method. The

Re: [Pharo-dev] [Ann] TelePharo and PharoThings adopted for Pharo 7

Hi Norbert. вс, 17 февр. 2019 г. в 20:41, Norbert Hartl : > > > > Am 17.02.2019 um 21:03 schrieb Denis Kudriashov : > > > > Hi. > > > > I released new versions of TelePharo (v0.3.0) and PharoThings (v0.2.3) > adopted for Pharo 7 changes. > > > &g

[Pharo-dev] [Ann] TelePharo and PharoThings adopted for Pharo 7

Hi. I released new versions of TelePharo (v0.3.0) and PharoThings (v0.2.3) adopted for Pharo 7 changes. PharoThings also includes new features from Alex Oliveira: - Raspberry model B3 - water alarm example And few models of Arduino from @gaterfy. Best regards, Denis

Re: [Pharo-dev] shortcut to browser ref to a class

Hi Stef. cmd+n does not work for you? вт, 5 февр. 2019 г., 19:21 ducasse steph...@netcourrier.com: > Hi > > Is it me or we lost cmd + shift B to browse refs to class in Calypso? > > Stef > > > >

Re: [Pharo-dev] Bad baseline practices

Hi Stephan. There was discussion about it. And idea is to have reproducible builds for Pharo. With floating versions we can't achieve it (at least with current tools). In addition I maintain floating branches for those projects (v0.15.x). So for your own projects you can reference them instead

Re: [Pharo-dev] Availability of Smallapack in Pharo6.0

Hi Nicolas пт, 11 янв. 2019 г. в 23:34, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > Hi, > I announce the availability of Smallapack in Pharo6. > > The ConfigurationOfSmallapack is in > http://www.squeaksource.com/MetacelloRepository and there is a copy in > meta repo for Pharo

Re: [Pharo-dev] DebugSession>>activePC:

Hi guys. Funny thing that DebugSession does not exists in Squeak. It was introduced in Pharo to represent the model for debugger. пт, 11 янв. 2019 г. в 22:34, Thomas Dupriez via Pharo-dev < pharo-dev@lists.pharo.org>: > Yeah, it's a bit unfortunate you assumed I wanted to remove the method. >

Re: [Pharo-dev] [Pharo 7.0] Build #88: 22827-Update-Calypso-Version

And now we have Breakpoints browser in image (from Debugging menu) сб, 29 дек. 2018 г. в 14:22, : > There is a new Pharo build available! > > The status of the build #88 was: FAILURE. > > The Pull Request #2115 was integrated: "22827-Update-Calypso-Version" > Pull request url:

Re: [Pharo-dev] Pharo 7 changelog proposal

Remove trait related items from calypso вс, 23 дек. 2018 г., 11:29 Pavel Krivanek pavel.kriva...@gmail.com: > Hi, > > I'm trying to summarize the changelog for Pharo 7 (based on about 2500 > merged PRs, not counting standalone commits to Iceberg and Calypso). If > something more should be

Re: [Pharo-dev] Huge Critiques Area in Calypso in Pharo 7

Hi Petr. Setting would be nice. I did not know about it in Nautilus вт, 18 дек. 2018 г. в 14:44, Petr Fischer via Pharo-dev < pharo-dev@lists.pharo.org>: > I have that feeling too - critiques pane is annoying + occupying too much > place - what about showing critiques inline only (in the line

Re: [Pharo-dev] Huge Critiques Area in Calypso in Pharo 7

nis, for the swift reply. > What is the solution, though ? > What do you think should happen ? > Make the constant smaller, like the height of 1 row ? > > > On 17 Dec 2018, at 18:42, Denis Kudriashov wrote: > > > > Hi Sven. > > > > I checked problem and

Re: [Pharo-dev] Huge Critiques Area in Calypso in Pharo 7

Hi Sven. I checked problem and found following method: FTTableMorph >> minHeight ^ 100 It prevents full critiques widget to be small. There is probably a bug in morphic which does not set up this "correct" extent by default. In my case when I browse your method in fresh image only three rows

Re: [Pharo-dev] Calypso equivalent

Hi Ben. All Calypso commands are implemented with Commander. Look for example at remove package command. The menu item is declared by SycRemovePackageCommand class>>#fullBrowserMenuActivation. Doc for Commander https://github.com/SquareBracketAssociates/Booklet-Infrastructure (with link to pdf).

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

ly file references are exposed to users. User chooses a file and Pharo gives him a reference to this file. > > On Sat, Oct 27, 2018 at 2:42 PM Denis Kudriashov > wrote: > >> What about different names? >> >> UIManager default >> chooseFileIn: aFileReference

Re: [Pharo-dev] ClyMethodGroup>>#fileOut dead code ?

Hi Sven. It is not dead. It is here to file out any method group including normal protocols. It was copied from SystemOrganizer>>fileOutCategory:. Now it needs to be fixed in Pharo 7 and it would be nice to have it in better form ср, 31 окт. 2018 г. в 15:39, Sven Van Caekenberghe : > Hi, > >

Re: [Pharo-dev] Streams and FileDialog in Pharo 6 and 7

What about different names? UIManager default chooseFileIn: aFileReference withExtensions: #() title: 'title' UIManager default chooseFileForSaveIn: aFileReference withExtensions: #() title: 'title' We can just expect file references because it is what is exposed

Re: [Pharo-dev] What you think about visibility of trait method in browser?

Hi Guille. чт, 11 окт. 2018 г. в 9:24, Guillermo Polito : > Hi, > > >> On Wed, Oct 10, 2018, 19:40 Denis Kudriashov >> wrote: >> >>> Hello. >>> >>> I want to ask you what you think about it. >>> - do you prefer to see trait methods

[Pharo-dev] What you think about visibility of trait method in browser?

Hello. In next Calypso version the option to enable or disable trait method visibility will not be available anymore (not my choice). All trait methods installed to the class will be just a class methods like it was in Nautilus. No way to hide them. I want to ask you what you think about it. - do

Re: [Pharo-dev] Extension methods in p7

Yes, the problem related to some changes. In latest image I have two packages: Gofer-Core and Gofer-core-accessing. So all such extensions force separate packages. 2018-08-21 10:10 GMT+01:00 Torsten Bergmann : > Hi Norbert, > > maybe it is unrelated - but I saw strange behavior with extensions

Re: [Pharo-dev] Extension methods in p7

Hi Norbert. In Calypso there are no protocols for extensions. You should simply call command Move methods to package either from menu or drag and drop to package (where you see it). I don't know what the reason for commit and removal. I will check. вт, 21 авг. 2018 г., 8:32 Norbert Hartl : >

Re: [Pharo-dev] About the infinite debugger

m/f/cases/20274/Debugger-infinite-recursion-when-terminating-delay-which-waits-inside-ensure-block> . They are still relevant 2018-08-07 22:01 GMT+01:00 Denis Kudriashov : > Hi. > > Good job guys. I just checked my case 19848 > <https://pharo.fogbugz.com/f/cases/19848/Step-o

Re: [Pharo-dev] About the infinite debugger

Hi. Good job guys. I just checked my case 19848 . And it is now fixed. Thanks 2018-06-29 15:48 GMT+01:00 Guillermo Polito : > Hi all, > > during today's sprint we

Re: [Pharo-dev] IndexedSlots in combination with StatefulTraits

Hi 2018-07-17 9:55 GMT+01:00 teso...@gmail.com : > Hi Torsten, >the problem is defining the behavior expected from the set of messages: > > Today we have 3 (yes 3 awful) they are to keep compatibility with the > tools, we have to continue improving them. > > - allSlots: returns all the

[Pharo-dev] Commenting test classes?

Hi. I noticed pull requests which add comments to test cases (class comments). I guess the reason is that in Calypso uncommented classes are marked differently than in Nautilus and the exclamation does not disappear when class provides special icon like status of tests. So the question is do we

Re: [Pharo-dev] [Pharo-users] [ann] gt documenter

Hi Tudor. This is super impressive. What's next? Do you plan to implement IDE for writing documents, navigation, refactorings? (senders, renames should find all places in documents) 2018-06-13 21:57 GMT+01:00 Tudor Girba : > Hi, > > We are happy to announce a new leap of GToolkit Documenter,

Re: [Pharo-dev] #literals and #hasLiteral: not in sync

Hi Marcus. #literals and #allLiterals are good idea but maybe we can better distinguish them using more specific names like: - for all literals: encodedLiterals or allEncodedLiterals - for real literals: syntaxLiterals, semanticLiterals, userLiterals, sourceCodeLiterals 2018-06-08 11:17

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

There is booklet https://github.com/SquareBracketAssociates/ Booklet-Infrastructure (Commander chapter). 2018-06-03 16:23 GMT+03:00 Peter Uhnák : > Commands are responsible to build menu items for themselves. By default >> they build single item. But you can override method and generate multiple

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

Hi Peter. 2018-06-02 19:17 GMT+03:00 Peter Uhnák : > > I believe we should move to Commander with first class commands. > > How would that work when menu entries can be generated dynamically? > Commands are responsible to build menu items for themselves. By default they build single item. But

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

Looks like Pharo 7 will be the most impressive release in all aspects of system:). About pragmas: I believe we should move to Commander with first class commands. It requires to create command classes for all menu items. For example "Save image": SaveImageCommand>>execute Smalltalk snapshot:

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-26 12:26 GMT+03:00 Guillermo Polito : > > > Also, didn't we agree that in Pharo7 we should try to remove something for > each thing that is added? > But it is not the case. We do not have logging system in Pharo. So Beacon will not replace anything. It is new

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-26 12:19 GMT+03:00 Norbert Hartl <norb...@hartl.name>: > > > Am 26.05.2018 um 08:41 schrieb Denis Kudriashov <dionisi...@gmail.com>: > > > 2018-05-26 9:30 GMT+03:00 Stephan Eggermont <step...@stack.nl>: > >> Denis Kudriashov <dionisi...@gmai

Re: [Pharo-dev] Beacon for Pharo 7

Very good questions. 2018-05-26 10:00 GMT+03:00 Guillermo Polito : > Hi all, > > Just to state my position about the integration of Beacon. My main concern > now is that I do not want to it become Glamour. > I do not want to integrate a new tool that will be half

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-26 10:20 GMT+03:00 Stephan Eggermont <step...@stack.nl>: > Denis Kudriashov <dionisi...@gmail.com> > wrote: > > If two entities needs separate versioning they should be in > separate > > repositories. Do you agree with this? > > They don’t, and sho

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-26 9:30 GMT+03:00 Stephan Eggermont <step...@stack.nl>: > Denis Kudriashov <dionisi...@gmail.com> > wrote: > > 2018-05-25 20:03 GMT+03:00 Stephan Eggermont > <step...@stack.nl>: > > > >> Denis Kudriashov <dionisi...@gmail.com> > &

Re: [Pharo-dev] Beacon for Pharo 7

gt; Norbert > > Am 25.05.2018 um 21:08 schrieb Tudor Girba <tu...@tudorgirba.com>: > > > > Hi, > > > > Yes, we want to have the concrete loggers managed with separate > baselines. I would also put them in individual repositories. > > > > Cheers, > &g

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-25 20:03 GMT+03:00 Stephan Eggermont <step...@stack.nl>: > Denis Kudriashov <dionisi...@gmail.com> > wrote: > > > > Because when you will fix or improve Beacon-SysLog you will probably do > not > > want to update Beacon-Core version which will forc

Re: [Pharo-dev] Beacon for Pharo 7

2018-05-25 17:21 GMT+03:00 Stephan Eggermont <step...@stack.nl>: > Denis Kudriashov <dionisi...@gmail.com> > wrote: > > Hi. > > > > I was looking at Beacon again to prepare integration. Some changes was > > needed in baseline for better granularity. S

[Pharo-dev] Beacon for Pharo 7

Hi. I was looking at Beacon again to prepare integration. Some changes was needed in baseline for better granularity. So I send pull request because I have no permissions. But now I remember that we had idea to integrate only core part of Beacon which requires MemoryLogger and TranscriptLogger.

Re: [Pharo-dev] feenk log

Hi Tudor. Very impressive progress. I have one question about scrolling support. How it works or is it works with elements which are based on infinite layout like mentioned grid widget? Does grid implemented with PannableElement too? 2018-05-25 14:30 GMT+03:00 Tudor Girba

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

part of Files, not FileSystem), keeping it > probably > > > > makes more sense. > > > > > > > > Similar duplication exists for FileAlreadyExistsException and > > > > FileExists. > > > > > > > > Thoughts? > > > > >

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

+1 2018-05-21 16:36 GMT+03:00 Sven Van Caekenberghe : > I vote for the simple names without Exception in them. > > > On 21 May 2018, at 15:01, Cyril Ferlicot D. > wrote: > > > > Le 21/05/2018 à 14:58, Alistair Grant a écrit : > >> Hi Everyone, > >> > >>

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

2018-05-17 13:00 GMT+03:00 Marcus Denker : > > I really wonder if this is the same as breakpoint. E.g. it only applies to >> the whole method, it is not an “action”, so a guter icon >> seems to be not the right visualization. >> > > Hm, I would like to see indication in

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

2018-05-17 10:53 GMT+03:00 Marcus Denker <marcus.den...@inria.fr>: > On 16 May 2018, at 18:21, Denis Kudriashov <dionisi...@gmail.com> wrote: > > > Hi Marcus. > I commented on github. > > 2018-05-16 18:34 GMT+03:00 Marcus Denker <marcus.den...@inria.fr>

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

2018-05-17 10:53 GMT+03:00 Marcus Denker <marcus.den...@inria.fr>: > On 16 May 2018, at 18:21, Denis Kudriashov <dionisi...@gmail.com> wrote: > > > Hi Marcus. > I commented on github. > > 2018-05-16 18:34 GMT+03:00 Marcus Denker <marcus.den...@inria.fr>

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

Hi Marcus. I commented on github. 2018-05-16 18:34 GMT+03:00 Marcus Denker : > > > > On 4 Apr 2018, at 18:02, Marcus Denker wrote: > > > > Hi, > > > > Some code is very “active”, executed all the time, e.g. collections, > graphics… or imagine if

Re: [Pharo-dev] [Pharo 7.0-dev] Build #869: 21863-Integrate-Calypso-v0113

Thanks Sven. But still there are a lot to improve in Calypso design and code. 2018-05-11 12:04 GMT+03:00 Sven Van Caekenberghe : > > > > On 11 May 2018, at 09:50, ci-pharo-ci-jenki...@inria.fr wrote: > > > > There is a new Pharo build available! > > > > The status of the build #869

Re: [Pharo-dev] fun with announcers

I checked on my few days image. And I have >2000 announcers. Cleaning Calypso cache does not help. And in fact after closing all browsers and collecting garbage the cache became empty. I found that most of subscriptions are related to rubric announcements. 2018-05-08 18:36 GMT+03:00

Re: [Pharo-dev] fun with announcers

Hi. Can you try with clean Calypso cache to check if it is the bad guy? Close all browsers, evaluate "ClyNavigationEnvironment reset" and collect garbage. 2018-05-08 11:05 GMT+03:00 Esteban Lorenzano : > Hi, > > A P7 image just downloaded: > > Announcer allInstances size.

Re: [Pharo-dev] Problems with the removal of Nautilus

Thanks Pavel 2018-05-04 16:24 GMT+03:00 Pavel Krivanek : > createPackageNamed: - solved by you > browse - adds an ability for RBBrowserEnvironment to be browsed by > Nautilus, no action needed > asRingDefinition - for UndefinedObject, solved by Nautilus removal, no >

Re: [Pharo-dev] Is Beacon still planned to be added to P7?

2018-04-26 16:27 GMT+02:00 Guillermo Polito : > > > On Mon, Apr 23, 2018 at 1:13 PM, Tudor Girba wrote: > >> I hope so. Beacon is ready to be integrated, but I do not know if there >> is enough bandwidth right now due to the Iceberg work. >> > >

Re: [Pharo-dev] SortedCollection based on SortFunction [Re: SortedCollection>>reverse answers an inconsistent object]

> itself for instances where sortblock is based on #<= as it currently is. > +1 for default function in collection. But I don't like solution. We have DefaultSortFunction for this. Only missing part is singleton instance: SortedCollection>>new ^self sortBlock: DefaultSortFun

[Pharo-dev] SortedCollection based on SortFunction [Re: SortedCollection>>reverse answers an inconsistent object]

Hi. Now we have really nice SortFunction's machinery. We can simply write: Object allSubclasses sorted: #name ascending instead of: Object allSubclasses sorted: [:a :b | a name <= b name ]. And there is special kind of SortFunction which represent such block itself: [:a :b | a name <= b

Re: [Pharo-dev] Calypso zero class refs for TComparable

s" relationship. And there is another option "Traits" for classes which uses traits. And notice that we do not show subclasses of class in the result of "Class refs" query. > > It will make your UI more consistent and predictable to the end user. > > Hilaire > &

Re: [Pharo-dev] Calypso zero class refs for TComparable

2018-04-22 16:01 GMT+02:00 Ben Coman <b...@openinworld.com>: > > On 22 April 2018 at 18:45, Denis Kudriashov <dionisi...@gmail.com> wrote: > >> Hi. >> >> When you select trait new hierarchy mode appears: trait users. >> > > I see it now, bu

Re: [Pharo-dev] Calypso zero class refs for TComparable

Hi. When you select trait new hierarchy mode appears: trait users. 2018-04-22 11:59 GMT+02:00 Cyril Ferlicot : > > On dim. 22 avr. 2018 at 03:54, Ben Coman wrote: > >> I expected TComparable to be used somewhere in the Image? >> >> So I was

Re: [Pharo-dev] Critiques - Temporaries read before written.

2018-04-15 20:40 GMT+02:00 Martin McClure : > On 04/15/2018 07:42 AM, Ben Coman wrote: > > The greater prominence of Critiques in Calypso > encourages me to try to clean them out. > > I bumped into a false positive "Temporaries read before written." > that I've condensed to

Re: [Pharo-dev] [Pharo70 alpha] Store settings raise a DNU primFlush

+1 to deprecate #closed 2018-04-14 16:24 GMT+02:00 Sean P. DeNigris : > Sven Van Caekenberghe-2 wrote > > If we add #closed to ZnBufferedReadStream… > > Would #isClosed be more consistent with the rest of the system? > > > > - > Cheers, > Sean > -- > Sent from:

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

2018-04-12 20:46 GMT+02:00 Stephane Ducasse : > Eliot > > We do not want to go the road of overrides. We want to keep our > engineer task forces. > We will need support this anyway. It's very similar to loading methods extending undefined class (you already have

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

will just need to fix code exporters and importers. But fixing package system is not easy task. Extension protocols and packages are bound implicitly using events. > Why can't we focus on important next steps. > I would say it is required step to achieve module system. > > On Thu, Apr

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

2018-04-12 12:31 GMT+02:00 Peter Uhnák : > In future it should be completely removed (you know how RPackage is ugly >> because of that). Only old text code formats will use star protocols. > > >> So Calypso is a step to remove this "star habit" from users. >> > > What is the

Re: [Pharo-dev] Why can't we use * in protocol for package extension?

But it shows notification why it does not supported and what to use instead. (it was not available in old versions) Idea to move away from star convention. Calypso gives you explicit tools to add method to the package. Most simple is checkbox "extension" in the status bar of method editor. For

Re: [Pharo-dev] Why String do not implement #displayString?

, Apr 10, 2018 at 5:28 PM, Esteban A. Maringolo > >>> <emaring...@gmail.com> wrote: > >>> > Isn't #displayString implemented in terms of #displayOn: the same way > >>> > #printString is implemented in terms of "printOn:"? > >>>

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

2018-04-11 17:02 GMT+02:00 Sven Van Caekenberghe : > > > > On 11 Apr 2018, at 16:36, Sven Van Caekenberghe wrote: > > > > I can make your example, using the Zn variants, work with the following > change: > > > > StdioStream>>#atEnd > > ^ peekBuffer isNil or: [

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

14:56 GMT+02:00 Alistair Grant <akgrant0...@gmail.com>: > Hi Sven & Dennis, > > On 11 April 2018 at 12:04, Denis Kudriashov <dionisi...@gmail.com> wrote: > > Hi Alistair. > > > > I don't think anybody is annoyed by you. You are doing really good job. >

Re: [Pharo-dev] Changed #atEnd primitive - #atEnd vs #next returning nil

> At the moment, ZnCharacterEncoder uses #atEnd on character / byte > streams, so fails for stdin on a terminal. > > Back to your questions: > > On 11 April 2018 at 11:12, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > > >> On 11 Apr 2018, at 10:29, Al

  1   2   3   4   5   6   7   8   9   10   >