- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by kilon alios

oh my bad, I had it in one of the early drafts of the video tutorial (had to do several times to cut it down to 10 minutes) but I forgot to include it. Anyway this is how you do it. On Mon, Dec 1, 2014 at 10:33 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > someone did not watch my video tutorial about github ;D > > go to your github repo front page on the right side you will see an icon > labeled settings click on it and the first setting will you see is how to > rename the repo. > > On Sun, Nov 30, 2014 at 9:51 PM, stepharo <stepharo(a)free.fr> wrote: > >> great now I can compile :) >> About your question about moving >> >> PharoWebStack should be renamed PharoWeb: a Tutorial >> >> EntreprisePharo should be renamed PharoWebStack >> But I do not know how to do that on github. >> >> Stef >> >> Le 29/11/14 23:22, Luc Fabresse a Ã©crit : >> >> >> now I can compile. >> I've pushed some fixes on github, we will see if it now breaks for other >> ;-) >> >> @Stef: >> $ luatex -v >> This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_3) >> (rev 4971) >> >> do a macport update if you do not have this version. >> $ sudo port selfupdate >> $ sudo port update outdated >> >> Then, you should be able to compile the latest version on github. >> >> Cheers, >> >> #Luc >> >> 2014-11-29 9:23 GMT+01:00 Luc Fabresse <luc.fabresse(a)gmail.com>: >> >>> >>> can one of you just give me the result of: >>> >>> luatex -v >>> >>> that works compiling the chapter. >>> then, I will investigate. >>> >>> #Luc >>> >>> 2014-11-29 8:55 GMT+01:00 stepharo <stepharo(a)free.fr>: >>> >>>> The problem is not related to that. >>>> To display the full encoding the guys here (damien * damien) only found >>>> luaTex working. >>>> But LuaTex does not work well on our machines apparently. >>>> >>>> Le 29/11/14 02:38, Ben Coman a Ã©crit : >>>> >>>> kilon alios wrote: >>>>> >>>>>> have you tried MacTex ? >>>>>> >>>>>> https://tug.org/mactex/ >>>>>> >>>>>> its what I use with my iMac and so far has been working for me >>>>>> without any issues. >>>>>> >>>>> >>>>> I also ended up using MaxTex fairly easily. (I can't remember which >>>>> other one originally tried that had some issues.) >>>>> cheers -ben >>>>> >>>>> >>>>>> On Sat, Nov 29, 2014 at 12:02 AM, Luc Fabresse < >>>>>> luc.fabresse(a)gmail.com <mailto:luc.fabresse@gmail.com>> wrote: >>>>>> >>>>>> Hi All, >>>>>> >>>>>> I cannot compile the latest version in >>>>>> SquareBracketAssociates/EnterprisePharo.git >>>>>> My problem is that the "FiraSans" cannot be found. >>>>>> But in common.tex, the font path is correctly set up and the font >>>>>> is >>>>>> there. >>>>>> >>>>>> So on CI which version of luatex is used? >>>>>> I did not find it in the Jenkins log. >>>>>> >>>>>> I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts >>>>>> 2014_1) (rev 4971) >>>>>> >>>>>> Cheers, >>>>>> >>>>>> #Luc >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> >> >

Dec. 1, 2014

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by kilon alios

someone did not watch my video tutorial about github ;D go to your github repo front page on the right side you will see an icon labeled settings click on it and the first setting will you see is how to rename the repo. On Sun, Nov 30, 2014 at 9:51 PM, stepharo <stepharo(a)free.fr> wrote: > great now I can compile :) > About your question about moving > > PharoWebStack should be renamed PharoWeb: a Tutorial > > EntreprisePharo should be renamed PharoWebStack > But I do not know how to do that on github. > > Stef > > Le 29/11/14 23:22, Luc Fabresse a Ã©crit : > > > now I can compile. > I've pushed some fixes on github, we will see if it now breaks for other > ;-) > > @Stef: > $ luatex -v > This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_3) (rev > 4971) > > do a macport update if you do not have this version. > $ sudo port selfupdate > $ sudo port update outdated > > Then, you should be able to compile the latest version on github. > > Cheers, > > #Luc > > 2014-11-29 9:23 GMT+01:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > >> >> can one of you just give me the result of: >> >> luatex -v >> >> that works compiling the chapter. >> then, I will investigate. >> >> #Luc >> >> 2014-11-29 8:55 GMT+01:00 stepharo <stepharo(a)free.fr>: >> >>> The problem is not related to that. >>> To display the full encoding the guys here (damien * damien) only found >>> luaTex working. >>> But LuaTex does not work well on our machines apparently. >>> >>> Le 29/11/14 02:38, Ben Coman a Ã©crit : >>> >>> kilon alios wrote: >>>> >>>>> have you tried MacTex ? >>>>> >>>>> https://tug.org/mactex/ >>>>> >>>>> its what I use with my iMac and so far has been working for me without >>>>> any issues. >>>>> >>>> >>>> I also ended up using MaxTex fairly easily. (I can't remember which >>>> other one originally tried that had some issues.) >>>> cheers -ben >>>> >>>> >>>>> On Sat, Nov 29, 2014 at 12:02 AM, Luc Fabresse <luc.fabresse(a)gmail.com >>>>> <mailto:luc.fabresse@gmail.com>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I cannot compile the latest version in >>>>> SquareBracketAssociates/EnterprisePharo.git >>>>> My problem is that the "FiraSans" cannot be found. >>>>> But in common.tex, the font path is correctly set up and the font >>>>> is >>>>> there. >>>>> >>>>> So on CI which version of luatex is used? >>>>> I did not find it in the Jenkins log. >>>>> >>>>> I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts >>>>> 2014_1) (rev 4971) >>>>> >>>>> Cheers, >>>>> >>>>> #Luc >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> > >

Dec. 1, 2014

Woden-GT integration

by Yuriy Tymchuk

Hi everyone, I think that during ESUG Woden was integrated into Toolkit in a way, what you can see a 3D visualization as one of the representations of the view. Is there any additional package that provides this functionality? Uko

Dec. 1, 2014

WhatsUp from: 2014-12-01 until: 2014-12-14

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-12-14 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Dec. 1, 2014

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by Luc Fabresse

2014-11-30 20:51 GMT+01:00 stepharo <stepharo(a)free.fr>: > great now I can compile :) > cool! > About your question about moving > > PharoWebStack should be renamed PharoWeb: a Tutorial > > EntreprisePharo should be renamed PharoWebStack > ok > But I do not know how to do that on github. > I do not know Luc > Stef > > Le 29/11/14 23:22, Luc Fabresse a Ã©crit : > > > now I can compile. > I've pushed some fixes on github, we will see if it now breaks for other > ;-) > > @Stef: > $ luatex -v > This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_3) (rev > 4971) > > do a macport update if you do not have this version. > $ sudo port selfupdate > $ sudo port update outdated > > Then, you should be able to compile the latest version on github. > > Cheers, > > #Luc > > 2014-11-29 9:23 GMT+01:00 Luc Fabresse <luc.fabresse(a)gmail.com>: > >> >> can one of you just give me the result of: >> >> luatex -v >> >> that works compiling the chapter. >> then, I will investigate. >> >> #Luc >> >> 2014-11-29 8:55 GMT+01:00 stepharo <stepharo(a)free.fr>: >> >>> The problem is not related to that. >>> To display the full encoding the guys here (damien * damien) only found >>> luaTex working. >>> But LuaTex does not work well on our machines apparently. >>> >>> Le 29/11/14 02:38, Ben Coman a Ã©crit : >>> >>> kilon alios wrote: >>>> >>>>> have you tried MacTex ? >>>>> >>>>> https://tug.org/mactex/ >>>>> >>>>> its what I use with my iMac and so far has been working for me without >>>>> any issues. >>>>> >>>> >>>> I also ended up using MaxTex fairly easily. (I can't remember which >>>> other one originally tried that had some issues.) >>>> cheers -ben >>>> >>>> >>>>> On Sat, Nov 29, 2014 at 12:02 AM, Luc Fabresse <luc.fabresse(a)gmail.com >>>>> <mailto:luc.fabresse@gmail.com>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I cannot compile the latest version in >>>>> SquareBracketAssociates/EnterprisePharo.git >>>>> My problem is that the "FiraSans" cannot be found. >>>>> But in common.tex, the font path is correctly set up and the font >>>>> is >>>>> there. >>>>> >>>>> So on CI which version of luatex is used? >>>>> I did not find it in the Jenkins log. >>>>> >>>>> I am using LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts >>>>> 2014_1) (rev 4971) >>>>> >>>>> Cheers, >>>>> >>>>> #Luc >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> > >

Nov. 30, 2014

Re: [Pharo-dev] New Cog VMs available

by Tudor Girba

+1 Doru On Sun, Nov 30, 2014 at 8:57 PM, stepharo <stepharo(a)free.fr> wrote: > No problem! Thanks for creating this great asset! > > Stef > > > > On Fri, Nov 21, 2014 at 4:08 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3144. >> >> Apologies; the 3143 VMs were broken. >> > > and I'm sorry to say the 3144 look broken too. I suspect the VM is not > correctly normalizing bit-operations on large integers into SmallIntegers > as expected. > > >> CogVM binaries as per VMMaker.oscog-eem.950/r3144 >> >> Fix regression in new primitiveBitShift. >> Introduce >>> as an explicitly signed shift. >> 64-bit ize magnitude64BitIntegerFor:neg:, >> positive64BitIntegerFor: & signed64BitIntegerFor: >> -- >> best, >> Eliot >> > > > > -- > best, > Eliot > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 30, 2014

Re: [Pharo-dev] New Cog VMs available

by stepharo

No problem! Thanks for creating this great asset! Stef > > > On Fri, Nov 21, 2014 at 4:08 PM, Eliot Miranda > <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3144 > <http://www.mirandabanda.org/files/Cog/VM/VM.r3144>. > > Apologies; the 3143 VMs were broken. > > > and I'm sorry to say the 3144 look broken too. I suspect the VM is > not correctly normalizing bit-operations on large integers into > SmallIntegers as expected. > > > CogVM binaries as per VMMaker.oscog-eem.950/r3144 > > Fix regression in new primitiveBitShift. > Introduce >>> as an explicitly signed shift. > 64-bit ize magnitude64BitIntegerFor:neg:, > positive64BitIntegerFor: & signed64BitIntegerFor: > -- > best, > Eliot > > > > > -- > best, > Eliot

Nov. 30, 2014

Re: [Pharo-dev] merge conflict (issue validator)

by stepharo

I do not know either and I hate the reclassification because after it drops from our radar. Le 29/11/14 23:04, Nicolai Hess a Ã©crit : > I don't understand this merge conflict in hte issue validation for > case 14288 <https://pharo.fogbugz.com/default.asp?14288> > I can manually load the slice and it does not show any conflicts. > > Any ideas? > >

Nov. 30, 2014

Re: [Pharo-dev] ensure: and assignments RB Rule

by stepharo

thanks we should open a bug entry to improve the class comment of this rule. Any taker? Stef Le 30/11/14 12:10, Thierry Goubier a Ã©crit : > Le 30/11/2014 12:01, Max Leske a Ã©crit : >> >>> On 30.11.2014, at 11:18, Thierry Goubier <thierry.goubier(a)gmail.com> >>> wrote: >>> >>> Le 30/11/2014 11:06, Max Leske a Ã©crit : >>>> The code would look like this: >>>> >>>> [ | file | >>>> file := StandardFileStream forceNewFileNamed: âfooâ. >>>> file nextPutAll: âbarâ ] >>>> ensure: [ file close ]. >>>> >>>> Why that is considered bad practice however, I canât tell. >>> >>> This one would fail because file is a temp to the block (and not >>> visible to the ensure block). >> >> If it werenât visible, wouldnât the compiler raise an exception? > > In your example, yes. > > But the rule matched: > > | file | > [ > file := StandardFileStream forceNewFileNamed: âfooâ. > file nextPutAll: âbarâ ] > ensure: [ file close ]. > > (Hum: wouldn't the compiler complain of file might be nil in the > ensure block?) > >>> Another problem is that, if you have a failure in >>> forceNewFileNamed:, file is nil and the ensure: fail as well. >> >> True, but thatâs a problem this rule doesnât really cover I guess. >> That oneâs up to the developer. > > I would expect that rule to flag bad coding practices, and I think it > does ;) > > Thierry > >

Nov. 30, 2014

Re: [Pharo-dev] Compilation error of the PharoEnterprise book with luatex

by stepharo

great now I can compile :) About your question about moving PharoWebStack should be renamed PharoWeb: a Tutorial EntreprisePharo should be renamed PharoWebStack But I do not know how to do that on github. Stef Le 29/11/14 23:22, Luc Fabresse a Ã©crit : > > now I can compile. > I've pushed some fixes on github, we will see if it now breaks for > other ;-) > > @Stef: > $ luatex -v > This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/MacPorts 2014_3) > (rev 4971) > > do a macport update if you do not have this version. > $ sudo port selfupdate > $ sudo port update outdated > > Then, you should be able to compile the latest version on github. > > Cheers, > > #Luc > > 2014-11-29 9:23 GMT+01:00 Luc Fabresse <luc.fabresse(a)gmail.com > <mailto:luc.fabresse@gmail.com>>: > > > can one of you just give me the result of: > > luatex -v > > that works compiling the chapter. > then, I will investigate. > > #Luc > > 2014-11-29 8:55 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > The problem is not related to that. > To display the full encoding the guys here (damien * damien) > only found luaTex working. > But LuaTex does not work well on our machines apparently. > > Le 29/11/14 02:38, Ben Coman a Ã©crit : > > kilon alios wrote: > > have you tried MacTex ? > > https://tug.org/mactex/ > > its what I use with my iMac and so far has been > working for me without any issues. > > > I also ended up using MaxTex fairly easily. (I can't > remember which other one originally tried that had some > issues.) > cheers -ben > > > On Sat, Nov 29, 2014 at 12:02 AM, Luc Fabresse > <luc.fabresse(a)gmail.com > <mailto:luc.fabresse@gmail.com> > <mailto:luc.fabresse@gmail.com > <mailto:luc.fabresse@gmail.com>>> wrote: > > Hi All, > > I cannot compile the latest version in > SquareBracketAssociates/EnterprisePharo.git > My problem is that the "FiraSans" cannot be found. > But in common.tex, the font path is correctly set > up and the font is > there. > > So on CI which version of luatex is used? > I did not find it in the Jenkins log. > > I am using LuaTeX, Version beta-0.79.1 (TeX Live > 2014/MacPorts > 2014_1) (rev 4971) > > Cheers, > > #Luc > > > > > > > > >

Nov. 30, 2014