- Pharo-users - lists.pharo.org

Re: [Pharo-users] spec column/ row layout

by Hilaire

Le 14/02/2015 10:21, Hilaire a Ã©crit : > Le 14/02/2015 00:52, Sebastian Heidbrink a Ã©crit : >> What is wrong with this spec? >> Why is the checkbox attached to the buttom? I would have expected it >> to be directly underneath the password label. >> Is this default behavior and how can I prevent this? >> > I don't know spec at all, but it looks like a shrink attributes should > be used. May be there is on the spec api. > > Hilaire > Another remark, why is height: self inputTextHeight; needed? Should not spec have a default automatic way to set it, deducing from the row contents? Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Feb. 14, 2015

Re: [Pharo-users] spec column/ row layout

by Hilaire

Le 14/02/2015 00:52, Sebastian Heidbrink a Ã©crit : > What is wrong with this spec? > Why is the checkbox attached to the buttom? I would have expected it > to be directly underneath the password label. > Is this default behavior and how can I prevent this? > I don't know spec at all, but it looks like a shrink attributes should be used. May be there is on the spec api. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Feb. 14, 2015

Re: [Pharo-users] spec column/ row layout

by Peter UhnÃ¡k

Hi Sebastian, the problem is that the layout tries to always take all the available space. What I usually do is add an empty row at the bottom newRow: [ :row | ] to take all the excessive space. Peter On Sat, Feb 14, 2015 at 12:52 AM, Sebastian Heidbrink <sheidev(a)yahoo.de> wrote: > What is wrong with this spec? > Why is the checkbox attached to the buttom? I would have expected it to be > directly underneath the password label. > Is this default behavior and how can I prevent this? > > > defaultSpec > <spec: #default> > ^SpecLayout composed > newColumn: [ :col | > col > newRow: [ :row | > row > add: #usernameLabel ; > add: #usernameField ] > height: self inputTextHeight; > newRow: [ :row | > row > add: #passwordLabel; > add: #passwordField ] > height: self inputTextHeight; > newRow: [ :row | > row > add: #showPasswordCheckBox] > height: self inputTextHeight ]; > yourself > > Thank you > Sebastian > >

Feb. 14, 2015

Re: [Pharo-users] [ANN] PUnQLite NoSQL database project updated

by Stephan Eggermont

If I use the file from https://github.com/mumez/PunQLite/tree/master/binary/mac at least the library is found. The db file is not created though resulting in a PqCursorError in keys db := PqDatabase open: 'test.db'. db at: 'Smalltalk' put: 'COOL'. db at: 'Pharo' put: 'HOT'. db at: 'Smalltalk' ifPresent: [:data | data asString inspect ]. Transcript cr; show: db keys.

Feb. 14, 2015

Re: [Pharo-users] [ANN] PUnQLite NoSQL database project updated

by Stephan Eggermont

Fails on Mavericks 10.9.4 in 40486 with 402 vm, 20619 with vm from 18-9-2013 open: dbHandle named: dbName mode: mode <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ self nbCall: #( int unqlite_open( db_ptr* dbHandle, String dbName, uint mode) ) module: self libraryFileNameForPlatform I did not compile myself, just used the lib-unqlite.dylib that is downloaded by the configuration. Stephan

Feb. 14, 2015

Re: [Pharo-users] Spotter vs Spotlight was: [Re: Cleaning code completition's namespace]

by Laura Risani

Hi, There was a mistake in the algorithm as the matching was case sensitive >>> which is not useful in our case. So, try this: >>> >> spotterSelectorsFor: aStep > (...) > Works perfect. So additions i would like to see built by default >> Cmd+w to close on GTSpotter and GTPlayground. >> > > This works. Could you explain what you do (including the versions and OS > you use)? > You're right, Cmd+w works fine, i forgot i had changed Cmd key. > Remove/know-how-to remove the 5 limit on results. > > Every processor is defined in a class extensions annotated with > <spotterPreview:>. The processor can specify the limit. Right now, the > implementations specify 5 items. You can play with variations. > > Thank you for the tip. Font size configured at SystemBrowser to have effect on GTSpotter both on >> search results and preview. >> > > Good point. Could you open a Pharo issue for this one? > Done, number 14933 . Love, Laura

Feb. 14, 2015

Re: [Pharo-users] [ANN] PUnQLite NoSQL database project updated

by Pierce Ng

On Fri, Feb 13, 2015 at 06:07:07PM +0100, Stephan Eggermont wrote: > What should be done to make this work on OS X? > UnQLiteFFI>>libraryFileNameForPlatform > has a wrong name, but that doesn't help me. > Even after renaming the library cannot be found. Smalltalk side, version 12/23/2013 by Masashi Umezawa: libraryFileNameForPlatform | platformClass | platformClass := NativeBoost forCurrentPlatform class. platformClass = NativeBoostMac32 ifTrue: [^'unqlite.dylib']. platformClass = NativeBoostWin32 ifTrue: [^'unqlite.dll']. platformClass = NativeBoostLinux32 ifTrue: [^'unqlite.so']. ^'unqlite' OSX side, place the file unqlite.dylib in Pharo.app/Contents/MacOS/Plugins. This worked for me in a Pharo 2.0 image and Jan 2014 VM. Pierce

Feb. 14, 2015

spec column/ row layout

by Sebastian Heidbrink

Â What is wrong with this spec? Why is the checkbox attached to the buttom? I would have expected it to be directly underneath the password label. Is this default behavior and how can I prevent this? defaultSpec Â Â Â <spec: #default> Â Â Â ^SpecLayout composed Â Â Â Â Â newColumn: [ :col | Â Â Â Â Â Â Â col Â Â Â Â Â Â Â Â Â newRow: [ :row | Â Â Â Â Â Â Â Â Â Â Â row Â Â Â Â Â Â Â Â Â Â Â Â Â add: #usernameLabel ; Â Â Â Â Â Â Â Â Â Â Â Â Â add: #usernameField ] Â Â Â Â Â Â Â Â Â height: self inputTextHeight; Â Â Â Â Â Â Â Â Â newRow: [ :row | Â Â Â Â Â Â Â Â Â Â Â row Â Â Â Â Â Â Â Â Â Â Â Â Â add: #passwordLabel; Â Â Â Â Â Â Â Â Â Â Â Â Â add: #passwordField ] Â Â Â Â Â Â Â Â Â height: self inputTextHeight; Â Â Â Â Â Â Â Â Â Â Â newRow: [ :row | Â Â Â Â Â Â Â Â Â Â Â row Â Â Â Â Â Â Â Â Â Â Â Â Â add: #showPasswordCheckBox] Â Â Â Â Â Â Â Â Â height: self inputTextHeightÂ ]; Â Â Â Â Â Â yourself Thank you Sebastian

Feb. 13, 2015

Re: [Pharo-users] Tagging packages

by Laura Risani

Ok, forget it, i've just noticed "Groups"... On Fri, Feb 13, 2015 at 8:04 PM, Laura Risani <laura.risani(a)gmail.com> wrote: > Hi all, > > What method do you use to organize/tag your packages so you can then > easily retrieve those sharing a same tag? Is there any functionality > intended for it? > > I've been trying the following ones (ordered by increasing satisfaction): > prefixing, flagging, sharing repository, pragma. But i feel like none of > these achieves a proper balance (for package tagging) between ease of > retrieving, persistence and conceptual coherence/cleanness (at least in the > way i've been using them, perhaps i ignore something). > > Love, > Laura > > > > >

Feb. 13, 2015

Re: [Pharo-users] Writing a Login Dialog using Spec in 3 methods

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Spec is not perfect, its main 'issue' is that the UI elements are called > models I appreciate the ability to easily create standard vanilla business UIs... which we did not have in the not-too-distant-past. And I'm not too worried because everything's a work in progress. But I would say that my main issues with it are discoverability and understandability. It seems that we're getting further and further from the Morphic dream of dragging something visual that "almost does what you want" and dropping it into your cool new UI, or at least digging down through halos to see how things work. And when I step through layers of symbol interpretation I feel sad. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Writing-a-Login-Dialog-using-Spec-in-3-methods-tp4805… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 13, 2015