- Pharo-users - lists.pharo.org

Pharocasts: Document with HelpSystem
by laurent laffont Sept. 20, 2010

Sept. 20, 2010

You will learn how to: - write an HelpSystem book - use PackageAPIHelpBuilder to generate the API documentation of a package - create your own builder to dynamically create a documentation from the system Starting from now, no excuses to not write documentation ;) http://pharocasts.blogspot.com/2010/09/document-with-helpsystem.html Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

2 1

A point about pharo: the red line
by StÃ©phane Ducasse Sept. 18, 2010

Sept. 18, 2010

Hi pharoers We want to stress something that may seem obvious for us but that can may be not for you and that people attending ESUG could discover live :) lucky them :) But you will be able to watch the video and get an idea soon. What is important is that it can explain a lot of our actions and future actions. Here is a list of statements that I tried to make short. - We do pharo because we want to create an ecosystem for companies and research/innovation. - We don't do pharo for fame and fans else we would do ruby or hard-rock. :) (ok probably ruby) - We want to build a powerful open-source community. - Every single node in the community is important. So yes you doing your little project in your corner you are important. Why? Because a community is a synergetic beast and we are all cool because the community is cool. So you are also important to us. For example if you want to give a lecture on pharo, we can help. if you want to do presentations, we can help, if you have problems/ideas let us know. - Often we do actions not because we want credit but just because somebody has to do it: seaside book, esug are to other examples of why we did pharo. Because we need a power rocking hyper cool beautifully designed system. (I know some of you think that I'm lousy and I use too much cool but this is what I mean) - We believe in strong elegant beautiful infrastructure: fix the stuff so that you can go faster to build the next one. We did that with Moose: offer to software engineering researchers a foundation to focus on problems versus rebuilding each time a clean source code meta model and importer. Infrastructure will give us the leverage to build the next generation. Stef and other pharoers

1 0

Community in the IDE
by laurent laffont Sept. 17, 2010

Sept. 17, 2010

Hi, an idea I haven't found the courage to implement but may not be hard and can have an impact (at least fun to code). - Write / put a chat server on seasidehosting|INRIA|whatever - Pharo image includes a chat client per default - uses Author as nickname So as soon as we open an image we are connected to other users. Can be interesting in courses as students are directly connected to *real* developpers while learning (and students love to chat :). So we can exchange snippets instantly, ask questions, ... Someone ? Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

2 1

About pharo book localisation chapter.
by Panu Suominen Sept. 12, 2010

Sept. 12, 2010

In localisation chapter people are asked to reload their image to enable translations. I think that NaturalLanguageTranslator privateStartUp is enough. It might be worth to mention because it speeds up testing. -- Panu

1 0

Re: [Pharo-users] i18n tools
by Panu Suominen Sept. 10, 2010

Sept. 10, 2010

2010/9/10 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > Check with Philip Marchall, he did modification to use gettext code with > Seaside. Ok. Thanks to all for the help. Seaside and gettext are apparently the magic words that solves this problem. :) http://forum.world.st/Seaside-Gettext-sneak-peak-td2164600.html -- Panu

1 0

i18n tools
by Panu Suominen Sept. 10, 2010

Sept. 10, 2010

I am researching wether out team could start using Pharo. I have tried to locate some tools to do user interface translations but I did not find anything in time so I had to develop some rudimentary key-based translation tools my self. I would like to know is this lack of translation tools reality and if others are having same kind of problems? -- Panu

5 6

Re: [Pharo-users] i18n tools
by Panu Suominen Sept. 10, 2010

Sept. 10, 2010

2010/9/10 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > I don't understand what you want to do. > Have you read the localisation chapter I wrote in the Pharo Collaboactive > book? Ok. Now I managed to see the localisation page. Thank you for the tip. I try to integrate that to seaside. -- Panu

1 0

Re: [Pharo-users] i18n tools
by Panu Suominen Sept. 10, 2010

Sept. 10, 2010

2010/9/10 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > I don't understand what you want to do. I am researching a way to translate user interface in seaside application. I have tried to look for code to take care of translations but haven't found anything. > Have you read the localisation chapter I wrote in the Pharo Collaboactive > book? I did not know that there is such a chapter there. Is there a link to the book from pharo homepage? However, the book gives me an error: Seaside Walkback Error: subscript is out of bounds: 8218 -- Panu

1 0

Sept. 9, 2010

hi guys Since Opalers are working hard in the shadow, I thought that I can do a little digest for them. Each time I will delete ten entries I will do a small digest. Thanks marcus, Jorge and JB for their time and energy. Stef PS: OPAL is the new compiler framework we will have in 1.3. Really cool. OPAL comes from the Opal coast near to lille with cool dunes and birds. ==================== Summary ==================== Name: OpalCompiler-Core-MarcusDenker.33 Author: MarcusDenker Time: 9 September 2010, 8:12:20 pm UUID: beb4fce5-38ef-4ff1-ba41-924245ff6456 Ancestors: OpalCompiler-Core-MarcusDenker.32 - cleanups (unsent methods) - make sure to hand over array of copiedTemos to IRBuilder, not Set. final one for today... things start to work. Failing tests down to 24 (from 40). TestCoverage 81% ==================== Summary ==================== Name: OpalCompiler-Tests-MarcusDenker.29 Author: MarcusDenker Time: 9 September 2010, 7:47:08 pm UUID: aa19bd88-0895-4ab8-b55c-3f62f1698e33 Ancestors: OpalCompiler-Tests-MarcusDenker.28 - ASTChecker tests does not use verifyin, but just the ASTChecker - misc changes ==================== Summary ==================== Name: OpalCompiler-Core-MarcusDenker.32 Author: MarcusDenker Time: 9 September 2010, 7:46:21 pm UUID: 845092d2-e58f-441a-9304-43106311e5a1 Ancestors: OpalCompiler-Core-MarcusDenker.31 -> ASTTraslator now requests a tempVector from IRBuilder if needed -> simplified ASTClosureAnalyzer --> moved code to block/method scope -> tempVector now is not a temp anymore, just a copying one if needed -> verifyIn: now calls both visitors. ==================== Summary ==================== Name: OpalCompiler-Core-MarcusDenker.31 Author: MarcusDenker Time: 9 September 2010, 5:49:20 pm UUID: ab2dc77f-71b4-4f82-9cb4-4a2c1261e3fe Ancestors: OpalCompiler-Core-MarcusDenker.30 - simplify a bit re-lookup of variables in OCASTClosureAnalyzer - scopes now have a unique name after ASTChecker pass (this is then used as the name of the vector) ==================== Summary ==================== Name: OpalCompiler-Tests-MarcusDenker.28 Author: MarcusDenker Time: 9 September 2010, 5:49:34 pm UUID: 4821aa22-5ca5-4973-9c18-df0b1bb0297f Ancestors: OpalCompiler-Tests-MarcusDenker.27 more tests... ==================== Summary ==================== Name: OpalCompiler-Tests-MarcusDenker.27 Author: MarcusDenker Time: 9 September 2010, 5:09:43 pm UUID: 49dfe8ab-d8af-4b61-9bcc-066fcf7e5aa0 Ancestors: OpalCompiler-Tests-JorgeRessia.26 fix tests... ==================== Summary ==================== Name: OpalCompiler-Core-MarcusDenker.30 Author: MarcusDenker Time: 9 September 2010, 5:09:27 pm UUID: 2485ef0c-25fe-4863-bd49-fad1aaa0f8bc Ancestors: OpalCompiler-Core-jb.29, OpalCompiler-Core-JorgeRessia.29 more work for scope analysis... -> after variables are re-looked up, add copying temps to outer scop -> Fixes ==================== Summary ==================== Name: OpalCompiler-Tests-JorgeRessia.26 Author: JorgeRessia Time: 7 September 2010, 9:29:08 pm UUID: 4def3fb1-2057-45fe-b7f7-62f057c999fb Ancestors: OpalCompiler-Tests-MarcusDenker.25 - Introduction of optimized block scopes. - the closure analysis is been moved out of the astchecker ==================== Summary ==================== Name: OpalCompiler-Core-JorgeRessia.29 Author: JorgeRessia Time: 7 September 2010, 9:28:46 pm UUID: 02e0a230-43fb-4c08-97f2-a767968faaf8 Ancestors: OpalCompiler-Core-MarcusDenker.28 - Introduction of optimized block scopes. - the closure analysis is been moved out of the astchecker ==================== Summary ==================== Name: OpalCompiler-Core-jb.29 Author: jb Time: 7 September 2010, 11:31:01 am UUID: 06331cc1-732f-4e49-8327-1d6eef92bf26 Ancestors: OpalCompiler-Core-MarcusDenker.28 Fix some bug about Jump in decompiler and clean a bit the code.

2 1

Sept. 8, 2010

Hi Pharoers, lurkers, users We repeat all over the same: we welcome you to participate and while we are cool and welcoming, you feel "oh I cannot, I do not know, this is complex..." You look at us like Gurus, but let us be clear, we are not, we are just common people that have a debugger, kids in the bed and good music in the background (for me Cool Jazz or Thrash Metal). Of course some parts of the system are ugly, buggy, britlle, messy... but less and less, more and more good abstractions are taking life AND!!!! First, we are all learners and newbie on something (at least the mortal among us) but to learn we should start somewhere Second, start small - we tag some bug entries as easy, give a try. - put a break point in the code - write a test - do something fun You will not fail, why? because either you do not find anything and there is no problem but you will learn something and you can pass to the next one. Or you find something and you got it :) We did that with marcus when we were squeak harvesters. There were a lot of things we could not get but we pass to the next. :) Now I browse bugs bugs and bugs and I can tell you that 85% of the bugs are terribly stupid. Even more. So focus on these ones :) Pharo is the system we (you and us) will build. Stef

1 0