February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [SPAM] text selection feature

by Alain Plantec

Hi Micheal it is called secondary selection. there is also the selection bar and the find replace selection. You can disallow them individually or change the colors Cheers Alain Le 14/02/2011 22:52, Sven Van Caekenberghe a Ã©crit : > Micheal, > > On 14 Feb 2011, at 22:40, Michael Roberts wrote: > >> Hi, there is a recent (I don't know how old) feature where text areas >> now highlight the selected text in all parts of the same text pane. >> Does this feature have a name and a setting to control it? >> >> thanks, >> Mike > Try Settings>> Editing>> Use the secondary selection > There is also Settings>> Editing>> Show the colored bar on the current line > > HTH, > > Sven > > >

Feb. 14, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Igor Stasenko

On 14 February 2011 23:33, Adrien BARREAU <abarreau.dev(a)live.fr> wrote: > Hi, > > I'm sorry to interrupt that discussion, but I read all the messages about > that subject since you started to discuss it and I really would like to > understand a thing: > Why does the case structure seem to be so bad in Smalltalk? > > I hope some of you could explain me :) > Because you can do such kind of dispatching using messages. > Adrien. > -- Best regards, Igor Stasenko AKA sig.

Feb. 14, 2011

[Pharo-project] Issue 3704 in pharo: remove FakeClassPool adopt: and its senders

by pharo＠googlecode.com

Status: Accepted Owner: nicolas....(a)gmail.com Labels: Difficulty-Easy New issue 3704 by nicolas....(a)gmail.com: remove FakeClassPool adopt: and its senders http://code.google.com/p/pharo/issues/detail?id=3704 As developped on following link, this message is useless http://article.gmane.org/gmane.comp.lang.smalltalk.squeak.general/154929 The job is easy: if you see a sender of FakeClassPool adopt: then just remove it. This is part of a larger plan, remove FakeClassPool itself since it's sole use is to flash a TextEditor when self is returned from a nil doItReceiver. See also http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-February/157518… for a possible Comment Of The Day ;)

Feb. 14, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #61 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 yes it's normal, for two reasons: - a method that should be removed is still here :s - SHWorkspace overrides a lot of methods and break the styling (ironic no ^^) I've wrote a cs for the first point, and committed a new version of SHWorkspace emptied for the second. I've also create a minimal cs that makes SHWorkspace work, but it's really a patch. So with the last version of SHWorkspace, it should work now ^^ (maybe we should move SHWorkspace in Deprecated ?) Attachments: FixWorkspaceAgain.1.cs 155 bytes FixSHWorkspace.1.cs 160 bytes

Feb. 14, 2011

Re: [Pharo-project] Loading Seaside into Pharo 1.2 core

by Dale Henrichs

Hello Mike, I am presently working on Seaside 3.0.4 which will correctly load into Pharo1.2, but you should be aware that there a number of test failures will remain and that (speaking unofficialy), Seaside3.0 isn't yet supported on Pharo1.2... To answer your general question you don't have to specify individual packages by hand. The following load expression will load the 'default' group for a project: (ConfigurationOfSeaside30 project version: '3.0.3') load. By _default_ the 'default' group is the all of the packages and project references defined in a configuration. A developer may explicitly define the packages/project refs that are included in the 'default' group. A developer may also define groups that are specific to the project. A common group name is 'Core'. The 'Core' group typically defines the basic unit that the developers expect you to load. To find out which groups are defined in a project, you can execute the following expression: (ConfigurationOfSeaside30 project version: '3.0.3') groups collect: [:each | each name ] You can name a group in a load expression along with package names. Here are the list of groups for Seaside 3.0: - 'Base' - 'Base Tests' - 'Development' - 'Development Tests' - 'Core' - 'Tests' - 'OneClick' You will note that there aren't a lot of options for partitioning a Seaside3.0 load: - 'Base' is the absolute minimum set of packages that should be loaded to get expected Seaside3.0 functionality - 'Development' adds in the Seaside30 development tools. It should be noted that it is recommended that the Seaside30 development tools be loaded in a production image, because the tools are considered essential - 'Core' includes "optional" packages like javascript support, adaptors, etc. - 'OneClick' is the subset of 'Core' that is shipped in the one-click image It is recommended that you load the 'Core' group, if you want to exclude the tests and load the 'default' group (i.e., everything) if you want to include the tests. Here's the list of packages in the 'Core' group: - 'Comet-Core' 'Seaside-Examples' 'Scriptaculous-Core' 'Seaside-Tools-Core' 'Seaside-Tools-OmniBrowser' 'Seaside-HTML5' 'Seaside-Environment' 'Seaside-Core' 'Seaside-Adaptors-Swazoo' 'Seaside-Widgets' 'Seaside-Flow' 'Seaside-InternetExplorer' 'Javascript-Core' 'JQuery-UI' 'Seaside-Adaptors-Comanche' 'Seaside-Development' 'Seaside-Component' 'Seaside-Canvas' 'RSS-Examples' 'RSS-Core' 'Scriptaculous-Components' 'JQuery-Core' 'Seaside-FileSystem' 'Seaside-Session' 'Seaside-Email' 'Seaside-Tools-Web' 'Comet-Examples' 'Seaside-RenderLoop' 'Seaside-Welcome' 'Prototype-Core' 'Seaside-Swazoo' 'Seaside-Slime' You must choose at least one adaptor (from the 'Core; group), so in theory the absolute minimum loadable unit for Seaside30 would be: (ConfigurationOfSeaside30 project version: '3.0.3') load: #('Base' 'Seaside-Adaptors-Comanche'). Note that there are no pre-defined components registered in this case, so even if you manually start WAKom: WAKom startOn: 8080 the only page you can hit is the files page: http://localhost:8080/files You could load the example packages: (ConfigurationOfSeaside30 project version: '3.0.3') load: #('Seaside-Examples'). to have a few more pages to hit: http://localhost:8080/examples/examplebrowser but without the familiar development tools you might not have an enjoyable experience. You can add in the development tools with the following expression: (ConfigurationOfSeaside30 project version: '3.0.3') load: #('Development'). Only then will you see the familiar Dispatcher page when you hit: http://localhost:8080/ At this point in time, the only things that you won't have loaded (because of package dependencies) are: - Comet - Swazoo - RSS support - javascript support - HTML5 support - EMail - Welcome page To add the remaining pieces you'd now have to list the individual packages ... Does this help? Dale On 02/14/2011 12:42 PM, Michael Roberts wrote: > Hi, i want to load Seaside into Pharo 1.2 core. I have followed > various threads talking about doing this with metacello, but beyond > the simple tutorial i have worked through I am lost. I don't want to > have to specify each package by hand. > > I can do this... > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > (ConfigurationOfSeaside30 project version: '3.0.3') > load: { 'Grease Core'. 'Grease Core Tests'. 'Swazoo2'} > > I can do this... > > (ConfigurationOfSeaside30 project version: '3.0.3') > load: { 'Javascript-Core'} > > but how do I load all the stuff declared as #common, or some of the > other parts, in the spec? I don't want to do this in a Pharo image. > > If I do something like load: { #common } or load: { #pharo } then > this was clearly a stupid request and I get 100s of errors pop up from > some decompiler issue and my image dies. If someone can help or just > point me at the part of the docs I should be reading that would be > great. > > thanks, > Mike >

Feb. 14, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Adrien BARREAU

Hi, I'm sorry to interrupt that discussion, but I read all the messages about that subject since you started to discuss it and I really would like to understand a thing: Why does the case structure seem to be so bad in Smalltalk? I hope some of you could explain me :) Adrien.

Feb. 14, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Stephen Taylor

Igor Stasenko wrote: > On 14 February 2011 01:32, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> That's where I typically use a dictionary. > Indeed. Yes - sensible answer from Wilhelm Schwab. >> You didn't answer the question though. > Because it sounds rhetoric to me. > How to deal with randomly put integers coming from outer source? > If you're a software engineer, you should know it. :) Indeed. Case construct is sometimes an appropriate way. > - first try to avoid dealing with them. So if you can control the > protocol, use other ways of encoding actions/data. Yes, but the point is that one does not always have full control of ones environment. Of course it would be nice it to have sensible input data. It would be nice to have a pony with wings too. > - organize these numbers (using dictionary or whatever), so they > won't look like a random noise > for people who first looking at your code. Put them into single place > with documentation etc. I do like the dictionary approach and sometimes do that. Other times I wonder if I've made the world that much of a better place by loading the logic into a dictionary rather than leaving it out in the code where anyone can see it. It depends on the number of symbols. I'm going to leave it here, as I don't want to find myself in the position of the last and loudest advocate of case statements. I don't think they're that good an idea in most circumstances, but I do think they're reasonable enough sometimes. Steve

Feb. 14, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Eliot Miranda

On Mon, Feb 14, 2011 at 1:58 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 14 February 2011 22:38, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > > > On Fri, Feb 11, 2011 at 1:43 PM, stephane ducasse < > stephane.ducasse(a)free.fr> > > wrote: > >> > >> Hi guys > >> > >> let us do another pass at cleaning and realigning the system. > >> Could we agree to deprecate caseOf: and caseOf:otherwise:? > >> it will simply the compiler, decompiler and also we do not need that at > >> all. > >> > >> | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. #b caseOf: > z > >> > >> => > >> "| z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. > >> z detect: [:each | each key value = #b] " > >> > >> there is one user which I fixing right now. > > > > please don't. It is used in many places in Cog and would be extremely > > uncomfortable to live without. > > > > Yes, i mentioned that too.. > > It is strange however that the only 'senders' of these messages in VMMaker > is: > > TMethod>>prepareMethodIn: aCodeGen > ... > (#(caseOf: #caseOf:otherwise:) > includes: node selector) ifTrue: > [replacements at: node put: > (self buildSwitchStmt: node)]]]. > > ahh... probably it means that system navigation can't detect them , > because they are 'inlined' and there is no references to > these selectors from methods where it used. That's right. The compiler inlines caseOf: into a series of comparisons and jumps. One way to find some uses (those without an explicit otherwise clause) is to look for senders of #caseError. > But if you look at code > there, VMMaker won't stop working if we remove compiler support of > these guys, because it just reacts on a message-send level by checking > if it a special selector, so it will be translated to switch statement > in C. > But we /will/ lose the ability to load code including it. This clearly isn't any kind of solution. > > Oh.. or perhaps because code using #dispatchOn:in: :) cheers Eliot > >> > >> Stef > >> > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Feb. 14, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Igor Stasenko

On 14 February 2011 22:38, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Fri, Feb 11, 2011 at 1:43 PM, stephane ducasse <stephane.ducasse(a)free.fr> > wrote: >> >> Hi guys >> >> let us do another pass at cleaning and realigning the system. >> Could we agree to deprecate caseOf: and caseOf:otherwise:? >> it will simply the compiler, decompiler and also we do not need that at >> all. >> >> | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. #b caseOf: z >> >> => >> "| z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. >> z detect: [:each | each key value = #b] " >> >> there is one user which I fixing right now. > > please don't. Â It is used in many places in Cog and would be extremely > uncomfortable to live without. > Yes, i mentioned that too.. It is strange however that the only 'senders' of these messages in VMMaker is: TMethod>>prepareMethodIn: aCodeGen ... (#(caseOf: #caseOf:otherwise:) includes: node selector) ifTrue: [replacements at: node put: (self buildSwitchStmt: node)]]]. ahh... probably it means that system navigation can't detect them , because they are 'inlined' and there is no references to these selectors from methods where it used. But if you look at code there, VMMaker won't stop working if we remove compiler support of these guys, because it just reacts on a message-send level by checking if it a special selector, so it will be translated to switch statement in C. Oh.. or perhaps because code using #dispatchOn:in: :) >> >> Stef >> > > -- Best regards, Igor Stasenko AKA sig.

Feb. 14, 2011

Re: [Pharo-project] [SPAM] text selection feature

by Sven Van Caekenberghe

Micheal, On 14 Feb 2011, at 22:40, Michael Roberts wrote: > Hi, there is a recent (I don't know how old) feature where text areas > now highlight the selected text in all parts of the same text pane. > Does this feature have a name and a setting to control it? > > thanks, > Mike Try Settings >> Editing >> Use the secondary selection There is also Settings >> Editing >> Show the colored bar on the current line HTH, Sven

Feb. 14, 2011