August 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Slice loading/merging differences question

by Tim Mackinnon

stepharo wrote > When we integrate changes we systematically merge so that even if you > did a fix on a not recent version we get both improvements. Stef - just to check on this, in the case of fogbugz 13526 - if you just merge, you don't pick up the requirement to load fogbugz 13787? So how do the dependencies work with merging? Am I right in thinking that using "Load" - MC uses the dependency information encoded to actually load 13787 as well? When I merged manually in a clean image - I didn't get that dependency (and only spotted it because Damien had mentioned it in the bug text, although I've now noticed it does seem to be encoded in the slice somehow?). This is the bit that is eluding me? Tim -- View this message in context: http://forum.world.st/Slice-loading-merging-differences-question-tp4772352p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 8, 2014

Re: [Pharo-users] Slice loading/merging differences question

by Ben Coman

Aug. 8, 2014

Re: [Pharo-users] Two Questions from a Newbie

by Ben Coman

Aug. 8, 2014

Re: [Pharo-users] Versionner and issue tracking

by Sean P. DeNigris

Evan Donahue wrote > everything works :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-and-issue-tracking-tp4772087p4772405.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 8, 2014

Re: [Pharo-users] Two Questions from a Newbie

by Hilaire

Le 08/08/2014 04:31, stepharo a Ã©crit : >> This is also a major drawback for a newcomer to pharo. A >> very thick entry barrier. > Yes we know it and I'm sad as you but you know if people building > frameworks do not document them then it is more difficult for other to > do it. > Did you check Pharo for the Entreprise because we are writing many > chapters on frameworks. > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > Steph, may be you could mention Pillar this new interesting way of documentation online about Pharo core and external package. Hope I understood correctly what is Pillar. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Aug. 8, 2014

Re: [Pharo-users] Two Questions from a Newbie

by kilon alios

Fortunately Smalltalk is a never ending journey into the land of weirdness and Pharo is its champion. Pharo is by far the most actively developed open source Smalltalk out there. Most likely more actively developed than the commercial ones too. So the overlap is pretty minimum actually. Smalltalk is not a programming language. Its a live coding environment that has also a very minimalistic language. Yeap documentation is a big problem in Pharo. I was complaining about it a few days ago. However people here are very helpful and very friendly to newcomers (unlike other programming languages ) and stackoverflow questions never go unanswered so you are not alone and people can help a lot. So its not that bad. Also there is already a lot of documentation about Pharo. Pharo for The Enterprise , Pharo By Example and Deep Into Pharo should keep you occupied for months if not years. As a newcomer its important to keep an open mind, Pharo is actually easy to learn but unlike other programming languages is not the same thing repackaged diffirently . Its quite diffirent actually and I think that is what makes it so productive and fun. In any case the secret of learning is very simple ... ask and you shall receive ;) Oh and welcome to Pharo .And remember if you are not having fun then its a Pharo bug and you should report it ;D On Thu, Aug 7, 2014 at 10:56 PM, Ichiseki <is076(a)outlook.com> wrote: > Konnichiwa > First thanks to those that gave me some directions to start with Pharo / > Smalltalk. > Now I have some questions that I'm sure are very stupid. > The first one is, is there a way to use the bouncing atoms and the lights > on > on Pharo 3? Because I tried to build it in there and it doesn't work > The second one is why there are like three different smalltalk > environments? > Pharo Squeek and Cuis? What are the differences? Is there a standard? I > find > this extremelly intriguing as it seems like there is a lot of dupplicate > effort? > The third one is which is the line between the core language and frameworks > and libraries in Pharo? > I found that, for instance Cuis has something like a basic image and some > external frameworks, pharo has some internal frameworks and lots of > externals. This is weird from someone comming from other languages. > The fourth is I found that documentation is very, very scarce especially > for > some frameworks. This is also a major drawback for a newcomer to pharo. A > very thick entry barrier. > > Thank you > Ichiro > > > > > -- > View this message in context: > http://forum.world.st/Two-Questions-from-a-Newbie-tp4772384.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014

Re: [Pharo-users] Two Questions from a Newbie

by stepharo

On 7/8/14 21:56, Ichiseki wrote: > Konnichiwa > First thanks to those that gave me some directions to start with Pharo / > Smalltalk. Welcome!!! > Now I have some questions that I'm sure are very stupid. There are no stupid questions :) Feel free to ask any questions you want. > The first one is, is there a way to use the bouncing atoms and the lights on > on Pharo 3? LightOn should work as described step by step in the Pharo by example book. What is not working. Do you have the code somewhere? > Because I tried to build it in there and it doesn't work > The second one is why there are like three different smalltalk environments? > Pharo Squeek and Cuis? What are the differences? Is there a standard? No > I find > this extremelly intriguing as it seems like there is a lot of dupplicate > effort? Indeed we created Pharo when we could not change anything in Squeak (and it was a hard decision) and after Squeak started to move a bit. Cuis is the work on Juan Vuletich. The goal of Pharo is to rethink Smalltalk and create a language inspired by Smalltalk but not bound to it. The goal of Pharo is also to make sure people can make money with it. > The third one is which is the line between the core language and frameworks > and libraries in Pharo? Usually frameworks are loaded on top. Now the core is what is needed. > I found that, for instance Cuis has something like a basic image and some > external frameworks, pharo has some internal frameworks and lots of > externals. Pharo has a "minimal" image, and framework loaded and libraries that you can load. We are in the process to have a really modular system and one of our goal is to be able to create minimal images from scratch and create different images based on what people need. Now this is not easy to manage because if you get a fix for one part how do you propagate it to the other users. But we are getting there. > This is weird from someone comming from other languages. Why Java has a core and libraries too and we are getting there too. For Pharo we are about to bootstrap a kernel (get a textual description and a process and create core containing small working core). > The fourth is I found that documentation is very, very scarce especially for > some frameworks. Like what? > This is also a major drawback for a newcomer to pharo. A > very thick entry barrier. Yes we know it and I'm sad as you but you know if people building frameworks do not document them then it is more difficult for other to do it. Did you check Pharo for the Entreprise because we are writing many chapters on frameworks. https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > > Thank you > Ichiro > > > > > -- > View this message in context: http://forum.world.st/Two-Questions-from-a-Newbie-tp4772384.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014

Re: [Pharo-users] [Moose-dev] Re: Tree/Outliners of playgrounds, markdown inside comments and some quick medium size dreams for Pharo/Smalltalk

by Offray Vladimir Luna CÃ¡rdenas

Hi Doru and Community :-), In the screenshot at [1] you can see my explorations. I took the code from treeWithChildrenByeLevel in the GLMBasicExamples and modified it until I got this: [1] http://www.enlightenment.org/ss/e-53e3dee6777744.68598023.jpg So I have now a browser which shows a tree made of UbakyeNodes (a tree like data structure I defined), but I would like not to show the Ubakye Nodes, but the titles of each node (headers) and the contents (bodies) of them when selected. With your help I have understood that I need to pass the collection of all children (not just the headers of them), but I don't know who to sellect something particular in that collection to be shown on the browser, like headers of nodes in the #tree panel or bodies in the #body panel. I would like to change also the size of each panel to be more like the shown in the screenshot, instead of the default one and be relative to window size. Is this possible? Thanks, Offray Below is the code, for easiness of reading: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- " Another exploration of Outliners provided by Glamorous Toolkit and browsers. This code was obtained by running 'GLMBasicExamples open' and then browsing until 'treeWithChildrenByLevel'. Some code was modified to open explicitely the browser on the world and starting to hack on it. " | browser mainTree | mainTree := UbakyeNode new. mainTree becomeDefaultTree. browser := GLMTabulator new. browser column: #tree; column: [ :c | c row: #body; row: #plugins ]. (browser transmit) to: #tree; andShow: [ :a | (a tree) title: mainTree header; children: [ :eachNode | eachNode children. ] "Children must return a collection" ]. (browser transmit) to: #body; from: #tree; andShow: [ :a | a text title: 'Cuerpo | Body ' ]. (browser transmit) to: #plugins; from: #tree port: #selectionPath; andShow: [ :a | a text title: 'Plugins | Extensiones' ]. browser openOn: mainTree children. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- On 08/05/2014 12:19 AM, Tudor Girba wrote: > Hi, > > You probably need this: > > explorer transmit to: #tree; andShow: [:a | > a tree > display: headers; > *children: [:eachNode | eachNode theMessageYouUseToGoToTheChildrenOfANode ]*]. > > A tree is a recursive structure, and to describe it you need: > - a way to construct the root elements. This is the result of applying display: > to the input object. So, display: either takes a collection or a block that will > return a collection when executed. > - a way to define the children for each node. This is the result of applying > children: > > You should also take a look at the examples from: > GLMBasicExamples open > > Does this help now? > > Cheers, > Doru > > > > > > On Sun, Jul 27, 2014 at 4:59 PM, Offray Vladimir Luna CÃ¡rdenas > <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: > > Hi, > > Answering to myself: I have solved the code that selects the headers of the > main tree. The key is to create a new collection containing only node names. > Here is the code: > > "*************************" > | mainTree node1 node2 explorer headers | > > mainTree := UbakyeNode > header: 'Arbol raÃz' > body: ''. > > node1 := UbakyeNode > header: 'Nodo 1' > body: 'Texto 1'. > > node2 := UbakyeNode > header: 'Nodo 2' > body: 'Texto 2'. > > mainTree > addNode: node1; > addNode: node2. > > > explorer := GLMTabulator new > title: (mainTree header). > explorer column: #tree; > column: #body. > > headers := (mainTree children) > collect: [:node | node header]. > > > explorer transmit to: #tree; andShow: [:a | > a tree > display: headers]. > > explorer openOn: mainTree. > > "*************************" > > Now I need to make the children sellectable, and that all the contents of > the tree can be updated with a shortcut. > > I will keep you posted. > > Cheers, > > Offray > > > On 07/26/2014 09:01 PM, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hi again, > > I will be using this thread to update my advances and questions about > how to build an outliner in Pharo Smalltalk. If there is a better method > like starting a new thread for particular questions, or a less narrative > style, please let me know. > > The idea is to use the tools provided by Moose to build a quick outliner > that can be extended to suit my needs on academical writing. This is > kind of a strange approach in the sense that I'm not following the > tutorials with a predefined problems (make a game and so) but trying to > start with a real (in the sense of closer) problem (making an outliner) > and to see which knowledge I need to solve this necessity. In that sense > is more like the Freire's alphabetization of adults in Brazil. > > So, the things I have done so far was to search for a good model to > start with. Something already done that can be used as scaffolding for > my outliner. The Help System seems like a good start for an outliner (in > fact it is already one), so I have taken the Help-Core system and start > to use it as a base for my project. > > After that I have used the Moose browsers to build a simple interface, > as seen here: > > http://mutabit.com/offray/__static/blog/output/galleries/__objetos/ubakye-b… > <http://mutabit.com/offray/static/blog/output/galleries/objetos/ubakye-brows…> > > > The part I want to deal with is this: > > =============== > > explorer := GLMTabulator new > title: (mainTree header). > explorer column: #tree; > column: #body. > > explorer transmit to: #tree; andShow: [:a | > a tree > display: mainTree children ]. > > explorer openOn: mainTree. > > =============== > > So, instead of "display: mainTree children" I need something that takes > the get names (headers) of the two nodes and the contents in the right > panel. For that I think that I need to learn some iterators. I have > already a "header" method for the nodes. Any clue would be appreciated > and I will keep you posted on my advances. > > Cheers, > > Offray > > > On 07/21/2014 12:58 PM, Offray Vladimir Luna CÃ¡rdenas wrote: > > Hi Damien, > > Thanks for your answer. Comments below. > > On 07/21/2014 11:09 AM, Damien Cassou wrote: > > On Sat, Jul 19, 2014 at 2:47 AM, Offray Vladimir Luna CÃ¡rdenas > <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: > > The first idea that comes to mind is using STON for storage > nodes and > tree > information, so I can interchange it with the flatland files > world > and keep > it readable. Sounds that reasonable? > > > > without more information, it is hard to stay. Try with STON and > change > if that does not work :-). We have XML and JSON generators as well. > > > > This is a kind of raw preview of I'm talking about: > > http://www.enlightenment.org/__ss/e-53cd4f36f021e9.68569046.__jpg > <http://www.enlightenment.org/ss/e-53cd4f36f021e9.68569046.jpg> > > Of course in this case, it is just a Help browser with a Playground > window over it, but I would like to have something like Playgrounds > inside the help browser. I was trying to build a custom browser with > Glamour, but seems that Help Browser already has the machinery I'm > looking for. > > So my first question is how to use the Help Browser class as a template > for my outliner class? And can I put a Playground where the plain text > is located right now? > > > The second thing I would like to do is to add pandoc's > markdown inside > comments, but I don't like the syntax of comments in > Smalltalk because > single quotes are fairly easy to find in light markup > language like > markdown. Is difficult to change it to create something more > like > python > (with """) or Lua (with -[]- )? > > > > There is only one syntax for comments in Pharo. Instead of Markdown, > you might want to have a look at Pillar which is implemented in > Pharo > and can generate Markdown (and html, and pdf) : > https://github.com/pillar-__markup/pillar-documentation/ > <https://github.com/pillar-markup/pillar-documentation/> > > > > I have seen Pillar. Seems really interesting, but Pandocs markdown > support academic citation in several formats and I have already long > docs wrote on that format integrated in my workflow from Zotero and even > there is a growing community working on Scholarly Markdown[1][2] so I > would like to stick with it as much as I can for my own writing. > That being said. I would like also a better integration between > Smalltalk outliners and all the academic publication work flow, > including working better with pandoc as a external library. > > [1] https://github.com/scholmd/__scholmd/wiki > <https://github.com/scholmd/scholmd/wiki> > [2] > http://blog.martinfenner.org/__2013/06/29/metadata-in-__scholarly-markdown/ > <http://blog.martinfenner.org/2013/06/29/metadata-in-scholarly-markdown/> > [3] > http://programminghistorian.__org/lessons/sustainable-__authorship-in-plain… > <http://programminghistorian.org/lessons/sustainable-authorship-in-plain-tex…> > > > > Thanks again, this conversation with people in the community is very > valuable to me, > > Offray > > > > > > > > _________________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/__mailman/listinfo/moose-dev > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" >

Aug. 7, 2014

Re: [Pharo-users] Slice loading/merging differences question

by stepharo

to complement mariano great answer. When we integrate changes we systematically merge so that even if you did a fix on a not recent version we get both improvements. Stef On 7/8/14 18:15, Tim Mackinnon wrote: > Hi - I am still a bit confused about the difference between load vs. > merge with Monticello? > > Last month, when I tried to verify a bug fix, I did a load - and it > caused other things (dependencies?) to be loaded into my clean image > and so I ended up with something else in a broken state. So I had to > do a Merge - get just the specific fixes and I could prove everything > worked. > > Yesterday however I wanted to test a fix Damien made for bug 13526. > But when I Merged it, I hit a DNU and then noticed he had put the > following comment (Slice .2 depends on 13787). > So I repeated the same merge step for 13787 and it then worked (apart > from another edge case I found and he has now fixed). > > But this has got me thinking, I donât really understand the difference > between merge/load. Can someone explain it to me in the above context? > Should I have âloadedâ 13526 so that it pulled in the > dependency indicated? (I notice in the slice description - it shows - > Dependencies: Tool-Base-DamienPollet.24). I thought Monticello managed > dependencies - so now Iâm confused why I need to do Merge anyway? > > Related to this, when the next âreleaseâ image gets built - how are > these slices assembled such that Tool-Base-DamienPollet.24 is > correctly loaded in release image? > > Thanks for any help. > > Tim

Aug. 7, 2014

Two Questions from a Newbie

by Ichiseki

Konnichiwa First thanks to those that gave me some directions to start with Pharo / Smalltalk. Now I have some questions that I'm sure are very stupid. The first one is, is there a way to use the bouncing atoms and the lights on on Pharo 3? Because I tried to build it in there and it doesn't work The second one is why there are like three different smalltalk environments? Pharo Squeek and Cuis? What are the differences? Is there a standard? I find this extremelly intriguing as it seems like there is a lot of dupplicate effort? The third one is which is the line between the core language and frameworks and libraries in Pharo? I found that, for instance Cuis has something like a basic image and some external frameworks, pharo has some internal frameworks and lots of externals. This is weird from someone comming from other languages. The fourth is I found that documentation is very, very scarce especially for some frameworks. This is also a major drawback for a newcomer to pharo. A very thick entry barrier. Thank you Ichiro -- View this message in context: http://forum.world.st/Two-Questions-from-a-Newbie-tp4772384.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 7, 2014