August 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: About SPDF
by StÃ©phane Ducasse Aug. 24, 2010

Aug. 24, 2010

Begin forwarded message: > From: Bruce Badger <bruce_badger(a)badgerse.com> > Date: August 24, 2010 11:10:04 PM GMT+02:00 > To: GermÃ¡n Arduino <gsa(a)arsol.net> > Cc: StÃ©phane Ducasse <stephane.ducasse(a)free.fr> > Subject: Re: About SPDF > > Hi, > > The license in full, taken from the SPDF-Core package comment, is > below. The license is pretty close to a BSD style license, but is a > one-off concocted by the SPL WorldGroup lawyers (sorry Stephane). As > the person who actually wrote the library I can tell you I would be > perfectly happy for you to use the library, but I don't hold the > copyright. The company SPL WorldGroup held the copyright when the > library was written but they have been bought by Oracle now so I guess > that means Oracle own the copyright. > > The intent of the license is to enable anyone to use the code as long > as they don't bother SPL WorldGroup (now Oracle) about it. I know, > because I was there when the license was put together, that the > license was written to allow people to do just the kind of thing you > would like to do ... but IANAL. > > Here is the text from the package comment which includes some notes > and the license text: > > ~~~~ > > Look at the class side methods in PDFSelfTest for an idea of what the > classes in this package can do for you. > > The code in this library is based upon the PDF Reference Manual V1.2. > > This library is made available under the following license: > > Preamble > > In the spirit of encouraging the continuing development of software > for open computing environments and in the spirit of improving the > quality of software generally, our goal is to provide this software to > you free of charge and with the fewest possible restrictions. To > achieve this, we asked our attorneys to draft an agreement which would > permit you to do just about anything you lawfully wish with this > software, while also preserving SPL's right to continue developing > this and related software (something which we didn't feel the GNU GPL > would allow us to do), and protecting SPL from excessive liability > risks. We therefore offer this software, free of charge, according to > the terms of the license below. > > The legal bit > > SPL WorldGroup, Inc. ("SPL") is willing to license the SPL Software > and any Associated Materials (consisting of accompanying > specifications, test suites and user documentation) to you only on the > condition that you accept all of the terms and conditions in this > Agreement. The SPL Software and Associated Materials are referred to > collectively as the "SPL Technology." > > Please read the terms carefully before clicking on the "Accept" > button, as by clicking on the "Accept" button you acknowledge that you > have read this Agreement, understand it and agree to be bound by its > terms and conditions. > > If you do not agree to these terms and conditions, SPL is unwilling to > license the SPL Technology to you. You should click on the "Cancel > Download" button to discontinue the installation process. > > 1. Licenses. > > 1.1 License. Subject to the terms and conditions contained herein, SPL > grants you during the term of this Agreement a nonexclusive and > fee-free right to download, install, copy, demonstrate, modify, create > derivative works from, distribute, and use, in binary and or source > code form, the SPL Technology, provided that you reproduce all > copyright and other proprietary notices that are on the original copy > of the SPL Technology. > > 1.2 Cross-License. Subject to the terms and conditions contained > herein, you grant to SPL a nonexclusive and fee-free right to > download, install, copy, demonstrate, modify, create derivative works > from, distribute, and use, in binary and or source code form, any > improvements, modifications or derivative works of the SPL Technology > made by you and provided to SPL. > > 2. Restrictions. The SPL Technology is not designed or licensed for > use in on-line control equipment in hazardous environments, such as > operation of nuclear facilities, aircraft navigation or control, or > direct life support machines. > > 3. Ownership. The SPL Technology is licensed, not sold, to you for use > only under the terms of this Agreement, and SPL reserves all rights, > including patent rights, not expressly granted to you. You own the > media, if any, on which the SPL Technology is recorded, but SPL > retains ownership of all copies of the SPL Technology itself. > > 4. Support And Updates. SPL is under no obligation to support the SPL > Technology in any way or to provide updates or error corrections. > > 5. Disclaimer of Warranty. The SPL Technology is provided to you free > of charge and "As Is," there is no warranty. To the maximum extent > permitted by law, SPL expressly disclaims all warranties, including > the implied warranties of merchantability, fitness for a particular > purpose, and non-infringement. No oral or written information or > advice given by SPL, its employees, distributors, dealers, licensors > or agents shall increase the scope of the above warranties or create > any new warranties. > > 6. Limitations of Remedies. > > 6.1 You acknowledge that: (a) the SPL Technology is experimental and > provided to you only for the purposes set forth in this Agreement; (b) > the SPL Technology may have errors, bugs, design flaws, defects or > other deficiencies which cannot or will not be corrected by SPL; (c) > use of the SPL Technology may result in unexpected results, loss of > data or other unpredictable damage or loss to you; and (d) SPL is > under no obligation to release the SPL Technology as a product of SPL. > You will hold SPL harmless from any claims based on the use of the SPL > Technology, from any claims that any product released by SPL is > incompatible with the SPL Technology and from SPL's decision not to > release the SPL Technology as a product. You will have the sole > responsibility for adequate protection and backup of your data and/or > equipment used with the SPL Technology. > > 6.2 Regardless of whether any remedy set forth herein fails of its > essential purpose or otherwise, in no event will spl or its licensors > be liable to you or to any third party for any lost profits, lost > data, interruption of business, or other special, indirect, incidental > or consequential damages of any kind, whether in contract, tort > (including negligence) or otherwise, arising out of the use or > inability to use the spl technology or any data supplied therewith, > even if spl or its licensors have been advised of the possibility of > such loss or damage and whether or not such loss or damages are > foreseeable. > > 7. Term. This Agreement is effective until terminated. You may > terminate this Agreement at any time by destroying all copies of SPL > Technology. This Agreement will immediately and automatically > terminate without notice if you fail to comply with any material term > or condition of this Agreement. You agree upon termination to promptly > destroy the SPL Technology and all copies thereof. > > 8. Export Law. The SPL Technology is subject to U.S. export control > laws and may be subject to export or import regulations in other > countries. You agree to strictly comply with all such laws and > regulations and acknowledge that you have the responsibility to obtain > such licenses to export, re-export or import as may be required. By > downloading the SPL Technology, you agree to strictly comply with all > of the United States and other applicable country laws and regulations > when either exporting or re-exporting or importing the SPL Technology > or any underlying information or technology. Further, you acknowledge > that you are not a national of Cuba, Iran, Iraq, Libya, North Korea, > Sudan or Syria or a party that is listed in the U.S. Table of Denial > Orders or U.S. Treasury Department's list of Specially Designated > Nationals. This SPL Technology is exported from the United States in > accordance with U.S. Export Administration Regulations. Diversion > contrary to U.S. law is strictly prohibited. The SPL Technology is > restricted from being used for the design or development of nuclear, > chemical, biological, weapons or missile technology without the prior > permission of the U.S. Government. > > 9. General. Any action related to this Agreement will be governed by > California law and controlling U.S. Federal law, and the United > Nations Convention on Contracts for the International Sale of Goods > and the choice of law rules of any jurisdiction shall not apply. If > any provision of this Agreement is held to be unenforceable, that > provision will be removed and the remaining provisions will remain in > full force. This Agreement is the complete and exclusive statement of > the agreement between us which supersedes any proposal or prior > agreement, oral or written, and any other communications between us in > relation to the subject matter of this Agreement. If you have any > questions concerning this Agreement, you may contact by writing to > SPL, Inc. at 75 Hawthorne Plaza, Suite 2010, San Francisco, CA, 94105. > The SPL Technology is protected by United States Copyright Law and > International Treaty. Unauthorized reproduction or distribution is > subject to civil and criminal penalties. > > By downloading the SPL Technology, I acknowledge that I have read and > fully understand the foregoing information and agree to abide by its > terms and conditions. > > > > > On 24 August 2010 15:56, GermÃ¡n Arduino <gsa(a)arsol.net> wrote: >> Hi Bruce: >> >> We are (on the Pharo community) talking about your SPDF code to >> generate PDF's from inside Squeak. >> >> We wish to have this package adapted to the newest versions of Pharo, >> but the source code seem to by copyrighted, and we can't found the >> urls >> talking about, as http://wiki.cs.uiuc.edu/VisualWorks/PDF+Library or >> www.splwg.com. >> >> Can you confirm us if we can take such source code and create a >> squeaksource MIT licensed project to adapt it to Pharo? Â¿Is possible >> to change >> the license to MIT?. >> >> We wait your comments. >> >> Thanks you. >> >> -- >> ================================================= >> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino >> Arduino Software & Web Hosting http://www.arduinosoftware.com >> PasswordsPro http://www.passwordspro.com >> ================================================= >> > > > > -- > Make the most of your skills - with OpenSkills > http://www.openskills.org/ >

2 1

[Pharo-project] [update 1.2] #12110
by StÃ©phane Ducasse Aug. 24, 2010

Aug. 24, 2010

12110 ----- - Network-Protocol fixes. Thanks SvenVanCaekenberghe Switched to proper use of #pathForFile. - WebClient-Core, WebClientTests Thanks Andreas Raab and SvenVanCaekenberghe/Philippe Marshall Sorry that it took so long to integrate WebClient, but we did not want that people think we were jumping on other works. I hope that our engineer will be able to contribute back to the package. Now I heard that several fixes coming from nice seasiders in pharo were not integrated. May be people are too busy, so we will see in the future. Now we should probably have a deeper look and integrate the new commits and also make sure the tests are green. Stef

1 0

Re: [Pharo-project] Poll: missing libraries to support busines
by Stephan Eggermont Aug. 24, 2010

Aug. 24, 2010

I would like to have native, or at least better, libraries for manipulating PDFs and office files. Stephan

6 13

[Pharo-project] [Fixed]: Issue 2856: Use unique URL to core from [Dev image]->World Menu->System>Software update
by Sean P. DeNigris Aug. 24, 2010

Aug. 24, 2010

http://code.google.com/p/pharo/issues/detail?id=2856 In a 1.2 dev image, when a user chooses System>Software update, they see a dialog explaining how to get an updatable (i.e. core trunk) image (issue ). This link should be the unique URL that was just set up - http://www.pharo-project.org/pharo-download/unstable-core. Fix in PharoInbox: SLICE-Issue-2856-DevSoftwareUpdateShowsUnqiueCoreURL-SeanDeNigris.1 Sean -- View this message in context: http://forum.world.st/Fixed-Issue-2856-Use-unique-URL-to-core-from-Dev-imag… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] [update 1.2] #12106
by StÃ©phane Ducasse Aug. 24, 2010

Aug. 24, 2010

12106 ----- - Issue 2843: ColoredCodeStream not used. Thanks Marcus Denker. - Issue 2769: Fixes for broken SocketStream behavior. Thanks Andreas Raab Fix the loop in network tests. Stef

3 7

[Pharo-project] Float>>basicAt: primitive for Cog
by Guillermo Polito Aug. 24, 2010

Aug. 24, 2010

Hi! taking a look at issue 2579 http://code.google.com/p/pharo/issues/detail?id=2579 I saw it's all done but: "The float access methods are an alternative to what is described in 2580 / 2581 , didn't see this when I posted. They are slightly slower in a CogVM when primitive fails, since you will have 2 primitive failures before handling, but do not need the Parser change which allows primitive pragmas with non-literal error parameter. Either way, if this approach is chosen, we might as well write: (same for basicAt:put:) Float >> basicAt: index <primitive: 38> ^super basicAt: index as ec is always nil in this case." That should replace Float >> basicAt: index "...." <primitive: 38> | ec | ec == nil ifTrue: "primitive not implemented; floats are in big-endian/PowerPC order." [^super basicAt: index]. index isInteger ifTrue: [self errorSubscriptBounds: index]. index isNumber ifTrue: [^self basicAt: index asInteger] ifFalse: [self errorNonIntegerIndex] -------------------------------------------------------------------------- I ran all the FloatTests and I got: -Cog VM: all green before and after the change. -non-Cog VM: 1 failure (on testNaNCompare) before and after the change I can't see tests for the primitive failure, maybe we should have... Anyway, I wonder if this change is ok for the non-cog vm also. Does anyone know? Cheers, Guile

2 1

[Pharo-project] Fwd: [Pharo-users] 3600 seconds seconds = 0 ???
by StÃ©phane Ducasse Aug. 24, 2010

Aug. 24, 2010

3600 seconds seconds = 0 which means that this is a number of seconds in the hour:min:seconds decomposition Now it looks to me that the method comment is wrong seconds "Answer the number of seconds the receiver represents." ^ (seconds rem: SecondsInMinute) 3600 seconds asSeconds = 3600 is what is working may be (Duration seconds: 3600) would be better To me there is something conceptually bogus with such definition of minutes and seconds. (Duration seconds: 3600) minutes = 0 (Duration seconds: 3600) seconds = 0 Stef _______________________________________________ Pharo-users mailing list Pharo-users(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

3 6

[Pharo-project] some important fixes we should focus on for 1.2
by stephane ducasse Aug. 24, 2010

Aug. 24, 2010

Hi guys here is a list of issue I would like to work and get some help. Stef http://code.google.com/p/pharo/issues/detail?id=2570 Issue 2570: Removed implicit conversion of DateAndTime equality-testing argument. http://code.google.com/p/pharo/issues/detail?id=2579 http://code.google.com/p/pharo/issues/detail?id=2698 Issue 2698: Smalltalk registration to SystemChangeNotifier should be handle in startup http://code.google.com/p/pharo/issues/detail?id=2177 Issue 2177: Generalize stream protocol #readInto:startingAt:count: Issue 1981: Raising DuplicateError Exception in class builder http://code.google.com/p/pharo/issues/detail?id=1981 http://code.google.com/p/pharo/issues/detail?id=2146 Issue 2146: Fix SystemChangeNotification for traits. http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: MethodDictionary improvement http://code.google.com/p/pharo/issues/detail?id=2315 Method Dictionary Compact protocol to investigate http://code.google.com/p/pharo/issues/list?cursor=2313 Issue 2313: HashedCollectionIntegrityTest http://code.google.com/p/pharo/issues/detail?id=2583 Issue 2583: COG - MessageTally Issue 2619: ignore vm parameters with nil value in MessageTally, so it can be used in Cog http://code.google.com/p/pharo/issues/detail?id=2584 COG- COG- LargeNegativeInteger to be compact at 5 http://code.google.com/p/pharo/issues/detail?id=2567 Issue 2567: evaluate the finalizers outside the protected block in WeakRegistry http://code.google.com/p/pharo/issues/detail?id=2564 Issue 2564: WeakKeyDictionary finalizeValue tests http://code.google.com/p/pharo/issues/detail?id=2769 Issue 2769: Fixes for broken SocketStream behavior. http://code.google.com/p/pharo/issues/list?cursor=2551 weakstructure http://code.google.com/p/pharo/issues/detail?can=2&q=2244 Issue 2244: Socket support for #next:putAll:startingAt: and #readInto:startingAt:count: http://code.google.com/p/pharo/issues/detail?id=2825 Issue 2825: [[true] whileTrue] fork cannot be interrupted

4 5

[Pharo-project] [Survey] Assess the cycles in your software
by Laval Jannik Aug. 24, 2010

Aug. 24, 2010

Hi Pharoers, and Smalltalkers in general, Have you seen waited to assess the cycles in your software? Now you can :) We request some of you to perform an experiment using DSM to see your software package structure and to fix cycles between packages. Our tool shows dependencies between packages and highlight some bad dependencies generating structure cycles. It also helps to understand dependencies. Your goal is to fill a survey using our tool. I prepared a mini-tutorial about DSM and eDSM. It can help you to understand the visualization tool. To ease the use of our tool, I loaded it in a PharoCore1.2. And there are two archives available: - the first contains an image with our tool with a model of Pharo loaded in it, so you can play with our tool on pharo itself. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithPharo.zip. Pay attention, the image is slow. - the second contains the same thing without the model of Pharo. Here, you have to load your code, then populate a moose model and use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip The two archives contain the tutorial and the survey. If you are a pharo integrator, we suggest you to take the one with Pharo model loaded, else the other. To use our tool, load your tool in Pharo. Then do "MoosePanel open", and import your software in Moose by "import from Smalltalk image". When it is imported, select your project in the list on the left of MoosePanel, and select "all model packages" on the list on center. Then, you have two choices: - you can scan all your project: right click on "all model packages" and do DSM. - or select "all model packages" then select some packages in the next list and right click, do DSM. After that, you can perform the survey (with reading of the tutorial). We need your answers for the end of August. So, you have two months to do it. If you have any question, just let me know. Best regards, Jannik. --- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---

3 5

[Pharo-project] Working on Pharo 1.2
by James Foster Aug. 24, 2010

Aug. 24, 2010

All, I'm having trouble finding 1.2. http://pharo-project.org/home contains the following: 'If you want to use all the new features and improvements that have been added to Pharo lately, and you don't mind living on the bleeding edge, download the current Pharo 1.2.' Clicking on the 'download' link takes me to http://pharo-project.org/pharo-download, but I can't find any place to download 1.2. I've tried enabling the update menu in a 1.1 image, but there seem to be no updates. I've briefly searched the archives for a thread on 'How to contribute to 1.2' but haven't found anything. I've been to http://www.squeaksource.com/PharoInbox.html, but don't see any instructions beyond 'just publish it here.' I've been to http://hudson.lukas-renggli.ch/job/Pharo/, and see that there is a build of 1.1 on July 17, and another build on July 20, but that seems to be not exactly current, and does not describe itself as 1.2. Where do I go to get the current (unstable) 1.2 build? What do I need to do to contribute (beyond adding to the PharoInbox)? Send mail? James

10 30