- Pharo-users - lists.pharo.org

Re: [Pharo-users] Information on Spec development

by Alexandre Bergel

Thanks for sharing this. You guys are doing an amazing job. I do not mind having a couple of warning times to time. Cheers, Alexandre > On Jun 20, 2019, at 11:29 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hello everyone! > > This is an important update about the development of Spec. > > As you might have heard, we are working on Spec to release a new > version in Pharo 8. One goal is to unify all Pharo interfaces behind > one GUI framework and a second goal is to allow multiple back-ends > (Morphic but also GTK, Bloc, ...). To reach those goals we have been > updating the current version of Spec. We see now, however, that > updating Spec directly creates troubles with migration. For example, > we currently have a lot of deprecation warnings in Iceberg, because we > can't update it without breaking Pharo 7 compatibility. > > After some discussions between the engineers working on Spec, here is > our plan to improve the situation: We will copy all classes of Spec > and rename them with the "Sp" prefix. (We will also ensure that every > class of Spec started with the same prefix for consistency). For > extensions methods, we will rename them to have a version different > from Spec 1 (The spec from Pharo 7). Once done we will integrate this > new version in Pharo 8. From there we will wait some weeks to let > users who started to use the updated Spec change their projects to use > this new Spec2. Finally, we will revert all changes that happened on > Spec 1 and deprecate the packages. We hope this will make things > easier for everyone. > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 20, 2019

Information on Spec development

by Cyril Ferlicot

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

June 20, 2019

Re: [Pharo-users] Question: anyone using NOCompletion setting?

by Alexandre Bergel

Marcus, this is an excellent idea! Alexandre > On Jun 19, 2019, at 4:15 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 18 Jun 2019, at 19:34, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> I use it sometimes. IIRC there was a paper that it was objectively better at >> finding the "right" thing. Are you thinking of removing it? >> >> > > I would like to re-implement sorting of results in a more pluggable wayâ¦ so that e.g. > people can add more sorting ideas. > > But doing that in one step seems hardâ¦ it would be much easier if we could simplify the system > first. > > Removing the Ocompletion (for a while) would make it much easierâ¦ > > Marcus > >

June 20, 2019

seaside hosting

by Jeff Gray

Are there options for hosting seaside apps? I had a look round but didn't see much. I could run it from home I suppose. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 20, 2019

sqlite garage

by Jeff Gray

anyone using Garage for accessing SQLite? I am using Garage for MySQL in Pharo 7 on windows and it all works seamlessly but I don't know what connection string to use to connect to a database file that I have in my pharo directory. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 20, 2019

Re: [Pharo-users] Playground auto-save?

by Hilaire

June 19, 2019

Re: [Pharo-users] Playground auto-save?

by Esteban Maringolo

I still don't know why there is no explicit "save", to at least capture that state in the play-stash. There is an explicit "publish" to the cloud, but no save. Esteban A. Maringolo On Wed, Jun 19, 2019 at 2:34 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > if you give the playground's tab a name, it will save it under that name > in pharo-local/play-stash - which I found reasonably reliable. > > > On 19 Jun 2019, at 15:38, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > Hi Hilaire, > > > > this is a known problem. I've been losing code to Playground for years. > (e.g. using undo (ctrl+z) is a good way to lose code) > > > > What helps a lot is to look into pharo-local/play-cache directory (you > can open Spotter and type in "pharo-local" (without quotes)) which contains > a log of probably 90% of playgrounds you executed. > > > > There are still some conditions under which you can lose code even with > play-cache (e.g. ctrl+z sometimes)... so good to keep that in mind. > > > > Peter > > > > On Wed, Jun 19, 2019 at 3:20 PM Hilaire <hilaire(a)drgeo.eu> wrote: > > Beside that, auto-save is a nice feature, but it needs to be predictable. > > > > Hilaire > > > > Le 18/06/2019 Ã 21:53, Hilaire a Ã©crit : > > > Hi, > > > > > > I have to admit it is working randomly in P7 with Dr.Geo. (19.06 rel) > > > > > > Sometime script can be retrieved with the playpage button other time > no: > > > executed script can not be retrieved. > > > > > > Its behavior is not predictable and it is a problem for me and the kids > > > playing code. > > > > > > Hilaire > > > > -- > > Dr. Geo > > http://drgeo.eu > > > > > > > > >

June 19, 2019

Re: [Pharo-users] Playground auto-save?

by Hilaire

Ok, good to know. Looking fot pharo-local from Spotter does not produce meaningful results within DrGeo (P7 based), screenshot attached. The folder DrGeo/Contents/Resources/pharo-local/play-cache exists though Thanks. Le 19/06/2019 Ã 15:38, Peter Uhnak a Ã©critÂ : > this is a known problem. I've been losing code to Playground for > years. (e.g. using undo (ctrl+z) is a good way to lose code) > -- Dr. Geo http://drgeo.eu

June 19, 2019

Re: [Pharo-users] Playground auto-save?

by Sven Van Caekenberghe

if you give the playground's tab a name, it will save it under that name in pharo-local/play-stash - which I found reasonably reliable. > On 19 Jun 2019, at 15:38, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Hi Hilaire, > > this is a known problem. I've been losing code to Playground for years. (e.g. using undo (ctrl+z) is a good way to lose code) > > What helps a lot is to look into pharo-local/play-cache directory (you can open Spotter and type in "pharo-local" (without quotes)) which contains a log of probably 90% of playgrounds you executed. > > There are still some conditions under which you can lose code even with play-cache (e.g. ctrl+z sometimes)... so good to keep that in mind. > > Peter > > On Wed, Jun 19, 2019 at 3:20 PM Hilaire <hilaire(a)drgeo.eu> wrote: > Beside that, auto-save is a nice feature, but it needs to be predictable. > > Hilaire > > Le 18/06/2019 Ã 21:53, Hilaire a Ã©crit : > > Hi, > > > > I have to admit it is working randomly in P7 with Dr.Geo. (19.06 rel) > > > > Sometime script can be retrieved with the playpage button other time no: > > executed script can not be retrieved. > > > > Its behavior is not predictable and it is a problem for me and the kids > > playing code. > > > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

June 19, 2019

Re: [Pharo-users] Playground auto-save?

by Peter Uhnak

Hi Hilaire, this is a known problem. I've been losing code to Playground for years. (e.g. using undo (ctrl+z) is a good way to lose code) What helps a lot is to look into pharo-local/play-cache directory (you can open Spotter and type in "pharo-local" (without quotes)) which contains a log of probably 90% of playgrounds you executed. There are still some conditions under which you can lose code even with play-cache (e.g. ctrl+z sometimes)... so good to keep that in mind. Peter On Wed, Jun 19, 2019 at 3:20 PM Hilaire <hilaire(a)drgeo.eu> wrote: > Beside that, auto-save is a nice feature, but it needs to be predictable. > > Hilaire > > Le 18/06/2019 Ã 21:53, Hilaire a Ã©crit : > > Hi, > > > > I have to admit it is working randomly in P7 with Dr.Geo. (19.06 rel) > > > > Sometime script can be retrieved with the playpage button other time no: > > executed script can not be retrieved. > > > > Its behavior is not predictable and it is a problem for me and the kids > > playing code. > > > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > > >

June 19, 2019