- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Error when trying to create a package

by Jim Menard

Alexandre, On Sun, May 10, 2009 at 3:30 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > Here we are. Just update OB. The following doIt should be enough: Thank you. Jim -- Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com http://www.io.com/~jimm/

May 10, 2009

Re: [Pharo-project] Ideas for solving SLOW MultiByteFileStream nextPutAll:

by StÃ©phane Ducasse

Thanks nicolas I would like to have much more time to devote to pharo. But I'm(sick right now) and have a lot of mess around (home....) I will let mike give you some comments. My knowledge about UTf-8 is too limited and the way squeak handles it is even weaker (with leading char and other beasts). Stef On May 10, 2009, at 2:28 AM, Nicolas Cellier wrote: > 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 > <FasterLatin1Conversion-Part1.1.cs><FasterLatin1Conversion- > Part2.1.cs><FasterLatin1Conversion- > Part3.1.cs><FasterLatin1Conversion- > Part4.1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 10, 2009

[Pharo-project] The Fame code generator does not generate "container" annotation.

by FranÃ§ois Tanguy

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

May 10, 2009

Re: [Pharo-project] Error when trying to create a package

by Alexandre Bergel

Here we are. Just update OB. The following doIt should be enough: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | instClass | instClass := self environment at: #Installer ifAbsent: [ScriptLoader new installingInstaller]. ScriptLoader new universalInstaller universe update; addPackage: 'Shout'; install. "load latest alpha version of OB directly from its Monticello repo" instClass wiresong project: 'ob'; install: 'OmniBrowser'; install: 'OB-Standard'; install: 'OB-Morphic'. instClass ss project: 'AST'; install: 'AST-lr'. instClass ss project: 'RefactoringEngine'; install: 'Refactoring-Core'; install: 'Refactoring-Spelling'. instClass ss project: 'Regex'; install: 'VB-Regex'. instClass wiresong project: 'ob'; install: 'OB-Refactory'; install: 'OB-Enhancements'. instClass lukas project: 'omnibrowser'; install: 'OB-Regex' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ScriptLoader loadOBAlpha may not work since you probably have a old version of ScriptLoader. Alexandre On 10 May 2009, at 00:18, Jim Menard wrote: >> Open a Monticello browser, and search for OB-Enhancements > > It's dr.319 > > Jim > >> >> Cheers, >> Alexandre >> >> >> On 9 May 2009, at 22:48, Jim Menard wrote: >> >>> Alexandre, >>> >>> On Sat, May 9, 2009 at 4:02 PM, Alexandre Bergel >>> <alexandre(a)bergel.eu> wrote: >>>> I just tried and it works as expected. I fix the bug you >>>> mentioned on >>>> April 20, 2009. Which version of OB-Enhancements do you use? >>> >>> I don't know. How can I tell? >>> >>> Jim >>> -- >>> Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com >>> http://www.io.com/~jimm/ >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com > http://www.io.com/~jimm/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 10, 2009

[Pharo-project] Ideas for solving SLOW MultiByteFileStream nextPutAll:

by Nicolas Cellier

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

May 10, 2009

Re: [Pharo-project] Error when trying to create a package

by Jim Menard

> Open a Monticello browser, and search for OB-Enhancements It's dr.319 Jim > > Cheers, > Alexandre > > > On 9 May 2009, at 22:48, Jim Menard wrote: > >> Alexandre, >> >> On Sat, May 9, 2009 at 4:02 PM, Alexandre Bergel >> <alexandre(a)bergel.eu> wrote: >>> I just tried and it works as expected. I fix the bug you mentioned on >>> April 20, 2009. Which version of OB-Enhancements do you use? >> >> I don't know. How can I tell? >> >> Jim >> -- >> Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com >> http://www.io.com/~jimm/ >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com http://www.io.com/~jimm/

May 9, 2009

Re: [Pharo-project] Submitting changes to upstream repositories

by Damien Pollet

On Sat, May 9, 2009 at 23:11, Lukas Renggli <renggli(a)gmail.com> wrote: > I guess you are talking about named branches. This was broken for a > while as people used dots in their initials, but Julien and I provided > patches that are included in recent versions of Pharo. We use > named-branches in Seaside and in various commercial projects > extensively. Exactly. And of the lack of support from MC Browser or Squeaksource at the user level. I know that each snapshot is a branch, but relying on a naming convention that isn't even enforced kinda sucks (what breaks if I commit MyPackage.initials.42.mcz, but change the file name to foobar.mcz before saving?). In Seaside, you can maintain it because you really pay attention or are used to it and know MC well. > My take on this is the following: If you fork you create your own > branch. It is not the job of people that fork to keep compatible with > the rest of the world or to merge changes back into the main trunk. > Sometimes it happens that original project merges changes from a fork, > but the initiative has to come from the original maintainers. This is > a good read on the topic: <http://producingoss.com/en/forks.html>. Sure, but it's also good practice to announce at least that you do changes, or better send the changes (fire and forget, but at least the upstream maintainers can go through them and follow if they wish). I have friends working for a linux distro and they often complain that some other distro fixes stuff without notifying upstream, so not only upstream is not notified of bugs and fixes, but every distro duplicates some the fixes and misses some others. Since most fixes could benefit to most forks, it's just a waste of ressources and does more against propagating fixes than otherwise. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 9, 2009

Re: [Pharo-project] Submitting changes to upstream repositories

by Alexandre Bergel

Thanks for the link. This is indeed an excellent reading Alexandre On 9 May 2009, at 23:11, Lukas Renggli wrote: > http://producingoss.com/en/forks.html -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 9, 2009

Re: [Pharo-project] Submitting changes to upstream repositories

by Alexandre Bergel

> My take on this is the following: If you fork you create your own > branch. It is not the job of people that fork to keep compatible with > the rest of the world or to merge changes back into the main trunk. Agree on this (I wasn't clear enough in my previous email). However telling the author of the original package that new versions have been produced is not very costly. And if the package author is ready to backport, this is even better, but this is up to him only. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 9, 2009

Re: [Pharo-project] Error when trying to create a package

by Alexandre Bergel

Open a Monticello browser, and search for OB-Enhancements Cheers, Alexandre On 9 May 2009, at 22:48, Jim Menard wrote: > Alexandre, > > On Sat, May 9, 2009 at 4:02 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> I just tried and it works as expected. I fix the bug you mentioned on >> April 20, 2009. Which version of OB-Enhancements do you use? > > I don't know. How can I tell? > > Jim > -- > Jim Menard, jimm(a)io.com, jim.menard(a)gmail.com > http://www.io.com/~jimm/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 9, 2009