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

Re: [Pharo-project] [Seaside] a note system for pharo?

by Sean P. DeNigris

I just revisited this. If you use a [fill in favorite word for pragma/annotation here], you can have the same effect as revisit: or flag: (or as many custom note types as you want) without adding any methods to Object. Sean -- View this message in context: http://forum.world.st/Re-Seaside-a-note-system-for-pharo-tp1751477p2068053.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 27, 2010

Re: [Pharo-project] [Moose-dev] Re: Adding accessing methods

by Alexandre Bergel

Added Behavior>>numberOfInstanceVariables ClassDescription>>numberOfLinesOfCode ClassDescription>>numberOfMethods fixed some typos in the comments. Tests are also proposed #2366 In the inbox: SLICE-FewMetricsDefinedOnClasses-Alexandre_Bergel.1 Cheers, Alexandre On 25 Apr 2010, at 03:08, StÃ©phane Ducasse wrote: > I thought that CompiledMethod has something because marcus use it to > compute some stats now > rationalizing would be good. > > so propose something on pharo and > numberOfInstanceVariables would be better > > On Apr 24, 2010, at 10:53 PM, Alexandre Bergel wrote: > >>>> I would like to have numberOfMethods, >>>> , numberOfAttributes defined in Behavior. >>> >>> the problems is that numberOfAttributes is not the right vocabulary. >>> Did you check for the other ones if there is not already an >>> equivalent? >> >> Behavior>>instSize returns the number of named variables, tacking >> class inheritance into account. >> ClassDescription>>numberOfMethods returns the number of local (ie >> not defined in a trait) methods >> >> Behavior has nothing close to FAMIXClass>>numberOfLinesOfCode. >> >> Cheers, >> Alexandre >> >> >>> >>> Stef >>> >>>> Stef, does this make sense? Shall I produce a slice and put it >>>> PharoInbox? >>>> >>>> Alexandre >>>> >>>> >>>>> >>>>> Stef >>>>> On Apr 23, 2010, at 8:05 PM, Alexandre Bergel wrote: >>>>> >>>>>> hi! >>>>>> >>>>>> What about adding in FAMIXClass: >>>>>> withAllSubclasses, allSubclasses, superclasses, >>>>>> withAllSuperclasses, allSuperclasses >>>>>> >>>>>> FAMIXClass should be somewhat polymorphic to Behavior. >>>>>> That would be useful... I can do it. >>>>>> >>>>>> Any opinion? >>>>>> >>>>>> Cheers, >>>>>> Alexandre >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> Moose-dev(a)iam.unibe.ch >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 27, 2010

[Pharo-project] Software update

by Alexandre Bergel

Pharo image: core 1.1 Pharo core version: Latest update: #11323 Virtual machine used: OSX Steps to reproduce: 1. Do a software update 2. The system will always tell you that no update were done, where it has actually. by the way, couldn't 'software update' be renamed 'Pharo update' ? http://code.google.com/p/pharo/issues/detail?id=2365 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 27, 2010

[Pharo-project] ConfigurationOfPharo

by Torsten Bergmann

Hi Mariano, now he complains about "OmniBrowser-DamineCassou.462" (which comes from 1.0 of ConfigurationOfAutomaticMethodCategorizer which loads 1.0 of ConfigurationOfOmniBrowser which loads OmniBrowser-DamienCassou.462) Looks like this conflicts with "OmniBrowser-lr.469" which is noted in version 1.1.3 of ConfigurationOfOmniBrowser Looks like a conflict: You now use 1.1.3 of ConfigurationOfOmniBrowser, but the ConfigurationOfAutomaticMethodCategorizer that you use in ConfigurationOfPharo still points to 1.0 of ConfigurationOfOmniBrowser. Lesson learned: take care when you edit configs since you may break other peoples code. So I would not call this a reproducable Pharo 1.0 Release ;) Just try in a clean 1.0 core image: -------------------------- Gofer new squeaksource: 'MetaSource'; package: 'ConfigurationOfMetaSource'; load. ((Smalltalk at: #ConfigurationOfMetaSource) project version: '1.0-alpha1') load -------------------------- -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 27, 2010

[Pharo-project] [update 1.1] #11323

by StÃ©phane Ducasse

11323 ----- - Issue 2352: aDuration seconds should not return a fraction - Issue 2270: Test for FileStream>>atEnd - Issue 2332: Add a test for file-truncation.

April 27, 2010

Re: [Pharo-project] World menu and preference compatibility

by Henrik Johansen

On Apr 27, 2010, at 5:51 07PM, Alain Plantec wrote: > Sean P. DeNigris a Ã©crit : >> There is a conversation on squeak-dev right now about how to handle world >> menus / prefs / docking bar. >> >> The participants seem to be leaning toward using pragmas, and I am a strong >> voice for compatibility where we can, especially on the fundamentals. >> >> If anyone can/wants to share their experience with the pragma solution so >> far (there is a question in particular about whether it allows dynamic menu >> additions/removals), it would be relevant. >> > Hi Sean, > you can declare a menu item with a precondition block. > the menu item is not added to the menu if the precondition is false. > We have one example in the core. See the precondition in the #'Software update' item. > > WorldState class>>systemOn: aBuilder > <worldMenu> (aBuilder item: #System) > order: 4.0; > withSeparatorAfter; > icon: MenuIcons smallConfigurationIcon; > with: [ > (aBuilder item: #'About...') > order: 0; > action: [Smalltalk aboutThisSystem]. > (aBuilder item: #'Software update') > order: 1; > precondition: [self showUpdateOptionInWorldMenu]; > action: [Utilities updateFromServer]; > help: 'Load latest code updates via the internet'] > > Cheers > Alain Comparing Settings to Preference Annotations might gleam at the difference you might expect between menu annotations in Pharo and Squeak. In Pharo the method contains a simple annotation with no args, and the method contains code for building a menuitem using the builder passed as argument, My speculation: If following the existing preference-style, Squeak will probably use an annotation with more args, with the method body containing the actual action. i.e. Alains example would be written something like: WorldState class>>aboutMenuItem <menuItemIn: #('WorldMenu' 'System') order: 0 label: 'About... '> Smalltalk aboutThisSystem WorldState>>updateFromServertMenuItem <menuItemIn: #('WorldMenu' 'System') order: 1 label: 'About... ' visible: #showUpdateOptionInWorldMenu help: 'Load latest code updates via the internet'> Utilites updateFromServer Both approaches have their pros and cons. The one in Pharo depends on a builder responding to certain messages, so expanding the API might lead to breakage if you try to load into an old image. You also have to define new annotation keywords for each menu you want to build this way, . The one for Squeak might suffer a risk of needing a large amount of permutations of annotations , depending on which PluggableMenuItemSpec properties you'd want to be able to leave optional. In short: In Pharo you have access to the builder in the method, while in Squeak (based on how Preferences annotations work) I'd expect they end up with a builder parsing an annotation instead. Cheers, Henry

April 27, 2010

[Pharo-project] Pharo developers you can subscribe to Pharo-Users too ; )

by Mariano Martinez Peck

Hi everybody. We have two mailing list as you may know: one for pharo developers or people very interested in Pharo and its internal details. This mailing list is pharo-project(a)lists.gforge.inria.fr It is high traffic and there are a lot of people that cannot follow. Then we have the Pharo-User mailing list for those that just want to use Pharo and don't care about their internals. This mailing list has less traffic. This mailing list is pharo-users(a)lists.gforge.inria.fr The problem is that there is people that are subscribed to pharo-project(a)lists.gforge.inria.fr but not to pharo-users. In this last mailing list, usually new comers ask questions. It would be great that all the people that is already subscribed to pharo-project(a)lists.gforge.inria.frand have time to follow that mailing list, to subscribe also to Pharo-Users. Sometimes I am obligued to tell new comers "ask in pharo-project(a)lists.gforge.inria.fr as not all the people is subscribed there" ... and thus, the Pharo-Users becomes useless. Thanks Mariano

April 27, 2010

Re: [Pharo-project] World menu and preference compatibility

by Alain Plantec

Sean P. DeNigris a Ã©crit : > There is a conversation on squeak-dev right now about how to handle world > menus / prefs / docking bar. > > The participants seem to be leaning toward using pragmas, and I am a strong > voice for compatibility where we can, especially on the fundamentals. > > If anyone can/wants to share their experience with the pragma solution so > far (there is a question in particular about whether it allows dynamic menu > additions/removals), it would be relevant. > Hi Sean, you can declare a menu item with a precondition block. the menu item is not added to the menu if the precondition is false. We have one example in the core. See the precondition in the #'Software update' item. WorldState class>>systemOn: aBuilder <worldMenu> (aBuilder item: #System) order: 4.0; withSeparatorAfter; icon: MenuIcons smallConfigurationIcon; with: [ (aBuilder item: #'About...') order: 0; action: [Smalltalk aboutThisSystem]. (aBuilder item: #'Software update') order: 1; precondition: [self showUpdateOptionInWorldMenu]; action: [Utilities updateFromServer]; help: 'Load latest code updates via the internet'] Cheers Alain > http://forum.world.st/Squeak-dev-World-Menu-Registry-td2064576.html >

April 27, 2010

Re: [Pharo-project] What packages do you use that you can't live without?!

by Mariano Martinez Peck

I already asked that. You can see the answer if you want here: http://forum.world.st/Putting-Algernon-and-WorkingSet-in-a-Dev-image-td1295… Algernon and WorkingSet don't work together. There is a problem with the keyboard handling. I once checked a code to fix this and contacted romain robbles to see if he can fix WorkingSet with that and thus be able to use both of them. Romian, any news in this aspect? Regarding your question, I would also add to Pharo 1.1 dev the package ScriptManager. http://forum.world.st/template/NodeServlet.jtp?tpl=search-page&node=1294837… Cheers Mariano On Tue, Apr 27, 2010 at 5:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > may be workingSet could be added to pharo1.1 dev > > On Apr 27, 2010, at 5:11 PM, Sean P. DeNigris wrote: > > > > > In most of the threads on this list, I learn about packages that sound > > totally indispensible (e.g. WorkingSet, algernon). I thought it'd be > great > > to share what we're using to develop that makes a dramatic difference on > our > > productivity. And, especially whether they work in 1.0 or 1.1 or both. > > > > > > Being new, I just have two: > > 1. SSpec - works in Pharo 1.0 almost flawlessly, I fixed it for Pharo 1.1 > > and will upload shortly > > 2. Setup - works in Pharo 1.0, I uploaded a fixed for 1.1 version to ss > > > > Sean > > > > -- > > View this message in context: > http://forum.world.st/What-packages-do-you-use-that-you-can-t-live-without-… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 27, 2010

Re: [Pharo-project] ConfigurationOfPharo

by Mariano Martinez Peck

On Tue, Apr 27, 2010 at 3:11 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi! > > I am curious to see how Pharo1.1 can be produced from Core1.1. I loaded > ConfigurationOfPharo from MetacelloRepository, and evaluated in a workspace: > ConfigurationOfPharo project > > This triggered many loads, to end with an error: 'Name not found: > ArchiveViewer'. I removed the reference of ArchiveViewer in the baseline. > Thanks for the bug report and fix ;) For the rest of the fixes, I don't know what to tell you. I would contact the maintainers for those project where we have a maintainer. Then, you can commit in their repositories or ask them what to do. My main concern is what happens with all these changes, do they make those packages non compatible with Pharo 1.0 or it will still work there? For the <worldMenu> I guess there is no problem. but what about the others? Cheers Mariano > I then had to do some modifications: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Getting Pharo 1.1 from PharoCore 1.1 > > - add <worldMenu> in: > SHWorkspace class>>open > > - changed asSortedArray into "asArray sort" > OBMetagraphBuilder>>execute () > OBAllMethodCategoryNode>>methodReferences > OBSelectorNode>>implementors > OBMethodNode>>messageSelectors > OBMethodNode>>implementorsOf: > OBSelectorNode>>senders > ORCommand>>instanceVariables > > > - fix in > OCompletionTable class>>initializeWithPackages (FillInTheBlank) > NSAbstractDataStream class>>initialize (isInMemory) > SHParserST80>>resolvePartial: (hasBindingThatBeginsWith: is not defined in > SystemDictionary anymore) > > > - Registration in the WorldMenu: > In Moose > PetitGUI > MoosePanel > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > I would like to see Pharo1.1 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

April 27, 2010