Re: [Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows

[pharo]

Comment #6 on issue 3458 by torsten@astares.de: bug in the class  
MultiByteFileStream when Pharo running under Windows

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

When I try "Pharo-1.1.1--Latest update: #11414"

and run

(MultiByteFileStream new)
 wantsLineEndConversion: true;
 open: 'c:\temp\1.txt' forWrite: true;
 cr;
 close.

I get a file with hex: 0D 0A 0A

So it existed in 1.1 already and looks like it is not a show stopper.
Marcus: You should move it to 1.3

Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

[pharo]

Comment #3 on issue 3420 by torsten@astares.de:  
ReleaseTest>>#testUndeclared is failing

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

Anyone contacted Lukas already? HDLintReport is a class from his Hudson  
interface, is'nt it?

Re: [Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows

[pharo]

Updates:
Labels: -Milestone-1.2 Milestone-1.3

Comment #7 on issue 3458 by marcus.d...@gmail.com: bug in the class  
MultiByteFileStream when Pharo running under Windows

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

Moved to 1.3

Re: [Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error

[pharo]

Updates:
Cc: marcus.denker

Comment #2 on issue 3534 by torsten@astares.de:  
LargePositiveInteger(Object)>>error

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

Didnt have the problem with the latest Cog but it may still be there ...

Suggest to move it to 1.3. (we deliver 1.2 with standard VM, dont we?)
If we see it again we can patch 1.2 anyway.

Re: [Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error

[pharo]

Comment #3 on issue 3534 by marianopeck: LargePositiveInteger(Object)>>error
http://code.google.com/p/pharo/issues/detail?id=3534

Torsten, can you check if this is the same bug that Mattew reported to  
Eliot? It seems the same bug, in such case, it is a Cog bug and Eliot said  
he was going to release a new VM during the weekend

Re: [Pharo-project] Gofer issue

[Igor Stasenko]

On 20 January 2011 22:52, Lukas Renggli  wrote:
>>> Following the coventions your name is 'Igor' and the package is on the
>>> branch 'Stasenko'. Gofer proritizes the main branch.
>>
>> how about retrieving the latest version regardless of branch?
>> Can you provide an example how to tell Gofer to load it?
>
> There is no such thing as the latest version in Monticello, unless you
> download all versions and compare the timestamps.
>

why you saying like that? If i open this repo in monticello browser, i
can clearly see what is the latest
uploaded version. And i sure that MC browser does not downloads all
versions from repository.
So, why i can't instruct Gofer to load it?


>> okay, i doing:
>>
>> Gofer new
>>        url: 'http://squeaksource.com/VMMaker';
>>        package: 'VMMaker-oscog';
>>          resolved
>>
>>  an Array(a GoferResolvedReference name: 'VMMaker-oscog-Igor.Stasenko.47')
>>
>> hmm.. that doesn't looks right, isnt? Because as you said,
>> following the coventions author's name is 'Igor' and the package is on the
>>  branch 'Stasenko'
>
> Obviously you must have 'VMMaker-oscog-Igor.Stasenko.47' in your package 
> cache.
>
yes, i will upload it shortly.
And that strange too, since i told to get the latest version from
'http://squeaksource.com/VMMaker',
not from cache. But that probably ok.

> For me I get 'VMMaker-oscog-Igor.Stasenko.43', because there are only
> two versions of the package 'VMMaker-oscog' in
> : 'VMMaker-oscog-Igor.Stasenko.43'
> and 'VMMaker-oscog-Igor.Stasenko.38'. Looks as expected.
>
humm.. what about rest
VMMaker-oscog* versions?


> Lukas
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
>



-- 
Best regards,
Igor Stasenko AKA sig.

Re: [Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error

[pharo]

Updates:
Labels: -Milestone-1.2 Milestone-1.3

Comment #4 on issue 3534 by marcus.d...@gmail.com:  
LargePositiveInteger(Object)>>error

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

ok, I move it to 1.3

Re: [Pharo-project] Issue 3513 in pharo: Failing Test:ClosureTests.testWhileWithTempIsNil

[pharo]

Comment #1 on issue 3513 by marcus.d...@gmail.com: Failing  
Test:ClosureTests.testWhileWithTempIsNil

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

related to Issue 2360

Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

[pharo]

Comment #4 on issue 3420 by marcus.d...@gmail.com:  
ReleaseTest>>#testUndeclared is failing

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

I will for now just try to delete the class in the build script (hehe ;-)

[Pharo-project] Issue 3563 in pharo: PCCByCompilationTest tests sometimes fail randomly

[pharo]

Status: Accepted
Owner: marcus.d...@gmail.com
Labels: Milestone-1.2 Milestone-1.3

New issue 3563 by marcus.d...@gmail.com: PCCByCompilationTest tests  
sometimes fail randomly

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

PCCByCompilationTest tests sometimes fail randomly

[Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

[pharo]

Status: Accepted
Owner: johanbri...@me.com
Labels: Milestone-1.2

New issue 3564 by johanbri...@me.com: Comparison of source references (for  
sorting)

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

Not all SourceReference subclasses implement <=

Steps to reproduce:
1. search method source with 'CustomMenu'
2. hit bug

Re: [Pharo-project] Gofer issue

[Hernán Morales Durand]

Hi Igor,

2011/1/21 Igor Stasenko :
> On 20 January 2011 22:52, Lukas Renggli  wrote:
 Following the coventions your name is 'Igor' and the package is on the
 branch 'Stasenko'. Gofer proritizes the main branch.
>>>
>>> how about retrieving the latest version regardless of branch?
>>> Can you provide an example how to tell Gofer to load it?
>>
>> There is no such thing as the latest version in Monticello, unless you
>> download all versions and compare the timestamps.
>>
>
> why you saying like that? If i open this repo in monticello browser, i
> can clearly see what is the latest
> uploaded version. And i sure that MC browser does not downloads all
> versions from repository.

I didn't checked the source code but it seems MC repository inspector
always sort the package list by version number and when you save a
package in the Monticello Browser you can edit the version number and
write a lower number, then you cannot concede the first in the list is
the latest cronologically. I don't know why the version number is
editable though.

Hernán

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

[pharo]

Updates:
Labels: Milestone-1.3

Comment #3 on issue 3179 by marcus.d...@gmail.com: Failing Tests for  
Monticello

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

[pharo]

Updates:
Labels: Milestone-1.3

Comment #4 on issue 3419 by marcus.d...@gmail.com:  
TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

[pharo]

Updates:
Labels: Milestone-1.3 Milestone-1.1.1

Comment #5 on issue 3420 by marcus.d...@gmail.com:  
ReleaseTest>>#testUndeclared is failing

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3513 in pharo: Failing Test:ClosureTests.testWhileWithTempIsNil

[pharo]

Updates:
Labels: Milestone-1.3

Comment #2 on issue 3513 by marcus.d...@gmail.com: Failing  
Test:ClosureTests.testWhileWithTempIsNil

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

[pharo]

Updates:
Labels: Milestone-1.3

Comment #5 on issue 3520 by marcus.d...@gmail.com: Workspaces do not  
recognize previously evaluated temps

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

[pharo]

Updates:
Labels: Milestone-1.3

Comment #3 on issue 3556 by marcus.d...@gmail.com:  
PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

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

(No comment was entered for this change.)

[Pharo-project] MacMenubarPlugin does not work on Cog?

[Mariano Martinez Peck]

Hi. I am testing a Pharo image from here:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/Pharo-1.2.zip

and the Mac host menu doesn't appear at all. I checked with

SmalltalkImage current listLoadedModules
SmalltalkImage current listBuiltinModules

and MacMenubarPlugin is included. However, evaluating "HostSystemMenusMacOSX
new "   will throw a 'primDeleteMenu: failed'

Why the image doesn't throw any error???  Look in

HostSystemMenus >> startUp: resuming
resuming ifFalse: [^self].
self clearDefault.
[self setDefaultMenuProxyClass] ifError: [].

Soindeed, setDefaultMenuProxyClass is throwing an error...but we are
puting it under the carpet.

Anyway, does someone know why this is not working in Cog?  because In the
standard VM in works perfect.

Cheers

Mariano

[Pharo-project] [update 1.3] #13006

[Marcus Denker]

13006
-

Issue 3556: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

[pharo]

Updates:
Labels: Milestone-1.3

Comment #1 on issue 3564 by marcus.d...@gmail.com: Comparison of source  
references (for sorting)

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3464 in pharo: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

[pharo]

Updates:
Status: Closed

Comment #2 on issue 3464 by marianopeck: [Failing Test]  
ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

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

Doesn't fail anymore in
Pharo1.2beta
Latest update: #12303

Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

[pharo]

Updates:
Status: Closed

Comment #6 on issue 3420 by marcus.d...@gmail.com:  
ReleaseTest>>#testUndeclared is failing

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

workaround applied 1.1, 1.2 and 1.3 builds (Full and Core)

Re: [Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

[pharo]

Comment #4 on issue 3556 by stephane...@gmail.com:  
PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

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

(No comment was entered for this change.)

Attachments:
AAA-Pluggable.1.cs  4.6 KB

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

[pharo]

Comment #6 on issue 3520 by siguc...@gmail.com: Workspaces do not recognize  
previously evaluated temps

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

- this should fix the issue

Attachments:
workspace-bindings-fix.1.cs  869 bytes

Re: [Pharo-project] New chapter on OpenGL in Pharo

[Hernán Morales Durand]

2011/1/21 Javier Pimás :
> Hi! I just gathered many of my previous experiences trying to use opengl and
> uploaded it to the pharo book. It would be nice if someone could check the
> info, try to add more and mainly test the tips to see if they are working.

Link?

> With FFI OpenGL I'm getting an error while compiling a test method in Pharo

which error?

> 1.2 and some problems with underscore assignments and deprecations, we

which problems?

Menu -> System -> Settings
Write underscore, hit Enter
Check "Allow underscore as assignment"

To change all underscores _ to := install AST and RB and evaluate:

| environment change rule |
environment := BrowserEnvironment new forPackageNames: #('YourPackageName').
rule := RBUnderscoreAssignmentRule new.
SmalllintChecker runRule: rule onEnvironment: environment.
change := CompositeRefactoryChange new.
change changes: rule changes.
change execute

> should fix them but I don't think I have access to that repo. Also, loading
> it involves many steps, having a ConfigurationOfFFIOpenGL would be awsome.
> Please add anything you consider useful.
> Regards,
>           Javier.
>
> --
> Javier Pimás
> Ciudad de Buenos Aires
>

Re: [Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

[pharo]

Updates:
Status: Closed

Comment #5 on issue 3556 by marcus.d...@gmail.com:  
PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

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

in 13006 and 12315

Re: [Pharo-project] Instruments for headless images

[Sven Van Caekenberghe]

Igor,

Headless support is an important feature.
It should be something simple so that it can be used in many ways.
I would suggest to read chapter 20 of the VW Application Developers Guide (it 
is only 10 pages).

They basically have the option to toggle between headless and headfull.
This is not detected automatically, but a global switch (with a test method).

In headless mode all display access results in an error.
In headless mode all Transcript output (can/is) also sent to a file (stdout 
would be another option).

What is interesting (and we might make that an option) is that the 'no display' 
error results in the image being saved 'headfull' so that you can start it up 
using a display to debug it (suspended process/debugger). 
Saving a headless image headfull can also be done programmatically.

I don't think more than that is needed. There are many options to interact with 
headless images, forcing one on people would not be good, the same goes for 
command line parsing, preferences, startup files, ... These other options could 
become separate projects.

I would be an interested user and if I can will try to help.

Regards,

Sven

On 20 Jan 2011, at 21:39, Igor Stasenko wrote:

> Hello folks.
> 
> I'd like to ask, if there any 'standartized' instruments for headless
> images (or alike).
> 
> I need a simple things:
> - redirect all  ToolSet/UIManager messages to Transcript
> - redirect Transcript logging to file or stdout
> 
> in short, these tools should serve a simple, yet important purpose:
> - if image runs in headless mode, it should suppress anything which
> expecting user interaction (like showing warnings with 'continue'
> button) and either log such messages to file
> or simply quit image with error message.
> 
> Without such tool it is quite difficult to monitor, what happens with
> your headless image.. unless you have RFB installed.. but that is
> different and unrelated story.
> 
> 
> I did a prototype once for Hydra (you can check it at
> SqS/HydraVM/HydraVM.mcz package)
> there are two subclasses:
> - MorphicUIManager subclass: #HydraUIManager
> - StandardToolSet subclass: #HydraDebugToolSet
> 
> and
> - WriteStream subclass: #HydraTranscript
> 
> which can be installed as a Transcript.
> 
> And in order to prepare image to run in headless mode, i issued:
>   ToolSet unregister: StandardToolSet.
>   ToolSet register: HydraDebugToolSet.
>   UIManager default: HydraUIManager new.
> 
> Also, HydraTranscript
> startUp does something like:
> 
>   TranscriptStream
>   newTranscript: (self basicNew initialize
>   on: (String new: 1000))
> 
> 
> With that i could run the image in headless mode, knowing that in case
> of error or warning etc, all will be redirected to transcript,
> moreover i even stopped the UI process, so it never run on headless images.
> 
> I wonder if there are other work, which can offer similar,
> and is there any way to detect that image are running in headless mode?
> 
> 
> -- 
> Best regards,
> Igor Stasenko AKA sig.
> 

Re: [Pharo-project] Gofer issue

[Igor Stasenko]

On 21 January 2011 10:16, Hernán Morales Durand
 wrote:
> Hi Igor,
>
> 2011/1/21 Igor Stasenko :
>> On 20 January 2011 22:52, Lukas Renggli  wrote:
> Following the coventions your name is 'Igor' and the package is on the
> branch 'Stasenko'. Gofer proritizes the main branch.

 how about retrieving the latest version regardless of branch?
 Can you provide an example how to tell Gofer to load it?
>>>
>>> There is no such thing as the latest version in Monticello, unless you
>>> download all versions and compare the timestamps.
>>>
>>
>> why you saying like that? If i open this repo in monticello browser, i
>> can clearly see what is the latest
>> uploaded version. And i sure that MC browser does not downloads all
>> versions from repository.
>
> I didn't checked the source code but it seems MC repository inspector
> always sort the package list by version number and when you save a
> package in the Monticello Browser you can edit the version number and
> write a lower number, then you cannot concede the first in the list is
> the latest cronologically. I don't know why the version number is
> editable though.
>

Okay, i found the solution. Use Installer !

Installer monticello http: 'http://www.squeaksource.com';
 project: 'VMMaker';
 install: 'CMakeVMMaker'


works well for me and loads correct *latest* version.



> Hernán
>
>



-- 
Best regards,
Igor Stasenko AKA sig.

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

[pharo]

Updates:
Status: Fixed

Comment #5 on issue 3419 by jannik.l...@gmail.com:  
TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

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

Fixed for Pharo1.2
We remove the test
In SLICE-Issue-3419-TraitCompositionFail-janniklaval.1

[Pharo-project] Gofer issue

[Torsten Bergmann]

Lukas wrote:
>Looks good, but instead of duplicating the documentation I would
>rather just return the class comment from the help method.

Feel free to do so. I just wanted to point you to the fact
that you can already use the pier style notation to document 
stuff. 

Hope we will now see more docu popping up.

And it is now possible to easily extend the help system 
with other pragma/non pragma based help types. We could 
have others like  and the like in the future.


Some more notes on WikiStyleHelp:

   Currently it uses pier in  as default 
   since Alain provided the code for that but in the future 
   I would like to see more syntaxes. 

   Thats already prepared since you can also write 
http://portal.gmx.net/de/go/demail

[Pharo-project] [update 1.3] #13007

[Marcus Denker]

13007
-

Issue 3520: Workspaces do not recognize previously evaluated temps
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

[pharo]

Updates:
Status: Fixed

Comment #7 on issue 3520 by marcus.d...@gmail.com: Workspaces do not  
recognize previously evaluated temps

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues

[pharo]

Comment #1 on issue 3465 by marianopeck: Hundson OneClick: Does not show  
Mac menues

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

This is related with Cog. The same image works perfectly with a Standard VM.
---


Hi. I am testing a Pharo image from here:  
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/Pharo-1.2.zip


and the Mac host menu doesn't appear at all. I checked with

SmalltalkImage current listLoadedModules
SmalltalkImage current listBuiltinModules

and MacMenubarPlugin is included. However,  
evaluating "HostSystemMenusMacOSX new "   will throw a 'primDeleteMenu:  
failed'


Why the image doesn't throw any error???  Look in

HostSystemMenus >> startUp: resuming
resuming ifFalse: [^self].
self clearDefault.
[self setDefaultMenuProxyClass] ifError: [].

Soindeed, setDefaultMenuProxyClass is throwing an error...but we are  
puting it under the carpet.


Anyway, does someone know why this is not working in Cog?  because In the  
standard VM in works perfect.


Cheers

Mariano

Re: [Pharo-project] Instruments for headless images

[Igor Stasenko]

On 21 January 2011 11:04, Sven Van Caekenberghe  wrote:
> Igor,
>
> Headless support is an important feature.
> It should be something simple so that it can be used in many ways.
> I would suggest to read chapter 20 of the VW Application Developers Guide (it 
> is only 10 pages).
>
> They basically have the option to toggle between headless and headfull.
> This is not detected automatically, but a global switch (with a test method).
>
> In headless mode all display access results in an error.

yes.

> In headless mode all Transcript output (can/is) also sent to a file (stdout 
> would be another option).
>
yes

> What is interesting (and we might make that an option) is that the 'no 
> display' error results in the image being saved 'headfull' so that you can 
> start it up using a display to debug it (suspended process/debugger).

That could be done.. but not as userful as simply report an error.
Usually we (developers) knowing what we want to do,
and what i don't want to see in my headless image is any attempts to
access display/ui.

> Saving a headless image headfull can also be done programmatically.
>
> I don't think more than that is needed. There are many options to interact 
> with headless images, forcing one on people would not be good, the same goes 
> for command line parsing, preferences, startup files, ... These other options 
> could become separate projects.
>

well, again, when people running image(s) in headless mode, they are
know what they doing, and i think their default expectation is that
image(s) should be aware that it runs headless and do not try to
invoke anything which requires user interaction (like yes/no dialog) ,
because this does not makes any sense.

> I would be an interested user and if I can will try to help.
>
> Regards,
>
> Sven
>

-- 
Best regards,
Igor Stasenko AKA sig.

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

[pharo]

Updates:
Status: Closed
Labels: -Milestone-1.2

Comment #6 on issue 3419 by marcus.d...@gmail.com:  
TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

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

Workaround

12316. Not to be appled to 1.3

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

[pharo]

Comment #8 on issue 3520 by marcus.d...@gmail.com: Workspaces do not  
recognize previously evaluated temps

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

12316

TODO: 1.3

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

[pharo]

Updates:
Status: Accepted

Comment #7 on issue 3419 by marcus.d...@gmail.com:  
TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

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

(No comment was entered for this change.)

Re: [Pharo-project] Instruments for headless images

[Sven Van Caekenberghe]

On 21 Jan 2011, at 11:19, Igor Stasenko wrote:

>> What is interesting (and we might make that an option) is that the 'no 
>> display' error results in the image being saved 'headfull' so that you can 
>> start it up using a display to debug it (suspended process/debugger).
> 
> That could be done.. but not as userful as simply report an error.
> Usually we (developers) knowing what we want to do,
> and what i don't want to see in my headless image is any attempts to
> access display/ui.

Yeah, that's why I said it would better be an option. The first thing to do is 
simply report the error (and quit, or maybe that should be an option too). But 
many people playing with headless images (myself included) have had 
blocking/locked up images: having a log would be great, but adding this option 
to debug the cause further would be great.

Sven

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

[pharo]

Updates:
Status: Closed

Comment #9 on issue 3520 by marcus.d...@gmail.com: Workspaces do not  
recognize previously evaluated temps

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

13007

Re: [Pharo-project] Instruments for headless images

[Igor Stasenko]

On 21 January 2011 11:28, Sven Van Caekenberghe  wrote:
>
> On 21 Jan 2011, at 11:19, Igor Stasenko wrote:
>
>>> What is interesting (and we might make that an option) is that the 'no 
>>> display' error results in the image being saved 'headfull' so that you can 
>>> start it up using a display to debug it (suspended process/debugger).
>>
>> That could be done.. but not as userful as simply report an error.
>> Usually we (developers) knowing what we want to do,
>> and what i don't want to see in my headless image is any attempts to
>> access display/ui.
>
> Yeah, that's why I said it would better be an option. The first thing to do 
> is simply report the error (and quit, or maybe that should be an option too). 
> But many people playing with headless images (myself included) have had 
> blocking/locked up images: having a log would be great, but adding this 
> option to debug the cause further would be great.
>

this is next step..

I think this could be set by preference system
on error:
  - print error to log and quit
  - print error to log and do save & quit
  - print error to log and do save new version & quit

In future , by adding support from VM side we could also have:
  - switch to interactive(headfull) mode, by creating an OS window
opening debugger , showing dialog(s) etc etc


> Sven
>


-- 
Best regards,
Igor Stasenko AKA sig.

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

[pharo]

Comment #18 on issue 3542 by torsten@astares.de: Add  
SmalltalkImage>>#gcBiasToGrow: and friends to core

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

Mariano: ImageForDevelopers is used in the build for the upcoming Pharo  
1.2, isnt it?


Phillipe: is #loadLatestVersion of Seaside 3.0 working/compatible with the  
upcoming Pharo 1.2 already?

Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues

[pharo]

Updates:
Cc: eliot.miranda marianopeck

Comment #2 on issue 3465 by torsten@astares.de: Hundson OneClick: Does  
not show Mac menues

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

Setting Eliot on CC for this issue. Maybe the mac menu support code
is only in the standard VM and not yet integrated into Cog VM.

Mariano: You should note the exact image (download location) here so Eliot
can reproduce it.

[Pharo-project] Issue 3565 in pharo: Undeclared ref in 1.1.1

[pharo]

Status: Fixed
Owner: marcus.d...@gmail.com
Labels: Milestone-1.1.1

New issue 3565 by marcus.d...@gmail.com: Undeclared ref in 1.1.1
http://code.google.com/p/pharo/issues/detail?id=3565

Fix attached...



Attachments:
UndeclaredFix.1.cs  5.2 KB

Re: [Pharo-project] Using AlienOpenGL

[Alexandre Bergel]

Thanks Fernando for offering your help. We are still at the phase to decide 
what techno to use.
Lumiere has indeed many good things (even though I do not agree with every 
design decision made in it :-)

Cheers,
Alexandre


On 21 Jan 2011, at 04:21, Fernando Olivero wrote:

> Lumeire fulfills the specified goals: creating a world (scene) +
> cameras + light sources + 3d objects.
> 
> Lumiere currently uses AlienOpenGL to comunicate with OpenGl, it could
> easily use OpenGL FFI as well as the underlying glue code to the
> rendering library.
> 
> So resuming:
> 
> 1) Lumiere abstractions over matrixes and OGL.
> 
> 2) Rendering engined wrapper: AlienOpenGL (unmaintaned currently),
> OpenGL FFI , NativeBoost OpenGL (only  windows for now, until someone
> compiles native boost vm for other OS).
> 
> If someone needs the good abstractions of Lumiere, i could give some
> pointers on were to remove the AlienOpenGL dependency and "plug" the
> preferred engine.
> 
> Fernando
> 
> On Fri, Jan 21, 2011 at 1:43 AM, Alexandre Bergel  wrote:
>> I feel that we will take the easiest way: implement a small 3d engine. This 
>> is about 100 lines of code for something simple (what we need in fact).
>> Ricardo and Patricio spent several days having something that run with 
>> AlienOpenGL, and the technical problems are numerous (Cog vs Standard, 
>> Linux, ...)
>> 
>> We will let you know.
>> 
>> Cheers,
>> Alexandre
>> 
>>> If I knew what worked, I'd be making a recommendation :)  As it is, I can 
>>> perhaps help you work through the debugging process.  As I said, you could 
>>> indeed be missing a needed library, there could be dependencies missing 
>>> that make a .so unable to load, a .so could be just plain broken (I've seen 
>>> that once or twice), or the vm could be looking in the wrong place and 
>>> saying absolutely nothing about it.  If you can post more about what is 
>>> going wrong and how, we might be able to sort it out, hopefully w/o having 
>>> to hack the vm (but no promises).
>>> 
>>> My 3D goals would generally be to create a view/world, add a light source 
>>> or two and a camera, and to load a few meshes onto some type of retained 
>>> mode objects and start prodding them in simple ways.  Croquet's code for 
>>> that looked like it was perfect for what I have in mind, but the 3D needs 
>>> to go in the software, not the other way around.  Scouting reports would be 
>>> most welcome.
>>> 
>>> Bill
>>> 
>>> 
>>> 
>>> From: pharo-project-boun...@lists.gforge.inria.fr 
>>> [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Alexandre Bergel 
>>> [alexan...@bergel.eu]
>>> Sent: Thursday, January 20, 2011 7:22 PM
>>> To: Pharo-project@lists.gforge.inria.fr
>>> Subject: Re: [Pharo-project] Using AlienOpenGL
>>> 
 Not that you are wrong, but how did you choose AlienOpenGL over CroquetGL?
>>> 
>>> We're just looking for something that works.
>>> Is there currently a solution to make 3d with Pharo 1.2 and that works with 
>>> windows, linux and mac?
>>> The idea is to have a 3d version of Mondrian. No need of fancy 3d effect so 
>>> far.
>>> 
>>> Cheers,
>>> Alexandre
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-project] Pharo on the iPhone

[Alexandre Bergel]

Thanks John for these pointers

Alexandre


On 21 Jan 2011, at 03:05, John M McIntosh wrote:

> (a) sign up for Apple's SDK, to install apps on the iPhone you have to pay 
> $99 per year.
> 
> (b) visit squeakvm.org download the source tree
> 
> (c) look for the SqueakPureObjc.xcodeproj
> compile/link/debug/run the iPhone app 
> 
> (d) Optionally look for the SqueakPureObjcCogVM.xcodeproj after download the 
> COG tree. 
> Don't cut yourself on the rough edges, but I think Esteban has a workable 
> version now? 
> 
> The difference between the two is that the SqueakPureObjcCogVM builds a stack 
> VM, where as the SqueakPureObjc builds the traditional VM but is about 30% 
> slower. 
> 
> The image has to include the objective-c bridge and iphone stuff, there is a 
> sample image (broken) in the source tree. 
> 
> On 2011-01-20, at 5:10 PM, Alexandre Bergel wrote:
> 
>> Hi!
>> 
>> iPhone 4 is amazing. It will be even better with Pharo inside. Is there a 
>> way to install it?
>> 
>> Cheers,
>> Alexandre
>> 
>> NB: my device is non jailbreaked.
>> 
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>> 
>> 
>> 
> 
> --
> ===
> John M. McIntoshTwitter:  squeaker68882
> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> ===
> 
> 
> 
> 
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

[pharo]

Comment #4 on issue 3179 by cy.delau...@gmail.com: Failing Tests for  
Monticello

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

I join a changeSet that make all monticello test green.

For that, I made the fix provided by stephane in issue 2294 (see above),  
and fix the remaining test: MCChangeNotificationTest >>  
testExtMethodModified. That's the method I modified to solve the problem:


mockClassExtension

	"I change the protocol of this method (to be '*monticellomocks' instead  
of 'mocks') to resolve the failing test: MCChangeNotificationTest >>  
testExtMethodModified. This test basically test that when we modified an  
extension method, the extended package is marked as 'modified'. The problem  
is that Monticello treat differently a classic method from an extension  
method, and this only by checking if the protocol name start with a star.  
Therefore, if the protocol does not match the extending package name, the  
extending package name will never be notified, and the test will fail. "


Attachments:
issue3179.1.cs  3.1 KB

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

[pharo]

Updates:
Status: Fixed

Comment #2 on issue 3564 by johanbri...@me.com: Comparison of source  
references (for sorting)

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


Fixed in  
SLICE-Issue-3564-Not-all-SourceReference-subclasses-implement--JohanBrichau.3


(probably best to integrate in 1.2 because the bug breaks the source  
searching tools...)

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

[pharo]

Comment #3 on issue 3564 by marcus.d...@gmail.com: Comparison of source  
references (for sorting)

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

12317

TODO: 1.3

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

[pharo]

Updates:
Status: Fixed

Comment #5 on issue 3179 by marcus.d...@gmail.com: Failing Tests for  
Monticello

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

12317

TODO: 1.3

[Pharo-project] [update 1.2] #12317

[Marcus Denker]

12317
-

Issue 3564: Comparison of source references (for sorting)
Issue 3179: Failing Tests for Monticello
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3564 in pharo: Comparison of source references (for sorting)

[pharo]

Updates:
Status: Closed

Comment #4 on issue 3564 by marcus.d...@gmail.com: Comparison of source  
references (for sorting)

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

13008

[Pharo-project] [update 1.3] #13008

[Marcus Denker]

13008
-

Issue 3564: Comparison of source references (for sorting)
Issue 3179: Failing Tests for Monticello
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

[pharo]

Updates:
Status: Closed

Comment #6 on issue 3179 by marcus.d...@gmail.com: Failing Tests for  
Monticello

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

13008

Re: [Pharo-project] Issue 3565 in pharo: Undeclared ref in 1.1.1

[pharo]

Updates:
Status: Closed
Labels: -Milestone-1.1.1 Milestone-1.1.2

Comment #1 on issue 3565 by marcus.d...@gmail.com: Undeclared ref in 1.1.1
http://code.google.com/p/pharo/issues/detail?id=3565

11416

[Pharo-project] [update 1.1] #11416

[Marcus Denker]

11416
-

 Issue 3565:Undeclared ref in 1.1.1
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3420 in pharo: ReleaseTest>>#testUndeclared is failing

[pharo]

Updates:
Labels: -Milestone-1.1.1 Milestone-1.1.2

Comment #7 on issue 3420 by marcus.d...@gmail.com:  
ReleaseTest>>#testUndeclared is failing

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 2844 in pharo: String>>#numArgs is broken

[pharo]

Updates:
Labels: -Milestone-1.1.1 Milestone-1.1.2

Comment #7 on issue 2844 by marcus.d...@gmail.com: String>>#numArgs is  
broken

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3527 in pharo: Please add the following Generator code to Pharo. I need it to port a package I am writing from Squeak to Pharo

[pharo]

Updates:
Status: Fixed
Labels: Milestone-1.3

Comment #3 on issue 3527 by marcus.d...@gmail.com: Please add the following  
Generator code to Pharo.  I need it to port a package I am writing from  
Squeak to Pharo

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

(No comment was entered for this change.)

[Pharo-project] OB failing tests in Pharo 1.2

[Mariano Martinez Peck]

Hi Lukas. I was checking the 4 failing tests in Pharo 1.2:
http://code.google.com/p/pharo/issues/detail?id=3470

The problem seems related to the changes with the
SmalltalkEditor/ParagraphEditor and friends. The tests fails because the
instVar "message" is nil, because nobody call OBKeyBindingsTest >> browseIt:
aSelector
nor its friends. This was called in Pharo 1.1 from OBTextMorphEditor
because it was a subclass of ParagraphEditor.

Now, I have no idea how to make it work in Pharo 1.2

Cheers

mariano

Re: [Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

[pharo]

Updates:
Status: Fixed

Comment #2 on issue 3540 by johanbri...@me.com: Latest versions in  
DevImages Workspace

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

[pharo]

Updates:
Cc: renggli

Comment #2 on issue 3470 by marianopeck: [Failing Tests] OBKeyBindingsTest
http://code.google.com/p/pharo/issues/detail?id=3470

Hi Lukas. I was checking the 4 failing tests in Pharo 1.2:  
http://code.google.com/p/pharo/issues/detail?id=3470


The problem seems related to the changes with the  
SmalltalkEditor/ParagraphEditor and friends. The tests fails because the  
instVar "message" is nil, because nobody call OBKeyBindingsTest >>  
browseIt: aSelector
nor its friends. This was called in Pharo 1.1 from OBTextMorphEditor   
because it was a subclass of ParagraphEditor.


Now, I have no idea how to make it work in Pharo 1.2

Cheers

mariano

Re: [Pharo-project] Pharo on the iPhone

[Esteban Lorenzano]

Hi,

El 21/01/2011, a las 3:05a.m., John M McIntosh escribió:
> 
> compile/link/debug/run the iPhone app 
> 
> (d) Optionally look for the SqueakPureObjcCogVM.xcodeproj after download the 
> COG tree. 
> Don't cut yourself on the rough edges, but I think Esteban has a workable 
> version now? 

yes... but still not merged with the build model we are creating (with hudson, 
etc.), neither commited to trunk. You can download it from here: 
http://gitorious.org/~estebanlm/cogvm/cog-osx, and let me know if you find any 
problem (most likely, now :P)

Re: [Pharo-project] Issue 3561 in pharo: Remove everything into PluggableShoutMorph

[pharo]

Updates:
Labels: Milestone-1.3

Comment #1 on issue 3561 by stephane...@gmail.com: Remove everything into  
PluggableShoutMorph

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

This should be integrated in shout

Re: [Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

[pharo]

Updates:
Status: Closed

Comment #3 on issue 3540 by stephane...@gmail.com: Latest versions in  
DevImages Workspace

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3561 in pharo: Remove everything into PluggableShoutMorph

[pharo]

Comment #2 on issue 3561 by stephane...@gmail.com: Remove everything into  
PluggableShoutMorph

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

it should be merged in shout-MarianoMartinezPeck.98 since  
shout-StephaneDucasse.99 is not necessary anymore.

[Pharo-project] Reminder: change the archiving tool

[Igor Stasenko]

All .zip files with pharo images having an annoying Apple-ism - a
.DS_Store garbage file.
Please use a zip archiver which includes only relevant files to
archive, because obviously this garbage has no use anywhere but Macs.

-- 
Best regards,
Igor Stasenko AKA sig.

Re: [Pharo-project] Using AlienOpenGL

[Schwab,Wilhelm K]

Fernando,

The goals are mix of what Alexandre is trying to do short term and what I want 
to be able to do eventually.  It's great to know that you have addressed them.  
One thing we appear to have in common is Linux, which is why I jumped into this 
- I've had to debug several non-loading libraries and have learned some tricks 
that might help.

A related thread:

   http://forum.world.st/OpenGL-in-pharo-td1475316.html

Bill



From: pharo-project-boun...@lists.gforge.inria.fr 
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Fernando Olivero 
[fernando.oliv...@usi.ch]
Sent: Friday, January 21, 2011 2:21 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Using AlienOpenGL

Lumeire fulfills the specified goals: creating a world (scene) +
cameras + light sources + 3d objects.

Lumiere currently uses AlienOpenGL to comunicate with OpenGl, it could
easily use OpenGL FFI as well as the underlying glue code to the
rendering library.

So resuming:

1) Lumiere abstractions over matrixes and OGL.

2) Rendering engined wrapper: AlienOpenGL (unmaintaned currently),
OpenGL FFI , NativeBoost OpenGL (only  windows for now, until someone
compiles native boost vm for other OS).

If someone needs the good abstractions of Lumiere, i could give some
pointers on were to remove the AlienOpenGL dependency and "plug" the
preferred engine.

Fernando

On Fri, Jan 21, 2011 at 1:43 AM, Alexandre Bergel  wrote:
> I feel that we will take the easiest way: implement a small 3d engine. This 
> is about 100 lines of code for something simple (what we need in fact).
> Ricardo and Patricio spent several days having something that run with 
> AlienOpenGL, and the technical problems are numerous (Cog vs Standard, Linux, 
> ...)
>
> We will let you know.
>
> Cheers,
> Alexandre
>
>> If I knew what worked, I'd be making a recommendation :)  As it is, I can 
>> perhaps help you work through the debugging process.  As I said, you could 
>> indeed be missing a needed library, there could be dependencies missing that 
>> make a .so unable to load, a .so could be just plain broken (I've seen that 
>> once or twice), or the vm could be looking in the wrong place and saying 
>> absolutely nothing about it.  If you can post more about what is going wrong 
>> and how, we might be able to sort it out, hopefully w/o having to hack the 
>> vm (but no promises).
>>
>> My 3D goals would generally be to create a view/world, add a light source or 
>> two and a camera, and to load a few meshes onto some type of retained mode 
>> objects and start prodding them in simple ways.  Croquet's code for that 
>> looked like it was perfect for what I have in mind, but the 3D needs to go 
>> in the software, not the other way around.  Scouting reports would be most 
>> welcome.
>>
>> Bill
>>
>>
>> 
>> From: pharo-project-boun...@lists.gforge.inria.fr 
>> [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Alexandre Bergel 
>> [alexan...@bergel.eu]
>> Sent: Thursday, January 20, 2011 7:22 PM
>> To: Pharo-project@lists.gforge.inria.fr
>> Subject: Re: [Pharo-project] Using AlienOpenGL
>>
>>> Not that you are wrong, but how did you choose AlienOpenGL over CroquetGL?
>>
>> We're just looking for something that works.
>> Is there currently a solution to make 3d with Pharo 1.2 and that works with 
>> windows, linux and mac?
>> The idea is to have a 3d version of Mondrian. No need of fancy 3d effect so 
>> far.
>>
>> Cheers,
>> Alexandre
>>
>>
>>
>>
>>
>>
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
>

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

[pharo]

Comment #19 on issue 3542 by philippe...@gmail.com: Add  
SmalltalkImage>>#gcBiasToGrow: and friends to core

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

Maybe. We didn't test it. The last time I checked OB didn't work.

Re: [Pharo-project] Issue 3532 in pharo: OB does not allow accepting after deletion only

[pharo]

Comment #2 on issue 3532 by johanbri...@me.com: OB does not allow accepting  
after deletion only

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

This seems to come from the following 'bugfix' (comment in  
OBTextMorphEditorWithShout>>backTo:)


"When backspacing, 2 notifications of the userHasEdited are received.
This then causes a background process to not terminate correctly.
	The reason for all this is uncertain, but discarding the superfluous  
userHasEdited

message received while running backTo: seems to cure the problem"

I disabled this fix and do not get any problems... but the reason for the  
fix is not clear.

Re: [Pharo-project] Reminder: change the archiving tool

[Marcus Denker]

On Jan 21, 2011, at 2:00 PM, Igor Stasenko wrote:

> All .zip files with pharo images having an annoying Apple-ism - a
> .DS_Store garbage file.
> Please use a zip archiver which includes only relevant files to
> archive, because obviously this garbage has no use anywhere but Macs.
> 
Ok, will do.

(we need to automatize it anyway)



--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3527 in pharo: Please add the following Generator code to Pharo. I need it to port a package I am writing from Squeak to Pharo

[pharo]

Updates:
Status: Closed

Comment #4 on issue 3527 by stephane...@gmail.com: Please add the following  
Generator code to Pharo.  I need it to port a package I am writing from  
Squeak to Pharo

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

in 13009

Re: [Pharo-project] Issue 3527 in pharo: Generator

[pharo]

Updates:
Summary: Generator

Comment #5 on issue 3527 by stephane...@gmail.com: Generator
http://code.google.com/p/pharo/issues/detail?id=3527

(No comment was entered for this change.)

Re: [Pharo-project] Reminder: change the archiving tool

[Tudor Girba]

The latest builder code is able to produce a one-click distribution.

Cheers,
Doru


On 21 Jan 2011, at 14:41, Marcus Denker wrote:

> 
> On Jan 21, 2011, at 2:00 PM, Igor Stasenko wrote:
> 
>> All .zip files with pharo images having an annoying Apple-ism - a
>> .DS_Store garbage file.
>> Please use a zip archiver which includes only relevant files to
>> archive, because obviously this garbage has no use anywhere but Macs.
>> 
> Ok, will do.
> 
> (we need to automatize it anyway)
> 
> 
> 
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
> 
> 

--
www.tudorgirba.com

"The coherence of a trip is given by the clearness of the goal."

[Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Status: Accepted
Owner: ryd...@gmail.com
Labels: Milestone-1.2 Milestone-1.3

New issue 3566 by ryd...@gmail.com: Changes needed to update Sound for 1.2
http://code.google.com/p/pharo/issues/detail?id=3566

Some changes are needed to update the external PharoSound package and still  
be able to stay reasonably in synch with Squeak updates.


Mainly this means moving soundsEnabled and useThemeSounds from a separate  
class into other, appropriate classes.

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Updates:
Status: Fixed

Comment #1 on issue 3566 by ryd...@gmail.com: Changes needed to update  
Sound for 1.2

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

SLICE-Issue3566-MoveSoundSettings in Inbox

Re: [Pharo-project] Issue 3532 in pharo: OB does not allow accepting after deletion only

[pharo]

Updates:
Status: Closed

Comment #3 on issue 3532 by johanbri...@me.com: OB does not allow accepting  
after deletion only

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

Fixed in OBShout-JohanBrichau.12 (in PharoTaskForces)

remark: the deleted methods were solving _some bug_ that I do not seem to  
have... (the comments about this are vague and uncertain too). Seems to  
work just fine now.

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

[pharo]

Updates:
Cc: hilaire.fernandes aplantec

Comment #12 on issue 3489 by marianopeck: Pharo 1.2-dev still uses  
Preferences in BaseSoundSystem

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

I have just fixed as many as I could. There are still some pending ones:

Preferences canRecordWhilePlaying.
Preferences soundStopWhenDone.

People who is interested in Sound shoudl fix them.

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

[pharo]

Comment #13 on issue 3489 by marianopeck: Pharo 1.2-dev still uses  
Preferences in BaseSoundSystem

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

Sorry and Preferences soundQuickStart

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

[pharo]

Updates:
Status: Started

Comment #14 on issue 3489 by marianopeck: Pharo 1.2-dev still uses  
Preferences in BaseSoundSystem

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

(No comment was entered for this change.)

Re: [Pharo-project] Issue 3491 in pharo: Preferences are still referenced in Pharo-dev 1.2

[pharo]

Updates:
Status: Closed

Comment #3 on issue 3491 by marianopeck: Preferences are still referenced  
in Pharo-dev 1.2

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

The only pending ones are from PharoSounds and they are in

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

so I close this issue

[Pharo-project] Reminder: change the archiving tool

[Torsten Bergmann]

>All .zip files with pharo images having an annoying Apple-ism - a
>.DS_Store garbage file.
>Please use a zip archiver which includes only relevant files to
>archive, because obviously this garbage has no use anywhere but Macs.

Last time I mentioned this (as  windows user) 
I was told (by Adrian or Stef?) they are usefull/required for Mac users 
and it is easy for others platform users to throw them 
away

So maybe we should first check with the mac users around 
here before changing the one click distro

Bye
T.
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

[Pharo-project] Issue 3567 in pharo: FFI OpenGL doesn't load nor work

[pharo]

Status: New
Owner: 

New issue 3567 by elpochod...@gmail.com: FFI OpenGL doesn't load nor work
http://code.google.com/p/pharo/issues/detail?id=3567

Pharo image: Pharo
Pharo core version: Pharo1.2rc1. Latest update: #12317
Virtual machine used:  'Squeak3.10.2 of 11 February 2010 [latest update:  
#9314]' (windows)


Steps to reproduce:
1. Try to load FFI OpenGL (as described in the book  
http://book.pharo-project.org/book/3DGraphicsAndOpenGL)


There are problems with underscore assignments, a compiler error in  
OpenGLUnixQuartz class>>#test and some deprecations from going from  
SmalltalkImage current to Smalltalk.

[Pharo-project] Fwd: Issue 3532 in pharo: OB does not allow accepting after deletion only

[Mariano Martinez Peck]

Lukas feel free to include it in OB (even if we commit it to the TaskForces)

-- Forwarded message --
From: 
Date: Fri, Jan 21, 2011 at 3:05 PM
Subject: Re: [Pharo-project] Issue 3532 in pharo: OB does not allow
accepting after deletion only
To: pharo-project@lists.gforge.inria.fr


Updates:
   Status: Closed

Comment #3 on issue 3532 by johanbri...@me.com: OB does not allow accepting
after deletion only

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

Fixed in OBShout-JohanBrichau.12 (in PharoTaskForces)

remark: the deleted methods were solving _some bug_ that I do not seem to
have... (the comments about this are vague and uncertain too). Seems to work
just fine now.

[Pharo-project] [update 1.3] #13010

[Stéphane Ducasse]

13009
-
-  Issue 3527:  Generator. Thanks Ralph Boland

13010
-

- Issue 3361:   CompiledMethod copy. Thanks Gabriel Barbuto.

Stef

Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph

[pharo]

Comment #2 on issue 3482 by marianopeck: InterimSoundMorph references to  
SketchMorph

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

Guille. We have two options:  remove also InterimSoundMorph
oradd SketchMorph and its subclass JoystickMorph  to PharoMorphicExtras  
or something like that.

can you take care?

Re: [Pharo-project] Reminder: change the archiving tool

[Adrian Lienhard]

On Jan 21, 2011, at 15:23 , Torsten Bergmann wrote:

>> All .zip files with pharo images having an annoying Apple-ism - a
>> .DS_Store garbage file.
>> Please use a zip archiver which includes only relevant files to
>> archive, because obviously this garbage has no use anywhere but Macs.
> 
> Last time I mentioned this (as  windows user) 
> I was told (by Adrian or Stef?) they are usefull/required for Mac users 

not me :)

I agree, we should avoid shipping with this garbage... I assume that with the 
automated builds from Hudson the problem will go away. 

Adrian

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Comment #2 on issue 3566 by marianopeck: Changes needed to update Sound for  
1.2

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

Thanks  henrik. Today I did the same but for the PharoSound external  
package for PharoDev. You can take a look and fix it if necessary. In that  
case, please be sure of using the latest version of the packages in  
PharoNonCorePackages since I commit them today and not sure the hudson  
build a new dev with them

[Pharo-project] [update 1.1] #11417

[Marcus Denker]

11417
-

- more fixes for testrunner artefacts.
- do release clean
--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

Re: [Pharo-project] Issue 3542 in pharo: Add SmalltalkImage>>#gcBiasToGrow: and friends to core

[pharo]

Comment #20 on issue 3542 by marianopeck: Add  
SmalltalkImage>>#gcBiasToGrow: and friends to core

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

Mariano: ImageForDevelopers is used in the build for the upcoming Pharo  
1.2, isnt it?


answer: yes.

[Pharo-project] Reminder: change the archiving tool

[Sven Van Caekenberghe]

On 21 Jan 2011, at 15:23, Torsten Bergmann wrote:

> Last time I mentioned this (as  windows user) 
> I was told (by Adrian or Stef?) they are usefull/required for Mac users 
> and it is easy for others platform users to throw them 
> away
> 
> So maybe we should first check with the mac users around 
> here before changing the one click distro

http://en.wikipedia.org/wiki/.DS_Store

These are not really needed.
They make archives ugly for users on other systems, best to clean them unless 
there is a good reason to keep them.

Sven

Re: [Pharo-project] Issue 3482 in pharo: InterimSoundMorph references to SketchMorph

[pharo]

Comment #3 on issue 3482 by guillerm...@gmail.com: InterimSoundMorph  
references to SketchMorph

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

Mmm, tonight I will, promise :).

Re: [Pharo-project] OB failing tests in Pharo 1.2

[Lukas Renggli]

> Hi Lukas. I was checking the 4 failing tests in Pharo 1.2:
> http://code.google.com/p/pharo/issues/detail?id=3470
>
> The problem seems related to the changes with the
> SmalltalkEditor/ParagraphEditor and friends. The tests fails because the
> instVar "message" is nil, because nobody call OBKeyBindingsTest >> browseIt:
> aSelector
> nor its friends. This was called in Pharo 1.1 from OBTextMorphEditor
> because it was a subclass of ParagraphEditor.
>
> Now, I have no idea how to make it work in Pharo 1.2

Yeah, me neither. OB-Morphic is totally broken and it cannot be
quickly fixed. The editor support has to be completely rewritten on
top of the new infrastructure to get a browser that properly works.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

Re: [Pharo-project] New chapter on OpenGL in Pharo

[Javier Pimás]

On Fri, Jan 21, 2011 at 7:01 AM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:

> 2011/1/21 Javier Pimás :
> > Hi! I just gathered many of my previous experiences trying to use opengl
> and
> > uploaded it to the pharo book. It would be nice if someone could check
> the
> > info, try to add more and mainly test the tips to see if they are
> working.
>
> Link?
>
>
http://book.pharo-project.org/book/3DGraphicsAndOpenGL


>  > With FFI OpenGL I'm getting an error while compiling a test method in
> Pharo
>
> which error?
>

I added this issue  to
describe the problems and uploaded a slice to solve some.


>
> > 1.2 and some problems with underscore assignments and deprecations, we
>
> which problems?
>
> Menu -> System -> Settings
> Write underscore, hit Enter
> Check "Allow underscore as assignment"
>
> To change all underscores _ to := install AST and RB and evaluate:
>
> | environment change rule |
> environment := BrowserEnvironment new forPackageNames:
> #('YourPackageName').
> rule := RBUnderscoreAssignmentRule new.
> SmalllintChecker runRule: rule onEnvironment: environment.
> change := CompositeRefactoryChange new.
> change changes: rule changes.
> change execute
>
> > should fix them but I don't think I have access to that repo. Also,
> loading
> > it involves many steps, having a ConfigurationOfFFIOpenGL would be
> awsome.
> > Please add anything you consider useful.
> > Regards,
> >   Javier.
> >
> > --
> > Javier Pimás
> > Ciudad de Buenos Aires
> >
>
>


-- 
Javier Pimás
Ciudad de Buenos Aires

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

[pharo]

Comment #15 on issue 3489 by ryd...@gmail.com: Pharo 1.2-dev still uses  
Preferences in BaseSoundSystem

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

Issue3566 contains base 1.2 changes for the new 1.2 compatible version in  
PharoSound.

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Comment #3 on issue 3566 by ryd...@gmail.com: Changes needed to update  
Sound for 1.2

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

I updated the PharoSound repository with a working 1.2 package.

Re: [Pharo-project] Issue 3567 in pharo: FFI OpenGL doesn't load nor work

[pharo]

Comment #1 on issue 3567 by elpochod...@gmail.com: FFI OpenGL doesn't load  
nor work

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

A slice to solve the first 2 problems, that shouldn't break squeak nor  
pharo. For deprecations, I don't know what should be done. Doing


OpenGL new

should show some of them, but in the tested image deprecations are being  
hidden (I think)


Attachments:
OpenGL-JavierPimas.1.mcz  115 KB

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Comment #4 on issue 3566 by ryd...@gmail.com: Changes needed to update  
Sound for 1.2

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

The package in PharoSound is more up to date than what you can find in  
NonCorePackages.


I suggest deleting the one in Non..., and update Configurations to use  
PharoSound directly.

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

[pharo]

Issue 3566: Changes needed to update Sound for 1.2
http://code.google.com/p/pharo/issues/detail?id=3566

This issue is now blocking issue 3489.
See http://code.google.com/p/pharo/issues/detail?id=3489

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

[pharo]

Updates:
Blockedon: 3566

Comment #16 on issue 3489 by ryd...@gmail.com: Pharo 1.2-dev still uses  
Preferences in BaseSoundSystem

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

(No comment was entered for this change.)