- Pharo-users - lists.pharo.org

Re: [Pharo-users] Xs&Os game

by ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½

Really appreciate your comments, they are very useful for me. I will do my best to make commits as soon as possible to fix problems that you pointed out. Plus I've learned so much from only one message! thx:) 2014-02-04 Damien Cassou <damien.cassou(a)gmail.com>: > > > Would you consider writing a tutorial on how to implement an Xs&Os game in > Pharo? > > After finishing this game completely (it will take a while), I have in plans to implement another game. Then, if I have enoug experience in pharo, I want to write 2 tutorials for both games. Mark

Feb. 4, 2014

Re: [Pharo-users] Xs&Os game

by Damien Cassou

On Mon, Feb 3, 2014 at 11:39 AM, ÐÐ°ÑÐºÑÑÐ½ Ð ÑÐ·ÑÐ½ <mrizun(a)gmail.com> wrote: > As a novice in pharo, waiting for comments and advice. > Ð¡ritique is welcome too ;) > random comments (tested on Pharo 3.0): - I played and things work perfectly as far as I saw :-) - your code is of very good quality! - 2 tests don't pass (EmptyCellTestCase, CellRendererTestCase) - usually we don't append 'Case' at the end of our test classes - the package name doesn't follow the convention ( https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Convent… ) - you may want to avoid the use of non-alphanumeric characters in the package name (e.g., avoid &) - please indent your code (use ALT+Shift+u on each method to get automatic indentation) - "self should: [ offset = (50 @ 50) ]" --> "self assert: offset equals: 50@50" - "self should: [ cell isOff ]." --> "self assert: cell isOff" - all subclasses of Cell override #initialize in exactly the same way. Consider moving that to the superclass - you should try to avoid as much as possible doing a super send in a different method. For example, EmptyCell>>initializeState does a super send on #initialize. - OCell and XCell are exactly the same, this should not be and is very suspicious. - CellRenderer has 2 methods with an uppercase letter. This is not conventional - you use a lot of variables you use only once. Consider inlining them. For example in CellRenderer>>offsetWithinGridForm, all variables seem useless : "^ CellRenderer cellExtent * ((self cellLocation x - 1) @ (self cellLocation y - 1))" - CellRenderer>>renderContents uses branching on the class of objects instead of polymorphism. That's bad design in my opinion. Consider delegating to OCell and XCell or using double-dispatch. - Same thing for CellRenderer class>>rendererFor: All in all, very good job. Would you consider writing a tutorial on how to implement an Xs&Os game in Pharo? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by Stephan Eggermont

Configuration sanity checker. Load all ConfigurationOfs and check if dependencies are missing or conflicting. By checking monticello files, the introduction moment and interface changes of classes are known, so a range of possible version combinations can be generated. See DeprecationFinder for some sample code. Distributed Issue Tracker, see LightHouse. New widget set, for use with Spec & Glamour. Needs a designer too. Stephan

Feb. 4, 2014

Re: [Pharo-users] [Pharo-dev] Pharo Success Story: Reflex Vacances

by btc＠openinworld.com

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by Goubier Thierry

Le 04/02/2014 14:34, Sven Van Caekenberghe a Ã©crit : > > On 04 Feb 2014, at 14:31, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > >> * An interface to manage Smalltalk source code in GIT with tools for merging etc. - with Portability as a primary design goal (Cypress sure is the place to start from) > > That already exists, in Thierry's work, right ? He recently posted about this... I have the base git support... I carefully avoided the "tools for merging" part :P Anybody who has done merges with git, especially on Monticello packages under filetree format, will understand why :( (I tend to merge under Monticello and recommit instead. Works very well, but doesn't register as a merge for git. It's something I'd like to solve eventually, one day...) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by Sven Van Caekenberghe

On 04 Feb 2014, at 14:31, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > * An interface to manage Smalltalk source code in GIT with tools for merging etc. - with Portability as a primary design goal (Cypress sure is the place to start from) That already exists, in Thierry's work, right ? He recently posted about this...

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by Joachim Tuchel

* An interface to manage Smalltalk source code in GIT with tools for merging etc. - with Portability as a primary design goal (Cypress sure is the place to start from) * Tools to handle non-Smalltalk artefacts from within the Smalltalk IDE (JavaScript, XML, CSS, HTML, JSON) with an integration to the before-mentioned project idea - a portable kernel for handling this external stuff plus an API to put tools on top of it Joachim > btc(a)openinworld.com hat am 4. Februar 2014 um 14:01 geschrieben: > > > > * Inboxes on SmalltalkHub projects > * Smalltalk based issue tracker. Maybe integrated with SmalltalkHub. > Maybe project [1] from last year, although it seems quite a lot to it. > btw, after getting through the troubles getting a login, I find I quite > like Fogbugz. > > [1] http://gsoc2013.esug.org/projects/distributed-issue-tracker > > cheers -ben > > Janko MivÅ¡ek wrote: > > Dear Smalltalkers, > > > > Tenth GSoC is here and application deadline is earlier this year, > > already next Friday! > > > > Time therefore for your cool project ideas on this year Smalltalk GSoC > > Hurry up! > > > > For now just express any idea you have here on the mailing list. Later > > we will together develop it to be in complete format together with two > > mentors needed. To see how fully developed ideas look like please look > > at 2012 ones at:http://gsoc2013.esug.org/ideas. > > > > Ideally (but not necessary right now) you should prepare an idea > > following this template: > > > > ----------------------------------------------- > > > > Title: > > > > Level: (beginner, intermediate, advanced) > > > > Possible mentor: (can be assigned later) > > > > Possible second mentor: (can be assigned later) > > > > Description > > > > Technical Details > > > > Benefits to the Student > > > > Benefits to the Community > > > > ------------------------------------------------- > > > > Note also that students yourselves can propose a GSoC project. So if you > > like to be a student on this year GSoC and have a nice idea, don't be > > shy and propose it here! The community will listen you and guide to the > > really nicely proposed project. > > > > For the community, start looking around for students. Think about how to > > approach the universities near by you, do you know who to contact > > there, etc. > > > > Our special website is in preparation and will be online in few days. > > Official Google GSoC site is here: > > > > http://www.google-melange.com/gsoc/homepage/google/gsoc2014. > > > > Specially read carefully the FAQ: > > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20… > > > > Mentors of all past GSoCs please rejoin the mentors mailing list where > > we discuss all details about this year GSoC: > > > > http://groups.google.com/group/smalltalk-gsoc-mentors > > > > While students interested on GSoC please join a special Smalltalk GSoC > > mailing list for you: > > > > http://groups.google.com/group/smalltalk-gsoc-students > > > > Best regards > > Janko > > > > > > > >

Feb. 4, 2014

Re: [Pharo-users] Google Summer of Code is here, your ideas please!

by btc＠openinworld.com

* Inboxes on SmalltalkHub projects * Smalltalk based issue tracker. Maybe integrated with SmalltalkHub. Maybe project [1] from last year, although it seems quite a lot to it. btw, after getting through the troubles getting a login, I find I quite like Fogbugz. [1] http://gsoc2013.esug.org/projects/distributed-issue-tracker cheers -ben Janko MivÅ¡ek wrote: > Dear Smalltalkers, > > Tenth GSoC is here and application deadline is earlier this year, > already next Friday! > > Time therefore for your cool project ideas on this year Smalltalk GSoC > Hurry up! > > For now just express any idea you have here on the mailing list. Later > we will together develop it to be in complete format together with two > mentors needed. To see how fully developed ideas look like please look > at 2012 ones at:http://gsoc2013.esug.org/ideas. > > Ideally (but not necessary right now) you should prepare an idea > following this template: > > ----------------------------------------------- > > Title: > > Level: (beginner, intermediate, advanced) > > Possible mentor: (can be assigned later) > > Possible second mentor: (can be assigned later) > > Description > > Technical Details > > Benefits to the Student > > Benefits to the Community > > ------------------------------------------------- > > Note also that students yourselves can propose a GSoC project. So if you > like to be a student on this year GSoC and have a nice idea, don't be > shy and propose it here! The community will listen you and guide to the > really nicely proposed project. > > For the community, start looking around for students. Think about how to > approach the universities near by you, do you know who to contact > there, etc. > > Our special website is in preparation and will be online in few days. > Official Google GSoC site is here: > > http://www.google-melange.com/gsoc/homepage/google/gsoc2014. > > Specially read carefully the FAQ: > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20… > > Mentors of all past GSoCs please rejoin the mentors mailing list where > we discuss all details about this year GSoC: > > http://groups.google.com/group/smalltalk-gsoc-mentors > > While students interested on GSoC please join a special Smalltalk GSoC > mailing list for you: > > http://groups.google.com/group/smalltalk-gsoc-students > > Best regards > Janko > >

Feb. 4, 2014

Re: [Pharo-users] Could Pharo be more idiot-proof?

by PBK Research

Daniel Thanks for the comments. I have tried Prolog too, but didn't get very far. I am hoping to deal with pretty arbitrary inputs (typically news stories from internet newspapers etc), but initially just searching for key words and phrases. So far I have used PP to construct a pretty good tokeniser to identify words, sentences, punctuation etc, which was not very difficult. It may be that I won't get very far, but I'm retired and I do this for fun, so what the heck. Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Daniel Lyons Sent: 03 February 2014 18:52 To: Any question about pharo is welcome Subject: Re: [Pharo-users] Could Pharo be more idiot-proof? PBK Research writes: > As a supplementary point, I am trying to use PetitParser to parse > natural language. From the examples it is clear that PP is designed > with formal languages in mind. Am I wasting my time using it on > natural languages? Has anyone else tried this? What are you trying to do with natural language? Do you have highly regular input and a somewhat restricted domain? I have used Prolog DCGs to mess around with this kind of thing, and if you have a lot of control over the input and your expectations you can make progress with a tool for formal languages, but if you want to do something sophisticated or support arbitrary inputs, you're probably wasting your time. -- Daniel Lyons

Feb. 4, 2014

Google Summer of Code is here, your ideas please!

by Janko MivÅ¡ek

Dear Smalltalkers, Tenth GSoC is here and application deadline is earlier this year, already next Friday! Time therefore for your cool project ideas on this year Smalltalk GSoC Hurry up! For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. To see how fully developed ideas look like please look at 2012 ones at:http://gsoc2013.esug.org/ideas. Ideally (but not necessary right now) you should prepare an idea following this template: ----------------------------------------------- Title: Level: (beginner, intermediate, advanced) Possible mentor: (can be assigned later) Possible second mentor: (can be assigned later) Description Technical Details Benefits to the Student Benefits to the Community ------------------------------------------------- Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc. Our special website is in preparation and will be online in few days. Official Google GSoC site is here: http://www.google-melange.com/gsoc/homepage/google/gsoc2014. Specially read carefully the FAQ: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20… Mentors of all past GSoCs please rejoin the mentors mailing list where we discuss all details about this year GSoC: http://groups.google.com/group/smalltalk-gsoc-mentors While students interested on GSoC please join a special Smalltalk GSoC mailing list for you: http://groups.google.com/group/smalltalk-gsoc-students Best regards Janko -- Janko MivÅ¡ek Smalltalk GSoC Admin Team

Feb. 4, 2014