April 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] ToolBuilder / Squeak 4.1 changes
by Andreas Raab April 23, 2010

April 23, 2010

Hi - As a first step for merging, here are the changes that are in Squeak 4.1 relative to the latest versions in the repository at http://www.squeaksource.com/ToolBuilder. The following is a pretty much complete set of changes that happened since (there are a few more minor edits but they're pretty much irrelevant for our purposes here): Package: ToolBuilder-Kernel --------------------------- - PluggableAlternateMultiSelectionListSpec This class was added as an 'alternative' multi-selection list (used only by MessageTrace; perhaps Chris can comment) - PluggableCodePaneSpec This class was added to distinguish code-editing panes from others. It implies syntax highlighting any other goodies you'd like to see in code. - PluggableListSpec * doubleClick - selector to handle double click events * keystrokePreview - selector to handle key events for filtering - PluggableTextSpec * askBeforeDiscardingEdits - whether to ask before discarding changes - PluggableWindowSpec * isDialog - if the window should behave like a dialog - UIManager: * chooseFont:for:setSelector:getSelector: - font selector dialog * confirm:label: - confirm dialog w/ both message text and label * request:initialAnswer:centerAt: - positioned #request: message All of these changes are pretty straightforward and should not cause much of an issue. Package: ToolBuilder-Morphic ---------------------------- - ListChooser This class was added to implement the chooser dialog in Morphic. - PluggableDialogWindow This class was added for dialog windows in Cobalt. - PluggableTextMorphPlus: * styler - PTMPlus has been extended to support Shout directly. - MorphicUIManager: * chooseFont: - usage of FontChooser * chooseFrom: - usage of ListChooser * confirm: - usage of UserDialogBoxMorph * informUserDuring: - usage of SystemProgressMorph There is obviously more of an issue here. Various classes have only emerged in Squeak 4.1 and won't exist in Pharo. Not sure what to do here, because it's as much of an issue between 3.x and 4.1. I'll review the Pharo changes next. Cheers, - Andreas

3 2

[Pharo-project] [update 1.1] #11320
by StÃ©phane Ducasse April 23, 2010

April 23, 2010

11320 ----- - Issue 2295: AllocationTests - Issue 2346: ArrayTest>>testSorted is broken - Issue 2318: Smalltalk windowSystemName - Issue 2302: optional version identification primitives from Squeak Stef

1 0

[Pharo-project] Fix 2329 - Default MC Directory Setting
by Sean P. DeNigris April 23, 2010

April 23, 2010

In Inbox. http://code.google.com/p/pharo/issues/detail?id=2329. Details: Michael Roberts-2 wrote: > > I appreciate I hijacked this thread somewhat.... > That's it - I'm pissed and I'm taking my damn thread back ;-) Sean P. DeNigris wrote: > > http://code.google.com/p/pharo/issues/detail?id=2329 > > Pharo image: Pharo 1.0 > > In Monticello Browser, when I click "+Repository" and select "directory," > I'd love to be taken right to the directory where I keep my local > repositories, instead of having to click to the same place over and over. > Okay, now that we're back on track... StÃ©phane Ducasse wrote: > > it would be good to be able to > either choose to have one local cache on the side of the image > or one shared among image - this implies a way to store and set it up > => probably a class variable + a setting in 1.1 > Steph, I followed your suggestion and implemented it as a class var + settings. I had to add the capability to have directory-type settings (which was very similar to the existing file type settings, predictably). Summary: * Added ability to System-Settings to have directory-based settings * Added defaultDirectoryName setting to Settings-Monticello * Added feature to Monticello to remember parent directory where user likes to keep local repository directories and start directory-choosing dialogs there. * Tested (by hand) in PharoCore1.1ALPHA Latest update: #11312 Sean -- View this message in context: http://n4.nabble.com/Fix-2329-Default-MC-Directory-Setting-tp2019559p201955… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 7

[Pharo-project] [update 1.1] #11318
by StÃ©phane Ducasse April 23, 2010

April 23, 2010

11318 ----- - Issue 2329: FEATURE: User chooses preferred location for MC directory repositories. Thanks Sean. this is cool extension! * Added ability to System-Settings to have directory-based settings * Added defaultDirectoryName setting to Settings-Monticello * Added feature to Monticello to remember parent directory where user likes to keep local repository directories and start directory-choosing dialogs there. * Tested (by hand) in PharoCore1.1ALPHA Latest update: #11312 - Issue 2321: #sansPeriodSuffix doesn t match without convention of other methods Stef, Cyrille and others :)

1 0

Re: [Pharo-project] [squeak-dev] ToolBuilder / Pharo 1.0 changes
by Igor Stasenko April 23, 2010

April 23, 2010

On 23 April 2010 13:57, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: > Ok let us know. > > Your goal is to have ToolBuilder shared between Pharo and Squeak? > We should pay attention because we want to be able not to be backwards compatible but we can try. > Well, i think that if we keep this part shared, then developers will have at least a basis for building their UIs and do not bother with using different ports, if they want to support Pharo and Squeak both in their projects. > Stef > > On Apr 23, 2010, at 6:50 AM, Andreas Raab wrote: > >> Hi - >> >> Here are the changes between the latest ToolBuilder from http://www.squeaksource.com/ToolBuilder vs. Pharo 1.0 (again there are additional but fairly minor edits involved): >> >> Package ToolBuilder-Kernel >> -------------------------- >> - ToolBuilderTests >> Removed. >> >> - UIManager >> Â * fontFromUser: >> Â -- >> Â * chooseFrom:lines:message: >> Â * chooseFrom:lines:message:title: >> Â * chooseFrom:message: >> Â * chooseFrom:message:title: >> Â * chooseFrom:values:lines:message: >> Â * chooseFrom:values:lines:message:title: >> Â * chooseFrom:values:message: >> Â * chooseFrom:values:message:title: >> Â -- >> Â * createPageTestWorkspace >> Â * checkForNewDisplaySize >> Â * composeFormFor: >> Â * grafPort >> Â * interactiveParserFor: >> Â * newDisplayDepthNoRestore: >> Â * onDebug:context:title:full: >> Â * onPrimitiveError: >> Â * onEventSensorStartup: >> Â * onSnapshot >> Â * restoreDisplay >> Â * restoreDisplayAfter: >> >> Two sets of issues that we should discuss: If you care about unloading the (very small) set of tests we should move those into a separate package, which is easy enough. >> >> Secondly, UIManager. It seems there have been three types of additions: >> >> 1) 'Genuine' user requests like fontFromUser:. Since we added a similar protocol in Squeak we should work out which protocol is preferable and use it (or even both). >> >> 2) Polymorph extensions. Assuming Gary agrees, we should move those into UIManager but I'll point out that a quick look at senders didn't reveal any users? All the references were between these methods no apparent external callers. Are these used in other packages? >> >> 3) Methods that are not about user requests (everything from creatPageTestWorkspace through restoreDisplayAfter:). I don't really like those very much (after all UIManager is all about asking users for information); is there really no better place in Pharo to put these? I can kind of see why one would stick some of those into UIManager if there is absolutely no other place but ... is there? >> >> Package ToolBuilder-Morphic >> --------------------------- >> - MorphicToolBuilderTests >> Removed. >> >> - MorphicUIManager >> Â * isActiveManager - presumes Morphic-only >> Â * (all the code for the new methods in UIManager) >> >> Not much new stuff here. >> >> Package Polymorph-ToolBuilder-Morphic >> ------------------------------------- >> * PSPluggableListSpec >> Adds icon and double click selector to the list spec. >> >> This should be folded all the way up into PluggableListSpec. The lack of these is a real oversight. >> >> That's about it for the Pharo changes. Except from the methods in UIManager that don't really belong there, there's little to worry about. >> >> The next thing I'll do is post some recommendations of how I think we can move this forward. I'll have to think about this a little though. >> >> Cheers, >> Â - Andreas >> > > > -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] New company selling Smalltalk products
by Nicolas Petton April 23, 2010

April 23, 2010

Hi, SÃ©bastien Audier and I recently started a company named ObjectFusion selling Smalltalk web applications, using Iliad web framework. Our first product, Odyssey CMS, is a web content managment system. The system is available in english and french. It is designed to be extensible, flexible and easy to use. Instead of using a formatting syntax or a WYSIWYG text editor, our CMS is using inline editing, inspired by CMSBox. Every part of the page can be arranged and edited in place, and is automatically adapted to the design of the website. Odyssey also features mutliple undo/redo for all actions on a page. Any mistake can be cancelled at any time. When editing a page, it is also possible to copy/cut/paste any part. We offer several plans & pricing with commercial hosting. If you want to learn more about services we offer, you can visit our website (in french) : http://www.objectfusion.fr Cheers, Nicolas Petton

4 3

[Pharo-project] Fix 2344 - OmniBrowser using depreciated asSortedArray
by Sean P. DeNigris April 23, 2010

April 23, 2010

In inbox. http://code.google.com/p/pharo/issues/detail?id=2344 Sean DeNigris -- View this message in context: http://forum.world.st/Fix-2344-OmniBrowser-using-depreciated-asSortedArray-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] ToolBuilder / Pharo 1.0 changes
by Andreas Raab April 23, 2010

April 23, 2010

Hi - Here are the changes between the latest ToolBuilder from http://www.squeaksource.com/ToolBuilder vs. Pharo 1.0 (again there are additional but fairly minor edits involved): Package ToolBuilder-Kernel -------------------------- - ToolBuilderTests Removed. - UIManager * fontFromUser: -- * chooseFrom:lines:message: * chooseFrom:lines:message:title: * chooseFrom:message: * chooseFrom:message:title: * chooseFrom:values:lines:message: * chooseFrom:values:lines:message:title: * chooseFrom:values:message: * chooseFrom:values:message:title: -- * createPageTestWorkspace * checkForNewDisplaySize * composeFormFor: * grafPort * interactiveParserFor: * newDisplayDepthNoRestore: * onDebug:context:title:full: * onPrimitiveError: * onEventSensorStartup: * onSnapshot * restoreDisplay * restoreDisplayAfter: Two sets of issues that we should discuss: If you care about unloading the (very small) set of tests we should move those into a separate package, which is easy enough. Secondly, UIManager. It seems there have been three types of additions: 1) 'Genuine' user requests like fontFromUser:. Since we added a similar protocol in Squeak we should work out which protocol is preferable and use it (or even both). 2) Polymorph extensions. Assuming Gary agrees, we should move those into UIManager but I'll point out that a quick look at senders didn't reveal any users? All the references were between these methods no apparent external callers. Are these used in other packages? 3) Methods that are not about user requests (everything from creatPageTestWorkspace through restoreDisplayAfter:). I don't really like those very much (after all UIManager is all about asking users for information); is there really no better place in Pharo to put these? I can kind of see why one would stick some of those into UIManager if there is absolutely no other place but ... is there? Package ToolBuilder-Morphic --------------------------- - MorphicToolBuilderTests Removed. - MorphicUIManager * isActiveManager - presumes Morphic-only * (all the code for the new methods in UIManager) Not much new stuff here. Package Polymorph-ToolBuilder-Morphic ------------------------------------- * PSPluggableListSpec Adds icon and double click selector to the list spec. This should be folded all the way up into PluggableListSpec. The lack of these is a real oversight. That's about it for the Pharo changes. Except from the methods in UIManager that don't really belong there, there's little to worry about. The next thing I'll do is post some recommendations of how I think we can move this forward. I'll have to think about this a little though. Cheers, - Andreas

1 0

Re: [Pharo-project] [Question] ToolBuilder in Squeak 4.1 and Pharo 1.0 compatible?
by Andreas Raab April 22, 2010

April 22, 2010

On 4/21/2010 4:32 AM, Hannes Hirzel wrote: > A question: Art the ToolBuilder in Squeak 4.1 and Pharo 1.0 the same? > Or if there is a difference what is the impact of it? > > Or put the question in another way. If I code an UI using the > ToolBuilder in Squeak 4.1 will it run in Pharo? They are mostly the same but not identical. If there is interest in the Pharo community we should merge the versions upstream in http://www.squeaksource.com/ToolBuilder.html (contact me if you're interested). Cheers, - Andreas

3 7

April 22, 2010

Hi pharo Gofer new squeaksource: 'HelpSystem'; version: 'HelpSystem-Core-tbn.35'; load and enjoy HelpBrowser openOn: SystemReference HelpBrowser openOn: (SystemReference forClass: Integer) HelpBrowser openOn: (SystemReference hierarchyFor: Integer) HelpBrowser openOn: (SystemReference hierarchyWithMethodsFor: Integer) with some tweaks it can be realllllly cool. Stef

2 2