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

Pillar question: PRCitationTransformer

by stepharo

Hi I'm trying to extend Pillar to get new $publications:...$ structure and it looks like Pillar is getting more and more complex. And the comments do not really help because they are short and written for someone already understanding it. :( To try to understand I tried to ! Youpi ${cite:ref=Duca18rmod}$ !! Others but I get {"content":"!Youpi\n\n\n\n!!Others"} ./pillar export --to=pillar Example.pillar May be I cannot export to pillar a citation. I have no idea. I tried to add PRPillarWriter >> visitCitationAnnotation: aCitation "We invoke visitAnnotation: to make sure that the rest of the document is visited." self halt. super visitCitationAnnotation: aCitation Did not stop! So I put an halt into PRVisitor >> visitCitationAnnotation: aCitationAnnotation self halt. self createNewCitationWith: aCitationAnnotation. self replace: (OrderedCollection with: tmpCitation) . super visitCitationAnnotation: aCitationAnnotation and it stopped. I tried to understand who is calling PRCitationTransformer No luck. I'm sure that there is a magic registration mechanism but I failed to find it. Looking at tests (BTW Tests are not documentation or class comments, there are tests). It looks like I need a configuration. (self actualClass executeOn: (PRCompilationContext withDocument: anInput withConfiguration: aConfig)) input And then I fall on executeOn: implementors..... LLPhase and PRNodeTransformer. and I have no idea how a Phase relates to a visitor. To bad, after all the efforts on Pillar it looks like getting too complex. So do not think that we can decently ask students to work on improving Pillar anymore because they will just get lost and disgusted from Pharo. :( Sad news isn't. I hope that I will not have to switch back to LaTeX or markdown (shit). Stef

Aug. 22, 2016

Re: [Pharo-users] Browse scoped and new class Problem

by Vitor Medina Cruz

Done: https://pharo.fogbugz.com/f/cases/18972/Group-browse-scoped-class-sync On Sun, Aug 21, 2016 at 4:37 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-08-21 19:50 GMT+02:00 Vitor Medina Cruz <vitormcruz(a)gmail.com>: > >> Hello, >> >> I have a bunch of packages into a group browse scoped. If I create a new >> class inside of one of the packages the, the full browse updates correctly >> to show the new class, but the browse scoped don't, I had to close it and >> scope again to see the new class, is this the correct behavior? >> > > I don't know if this was intended, but the current way for a group to > create a scoped environment is to create a fixed classes environment of all > *current* classes in this group. > Any new class won't show up. > But yes, if the group contains a package and as the package classes can be > changed, the scoped view should create a package environment instead of a > classes environment. > Can you open a fogbugz issue. > > > >> >> I am using Pharo 5 in a windows 10 O.S. >> >> Regards, >> Vitor >> > >

Aug. 21, 2016

Re: [Pharo-users] Keyboard work flow?

by Peter UhnÃ¡k

I've made a shortcuts overview for Nautilus short while ago https://www.peteruhnak.com/blog/2016/08/03/nautilus-shortcuts-cheatsheet/ https://gist.github.com/peteruhnak/d9ee54f67d88b20ba85618e189b15669 but as noted there, when you are in the code pane it's a bit tricky. Peter On Sun, Aug 21, 2016 at 10:41 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 21/08/16 22:23, epeld wrote: > >> Is it possible to get by using ONLY the keyboard in the standard >> development >> components? >> > > Not really/yet. Nautilus can be controlled by keyboard for a large part of > its functionality, but the flow is not ideal. I've done some experiments > with CodePanel/NewUI in the past year. > > Stephan > > > >

Aug. 21, 2016

Re: [Pharo-users] Keyboard work flow?

by Stephan Eggermont

On 21/08/16 22:23, epeld wrote: > Is it possible to get by using ONLY the keyboard in the standard development > components? Not really/yet. Nautilus can be controlled by keyboard for a large part of its functionality, but the flow is not ideal. I've done some experiments with CodePanel/NewUI in the past year. Stephan

Aug. 21, 2016

Keyboard work flow?

by epeld

Hello! Is it possible to get by using ONLY the keyboard in the standard development components? Here are some workflows that I frequently use and would like to perform without mouse if possible: 1. Use Spotter to browse a class 2. Define a new method. That is, allow me to immediately focus the source code editor so I can start typing a new method or 1. Use Spotter to browse the implementation of a method 2. Edit its source code and accept 3. Now recategorize or rename or create new class etc etc. (the problem here is that the source code editor will shadow all the shortcuts I normally have in the browser, e.g CMD-M CMD-M would normally recategorize the method, but now this brings up the implementors list instead. Thanks! -- View this message in context: http://forum.world.st/Keyboard-work-flow-tp4912091.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 21, 2016

Re: [Pharo-users] Browse scoped and new class Problem

by Nicolai Hess

2016-08-21 19:50 GMT+02:00 Vitor Medina Cruz <vitormcruz(a)gmail.com>: > Hello, > > I have a bunch of packages into a group browse scoped. If I create a new > class inside of one of the packages the, the full browse updates correctly > to show the new class, but the browse scoped don't, I had to close it and > scope again to see the new class, is this the correct behavior? > I don't know if this was intended, but the current way for a group to create a scoped environment is to create a fixed classes environment of all *current* classes in this group. Any new class won't show up. But yes, if the group contains a package and as the package classes can be changed, the scoped view should create a package environment instead of a classes environment. Can you open a fogbugz issue. > > I am using Pharo 5 in a windows 10 O.S. > > Regards, > Vitor >

Aug. 21, 2016

Browse scoped and new class Problem

by Vitor Medina Cruz

Hello, I have a bunch of packages into a group browse scoped. If I create a new class inside of one of the packages the, the full browse updates correctly to show the new class, but the browse scoped don't, I had to close it and scope again to see the new class, is this the correct behavior? I am using Pharo 5 in a windows 10 O.S. Regards, Vitor

Aug. 21, 2016

Re: [Pharo-users] Spec > TreeModel: Updating the tree selection after a deletion

by Nicolai Hess

Hi Offrey, I think one problem is that the tree is always rebuild (on every selection?) even with self needRebuild:false tree needREbuild: false. all subwidgets of the notebook (tree and body) are removed and rebuild from changeBodys call to self buildWithSpecLayout: self class defaultSpec. I don't know if this is a bug or unavoidable. 2016-08-18 17:31 GMT+02:00 Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com>: > Hi all, > > Thanks Nicolai. Your examples helped me to advance and now I have the > basic possibility to modify the tree. The two methods that did the trick > are #addNode and #highlightNextitem, listed below, but I still get a MNU: > receiver of "selectedMorphList is nil, anytime I try to highlight the next > item and even from time to time with your code example. If you or anyone > want to work with the code directly please install run the playgrounds at > [1], [2] & [3], select any node after running [3] and press the Plus > button. You'll see that nodes are added in the tree after the current > selection, but the recently added node doesn't get the selection after > being created (instead the MNU mentioned before, appears). > > I will try to use the new created grafoscopio node and look for the > TreeNodeModel which has this node as a content to get the highlight. > > Help as always is greatly appreciated. > > Cheers, > > Offray > [1] http://ws.stfx.eu/M5A1F2NPD0QU > [2] http://ws.stfx.eu/EVOY0UKH74L0 > [3] http://ws.stfx.eu/5EF0OCUIG7CY > > ================ > > GrafoscopioNotebook>>addNode > tree needRebuild: true. > tree highlightedItem content addNodeAfterMe. > self notebookContent: notebook. > self highlightNextItem. > self buildWithSpecLayout: self class defaultSpec. > > ================ > > GrafoscopioNotebook>>highlightNextItem > | currentItem | > currentItem := tree highlightedItem. > currentItem > ifNotNil: [ | allItems index childrenSize parentNode | > currentItem parentNode > ifNil: [ > parentNode := currentItem container. > allItems := parentNode roots ] > ifNotNil: [ > parentNode := currentItem parentNode. > allItems := parentNode children value. ]. > childrenSize := currentItem content parent children size. > index := allItems indexOf: currentItem. > (index < childrenSize) ifTrue: [ > "{allItems . currentItem . index } inspect." > currentItem selected: false. > parentNode > highlightedItem: ((allItems at:(index+1)) > selected:true; > takeHighlight;yourself). > ] > ] > > > > On 11/08/16 13:05, Nicolai Hess wrote: > > > > 2016-08-10 21:03 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-08-10 20:42 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2016-08-10 19:12 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>>> >>>> >>>> 2016-08-10 19:05 GMT+02:00 Offray Vladimir Luna CÃ¡rdenas < >>>> offray.luna(a)mutabit.com>: >>>> >>>>> Hi, >>>>> >>>>> I have been fighting with this for several hours until now. I can't >>>>> understand how to manage change on selections on TreeModels with Spec, >>>>> which is really frustrating.... >>>>> >>>>> Here is what I have: >>>>> >>>>> GrafoscopioNotebook>>initializePresenter >>>>> tree whenSelectedItemChanged: [ :item | >>>>> self updateBodyFor: item. >>>>> header whenTextChanged: [ :arg | >>>>> (tree selectedItem content header) = arg >>>>> ifFalse: [ >>>>> (tree highlightedItem) content header: arg. >>>>> tree roots: tree roots]]] >>>>> >>>>> GrafoscopioNotebook>>updateBodyFor: item >>>>> item >>>>> ifNotNil: [ self changeBody: item ] >>>>> ifNil: [ self inform: 'Nil node' ] >>>>> >>>>> and #changeBody: deals with putting a textual or code pane according >>>>> to some tags on the selected node (and it's working properly). >>>>> >>>>> The problem seems that when I add/delete nodes to my tree, or while >>>>> changing the selection between nodes, the item variable becomes temporarily >>>>> nil and I can't update the contents of the body to correspond to the >>>>> current selection. I would like to say explicitly that a new tree added >>>>> node gets the selection and that the deletion of nodes gives selection to >>>>> its siblings or parent (if there are not siblings) and that node body pane >>>>> should be updated accordingly. >>>>> >>>>> Again, any hint would be really valuable... I'll take a break from the >>>>> computer to dissipate current frustration... Pharo is generally a happy >>>>> productive place... but not today :-/... anyway some hits are part of >>>>> learning to play with it. >>>>> >>>> >>>> Hi Offray, >>>> I do remember that I tried this as well, I will if I can find out how >>>> far I got it to work. >>>> >>> >>> a simiple example: >>> >>> |t nodeBlock | >>> nodeBlock:= [:class | |node| >>> node := TreeNodeModel new. >>> node hasChildren:[ class subclasses isEmpty not]. >>> node children: [class subclasses collect:[:subclass | nodeBlock >>> value: subclass]]. >>> node content: class]. >>> t:=TreeModel new. >>> t roots: (Morph subclasses collect:[:class | nodeBlock value:class]). >>> t whenBuiltDo:[ t selectedItem:( t roots first >>> selected:true;takeHighlight;yourself)]. >>> t openWithSpec >>> >>> the important part is the "takeHighlight" and to call it after the >>> widget is built >>> >>> >>> >> >> >> And an awfull example on how to modify selection (only the nodes of the >> root, couldn't find out how to do it for arbitrary subnodes) >> >> |t nodeBlock | >> nodeBlock:= [:class | |node| >> node := TreeNodeModel new. >> node hasChildren:[ class subclasses isEmpty not]. >> node children: [class subclasses collect:[:subclass | nodeBlock >> value: subclass]]. >> node content: class]. >> t:=TreeModel new. >> t autoDeselection:true. >> t roots: (Morph subclasses collect:[:class | nodeBlock value:class]). >> t menu:[:menu ||group| >> group := MenuGroupModel new. >> menu addMenuGroup: group. >> group addMenuItem:(MenuItemModel new name:'next';action:[ >> |item| >> item := t selectedItem. >> item ifNotNil:[|allItems index| >> allItems := item container roots. >> index := allItems indexOf: item. >> (index < allItems size) ifTrue:[item selected:false. item >> container selectedItem:((allItems at:(index+1)) >> selected:true;takeHighlight;yourself)] >> ] >> ])]. >> t whenBuiltDo:[ t selectedItem:( t roots first >> selected:true;takeHighlight;yourself)]. >> t openWithSpec >> >> again, the important part is #selectedItem: and #takeHighlight, otherwise >> the model doesn't know about the selection change. >> >> >> > Hm, yes, updating the selection after deletion is much more difficult. The > problem is that most in spec TreeModel is done for creating the tree > widget, not > for managing nodes and changes afterwards. > > >> >> >>> >>>> >>>>> >>>>> Cheers, >>>>> >>>>> Offray >>>>> >>>>> >>>>> On 07/08/16 16:11, Offray Vladimir Luna CÃ¡rdenas wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have a Spec TreeModel to represent the GUI of a grafoscopio >>>>>> notebook. >>>>>> >>>>>> The message that deletes nodes is something like this: >>>>>> >>>>>> ============ >>>>>> >>>>>> GrafoscopioNotebook>>removeNode >>>>>> | nodeToDelete | >>>>>> nodeToDelete := tree selectedItem content. >>>>>> nodeToDelete parent removeNode: nodeToDelete. >>>>>> tree selectedItem: tree selectedItem parentNode. >>>>>> tree needRebuild: true. >>>>>> tree roots: tree roots. >>>>>> self buildWithSpecLayout: self class defaultSpec. >>>>>> >>>>>> ============= >>>>>> >>>>>> And its working fine in the sense that it deletes the selected node, >>>>>> but after the deletion the contents of the old node are showed no matter if >>>>>> I change the node selection on the tree. I would like to manage selections >>>>>> in a smart way, so if I add a new node to the notebook, the new node gets >>>>>> the selection. If I delete a notebook node, the previous node gets selected >>>>>> or the parent if no more siblings are encountered and so on. There is some >>>>>> simple example to look for, about managing and updating selections in a >>>>>> TreeModel interface? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Offray >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> > >

Aug. 21, 2016

Re: [Pharo-users] [Pharo-dev] Beta of Mooc webportal

by Tudor Girba

This is great news. Thanks a lot for this effort! Doru > On Aug 20, 2016, at 3:24 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I published a new version of the webportal (a packaged version of the mooc) with the help of thibault. Now I'm about to test that all the videos have indeed the correct subtitles. > > If you want to give me a hand or simply have a look > > http://rmod-pharo-mooc.lille.inria.fr/MOOC/WebPortal/co/pharo.html > > Once everything will be verified we will push it to the mooc web page and announce it. > > Stef > > -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Aug. 21, 2016

Re: [Pharo-users] Google building new OS with Dart

by askoh

I think a lot could have change in the two years since I asked how Smalltalk can benefit from the development of Dart. Originally, Dart was meant to be a web language. Now it is going to be the main language for an Operating System. Since it has the full backing of Google, it is in our interest to ride with it. I wish Smalltalk not to miss out again. We can of course port the current VM's for Squeak, Pharo, VisualWorks to Fuchsia, but what do we gain by that? Not much, I think. What if Smalltalk can do everything Dart can do in Fuchsia - look and feel, apps, scripting, concurrency, etc. Since Smalltalk seems to be a superset of Dart, can we auto translate Dart to Smalltalk? Just as Slang converts Smalltalk to C, can we have a Smalltalk subset that converts to Dart? Can Smalltalk be the debugger or simulator for Dart development? Can Smalltalk do more than what Dart can do in Fuchsia? I wish I have access to the great minds Ben had mentioned. I am hoping that this thread will draw the best minds and ideas to pave the way for Smalltalk or its descendants to succeed in the future. Again, let's brainstorm. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Google-building-new-OS-with-Dart-tp4911649p4912075.ht… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 20, 2016