It's December, and time to consider freezing the 4.2 code base. If we
can push any final enhancements and image documentation desired for 4.2 in over the next week, we can freeze officially on the 11th. Is this ok? We should begin considering the release-notes. What is the easiest way to identify everything that's one into 4.2 since 4.1? Some of the items listed at the 4.2-release page (http://wiki.squeak.org/squeak/6160) are: - Integration of Cryptography - Documentation - Integration of O-Completion What do we all think about integration of O-Completion? Levente already did the work, it makes the IDE that much more useful and modern and, it can be turned off. Shall we include that? What What else do we need to consider for the 4.2 image release? |
O-Completion: +1 This is something that I can show developers who are new to Smalltalk that they'll recognize and appreciate. I think it's a really big win.
On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: It's December, and time to consider freezing the 4.2 code base. If we -- Casey Ransberger |
Administrator
|
+1 for O-Completion
Cheers,
Sean |
O-Completion: +1
2010/12/5 Sean P. DeNigris <[hidden email]>
|
In reply to this post by Chris Muller-3
What do we all think about integration of O-Completion? Levente If it is stable, independent package, everyone can load it. As far as I understand the reasoning of why package X is in Trunk it is that (1) it is easier to develop trunk image with some set of currently cohesive packages in place, or that (2) package provides some essential functionality in line with Squeak's vision. I do use Squeak everyday but I have no need in funcionality O-Completion provides. I am interested that list of packages I need to unload before release do not grow.
Vaidotas
|
On 12/5/10 7:45 AM, "Vaidotas Didžbalis" <[hidden email]> wrote: If it is stable, independent package, everyone can load it. As far as I understand the reasoning of why package X is in Trunk it is that (1) it is easier to develop trunk image with some set of currently cohesive packages in place, or that (2) package provides some essential functionality in line with Squeak's vision. I do use Squeak everyday but I have no need in funcionality O-Completion provides. I am interested that list of packages I need to unload before release do not grow. As builder of reduced images , I also was against packages list grows and grows. We should have a SqueakCore , as several times ask , and a serious work on it. And a list of well done , documented and useful packages which loads nicely and they do not fight each other. Edgar |
In reply to this post by Casey Ransberger-2
About easy loading of 'community supported packages' ... Philipp Tessenow and I are working on something there, to make it easier. Shouldn't take much longer, will announce soon-ish.
-- Gesendet von meinem Palm Pre Casey Ransberger <[hidden email]> schrieb am 05.12.2010 03:52: O-Completion: +1 This is something that I can show developers who are new to Smalltalk that they'll recognize and appreciate. I think it's a really big win.
On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: It's December, and time to consider freezing the 4.2 code base. If we -- Casey Ransberger |
In reply to this post by laza
O-Completion: +1
Any dev environment provides help to the new users, and if we want more squeakers we need to offer tools as O-Completion. 2010/12/5 Alexander Lazarević <[hidden email]>: > O-Completion: +1 > > 2010/12/5 Sean P. DeNigris <[hidden email]> >> >> +1 for O-Completion >> -- >> View this message in context: >> http://forum.world.st/4-2-code-freeze-tp3072962p3073011.html >> Sent from the Squeak - Dev mailing list archive at Nabble.com. >> > > > > > -- ================================================= Germán S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com ================================================= |
In reply to this post by Casey Ransberger-2
On Sat, Dec 04, 2010 at 06:52:08PM -0800, Casey Ransberger wrote:
> O-Completion: +1 > > Yes oh yes please include O-Completion in 4.2. When we figure out what we're > doing about easy loading of "Community Supported Packages" we can think > about pulling it back out and making it an easily loadable package. IIUC, the O-Completion package is very actively maintained on SqueakSource and is already loadable in Squeak trunk. Making a fork of this in Squeak sounds to me like a Really Bad Idea. What would be a good idea is to *document* how to load O-Completion (probably in one of the welcome workspaces that appears when the image is first opened), so that a first time user can open Squeak 4.2 and easily see how to load this package. I just tried loading it myself, and it loads cleanly and works as advertised. What's not to like? :) Dave > > This is something that I can show developers who are new to Smalltalk that > they'll recognize and appreciate. I think it's a really big win. > > On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: > > > It's December, and time to consider freezing the 4.2 code base. If we > > can push any final enhancements and image documentation desired for > > 4.2 in over the next week, we can freeze officially on the 11th. Is > > this ok? Yes this sounds good to me. > > > > We should begin considering the release-notes. What is the easiest > > way to identify everything that's one into 4.2 since 4.1? > > > > Some of the items listed at the 4.2-release page > > (http://wiki.squeak.org/squeak/6160) are: > > > > - Integration of Cryptography > > - Documentation > > - Integration of O-Completion > > > > What do we all think about integration of O-Completion? Levente > > already did the work, it makes the IDE that much more useful and > > modern and, it can be turned off. Shall we include that? > > > > What What else do we need to consider for the 4.2 image release? > > |
Not maintaining it in the Trunk image is probably the right thing to do, but it should be included in the 4.2 release image.
-- Gesendet von meinem Palm Pre David T. Lewis <[hidden email]> schrieb am 05.12.2010 16:50: On Sat, Dec 04, 2010 at 06:52:08PM -0800, Casey Ransberger wrote: > O-Completion: +1 > > Yes oh yes please include O-Completion in 4.2. When we figure out what we're > doing about easy loading of "Community Supported Packages" we can think > about pulling it back out and making it an easily loadable package. IIUC, the O-Completion package is very actively maintained on SqueakSource and is already loadable in Squeak trunk. Making a fork of this in Squeak sounds to me like a Really Bad Idea. What would be a good idea is to *document* how to load O-Completion (probably in one of the welcome workspaces that appears when the image is first opened), so that a first time user can open Squeak 4.2 and easily see how to load this package. I just tried loading it myself, and it loads cleanly and works as advertised. What's not to like? :) Dave > > This is something that I can show developers who are new to Smalltalk that > they'll recognize and appreciate. I think it's a really big win. > > On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: > > > It's December, and time to consider freezing the 4.2 code base. If we > > can push any final enhancements and image documentation desired for > > 4.2 in over the next week, we can freeze officially on the 11th. Is > > this ok? Yes this sounds good to me. > > > > We should begin considering the release-notes. What is the easiest > > way to identify everything that's one into 4.2 since 4.1? > > > > Some of the items listed at the 4.2-release page > > (http://wiki.squeak.org/squeak/6160) are: > > > > - Integration of Cryptography > > - Documentation > > - Integration of O-Completion > > > > What do we all think about integration of O-Completion? Levente > > already did the work, it makes the IDE that much more useful and > > modern and, it can be turned off. Shall we include that? > > > > What What else do we need to consider for the 4.2 image release? > > |
In reply to this post by David T. Lewis
I agree with Dave. Keep everything that is loadable out of the base release. If desired, make another dev release with the good stuff already loaded. I am finding the 'Extending the System' menu selection, opening the Workspace with all the snippets for loading externally maintained packages, seems to be a step in the right direction. IMHO, trunk could be thought of as an easy way to try things out and work on them, but not the best way for longer term maintenance of packages that should remain loadable.
Ken G. Brown from my iPhone On 2010-12-05, at 8:49, "David T. Lewis" <[hidden email]> wrote: > On Sat, Dec 04, 2010 at 06:52:08PM -0800, Casey Ransberger wrote: >> O-Completion: +1 >> >> Yes oh yes please include O-Completion in 4.2. When we figure out what we're >> doing about easy loading of "Community Supported Packages" we can think >> about pulling it back out and making it an easily loadable package. > > IIUC, the O-Completion package is very actively maintained on SqueakSource > and is already loadable in Squeak trunk. Making a fork of this in Squeak > sounds to me like a Really Bad Idea. > > What would be a good idea is to *document* how to load O-Completion > (probably in one of the welcome workspaces that appears when the image > is first opened), so that a first time user can open Squeak 4.2 and > easily see how to load this package. I just tried loading it myself, > and it loads cleanly and works as advertised. What's not to like? :) > > Dave > >> >> This is something that I can show developers who are new to Smalltalk that >> they'll recognize and appreciate. I think it's a really big win. >> >> On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: >> >>> It's December, and time to consider freezing the 4.2 code base. If we >>> can push any final enhancements and image documentation desired for >>> 4.2 in over the next week, we can freeze officially on the 11th. Is >>> this ok? > > Yes this sounds good to me. > > >>> >>> We should begin considering the release-notes. What is the easiest >>> way to identify everything that's one into 4.2 since 4.1? >>> >>> Some of the items listed at the 4.2-release page >>> (http://wiki.squeak.org/squeak/6160) are: >>> >>> - Integration of Cryptography >>> - Documentation >>> - Integration of O-Completion >>> >>> What do we all think about integration of O-Completion? Levente >>> already did the work, it makes the IDE that much more useful and >>> modern and, it can be turned off. Shall we include that? >>> >>> What What else do we need to consider for the 4.2 image release? >>> > > |
The thing is, although the 'Extending the System' workspace helps, newbies do not know about it, and even when they find it, it's not clear what to load to get a good dev-image. All current IDEs and even most better text editors have some sort of auto-completion nowadays. Since Squeak presents itself to the newcomer as an integrated development environment, it should act that way, too, imho. Having a good one-click, out-of-the-box experience is crucial if we want new people to come and stick to Squeak - otherwise they'll simply go on and use Pharo.
Just my 2¢. -- Gesendet von meinem Palm Pre Ken G. Brown <[hidden email]> schrieb am 05.12.2010 18:06: I agree with Dave. Keep everything that is loadable out of the base release. If desired, make another dev release with the good stuff already loaded. I am finding the 'Extending the System' menu selection, opening the Workspace with all the snippets for loading externally maintained packages, seems to be a step in the right direction. IMHO, trunk could be thought of as an easy way to try things out and work on them, but not the best way for longer term maintenance of packages that should remain loadable. Ken G. Brown from my iPhone On 2010-12-05, at 8:49, "David T. Lewis" <[hidden email]> wrote: > On Sat, Dec 04, 2010 at 06:52:08PM -0800, Casey Ransberger wrote: >> O-Completion: +1 >> >> Yes oh yes please include O-Completion in 4.2. When we figure out what we're >> doing about easy loading of "Community Supported Packages" we can think >> about pulling it back out and making it an easily loadable package. > > IIUC, the O-Completion package is very actively maintained on SqueakSource > and is already loadable in Squeak trunk. Making a fork of this in Squeak > sounds to me like a Really Bad Idea. > > What would be a good idea is to *document* how to load O-Completion > (probably in one of the welcome workspaces that appears when the image > is first opened), so that a first time user can open Squeak 4.2 and > easily see how to load this package. I just tried loading it myself, > and it loads cleanly and works as advertised. What's not to like? :) > > Dave > >> >> This is something that I can show developers who are new to Smalltalk that >> they'll recognize and appreciate. I think it's a really big win. >> >> On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: >> >>> It's December, and time to consider freezing the 4.2 code base. If we >>> can push any final enhancements and image documentation desired for >>> 4.2 in over the next week, we can freeze officially on the 11th. Is >>> this ok? > > Yes this sounds good to me. > > >>> >>> We should begin considering the release-notes. What is the easiest >>> way to identify everything that's one into 4.2 since 4.1? >>> >>> Some of the items listed at the 4.2-release page >>> (http://wiki.squeak.org/squeak/6160) are: >>> >>> - Integration of Cryptography >>> - Documentation >>> - Integration of O-Completion >>> >>> What do we all think about integration of O-Completion? Levente >>> already did the work, it makes the IDE that much more useful and >>> modern and, it can be turned off. Shall we include that? >>> >>> What What else do we need to consider for the 4.2 image release? >>> > > |
In reply to this post by Tim Felgentreff
On 05.12.2010, at 16:59, Tim Felgentreff wrote:
> Not maintaining it in the Trunk image is probably the right thing to do, but it should be included in the 4.2 release image. +1 - Bert - -- Sent from my Zuse Z3 > -- Gesendet von meinem Palm Pre > > David T. Lewis <[hidden email]> schrieb am 05.12.2010 16:50: > > On Sat, Dec 04, 2010 at 06:52:08PM -0800, Casey Ransberger wrote: > > O-Completion: +1 > > > > Yes oh yes please include O-Completion in 4.2. When we figure out what we're > > doing about easy loading of "Community Supported Packages" we can think > > about pulling it back out and making it an easily loadable package. > > IIUC, the O-Completion package is very actively maintained on SqueakSource > and is already loadable in Squeak trunk. Making a fork of this in Squeak > sounds to me like a Really Bad Idea. > > What would be a good idea is to *document* how to load O-Completion > (probably in one of the welcome workspaces that appears when the image > is first opened), so that a first time user can open Squeak 4.2 and > easily see how to load this package. I just tried loading it myself, > and it loads cleanly and works as advertised. What's not to like? :) > > Dave > > > > > This is something that I can show developers who are new to Smalltalk that > > they'll recognize and appreciate. I think it's a really big win. > > > > On Sat, Dec 4, 2010 at 5:53 PM, Chris Muller <[hidden email]> wrote: > > > > > It's December, and time to consider freezing the 4.2 code base. If we > > > can push any final enhancements and image documentation desired for > > > 4.2 in over the next week, we can freeze officially on the 11th. Is > > > this ok? > > yle\x3D\"width:16px;height:16px;margin-top:.2em;border:none;\"/\x3E \x3C/a\x3E \x3Ca href\x3D\"http://digg.com/submit?phase\x3D2&url\x3Dhttps%3A%2F%2Fforum.world.st%2F4-2-code-freeze-tp3072962p3073471.html&title\x3DRe%3A+4.2+code+freeze\" title\x3D\"Digg\" target\x3D\"_blank\" ignore\x3D\"y\"\x3E \x3Cimg src\x3D\"/images/social/digg.png\" style\x3D\"width:16px;height:16px;margin-top:.2em;border:none;\"/\x3E \x3C/a\x3E','white-space:nowrap'); dropdown.build('dd_postdropdown3073471'); dropdown.loadOnClick('/template/NamlServlet.jtp?macro=post_dropdown_later&node=3073471&_=' + Math.floor(Math.random()*999999)); Re: 4.2 code freeze
Re: AW: Re: [squeak-dev] 4.2 code freeze
Re: AW: Re: [squeak-dev] 4.2 code freeze
«
Return to Squeak - Dev
|
1 view|%1 views
|