- Pharo-users - lists.pharo.org

Re: [Pharo-users] Help for #fullscreen window

by Jigyasa Grover

Thank You Sir :) It does almost what I desire . Regards Jigyasa -- View this message in context: http://forum.world.st/Help-for-fullscreen-window-tp4841116p4841156.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 5, 2015

Re: [Pharo-users] Help for #fullscreen window

by Thierry Goubier

Hi jigyasa, You have an openFullScreen method somewhere, which really opens full screen (and makes it hard to close;) ). Thierry Le 5 aoÃ»t 2015 5:30 PM, "Jigyasa Grover" <grover.jigyasa1(a)gmail.com> a Ã©crit : > Hi ! > I am using *WidgetExamples exampleBuilder* to make an accordion widget. I > open a model *newPluggableWindow* in it, and would like it to be a > fullscreen entity. > I have tried all the methods, *#fullscreen *and *#extent* but in vain. It > would be great if anyone could help. > > The code snippet is as : > > *printSearchResults* > > *self open. * > *SearchQuick searchQuick: self myString. * > *builder := WidgetExamples exampleBuilder.* > *dialog := (builder newPluggableDialogWindow: 'SEARCH RESULTS FOR " ', > myString , ' " ').* > *searchResultsAccordion := dialog contentMorph:* > *(* > * dialog newColumn: { * > * dialog newColumn: * > * (* > * SearchQuick myResult collect: [ :r |* > * dialog newRow: {* > * (* > * (* > * dialog newExpander: r title asString* > * forAll: { * > * ( dialog newTextEditorFor: ( ValueHolder new contents: r content > asString )* > * getText: #contents setText: #contents: )minHeight: 150.* > * }* > * )minWidth:750; minHeight: 10* > * )* > * cellInset: 0;* > * borderStyle: (BorderStyle inset baseColor: dialog paneColor; width: 1)* > * } * > * ]* > * ) .* > * backBtn := dialog newButtonFor: self action: #backButtonClicked label: > 'Back' help: 'Back'.* > * backBtn extent: 750(a)30.* > * }* > * ); minWidth: World extent x; minHeight: World extent y;* > > * model: nil.* > * searchResultsAccordion position: 0(a)0.* > * searchResultsAccordion extent: World extent.* > * searchResultsAccordion width: World extent x.* > * searchResultsAccordion height: World extent y.* > * builder newScrollPaneFor: searchResultsAccordion.* > * dialog position: 0(a)0.* > * dialog extent: World extent.* > * builder openModal: dialog.* > * dialog newScrollPaneFor: searchResultsAccordion .* > > > Regards > Jigyasa >

Aug. 5, 2015

Re: [Pharo-users] Git Topic Branches and CI

by Thierry Goubier

Le 5 aoÃ»t 2015 7:55 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> a Ã©crit : > > When using a branch-per-issue, it's not so easy to define #development a la > Metacello. How are you handling this? Are you somehow dynamically doing a > CI-build-per-branch? If you use Travis as CI as in filetree on github, you get one CI build per branch. I don't know how to do the same with Jenkins. Thierry > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Git-Topic-Branches-and-CI-tp4841141.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 5, 2015

Re: [Pharo-users] Modern Events Touch and Gestures in Pharo.

by Alexandre Bergel

Impressive!!! Dreaming about that to use in Roassal Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 5, 2015, at 2:20 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > this awesome , great work :) > > On Tue, Jun 30, 2015 at 8:18 PM stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Thanks Thales for the sponsoring. > > https://youtu.be/eNrbH8A5nyY <https://youtu.be/eNrbH8A5nyY> > > Stef and the rmod team >

Aug. 5, 2015

Git Topic Branches and CI

by Sean P. DeNigris

When using a branch-per-issue, it's not so easy to define #development a la Metacello. How are you handling this? Are you somehow dynamically doing a CI-build-per-branch? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Git-Topic-Branches-and-CI-tp4841141.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 5, 2015

Re: [Pharo-users] Help for #fullscreen window

by Hilaire

Le 05/08/2015 23:30, Jigyasa Grover a Ã©crit : > Hi ! > I am using *WidgetExamples exampleBuilder* to make an accordion > widget. I open a model *newPluggableWindow* in it, and would like it > to be a fullscreen entity. > I have tried all the methods, *#fullscreen *and *#extent* but in vain. > It would be great if anyone could help. Hello, I only reply to pharo.user group, no need to cross post to pharo.dev. May be dialog are constrained to not be fullscreen, not sure. What you could try, is debug your code when requesting fullscreen on your dialog: In a workspace, (or from an inspector on your dialog): myDialog fullscreen (or self fullscren from an inspector), then select and debut with Alt+shift+d (on linux) But I just tested these in a workspace: "Does not open fullscreen" d := ExampleBuilderMorph new newPluggableDialogWindow. d fullscreen. d openInWorld. "Works, set to fullscreen" d := ExampleBuilderMorph new newPluggableDialogWindow. d openInWorld. d fullscreen. Looks like, the dialog has to be open first in the World then notified for fullscreen. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

Aug. 5, 2015

Re: [Pharo-users] Modern Events Touch and Gestures in Pharo.

by Dimitris Chloupis

this awesome , great work :) On Tue, Jun 30, 2015 at 8:18 PM stepharo <stepharo(a)free.fr> wrote: > Thanks Thales for the sponsoring. > > https://youtu.be/eNrbH8A5nyY > > Stef and the rmod team > >

Aug. 5, 2015

Help for #fullscreen window

by Jigyasa Grover

Hi ! I am using *WidgetExamples exampleBuilder* to make an accordion widget. I open a model *newPluggableWindow* in it, and would like it to be a fullscreen entity. I have tried all the methods, *#fullscreen *and *#extent* but in vain. It would be great if anyone could help. The code snippet is as : *printSearchResults* *self open. * *SearchQuick searchQuick: self myString. * *builder := WidgetExamples exampleBuilder.* *dialog := (builder newPluggableDialogWindow: 'SEARCH RESULTS FOR " ', myString , ' " ').* *searchResultsAccordion := dialog contentMorph:* *(* * dialog newColumn: { * * dialog newColumn: * * (* * SearchQuick myResult collect: [ :r |* * dialog newRow: {* * (* * (* * dialog newExpander: r title asString* * forAll: { * * ( dialog newTextEditorFor: ( ValueHolder new contents: r content asString )* * getText: #contents setText: #contents: )minHeight: 150.* * }* * )minWidth:750; minHeight: 10* * )* * cellInset: 0;* * borderStyle: (BorderStyle inset baseColor: dialog paneColor; width: 1)* * } * * ]* * ) .* * backBtn := dialog newButtonFor: self action: #backButtonClicked label: 'Back' help: 'Back'.* * backBtn extent: 750(a)30.* * }* * ); minWidth: World extent x; minHeight: World extent y;* * model: nil.* * searchResultsAccordion position: 0(a)0.* * searchResultsAccordion extent: World extent.* * searchResultsAccordion width: World extent x.* * searchResultsAccordion height: World extent y.* * builder newScrollPaneFor: searchResultsAccordion.* * dialog position: 0(a)0.* * dialog extent: World extent.* * builder openModal: dialog.* * dialog newScrollPaneFor: searchResultsAccordion .* Regards Jigyasa

Aug. 5, 2015

Re: [Pharo-users] Garage, Glorp, PostgreSQL and Cursors

by Tommaso Dal Sasso

On 04/08/15 16:25, Guillermo Polito wrote: > Helloooooo :) > > First Tomasso, it's nice to know it's working well for you :). We need > feedback and contributions, even the smallests (like docs, or blogposts > with your experiences or tutorials). > > Answering your question, GarageGlorp does not yet use the cursors from > the Garage drivers. I do not know what exactly should be added to the > Glorp's GarageAdapter, maybe we can take a look at it if you are available. > Hi Guillermo, thanks, that would be really interesting. Unfortunately right now I'm in a hurry to read some data from posgtgres, so I'll manage to do that "by hand" (i.e. without cursors), but I think that if we want to use Pharo for data analysis, being able to process large volume of data in a lean way is a must (it is not the first time I need it) and the option of glorp+cursors to stream the data from the db without kill the ram would be amazing. I would be happy to help enable this feature for Garage, but I don't really know where to look, do you have any hints? Tommaso > For the rest: > > *OpenDBX* -> it is a database abstraction written in C. It was developed > outside the community, though we contribute if necessary. There is also > a driver in Pharo providing bindings against this opendbx library. > *Garage* -> a database abstraction in Pharo. It provides a common > interface to talk with several drivers (e.g., opendbx, native postgres, > native mysql...) > *Glorp* -> an object relational mapping framework that connects to a > database (therefore it needs some database driver) and converts > relational data into objects. > *DBXTalk* -> the umbrella project of all the above (and their connections) > > Cheers, > Guille > > El mar., 4 de ago. de 2015 a la(s) 12:36 a. m., Esteban A. Maringolo > <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> escribiÃ³: > > 2015-08-03 16:20 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com > <mailto:estebanlm@gmail.com>>: > > yesâ¦ just that is not accurate :) > > is basically like that, just that DBXTalk is not a driver, is an > umbrella project. The OpenDBX drivers is still called OpenDBXDriver :P > > TooManyAbstractionsException signal. > > ;) > > Esteban A. Maringolo >

Aug. 5, 2015

Re: [Pharo-users] Garage, Glorp, PostgreSQL and Cursors

by Arturo Zambrano

Thanks Guillermo, we were struggling with all these names also. This reference is important, and IMHO it should be pasted also in the page of every DB related project, so that we can have a map and now where we are. best arturo On Tue, Aug 4, 2015 at 11:25 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > *OpenDBX* -> it is a database abstraction written in C. It was developed > outside the community, though we contribute if necessary. There is also a > driver in Pharo providing bindings against this opendbx library. > *Garage* -> a database abstraction in Pharo. It provides a common > interface to talk with several drivers (e.g., opendbx, native postgres, > native mysql...) > *Glorp* -> an object relational mapping framework that connects to a > database (therefore it needs some database driver) and converts relational > data into objects. > *DBXTalk* -> the umbrella project of all the above (and their connections) > >

Aug. 5, 2015