May 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Preferences -> Settings: #browsing group
by Alain Plantec May 11, 2009

May 11, 2009

Hi all, Below are listed all old preferences of the #browsing group. For each one, its name is shown with the comment that we can read from the preference browser. Then I've added and 'action' (remove or keep it). If kept, I've also added a possible new setting declaration. Could you read it carefully and give your point of view about the desired action. Thanks Alain ------------------------------------------------ ------------------------------------------------ alternativeBrowseIt : "if true cmd-b offers a list of class names matching selection" action: remove it because this feature is always desired ----------------------------------- annotationPanes: "if true, a thin horizontal pane is used in browsers" action: don't know because the annotation pane seems not correctly updated by browsers. However, it is correctly updated by MessageSet. if kept: CodeHolder class>>annotationPane <setting> ^ AnnotationPane ifNil: [AnnotationPane := (SettingManager newSetting: 'Annotation pane') default: false; parent: #browsing; description: 'If true, a thin horizontal annotation pane is used in browsers. When a method is selected, then the pane is updated with useful informations about the method'] ----------------------------------- balloonHelpInMessageLists: "If true, then message-list browsers in Morphic will show balloon help, consisting of the first comment of the method or of a superclass" action: would remove it. didn't succeed in making it work. Serves as a value for a Morph property #balloonTextSelectorForSubMorphs. This property is used by PluggableListMorph>>list: which has following comment: "lex doesn't think this is used any longer, but is not yet brave enough to remove it. It should be removed eventually" ------------------------------------ browseWithPrettyPrint "If true, browsers will automatically format their contents" action: keep it ? CodeHolder class>>browseWithPrettyPrint <setting> ^BrowseWithPrettyPrint ifNil: [BrowseWithPrettyPrint := (SettingManager newSetting: 'Pretty print') default: false; parent: #browsing; description: 'If true, browsers will automatically format their contents'] question: do we really need style for code file out ? (problem: used by Text>>askIfAddStyle: priorMethod req: requestor send by ClassDescription and TraitDescription) ->would introduce a dependence from Text to CodeHolder). ------------------------------------ colorWhenPrettyPrinting:"If true, then when browseWithPrettyPrint is in effect, the pretty-printing will be presented in color" action: remove it ? No effect anymore on pharo-core browsers ------------------------------------ decorateBrowserButtons: "Governs whether certain buttons, such as the Inheritance button, should bear colors that provide user feedback on their applicability" action: maybe remove it ? such a feedback is now provided by OB-browser with its icon set. ------------------------------------ diffsInChangeList: "If true, changeList browsers and Versions browsers will open up by default showing diffs, i.e. revealing the differences between successive versions or between the in-memory code and the code on disk" action: keep it ? CodeHolder class>>showDifferencesInChangeList <setting> ^ ShowDifferencesInChangeList ifNil: [ShowDifferencesInChangeList := (SettingManager newSetting: 'Show differences in ChangeList') default: true; parent: #browsing; description: 'If true, changeList browsers and Versions browsers will open up by default showing diffs, i.e. revealing the differences between successive versions or between the in-memory code and the code on disk'] ------------------------------------ diffsWithPrettyPrint: "if true, displays of source code differences will be pretty-printed first" action: keep it ? CodeHolder class>>prettyPrintDifferences <setting> ^ PrettyPrintDifferences ifNil: [PrettyPrintDifferences := (SettingManager newSetting: 'Pretty print differences') default: false; parent: #browsing; description: 'if true, displays of source code differences will be pretty-printed first'] ------------------------------------ optionalButtons: "If true, then optional buttons will be used in certain standard tools, including browsers, message lists, fileLists, changeLists, and debuggers" action: remove it ? because it is always used ------------------------------------ smartUpdating: "If true, then morphic tools such as browsers and inspectors will keep their contents up to date automatically, so that if something changes anywhere, the change will be reflected everywhere." action: keep it ? true by default, when do we set this to false ? CodeHolder class>>smartUpdating <setting> ^ SmartUpdating ifNil: [SmartUpdating := (SettingManager newSetting: 'Smart updating') default: true; parent: #browsing; description: 'If true, then morphic tools such as browsers and inspectors will keep their contents up to date automatically, so that if something changes anywhere, the change will be reflected everywhere.'] ------------------------------------ useNewDiffToolsForMC: "When enabled the Polymorph diff tools will be used with Monticello. When diabled, the original tools are used." action: remove it ? Should it be a setting ? What is wrong with the new diff tool ? ------------------------------------

2 3

[Pharo-project] Questions: PDFs
by Stephan Eggermont May 11, 2009

May 11, 2009

Stefan Schmiedl wrote: >> http://www.seaside.st/documentation/pdfs > Is it just me or are the LaTeX samples lacking backslashes? > Thanks for a valuable overview, You're right, they should have backslashes. Probably a conversion problem. Andreas Brodbeck writes about another solution: http://andreas.mindclue.ch/blog/seaside+project+live Stephan

2 1

[Pharo-project] Ideas for solving SLOW MultiByteFileStream nextPutAll:
by Nicolas Cellier May 10, 2009

May 10, 2009

Well, this is latin1-centric, but could speed-up a majority of us, since most code is written in English. The idea is to use Andreas fast conversions ByteString>>#squeakToUtf8 ... However creating an intermediary Stream then an intermediary String is not necessary... So we'll have to replace this with dispatching techniques. Moreover, the technique can be generalized to other encodings. More more over, the lineEndConventions can be handled by the very same trick. To achieve this, we install a latin1Map and latin1Encodings as class instance variables in TextConverter to generalize Andreas' squeakToUtf8 trick. Then we copy these in instance variables. This is to enable lineEndConventions mapping. Then we care to #installLineEndConventionInConverter in MultiByteFileStream to initialize TextConverter variables. Then we use following dispatching: MultiByteFileStream nextPutAll: -> TextConverter nextPutAll: And use a hack for ByteString in TextConverter nextPutAll: (dispatching on String would be overkill by now). To measure how it can enhance things, I put a hack in Debugger class>>#openOn:context:label:contents:fullView: Preferences logDebuggerStackToFile ifTrue: [MessageTally spyOn: [Smalltalk logError: title inContext: context to: 'SqueakDebug.log']] Then did a 0/0 FasterLatin1Conversion reduce tallies from - 11452 tallies, 11586 msec. to - 3625 tallies, 3718 msec. Still a little bit long for a Debugger to open, but already better. Nicolas

2 1

[Pharo-project] The Fame code generator does not generate "container" annotation.
by FranÃ§ois Tanguy May 10, 2009

May 10, 2009

Hello all, The Fame code generator does not generate "container" annotation. ex : if in a MSE file (FM3.Property (id: 10051) (name ''superEquipment'') (type (ref: 5)) (container true) (opposite (ref: 10061)) ) the code generated looks like this : superEquipment <MSEProperty: #superEquipment type: #SCAbstractEquipment opposite: #subEquipments> ^superEquipment should not it be like the following ? superEquipment <MSEProperty: #superEquipment type: #SCAbstractEquipment opposite: #subEquipments> <container> ^superEquipment It is pretty important because it allows the traversal of a model based on the containment of objects. FranÃ§ois

1 0

[Pharo-project] Submitting changes to upstream repositories
by Damien Pollet May 9, 2009

May 9, 2009

Hi, There are recent versions of VB-Regex in the images, but they are not at http://www.squeaksource.com/Regex I will copy them but that's just on of those things that make people say Pharo is not playing nice with other forksâ¦ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

4 10

[Pharo-project] Mass upload to squeaksource ?
by Damien Pollet May 9, 2009

May 9, 2009

Is there a simple way to upload many MC snapshots at once to a SqueakSource project ? One thing would be to enable multiple selection for the copy command in the MC browser, but since I suppose this is a simple HTML upload, maybe someone has a simple script to do that already ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

2 1

[Pharo-project] Questions: PDFs
by Stephan Eggermont May 8, 2009

May 8, 2009

On the seaside site, there is an overview I collected with Lukas last ESUG http://www.seaside.st/documentation/pdfs Stephan

2 1

[Pharo-project] macintosh carbon vm 4.1.1b2
by John M McIntosh May 8, 2009

May 8, 2009

I've pushed out a macintosh carbon closure VM 4.1.1b2 for testing. It can be found via links on http://www.smalltalkconsulting.com/squeak.html It includes the following fixes. 4.1.1b2 Window Title now accepts UTF8 strings Build with VMMaker-dtl-121 includes fix for closure vm crash http://bugs.squeak.org/view.php?id=7349 primitiveDisableFileAccess primitiveDisableImageWrite primitiveDisableSocketAccess primitiveHasSocketAccess includes fix for Reference Mantis 6987: signed32BitValueOf:, signed64BitValueOf: etc. broken a fix for #signed32BitIntegerFor: on 64-bit images. includes fix fortwo methods with assignment to block temp arguments, reported on vm-dev list <http://lists.squeakfoundation.org/pipermail/vm-dev/2009-April/002607.html > 4.1.1b2 distributed only for testing to a few people. 4.1.0b1 UTF-8 on clipboard primitives via code from qwaq UTF-8 for file names compile SDK for ppc is 10.4.x now, versus 10.3.x Unknown if clipboard works on 10.2 or 10.3 ppc systems? -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

2 1

[Pharo-project] Love that background image!
by stepken May 7, 2009

May 7, 2009

I love that one as background image for Pharo: http://images.apple.com/ipodshuffle/images/overview_hero_20090311.jpg cheers, Guido Stepken

1 0

[Pharo-project] [SqueakDBX] Can't parse date
by Hilaire Fernandes May 7, 2009

May 7, 2009

Hello, I have noted this problem, see attached log -- http://blog.ofset.org/hilaire

2 11