June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Regression with PNGReaderWriter in P6

by kmo

Just to confirm - I've tried it - works fine in Linux 32 bit VM - but fails with the 64 bit VM -- View this message in context: http://forum.world.st/Regression-with-PNGReaderWriter-in-P6-tp4951796p49518… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 18, 2017

Re: [Pharo-users] Regression with PNGReaderWriter in P6

by Hilaire

Aha, so I understand why you have all icons displayed just fine Some arrays are decoded fine, but most are not. Damn it. Anyway the attached example will be fine for a unit test. Le 18/06/2017 Ã 14:12, Nicolai Hess a Ã©crit : > > Works for me in windows 32. > Maybe it is an 32/64 bit vm issue ? -- Dr. Geo http://drgeo.eu

June 18, 2017

Re: [Pharo-users] Regression with PNGReaderWriter in P6

by Nicolai Hess

2017-06-18 14:01 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > The code bellow decodes the PNG picture just fine in P3, in P6 it can't! > > I suspect changes in PNGReaderWriter>>nextImage > However the version shows no history of edit :( > > One should add this code below in a test for PNG. > > > PNGReadWriter createAFormFrom: #(137 80 78 71 13 10 26 10 0 0 0 13 73 72 > 68 82 0 0 0 48 0 0 0 48 16 6 0 0 0 7 146 37 196 0 0 0 6 98 75 71 68 255 > 255 255 255 255 255 9 88 247 220 0 0 0 9 112 72 89 115 0 0 0 72 0 0 0 72 > 0 70 201 107 62 0 0 1 153 73 68 65 84 120 218 237 155 73 110 195 48 12 > 69 227 162 183 211 9 180 11 130 220 77 39 208 249 210 77 181 8 81 69 19 > 39 169 255 109 12 35 137 197 255 105 81 244 144 219 13 0 0 0 0 0 116 16 > 66 8 33 188 94 214 113 120 99 214 151 111 238 1 115 206 57 231 235 178 > 54 68 10 238 19 112 58 1 189 1 238 158 16 233 25 255 37 117 224 221 141 > 215 210 193 158 128 83 140 215 210 181 156 0 26 216 169 139 180 155 210 > 218 50 184 124 126 74 34 122 245 204 234 101 207 224 41 221 145 150 14 > 49 67 118 77 132 118 220 98 93 208 168 64 107 172 226 18 63 19 91 194 > 172 103 132 117 124 106 194 117 132 210 227 215 143 103 109 124 65 173 4 > 181 4 173 149 128 254 223 121 49 190 160 190 6 212 4 126 22 94 12 163 91 > 173 241 229 112 219 141 188 51 106 184 223 46 139 162 62 3 164 137 49 > 198 24 253 117 89 219 241 183 145 181 82 180 94 154 192 47 212 248 247 > 253 209 45 152 102 205 120 36 130 137 182 193 159 19 5 22 233 53 158 126 > 31 48 209 54 190 181 15 8 189 247 215 71 141 174 25 127 218 243 137 105 > 168 17 53 99 164 140 247 154 8 183 119 67 139 177 41 165 148 210 117 209 > 125 233 241 181 16 187 18 158 21 254 124 62 30 247 251 186 241 173 113 > 122 227 148 70 237 145 100 175 33 210 120 139 207 205 237 232 255 22 71 > 129 45 16 60 3 158 163 123 6 140 214 74 239 198 207 198 201 189 102 12 > 151 32 26 128 155 23 150 22 105 189 96 38 181 88 31 211 206 113 163 165 > 151 109 17 182 110 231 118 213 193 222 5 237 154 8 171 184 217 254 31 > 176 123 9 114 255 146 177 187 128 224 3 0 0 0 0 192 198 252 0 102 116 72 > 96 211 171 62 8 0 0 0 0 73 69 78 68 174 66 96 130) asByteArray > > > > -- > Dr. Geo > http://drgeo.eu > > > Works for me in windows 32. Maybe it is an 32/64 bit vm issue ?

June 18, 2017

Regression with PNGReaderWriter in P6

by Hilaire

The code bellow decodes the PNG picture just fine in P3, in P6 it can't! I suspect changes in PNGReaderWriter>>nextImage However the version shows no history of edit :( One should add this code below in a test for PNG. PNGReadWriter createAFormFrom: #(137 80 78 71 13 10 26 10 0 0 0 13 73 72 68 82 0 0 0 48 0 0 0 48 16 6 0 0 0 7 146 37 196 0 0 0 6 98 75 71 68 255 255 255 255 255 255 9 88 247 220 0 0 0 9 112 72 89 115 0 0 0 72 0 0 0 72 0 70 201 107 62 0 0 1 153 73 68 65 84 120 218 237 155 73 110 195 48 12 69 227 162 183 211 9 180 11 130 220 77 39 208 249 210 77 181 8 81 69 19 39 169 255 109 12 35 137 197 255 105 81 244 144 219 13 0 0 0 0 0 116 16 66 8 33 188 94 214 113 120 99 214 151 111 238 1 115 206 57 231 235 178 54 68 10 238 19 112 58 1 189 1 238 158 16 233 25 255 37 117 224 221 141 215 210 193 158 128 83 140 215 210 181 156 0 26 216 169 139 180 155 210 218 50 184 124 126 74 34 122 245 204 234 101 207 224 41 221 145 150 14 49 67 118 77 132 118 220 98 93 208 168 64 107 172 226 18 63 19 91 194 172 103 132 117 124 106 194 117 132 210 227 215 143 103 109 124 65 173 4 181 4 173 149 128 254 223 121 49 190 160 190 6 212 4 126 22 94 12 163 91 173 241 229 112 219 141 188 51 106 184 223 46 139 162 62 3 164 137 49 198 24 253 117 89 219 241 183 145 181 82 180 94 154 192 47 212 248 247 253 209 45 152 102 205 120 36 130 137 182 193 159 19 5 22 233 53 158 126 31 48 209 54 190 181 15 8 189 247 215 71 141 174 25 127 218 243 137 105 168 17 53 99 164 140 247 154 8 183 119 67 139 177 41 165 148 210 117 209 125 233 241 181 16 187 18 158 21 254 124 62 30 247 251 186 241 173 113 122 227 148 70 237 145 100 175 33 210 120 139 207 205 237 232 255 22 71 129 45 16 60 3 158 163 123 6 140 214 74 239 198 207 198 201 189 102 12 151 32 26 128 155 23 150 22 105 189 96 38 181 88 31 211 206 113 163 165 151 109 17 182 110 231 118 213 193 222 5 237 154 8 171 184 217 254 31 176 123 9 114 255 146 177 187 128 224 3 0 0 0 0 192 198 252 0 102 116 72 96 211 171 62 8 0 0 0 0 73 69 78 68 174 66 96 130) asByteArray -- Dr. Geo http://drgeo.eu

June 18, 2017

Re: [Pharo-users] Pharo6 server deployment and no home directory

by Juraj Kubelka

> El 16-06-2017, a las 10:34, Holger Freyther <holger(a)freyther.de> escribiÃ³: > > >> On 12. Jun 2017, at 16:41, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> >> Hi Holger, >> >> I have an impression that it can be solved by using "--no-default-preferencesâ option: >> ./pharo Pharo.image --no-default-preferences >> >> Is it a good solution for you? Or do you need to load some preferences? > > Right, unsetting HOME and then using --no-default-preferences makes the error go away. > > > >> Another option could be implementing an error signal, e.g., CantFindOriginError in the cantFindOriginError method and catch this in the GlobalIdentifier object. > > I wonder if "FileLocator home exists" should really throw an exception in case {home} can not be resolved. > > a.) Just because it can not be resolved, it might still exist? > b.) If it can not be resolved it doesn't exist from an image point of view? I think it is better to throw an exception. Then someone is sure that does not use a code, that needs {home} directory, but cannot. Maybe there could be a specialized error class for this. Now it uses Error, if I remember well. Juraj > > holger

June 18, 2017

UK Smalltalk User Group meeting - Monday, 26th June

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group Meeting will be on Monday, 26th June. We'll meet at our usual venue The Counting House ( http://www.the-counting-house.com/) at 7pm. If you'd like to join us, you can just show up at the pub. You can also sign up in advance at the meeting's Meetup page: *https://www.meetup.com/UKSTUG/events/240660858/ <https://www.meetup.com/UKSTUG/events/240660858/>* . See you there!

June 18, 2017

Re: [Pharo-users] UUIDGenerator

by phil＠highoctane.be

Spotting for hex is hardly complex. Shift-Enter hex #im --> implementors of hex, first one I see is in ByteArray. Shit-Enter hex #se --> senders of hex. First one is a test in ByteArray testHex "self debug: #testHex" self assert: #[122 43 213 7] hex = '7a2bd507'. self assert: #[151 193 242 221 249 32 153 72 179 41 49 154 48 193 99 134] hex = '97c1f2ddf9209948b329319a30c16386'. self assert: (ByteArray readHexFrom: '7A2BD507') = #[122 43 213 7]. self assert: (ByteArray readHexFrom: '7a2bd507') = #[122 43 213 7]. >From this test, one can spot readHexFrom: which uses lowercase or uppercase for reading. And asUppercase, Shift-Enter upper, scrolll down as bit, find String>>#asUppercase Spotter is really great at finding stuff, and coupled with tests and examples it helps in building understanding. Agreed, this is not the same as looking for stuff as in, say, Java or Python. I find it better in the long run still. Phil On Sat, Jun 17, 2017 at 9:23 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > Message 'next' is not understood. > > But yes, > > UUID new hex asUppercase > > works fine. > > This is what happens when there is inadequate documentation: you end up > doing things the *hard* way. > > Thanks. > > > > Sven Van Caekenberghe-2 wrote > > Why not just > > > > UUIDGenerator default next hex asUppercase. > > > > Or even > > > > UUID new hex asUppercase. > > > > ? > > > > Since you are using #generateBytes:forVersion: (which is an internal > > method BTW), you must be working in an older Pharo image (older than 6). > > We replaced the UUIDGenerator class, the class comment in from the newer > > version. > > > >> On 17 Jun 2017, at 16:27, horrido < > > > horrido.hobbies@ > > > > wrote: > >> > >> Okay, I figured it out. Here's my method: > >> > >> generateUUID > >> | aStream hex s x | > >> hex := '0123456789ABCDEF'. > >> x := ByteArray new: 16. > >> UUIDGenerator default generateBytes: x forVersion: 4. > >> s := String new: 32. > >> aStream := WriteStream on: s. > >> x do: [ :each | aStream nextPut: (hex at: each // 16 + 1). > >> aStream nextPut: (hex at: each \\ 16 + 1) ]. > >> ^ s > >> > >> Works like a charm. It would've been nice if a similar example was > >> available > >> /somewhere/ on the web. > >> > >> > >> > >> -- > >> View this message in context: > >> http://forum.world.st/UUIDGenerator-tp4951725p4951731.html > >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >> > > > > > > -- > View this message in context: http://forum.world.st/UUIDGenerator- > tp4951725p4951743.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

June 18, 2017

Re: [Pharo-users] WrapAthen, World coordinate?

by Hilaire

It behaves as the canvas wrapped in the Athens wrapper got its origin locked to top left position Le 17/06/2017 Ã 23:24, Hilaire a Ã©crit : > Any information to know to understand why a DrGeo canvas wrapped in P6 > AthenWrappedMorph got its coordinates shifted, clipped, background in > gray and not white? -- Dr. Geo http://drgeo.eu

June 18, 2017

Re: [Pharo-users] Finding files in Pharo

by HernÃ¡n Morales Durand

Thanks Sven, Just checking some brave soul out there with a cool "unpublished" package... Cheers, HernÃ¡n 2017-06-18 3:58 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > HernÃ¡n, > > We obviously don't have as many options as find, but this should get you > started: > > Check the category 'enumerating' in AbstractFileReference, with methods > like #childrenMatching: and #allChildrenMatching: > > Once you have a reference, you can use other meta data, see the > 'accessing' protocol to further your query. > > HTH, > > Sven > > > On 18 Jun 2017, at 04:59, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > > I would like to find files in Pharo like the UNIX find command: > > > > find . -iname "*.txt" -type f -print > > > > find . \( -iname "*.txt" -o -iname "*.csv" \) -print > > > > find . -maxdepth 2 -name "example*" -type f -print > > > > find . -type f -atime -7 -size +2M -perm 644 -print > > > > Do we have some package on top of FileSystem to make complex find > searches? > > > > HernÃ¡n > > > > >

June 18, 2017

Re: [Pharo-users] Finding files in Pharo

by HernÃ¡n Morales Durand

I know file system commands could be executed using the OS wrappers. But Smalltalk is more elegant than shell command line, and we have Windows still the most used OS. 2017-06-18 3:59 GMT-03:00 john pfersich <jpfersich(a)gmail.com>: > Why not just use OsProcess or OsSubprocess to run the unix commands (works > on Mac OS and Linux)? > > Sent from my iPhone > > > On Jun 17, 2017, at 19:59, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > > I would like to find files in Pharo like the UNIX find command: > > > > find . -iname "*.txt" -type f -print > > > > find . \( -iname "*.txt" -o -iname "*.csv" \) -print > > > > find . -maxdepth 2 -name "example*" -type f -print > > > > find . -type f -atime -7 -size +2M -perm 644 -print > > > > Do we have some package on top of FileSystem to make complex find > searches? > > > > HernÃ¡n > > > >

June 18, 2017