September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GToolkit in Pharo 4?

by Yuriy Tymchuk

So is it working for you? Because when I load it, I get emergency evaluator when debugger should openâ¦ Uko > On 29 Jul 2014, at 09:17, Max Leske <maxleske(a)gmail.com> wrote: > > Ok, thanks. > > > On 28.07.2014, at 22:37, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Just fix the configuration. Nothing there for pharo 4.x >> And as baseline012 refers to #development everywhere, >> you'll need to check all dependencies too >> >> Stephan >> > >

Sept. 22, 2014

Re: [Pharo-dev] Fixed case 11996 -- exception handler search bug

by Ben Coman

Martin McClure wrote: > This fix required multiple slices since loading things in the wrong > order broke exceptions badly enough to hang the system. I packaged > things in five slices. (It's possible that if Monticello was smart > enough I could have done it in less than five, but it did need more > than one). > > The automatic test runner seems to only load the first of the five > slices. Therefore two exception tests fail, which is expected. All > exception tests should pass after all five slices are loaded in order. > > Is there a way to tell the automatic test runner to load all five, or > does this one require manual testing? (I did test it manually before > dropping the slices in the inbox, but that was a month ago.) > > Regards, > > -Martin > > There is no built in mechanism for loading multiple slices. Now perhaps your slice can contain only a "Dummy class>>initialize" method that scripts Gopher to load the slices in order. Disclaimer, never tried it - just thinking out loud. cheers -ben

Sept. 22, 2014

Re: [Pharo-dev] [issue tracker] back porting 4 to 3

by Ben Coman

Sept. 22, 2014

Re: [Pharo-dev] Fixed case 11996 -- exception handler search bug

by Martin McClure

This fix required multiple slices since loading things in the wrong order broke exceptions badly enough to hang the system. I packaged things in five slices. (It's possible that if Monticello was smart enough I could have done it in less than five, but it did need more than one). The automatic test runner seems to only load the first of the five slices. Therefore two exception tests fail, which is expected. All exception tests should pass after all five slices are loaded in order. Is there a way to tell the automatic test runner to load all five, or does this one require manual testing? (I did test it manually before dropping the slices in the inbox, but that was a month ago.) Regards, -Martin

Sept. 22, 2014

Re: [Pharo-dev] Fixed case 11996 -- exception handler search bug

by Martin McClure

On 09/22/2014 12:12 AM, Marcus Denker wrote: > > On 22 Sep 2014, at 07:30, Martin McClure <martin(a)hand2mouse.com> wrote: > >> Andres and I developed a fix at ESUG for case 11996. The search for exception handlers was not taking into account the general case of exception handlers established or exceptions signaled while already in a handler block, so could find the wrong handler. >> >> I put the slices for this fix in the inbox a while back, but neglected to let the list know. >> >> Is there anything else I need to do to get this integrated into 4.0? >> > > it is important to notify about it. There are >600 issues in the tracker, that means that just solving something but not telling will only lead to action if > by chance someone looks a the issue tracker entry. (which means, it is very very unlikely). > > There are two ways to notify: > > 1) putting the issue to âfix review neededâ > 2) send a mail to the list > > (the second option is good for complex cases) OK, thanks. It would be good to add the "Press resolve" and "set to fix review needed" steps to http://pharo.org/contribute-propose-fix. Right now it just says" "Update the bug entry to mention that you submitted a slice in the inbox. Now you can feel good!" Regards, -Martin

Sept. 22, 2014

Re: [Pharo-dev] Exceptions chapter of Deep Into Pharo

by Martin McClure

On 09/21/2014 11:18 PM, stepharo wrote: > >> Since Andres and I were working on exceptions at ESUG, Stef asked me >> to review the Exceptions chapter of Deep Into Pharo. I've done this, >> and there are some changes needed to reflect the fix of issue 11996, >> and a number of other small improvements I'd like to make. > > super! > I love that. > Thanks a lot. >> So, a couple of questions: >> >> * Would now be a good time to update this chapter for Pharo 4.0? > > Yes! Definitevely. >> * What's the process for contributing updates to the book? > I can give you access to the svn or you can send to me text and I will > incorporate them. > (In the future we will turn it into pillar and github). > I would prefer that you edit because you are better fit technically and > english-wise :). OK, send me the SVN info and I'll work on the edits. Regards, -Martin

Sept. 22, 2014

DejaVu license

by Henrik Johansen

Now that the Classes from which the DejaVu StrikeFont instances were created have been removed from the image, where do we keep the required Copyright notices? http://dejavu-fonts.org/wiki/index.php?title=License Cheers, Henry

Sept. 22, 2014

Re: [Pharo-dev] How production ready is Pharo on SQLServer?

by Sebastian Sastre

Wonderful Torsten, thanks so much for that. Worked flawlessly from iPad > On 19/09/2014, at 18:36, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Sebastian, > > I think there are two ways for ODBC'ing from Pharo: > > 1. one is the one included in DBXTalk, I think I had this running also in the past and added > the glorp adaptor for ODBC. Cant remember why I switched to 2. > > 2. the ODBC package (on top of FFI) that you can load from the Config browser in Pharo 3.0 > This one is based on the ODBC known from Squeak (http://wiki.squeak.org/squeak/2480) > > Try it with the second first. You have to open the ODBC settings panel in Windows first, > and then connect to the DB by creating a system wide DSN name > similar to what is explained here for Oracle: > http://www.rpi.edu/datawarehouse/dw-brio-oce-stu-prod.html > > You have to choose the correct MSSQL server driver. Then use this name for the connection in Smalltalk. > If the connection fails try with a database viewer tool first. > > In detail: > 1. Use a new Pharo 3.0 as from the website first. > 2. Install "ODBC" from the config browser (this will install requirements like FFI automatically) > 3. Install "OSWindows" from config browser > 4. Evaluate > WinControlPanel showODBCSettings > to open the ODBC panel > 5. Click on the "System DSN" tab there > 6. Click "Add" > 7. Select the SQL Server driver (usually "SQL Server Native Client blah"), click Next > 8. Enter an unused DSN name like "MYAPP_DB", also enter the IP address (xxx.xxx.xxx.xxx) > of the server and go Next (no need for port as SQLServer usually runs on 1433) > 9. Authentication depends on installation. Usually one uses the SQL Server authentication, either with > a dedicated user connection administrated in SQL Server Tools or by default the user is something > with "sa" (for system administrator) > 10. After login you should be able to select the database and test connection right in the ODBC control panel > 11. Go back to Pharo and run some query: > > | con results | > Transcript open. > con := ODBCConnection dsn:'MY_SYSTEM_DSN_NAME' user: 'db_user' password: 'secretOne'. > results := (con query: 'select * from MyApp.dbo.MyTable') execute. > results do:[:row | Transcript show: row; cr]. > con close. > > Try the query with a database tool first. If the query works from ST you can either use this or try your luck > with DBXTalk and ODBC. Hope this helps. > > Bye > T. > > > Gesendet: Freitag, 19. September 2014 um 21:00 Uhr > Von: "Sebastian Sastre" <sebastian(a)flowingconcept.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] How production ready is Pharo on SQLServer? > On Sep 19, 2014, at 8:05 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > In the end I used ODBC package as it is easy to load from the config browser and one only has > to setup an ODBC name > > After installing all and getting things sorted, it rejects my connection. Triplechecked, network settings, server and client with tcp enabled, everything but canât connect. > > So I guess is time to try ODBC. > > but odbc has no host:port, what should I do about connection settings? > > I how do I make a DBXConnection based in an odbc one? > > thanks! > > sebastian > > o/ > > blog: http://sebastianconcept.com > LinkedIn: http://www.linkedin.com/in/sebastiansastre > github: https://github.com/sebastianconcept >

Sept. 22, 2014

Re: [Pharo-dev] [Review: 13229] Year arithmetic broken

by Henrik Johansen

I am sceptical to the use of Floats. Even using doubles, you've lost nanosecond accuracy when you get up to a number of seconds corresponding to a year: 31536000.000000001 = 31536000.0 true I don't see how the summing done in basicSeconds can possibly add up to correct values... Cheers, Henry On 18 Sep 2014, at 9:56 , Max Leske <maxleske(a)gmail.com> wrote: > Another issue for cleanup review. > > https://pharo.fogbugz.com/f/cases/13229/Year-arithmetic-broken > > > Ported from Pharo 30. > > Made a few additional changes to #hash and #printOn: methods that no longer worked, added class comment to AnnualDuration. > > NOTE: I haven't done a full review on this and the change of seconds from integer to floats can have quite serious implications. Please look at this carefully. > > > > Name: SLICE-Issue-13229-Year-arithmetic-broken-MaxLeske.1 > Author: MaxLeske > Time: 18 September 2014, 9:50:41.500402 pm > UUID: 44e5effc-4344-4aec-8cf5-3cb5d92ad73e > Ancestors: > Dependencies: Kernel-MaxLeske.1827, KernelTests-MaxLeske.678 > > Port from Pharo 30. > > - Added class comment to AnnualDuration. > - adapted #hash and #printOn: methods that no longer worked because of seconds being floats

Sept. 22, 2014

Re: [Pharo-dev] [Issue Tracker] Call for CleanUp of the issue tracker

by Sean P. DeNigris

Marcus Denker-4 wrote > But for me it is important that they are âclosed* I understand. It seems Closed + special status serves both needs. I had proposed "stale" before, but it seemed that existing "postponed" was close enough last time we discussed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-Tracker-Call-for-CleanUp-of-the-issue-tracker-t… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 22, 2014