March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo consultants

by Sebastian Sastre

That would be awesome. Glad to hear about an initiative to make things sustainable. A catalog of people who works using it would be great. No need to be a social network site, just a catalog for people to navigate who's working with it. Plus a subscribe/login for everyone manage its own profile so consultants can set a photo some bio and its portfolio Everybody could endorse skills or write reviews I know I know... Linked In already kind of does that, but that's not the point The point is that we have our little proprietary thing focused on Pharo and endorsed by Pharo itself If I would have available time I would make flowing itself to sponsor with developing such a site/extension to current pharo site sebastian o/ On Mar 8, 2013, at 6:05 PM, StÃ©phane Ducasse wrote: > Hi guys > > I just got a nice chat with a cool Pharo expert (Mariano) that is doing consulting and development around Pharo and this is a cool feeling to know that smart guys in our community can find nice jobs that keeps them busy in Pharo. > I think that we should market the community much more, because I think that this is important for other companies > to know that they can find help with really talented people in our community. > May be we should make more noise around: > Pharo: a community with smart developers for cool business > > Stef > > > > >

March 9, 2013

[Pharo-project] fogbugz entries

by Camillo Bruni

I wanted to have a look at the new fogbugz entries. But when I list all active entries, I have quite a lot of entries with "Closed (Active)", any clue what that means?

March 9, 2013

Re: [Pharo-project] building traits programmatically

by Ciprian Teodorov

On Sat, Mar 9, 2013 at 4:00 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > how to create trait programmatically? > > Here you go: > > trait := Trait named: #MyProgrammaticallyCreatedTrait. > > > You can also do the same trick with classes, btw: > > newclass := Object subclass: #MyNewClass. > > ;) > > cool... ;) +igor but then why do we need changes and change classes ? but yeah I asked a stupid question [?]... the DNU is still there though > -- > Best regards, > Igor Stasenko. > > -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

March 9, 2013

Re: [Pharo-project] building traits programmatically

by Igor Stasenko

how to create trait programmatically? Here you go: trait := Trait named: #MyProgrammaticallyCreatedTrait. You can also do the same trick with classes, btw: newclass := Object subclass: #MyNewClass. ;) -- Best regards, Igor Stasenko.

March 9, 2013

Re: [Pharo-project] Pharo Command Line

by Igor Stasenko

@Stef in the attached.. conclusion seems highly unrelated to zero conf :) On 8 March 2013 22:14, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Because in Pharo we are doing more than talking and we value documentation â¦â¦ > Yes guys you can twitt that one! > > :) > > > > > > > > On Mar 8, 2013, at 2:50 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Sven wrote: >>> The last couple of days I have been using the new command line tools and zero conf scripts for real and I must say that I am >truly impressed and happy. >>> >>> The save, printVersion, eval, st, config and test handlers are a joy to work with. The terminal colours add a nice polish. >> >> Any documentation on it, blog posts or pharocasts available? >> >> Thx >> Torsten >> >> >> > > -- Best regards, Igor Stasenko.

March 9, 2013

Re: [Pharo-project] Pharo Command Line

by Camillo Bruni

On 2013-03-09, at 13:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > On Mar 9, 2013, at 12:49 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> On 2013-03-08, at 22:14, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Because in Pharo we are doing more than talking and we value documentation â¦â¦ >>> Yes guys you can twitt that one! >> >> thanks stef. >> >> though something to nag about... :P why is code not in a fixed-width font in the >> pdf? :D It breaks all the formatting for the help comments. > > > Because I ***HATE*** \tt in pdf because it slows reading :) > This is like that in all the books I wrote. it's called source code, not english prose text or a roman. and in this particular case you broke readability 100% because my help output was aligned.

March 9, 2013

Re: [Pharo-project] [Pharo-users] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

by Janko MivÅ¡ek

Hi Stef, Post on the mailing list for each project idea by following this template: Level: (beginner, intermediate, advanced) Possible mentor: Possible second mentor: Description Technical Details Benefits to the Student Benefits to the Community Best regards Janko Dne 09. 03. 2013 13:46, piÅ¡e stephane ducasse: > Hi janko > > How do you want to proceed for the topics? > I have a list of topics now where do we write them. > > - tool support rewrite rules > - new generation debugger > - new change model and session manager (with martin dias) > - improving roassal (with alexandre bergel et vanessa pena) > - improving eyesee (with alexandre bergel et vanessa pena) > - support touch event > - UIPainter (with esteban lorenzano) > - New widgets > > > Stef > > >> Dear Smalltalkers, >> >> Time for your cool project ideas on this year Smalltalk GSoC! >> >> 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. Deadline is end of Mart, so we have three weeks of time. >> To see how fully developed ideas look like please look at 2012 ones at: >> http://gsoc2012.esug.org/ideas. >> >> 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. Last year 6 student proposed projects >> were accepted and finished successfully! >> >> 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. >> >> We are namely preparing an application to this year Smalltalk Google >> Summer of Code under ESUG umbrella, as last year. If accepted, Google >> will pay few stipendiums to students on our Smalltalk projects. >> >> More on our special Smalltalk GSoC 2013 website: >> >> http://gsoc2013.esug.org >> >> I'm specially inviting mentors of all past GSoCs to 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 >> Aida/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 9, 2013

Re: [Pharo-project] Pharo Command Line

by stephane ducasse

On Mar 9, 2013, at 12:49 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-08, at 22:14, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Because in Pharo we are doing more than talking and we value documentation â¦â¦ >> Yes guys you can twitt that one! > > thanks stef. > > though something to nag about... :P why is code not in a fixed-width font in the > pdf? :D It breaks all the formatting for the help comments. Because I ***HATE*** \tt in pdf because it slows reading :) This is like that in all the books I wrote. Stef

March 9, 2013

Re: [Pharo-project] building traits programmatically

by stephane ducasse

On Mar 8, 2013, at 11:50 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > > > On Fri, Mar 8, 2013 at 10:32 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On Mar 8, 2013, at 7:57 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > >> Hi guys, >> >> Can anyone give me some pointers on how to create traits dynamically? > > you mean with the refactoring engine? > Yes something like it, I am little confused with all ring, rb stuff. ring is simple: imagine that all the tools can manipulate objects that represent objects that get executed. for RB you have an engine to transform code. Now to programmatically create traits you do not need RB nor ring > But I know that I can build classes, add methods, and see changes (and apply them) using RBNamespace api... it does not seem to work with traits. Some time ago I have spend some time patching the RB thingy to accept trait also... but then I have run into other problems (i don't remember exactly what)... Moreover, it was just hacks to make it work... so I've lost them over time... and I don't like patching every new image that I download with my changes to make It work... > > So maybe, I don't use them right... or there are things that should be done... I'm willing to contribute, if it helps. looking a the enhancements proposed to make rb handle traits would be good > > I know that one argentinian student added support for traits in RB but I never got the time to have a look and integrate it. > cool, maybe we should have a look... > > Then again, it is not clear in my head what is the politics of traits and pharo... I know that there were some discussions about them being bad because their methods are copied to classes, not being well integratedâ¦. it was just for implementors. > how exactly do they fit in the big picture (next pharo versions). Can we use them as they are now, or the implementation is likely to change in the near future? -- stateful traits, or something else? No stateful traits in the horizon. For now traits will stay but we should have a look at the internal implementation to simplify it. Second the internal change should not impact external users and will be transparent. > > cheers, > ciprian > > >> I have tried something like: >> >> model := RBNamespace new. >> >> model defineClass: ('Trait named: #TMyTrait >> uses: {} >> category: ''My-Tests'''). >> >> and I get a DNU: RBAddTraitChange>>superclassName >> >> Cheers, >> -- >> Dr. Ciprian TEODOROV >> IngÃ©nieur DÃ©veloppement CAO >> >> tÃ©l : 06 08 54 73 48 >> mail : ciprian.teodorov(a)gmail.com >> www.teodorov.ro > > > > > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro

March 9, 2013

Re: [Pharo-project] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

by stephane ducasse

Hi janko How do you want to proceed for the topics? I have a list of topics now where do we write them. - tool support rewrite rules - new generation debugger - new change model and session manager (with martin dias) - improving roassal (with alexandre bergel et vanessa pena) - improving eyesee (with alexandre bergel et vanessa pena) - support touch event - UIPainter (with esteban lorenzano) - New widgets Stef > Dear Smalltalkers, > > Time for your cool project ideas on this year Smalltalk GSoC! > > 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. Deadline is end of Mart, so we have three weeks of time. > To see how fully developed ideas look like please look at 2012 ones at: > http://gsoc2012.esug.org/ideas. > > 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. Last year 6 student proposed projects > were accepted and finished successfully! > > 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. > > We are namely preparing an application to this year Smalltalk Google > Summer of Code under ESUG umbrella, as last year. If accepted, Google > will pay few stipendiums to students on our Smalltalk projects. > > More on our special Smalltalk GSoC 2013 website: > > http://gsoc2013.esug.org > > I'm specially inviting mentors of all past GSoCs to 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 > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

March 9, 2013