Pharo 4, format on accept/display
Hi I've hacked together an implementation of format on accept & display. I know someone is redoing that functionality to better suit future needs. Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness? Thanks Paul
By "publish a slice" do you also mean to ask it to be integrated into Pharo4? The general issue is that every new fix for the released Pharo40 has the *chance* of introducing some other problem, or adversely affecting someone else's idea of how the system should operate. Even with minimal quaility assurance for a release it takes effort to integrate fixes, so each needs to be evaluated for impact. So the options for Pharo 4 are: 1. Continually integrate fixes as they arise ==> ++effort 2. Continually integrate critical fixes only, hold all others for the next point release. 3. Hold all fixes for next point release. I don't see this as a critical fix :), so you'd be asking for (1.), when probably (2.) should be the rule. Now I had the idea that fixes for a release that were not immediately integrated might be published as a "hotfix" - taking Microsoft's terminology for an update fixing a specific issue without having gone through full quality control with all other fixes, so kind of "use at own risk". I'm not sure if that was popular or the best way to go about it. Possibly just adding "hotfix" in the mcz file name would provide enough to find them by filtering. cheers -ben On Thu, Jun 11, 2015 at 2:47 AM, Paul DeBruicker <pdebruic@gmail.com> wrote:
Hi
I've hacked together an implementation of format on accept & display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness?
Thanks
Paul
If my understanding of Pharo's release management is correct, then no new features are added after a release, only bugfixes. So from this perspective I would suggest to publish it to Pharo50Inbox instead, including creating a new issue in Pharo bugtracker where you describe what is it changing. If you need in Pharo 4 it may be preferable to create a new repository for it (at smalltalkhub) and pushing it's configuration to http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo40, so people can install it manually via Configuration Browser without affecting Pharo 4 release. Peter On Thu, Jun 11, 2015 at 7:25 AM, Ben Coman <btc@openinworld.com> wrote:
By "publish a slice" do you also mean to ask it to be integrated into Pharo4?
The general issue is that every new fix for the released Pharo40 has the *chance* of introducing some other problem, or adversely affecting someone else's idea of how the system should operate. Even with minimal quaility assurance for a release it takes effort to integrate fixes, so each needs to be evaluated for impact. So the options for Pharo 4 are: 1. Continually integrate fixes as they arise ==> ++effort 2. Continually integrate critical fixes only, hold all others for the next point release. 3. Hold all fixes for next point release.
I don't see this as a critical fix :), so you'd be asking for (1.), when probably (2.) should be the rule.
Now I had the idea that fixes for a release that were not immediately integrated might be published as a "hotfix" - taking Microsoft's terminology for an update fixing a specific issue without having gone through full quality control with all other fixes, so kind of "use at own risk". I'm not sure if that was popular or the best way to go about it. Possibly just adding "hotfix" in the mcz file name would provide enough to find them by filtering.
cheers -ben
On Thu, Jun 11, 2015 at 2:47 AM, Paul DeBruicker <pdebruic@gmail.com> wrote:
Hi
I've hacked together an implementation of format on accept & display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness?
Thanks
Paul
On 11 Jun 2015, at 08:16, Peter Uhnák <i.uhnak@gmail.com> wrote:
If my understanding of Pharo's release management is correct, then no new features are added after a release, only bugfixes.
Yes, but we do make exceptions⦠e.g. I added format on display and accept to Pharo3 after the release, because it is indeed a nice thing to have. So in that sense not having it in Pharo4 is kind of a bug. The version we get in Pharo5 will come with a new pretty printer, we will not back port that, so doing a âminimally intrusiveâ version for Pharo4 makes sense. Marcus
The 'fix' for Pharo40 is in the Pharo40Inbox as Slice-14387. It formats code on accept and/or display using the RBConfigurableFormatter. Marcus Denker-4 wrote
On 11 Jun 2015, at 08:16, Peter Uhnák <
i.uhnak@
> wrote:
If my understanding of Pharo's release management is correct, then no new features are added after a release, only bugfixes.
Yes, but we do make exceptionsâ¦
e.g. I added format on display and accept to Pharo3 after the release, because it is indeed a nice thing to have.
So in that sense not having it in Pharo4 is kind of a bug.
The version we get in Pharo5 will come with a new pretty printer, we will not back port that, so doing a âminimally intrusiveâ version for Pharo4 makes sense.
Marcus
-- View this message in context: http://forum.world.st/Pharo-4-format-on-accept-display-tp4831485p4831720.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Thanks, I will have a look.
On 11 Jun 2015, at 16:39, Paul DeBruicker <pdebruic@gmail.com> wrote:
The 'fix' for Pharo40 is in the Pharo40Inbox as Slice-14387.
It formats code on accept and/or display using the RBConfigurableFormatter.
Marcus Denker-4 wrote
On 11 Jun 2015, at 08:16, Peter Uhnák <
i.uhnak@
> wrote:
If my understanding of Pharo's release management is correct, then no new features are added after a release, only bugfixes.
Yes, but we do make exceptionsâ¦
e.g. I added format on display and accept to Pharo3 after the release, because it is indeed a nice thing to have.
So in that sense not having it in Pharo4 is kind of a bug.
The version we get in Pharo5 will come with a new pretty printer, we will not back port that, so doing a âminimally intrusiveâ version for Pharo4 makes sense.
Marcus
-- View this message in context: http://forum.world.st/Pharo-4-format-on-accept-display-tp4831485p4831720.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Format on display does horrible things to the Playground for the version I uploaded yesterday. A new version is in the inbox that does not do them. Marcus Denker-4 wrote
Thanks, I will have a look.
On 11 Jun 2015, at 16:39, Paul DeBruicker <
pdebruic@
> wrote:
The 'fix' for Pharo40 is in the Pharo40Inbox as Slice-14387.
It formats code on accept and/or display using the RBConfigurableFormatter.
Marcus Denker-4 wrote
On 11 Jun 2015, at 08:16, Peter Uhnák <
i.uhnak@
> wrote:
If my understanding of Pharo's release management is correct, then no new features are added after a release, only bugfixes.
Yes, but we do make exceptionsâ¦
e.g. I added format on display and accept to Pharo3 after the release, because it is indeed a nice thing to have.
So in that sense not having it in Pharo4 is kind of a bug.
The version we get in Pharo5 will come with a new pretty printer, we will not back port that, so doing a âminimally intrusiveâ version for Pharo4 makes sense.
Marcus
-- View this message in context: http://forum.world.st/Pharo-4-format-on-accept-display-tp4831485p4831720.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- View this message in context: http://forum.world.st/Pharo-4-format-on-accept-display-tp4831485p4831805.htm... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Le 10/6/15 20:47, Paul DeBruicker a écrit :
Hi
I've hacked together an implementation of format on accept & display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness? Yes it is cool :) :) new text editor new pretty printer :) print on read print on accept :)
Thanks
Paul
Date: Thu, 11 Jun 2015 08:35:10 +0200 From: stepharo@free.fr To: pharo-dev@lists.pharo.org Subject: Re: [Pharo-dev] Pharo 4, format on accept/display
Le 10/6/15 20:47, Paul DeBruicker a écrit :
Hi
I've hacked together an implementation of format on accept & display.
I know someone is redoing that functionality to better suit future needs.
Should I publish what I've got as a slice to the Pharo40Inbox for people to use that may miss it now that do not want to wait for the new hotness? Yes it is cool :) :) new text editor new pretty printer :) print on read print on accept :) Hi,
We are working on a new pretty printer and using rubric in Nautilus for the source code area so you will soon be able to format on accept but not only. A format as you read feature will be introduce, if you activate it, it will format the source code with your own preferences every time you read code, and every time you accept. Franck
Thanks
Paul
participants (6)
-
Ben Coman -
Franck Warlouzet -
Marcus Denker -
Paul DeBruicker -
Peter Uhnák -
stepharo