September 2014 - Pharo-users

Re: [Pharo-users] UI testing

by Marcus Denker

On 30 Sep 2014, at 11:00, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > Hi all, > > Is there anything in Pharo that supports UI testing? > What I would like to achieve is to be able to simulate a click, select a menu item, input some text in text fields, Ok/Cancel button click, and some other basic task for the automation of my tests. > > With Glamour, I can simulate transmissions programatically and then test for the display values in the presentations or dig the resulting morph structure to test for specific information. The problem with dialog boxes is that once launched, I cannot perform anything in the system because my test code is active only when dialog boxes get their intended input and are validated. > > So, if there is anything for simulating testing "scenarios" (click on second button -> select third menu item -> fill up text field -> select color -> ok button -> test fourth PanelMorph in the window ), it would be really helpful and make my testing much more productive. > There is UITestCase (see the subclasses), e.g. testSimulateClick "self run: #testSimulateClick" morph := TextMorph new contents: ''; openInWorld. morph simulateClick. self assert: morph hasKeyboardFocus. But it definitely needs more e.g. for pressing buttons and things like that. Marcus

Sept. 30, 2014

Re: [Pharo-users] Versioneer. nice. mmMmmm...

by kilon alios

Not really, not if you are a begineer like me and does not come to mind to right click on the entry. A GUI should have as button all the basic functionality. Obviously not all functionality should be crammed into a GUI , though depending on the design thats possible too. Also I do feel Versioneer can be an excellent tool even replacing Configuration Browser, allowing users to browse through projects in metarepo repositories and choose specific version for each package to load, even display information for those packages. I love the tool as it is, but I do feel there is a lot more potential in it and I am willing to contribute if that is desirable. On Tue, Sep 30, 2014 at 11:52 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Hi Kilon, > > Le 29 sept. 2014 Ã 19:24, kilon alios a Ã©crit : > > > great tool, the only thing missing is a button to load the configurations > > What do you mean? > > > /versions. > > To load a version, select a version in the version list, rigth-click and > select "load". Isn't it enough? > >

Sept. 30, 2014

UI testing

by Usman Bhatti

Hi all, Is there anything in Pharo that supports UI testing? What I would like to achieve is to be able to simulate a click, select a menu item, input some text in text fields, Ok/Cancel button click, and some other basic task for the automation of my tests. With Glamour, I can simulate transmissions programatically and then test for the display values in the presentations or dig the resulting morph structure to test for specific information. The problem with dialog boxes is that once launched, I cannot perform anything in the system because my test code is active only when dialog boxes get their intended input and are validated. So, if there is anything for simulating testing "scenarios" (click on second button -> select third menu item -> fill up text field -> select color -> ok button -> test fourth PanelMorph in the window ), it would be really helpful and make my testing much more productive. regards, usman

Sept. 30, 2014

Re: [Pharo-users] Versioneer. nice. mmMmmm...

by Christophe Demarey

Hi Kilon, Le 29 sept. 2014 Ã 19:24, kilon alios a Ã©crit : > great tool, the only thing missing is a button to load the configurations What do you mean? > /versions. To load a version, select a version in the version list, rigth-click and select "load". Isn't it enough?

Sept. 30, 2014

Re: [Pharo-users] BLOG: Block Translators - parsing magic

by Udo Schneider

Hi Damien, moving to Pillar was quite easy: http://pillarhub.pharocloud.com/hub/UdoSchneider/6bqsrq7ut85ddotzjy2xqrtth How to proceed? Best Regards, Udo On 29.09.14 18:47, Udo Schneider wrote: > Hi Damien, > > I think the most important thing to start with is not to add content, > > but to put the content you already have in > > > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english. > > You will have to use Pillar: > > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > I did write the entry in Markdown - so converting it to Pillar shouldn't > be a big deal. I'll start translating t now. > > Best Regards, > > Udo > > > > On 28.09.2014 11:08, Damien Cassou wrote: >> Hi Udo, >> >> On Thu, Sep 25, 2014 at 10:28 PM, Udo Schneider >> <udo.schneider(a)homeaddress.de> wrote: >>>> We could easily turn your blog into a chapter for a future book :) >>> Wow! I didn't really expect that! But I'd happy to help any way I >>> can. Maybe >>> by adding some bits an pieces how to parse blocks with multiple >>> expressions? >> >> >> I think the most important thing to start with is not to add content, >> but to put the content you already have in >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english. >> You will have to use Pillar: >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> > > > >

Sept. 29, 2014

Re: [Pharo-users] Versioneer. nice. mmMmmm...

by kilon alios

great tool, the only thing missing is a button to load the configurations/versions. On Mon, Sep 29, 2014 at 7:17 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Hi Ben, > > Le 22 sept. 2014 Ã 18:23, Ben Coman a Ã©crit : > > > > > While I had done the Versioneer tutorial some time ago, I had some > inertial problem using it in anger. Now I'm happy to report using it just > now to update the ConfigurationOfPharoLauncher was simple and smooth - > which is great since I've never done a Configuration by hand. I thought it > would be useful for others to see how simple it was... > > > > 1. Loaded latest ConfigurationOfPharoLauncher. > > 2. Loaded and tested newer PharoLauncher packages. > > > > 3. Opened World > Tools > Versioneer. > > 4. Selected PharoLauncher and <Open Project>. > > 5. Selected "development" list item. > > 6. Clicked <Release Version> and <Ok> to accept auto increment of > version number. > > 7. Clicked <Commit the project> > > Now there is an updated ConfigurationOfPharoLauncher in its Smalltalkhub > repository. > > > > Easy with Versioneer. mmMmmmm. nice. shiny..... > > cheers -ben > > I'm happy to see that this tool is useful. Still improvable on many points > but helps a lot for basic tasks. > > Christophe > >

Sept. 29, 2014

Re: [Pharo-users] Unicode support in Pharo

by Sven Van Caekenberghe

On 29 Sep 2014, at 19:10, Robert Shiplett <grshiplett(a)gmail.com> wrote: > Must be a thing about European "guys" ... > > <quote> > > - ByteString is needed for most european/occidental people who don't care about internationalization and should stay because Pharo is an european/english based system , also not to break existing code > (again will be transparent to most users for same reason). > > </unquote> > > Of all reasons to retain ByteString, let's hope this one is not listed, lest we appear ridiculous in our threads. Apart from being incorrect, it is indeed a totally wrong formulation which furthermore gives a bad impression. ByteString is simply an optimisation covering Strings where all characters use the lower 256 Unicode code points. > On 26 September 2014 18:22, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Le 26/09/2014 20:47, stepharo a Ã©crit : > I'm not expert and I would like to know what people think. > But I think that we should consider > > - the impact of spur new object format. I would like to have > unicode and clean the leadChar > > Stef > > > Just to start a new thread about that, because it deserves it > and also some people might appreciate :) > (was in: "Ridiculous we are"). > > I may not be the most qualified to state on that but I give my 2c > (this is a community isn't it ? please do not flame...) > > As Sven said, the situation is not so bad (quite good in fact): Pharo has true unicode built-in support with WideString and encoders (great job, IMHO this part of Zn components should be in the base system > or in an internationalization package not hidden in an htpp components package). > - encoding support has to be in the system : ZnEncoders(?) for utf8, unicode and other encoders for locale support because of existing system basis, web (utf8) and internationalization. > - this will be transparent: Smalltalk is a typeless langage, one do not have to specify String type (ByteString or WideString) > - Spur new character encoding is very interesting (in alpha stage now) and will be transparent for the same reason (though I'm still wondering of the 32bits/64 bits encoding on a 64 bits vm?). > - ByteString is needed for most european/occidental people who don't care about internationalization and should stay because Pharo is an european/english based system , also not to break existing code > (again will be transparent to most users for same reason). > - some parts of the system seems to be not "WideString/unicode aware" : > Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), but GT Inspector display is ok. > Font plugin seems to require little work : uses fopen instead of _wfopen (utf16 version) on windows and needs utf8 convertion on unix. > may be a check with File plugin (and other system related plugins) is also needed? > > In short, some little additionnal work but a very good basis. > (but what is leadChar about?) > > Regards, > > Alain > > >

Sept. 29, 2014

Re: [Pharo-users] Unicode support in Pharo

by Robert Shiplett

Must be a thing about European "guys" ... <quote> - ByteString is needed for most european/occidental people who don't care about internationalization and should stay because Pharo is an european/english based system , also not to break existing code (again will be transparent to most users for same reason). </unquote> Of all reasons to retain ByteString, let's hope this one is not listed, lest we appear ridiculous in our threads. r On 26 September 2014 18:22, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Le 26/09/2014 20:47, stepharo a Ã©crit : > >> I'm not expert and I would like to know what people think. >> But I think that we should consider >> >> - the impact of spur new object format. I would like to have >> unicode and clean the leadChar >> >> Stef >> >> >> Just to start a new thread about that, because it deserves it > and also some people might appreciate :) > (was in: "Ridiculous we are"). > > I may not be the most qualified to state on that but I give my 2c > (this is a community isn't it ? please do not flame...) > > As Sven said, the situation is not so bad (quite good in fact): Pharo has > true unicode built-in support with WideString and encoders (great job, IMHO > this part of Zn components should be in the base system > or in an internationalization package not hidden in an htpp components > package). > - encoding support has to be in the system : ZnEncoders(?) for utf8, > unicode and other encoders for locale support because of existing system > basis, web (utf8) and internationalization. > - this will be transparent: Smalltalk is a typeless langage, one do not > have to specify String type (ByteString or WideString) > - Spur new character encoding is very interesting (in alpha stage now) and > will be transparent for the same reason (though I'm still wondering of the > 32bits/64 bits encoding on a 64 bits vm?). > - ByteString is needed for most european/occidental people who don't care > about internationalization and should stay because Pharo is an > european/english based system , also not to break existing code > (again will be transparent to most users for same reason). > - some parts of the system seems to be not "WideString/unicode aware" : > Pasting a Greek string in a workspace shows hieroglyphs (editors? morph?), > but GT Inspector display is ok. > Font plugin seems to require little work : uses fopen instead of _wfopen > (utf16 version) on windows and needs utf8 convertion on unix. > may be a check with File plugin (and other system related plugins) is also > needed? > > In short, some little additionnal work but a very good basis. > (but what is leadChar about?) > > Regards, > > Alain > > >

Sept. 29, 2014

Re: [Pharo-users] BLOG: Block Translators - parsing magic

by Udo Schneider

Hi Damien, I think the most important thing to start with is not to add content, > but to put the content you already have in > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english. > You will have to use Pillar: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… I did write the entry in Markdown - so converting it to Pillar shouldn't be a big deal. I'll start translating t now. Best Regards, Udo On 28.09.2014 11:08, Damien Cassou wrote: > Hi Udo, > > On Thu, Sep 25, 2014 at 10:28 PM, Udo Schneider > <udo.schneider(a)homeaddress.de> wrote: >>> We could easily turn your blog into a chapter for a future book :) >> Wow! I didn't really expect that! But I'd happy to help any way I can. Maybe >> by adding some bits an pieces how to parse blocks with multiple expressions? > > > I think the most important thing to start with is not to add content, > but to put the content you already have in > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english. > You will have to use Pillar: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >

Sept. 29, 2014

Re: [Pharo-users] Versioneer. nice. mmMmmm...

by Christophe Demarey

Hi Ben, Le 22 sept. 2014 Ã 18:23, Ben Coman a Ã©crit : > > While I had done the Versioneer tutorial some time ago, I had some inertial problem using it in anger. Now I'm happy to report using it just now to update the ConfigurationOfPharoLauncher was simple and smooth - which is great since I've never done a Configuration by hand. I thought it would be useful for others to see how simple it was... > > 1. Loaded latest ConfigurationOfPharoLauncher. > 2. Loaded and tested newer PharoLauncher packages. > > 3. Opened World > Tools > Versioneer. > 4. Selected PharoLauncher and <Open Project>. > 5. Selected "development" list item. > 6. Clicked <Release Version> and <Ok> to accept auto increment of version number. > 7. Clicked <Commit the project> > Now there is an updated ConfigurationOfPharoLauncher in its Smalltalkhub repository. > > Easy with Versioneer. mmMmmmm. nice. shiny..... > cheers -ben I'm happy to see that this tool is useful. Still improvable on many points but helps a lot for basic tasks. Christophe

Sept. 29, 2014