- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] you may need to update your configurations

by Dale K. Henrichs

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Nicolas Cellier

Certainly not in 2.0 Even in 3.0, this will be hard because this mean a big clean-up of Stream mess (Xtreams?) 2013/6/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 19 Jun 2013, at 22:55, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > Yes, this part is perfectly correct. > > It's just that I used ZnInvalidUTF8 in TextConverter which introduces a > dependency of TextConverter on Zinc. > > OK, but technically, it is a dependency on Zinc-Character-Encoding-Core, > which is independent of the Zinc HTTP code itself. Just like > Zinc-Resource-Meta-Core (containing ZnUrl and ZnMimeType) is independent of > the HTTP code proper. These sub packages where created specifically to > break unwanted dependencies, as requested by Pavel et al. > > > This only make sense if in the long term we replace those TextConverters > by cleaner Zinc encoders/decoders. > > Yes, that is the idea, eventually. But never in 2.0. > > > 2013/6/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > > > On 19 Jun 2013, at 22:33, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > > The change is very light, I applied it almost unchanged on Squeak > (can't remember which version was the first). > > > The only thing we neeed is to catch an UTF8Error. > > > > > > Since in Pharo there are two encoder/decoder hierarchies, and since > that of Zinc is cleaner, I made a bet on future and chose to make UTF8Error > a subclass of existing already Zn Encoding/Decoding exception. > > > > > > But we still use the old TextConverter hierarchy in MC, even in Pharo > 3.0. > > > So the dependency on Zinc is totally arbitrary and un-necessary right > now; it does not exist in Smalltalk version. > > > It's just a bet on the future. > > > For a backport to 2.0, I would just use an UTF8Error like in Squeak > and avoid any dependency on Zinc. > > > > Well ZnInvalidUTF8 is now a full part of Zinc itself > (Zinc-Character-Encoding-Core to be exact). It is already in 3.0 (with your > code) and I guess we'll upgrade Zinc in 2.0 as well. But is is a > dependency, that is correct. > > > > Anyway, we have to double check. > > > > > Nicolas > > > > > > > > > 2013/6/19 GOUBIER Thierry <thierry.goubier(a)cea.fr> > > > StÃ©phane, > > > > > > I'll probably have a look at Nicolas fix anyway, but as it required > also a change to Zinc... then I started to worry. But it may be better than > trying to fix ZipArchive incorrect encoding issues from the outside (by > forcing an utf8 conversion out of the contents of the ZipArchive members). > > > > > > If I manage to make sense of it, I'll put a enhancement request in > FogBuz with a slice. > > > > > > Yes, I think 30 is not that unstable, like 2.0 was before ... except > that I'm fairly dependent on the RPackage infrastructure, and I prefer to > wait until the RPackage refactoring is done ;-) > > > > > > Thierry > > > > > > ________________________________________ > > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de > StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > > > Date d'envoi : mercredi 19 juin 2013 21:21 > > > Ã : Pharo Development List > > > Objet : Re: [Pharo-dev] you may need to update your configurations > > > > > > > > > > > > > > >> Christophe. > > > >> > > > >> [1] https://pharo.fogbugz.com/default.asp?10801 > > > > > > > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > > > > > > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year > or so or fighting every few days with 3.0 and knowing that anyway it's not > production ready. I had to cope with 1.4 not being able to handle utf8 in > the same way. > > > > > > Thierry what we can do is the following: > > > have a look at the fix of nicolas and we can try to add to th > 2.0 batch but we should pay attention > > > not to introduce other bugs (because I'm afraid it will). > > > > > > BTW 30 is not that instable. > > > > > > > > > > The window for my next serious developpement with Pharo is around > 2014, so I guess I could just sit and wait. > > > > > > > > By the way, why the change in > MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > > > > > > > > > > > > > > > > >

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Sven Van Caekenberghe

On 19 Jun 2013, at 22:55, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Yes, this part is perfectly correct. > It's just that I used ZnInvalidUTF8 in TextConverter which introduces a dependency of TextConverter on Zinc. OK, but technically, it is a dependency on Zinc-Character-Encoding-Core, which is independent of the Zinc HTTP code itself. Just like Zinc-Resource-Meta-Core (containing ZnUrl and ZnMimeType) is independent of the HTTP code proper. These sub packages where created specifically to break unwanted dependencies, as requested by Pavel et al. > This only make sense if in the long term we replace those TextConverters by cleaner Zinc encoders/decoders. Yes, that is the idea, eventually. But never in 2.0. > 2013/6/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 19 Jun 2013, at 22:33, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > The change is very light, I applied it almost unchanged on Squeak (can't remember which version was the first). > > The only thing we neeed is to catch an UTF8Error. > > > > Since in Pharo there are two encoder/decoder hierarchies, and since that of Zinc is cleaner, I made a bet on future and chose to make UTF8Error a subclass of existing already Zn Encoding/Decoding exception. > > > > But we still use the old TextConverter hierarchy in MC, even in Pharo 3.0. > > So the dependency on Zinc is totally arbitrary and un-necessary right now; it does not exist in Smalltalk version. > > It's just a bet on the future. > > For a backport to 2.0, I would just use an UTF8Error like in Squeak and avoid any dependency on Zinc. > > Well ZnInvalidUTF8 is now a full part of Zinc itself (Zinc-Character-Encoding-Core to be exact). It is already in 3.0 (with your code) and I guess we'll upgrade Zinc in 2.0 as well. But is is a dependency, that is correct. > > Anyway, we have to double check. > > > Nicolas > > > > > > 2013/6/19 GOUBIER Thierry <thierry.goubier(a)cea.fr> > > StÃ©phane, > > > > I'll probably have a look at Nicolas fix anyway, but as it required also a change to Zinc... then I started to worry. But it may be better than trying to fix ZipArchive incorrect encoding issues from the outside (by forcing an utf8 conversion out of the contents of the ZipArchive members). > > > > If I manage to make sense of it, I'll put a enhancement request in FogBuz with a slice. > > > > Yes, I think 30 is not that unstable, like 2.0 was before ... except that I'm fairly dependent on the RPackage infrastructure, and I prefer to wait until the RPackage refactoring is done ;-) > > > > Thierry > > > > ________________________________________ > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > > Date d'envoi : mercredi 19 juin 2013 21:21 > > Ã : Pharo Development List > > Objet : Re: [Pharo-dev] you may need to update your configurations > > > > > > > > > > >> Christophe. > > >> > > >> [1] https://pharo.fogbugz.com/default.asp?10801 > > > > > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > > > > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or fighting every few days with 3.0 and knowing that anyway it's not production ready. I had to cope with 1.4 not being able to handle utf8 in the same way. > > > > Thierry what we can do is the following: > > have a look at the fix of nicolas and we can try to add to th 2.0 batch but we should pay attention > > not to introduce other bugs (because I'm afraid it will). > > > > BTW 30 is not that instable. > > > > > > > The window for my next serious developpement with Pharo is around 2014, so I guess I could just sit and wait. > > > > > > By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > > > > > > > >

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Nicolas Cellier

Yes, this part is perfectly correct. It's just that I used ZnInvalidUTF8 in TextConverter which introduces a dependency of TextConverter on Zinc. This only make sense if in the long term we replace those TextConverters by cleaner Zinc encoders/decoders. 2013/6/19 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 19 Jun 2013, at 22:33, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > The change is very light, I applied it almost unchanged on Squeak (can't > remember which version was the first). > > The only thing we neeed is to catch an UTF8Error. > > > > Since in Pharo there are two encoder/decoder hierarchies, and since that > of Zinc is cleaner, I made a bet on future and chose to make UTF8Error a > subclass of existing already Zn Encoding/Decoding exception. > > > > But we still use the old TextConverter hierarchy in MC, even in Pharo > 3.0. > > So the dependency on Zinc is totally arbitrary and un-necessary right > now; it does not exist in Smalltalk version. > > It's just a bet on the future. > > For a backport to 2.0, I would just use an UTF8Error like in Squeak and > avoid any dependency on Zinc. > > Well ZnInvalidUTF8 is now a full part of Zinc itself > (Zinc-Character-Encoding-Core to be exact). It is already in 3.0 (with your > code) and I guess we'll upgrade Zinc in 2.0 as well. But is is a > dependency, that is correct. > > Anyway, we have to double check. > > > Nicolas > > > > > > 2013/6/19 GOUBIER Thierry <thierry.goubier(a)cea.fr> > > StÃ©phane, > > > > I'll probably have a look at Nicolas fix anyway, but as it required also > a change to Zinc... then I started to worry. But it may be better than > trying to fix ZipArchive incorrect encoding issues from the outside (by > forcing an utf8 conversion out of the contents of the ZipArchive members). > > > > If I manage to make sense of it, I'll put a enhancement request in > FogBuz with a slice. > > > > Yes, I think 30 is not that unstable, like 2.0 was before ... except > that I'm fairly dependent on the RPackage infrastructure, and I prefer to > wait until the RPackage refactoring is done ;-) > > > > Thierry > > > > ________________________________________ > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de > StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > > Date d'envoi : mercredi 19 juin 2013 21:21 > > Ã : Pharo Development List > > Objet : Re: [Pharo-dev] you may need to update your configurations > > > > > > > > > > >> Christophe. > > >> > > >> [1] https://pharo.fogbugz.com/default.asp?10801 > > > > > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > > > > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or > so or fighting every few days with 3.0 and knowing that anyway it's not > production ready. I had to cope with 1.4 not being able to handle utf8 in > the same way. > > > > Thierry what we can do is the following: > > have a look at the fix of nicolas and we can try to add to th > 2.0 batch but we should pay attention > > not to introduce other bugs (because I'm afraid it will). > > > > BTW 30 is not that instable. > > > > > > > The window for my next serious developpement with Pharo is around > 2014, so I guess I could just sit and wait. > > > > > > By the way, why the change in > MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > > > > > > > >

June 19, 2013

Re: [Pharo-dev] Pharo MIDIPlugin

by Nicolas Cellier

At some point, I remember that there have been a mess when merging changes from interpreter-VM in cog-vm branch. This might have infected the Pharo-branch and this plugin may have been retracted at that time. I'm not really sure, but that would be my starting point for inquiring about MIDIPlugin status (that's what a CI server can serve well). 2013/6/19 jannik.laval <jannik.laval(a)gmail.com> > MIDIPlugin is loaded in a prvious PharoVM version (7.zip in the file > directory). > Here is the system report, probably something has change since this > version: > > === > Image > ----- > /Users/janniklaval/Desktop/Pharo-2.0/Pharo-2.0.image > Pharo2.0 > Latest update: #20593 > Unnamed > > Virtual Machine > --------------- > /Users/janniklaval/Desktop/Pharo-2.0/Pharo.app/Contents/MacOS/Pharo > NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: > 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 > NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: > 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 > git://gitorious.org/cogvm/blessed.git Commit: > 452863bdfba2ba0b188e7b172e9bc597a2caa928 Date: 2012-12-07 16:49:46 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #5922 > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: > 452863bdfba2ba0b188e7b172e9bc597a2caa928 Date: 2012-12-07 16:49:46 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #5922 > NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: > 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 > NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: > 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 > === > > Jannik > > On Jun 19, 2013, at 10:05 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > > caseOf: MacOSX > > 1. MIDIPlugin in Pharo vm requires SerialPlugin (see sqMacMIDI.c). > 2. source of SerialPlugin is sqUnixSerial.c (see MacOSConfig>> > configureSerialPlugin: in vmmaker-image). > 3. at midiInit() of sqMacMIDI.c, it checks the functions of SerialPlugin, > but functions below ware missing. > serialPortIsOpen > serialPortSetControl > serialPortNames > serialPortCount > So midiInit() returns interpreterProxy success: false. it causes primitive > error while loading. > > 2013/05/03, i'd tried to build vm after these ioLoadFunctionFrom 4 > functions comment out, and load sound package from PharoExtras, it could > use ScorePlayer. yes, checked midi-out only. > > at least up to Pharo 1.2 MIDIPlugin was loaded. > > regards. > > > > > 2013/6/20 jannik.laval <jannik.laval(a)gmail.com> > >> In a previous version it was loaded, but I don't remember which one. >> >> Jannik >> >> On Jun 19, 2013, at 9:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >> yes. >> >> On Jun 19, 2013, at 6:56 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >> >> Mac OS X? >> >> >> 2013/6/19 jannik laval <jannik.laval(a)gmail.com> >> >>> Hi pharoers, >>> >>> It seems that MidiPlugin is not loaded in Pharo2.0. >>> The plugin is present in the repository, but when I try "Smalltalk >>> loadModule: 'MIDIPlugin'" it raises an error. >>> >>> In "Smalltalk listLoadedModules" and "Smalltalk listBuiltinModules" >>> there is no MIDIPlugin. >>> Could someone give me some help to solve this ? >>> >>> Jannik >>> >> >> >> >> -- >> -- >> "NISHIHARA Satoshi" >> [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >> >> >> >> > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > > >

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Sven Van Caekenberghe

On 19 Jun 2013, at 22:33, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > The change is very light, I applied it almost unchanged on Squeak (can't remember which version was the first). > The only thing we neeed is to catch an UTF8Error. > > Since in Pharo there are two encoder/decoder hierarchies, and since that of Zinc is cleaner, I made a bet on future and chose to make UTF8Error a subclass of existing already Zn Encoding/Decoding exception. > > But we still use the old TextConverter hierarchy in MC, even in Pharo 3.0. > So the dependency on Zinc is totally arbitrary and un-necessary right now; it does not exist in Smalltalk version. > It's just a bet on the future. > For a backport to 2.0, I would just use an UTF8Error like in Squeak and avoid any dependency on Zinc. Well ZnInvalidUTF8 is now a full part of Zinc itself (Zinc-Character-Encoding-Core to be exact). It is already in 3.0 (with your code) and I guess we'll upgrade Zinc in 2.0 as well. But is is a dependency, that is correct. Anyway, we have to double check. > Nicolas > > > 2013/6/19 GOUBIER Thierry <thierry.goubier(a)cea.fr> > StÃ©phane, > > I'll probably have a look at Nicolas fix anyway, but as it required also a change to Zinc... then I started to worry. But it may be better than trying to fix ZipArchive incorrect encoding issues from the outside (by forcing an utf8 conversion out of the contents of the ZipArchive members). > > If I manage to make sense of it, I'll put a enhancement request in FogBuz with a slice. > > Yes, I think 30 is not that unstable, like 2.0 was before ... except that I'm fairly dependent on the RPackage infrastructure, and I prefer to wait until the RPackage refactoring is done ;-) > > Thierry > > ________________________________________ > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Date d'envoi : mercredi 19 juin 2013 21:21 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] you may need to update your configurations > > > > > > >> Christophe. > >> > >> [1] https://pharo.fogbugz.com/default.asp?10801 > > > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or fighting every few days with 3.0 and knowing that anyway it's not production ready. I had to cope with 1.4 not being able to handle utf8 in the same way. > > Thierry what we can do is the following: > have a look at the fix of nicolas and we can try to add to th 2.0 batch but we should pay attention > not to introduce other bugs (because I'm afraid it will). > > BTW 30 is not that instable. > > > > The window for my next serious developpement with Pharo is around 2014, so I guess I could just sit and wait. > > > > By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > >

June 19, 2013

Re: [Pharo-dev] NBOpenGL

by Alexandre Bergel

>> Are there some resources that are not freed when I saved my image? How can I reset them? >> > According to your log, NB cannot get source code of methods. make > sure .source and .changes > files are accessible to image. Ah yes! Thanks Igor! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 19, 2013

Re: [Pharo-dev] you may need to update your configurations

by Nicolas Cellier

The change is very light, I applied it almost unchanged on Squeak (can't remember which version was the first). The only thing we neeed is to catch an UTF8Error. Since in Pharo there are two encoder/decoder hierarchies, and since that of Zinc is cleaner, I made a bet on future and chose to make UTF8Error a subclass of existing already Zn Encoding/Decoding exception. But we still use the old TextConverter hierarchy in MC, even in Pharo 3.0. So the dependency on Zinc is totally arbitrary and un-necessary right now; it does not exist in Smalltalk version. It's just a bet on the future. For a backport to 2.0, I would just use an UTF8Error like in Squeak and avoid any dependency on Zinc. Nicolas 2013/6/19 GOUBIER Thierry <thierry.goubier(a)cea.fr> > StÃ©phane, > > I'll probably have a look at Nicolas fix anyway, but as it required also a > change to Zinc... then I started to worry. But it may be better than trying > to fix ZipArchive incorrect encoding issues from the outside (by forcing an > utf8 conversion out of the contents of the ZipArchive members). > > If I manage to make sense of it, I'll put a enhancement request in FogBuz > with a slice. > > Yes, I think 30 is not that unstable, like 2.0 was before ... except that > I'm fairly dependent on the RPackage infrastructure, and I prefer to wait > until the RPackage refactoring is done ;-) > > Thierry > > ________________________________________ > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de StÃ©phane > Ducasse [stephane.ducasse(a)inria.fr] > Date d'envoi : mercredi 19 juin 2013 21:21 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] you may need to update your configurations > > > > > > >> Christophe. > >> > >> [1] https://pharo.fogbugz.com/default.asp?10801 > > > > Ouch. Does not bode too well for backporting that to Pharo 2.0. > > > > I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or > so or fighting every few days with 3.0 and knowing that anyway it's not > production ready. I had to cope with 1.4 not being able to handle utf8 in > the same way. > > Thierry what we can do is the following: > have a look at the fix of nicolas and we can try to add to th 2.0 > batch but we should pay attention > not to introduce other bugs (because I'm afraid it will). > > BTW 30 is not that instable. > > > > The window for my next serious developpement with Pharo is around 2014, > so I guess I could just sit and wait. > > > > By the way, why the change in > MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? > > >

June 19, 2013

Re: [Pharo-dev] Pharo MIDIPlugin

by jannik.laval

MIDIPlugin is loaded in a prvious PharoVM version (7.zip in the file directory). Here is the system report, probably something has change since this version: === Image ----- /Users/janniklaval/Desktop/Pharo-2.0/Pharo-2.0.image Pharo2.0 Latest update: #20593 Unnamed Virtual Machine --------------- /Users/janniklaval/Desktop/Pharo-2.0/Pharo.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 git://gitorious.org/cogvm/blessed.git Commit: 452863bdfba2ba0b188e7b172e9bc597a2caa928 Date: 2012-12-07 16:49:46 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #5922 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 452863bdfba2ba0b188e7b172e9bc597a2caa928 Date: 2012-12-07 16:49:46 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #5922 NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Dec 12 2012 === Jannik On Jun 19, 2013, at 10:05 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > caseOf: MacOSX > > 1. MIDIPlugin in Pharo vm requires SerialPlugin (see sqMacMIDI.c). > 2. source of SerialPlugin is sqUnixSerial.c (see MacOSConfig>>configureSerialPlugin: in vmmaker-image). > 3. at midiInit() of sqMacMIDI.c, it checks the functions of SerialPlugin, but functions below ware missing. > serialPortIsOpen > serialPortSetControl > serialPortNames > serialPortCount > So midiInit() returns interpreterProxy success: false. it causes primitive error while loading. > > 2013/05/03, i'd tried to build vm after these ioLoadFunctionFrom 4 functions comment out, and load sound package from PharoExtras, it could use ScorePlayer. yes, checked midi-out only. > > at least up to Pharo 1.2 MIDIPlugin was loaded. > > regards. > > > > > 2013/6/20 jannik.laval <jannik.laval(a)gmail.com> > In a previous version it was loaded, but I don't remember which one. > > Jannik > > On Jun 19, 2013, at 9:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> yes. >> >> On Jun 19, 2013, at 6:56 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >> >>> Mac OS X? >>> >>> >>> 2013/6/19 jannik laval <jannik.laval(a)gmail.com> >>> Hi pharoers, >>> >>> It seems that MidiPlugin is not loaded in Pharo2.0. >>> The plugin is present in the repository, but when I try "Smalltalk loadModule: 'MIDIPlugin'" it raises an error. >>> >>> In "Smalltalk listLoadedModules" and "Smalltalk listBuiltinModules" there is no MIDIPlugin. >>> Could someone give me some help to solve this ? >>> >>> Jannik >>> >>> >>> >>> -- >>> -- >>> "NISHIHARA Satoshi" >>> [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >> > > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

June 19, 2013

Re: [Pharo-dev] Pharo MIDIPlugin

by NISHIHARA Satoshi

caseOf: MacOSX 1. MIDIPlugin in Pharo vm requires SerialPlugin (see sqMacMIDI.c). 2. source of SerialPlugin is sqUnixSerial.c (see MacOSConfig>> configureSerialPlugin: in vmmaker-image). 3. at midiInit() of sqMacMIDI.c, it checks the functions of SerialPlugin, but functions below ware missing. serialPortIsOpen serialPortSetControl serialPortNames serialPortCount So midiInit() returns interpreterProxy success: false. it causes primitive error while loading. 2013/05/03, i'd tried to build vm after these ioLoadFunctionFrom 4 functions comment out, and load sound package from PharoExtras, it could use ScorePlayer. yes, checked midi-out only. at least up to Pharo 1.2 MIDIPlugin was loaded. regards. 2013/6/20 jannik.laval <jannik.laval(a)gmail.com> > In a previous version it was loaded, but I don't remember which one. > > Jannik > > On Jun 19, 2013, at 9:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > yes. > > On Jun 19, 2013, at 6:56 PM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > > Mac OS X? > > > 2013/6/19 jannik laval <jannik.laval(a)gmail.com> > >> Hi pharoers, >> >> It seems that MidiPlugin is not loaded in Pharo2.0. >> The plugin is present in the repository, but when I try "Smalltalk >> loadModule: 'MIDIPlugin'" it raises an error. >> >> In "Smalltalk listLoadedModules" and "Smalltalk listBuiltinModules" there >> is no MIDIPlugin. >> Could someone give me some help to solve this ? >> >> Jannik >> > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > > > > -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

June 19, 2013