- Pharo-users - lists.pharo.org

Re: [Pharo-users] FFI seaside3.06 Mac OSX Lion dbxtalk postgres - trouble shooting

by Cameron Sanders

Mariano, *Thank you, regarding the 32 bits!* (I questioned that late one evening, and then I forgot about that possibility!) When I said Seaside3.06, it was straight out of the box (download). *So I will need to see which VM 3.06 has in it. How do I discover that?* I stopped paying attention to the VMs etc, once the one-click installs came with Cog. *It is not clear to me what client libraries I need from the DB vendor in the case of Postgres. Is it included as part of the standard package? * -- Any feedback here is greatly appreciated! Thanks for the information provided, and any more than you can offer! Cam On Tue, Apr 10, 2012 at 4:01 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi. It would also help if you can tell use which VM are you using because > the problem is in fact that FFI cannot find the opendbx library. > Be aware that openDBX has to be compiled 32 bits. That is, if you are in a > 64 bits machine, you will need to compile it for 32 bits. > The same for the database client library. > > Cheers > > On Mon, Apr 9, 2012 at 6:02 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi!! >> >> >> On Sun, Apr 8, 2012 at 11:53 PM, Cameron Sanders <camsanders(a)aol.com>wrote: >> >>> I am having difficulties getting set up and running with DBXTalk tools >>> on a Mac. I hate to pester the community with some basics, but I am getting >>> way too many hours in simply trying to connect to a Postgres DB. Any help >>> or guidance that anyone can offer is greatly appreciated. >>> >>> Keep up the good work on Pharo! It is a great platform! [I have not >>> checked in lately to see where things are with regard to us commercial >>> operators contributing to the community, but I am overdue!] >>> >>> Thanks for the feedback in advance! >>> -Cam >>> >>> >>> *#1:* From http://dbxtalk.smallworks.com.ar/Download/ >>> I see a paragraph near that top that reads: >>> >>> *If in the previous step you have installed OpenDBX by using its >>> binaries (no compilation), then you must install the databse client library >>> (C library) of your database.* >>> >>> By "client library", is the author referring to the libraries like >>> libpgsqlbackend.* which is part of the opendbx binaries? Or do I need to >>> install some posgres client from http://www.postgresql.org/? (My DB >>> server is remote, and this computer knows nothing about it.) >>> >> Yes, you need to install another thing: the client libraries from the >> database vendor. opendbx plays the role as an adaptor making the several >> database platforms polymorphic (in some kind of way :) ). >> See how to test it below in my reply. >> >>> I built the libs locally and successfully installed them -- after >>> finding specs that the utils cannot be compiled for Mac. Permissions for >>> all are read & execute, except for the ".a" libs which have only read >>> permission. >>> >> >> Hmm, how did you test it? >> >> You have to think of this (read the -> as "talks to"): >> >> (Smalltalk image with dbxtalk smalltalk library) -> opendbx c library -> >> database vendor C library -----> database (remote or local, doesn't matter) >> >> so, first of all, what you have to test, is the opendbx c library with >> the vendor's library (and therefore the database). You can do it executing >> the following from the terminal: >> >> ./odbxtest -b pgsql -h localhost -p 5432 -d myDatabase -u myUser -w myPass >> >> where: >> >> ./odbxtest -b <backend> -h <host> -p <port> -d <database name> -u <user> >> -w <password> >> >> *#2: does Pharo know where to look for these libraries on a mac?* Or do >>> I need to define environmental variables to point to them? After fishing >>> around, I read about a file called environment.plist (xml key/value), where >>> I defined the following environmental variables based on a link from >>> dbxtalk pages to a 2008 blog, so now my environment.plist file is stored in >>> ~/.MacOSX and contains the following: >>> >>> *<plist version="1.0"> >>> **<dict> >>> ** <key>LD_LIBRARY_PATH</key> >>> ** <string>/usr/local/lib:usr/lib</string>* >>> >>> * <key>DYLD_LIBRARY_PATH**</key> >>> ** <string>/usr/local/lib:usr/lib</string> >>> **</dict></plist>* >>> >> *More questions:* A) do I need to include the /usr/local/lib/opendbx >>> directory too, or do the dbx tools know to append that directory to the >>> other path elements? and B) after logging back into my computer (actually I >>> did a reboot -- it had been a while), I opened up a terminal, and executed >>> printenv, but the aforementioned variables are not to be seen, is there a >>> Mac expert in the crowd who knows why, or what the right way to do this is? >>> >> I'm not sure about this. I'm using linux, so let someone else answer >> this point. >> What about creating simlinks so you have >> >> /usr/lib/libopendbx.so --> /usr/lib/opendbx/libopendbx.so.whateverversion >> >> >>> *#3:* *Does anybody offer up a fairly clean image that includes the >>> standard seaside suite, and dbxtalk tools all pre-loaded?* >>> >>> I am just curious for the future, as I am currently stuck at testing the >>> OpenDBXDriver connectivity. Which implies that I have more things to >>> install and test. >>> >> >> Nope, sorry :(. But providing a clean image with dbxtalk loaded is not >> the problem. The problem is the rest of the environment you have to setup >> in order to make it work. >> >> >>> *#4 -- FFI question:* In seaside in the OpenDBXDriverTests the tests >>> all fail. (Previously I had altered DBXPostgreFacility>>createConnection to >>> match the db login specs.) When I debug the first failed test, it says >>> "createConnection:" failed "Error: External module not found", which is >>> what led to question(s) #2 up above. >>> >>> >>> An additional question in my mind, is when I am debugging FFI >>> connections, how can I find exactly what library it is trying to load >>> during the failure? And what paths it tried? >>> >>> In this case, looking at the following, near the top of the stack in the >>> debugger: >>> OpenDBXMacOSX>>apiInitialize: handle backend: backend host: host port: >>> port >>> "long odbx_init(odbx_t**, char*, char*, char*)" >>> <cdecl: long 'odbx_init' (ulong* char* char* char*) module: 'opendbx'> >>> ^self externalCallFailed >>> >> >> In unix, I think the LD_LIBRARY_PATH is followed. >> >> >>> >>> I see the reference to the module 'opendbx', so I presume that is the >>> library being sought. *So is the general solution to finding "what" is >>> being sought, to search for the pattern 'module:'?* >>> >> >> which means libopendbx.so is the library that's looked for, at least in >> unix. >> >> >>> * >>> * >>> That still leaves the question of "*where*" it looked. Answers to #2 up >>> above will likely address the rules, but the question stands: *is it >>> possible in the debugger to see where it looked for the module? or is that >>> simply too difficult.* >>> >> >> I don't think current FFI implementation tells you that... >> But there were some threads talking about specifying the module location >> in the image code. So maybe in the future... :/ >> >> >>> >>> Note: FFI unit tests all pass except for one using Form -- "#makeStar >>> method not found." >>> >>> Cheers, >>> Cam >>> >>> >>> >> I hope to be of help. >> BTW, subscribe to the dbxtalk mailing list, I think that list is the >> idoneous place to ask this questions :). >> >> Don't hesitate to ask for more help if needed :). >> Guille >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >

April 10, 2012

Re: [Pharo-users] FFI seaside3.06 Mac OSX Lion dbxtalk postgres - trouble shooting

by Mariano Martinez Peck

Hi. It would also help if you can tell use which VM are you using because the problem is in fact that FFI cannot find the opendbx library. Be aware that openDBX has to be compiled 32 bits. That is, if you are in a 64 bits machine, you will need to compile it for 32 bits. The same for the database client library. Cheers On Mon, Apr 9, 2012 at 6:02 PM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > Hi!! > > > On Sun, Apr 8, 2012 at 11:53 PM, Cameron Sanders <camsanders(a)aol.com>wrote: > >> I am having difficulties getting set up and running with DBXTalk tools on >> a Mac. I hate to pester the community with some basics, but I am getting >> way too many hours in simply trying to connect to a Postgres DB. Any help >> or guidance that anyone can offer is greatly appreciated. >> >> Keep up the good work on Pharo! It is a great platform! [I have not >> checked in lately to see where things are with regard to us commercial >> operators contributing to the community, but I am overdue!] >> >> Thanks for the feedback in advance! >> -Cam >> >> >> *#1:* From http://dbxtalk.smallworks.com.ar/Download/ >> I see a paragraph near that top that reads: >> >> *If in the previous step you have installed OpenDBX by using its >> binaries (no compilation), then you must install the databse client library >> (C library) of your database.* >> >> By "client library", is the author referring to the libraries like >> libpgsqlbackend.* which is part of the opendbx binaries? Or do I need to >> install some posgres client from http://www.postgresql.org/? (My DB >> server is remote, and this computer knows nothing about it.) >> > Yes, you need to install another thing: the client libraries from the > database vendor. opendbx plays the role as an adaptor making the several > database platforms polymorphic (in some kind of way :) ). > See how to test it below in my reply. > >> I built the libs locally and successfully installed them -- after finding >> specs that the utils cannot be compiled for Mac. Permissions for all are >> read & execute, except for the ".a" libs which have only read permission. >> > > Hmm, how did you test it? > > You have to think of this (read the -> as "talks to"): > > (Smalltalk image with dbxtalk smalltalk library) -> opendbx c library -> > database vendor C library -----> database (remote or local, doesn't matter) > > so, first of all, what you have to test, is the opendbx c library with the > vendor's library (and therefore the database). You can do it executing the > following from the terminal: > > ./odbxtest -b pgsql -h localhost -p 5432 -d myDatabase -u myUser -w myPass > > where: > > ./odbxtest -b <backend> -h <host> -p <port> -d <database name> -u <user> > -w <password> > > *#2: does Pharo know where to look for these libraries on a mac?* Or do >> I need to define environmental variables to point to them? After fishing >> around, I read about a file called environment.plist (xml key/value), where >> I defined the following environmental variables based on a link from >> dbxtalk pages to a 2008 blog, so now my environment.plist file is stored in >> ~/.MacOSX and contains the following: >> >> *<plist version="1.0"> >> **<dict> >> ** <key>LD_LIBRARY_PATH</key> >> ** <string>/usr/local/lib:usr/lib</string>* >> >> * <key>DYLD_LIBRARY_PATH**</key> >> ** <string>/usr/local/lib:usr/lib</string> >> **</dict></plist>* >> > *More questions:* A) do I need to include the /usr/local/lib/opendbx >> directory too, or do the dbx tools know to append that directory to the >> other path elements? and B) after logging back into my computer (actually I >> did a reboot -- it had been a while), I opened up a terminal, and executed >> printenv, but the aforementioned variables are not to be seen, is there a >> Mac expert in the crowd who knows why, or what the right way to do this is? >> > I'm not sure about this. I'm using linux, so let someone else answer this > point. > What about creating simlinks so you have > > /usr/lib/libopendbx.so --> /usr/lib/opendbx/libopendbx.so.whateverversion > > >> *#3:* *Does anybody offer up a fairly clean image that includes the >> standard seaside suite, and dbxtalk tools all pre-loaded?* >> >> I am just curious for the future, as I am currently stuck at testing the >> OpenDBXDriver connectivity. Which implies that I have more things to >> install and test. >> > > Nope, sorry :(. But providing a clean image with dbxtalk loaded is not > the problem. The problem is the rest of the environment you have to setup > in order to make it work. > > >> *#4 -- FFI question:* In seaside in the OpenDBXDriverTests the tests all >> fail. (Previously I had altered DBXPostgreFacility>>createConnection to >> match the db login specs.) When I debug the first failed test, it says >> "createConnection:" failed "Error: External module not found", which is >> what led to question(s) #2 up above. >> >> >> An additional question in my mind, is when I am debugging FFI >> connections, how can I find exactly what library it is trying to load >> during the failure? And what paths it tried? >> >> In this case, looking at the following, near the top of the stack in the >> debugger: >> OpenDBXMacOSX>>apiInitialize: handle backend: backend host: host port: >> port >> "long odbx_init(odbx_t**, char*, char*, char*)" >> <cdecl: long 'odbx_init' (ulong* char* char* char*) module: 'opendbx'> >> ^self externalCallFailed >> > > In unix, I think the LD_LIBRARY_PATH is followed. > > >> >> I see the reference to the module 'opendbx', so I presume that is the >> library being sought. *So is the general solution to finding "what" is >> being sought, to search for the pattern 'module:'?* >> > > which means libopendbx.so is the library that's looked for, at least in > unix. > > >> * >> * >> That still leaves the question of "*where*" it looked. Answers to #2 up >> above will likely address the rules, but the question stands: *is it >> possible in the debugger to see where it looked for the module? or is that >> simply too difficult.* >> > > I don't think current FFI implementation tells you that... > But there were some threads talking about specifying the module location > in the image code. So maybe in the future... :/ > > >> >> Note: FFI unit tests all pass except for one using Form -- "#makeStar >> method not found." >> >> Cheers, >> Cam >> >> >> > I hope to be of help. > BTW, subscribe to the dbxtalk mailing list, I think that list is the > idoneous place to ask this questions :). > > Don't hesitate to ask for more help if needed :). > Guille > -- Mariano http://marianopeck.wordpress.com

April 10, 2012

Re: [Pharo-users] FFI seaside3.06 Mac OSX Lion dbxtalk postgres - trouble shooting

by Guillermo Polito

Hi!! On Sun, Apr 8, 2012 at 11:53 PM, Cameron Sanders <camsanders(a)aol.com> wrote: > I am having difficulties getting set up and running with DBXTalk tools on > a Mac. I hate to pester the community with some basics, but I am getting > way too many hours in simply trying to connect to a Postgres DB. Any help > or guidance that anyone can offer is greatly appreciated. > > Keep up the good work on Pharo! It is a great platform! [I have not > checked in lately to see where things are with regard to us commercial > operators contributing to the community, but I am overdue!] > > Thanks for the feedback in advance! > -Cam > > > *#1:* From http://dbxtalk.smallworks.com.ar/Download/ > I see a paragraph near that top that reads: > > *If in the previous step you have installed OpenDBX by using its binaries > (no compilation), then you must install the databse client library (C > library) of your database.* > > By "client library", is the author referring to the libraries like > libpgsqlbackend.* which is part of the opendbx binaries? Or do I need to > install some posgres client from http://www.postgresql.org/? (My DB > server is remote, and this computer knows nothing about it.) > Yes, you need to install another thing: the client libraries from the database vendor. opendbx plays the role as an adaptor making the several database platforms polymorphic (in some kind of way :) ). See how to test it below in my reply. > I built the libs locally and successfully installed them -- after finding > specs that the utils cannot be compiled for Mac. Permissions for all are > read & execute, except for the ".a" libs which have only read permission. > Hmm, how did you test it? You have to think of this (read the -> as "talks to"): (Smalltalk image with dbxtalk smalltalk library) -> opendbx c library -> database vendor C library -----> database (remote or local, doesn't matter) so, first of all, what you have to test, is the opendbx c library with the vendor's library (and therefore the database). You can do it executing the following from the terminal: ./odbxtest -b pgsql -h localhost -p 5432 -d myDatabase -u myUser -w myPass where: ./odbxtest -b <backend> -h <host> -p <port> -d <database name> -u <user> -w <password> *#2: does Pharo know where to look for these libraries on a mac?* Or do I > need to define environmental variables to point to them? After fishing > around, I read about a file called environment.plist (xml key/value), where > I defined the following environmental variables based on a link from > dbxtalk pages to a 2008 blog, so now my environment.plist file is stored in > ~/.MacOSX and contains the following: > > *<plist version="1.0"> > **<dict> > ** <key>LD_LIBRARY_PATH</key> > ** <string>/usr/local/lib:usr/lib</string>* > > * <key>DYLD_LIBRARY_PATH**</key> > ** <string>/usr/local/lib:usr/lib</string> > **</dict></plist>* > *More questions:* A) do I need to include the /usr/local/lib/opendbx > directory too, or do the dbx tools know to append that directory to the > other path elements? and B) after logging back into my computer (actually I > did a reboot -- it had been a while), I opened up a terminal, and executed > printenv, but the aforementioned variables are not to be seen, is there a > Mac expert in the crowd who knows why, or what the right way to do this is? > I'm not sure about this. I'm using linux, so let someone else answer this point. What about creating simlinks so you have /usr/lib/libopendbx.so --> /usr/lib/opendbx/libopendbx.so.whateverversion > *#3:* *Does anybody offer up a fairly clean image that includes the > standard seaside suite, and dbxtalk tools all pre-loaded?* > > I am just curious for the future, as I am currently stuck at testing the > OpenDBXDriver connectivity. Which implies that I have more things to > install and test. > Nope, sorry :(. But providing a clean image with dbxtalk loaded is not the problem. The problem is the rest of the environment you have to setup in order to make it work. > *#4 -- FFI question:* In seaside in the OpenDBXDriverTests the tests all > fail. (Previously I had altered DBXPostgreFacility>>createConnection to > match the db login specs.) When I debug the first failed test, it says > "createConnection:" failed "Error: External module not found", which is > what led to question(s) #2 up above. > > > An additional question in my mind, is when I am debugging FFI connections, > how can I find exactly what library it is trying to load during the > failure? And what paths it tried? > > In this case, looking at the following, near the top of the stack in the > debugger: > OpenDBXMacOSX>>apiInitialize: handle backend: backend host: host port: port > "long odbx_init(odbx_t**, char*, char*, char*)" > <cdecl: long 'odbx_init' (ulong* char* char* char*) module: 'opendbx'> > ^self externalCallFailed > In unix, I think the LD_LIBRARY_PATH is followed. > > I see the reference to the module 'opendbx', so I presume that is the > library being sought. *So is the general solution to finding "what" is > being sought, to search for the pattern 'module:'?* > which means libopendbx.so is the library that's looked for, at least in unix. > * > * > That still leaves the question of "*where*" it looked. Answers to #2 up > above will likely address the rules, but the question stands: *is it > possible in the debugger to see where it looked for the module? or is that > simply too difficult.* > I don't think current FFI implementation tells you that... But there were some threads talking about specifying the module location in the image code. So maybe in the future... :/ > > Note: FFI unit tests all pass except for one using Form -- "#makeStar > method not found." > > Cheers, > Cam > > > I hope to be of help. BTW, subscribe to the dbxtalk mailing list, I think that list is the idoneous place to ask this questions :). Don't hesitate to ask for more help if needed :). Guille

April 9, 2012

FFI seaside3.06 Mac OSX Lion dbxtalk postgres - trouble shooting

by Cameron Sanders

I am having difficulties getting set up and running with DBXTalk tools on a Mac. I hate to pester the community with some basics, but I am getting way too many hours in simply trying to connect to a Postgres DB. Any help or guidance that anyone can offer is greatly appreciated. Keep up the good work on Pharo! It is a great platform! [I have not checked in lately to see where things are with regard to us commercial operators contributing to the community, but I am overdue!] Thanks for the feedback in advance! -Cam *#1:* From http://dbxtalk.smallworks.com.ar/Download/ I see a paragraph near that top that reads: *If in the previous step you have installed OpenDBX by using its binaries (no compilation), then you must install the databse client library (C library) of your database.* By "client library", is the author referring to the libraries like libpgsqlbackend.* which is part of the opendbx binaries? Or do I need to install some posgres client from http://www.postgresql.org/? (My DB server is remote, and this computer knows nothing about it.) I built the libs locally and successfully installed them -- after finding specs that the utils cannot be compiled for Mac. Permissions for all are read & execute, except for the ".a" libs which have only read permission. *#2: does Pharo know where to look for these libraries on a mac?* Or do I need to define environmental variables to point to them? After fishing around, I read about a file called environment.plist (xml key/value), where I defined the following environmental variables based on a link from dbxtalk pages to a 2008 blog, so now my environment.plist file is stored in ~/.MacOSX and contains the following: *<plist version="1.0"> **<dict> ** <key>LD_LIBRARY_PATH</key> ** <string>/usr/local/lib:usr/lib</string>* * <key>DYLD_LIBRARY_PATH**</key> ** <string>/usr/local/lib:usr/lib</string> **</dict></plist>* *More questions:* A) do I need to include the /usr/local/lib/opendbx directory too, or do the dbx tools know to append that directory to the other path elements? and B) after logging back into my computer (actually I did a reboot -- it had been a while), I opened up a terminal, and executed printenv, but the aforementioned variables are not to be seen, is there a Mac expert in the crowd who knows why, or what the right way to do this is? *#3:* *Does anybody offer up a fairly clean image that includes the standard seaside suite, and dbxtalk tools all pre-loaded?* I am just curious for the future, as I am currently stuck at testing the OpenDBXDriver connectivity. Which implies that I have more things to install and test. *#4 -- FFI question:* In seaside in the OpenDBXDriverTests the tests all fail. (Previously I had altered DBXPostgreFacility>>createConnection to match the db login specs.) When I debug the first failed test, it says "createConnection:" failed "Error: External module not found", which is what led to question(s) #2 up above. An additional question in my mind, is when I am debugging FFI connections, how can I find exactly what library it is trying to load during the failure? And what paths it tried? In this case, looking at the following, near the top of the stack in the debugger: OpenDBXMacOSX>>apiInitialize: handle backend: backend host: host port: port "long odbx_init(odbx_t**, char*, char*, char*)" <cdecl: long 'odbx_init' (ulong* char* char* char*) module: 'opendbx'> ^self externalCallFailed I see the reference to the module 'opendbx', so I presume that is the library being sought. *So is the general solution to finding "what" is being sought, to search for the pattern 'module:'?* * * That still leaves the question of "*where*" it looked. Answers to #2 up above will likely address the rules, but the question stands: *is it possible in the debugger to see where it looked for the module? or is that simply too difficult.* Note: FFI unit tests all pass except for one using Form -- "#makeStar method not found." Cheers, Cam

April 8, 2012

Re: [Pharo-users] Help with the interaction with widgets or morphs like Checkboxes, and Radio buttons and Texteditor boxes

by S Krish

openInWorld / openCenteredInWorld / openInWorld: all of them should work.. openModal: does what it says...! makes the dialog modal. On Sat, Apr 7, 2012 at 9:07 AM, Nelson Pingitore <pingitorenelson(a)gmail.com>wrote: > When I am using a construct such as the following: > > builder := UITheme exampleBuilder. > dialog := (builder newPluggableDialogWindow: 'Example basic controls') > useDefaultOKCancelButton. > . > . > . > > model: nil. > builder openModal: dialog. > > is there another option other than "openModel", to use to open the dialog? > > > On Sat, Mar 31, 2012 at 5:34 PM, S Krish < > krishnamachari.sudhakar(a)gmail.com> wrote: > >> I hope this might help... >> >> Simple SUnit tests.. through basic morphic... >> >> LayoutTests and MorphicWidgetTests would be nice.. #testModelAndView >> would be basics of what might help... >> >> But they are really the very rudimentary stuff.. Always use Model >> /controller - presenter along with the View/ UI class. makes it easier.. >> >> >> >> On Sun, Apr 1, 2012 at 2:54 AM, S Krish < >> krishnamachari.sudhakar(a)gmail.com> wrote: >> >>> I am not sure I would recommend using Builder.. except for playing >>> initially around. >>> >>> It is better to simply use the basic capabilities in Morph and tie it up >>> with TableLayout policy.. Proportional Layout >>> >>> In that you do have a better chance of working these issues out once you >>> get the core behaviors, the API/ methods of each of the morphs. That said >>> many of these morphs are not perfect and will require patience to rip >>> through the attributes you need and save to inst vars et al. >>> >>> Maybe sometime soon I can package a clean MorphicView system that will >>> alleviate this pain of figuring out Morphic.. but its fun once you figure >>> it out.. >>> >>> >>> >>> >>> On Sat, Mar 31, 2012 at 7:44 AM, Nelson Pingitore < >>> pingitorenelson(a)gmail.com> wrote: >>> >>>> Hello Pharo Users. I am seeking help with the interaction with widgets >>>> or morphs like Checkboxes, and Radio buttons and Texteditor boxes, I am >>>> creating a User Settings Class to learn how to use Pharo. I copied some >>>> core widgets from the UITheme exampleBasicControls. I would like to know, >>>> starting with the code below, how to detect if the User has selected the >>>> "Ok" or "Cancel" button in the lower right of the form, and then if the >>>> user selects "Ok" how do I detect the state of the widgets (Checkboxes, >>>> Radio buttons, or Texteditor), and save those states to instance variables? >>>> >>>> |dialog builder radioModel treeModel CheckboxA| >>>> builder := UITheme exampleBuilder. >>>> dialog := (builder newPluggableDialogWindow: 'Example basic controls') >>>> useDefaultOKCancelButton. >>>> radioModel := ExampleRadioButtonModel new. >>>> treeModel := ValueHolder new contents: TextStyle actualTextStyles >>>> explorerContents. >>>> dialog contentMorph: >>>> ( >>>> ( >>>> dialog newRow: >>>> { >>>> dialog newLabelGroup: >>>> { >>>> 'Normal Label'->(dialog newLabel: 'A Label'). >>>> 'Normal Button'->(dialog newButtonFor: nil action: nil label: 'A >>>> Button' help: 'This is a button'). >>>> 'Default Button'->((dialog newButtonFor: nil action: nil label: >>>> 'Default Button' help: 'This is a default button') isDefault: true). >>>> 'Selected Button'->(dialog newButtonFor: (ValueHolder new >>>> contents: true) getState: #contents >>>> action: nil arguments: #() getEnabled: nil label: 'A Button' >>>> help: 'This is a selected button'). >>>> 'Checkbox A'->(dialog newCheckboxFor: (ValueHolder new contents: >>>> true) >>>> getSelected: #contents setSelected: #contents: label: 'A >>>> Checkbox' help: 'This is a checkbox'). >>>> 'Checkbox B'->(dialog newCheckboxFor: (ValueHolder new contents: >>>> true) >>>> getSelected: #contents setSelected: #contents: label: 'A >>>> Checkbox' help: 'This is a checkbox'). >>>> 'Checkbox C'->(dialog newCheckboxFor: (ValueHolder new contents: >>>> true) >>>> getSelected: #contents setSelected: #contents: label: 'A >>>> Checkbox' help: 'This is a checkbox'). >>>> 'Radio Buttons'-> >>>> ( >>>> ( >>>> dialog newColumn: >>>> { >>>> (dialog newRadioButtonFor: radioModel getSelected: #isLeft >>>> setSelected: #beLeft label: 'Left' help: 'This is a radio buton'). >>>> (dialog newRadioButtonFor: radioModel getSelected: #isCenter >>>> setSelected: #beCenter label: 'Center' help: 'This is a radio buton'). >>>> (dialog newRadioButtonFor: radioModel getSelected: #isRight >>>> setSelected: #beRight label: 'Right' help: 'This is a radio buton') >>>> } >>>> ) >>>> vResizing: #shrinkWrap >>>> ). >>>> 'Text Entry'->(dialog newTextEntryFor: (ValueHolder new contents: >>>> 'Hello') getText: #contents setText: #contents: help: 'This is a text >>>> entry'). >>>> 'Slider'->(dialog newSliderFor: (ValueHolder new contents: 0.5) >>>> getValue: #contents setValue: #contents: help: 'This is a slider'). >>>> 'Bump Temp'->(dialog newTextEntryFor: (ValueHolder new contents: >>>> '75') getText: #contents setText: #contents: help: 'This is the random >>>> shift'). >>>> }. >>>> dialog newVerticalSeparator. >>>> dialog newLabelGroup: >>>> { >>>> 'Drop List'->(dialog newDropListFor: (ListModel new list: #('One' >>>> 'Two' 'Three' 'Four')) >>>> list: #list getSelected: #selectionIndex setSelected: >>>> #selectionIndex: help: 'This is a drop list'). >>>> 'Normal List'-> >>>> ( >>>> ( >>>> dialog newListFor: (ListModel new list: #('One' 'Two' 'Three' >>>> 'Four'); selectionIndex: 3) list: #list selected: #selectionIndex >>>> changeSelected: #selectionIndex: >>>> help: 'This is a list' >>>> ) >>>> minWidth: 120 >>>> ). >>>> }. >>>> } >>>> ) >>>> vResizing: #spaceFill >>>> ); >>>> model: nil. >>>> builder openModal: dialog. >>>> >>> >>> >> >

April 8, 2012

Re: [Pharo-users] Developing a Splash Screen...

by Bernat Romagosa

A tiny correction: [ (Delay forSeconds: 5) wait. image delete ] fork. You may wanna do this in the #startUp method of your class, and register it to the startup list by doing Smalltalk addToStartUpList: YourClass. Cheers! 2012/4/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Apr 8, 2012, at 5:31 AM, Nelson Pingitore wrote: > > > I am attempting to add a Splash Screen to a Pharo project. I currently > use the following to bring up the image: > > > > > > (ImageReadWriter formFromFileNamed: > 'C:\Users\npingito\Documents\Smalltalk\Splash Screen\splash.bmp') asMorph > openInWorld > > > > my question is, how can I close this image after a delay, such as after > 10 seconds, and is there a better construct to use? > > > > [Delay forSeconds: 5. > image delete.] fork > > ? > > > > Nelson > > > -- Bernat Romagosa.

April 8, 2012

Re: [Pharo-users] Developing a Splash Screen...

by StÃ©phane Ducasse

On Apr 8, 2012, at 5:31 AM, Nelson Pingitore wrote: > I am attempting to add a Splash Screen to a Pharo project. I currently use the following to bring up the image: > > > (ImageReadWriter formFromFileNamed: 'C:\Users\npingito\Documents\Smalltalk\Splash Screen\splash.bmp') asMorph openInWorld > > my question is, how can I close this image after a delay, such as after 10 seconds, and is there a better construct to use? [Delay forSeconds: 5. image delete.] fork ? > > Nelson

April 8, 2012

Developing a Splash Screen...

by Nelson Pingitore

I am attempting to add a Splash Screen to a Pharo project. I currently use the following to bring up the image: *(ImageReadWriter formFromFileNamed: 'C:\Users\npingito\Documents\Smalltalk\Splash Screen\splash.bmp') asMorph openInWorld * my question is, how can I close this image after a delay, such as after 10 seconds, and is there a better construct to use? Nelson

April 8, 2012

GSoC news: we got 30 proposals, few stats

by Janko MivÅ¡ek

Dear Smalltalkers, Yesterday passed a deadline for students to propose how will they do the projects and we received 30 proposals from 23 students, which is in my opinion quite a nice number and I'm sure we can end up with quite a number of nice projects this year. And what is even more important: new Smalltalkers in community! Next two weeks mentors will review and rank/vote for the proposals, Google will give us a number of stipendiums it will provide and in few days after Friday 20.April we will have a final list of accepted students and their projects. Few stats (numbers of all participating): 32 projects 34 mentors 32 students 30 proposals 23 students wrote proposal Students by Smalltalk skill: 11 None 9 Low 5 Medium 7 High Students from countries: 5 Argentina 5 India 4 Russia 3 USA 2 Chile 2 Czech Republic 2 Malaysia 1 China 1 Croatia 1 Ecuador 1 Egypt 1 France 1 Germany 1 Sweden 1 Ukraine 1 Slovenia Stay tuned! Janko @ Carla -- Smalltalk GSoC Admin Team http://gsoc2012.esug.org

April 7, 2012

Fwd: [Pharo-project] [ANN] NBOpenGL update

by StÃ©phane Ducasse

Begin forwarded message: > From: Igor Stasenko <siguctua(a)gmail.com> > Subject: [Pharo-project] [ANN] NBOpenGL update > Date: April 6, 2012 3:31:54 PM GMT+02:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Hi there, > > for those, who interested, i updated a NBOpenGL configuration. > > Changes are: > > - updated GL API to most recent available (taken directly from opengl > specs). Now there is about 300 more methods to explore :) > - finally dealt with win32 support code and made it working again > - fixed the GLX function prefix , which should be 'glX' not 'glx' > > To load it in 1.4 use: > > Gofer new > squeaksource: 'NBOpenGL'; > package: 'ConfigurationOfNBOpenGL'; > load. > > > and then > > (ConfigurationOfNBOpenGL project version: '1.0.2') load > > I did not tested the update thoroughly.. so i would appreciate if > people will try it out and tell how it goes. > > > -- > Best regards, > Igor Stasenko. >

April 7, 2012