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

Re: [Pharo-dev] Commenting the Session Manager

by Ben Coman

hi Guille, Thanks very much for that detailed write up. I have one concern about the [bracketed] text... A new session starts when the image starts [or when the image is saved]. A session ends when the image quits [or it is saved]. Doing the following in a playground... s1 := SessionManager default currentSession. "Save image without quitting" s2 := SessionManager default currentSession. "Save and quit image, then after reloading..." 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... https://www.diffchecker.com/FUWg5J8t cheers -ben On Thu, Apr 13, 2017 at 5:41 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi all, > > I took some minutes to write down a class comment for the SessionManager > class. There was an issue asking for it: > > https://pharo.fogbugz.com/f/cases/19463/Improve- > SessionManager-class-comment > > Since it is an important topic, and sometimes too low level for some > people, I'd like to have some feedback. Is it well explained? Is there > something that is key for you and is missing? > > I know that the comment is not exhaustive, it can be iterated and > enhanced, but we can have a nice first version of it for the release. > > Thanks, > Guille > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > I am the object responsible of managing how sessions work in Pharo. > A session defines the boundaries of work in the image. > > A new session starts when the image starts or when the image is saved. > A session ends when the image quits or it is saved. > There is only one active session at a single point of time. > Saving the image causes the active to stop, and starts a new session. > > > The current active session is hold by myself, the singleton session > manager. It can be accessed by doing: > > SessionManager default currentSession. > > The most important responsibility of the session manager is to manage how > resources and services in the image are started up and shut down at the > beginning and end of a session respectively. For example, when the image > starts, several initialization routines should be executed to make sure > that the image has access to the graphic drivers, the standard input/output > file descriptors and so on. > > Such initialization happens in the #snapshot:andQuit: method. > #snapshot:andQuit: will: > - stop current session > - save current image if requested > - quit if requested > - start a new session > > When a session is started, all elements registered in the startup list are > started up. > When a session is stopped, all elements registered in the shutdown list > are shut down. > > # Managing Startup and Shutdown lists > > The startup and shutdown lists can be accessed through the messages: > > SessionManager default startupList. > SessionManager default shutdownList. > > In general terms, the shutdown list is the startup list reversed. > > Upon a startup [shutdown], all elements in the startup list are sent the > message #startup: [#shutdown:] with a boolean as argument that indicates > wether the image is being saved [closed]. > > Internally, startup and shutdown lists are prioritised. Priorities are > managed by startup categories. By default the session manager includes the > following categories in decreasing priority order: > > - System > - Network > - Graphical User Interface > - Tools > - User > > Categories can be accessed as follows: > > SessionManager default categoryNamed: aName. > > New categories can be registered in the system using the messages: > > SessionManager default createCategory: aCategoryName. > SessionManager default createCategory: aCategoryName after: > anotherCategoryName. > > Finally, to subscribe some resource handler to the startup shutdown lists, > we need to subscribe a handler, subclass of AbstractSessionHandler. > The most common handler implementation so far is the ClassSessionHandler, > that allows to subscribe a class for startup and shutdown, keeping > backwards compatibility to the old startup mechanism. > > ClassSessionHandler forClassNamed: aClassName > > We can register a session handler as follows > > SessionManager default > register: (ClassSessionHandler forClassNamed: self name) > inCategory: SessionManager default systemCategory. > Or alternatively, by talking to the corresponding category: > > SessionManager default systemCategory register: (ClassSessionHandler > forClassNamed: self name) > > # System Category Priorities > > A system category internally prioritizes its elements to provide a fine > grained control on the startup and shutdown order. > All methods above have variants that allow developers to specify the > priority inside the category: > > SessionManager default > register: (ClassSessionHandler forClassNamed: self name) > inCategory: SessionManager default systemCategory > atPriority: 100. > > SessionManager default systemCategory > register: (ClassSessionHandler forClassNamed: self name) > atPriority: 100 > By default, if no priority is specified, a default priority is used. Every > category answers to the message #defaultPriority. > > # How does an image restart from the point it was before > > An important point in the image startup is how does it manage to restart > from the point where it was executing when it was saved. > > When the image is saved, using the snapshot primitive, the entire image is > freezed at the point of the snapshot. > More particularly, the process that invoked the snapshot primitive is > freezed at the point of the primitive call. > This works as a process fork: the running image will return from the > snapshot primitive and the saved file will also start from the freezed > point. > To differentiate whether we are executing in the running image or in the > freshly-saved image, the snapshot primitive returns a boolean indicating it. > > Read the comment of #snapshotPrimitive for more details. >

April 18, 2017

Re: [Pharo-dev] Test and Patch for writeStream error

by Blondeau Vincent

Hi, Thanks for reporting! If you want to contribute and have your fix integrated, I advise you to follow the procedure here: http://pharo.org/contribute-propose-fix If you need help, don't hesitate to reply! Regards, Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de K K > Subbu > EnvoyÃ© : mardi 18 avril 2017 17:34 > Ã : Pharo Development List > Objet : [Pharo-dev] Test and Patch for writeStream error > > Hi, > > I stumbled on an error in WriteStream>>ensureEndsWith: method. The error > caused extra blank lines in logs. > > Attached small changeset fixes it. It also adds a test to catch such errors in > the future. With this fix, > > ./pharo generator.image PharoVMSpur32Builder buildUnix32 > > gives a compact output without extra blank lines. > > To which box in which repo should I save this cs for mainlining it? > > Regards .. Subbu !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

April 18, 2017

Test and Patch for writeStream error

by K K Subbu

Hi, I stumbled on an error in WriteStream>>ensureEndsWith: method. The error caused extra blank lines in logs. Attached small changeset fixes it. It also adds a test to catch such errors in the future. With this fix, ./pharo generator.image PharoVMSpur32Builder buildUnix32 gives a compact output without extra blank lines. To which box in which repo should I save this cs for mainlining it? Regards .. Subbu

April 18, 2017

Re: [Pharo-dev] Iceberg and git repository management

by Christophe Demarey

Hi Peter, It will be possible and is already doable but with no ui support. You can use these messages: iceRepository contentOfFileNamed: 'relative/path/from/git/repo/rootâ commit: repository headCommit id iceRepository saveContent: âblaâ inWorkingCopyFile: ârelative/path/from/git/repo/rootâ. It adds the file to the git index. You still need to commit the index with the message #commitIndexWithMessage:andParents: after the file is written. Also, take care to not write Pharo code after that as it will override your working copy. Christophe > Le 16 avr. 2017 Ã 12:26, Peter Uhnak <i.uhnak(a)gmail.com> a Ã©crit : > > Hi, > > is Iceberg (or its git subsytem) capable of more than just Pharo code management? > > More specifically, would it be possible with Iceberg to commit e.g. a change to a README.md or .travis.yml file in the repository? > > Thanks, > Peter >

April 18, 2017

Re: [Pharo-dev] Please, test our 64bits builds

by Gabriel Cotelli

Hi Estaban, I've started working with this version and seems to be working ok. Just a minor detail with the zeroconf stuff, It still shows the 32 bits libraries notice when you download the image and vm: On a 64-bit system? You must install the 32-bit libraries Try `sudo aptitude install ia32-libs` or see http://pharo.org/gnu-linux-installation#64-bit-System-Setup for more info We can remove it when downloading the 64 bits version ;) On Wed, Apr 12, 2017 at 1:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > forget to say that iceberg will not work 100% yet :) > but here, problem is because you need to install the threaded version, > which of course I forget to point :P > > curl get.pharo.org/64/60+vmTLatest | bash > > > this is the correct one for linux users. > > Esteban > > > > On 12 Apr 2017, at 17:23, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban, > > On Wed, Apr 12, 2017 at 04:44:51PM +0200, Esteban Lorenzano wrote: > > Hello list, > > We are approaching to release and one big thing of this one is the > 64bits supports for Pharo (limited, since there is still not support > for Windows, but it will arrive, eventually ;) ) I asked you to test a > couple of months ago but now we are in better shape to do it. > > - VM and image are getting more and more stable and crashes > shouldn???t happen (but that???s why I want you to test: to discover > possible bugs/crashes) - I made 64bits a zeroconf citizen: > http://get.pharo.org/64 > > Now, you can test it by just doing: > > curl get.pharo.org/64/60+vmLatest | bash (In linux or mac, remember it > will not work for Windows) > > > I'm getting: > > LGit_GIT_ERROR: no error message set by libgit2 > > (full stack below) > > while executing: > > Metacello new > githubUser: 'pharophile' > project: 'TilingWindowManager' > commitish: 'master' > path: 'packages'; > baseline: 'TilingWindowManager'; > onWarningLog; > load. > > > Checking that libgit2.so is OK produces: > > $ ldd libgit2.so > ./libgit2.so: > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libssl.so.1.0.0: no > version information available (required by > /usr/lib/x86_64-linux-gnu/libcurl.so.4) > ./libgit2.so: > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libssl.so.1.0.0: no > version information available (required by > /usr/lib/x86_64-linux-gnu/libcurl.so.4) > ./libgit2.so: > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libssl.so.1.0.0: no > version information available (required by > /usr/lib/x86_64-linux-gnu/libcurl.so.4) > ./libgit2.so: > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libcrypto.so.1.0.0: no > version information available (required by > /usr/lib/x86_64-linux-gnu/libcurl.so.4) > linux-vdso.so.1 => (0x00007ffde370e000) > libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 > (0x00007f3b11727000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 > (0x00007f3b1150d000) > libssl.so.1.0.0 => > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libssl.so.1.0.0 > (0x00007f3b1129c000) > libcrypto.so.1.0.0 => > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libcrypto.so.1.0.0 > (0x00007f3b10ebf000) > libssh2.so.1 => > /dev/shm/p6/pharo-vm/lib/pharo/5.0-201704120850/libssh2.so.1 > (0x00007f3b10c86000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > (0x00007f3b10a7d000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f3b10860000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x00007f3b10497000) > libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 > (0x00007f3b10263000) > librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 > (0x00007f3b10047000) > libgssapi_krb5.so.2 => > /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f3b0fdfd000) > liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 > (0x00007f3b0fbed000) > libldap_r-2.4.so.2 => > /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f3b0f99c000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x00007f3b0f798000) > /lib64/ld-linux-x86-64.so.2 (0x0000561a2abc3000) > libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 > (0x00007f3b0f467000) > libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 > (0x00007f3b0f234000) > libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 > (0x00007f3b0effd000) > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 > (0x00007f3b0ed7d000) > libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 > (0x00007f3b0eaab000) > libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 > (0x00007f3b0e87b000) > libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 > (0x00007f3b0e677000) > libkrb5support.so.0 => > /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f3b0e46c000) > libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 > (0x00007f3b0e250000) > libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 > (0x00007f3b0e035000) > libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 > (0x00007f3b0ddf4000) > libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 > (0x00007f3b0db8f000) > libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 > (0x00007f3b0d97c000) > libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 > (0x00007f3b0d778000) > libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 > (0x00007f3b0d56e000) > libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 > (0x00007f3b0d2e4000) > libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 > (0x00007f3b0d041000) > libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 > (0x00007f3b0ce0e000) > libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 > (0x00007f3b0cbf8000) > libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 > (0x00007f3b0c9ef000) > libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 > (0x00007f3b0c7c6000) > libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 > (0x00007f3b0c5b7000) > libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 > (0x00007f3b0c36b000) > libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > (0x00007f3b0c096000) > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x00007f3b0be5e000) > > > The first few lines look dodgy to me. Searching on google (admittedly > briefly) it wasn't clear to me whether this is a fatal error or just a > warning. Most of the responses suggest recompiling with matching > versions, symbols, etc. > > Is there something else you'd like me to try? I can have a go at > compiling if you think it will help. > > Cheers, > Alistair > > > LGitReturnCodeEnum>>handleLGitReturnCode > LGitRepository(LGitExternalObject)>>withReturnHandlerDo: > LGitRepository>>clone:options:to: > LGitRepository>>clone:options: > [ | repo cloneOptions | > repo := LGitRepository on: self location. > cloneOptions := LGitCloneOptions > withCredentialsProvider: IceCredentialsProvider default. > repo clone: url options: cloneOptions. > aBranchName ifNotNil: [ repo checkout: aBranchName ]. > (LGitRemote of: repo named: 'origin') > lookup; > setUrl: url ] in IceLibgitLocalRepository>>cloneRepositoryFrom:branch: in > Block: [ | repo cloneOptions |... > [ self checkInitialized. > aBlock value ] in LGitGlobal class>>runSequence: in Block: [ self > checkInitialized.... > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in LGitActionSequence(DynamicVariable)>>value:during: in > Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > LGitActionSequence(DynamicVariable)>>value:during: > LGitActionSequence class(DynamicVariable class)>>value:during: > LGitGlobal class>>runSequence: > IceLibgitLocalRepository>>cloneRepositoryFrom:branch: > IceRepositoryCreator>>createRepository > [ (IceRepositoryCreator new > url: remoteUrl; > subdirectory: repoPath; > branchName: self projectVersion; > createRepository) register ] in MCGitHubRepository>>getOrCreateIcebergRepository > in Block: [ (IceRepositoryCreator new... > OrderedCollection(Collection)>>detect:ifFound:ifNone: > OrderedCollection(Collection)>>detect:ifNone: > MCGitHubRepository>>getOrCreateIcebergRepository > IceGithubRepositoryType>>mcRepository > Iceberg class>>mcRepositoryFor: > [ :cl | > (cl enableMetacelloIntegration > and: [ IceMetacelloRepositoryType canHandleType: type ]) > ifTrue: [ ^ cl mcRepositoryFor: aRepositorySpec description ] ] in > MetacelloPharo30Platform(MetacelloPharoCommonPlatform)>>createRepository: > in Block: [ :cl | ... > BlockClosure>>cull: > SystemDictionary(Dictionary)>>at:ifPresent: > SmalltalkImage>>at:ifPresent: > MetacelloPharo30Platform(MetacelloPharoCommonPlatform)>>createRepository: > MetacelloMCBaselineProject(MetacelloMCProject)>>createRepository: > MetacelloRepositorySpec>>createRepository > [ aSpec createRepository ] in [ :aSpec | > | description repo | > description := aSpec description. > (repo := repositories > detect: [ :rep | rep description = description ] > ifNone: [ aSpec createRepository ]) ~~ nil > ifTrue: [ repos add: repo ] ] in MetacelloFetchingMCSpecLoader( > MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: > [ aSpec createRepository ] > Array(Collection)>>detect:ifFound:ifNone: > Array(Collection)>>detect:ifNone: > [ :aSpec | > | description repo | > description := aSpec description. > (repo := repositories > detect: [ :rep | rep description = description ] > ifNone: [ aSpec createRepository ]) ~~ nil > ifTrue: [ repos add: repo ] ] in MetacelloFetchingMCSpecLoader( > MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: > [ :aSpec | ... > > >

April 18, 2017

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

by Denis Kudriashov

Hi Martin. 2017-04-18 0:22 GMT+02:00 Martin Dias <tinchodias(a)gmail.com>: > You can disable it: World Menu > Settings > Tools > Epicea > Detect lost > events on start up Idea to not disable it but to show notification about lost changes with button to open changes browser. It should remove delay on image startup because full changes will be not loaded in that case.

April 18, 2017

Re: [Pharo-dev] Missing VMMaker repo in Pharo 6

by Ben Coman

On Tue, Apr 18, 2017 at 1:57 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > On Monday 17 April 2017 11:52 PM, Cyril Ferlicot D. wrote: > > StartupPreferencesLoader default >> addAtStartupInGeneralPreferenceFolder: >> {(StartupAction >> name: 'Add my repository' >> code: [ MCRepositoryGroup default >> addRepository: >> (MCSqueaksourceRepository location: 'http://source.squeak.org/VMMaker') ] >> runOnce: true)} >> > > Thank you for this nice tip. I was just curious about why this repo was > omitted from the built-in repos in a released image? Is VMMaker not a > supported package for Pharo? > Pharo is not delivered with VMMaker built-in / pre-loaded. So neither is its repo built-in. VMMaker is not relevant to most users, and it has no priority over 100s of user packages. All the repos you see built-in are actually components delivered built-into Pharo. btw, AFAIK the VM Simulator doesn't work on Pharo - though I'm not sure anyone has had a serious look at it. The main vm-devs and the OpenSmalltalk CI builds work on top of Squeak. cheers -ben

April 18, 2017

Re: [Pharo-dev] Missing VMMaker repo in Pharo 6

by K K Subbu

On Monday 17 April 2017 11:52 PM, Cyril Ferlicot D. wrote: > StartupPreferencesLoader default > addAtStartupInGeneralPreferenceFolder: > {(StartupAction > name: 'Add my repository' > code: [ MCRepositoryGroup default addRepository: > (MCSqueaksourceRepository location: 'http://source.squeak.org/VMMaker') ] > runOnce: true)} Thank you for this nice tip. I was just curious about why this repo was omitted from the built-in repos in a released image? Is VMMaker not a supported package for Pharo? pharo-vm use of generator.image to build vmmaker is really neat. If systemtracer is also integrated into generator.image, then we could build a single static binary bootstrapper (like busybox on Linux) that can be scripted to cross-compile both vm and image. Regards .. Subbu

April 18, 2017

Re: [Pharo-dev] Help currency review

by Martin Dias

I created a fogbugz case for Epicea https://pharo.fogbugz.com/f/cases/19946/Update-Epicea-help On Sun, Apr 16, 2017 at 8:34 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > tx ben > indeed this is nice to update this text > s. > > On Sat, Apr 8, 2017 at 4:25 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> At this late stage of Pharo 6 development, it might be good to do a pass >> at... >> World > Help > Help Browser content >> >> Epicea >Browsers - mentions two separate browser windows >> >> GT Debugger >> Actions - TODO >> >> GT Playground >> Overview - http://gt.moosetechnology.org redirects to >> http://gtoolkit.org/ >> and same for several GT entries >> >> Welcome > Getting Help says... >> - The "Pharo Users" mailing list: http://lists.pharo.org/mailman >> /listinfo/pharo-users_lists.pharo.org >> - The "Pharo Slack Team": http://slack4pharo.trentosur.com/ >> - The "Pharo IRC Channel": irc.freenode.net, #pharo channel >> - http://pharo.org/community >> >> So we should change from Slack to Discord. >> I can take care of this one but a couple questions... >> >> 1. I propose a Discord #Help channel to record here in the help browser. >> >> 2. I bumped into an interesting tip >> https://www.reddit.com/r/discordapp/comments/3yu1bh/server_ >> vs_channel_invites/ >> >> Thus I propose we have a #Welcome channel providing info like what the >> bot has been providing. >> Later it could be good to have a bot just in that channel, but not off >> someone's home server :) >> I would expect that channel to not need anyone lurking in it. Newcomers >> will jump immediately >> from there #Help or #General >> >> 3. How active is the IRC channel? Should we remove it from the help >> browser? >> The mention at http://pharo.org/community could be sufficient. >> >> 4. Should we backport this help info update to Pharo 5? >> >> cheers -ben >> >> >

April 17, 2017

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

by Martin Dias

You can disable it: World Menu > Settings > Tools > Epicea > Detect lost events on start up I can make it initially disabled by default. However, I have an optimization that can improve a lot the time to read, maybe we can still integrate a new version of Epicea before 6.0 release. I've been testing it for a couple of weeks and works well. On Sun, Apr 16, 2017 at 11:09 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Me three > > Recover dialog is standard on all apps anyway > On Sun, 16 Apr 2017 at 16:22, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2017-04-16 12:09 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: >> >>> Of course if I am the only person that uses images in such a way then I >>> can just work around it myself. (because having endless lists of config >>> options is also nightmare) >> >> >> Me too >> >

April 17, 2017