November 2014 - Pharo-users

Re: [Pharo-users] Porting to a MAC

by garduino

Ian Bartholomew-23 wrote > Thanks to you both for the confirmation about using the Windows files, it > will make things a lot simpler. > > Given the situation I imagine there are a number of ex Dolphin users > floating about here - Hi All. I noticed the, sadly, late Bill Schwab > posted here sometimes, and he was once as much a committed a Dolphin user > as I was. I shall continue using Dolphin though, the ability to create > Windows executables is too useful to give up. Yes, it was a sad news of Bill's death, I read the list of Dolphin. About Dolphin, well, as you point, the ability to generate an exe and some other features more of the side of publishing a commercial app, make hard to abandon it (also the UI builder). My password manager PasswordsPro is still in Dolphin and will stay there for some time yet ... -- View this message in context: http://forum.world.st/Porting-to-a-MAC-tp4788105p4788123.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 2, 2014

Re: [Pharo-users] Bug? in Filein

by Nicolai Hess

Actually it is a bug in FileOUT! 14377 <https://pharo.fogbugz.com/default.asp?14377> FileOut creates invalid comment entries for classes with class side methods 2014-11-02 17:42 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > 2014-10-31 0:11 GMT+01:00 JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com>: > >> I see. But WATestError it is in the same package it is "Fileing", on line >> 3284 and is referenced many times before. I am sorry I have not enough >> knowledge about the internals to do more debugging. >> >> Seems to be a lack of coordination between FileOut and FileIn. Maybe >> nothing to do... >> >> Now a simpler and clearer test: >> >> 1. Back to the original situation. >> 2. FileOut *only* WAContextTest. It has a comment: "I am the base class >> for all tests that need a WARequestContext present.", in .st file in line 8. >> 3. Remove it. >> 4. FileIn again. No errors on Transcript BUT no comment appears for >> WAContextTest. >> >> Maybe, if I get a couple of free hours I could dare to debug a little.... >> >> Best >> >> >> 2014-10-30 23:30 GMT+01:00 stepharo <stepharo(a)free.fr>: >> >>> It says that the class WATestError is not available. >>> >>> >>> >>> Yes, I did. It is in the .st file >>> >>> >>> >>>> c. You get a bunch of errors in Transcript while filing in >>>>> >>>> No magic ball so we cannot guess. >>>> >>>> >>> Example of Transcript messages (in case it helps): >>> WADocumentHandlerResponseTest>>createAndVerifyBinaryDocumentNamed:hasAttachment: >>> (WATestingFiles is Undeclared) >>> >>> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >>> Undeclared) >>> >>> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >>> Undeclared) >>> >>> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >>> Undeclared) >>> >>> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >>> Undeclared) >>> >>> WAExceptionHandlerTest>>testInternalError (WATestError is Undeclared) >>> >>> >>> It happens in more cases. I just took this one because this is a >>> package anyone can install in order to reproduce the problem. >>> >>> Thanks >>> >>> >>> >> > > Yes, it is a bug. Verified on Pharo4 with class ZnMessageBenchmark. The > class has a comment, after fileout/remove class/filein this class is > without a comment. > I'll open a bug report. > >

Nov. 2, 2014

Re: [Pharo-users] Porting to a MAC

by stepharo

> Thanks to you both for the confirmation about using the Windows files, it > will make things a lot simpler. > > Given the situation I imagine there are a number of ex Dolphin users > floating about here - Hi All. I noticed the, sadly, late Bill Schwab > posted here sometimes, and he was once as much a committed a Dolphin user > as I was. I shall continue using Dolphin though, the ability to create > Windows executables is too useful to give up. I imagine. > > My only problem now is that as I ported my app from Dolphin to Pharo I > made some significant changes - so now I've got to port it back the other > way!

Nov. 2, 2014

Re: [Pharo-users] Porting to a MAC

by stepharo

On 2/11/14 19:45, Ian Bartholomew wrote: > Hi All. I'm a long time (25+ years) Smalltalk user, but only 3 days using > Pharo Welcome! > so I'm still stumbling around a bit (lot). You will get there :) > > I have an app that I need to run on Windows and a Mac (possibly Linux at a > later date). I've ported the code over from Dolphin and got it working > using Pharo 3.0 on my Windows box. I am just going to set the app > running, save the image and then send the whole Pharo folder over to the > Windows user - that will work won't it? Yes why it would not :) > The problem is the Mac user. As I can't set up the Mac image in the same > way (I have no access to a Mac box) I was wondering if I could just > replace the changes,sources and image files in the Mac download with the > ones I've set up for Windows and send that to him. Yes it should work. You can also ask us to try on our macs. > Would that work or do I need to send him file outs of my code and talk him through install and > set-up. You can use the one-click setup?

Nov. 2, 2014

Re: [Pharo-users] Porting to a MAC

by Ian Bartholomew

Thanks to you both for the confirmation about using the Windows files, it will make things a lot simpler. Given the situation I imagine there are a number of ex Dolphin users floating about here - Hi All. I noticed the, sadly, late Bill Schwab posted here sometimes, and he was once as much a committed a Dolphin user as I was. I shall continue using Dolphin though, the ability to create Windows executables is too useful to give up. My only problem now is that as I ported my app from Dolphin to Pharo I made some significant changes - so now I've got to port it back the other way!

Nov. 2, 2014

Re: [Pharo-users] Porting to a MAC

by garduino

Hi Ian: I know very well you (at least by the code that was very helpful to me on Dolphin!). Thanks for such contributions to the community! And yes, the image, changes and source are interchangeable between operating systems with no problems. -- View this message in context: http://forum.world.st/Porting-to-a-MAC-tp4788105p4788108.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 2, 2014

Re: [Pharo-users] Porting to a MAC

by kilon alios

no you should be fine, changes is OS-independent and so is the image, but you need the mac zip for all the other files, dynamic linked libraries and of course the executable binary. By the way you can install macos on windows via hackintosh and a VM like virtualbox so you can test this for yourself. You can even dual boot with windows and macos. An alternative which makes it very easy to install is via configuration browser, its a bit more work on your side as the developer but it is super easy for the user, the user can download pharo from the pharo website, open it , open world menu, go to tools, open configuration browser and click install on your project. But this way you will make it available for all pharoers which is something you may not want. On Sun, Nov 2, 2014 at 8:45 PM, Ian Bartholomew <ian(a)tcse327.eu> wrote: > Hi All. I'm a long time (25+ years) Smalltalk user, but only 3 days using > Pharo so I'm still stumbling around a bit (lot). > > I have an app that I need to run on Windows and a Mac (possibly Linux at a > later date). I've ported the code over from Dolphin and got it working > using Pharo 3.0 on my Windows box. I am just going to set the app > running, save the image and then send the whole Pharo folder over to the > Windows user - that will work won't it? > > The problem is the Mac user. As I can't set up the Mac image in the same > way (I have no access to a Mac box) I was wondering if I could just > replace the changes,sources and image files in the Mac download with the > ones I've set up for Windows and send that to him. Would that work or do > I need to send him file outs of my code and talk him through install and > set-up. > > Thanks > > >

Nov. 2, 2014

Porting to a MAC

by Ian Bartholomew

Hi All. I'm a long time (25+ years) Smalltalk user, but only 3 days using Pharo so I'm still stumbling around a bit (lot). I have an app that I need to run on Windows and a Mac (possibly Linux at a later date). I've ported the code over from Dolphin and got it working using Pharo 3.0 on my Windows box. I am just going to set the app running, save the image and then send the whole Pharo folder over to the Windows user - that will work won't it? The problem is the Mac user. As I can't set up the Mac image in the same way (I have no access to a Mac box) I was wondering if I could just replace the changes,sources and image files in the Mac download with the ones I've set up for Windows and send that to him. Would that work or do I need to send him file outs of my code and talk him through install and set-up. Thanks

Nov. 2, 2014

Re: [Pharo-users] Bug? in Filein

by Nicolai Hess

2014-10-31 0:11 GMT+01:00 JosÃ© ComesaÃ±a <jose.comesana(a)gmail.com>: > I see. But WATestError it is in the same package it is "Fileing", on line > 3284 and is referenced many times before. I am sorry I have not enough > knowledge about the internals to do more debugging. > > Seems to be a lack of coordination between FileOut and FileIn. Maybe > nothing to do... > > Now a simpler and clearer test: > > 1. Back to the original situation. > 2. FileOut *only* WAContextTest. It has a comment: "I am the base class > for all tests that need a WARequestContext present.", in .st file in line 8. > 3. Remove it. > 4. FileIn again. No errors on Transcript BUT no comment appears for > WAContextTest. > > Maybe, if I get a couple of free hours I could dare to debug a little.... > > Best > > > 2014-10-30 23:30 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> It says that the class WATestError is not available. >> >> >> >> Yes, I did. It is in the .st file >> >> >> >>> c. You get a bunch of errors in Transcript while filing in >>>> >>> No magic ball so we cannot guess. >>> >>> >> Example of Transcript messages (in case it helps): >> WADocumentHandlerResponseTest>>createAndVerifyBinaryDocumentNamed:hasAttachment: >> (WATestingFiles is Undeclared) >> >> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >> Undeclared) >> >> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >> Undeclared) >> >> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >> Undeclared) >> >> WAExceptionHandlerTest>>testCommaReturnsExceptionSet (WATestError is >> Undeclared) >> >> WAExceptionHandlerTest>>testInternalError (WATestError is Undeclared) >> >> >> It happens in more cases. I just took this one because this is a >> package anyone can install in order to reproduce the problem. >> >> Thanks >> >> >> > Yes, it is a bug. Verified on Pharo4 with class ZnMessageBenchmark. The class has a comment, after fileout/remove class/filein this class is without a comment. I'll open a bug report.

Nov. 2, 2014

Re: [Pharo-users] Zoomable & Infinitely scrollable PasteupMorph

by Thierry Goubier

Le 02/11/2014 16:29, Nicolai Hess a Ã©crit : > 2014-11-02 15:22 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>>: > > Le 02/11/2014 15:15, stepharo a Ã©crit : > > > I gave up on zoomability (with the idea to revisit after > Athens is > integrated), > > > Athens is integrated. Now if the community does not help > redefining the > drawnOn: methods using athens then it will not happen. > > > And, speaking of infinite zoomability, you have a few surprises > waiting for you in Athens :( (some are from Athens design, others > may be linked to Cairo). > > > ? > What exactly? (1) Precisions issues: Athens/Cairo seems only precise at 0.001 points in Roassal space (independently of the scaling of the canvas, i.e. even if you camera scaling is 10 pixels for 0.001). (2) Limits: if your Athens coordinates are over a certain number (around 1e7, I believe), Athens stop displaying things (independently of the scaling, again) (3) Athens design: the idea of having a stroke width of 1 has strange effects (polygons with scaling being 10 pixels wide, but with a border a 100 pixels wide: certainly not what you expect to see displayed) (1) means that you can't zoom to a meter/pixel resolution without errors on a earth map where your scale is at 1 in roassal / 1km at equator. (2) means that nothing will be displayed on your map of earth if your scale is at 1 in Roassal/1m on Earth (i.e., if you try to solve 1 by increasing your scale, then you may end up with nothing displayed). (3) is just plain annoying, because of (2). For normal Roassal use, doesn't matter except if your unlucky with your scaling. When you start to play with geo-referenced data with a meter resolution, you are sure to hit them. I did ;) Luckily, at that stage I knew I had proper projections and coordinate transforms, otherwise I would have lost a lot of time. Thierry

Nov. 2, 2014