December 2013 - Pharo-users

Re: [Pharo-users] have a question for morphic Designer in pharo.

by Igor Stasenko

On 20 December 2013 02:24, peter yoo <onionmixer(a)gmail.com> wrote: > hello smalltalker! this is my first thread. > > first! im smalltalk newbie and use ogly english. sorry!!! > > welcome aboard! > > i want using "Morphic Designer" in pharo. > because pharo is smart smalltalk environment, and morphic designer is > useful(maybe.... only loook movie file) > > > but use not easy! because squeak and pharo is not same. > ok i can try. > > i make a this guide. > Morphic Designer in Pharo2-writeen korean. > > http://workspace.onionmixer.net/mediawiki/index.php?title=Morphic_Designer_… > > > > now i can run in pharo. but encounterd error in playtime. > > look this section please. > > http://workspace.onionmixer.net/mediawiki/index.php?title=Morphic_Designer_… > > > start drag item but rise debug error. > debugger display "positionInWord" is nil. > > > no idea, i cannot even find any references (senders/implementors) to #positionInWord in my pharo image (though it is 3.0 one). > i misssion way for solution. > where look then can find way to answer? > > i guess you better contact with authors/developers of Morphic Designer project. > you can then little hint give to me please. > > My little hint: 1. read code 2. try to understand what's wrong 3. contact authors of code for help 4. try to fix it 5. if nothing helps, repeat from step 1. :) > thank you...T.T > > > -- > http://onionmixer.net | http://gentoo.or.kr | http://gnome.or.kr > peter yoo. ROK > -- Best regards, Igor Stasenko.

Dec. 20, 2013

have a question for morphic Designer in pharo.

by peter yoo

hello smalltalker! this is my first thread. first! im smalltalk newbie and use ogly english. sorry!!! i want using "Morphic Designer" in pharo. because pharo is smart smalltalk environment, and morphic designer is useful(maybe.... only loook movie file) but use not easy! because squeak and pharo is not same. ok i can try. i make a this guide. Morphic Designer in Pharo2-writeen korean. http://workspace.onionmixer.net/mediawiki/index.php?title=Morphic_Designer_… now i can run in pharo. but encounterd error in playtime. look this section please. http://workspace.onionmixer.net/mediawiki/index.php?title=Morphic_Designer_… start drag item but rise debug error. debugger display "positionInWord" is nil. i misssion way for solution. where look then can find way to answer? you can then little hint give to me please. thank you...T.T -- http://onionmixer.net | http://gentoo.or.kr | http://gnome.or.kr peter yoo. ROK

Dec. 20, 2013

Re: [Pharo-users] Roassal3D : MessageNotUnderstood:NBMSAAOffscreenDisplay

by Volkert Barr

Ok. i loaded it into the latest Pharo 3.0 (Latest update: #30654) and it looks good so far. I still have problems with the "3D IDE" menu (the windows are now empty), but the examples from the tutorial and the R3Example class i have tested are working fine. I give you more feedback tomorrow, when i have completed the tutorial. Cool stuff !!! BW, Volkert On 19.12.2013, at 20:05, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Dear Volkert, > > I just updated the configuration of Roassal 3D for it to load the baseline version of NBOpenGL, with the changes made. Its currently only been tested under Linux, so any feedback its appreciated. > > Greetings, > Ronie Salgado > > > 2013/12/19 Volkert Barr <volkert(a)nivoba.de> > Dear Ronie, > > i had no success with older versions. Please give my a short note, when the "configuration browser way" works again. > > BW, > Volkert > > On 15.12.2013, at 00:30, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > > Hello, > > > > Try with version 118, from Monticello. > > That problem is produced because I had to made some changes to NBOpenGL, for which I don't have commit privileges so I posted them on the pharo-dev mailing list. > > > > Greetings, > > Ronie Salgado > > > > > > 2013/12/14 Volkert Barr <volkert(a)nivoba.de> > > Hello, > > > > i loaded Roassal3D from the Configuration Browser into a fresh Pharo 3.0 Image. When selecting "3D IDE" (Roassal3D Easel??) from > > the tools-menu i got to the following error: MessageNotUnderstood:NBMSAAOffscreenDisplay>>bindFramebuffer. > > > > Probably i forgot to load some other base packages. > > > > Pharo3.0 > > Latest update: #30644 > > Host: OS X 10.8.5 > > > > Any hints? > > Volkert > > > > <PastedGraphic-1.tiff> > > > > -- > www.nivoba.de > > "The more complex an object, the larger the investment in learning to use it, and the greater the resistance to abandon it." > > > -- www.nivoba.de "The more complex an object, the larger the investment in learning to use it, and the greater the resistance to abandon it."

Dec. 19, 2013

Re: [Pharo-users] Roassal3D : MessageNotUnderstood:NBMSAAOffscreenDisplay

by Ronie Salgado

Dear Volkert, I just updated the configuration of Roassal 3D for it to load the baseline version of NBOpenGL, with the changes made. Its currently only been tested under Linux, so any feedback its appreciated. Greetings, Ronie Salgado 2013/12/19 Volkert Barr <volkert(a)nivoba.de> > Dear Ronie, > > i had no success with older versions. Please give my a short note, when > the "configuration browser way" works again. > > BW, > Volkert > > On 15.12.2013, at 00:30, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > > Hello, > > > > Try with version 118, from Monticello. > > That problem is produced because I had to made some changes to NBOpenGL, > for which I don't have commit privileges so I posted them on the pharo-dev > mailing list. > > > > Greetings, > > Ronie Salgado > > > > > > 2013/12/14 Volkert Barr <volkert(a)nivoba.de> > > Hello, > > > > i loaded Roassal3D from the Configuration Browser into a fresh Pharo 3.0 > Image. When selecting "3D IDE" (Roassal3D Easel??) from > > the tools-menu i got to the following error: > MessageNotUnderstood:NBMSAAOffscreenDisplay>>bindFramebuffer. > > > > Probably i forgot to load some other base packages. > > > > Pharo3.0 > > Latest update: #30644 > > Host: OS X 10.8.5 > > > > Any hints? > > Volkert > > > > <PastedGraphic-1.tiff> > > > > -- > www.nivoba.de > > "The more complex an object, the larger the investment in learning to use > it, and the greater the resistance to abandon it." > > >

Dec. 19, 2013

Re: [Pharo-users] Roassal3D : MessageNotUnderstood:NBMSAAOffscreenDisplay

by Volkert Barr

Dear Ronie, i had no success with older versions. Please give my a short note, when the "configuration browser way" works again. BW, Volkert On 15.12.2013, at 00:30, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Hello, > > Try with version 118, from Monticello. > That problem is produced because I had to made some changes to NBOpenGL, for which I don't have commit privileges so I posted them on the pharo-dev mailing list. > > Greetings, > Ronie Salgado > > > 2013/12/14 Volkert Barr <volkert(a)nivoba.de> > Hello, > > i loaded Roassal3D from the Configuration Browser into a fresh Pharo 3.0 Image. When selecting "3D IDE" (Roassal3D Easel??) from > the tools-menu i got to the following error: MessageNotUnderstood:NBMSAAOffscreenDisplay>>bindFramebuffer. > > Probably i forgot to load some other base packages. > > Pharo3.0 > Latest update: #30644 > Host: OS X 10.8.5 > > Any hints? > Volkert > > <PastedGraphic-1.tiff> > -- www.nivoba.de "The more complex an object, the larger the investment in learning to use it, and the greater the resistance to abandon it."

Dec. 19, 2013

Re: [Pharo-users] Writing an IRC bot

by kilon alios

*" I was considering using ChromiaXXX as a prefix instead.* *The problem with xxxUser is that right now I manage two "User" concepts: what NickServ understands as a user, and what Chromia understands as a User, both of them different from an "IRC User" understood as someone or something who is connected to IRC. ThatÂ´s what I meant by not enough meaning"* Make a User master class, subclass for IRC and Chromia. Dont use long names for what you can subclass, dont use long names for what you can document or add a class comment about. *" I see. I was thinking about how less classes make a system simpler and that I should remove it because the functionality is identical to that of a Dictionary. But as you point out, the dilemma can also be solved by adding new behaviour :) "* Less classes mean more methods. Nope definitely not good. Protocols tend to fix the mess of having too many methods in a class (see Morph class and scream in horror) but I prefer more classes and less methods. This way its more clear what you trying to do with the code. Of course still you need class comments but of course you already know that ;) >> > > > > > - IRCConfiguration could be replaced by a dictionary since itÂ´s nothing >> more >> > than a bunch of data. But the, on the other hand, it could encapsulate >> > validation on the settings to say something. >> >> I'm not sure what would be the gain of transforming a proper class >> into a dictionary. We usually do the opposite : creating classes out >> of collection usage. I would keep the class and give it a >> responsibility. >> > > > > >> > - Is PetitParser overkill for the time of parsing required? Are regular >> > expressions a better fit for this task? >> >> I don't know what parsing is required. But if it works, I would keep >> it the way it is. >> > > There are two scenarios, one is parsing incoming messages from the server > (I haven't considered DCC yet), which are in "IRC message format", > documented in RFCs. I built the parser for it by translating parts of the > BNF grammar into PetitParser. > > The other one is parsing the message that a user types in the client as a > command to to the bot, for example "!sayto #pharo Hello, my name is > Chromia". Right now, I do that using regular expressions. > > > >> > - Do I keep the Glamour browsers? IÂ´m rather partial to them :D >> >> Glamour is really great to write interfaces and I really like it. Now, >> if you develop a browser on top of glamour, you also need the moldable >> glamour debugger. >> > > More stuff to learn! \o/ > > > Cheers, > Sergi >

Dec. 19, 2013

Re: [Pharo-users] Writing an IRC bot

by StÃ©phane Ducasse

On 19 Dec 2013, at 10:37, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > 2013/12/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > what would be fun is to see if we can build a little tutorial that show to newbies how to write a simple IRC bot. > > You mean how to write a bot with Chromia? originally I thought how to write an irc bot ? > Would you be interested to work on that? > Because I would love that my son is able to build one with Pharo. > > I would like to at least make the code a bit more modular/less network-centric first. That said, I will see if I can find time to write something that resembles a tutorial these holidays. I would love to review it. > > Cheers, > Sergi >

Dec. 19, 2013

Re: [Pharo-users] Writing an IRC bot

by Sergi Reyner

2013/12/19 Damien Cassou <damien.cassou(a)gmail.com> > On Thu, Dec 19, 2013 at 11:07 AM, Sergi Reyner <sergi.reyner(a)gmail.com> > wrote: > > - Class names are awfully chosen. Besides almost every one of them having > > IRC as a "namespace" prefix, some like IRCUser donÂ´t convey enough > meaning. > > having a prefix is a common pattern. I don't see the problem of > IRCUser as a name. > I was considering using ChromiaXXX as a prefix instead. The problem with xxxUser is that right now I manage two "User" concepts: what NickServ understands as a user, and what Chromia understands as a User, both of them different from an "IRC User" understood as someone or something who is connected to IRC. ThatÂ´s what I meant by not enough meaning > - IRCConfiguration could be replaced by a dictionary since itÂ´s nothing > more > > than a bunch of data. But the, on the other hand, it could encapsulate > > validation on the settings to say something. > > I'm not sure what would be the gain of transforming a proper class > into a dictionary. We usually do the opposite : creating classes out > of collection usage. I would keep the class and give it a > responsibility. > I see. I was thinking about how less classes make a system simpler and that I should remove it because the functionality is identical to that of a Dictionary. But as you point out, the dilemma can also be solved by adding new behaviour :) > > - Is PetitParser overkill for the time of parsing required? Are regular > > expressions a better fit for this task? > > I don't know what parsing is required. But if it works, I would keep > it the way it is. > There are two scenarios, one is parsing incoming messages from the server (I haven't considered DCC yet), which are in "IRC message format", documented in RFCs. I built the parser for it by translating parts of the BNF grammar into PetitParser. The other one is parsing the message that a user types in the client as a command to to the bot, for example "!sayto #pharo Hello, my name is Chromia". Right now, I do that using regular expressions. > > - Do I keep the Glamour browsers? IÂ´m rather partial to them :D > > Glamour is really great to write interfaces and I really like it. Now, > if you develop a browser on top of glamour, you also need the moldable > glamour debugger. > More stuff to learn! \o/ Cheers, Sergi

Dec. 19, 2013

Re: [Pharo-users] Writing an IRC bot

by Damien Cassou

On Thu, Dec 19, 2013 at 11:07 AM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > - Class names are awfully chosen. Besides almost every one of them having > IRC as a "namespace" prefix, some like IRCUser donÂ´t convey enough meaning. having a prefix is a common pattern. I don't see the problem of IRCUser as a name. > - IRCConfiguration could be replaced by a dictionary since itÂ´s nothing more > than a bunch of data. But the, on the other hand, it could encapsulate > validation on the settings to say something. I'm not sure what would be the gain of transforming a proper class into a dictionary. We usually do the opposite : creating classes out of collection usage. I would keep the class and give it a responsibility. > - Is PetitParser overkill for the time of parsing required? Are regular > expressions a better fit for this task? I don't know what parsing is required. But if it works, I would keep it the way it is. > - Do I keep the Glamour browsers? IÂ´m rather partial to them :D Glamour is really great to write interfaces and I really like it. Now, if you develop a browser on top of glamour, you also need the moldable glamour debugger. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Dec. 19, 2013

Re: [Pharo-users] Writing an IRC bot

by Sergi Reyner

2013/12/19 Damien Cassou <damien.cassou(a)gmail.com> > > On Thu, Dec 19, 2013 at 10:37 AM, Sergi Reyner <sergi.reyner(a)gmail.com>wrote: > >> You mean how to write a bot with Chromia? > > > If you do it with Chromia, many details (such as network stuffs I guess) > won't be shown. But this gives you the possibility to implement a great bot. > > If you do it without Chromia, you can show all the details so that the > reader learns a lot of Pharo. > ThatÂ´s precisely why I asked, and why I said that first IÂ´d like to modularise it as I mentioned in my original mail. That way I can first explain how the framework is built, so I can transmit the benefits of building it this way instead of mashing it up all together (which is how I began :D). Then I can explain how to use that framework to write your own bot, which again makes the benefits stand out. At the moment IÂ´m going over some decisions that I feel can be improved. >From the top of my head: - Class names are awfully chosen. Besides almost every one of them having IRC as a "namespace" prefix, some like IRCUser donÂ´t convey enough meaning. - IRCConfiguration could be replaced by a dictionary since itÂ´s nothing more than a bunch of data. But the, on the other hand, it could encapsulate validation on the settings to say something. - Is PetitParser overkill for the time of parsing required? Are regular expressions a better fit for this task? - Do I keep the Glamour browsers? IÂ´m rather partial to them :D Both are fine I would say. If you decide to write a tutorial, we could > integrate it in the next book: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > Oh. Wow. Cheers, Sergi

Dec. 19, 2013