How do I know which issues are resolved in each new release?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

How do I know which issues are resolved in each new release?

Tim Mackinnon
Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).

Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?

Tim
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Michael Roberts-2
you can check the log of the script loader.  I don't have the code to
hand but check the state of the singleton I think.

It might be nice in the future to use the google SVN feature to tag
issues with the image update as we close them.

cheers,
Mike

On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <[hidden email]> wrote:

> Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
>
> Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
>
> Tim
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
I do not get it?
Can you explain how this works?
Because right now you take ScriptLoader and you get the log of all the issue that have been integrated.

Stef

On Nov 30, 2009, at 10:48 PM, Michael Roberts wrote:

> you can check the log of the script loader.  I don't have the code to
> hand but check the state of the singleton I think.
>
> It might be nice in the future to use the google SVN feature to tag
> issues with the image update as we close them.
>
> cheers,
> Mike
>
> On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <[hidden email]> wrote:
>> Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
>>
>> Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
>>
>> Tim
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Michael Roberts-2
do you mean the svn thing? you can mark files in the repository in a
way that updates the issue tracker.  I haven't tried it (we have no
files) but the docs look straightforward. It's meant for projects that
actually keep their source in the repository, but I think we could
have a dummy file that acted the same way. It would be a logical
closure for each issue to mark it with the update. That way it is
external to the image and gives the full life cycle on the tracker
which I think would be useful.

cheers Mike

On Mon, Nov 30, 2009 at 11:03 PM, Stéphane Ducasse
<[hidden email]> wrote:

> I do not get it?
> Can you explain how this works?
> Because right now you take ScriptLoader and you get the log of all the issue that have been integrated.
>
> Stef
>
> On Nov 30, 2009, at 10:48 PM, Michael Roberts wrote:
>
>> you can check the log of the script loader.  I don't have the code to
>> hand but check the state of the singleton I think.
>>
>> It might be nice in the future to use the google SVN feature to tag
>> issues with the image update as we close them.
>>
>> cheers,
>> Mike
>>
>> On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <[hidden email]> wrote:
>>> Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
>>>
>>> Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
>>>
>>> Tim
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Dale
In reply to this post by Tim Mackinnon
In the google issues list, one can add a column called "Fixed" and a version can be supplied for the value of that field (like Version or Milestone) when the bug is fixed ... I think this is what Tim is getting at. I've just done this for Metacello, since I think it is a good idea:)

Dale
----- "Tim Mackinnon" <[hidden email]> wrote:

| Hi guys - I noticed there was a new 9.11.4 release since buenos aires
| - and I got to wondering what issues have been resolved in it (as I am
| trying to follow Pharo by example - I am trying to test out features
| to see if they work as I progress through the material).
|
| Anyway - is there a list of issues fixed marked against each new
| version? I can see the list at:
| http://code.google.com/p/pharo/issues/list# - but it doesn't list any
| build numbers - just milestone 1.1?
|
| Tim
| _______________________________________________
| Pharo-project mailing list
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Tim Mackinnon
In reply to this post by Michael Roberts-2
Actually I am thinking of something like the following (this is JBoss - they use Jira - which is free for open source projects, although I find it a bit clunky - but it gives an idea. I have actually seen Trac - the wiki and ticket system used very effectively);

This link shows all of their version for the JBoss Web project:
https://jira.jboss.org/jira/browse/JBWEB?report=com.atlassian.jira.plugin.system.project:versions-panel

This link shows what was fixed in 2.1.1 GA
https://jira.jboss.org/jira/browse/JBWEB/fixforversion/12312592

I guess I am thinking that when I see the following in this list (from Marcus) - this information should appear somewhere as the things that were fixed in 9.11.5?
11066
-----

Issue 1526: remove #addInstanceVarNamed:withValue:
Issue 1518: #abbreviatedBrowserButtons should be removed
Issue 476: [Pending Etoy Cleaning] Object>>knownName
Issue 1520: remove global References


Tim

On 30 Nov 2009, at 22:34, Michael Roberts wrote:

> do you mean the svn thing? you can mark files in the repository in a
> way that updates the issue tracker.  I haven't tried it (we have no
> files) but the docs look straightforward. It's meant for projects that
> actually keep their source in the repository, but I think we could
> have a dummy file that acted the same way. It would be a logical
> closure for each issue to mark it with the update. That way it is
> external to the image and gives the full life cycle on the tracker
> which I think would be useful.
>
> cheers Mike
>
> On Mon, Nov 30, 2009 at 11:03 PM, Stéphane Ducasse
> <[hidden email]> wrote:
>> I do not get it?
>> Can you explain how this works?
>> Because right now you take ScriptLoader and you get the log of all the issue that have been integrated.
>>
>> Stef
>>
>> On Nov 30, 2009, at 10:48 PM, Michael Roberts wrote:
>>
>>> you can check the log of the script loader.  I don't have the code to
>>> hand but check the state of the singleton I think.
>>>
>>> It might be nice in the future to use the google SVN feature to tag
>>> issues with the image update as we close them.
>>>
>>> cheers,
>>> Mike
>>>
>>> On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <[hidden email]> wrote:
>>>> Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
>>>>
>>>> Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
>>>>
>>>> Tim
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
In reply to this post by Dale
this is what we do also.

On Dec 1, 2009, at 2:03 AM, Dale Henrichs wrote:

> In the google issues list, one can add a column called "Fixed" and a version can be supplied for the value of that field (like Version or Milestone) when the bug is fixed ... I think this is what Tim is getting at. I've just done this for Metacello, since I think it is a good idea:)
>
> Dale
> ----- "Tim Mackinnon" <[hidden email]> wrote:
>
> | Hi guys - I noticed there was a new 9.11.4 release since buenos aires
> | - and I got to wondering what issues have been resolved in it (as I am
> | trying to follow Pharo by example - I am trying to test out features
> | to see if they work as I progress through the material).
> |
> | Anyway - is there a list of issues fixed marked against each new
> | version? I can see the list at:
> | http://code.google.com/p/pharo/issues/list# - but it doesn't list any
> | build numbers - just milestone 1.1?
> |
> | Tim
> | _______________________________________________
> | Pharo-project mailing list
> | [hidden email]
> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Tim Mackinnon
So can can I see this somewhere? I was expecting on the download page there would be a link to show me what changes have been fixed in that release. ( even a list so that I can filter on 9.11.4 - and then see that #11504,11523... is included etc. would be fine).

Maybe in the future there might be some way to do something like the Trac guys do - where they have the convention that their SVN commit comments (I guess this could be MCZ comments or naming convention) include the ticket id number of the bug/feature they are fixing - they can then generate a list of whats in a build - and when you do a release, whats in the release. e.g. look at the following page on their website: http://trac.edgewall.org/wiki/TracL10N (press the edit button and see how they are querying out the outstanding tickets for a release). Is this what Mason and the things mentioned do?

The best system I have seen running was Trac with Hudson - however all these things are doable in any system (the ones mentioned here sound interesting).

I would just like to see something concrete so I can try and help in some way to make sure that V1.0 is stable and as bug free as possible.


Tim

On 1 Dec 2009, at 12:35, Stéphane Ducasse wrote:

> this is what we do also.
>
> On Dec 1, 2009, at 2:03 AM, Dale Henrichs wrote:
>
>> In the google issues list, one can add a column called "Fixed" and a version can be supplied for the value of that field (like Version or Milestone) when the bug is fixed ... I think this is what Tim is getting at. I've just done this for Metacello, since I think it is a good idea:)
>>
>> Dale
>> ----- "Tim Mackinnon" <[hidden email]> wrote:
>>
>> | Hi guys - I noticed there was a new 9.11.4 release since buenos aires
>> | - and I got to wondering what issues have been resolved in it (as I am
>> | trying to follow Pharo by example - I am trying to test out features
>> | to see if they work as I progress through the material).
>> |
>> | Anyway - is there a list of issues fixed marked against each new
>> | version? I can see the list at:
>> | http://code.google.com/p/pharo/issues/list# - but it doesn't list any
>> | build numbers - just milestone 1.1?
>> |
>> | Tim
>> | _______________________________________________
>> | Pharo-project mailing list
>> | [hidden email]
>> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
ScriptLoader new logContents

was used to generate the log of all the commit.
But apparently since 11000 it does not log anymore.

Now if you want you can offer a fix because everything is in the update method of the ScriptLoader





' ------------------------------------------------------
update10047
Fixing the release. Adrian made a few cosmetic changes and tagged testUnimplementedNonPrimitiveCalls as expected failure

Original description:
- added allClassesWithUnimplementedCalls to SystemNavigation to return structured classes with unimplemented calls
- added convenience method PackageOrganizer>>allPackagesContainingUnimplementedCalls
- adjusted ReleaseTest>>testUnimplemented... to exclude TestCase classes

  ------------------------------------------------------
withUdpateLog:
Added MCWorkingCopy printOn:

Scriptloader cleaning

MC repository cleaning

Adding new Sapphire repository
 ------------------------------------------------------
withUdpateLog:
Remove release builder package: classes were moved in scriptloader
 ------------------------------------------------------
withUdpateLog:
Fixing underscore of Service-base

Fixing underscore kernel

Fixing underscore VersionNumber
 ------------------------------------------------------
withUdpateLog:
Fixing invisible in Date and DateAndTime
 ------------------------------------------------------
withUdpateLog:
Fixing invisible in Kernel Chronology

enhancing FixUnderscores to fix also character lf

remove FFI organization
 ------------------------------------------------------
withUdpateLog:
Fixing invisible in Files and Exceptions

Fixing assign in Files and Exceptions
 ------------------------------------------------------
withUdpateLog:
Fixing invisible in Collection Graphics KernelTests Network Protocols PackageInfo Sounds System Tools VersionNumber

Will not fix them in Etoys, Morphic, MorphicExtra for obvious reasons
 ------------------------------------------------------
withUdpateLog:
Fixing - into :=  in Collection Compiler KernelTests Mutilingual Monticello PackageInfo NetworkTests Tests Sound System ToolBuilder-SUnit ToolBuilder-Morphic Tools Traits

Will not fix them in Etoys, Morphic, MorphicExtra for obvious reasons
 ------------------------------------------------------
withUdpateLog:
Utilities informuser:during: -> UIManager default informuser:during:
 ------------------------------------------------------
withUdpateLog:
Deprecating Utilities>>informDuring:
 ------------------------------------------------------
withUdpateLog:
Remove HTML Fileout + printout Method
 ------------------------------------------------------
withUdpateLog:
changes from Reflectivity, remove Packagepanebrowser, faster transcript
 ------------------------------------------------------
withUdpateLog:
scriptloader load mc silently + TTF fonts
http://bugs.squeak.org/view.php?id=6089
 ------------------------------------------------------
update10022
Lexicon and Instance Browser were not really used. We will rebuild it if necessary. Remove instanceBrowser and Lexicon + faster doOneCycleNow
 ------------------------------------------------------
update10023
remove Nebrasksa audiot chat + deprecated author in Utilities
 ------------------------------------------------------
update10024
Fixing Sapphire -> Pharo Squeak source Server + CS Servers
 ------------------------------------------------------
update10025
Unload Nebraska
 ------------------------------------------------------
update10026
Fixing Author FullName  
 ------------------------------------------------------
update10027
Lexicon merge, Better tests for rectangle, findString fix

http://bugs.squeak.org/view.php?id=3574

Remove superswiki
 ------------------------------------------------------
update10028
Fixing MC
 ------------------------------------------------------
update10030
Fixing Delay
         0006834: Delay class>>timeoutSemaphore:afterMSecs: doesn t.
Description The implementation for Delay class>>timeoutSemaphore:afterMSecs: doesn t even use its first parameter, so it can t do what it says it does.

This method should be deprecated or removed entirely.
Additional Information + tests

Fixing Obsolete references
 ------------------------------------------------------
withUdpateLog:
1.0 / (FloatArray with: 2.0) answer unexpected result.
Bug is in FloatArray>>adaptToNumber:andSend:
See : http://bugs.squeak.org/view.php?id=6782

fixing files left by tests
 ------------------------------------------------------
update10032
Fixing Number parsing

Cleaning nebraska
 ------------------------------------------------------
update10033
Simplifying Traits usage in kernel

Simplifying Traits usage in kernel
 ------------------------------------------------------
update10034
Fixing tests (serge stinckwich)

http://bugs.squeak.org/view.php?id=6936 
        #asHTMLColor is inaccurate for certain values.
     Attached fix resolves that, also gives 10x speed-up.
 ------------------------------------------------------
update10035
Merging MVC removal step one of Alain Plantec
 ------------------------------------------------------
update10036
Merging MVC removal step one of Alain Plantec (missing part)
 ------------------------------------------------------
update10037
Fixes the following 7 tests:

testRootsOfTheWorld -- test removed
testLocalMethodWithSameCodeInTrait -- removed duplicated method ClassDescription>>fileOutCategory:
testFinalizationOfEquals -- test fixed
testHash -- remove all assertions/tests that have hardcoded hash values:
        DateAndTimeEpochTest>>#testHash
        DateAndTimeLeapTest>>#testHash
        TimeTest>>#testHash
        TimespanTest>>#testHash
 ------------------------------------------------------
update10038
rootsOfTheWorld is back

Adding missing Class variables to TTCFonts + cleaning Scriptloader (norbert)
 ------------------------------------------------------
update10039
Nebraka category cleaning + graphics tests cleaning after
 ------------------------------------------------------
update10040
 replace: ReadStream on: ``@object with: ``@object readStream
 ------------------------------------------------------
update10041
MVC removal step 2
 ------------------------------------------------------
update10042
Couple of changes to make more tests work plus fix of finalization logic:
- changed WeakRegistry to use WeakIdentityKeyDictionary (http://bugs.squeak.org/view.php?id=6347)
- FinalizerTest reverted to real test case
- added missing class variables to DigitalSigntureAlgorithm
- Fix issue #13: TraitsTests pollutes ProtoObject subclasses (Mantis 7090)
- make BitmapStreamTest clean up the file bitmapStreamTest.ref.extSeg


 
        update10043
                MVC cleaning step 3
        update10043
                cleaning unimplemented calls
               
        update10045
             Some more cleaning made by Norbert
       
        update10046
                KernelTests-Numbers -- Nan and hex tests broken.
                Collection methods #select: and #collect: have no test.
                MC fixes.
                Remove testAllMethodsWithSourceString.



 ------------------------------------------------------
update10047
Fixing the release. Adrian made a few cosmetic changes and tagged testUnimplementedNonPrimitiveCalls as expected failure

Original description:
- added allClassesWithUnimplementedCalls to SystemNavigation to return structured classes with unimplemented calls
- added convenience method PackageOrganizer>>allPackagesContainingUnimplementedCalls
- adjusted ReleaseTest>>testUnimplemented... to exclude TestCase classes

 ------------------------------------------------------
update10048
Fix the Scriptloader logStream + Collection tests  http://bugs.squeak.org/view.php?id=6355 + Pharo Flaps
 ------------------------------------------------------
update10049
7073 CollectionAndCollectionTest
* [http://bugs.squeak.org/view.php?id=6367 M6367]
* seems good [http://bugs.squeak.org/view.php?id=5700 M5700]

Add 2 tests for RunArray class + at:put:
See :  http://bugs.squeak.org/view.php?id=6070
 ------------------------------------------------------
update10050
This update includes a set of Mantis fixes (that also went into Squeak 3.10):
http://code.google.com/p/pharo/issues/detail?id=27
http://code.google.com/p/pharo/issues/detail?id=31
http://code.google.com/p/pharo/issues/detail?id=32
http://code.google.com/p/pharo/issues/detail?id=30
mark testUnwindDebuggerWithStep as expected failure
 ------------------------------------------------------
update10051
Name: SLICE-remove-copyHtml-al.6
Author: al
Time: 22 July 2008, 9:37:16 pm
UUID: 9192a548-32f3-43ac-8477-236a754a2a93
Ancestors: SLICE-remove-copyHtml-dc.5

in addition to previous version by Damien
- remove #command: senders and implementors
- remove method references to deleted methods in MessageFinder
- remove String>>asHtml, which in turn required to...
- remove an etoys related mail message class (FancyMailComposition), which required to
- remove some html code in EToys (tell a friend feature)
 ------------------------------------------------------
update10052
ISSUE #124
While browsing at referencer of FileDoesNotExistException, I discovered the following pattern
that is used in many different places. I find this pretty ugly:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
        file := [fd readOnlyFileNamed: keysFileName]
                        on: FileDoesNotExistException do:[:ex| nil].
        file ifNil:[^self]. "no keys file"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The use of exception is completely outwitted.

I would rather write:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
        [file := fd readOnlyFileNamed: keysFileName]
                        on: FileDoesNotExistException do: [:ex| ^ self].
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 ------------------------------------------------------
update10053
Faster printString for LargeInteger

        http://code.google.com/p/pharo/issues/detail?id=114

        http://code.google.com/p/pharo/issues/detail?id=74

        There exist 2 related issues that report endless loops when using a bad base.
        http://bugs.squeak.org/view.php?id=6710
        http://bugs.squeak.org/view.php?id=7107
 ------------------------------------------------------
update10054
- Monticello enhancements (slice + comments)
                                        - UndefinedObject>>from3DS: removed
                                        - TransformationMorph>>heading:
                                        - Integer>>printStringBase:
                                        - - -> := in PasteUpMorph
                                        - Issue 118: 0006846: MenuMorphs can drop mouse focus. Patch provided by rootbeer.

 ------------------------------------------------------
update10055
Small fixes so that the NewCompiler can load and recompile the complete system
 ------------------------------------------------------
update10056
remove VeryPickyMorph + fix Comments... behavior in Monticello
 ------------------------------------------------------
update10057
remove duplicated code, remove unused code
 ------------------------------------------------------
update10058
cleaning duplicated method, part II
 ------------------------------------------------------
update10059
- remove duplicated / unused code
- small refactoring (e.g size=0 --> isEmpty, use #isEmptyOrNil)
- undeclaredCleanup in ComponentLikeModel
- rename all calls of #submorphOfClass: to #findA:
- clean up BasicButton (which should be removed...)
 ------------------------------------------------------
update10060
 - remove GeeMail experiment.
- fix undeclared Installer reference.
- remove StoryboardBookMorph, ZoomAndScrollControllerMorph, ZoomAndScrollMorph

 ------------------------------------------------------
update10061
 - remove EtoyProjectHistoryMorph, StretchyImageMorph, EToyProjectQueryMorph, EToyProjectRenamerMorph, EtoyGenericDialogMorph, EtoyProjectDetailsMorph, ShowEmptyTextMorph, EToyCommunicatorMorph, EtoyLoginMorph, EToyHierarchicalTextGizmo, EToyHierarchicalTextMorph, SimplerTextContainer, EToyTextNode, EToyTextNodeWrapper.

 ------------------------------------------------------
update10062
 - move the code for making a copy of a class into Class (from Browser).
           - fix for printing not initialized LargeIntegers (fixes printing of specialObjectsArray)

 ------------------------------------------------------
update10063
- add #numberOfMethods
        - fix Behavior>>linesOfCode to be traits-aware
        - create all morphic events with basicNew to save the send of #initialize
        - optimized path for Morph>>#fillStyle for emoty morph-extension. (Called a lot)
        - optimized path for Morph>>#shadowOffset for empy morphExtension (called a lot)
        - remove call to "self flag #arNote" in Morph>>#transformedFrom: (called on mouse-move)
        - remove MorphEvent>>#convertFromObsolete
        - remove turtle trails check from Morph>>#drawOn:
        - remove more calls to #flag:
        - some simple code simplification (e.g. call #methods, not #methodDict values, more isEmpty)
        - remove AbstractEvent>>#saveChangeNotificationAsSARFileWithNumber:

 ------------------------------------------------------
update10064
-0007136: [BUG] LinkedList add:after: fails to update lastLink
-0007156: Behavior>>#initialize sends #superclass: which can cause VM crash
- delete #isValidWonderlandTexture
- fix TClassAndTraitDescription>>#methods to return the methods of a class or trait
- add #localMethods to return methods defined in a class, not included by a trait.
-7147 Parser-removeUnusedTemps
-0006503: RunArray cant be created through #new:

 ------------------------------------------------------
update10065
Fixing Transcript and Smalltalk to return themselves when printed :)

 ------------------------------------------------------
update10066
tally it integration
http://bugs.squeak.org/view.php?id=1014

 ------------------------------------------------------
update10067
Cleaning html fileout removal
http://code.google.com/p/pharo/issues/detail?id=115

 ------------------------------------------------------
update10068

        - ClassBuilder fixes and tests from Noury Bouraqadi
Now instance variable names cannot be uppercased
and classVariables lowered.
     - Refactoring engine tests commented by alexandre bergel to let the test builder
        work
        - PackageInfo better printOn: + mostSpecificPackageOf:
        - Tools package loaded (was forgotten before) with tally enh of alexandre Bergel

 ------------------------------------------------------
update10070

       
        Remove TextSqkLink TextProjectSqkLink
       
       
 ------------------------------------------------------
update10071

       
        -> Issue 100: 7154 FixForDebugBlockValueWithArguments
-> Issue 172: show byte code menu item pane is broken
-> Issue 39: 7088 AnimatedMorphfix (M5692)
-> Issue 91: 7143 ValueWithinFix-ar
-> Issue 54: 7104 Morph-intersects-wiz (M6461)
-> Add RBSmallDictionary as SmallDictionary. Add SmallIdentityDictionary
-> Small Nebraska Removal related to HandMorph:
        -> do not test for #hasUserInformation in #needsToBeDraws
        -> remove user-drawing code from HandMorph>>#drawOn:
        -> delete HandMorph>>#hasUserInformation
-> fast path for empty extension in Morph>>#borderStyle
-> Remove unsent methods from Player:
        -> thumbnailMenuEvt:forMorph:, setFogDensity:, setFogRangeEnd:, setFogRangeStart:, setFogType:
        -> getFogColor, getFogDensity, getFogRangeEnd, getFogRangeStart, getFogType, setFogColor:
-> Remove unsent Methods:
        -> TextStyle>>changeDefaultFontSizeBy:
        -> AlignmentMorphBob1>>simpleToggleButtonFor:attribute:help:
-> fix ifNotNil:ifNil: and  ifNil:ifNotNil: to use #valueWithPossibleArgs: (to be consistent with ifNotNil:)
-> comment for #browseAllUnimplementedCalls
-> some refactoring everywhere to use isNil and ifNil: (more to go)
-> Start to remove deprecated methods that where deprecated in 3.9
-> enable deprecation warnings in postscript.

       
 ------------------------------------------------------
update10072
-> Issue 95: 7149 ChangeHooksTest-tearDown-M6702-rej
-> Issue 174: XMLSupport cant be loaded into latest Pharo image
-> Issue 52: 7102 ObjectPerformOrSendToFix (M1666)
-> Issue 106: 7090 DSAunimplementedCleanup
-> Issue 77: 7127 RemoveMappedCollection
-> More ifNil:/isNil refactorings
-> replace all occurrances of "isNil not" with "notNil"
 ------------------------------------------------------
update10073
- Issue 44: 7094 FixClassCompatibilityForClassVar (M6472)
- Issue 86: 7138 TransformationMorph-isSticky
- Issue 89: 7141 PrintingArraysWithMetaclasses
- Issue 42: 7092 TTCFontDNUfix (M5309)
- Issue 176:failing tests in 70072
- delete ParagraphEditor>>#initializeTextEditorMenus (never called, has undeclared)
- revert Issue 95: 7149 ChangeHooksTest-tearDown-M6702-rej (broke tests)
- MorphExtension now stores properties in SmallIdentityDictionary.
- in loadscript: Smalltalk associations do: [:each | each beReadWriteBindingAnnouncing: true]
 ------------------------------------------------------
update10074
- Issue 180: 10073 still needs some cleanup
- Issue 166: Cleaning up the menus
- Issue 182: Cleaning leftover from nebraska
- Issue 184: delete PseudoPoolVariable
- Issue 188: start of removing Vocabulary
- Issue 187: delete Button, OneOnSwitch, ST80MenusTest, Switch
- Issue 183: delete ClickExerciser, TestClickExerciser, DumberMenuMorph, PluggableFileList
- Issue 181: Remove codepane+tilescript from browser
- Issue 178: unsent messages
- remove hashMappedBy: and friends (never called).
- remove even more methods that have no senders (mostly etoys related)
- Classes removed: RemoteHandMorph PseudoPoolVariable ElementTranslation MethodCall UnknownType Button OneOnSwitch ST80MenusTest Switch DumberMenuMorph, ClickExerciser, ClickExerciserTest, PluggableFileList
- Postscript:
        SMSqueakMap default purge.
        Smalltalk cleanOutUndeclared.
        CustomEventsRegistry at: #scrolledIntoView put: IdentityDictionary new.
        CustomEventsRegistry at: #scrolledOutOfView put: IdentityDictionary new.
        Set rehashAllSets.

 ------------------------------------------------------
update10075
 Remove ComponentLikeModel

 ------------------------------------------------------
update10076
 fixing SystemWindow>>windowsIn:Satisfying
-> PasteUpMorph>>windowsSatifying:
+ defined as class extension for Morphic-Windows
+ put all the users of windowsIn:Satisfying as class extensions too.

 ------------------------------------------------------
update10077
 Remove ComponentLikeModel

 ------------------------------------------------------
update10078
 Removed isUniClass: (the package description is wrong sorry)

 ------------------------------------------------------
update10079
 Clean inspector from tiling behavior (following gary removal scripts)

 ------------------------------------------------------
update10080
  Remove uniClass influences in DeepCopier and Object following
gary cleans.

Remove universalTile... from Object


 ------------------------------------------------------
update10081
  Clean WorldState following gary changes
                remove expungeUniClasses from ChangesSorter and bros


 ------------------------------------------------------
update10082
  Etoy cleaning from gary (continued)
Removed UndefinedObjectTest>>testNewTileMorphRepresentative
Removed BooleanTest>>testNewTileMorphRepresentative
Removed BookMorph>>chooseAndRevertToVersion
Removed BookMorph>>revertToCheckpoint: secsSince1901
BookMorph>>installRollBackButtons
BookMorph>>methodHolderVersions
BookMorph>>methodHolders
BookMoprh>>goToPageMorph:  transitionSpec:  runTransitionScripts:  
BookMorph>>goToPageMorph:  transitionSpec:  
TabbedPalette>>selectTab: cleaned
Removed TabbedPalette>>becomeStandPalette
Removed>>currentPlayerDo: and fixed sender
EncodedCharSet fixed initialize

 ------------------------------------------------------
update10083
Issue 191: freeze in World/Configuration menu
Issue 134: ReadOnlyVariableBinding should be removed (unused experiment)
Issue 194: some random cleanups from 23.09
Issue 193: Squeakmap fails to open if it is purged and no sm/ dir present
Issue 205: [ENH] >10% faster senders of

-> removed "CurrentProjectRefectoring". --> all references replaced by "Project current".
-> ReadOnlyVariableBinding removed
-> cleanGenie: removes genie related methods from HandMorph
-> DNDAnimationKill: there is an option nobody ever uses to draw a line on dragndrop.
-> cleanSmallLandTheme: removes methods from Preferences. More needed later.
-> md-random-cleans.1: remove KidNavigationMorph and some never called methods.
-> Fullscreen of/on isrendered like soundof/on, that is just one entry that changes
   according to state of display.

 ------------------------------------------------------
update10084
- fixing a bug that the ReadOnlyVariableBinding removal introduced.
          - recompile the image to make sure everything works
 ------------------------------------------------------
update10085
- Latest version of OB (Yes I know we should use Universe....)
          - ArrayTest fixed
          - Behavior testBinding
          - Behavior testAllSelectors
          - M7166: speedup allSelectors add allSelectorsBelow:.
                Firstly #allSelectors inefficiently creates multiple intermediate collections. Refactoring
                this yields a 27% speed improvement.
                Secondly many users of #allSelectors forget that when applied to the class side it doesnt
                stop at ProtoObject class, it continues to Class ClassDescription, Behavior, Object and
                ProtoObject. This is catered for by adding #allSelectorsBelow:
                Magritte and SUnit are heavy users which benefit.
       
       
       
       
 ------------------------------------------------------
update10086
Issue 214: [enh] executeMethod via primitives
        - moves the *executeMethod: method to protoObject
        - uncomments the commented primitive for faster execution
Issue 211: undeclared fix for 10084
        - fixes one remaining reference to CurrentProjectRefactoring
Issue 210: [ENH] CompiledMethod explorer
Issue 206: [ENH] simplify unreferencedInstanceVariables, allUnreferencedInstanceVariables
        - add test for and simplify Behavor>>#whichSelectorsAccess:
        - simplify Behavior>>#unreferencedInstanceVariables
        - simplify and remove #isDoIt check from Behavior>>#allUnreferencedInstanceVariables
Issue 196: remove #hash from Association
Issue 212: random cleans
        - KillNewWorld: remove class NewWorldWindow
        - InspectorTileRemove: remove the menus from inspector for tiles
        - delPlayerSurrogate.1: remove class PlayerSurrogate
        - CleanExplanation: remove more code related to the "explain" functionality
        - UnsentMessages: remove some unsent messages
       
Postscript:

        Vocabulary allStandardVocabularies removeKey: #unknown.
        PartsBin allInstances do: [:pb| pb submorphs do: [:sm| (sm target name=#AnObsoleteGeeMailMorph) ifTrue: [ pb removeMorph: sm ]]].
        Preferences removePreference: #thoroughSenders.
        Preferences removePreference: #dragNDropWithAnimation.
        Set rehashAllSets.
       
 ------------------------------------------------------
update10087
 Issue 80: 7130 PluggableListMorphFix
 Issue 41: 7091 PluggableListMorphfix (M4719)
 Issue 98: 7152 Form-isAllWhiteandFormTest-ar
 Issue 57: 7107 IntervalReverseDoFix (M6438)
        -> used Nicolas fix from http://bugs.squeak.org/view.php?id=6456
 Issue 202: Pier-Model can not be loaded into Pharo
 ------------------------------------------------------
update10088
Issue 218: Enhancements collected by gary and simon
        1. Fixed flaky borwser comment text area sometime not showing.
        2. Added getArgumentPermutation to support RefactoringEngine.
        3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner to correctly align the first line of text
        when centered/justifed etc.
        4. Added more constant names to Character class.
        5. Modified ConnectionQueue to not accept connections when queue is full.
        6. Changed GrafPort to answer a MultiDisplayScanner when appropriate (allows subclasses of
        MultiNewParagraph).
        7. NaturalLanguageTranslator startup postion move to after PasteUpMorph since it will show a progress bar.
        8. Fix to Random>>nextInt: to allow large numbers which would be out of range if using Floats (as mentioned
        recently on dev, use of Floats is dodgy anyway...)
        9. Changed TranscriptStream>>clear to use a new buffer (was just reset which could leave a massive
        collection).
        10. Changed RemoteString to handle concurrent processes safely. This ones particularly interesting: we were
        load-testing our Seaside app here and getting lots of syntax errors when hitting the image with around the 20
        concurrent processes due to source file access. After this change we were hitting it with approximately 500
        concurrent processes, and the failure was in the Java load tester (it timed out).
Issue 224: random cleans
        - removeColorSwatch.1.cs: remove class ColorSwatch
Issue 221: cleanup: remove methods calling isThisEverCalled
        - remove some methods that where deprecated in 3.9
        - remove all methods with calls to #isThisEverCalled
Issue 222: methods from NewCompiler
        - some method from newcompiler/Reflectivity that are better directly in the base (accessors, mostly)
Issue 199: remove MethodFinder
        - finding methods by name is done by "Method Names", too
        - it s >1000 lines of Code.
        - it has a list of all selectors of a very old Squeak version. Many methods are only referenced here, thus
          they can not be found using the tools to find unsent mesages.
 ------------------------------------------------------
update10089
Fix BookMorph new openInWorld
 ------------------------------------------------------
update10090
Sunit extensiosn to store result and show progress
        CollectionsTests improved
 ------------------------------------------------------
update10091
SUnit removing %$^&*( self halt
       
        GATHER SEVERAL COLLECTION RELATED MANTIS TESTS AND FIXES

----------------------------------------

http://bugs.squeak.org/view.php?id=7172

CharacterSetComplement has spoiled previous byteArrayMap optimization.
Using #byteArrayMap is an optimization per se, possibly tailored for tight loops.
Taking too much time to compute this map is spoiling efficiency.
It is necessary to cache this this map for restoring efficiency to the level preceding introduction of CharacterSetComplement.

----------------------------------------

http://bugs.squeak.org/view.php?id=6998

((String new: 1) at: 1 put: $a) = $a -> true.
((WideString new: 1) at: 1 put: $a) = $a -> false.

WideString at:put: should return the put object like any other collection

----------------------------------------

http://bugs.squeak.org/view.php?id=5331
http://bugs.squeak.org/view.php?id=6366

Lots of tests and few patches for WideString not behaving correctly.

----------------------------------------

http://bugs.squeak.org/view.php?id=7180 +6455 +1603 +1602

Patches for Interval indexOf: and includes:

----------------------------------------

http://bugs.squeak.org/view.php?id=6994

Authorize this:
(#(1 2 3) as: ByteArray) as: Interval

----------------------------------------

http://bugs.squeak.org/view.php?id=7121 (ar)

Patches for OrderedCollection add:after: add:before:
Try this one to be convinced for the necessity:
| oc |
oc := #(1 2 3 4) asOrderedCollection.
(oc first:3) do: [:e | oc remove: e].
oc add: 0 beforeIndex: -2.
^oc

----------------------------------------

http://bugs.squeak.org/view.php?id=6977
incorrect use of super
(super basicNew in #new: dating from some 3.9 changes)

----------------------------------------

http://bugs.squeak.org/view.php?id=6778
SkipList copy is shallow

----------------------------------------

http://bugs.squeak.org/view.php?id=6994
deprecate the Service related #startsWith: because single implementor completely redundant with beginsWith:

Add tests and patch
for http://bugs.squeak.org/view.php?id=6873
and http://bugs.squeak.org/view.php?id=6874

bitAnd: is broken for LargeNegativeInteger on every 8-bit boundary


Mathieu little fix for syntax

 ------------------------------------------------------
update10092
 - FullScreen refactoring by mike Roberts
          - fixed a bug in PluggableListMorph>>basicKeyPress introduced in 10087 by Matthew Fulmer
          - improve SUnit history
          - Issue 235: 0007205: Monticello Snapshot Speedup via new MethodReference ivar
                        http://bugs.squeak.org/view.php?id=7205
       
       
 ------------------------------------------------------
update10093
 - Network fix by Yann Monclair
                Modified the deprecation comment on Url>>#toText. It was recommending using Url>>#asText instead, but that would mean the method would return a Text instead of a String as it currently does.
                I replaced the deprecation comment to recommend replacing #toText with #asString.
                All NetworkTests run green
        -    Fix by A. Bergel. The method PasteUpMorph>>findAPreferencesPanel:
is now an extension of MorphicExtras. Before it was part of Mophic-Worlds.
The reason to move findAPreferencesPanel: to MorphicExtras is  the method references PreferencesPanel, which is defined in MorphicExtras. PasteUpMorph calls findAPreferencesPanel: within PasteUpMorph>>defaultDesktopCommandKeyTriplets. The cycle is therefore not completely removed. However, defaultDesktopCommandKeyTriplets should be turned into a registration mechanism to completely remove the cycle.

        - allUnSentMessages -> allUnsentMessages, removeAllUnSentMessages -> removeAllUnsentMessages, allUnSentMessagesIn: -> allUnsentMessagesIn:

       
       
 ------------------------------------------------------
update10094
method categories cleanup by Lukas Renggli #241.
        - remove empty categories
        - sort all categories
        - make all categories lower case
        - replace #initialize-release/#class-initialization with #initialization
 ------------------------------------------------------
update10095
- Reorganization of the world menu and its sub-menus #185
- Kernel-Number fixes #245
- Replaced (Symbol allInstances) with (Symbol allSymbol) #227
- Duplicated methods in ClassTrait #140
- Remove #hash from Association (fix #testHash) #196
- Fix MC initialization broken by previous update
 ------------------------------------------------------
update10096
Issue 247: remove #hashMappedBy:
Issue 243: SMTPClient fix for authentication and support for EHLO (Mantis #6768)
Issue 233: fix for BreakPoint
Issue 229: remove preference Panel
 ------------------------------------------------------
update10097
Removed


        HaloMorph>>addScriptHandle:
        HaloMorph>>addViewHandle:


        Morph class>>additionsToViewerCategoryPenUse
        Morph class>>additionsToViewerCategoryObservation
        Morph class>>additionsToViewerCategoryMiscellaneous
        Morph class>>additionsToViewerCategoryMotion
        Morph>>isEtoyReadout
        Morph>>isaViewer
        Morph>>isTurtleRow
        Morph>>accumlatePlayersInto: aCollection andSelectorsInto: selectorsCollection
        Morph>>addStackItemsTo:
        Morph>>wrapWithAStack
        Morph>>abstractAModel
        Morph>>moveWithPenDownBy:
        Morph>>getPenColor
        Morph>>penUpWhile:
        Morph>>choosePenColor:
        Morph>>getPenDown
        Morph>>allMorphsWithPlayersDo:
        Morph>>appearsToBeSameCostumeAs:
        Morph>>addPlayerItemsTo:
        Morph>>containsCard:
        Morph>>getIndexInOwner
        Morph>>getPenSize
        Morph>>presentCardAndStackMenu
        Morph>>showBackgroundObjects
        Morph>>explainDesignations
        Morph>>insertCard
        Morph>>showForegroundObjects
        Morph>>goToNextCardInStack  
        Morph>>goToPreviousCardInStack
        Morph>>showForegroundObjects
        Morph>>selectorsForViewer
        Morph>>selectorsForViewerIn:
        Morph>>showPlayerMenu
        Morph>>becomeSharedBackgroundField
        Morph>>slotSpecifications
        Morph>>putOnForeground
        Morph>>putOnBackground
        Morph>>makeHoldSeparateDataForEachInstance
        Morph>>stopHolingSeparateDataForEachInstance
        Morph>>viewMorphDirectly
        Morph>>wrap
        Morph>>fenceEnabled

        Object>>isUniversalTiles
        Object>>isPlayerLike

        PasteUpMorph>>notePenDown: penDown forPlayer: player at: location
        PasteUpMorph>>updateTrailsForm
        PasteUpMorph>>drawPenTrailFor: aMorph from: oldPoint to: targetPoint
        PasteUpMorph>>addStackMenuItems:hand:
        PasteUpMorph>>presentCardAndStackMenu
        PasteUpMorph>>liftAllPens
        PasteUpMorph>>lowerAllPens
        PasteUpMorph>>linesForAllPens
        PasteUpMorph>>linesAndArrowsForAllPens
        PasteUpMorph>>dotsForAllPens
        PasteUpMorph>>addPenTrailsMenuItemsTo:
        PasteUpMorph>>arrowsForAllPens
        PasteUpMorph>>trailStyleForAllPens:
        PasteUpMorph>>printVocabularySummary
        PasteUpMorph>>clearTurtleTrails
        PasteUpMorph>>fenceEnabled
        PasteUpMorph>>fenceEnabled:
        PasteUpMorph>>toggleFenceEnabled
        PasteUpMorph>>fenceEnabledString
        PasteUpMorph>>
        PasteUpMorph>>
        PasteUpMorph>>browseAllScriptsTextually
        PasteUpMorph>>abandonCostumeHistory
       
        Pen>>arrowHeadFrom: prevPt to: newPt forPlayer: aPlayer
       
        PluggableTextMorphWithModel>>newTextContents:
        PluggableTextMorph>>selectionAsTiles
        PluggableTextMorph>>tileForIt
       
        Preferences>>fenceEnabled
       
        Quadrangle class>>exampleInViewer
       
        TextMorph>>setAllButFirstCharacter:
        TextMorph>>insertContentsOf:
       
        ScrollableField>>insertContentsOf:
       
        TransformationB2Morph
       
        ParagraphEditor>>selectionAsTiles
       
        TheWorldMainDockingBar>>clearTurtleTrails
        TheWorldMainDockingBar>>eToyVocabularySummary
        TheWorldMainDockingBar>>hideAllViewers
        TheWorldMainDockingBar>>hideAllViewersIn:
        TheWorldMainDockingBar>>showAllViewers
        TheWorldMainDockingBar>>clearTurtleTrails

 ------------------------------------------------------
update10098

       
        fixed taggings of senders with package
        deprecated statsWith:
        integrating fixes of gary in proportionalSplitterMorph so that
        Moprh x and y can be removed
 ------------------------------------------------------
update10099

       
        # fix menu debug in morph
       
        # 258 This changeset removes the following unused methods:

Object removeSelector: #basicAddInstanceVarNamed:withValue:!
Object removeSelector: #bindWithTemp:!
Object removeSelector: #handledListVerification!
Object removeSelector: #propertyList!

        # 255 by pavel
        WorldState >> doDeferredUpdatingFor: uses instance veriable remoteServer.
This instance variable can be removed completely.

        # 257
        http://bugs.squeak.org/view.php?id=7059
        In the Object Explorer, the menu item explore pointers is broken...
        It opens on an empty String.
        This is a patch from matthewf
       
        Harvested ProportionalSplitterMorph>>overlaps* from Polymorph
        because we got a DNU when we moved the splitter but now the splitter is broken :(
       
       
 ------------------------------------------------------
update10100

       
        # Really fix menu debug in morph
       
        # Correctly deprecates startsWith: (now it returns the right value)
       
        # Removed
                Morph>>newCard
                PasteUpMorph>>batchPenTrails
                PasteUpMorph>>batchPenTrails: ( and friends)
       
                PreferenceClass>>batchPenTrails

       
 ------------------------------------------------------
update10101

       
        # Removing other pen stuff

       
 ------------------------------------------------------
update10102
- Issue 277: SelfEvaluating Arrays
        -  {$a. Array. 1} instead of {$a . Array . 1}
- Issue 265: TODO: (simple): remove Browser "printOut" menu
- Issue 251: remove ref Parser from getSourceFor:in:
- Issue 249: add regexps to core image
       
 ------------------------------------------------------
update10104
Monadic ifNil
 ------------------------------------------------------
update10105
 - Sunit lr fixes
           - splitter morph fixes
           - Issue 279: fix: browseAllUnsentMessages
 ------------------------------------------------------
update10106
 - Monticello lukas enh (now we can sort the list)
           - Kedama random clean
           - New compiler tests
           - Regex valueOrUnwindDo: fixes
 ------------------------------------------------------
update10107
 - This provides a Fix and Test for String numArgs
                http://code.google.com/p/pharo/issues/detail?id=237
        - Nicolas Cellier: Just a small improvment required to speed up a little number reading:
rewrite a condition (a & b) as (a and: [b]).
        - Issue 275: TODO: remove OldSocket.
                Change HTTPSocket superclass from OldSimpleClientSocket to Socket.
                Reimplementing OldSocket protocol into Socket (some methods were missing).
                Changing CrLf variable access to (String crlf).

 ------------------------------------------------------
update10108
 - removing some unsent methods from etoy s to reduce the fat.

 ------------------------------------------------------
update10109
 - removing etoy -> ClassDescription
           - isUniClass senders and implementors

 ------------------------------------------------------
update10110
Issue 284: add literalsDo: as deprecated method
Issue 253: Mantis 6933 MultiByteFileStream upTo: does not work in binary mode
Issue 252: Mantis 6812 cannot inspect a WeakSet
- add back deprecated #literalsDo:
 ------------------------------------------------------
update10111
 - Debugger etoy removal
           - remove etoyFriendly preference
           - red/green for conflicts in MC (damien Pollet)
       
 ------------------------------------------------------
update10112
Issue 260: TODO: cleanup hasLiteralThorough:
 ------------------------------------------------------
update10113
- FileDirectory etoy cleaning
          - Project / ThreadNavigation method cleaning
 ------------------------------------------------------
update10114
- Issue 274: TwoWayScrollPane shoud be removed
- Issue 291: SystemNavigation tests + reimplementation for queries on sent and unsent messages
- Issue 290: SUnit Enhancement to ease writing tests involving the creation of classes
 ------------------------------------------------------
update10115
- Issue 274: TwoWayScrollPane shoud be removed
- Issue 291: SystemNavigation tests + reimplementation for queries on sent and unsent messages
- Issue 290: SUnit Enhancement to ease writing tests involving the creation of classes
 ------------------------------------------------------
update10116
- Issue 185: More World menu cleanup needed (includes the following improvements:  mouse-over sub-menus, capitalize tool names, exchange single with double change sorter)
- Issue 282: Increase default window sizes
- Issue 283: Remove fonts and change default font choices
- ScriptLoader>>cleanUpForRelease: flushes a lot of caches and deletes bitmaps from EToys to decrease the memory footpring
 ------------------------------------------------------
update10117
-  Issue 293: SystemNavigation UI + bug fixes
           - Installer installer in scriptloader updated
           - Issue 297: MethodReference printOn enhance
           - Etoy unsentMessages removed!!!!! :)

 ------------------------------------------------------
update10118
- fix script loading broken.
        Issue 294: VM does not send script files to image
 ------------------------------------------------------
update10119
- fix script loading broken.
        Issue 294: VM does not send script files to image
 ------------------------------------------------------
update10120
- Etoy removal
                TextMorph
                ThumbnailMorph
                TileMorphTest
                TraitDescription
                UndefinedObjectTest
                UpdatingStringMorph
                Vocabulary
 ------------------------------------------------------
update10121
- Etoy clean up FileList2 and other little left over
 ------------------------------------------------------
update10122
- Merging Type Hierarchy removal second attempt
 ------------------------------------------------------
update10123
- Stef and David Hacking on Morph etoy Removal
                - moved ScriptEditorMorph -> Etoy
 ------------------------------------------------------
update10124
- Revert to Accuny as the default font and remove the other font from the system
 ------------------------------------------------------
update10125
Issue 303: TODO: remove profiling methods
Issue 300: unimplemented call in AlignmentMorphBob1>>acceptDroppingMorph:event:
Issue 299: Mantis 007007 and 007008 correct toggle break on entry
 ------------------------------------------------------
update10126
-> Issue 248: SLICE-Mantis-ScaledDecimal-SqNumberParser-Fix-nice.1
-> Issue 295: #testSupplyAnswerUsingRegexMatchOfQuestion fails
-> latest collection tests
 ------------------------------------------------------
update10129
- delete unused vars in Morphic (Lukas R.)
- fix loop of liked list test (Damien P.)
 ------------------------------------------------------
update10129
Various etoy cleaning
 ------------------------------------------------------
update10130
313: FileList2 crashes if some subdirectory present
 ------------------------------------------------------
update10132
Fix some tests (duplicated methods from traits)
 ------------------------------------------------------
update10132
Removed

ccg:emitLoadFor:from:on:
ccg:generateCoerceToOopFrom:on:
ccg:generateCoerceToValueFrom:on:
ccg:prolog:expr:index:
 ------------------------------------------------------
update10134
- copyrith removed
- MC enh from lukas
- Dictionary Collect
This is http://bugs.squeak.org/view.php?id=7095
and http://code.google.com/p/pharo/issues/detail?id=292

Fix Dictionary>>collect: to return a Dictionary of mapped values (instead of an OrderedCollection).

Also provide tests for #select:, #reject:, and #collect: which should all behave in a similar way
 ------------------------------------------------------
update10135
- Issue 83: squeakToUtf8 and utf8ToSqueak convenience methods
- improved ScriptLoader robustness
 ------------------------------------------------------
update10136
Issue 305: TODO: garbage collection parameters
Issue 312: Typo in PasteUpMorph>>keyboardNavigationHandler
Issue 309: Color>hex: should be brought back
Issue 306: file stream not closed after drag and drop of CS
in postscript:
(Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil
changeSelector: nil.
 ------------------------------------------------------
update10137
simple etoy cleaning from gary list.
 ------------------------------------------------------
update10138
HaloMorphEtoyCleaning
 ------------------------------------------------------
update10139
EtoyUnsentMessageRemoval
 ------------------------------------------------------
update10140
Object etoy cleaning (treated so far)
        ? assured
        ? beViewed
        ? belongToUniClass
        ? browseOwnClassSubProtocol
        ? categoriesForViewer:
        ? categoriesForVocabulary: aVocabulary limitClass: aLimitClass
        ? chooseNewNameForReference
        ? defaultLimitClassForVocabulary:
        ? eToyStreamedRepresentationNotifying:
        ? infoFor: anElement inViewer: aViewer


Object (to fix later so far)
        ? presenter
        ? currentVocabulary
        ? defaultNameStemForInstances
 ------------------------------------------------------
update10141
3 timesRepeat: [SystemNavigation default removeUnsentMessagesWithProgressBarInPackageNamed: EToys]
 ------------------------------------------------------
update10142
Issue 317: lessMethodSendsInFontUsage
Issue 301: UIManager enhacements
 ------------------------------------------------------
update10143
- fix dropFrom:
- etoy removal fight

 ------------------------------------------------------
update10144
- ifNotNilDo: calls renamed
- Issue 232: Recreate Special Objects Array should preserve external semaphores + Fix

 ------------------------------------------------------
update10145
- Issue273-EmbeddedWorldBorderMorph-removal
 ------------------------------------------------------
update10146
-Issue 219: Cryptography does not load into Pharo
 ------------------------------------------------------
update10147
-etoy cleaning event etoy and autoexpansion
 ------------------------------------------------------
update10148
- Etoy cleaning (la nausee)
 ------------------------------------------------------
update10149
Morph removed
        couldHoldSeparateDataForEachInstance
        currentDataInstance
        goToPreviousCardInStack
        insertCard
        installAsCurrent:
        reshapeBackground
        relaxGripOnVariableNames
        reassessBackgroundShape
        stack
        stackDo:
        isStackBackground
        setAsDefaultValueForNewCard
        isPlayer: aPlayer ofReferencingTile: tile
        traverseRowTranslateSlotOld: oldSlotName of: aPlayer to: newSlotName
        traverseRowTranslateSlotOld: oldSlotName to: newSlotName
        openViewerForArgument
        handMeTilesToFire
        triggerScript:
        variableDocks
        shouldRememberCostumes
        currentDataValue
        newPlayerInstance
        isSyntaxMorph
        enclosingEditor
        topEditor
Morph fixed
        tryToRenamed:
        tabHitWithEvent:
PasteUpMorph removed
        scriptSelectorToTriggerFor:
        viewerFlapTabFor:
 ------------------------------------------------------
update10150
-> Issue 333: A fix for animated GIF harvested from Squeak
        -> Mantis 0006343: Process does not need to be a special object
        Change proposed by martin v. Loewis:
        When changing Process, I was warned that it is a special object and therefore
        it is dangerous to change its class definition. Process currently lives
        at: 28 of Smalltalk specialObjectsArray. In reviewing all references to
        the special objects array, I could not find any reference to that slot,
        neither in the Squeak 3.9 image nor in the VM.
        -> Postscript: Smalltalk recreateSpecialObjectsArray.

 ------------------------------------------------------
update10151
-> Issue 146: ClassDescription>>copyUnobstrusevely
        ClassDescription>>copyUnobstrusevely  and friends are only invoked by kedama which should be removed
-> Issue 128: M5711: TextFieldMorph changes text position when emptied
-> now really do Postscript: Smalltalk recreateSpecialObjectsArray.

 ------------------------------------------------------
update10152
-> Issue 276: candidate for core: Process-specific variables
        Martin von Loewis did a nice implementation of thread-specific variables:
        This project provides process-specific variables (called TLS - thread-local storage)
        in other environments. Two kinds of variables are provided: ProcessLocalVariable (similar to TLS),
        and DynamicVariables (akin LISPs dynamic scope)
 ------------------------------------------------------
update10153
Issue 308: Mac Menu support
 ------------------------------------------------------
update10156
ssue 195: Unicode membership test reduced to String #= (String #compare:caseSensitive:) ? M6336
 ------------------------------------------------------
update10157
-> Issue 84: 7136 TraitBehavior-2-dc
-> Issue 246: fix classVariableNames
 ------------------------------------------------------
update10158
- remove preferences twentyFourHourFileStamps, universalTiles, uniTilesClassic, eToyFriendly
  - remove many classes from Etoys, remove unsent methods.    
        - undo removal of Process from spclobjects
 ------------------------------------------------------
update10159
- Morph Etoy cleaning A->D
Object
        currentVocabulary

Morph
        appearsToBeSameCostumeAs:
        arrowDeltaFor:
        automaticViewing
        bringTileScriptingElementsUpToDate
        bringUpToDate
        buttonProperties
        buttonProperties: propertiesOrNil
        color: sensitiveColor sees: soughtColor
        colorUnder
        currentVocabulary
        hasButtonProperties
       
        ensuredButtonProperties
        isTileScriptingElement
       
PasteUpMorph
     currentVocabulary
     currentVocabularyFor:
 ------------------------------------------------------
update10160
-> remove more etoy classes (mostly tiles related)
-> 3 timesRepeat: [SystemNavigation default removeUnsentMessagesWithProgressBarInPackageNamed: EToys]
 ------------------------------------------------------
update10161
->Issue 323: look at all the senders of noviceMode and try to remove this preference
-> remove more etoy classes (mostly tiles related)
-> SystemNavigation default removeUnsentMessagesWithProgressBarInPackageNamed: EToys
-> remove preferences:
        Preferences removePreference: #simpleMenus.
Preferences removePreference: #mvcProjectsAllowed.
Preferences removePreference: #uniTilesClassic.
Preferences removePreference: #universalTiles.
Preferences removePreference: #typeCheckingInTileScripting.
Preferences removePreference: #eToyFriendly.
Preferences removePreference: #eToyLoginEnabled.
Preferences removePreference: #useVectorVocabulary.
Preferences removePreference: #noviceMode.
Preferences removePreference: #dropProducesWatcher.

 ------------------------------------------------------
update10162
More etoys/vocabulary cleans
 ------------------------------------------------------
update10163
-> added loading script for polymorph UI (Torsten Bergmann)
-> clean up cass "TheWorldMenu" a little (me)
-> Issue 339: Process stuck in 10156+OB?, 100% cpu load after ScriptLoader loadOB on macintosh only
 ------------------------------------------------------
update10164
Morph D->I cleaning
        defaultVariableName
        doMenuItem:
        noteNegotiatedName: uniqueName for: requestedName
     variableDocks

- SUnit extension (icon)
 ------------------------------------------------------
update10165
Stef and Damien happily adding tests to Array, OrderedCollection, Set, Bag, String, Symbol, Dictionary
based on traits
TIncludesTest, TCloneTest, TCopyTest
 ------------------------------------------------------
update10166
Simon fixes to icons tests No author pop up
 ------------------------------------------------------
update10167
- clean more Preferences (Marcus Denker)
          - Scriptloader Seaside loading methods (Torsten Bergmann)
          - Postscript: (Preferences preferenceAt:
#allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil.
        Preferences removePreference: #batchPenTrails.
Preferences removePreference: #allowEtoyUserCustomEvents.
Preferences removePreference: #automaticViewerPlacement.
Preferences removePreference: #capitalizedReferences.
Preferences removePreference: #fenceEnabled.
Preferences removePreference: #keepTickingWhilePainting.
Preferences removePreference: #tileTranslucentDrag.
Preferences removePreference: #translationWithBabel.
Preferences removePreference: #useButtonProprtiesToFire.
Preferences removePreference: #alphabeticalProjectMenu.
Preferences removePreference: #showAdvancedNavigatorButtons.
Preferences removePreference: #ignoreStyleIfOnlyBold.
Preferences removePreference: #propertySheetFromHalo.
 ------------------------------------------------------
update10173
-> clean Preferences more (see postscript)
-> clean Protocol. Delete unused classes: MethodInterface, MethodWithInterface, remove all implementors of #vocabularyDemanded.
-> clean Smallland Colorschems. Delete class SmallLandColorTheme and all 8 subclasses
-> Postscript:
Preferences removePreference: #twentyFourHourFileStamps.
Preferences removePreference: #showProjectNavigator.
Preferences removePreference: #viewersInFlaps.
Preferences removePreference: #compactViewerFlaps.
Preferences removePreference: #classicNavigatorEnabled.
Preferences removePreference: #navigatorOnLeftEdge.
Preferences removePreference: #changeSetVersionNumbers.
Preferences removePreference: #browseWithDragNDrop.
 ------------------------------------------------------
update10174
-> modify MCPackageLoader>>basicLoad for loading Polymorph
          -> delete some more unused classes in etoys (could not resist) ;-)
 ---------------------------------...etc...
On Dec 1, 2009, at 3:19 PM, Tim Mackinnon wrote:

> So can can I see this somewhere? I was expecting on the download page there would be a link to show me what changes have been fixed in that release. ( even a list so that I can filter on 9.11.4 - and then see that #11504,11523... is included etc. would be fine).
>
> Maybe in the future there might be some way to do something like the Trac guys do - where they have the convention that their SVN commit comments (I guess this could be MCZ comments or naming convention) include the ticket id number of the bug/feature they are fixing - they can then generate a list of whats in a build - and when you do a release, whats in the release. e.g. look at the following page on their website: http://trac.edgewall.org/wiki/TracL10N (press the edit button and see how they are querying out the outstanding tickets for a release). Is this what Mason and the things mentioned do?
>
> The best system I have seen running was Trac with Hudson - however all these things are doable in any system (the ones mentioned here sound interesting).
>
> I would just like to see something concrete so I can try and help in some way to make sure that V1.0 is stable and as bug free as possible.
>
>
> Tim


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
In reply to this post by Tim Mackinnon
you can use the google interface to get access to what is closed in 1.1

Stef


On Dec 1, 2009, at 11:03 AM, Tim Mackinnon wrote:

> Actually I am thinking of something like the following (this is JBoss - they use Jira - which is free for open source projects, although I find it a bit clunky - but it gives an idea. I have actually seen Trac - the wiki and ticket system used very effectively);
>
> This link shows all of their version for the JBoss Web project:
> https://jira.jboss.org/jira/browse/JBWEB?report=com.atlassian.jira.plugin.system.project:versions-panel
>
> This link shows what was fixed in 2.1.1 GA
> https://jira.jboss.org/jira/browse/JBWEB/fixforversion/12312592
>
> I guess I am thinking that when I see the following in this list (from Marcus) - this information should appear somewhere as the things that were fixed in 9.11.5?
> 11066
> -----
>
> Issue 1526: remove #addInstanceVarNamed:withValue:
> Issue 1518: #abbreviatedBrowserButtons should be removed
> Issue 476: [Pending Etoy Cleaning] Object>>knownName
> Issue 1520: remove global References
>
>
> Tim
>
> On 30 Nov 2009, at 22:34, Michael Roberts wrote:
>
>> do you mean the svn thing? you can mark files in the repository in a
>> way that updates the issue tracker.  I haven't tried it (we have no
>> files) but the docs look straightforward. It's meant for projects that
>> actually keep their source in the repository, but I think we could
>> have a dummy file that acted the same way. It would be a logical
>> closure for each issue to mark it with the update. That way it is
>> external to the image and gives the full life cycle on the tracker
>> which I think would be useful.
>>
>> cheers Mike
>>
>> On Mon, Nov 30, 2009 at 11:03 PM, Stéphane Ducasse
>> <[hidden email]> wrote:
>>> I do not get it?
>>> Can you explain how this works?
>>> Because right now you take ScriptLoader and you get the log of all the issue that have been integrated.
>>>
>>> Stef
>>>
>>> On Nov 30, 2009, at 10:48 PM, Michael Roberts wrote:
>>>
>>>> you can check the log of the script loader.  I don't have the code to
>>>> hand but check the state of the singleton I think.
>>>>
>>>> It might be nice in the future to use the google SVN feature to tag
>>>> issues with the image update as we close them.
>>>>
>>>> cheers,
>>>> Mike
>>>>
>>>> On Mon, Nov 30, 2009 at 10:24 PM, Tim Mackinnon <[hidden email]> wrote:
>>>>> Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material).
>>>>>
>>>>> Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1?
>>>>>
>>>>> Tim
>>>>> _______________________________________________
>>>>> Pharo-project mailing list
>>>>> [hidden email]
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Marcus Denker-3
In reply to this post by Tim Mackinnon
Hello,

Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And.
We will do all that, but not today :-)

        Marcus

On Dec 1, 2009, at 3:19 PM, Tim Mackinnon wrote:

> So can can I see this somewhere? I was expecting on the download page there would be a link to show me what changes have been fixed in that release. ( even a list so that I can filter on 9.11.4 - and then see that #11504,11523... is included etc. would be fine).
>
> Maybe in the future there might be some way to do something like the Trac guys do - where they have the convention that their SVN commit comments (I guess this could be MCZ comments or naming convention) include the ticket id number of the bug/feature they are fixing - they can then generate a list of whats in a build - and when you do a release, whats in the release. e.g. look at the following page on their website: http://trac.edgewall.org/wiki/TracL10N (press the edit button and see how they are querying out the outstanding tickets for a release). Is this what Mason and the things mentioned do?
>
> The best system I have seen running was Trac with Hudson - however all these things are doable in any system (the ones mentioned here sound interesting).
>
> I would just like to see something concrete so I can try and help in some way to make sure that V1.0 is stable and as bug free as possible.
>
>
> Tim
>
> On 1 Dec 2009, at 12:35, Stéphane Ducasse wrote:
>
>> this is what we do also.
>>
>> On Dec 1, 2009, at 2:03 AM, Dale Henrichs wrote:
>>
>>> In the google issues list, one can add a column called "Fixed" and a version can be supplied for the value of that field (like Version or Milestone) when the bug is fixed ... I think this is what Tim is getting at. I've just done this for Metacello, since I think it is a good idea:)
>>>
>>> Dale
>>> ----- "Tim Mackinnon" <[hidden email]> wrote:
>>>
>>> | Hi guys - I noticed there was a new 9.11.4 release since buenos aires
>>> | - and I got to wondering what issues have been resolved in it (as I am
>>> | trying to follow Pharo by example - I am trying to test out features
>>> | to see if they work as I progress through the material).
>>> |
>>> | Anyway - is there a list of issues fixed marked against each new
>>> | version? I can see the list at:
>>> | http://code.google.com/p/pharo/issues/list# - but it doesn't list any
>>> | build numbers - just milestone 1.1?
>>> |
>>> | Tim
>>> | _______________________________________________
>>> | Pharo-project mailing list
>>> | [hidden email]
>>> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

csrabak
Marcus,

This brings a question to me: is there a sort of API or web service we could use (obviously
for calling from inside Pharo) to post at the Pharo's Twitter account?

I surmise that doing that for the blog would be 'easier' :-)

--
Cesar Rabak
 

Em 04/12/2009 10:09, Marcus Denker < [hidden email] > escreveu:


Hello,

Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And.
We will do all that, but not today :-)

 Marcus

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
we can use soap for example and I would really like to have an nice example :)

Stef
On Dec 4, 2009, at 7:55 PM, [hidden email] wrote:

> Marcus,
>
> This brings a question to me: is there a sort of API or web service we could use (obviously
> for calling from inside Pharo) to post at the Pharo's Twitter account?
>
> I surmise that doing that for the blog would be 'easier' :-)
>
> --
> Cesar Rabak
>
>
> Em 04/12/2009 10:09, Marcus Denker < [hidden email] > escreveu:
>
>
> Hello,
>
> Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And.
> We will do all that, but not today :-)
>
> Marcus
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Marcus Denker-3
In reply to this post by csrabak

On Dec 4, 2009, at 7:55 PM, [hidden email] wrote:

> Marcus,
>
> This brings a question to me: is there a sort of API or web service we could use (obviously
> for calling from inside Pharo) to post at the Pharo's Twitter account?
>
> I surmise that doing that for the blog would be 'easier' :-)

Hmm... twitter has a REST style API: http://apiwiki.twitter.com/Twitter-API-Documentation

This should not be too difficult to use from within Pharo...

        Marcus
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Lukas Renggli
There is a Pier plugin with a nice model for Twitter at
http://source.lukas-renggli.ch/pieraddons, examples can be seen on the
front-page of ese.unibe.ch and lukas-renggli.ch.

I use the plugin mostly to pull public timelines, but it would be easy
to adapt to also post tweets. Below a shell script that could be
adapted:

curl --quiet --user "${USERNAME}:${PASSWORD}" --data
status="${MESSAGE}" "${URL}"

Cheers,
Lukas

2009/12/5 Marcus Denker <[hidden email]>:

>
> On Dec 4, 2009, at 7:55 PM, [hidden email] wrote:
>
>> Marcus,
>>
>> This brings a question to me: is there a sort of API or web service we could use (obviously
>> for calling from inside Pharo) to post at the Pharo's Twitter account?
>>
>> I surmise that doing that for the blog would be 'easier' :-)
>
> Hmm... twitter has a REST style API: http://apiwiki.twitter.com/Twitter-API-Documentation
>
> This should not be too difficult to use from within Pharo...
>
>        Marcus
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

csrabak
In reply to this post by Stéphane Ducasse
OK! I'll swamped until the end of this week, but will look for information on
this approach.  I think I'll need to assemble an account in Twitter for myself
also :-|

--
Cesar Rabak


Em 05/12/2009 08:28, Stéphane Ducasse < [hidden email] > escreveu:


we can use soap for example and I would really like to have an nice example :)

Stef
On Dec 4, 2009, at 7:55 PM, [hidden email] wrote:

> Marcus,
>
> This brings a question to me: is there a sort of API or web service we could use (obviously
> for calling from inside Pharo) to post at the Pharo's Twitter account?
>
> I surmise that doing that for the blog would be 'easier' :-)
>
> --
> Cesar Rabak
>
>
> Em 04/12/2009 10:09, Marcus Denker < [hidden email] > escreveu:
>
>
> Hello,
>
> Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And.
> We will do all that, but not today :-)
>
> Marcus
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: How do I know which issues are resolved in each new release?

Stéphane Ducasse
would be cool. :)

On Dec 5, 2009, at 7:45 PM, [hidden email] wrote:

> OK! I'll swamped until the end of this week, but will look for information on
> this approach.  I think I'll need to assemble an account in Twitter for myself
> also :-|
>
> --
> Cesar Rabak
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project