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

MNU PPContext>>identifier in GT Inspector extension

by Alistair Grant

Is anyone else seeing this error with Doru's Pillar GT Inspector extension? Given I can't get even a basic example to work I'm guessing that it is an environmental issue, but wanted to check first... I've tried loading it in both Pharo 5 and 6 with the same results when selecting the Pillar tab in GT Inspector: PPContext(Object)>>doesNotUnderstand: #identifier PPMemoizingSea(PPSea)>>check: PPMemoizingSea>>parseOn: PPActionParser>>parseOn: PPDelegateParser>>parseOn: PPChoiceParser>>parseOn: PPPossessiveRepeatingParser>>parseOn: GTPillarParser(PPDelegateParser)>>parseOn: GTPillarParser(PPParser)>>parseWithContext: GTPillarParser(PPParser)>>parse:withContext: GTPillarParser(PPParser)>>parse: GTPillarHighlighterTextDecorator>>parse:onError: GLMHighlighterTextParserStyler>>privateStyle: [ self privateStyle: text. view ifNotNil: [ view stylerStyledInBackground: text ] ] in [ backgroundProcess := [ self privateStyle: text. view ifNotNil: [ view stylerStyledInBackground: text ] ] forkAt: Processor userBackgroundPriority ] in GLMHighlighterTextParserStyler(SHTextStyler)>>styleInBackgroundProcess: in Block: [ self privateStyle: text.... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... This is attempting to inspect a FileReference to a file with the following contents: -- { "metadata": { "title": "My first document while reading the 5 minutes Pillar tutorial" } } !Hello World -- Code loaded with: Gofer it url: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'; configurationOf: 'Pillar'; loadStable "or Development or BleedingEdge" Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; package: 'PetitAnalyzer'; package: 'PetitIndent'; package: 'PetitIslands'; smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-InspectorExtensions-Pillar'; load Thanks, Alistair

Aug. 31, 2016

Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

by stepharo

Doru what would be fun is to extend pillar to get live display and update of scripts. Stef

Aug. 31, 2016

Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

by stepharo

I do not get how you can write a PhD in a system that does not support - footnote - citation - figure reference. Pillar supports all that. Le 30/8/16 Ã 15:28, Offray Vladimir Luna CÃ¡rdenas a Ã©crit : > Peter and Serge, > > I will be using Pandoc's markdown for sure. I can not wait *at this > moment* for Pillar to have the features I need for my writing (mainly > Zotero integration), but given the massive amount of work a proper > support of markdown will imply, I just use it, as now, by writing > plain text without any syntax highlighting support. There is an emacs binding for Pillar and it works well. There is also a textmate binding. > I wouldn't image that giving syntax highlighting support for markdown > in Pharo could be that hard, but I can write the thesis without it, > using just black text anywhere. Anyway having syntax support for > another languages is something that is being done for software > analysis, so, maybe at some point I can just try to learn how is being > done with Petit Parser o Smacc and see if I can help to create a more > markdown friendly environment in Pharo. I do not see the point I do not get why after all the efforts we are doing around Pillar and the proof that we can use it for making so great output people want markdown. Sorry but do not expect us to do anything in that direction. Stef > > Thanks, > > Offray > > > On 30/08/16 14:10, Serge Stinckwich wrote: >> On Tue, Aug 30, 2016 at 12:11 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> On Tue, Aug 30, 2016 at 07:50:10AM +0200, Offray Vladimir Luna >>> CÃ¡rdenas wrote: >>>> Hi, >>>> >>>> >>>> On 29/08/16 21:47, Yuriy Tymchuk wrote: >>>> >>>> [...] >>>>> >>>>>> It pains me that we are editing Pillar in outside tools, and now we >>>>>> should no longer have to do that. Of course, this is not the most >>>>>> ideal tool support for Pillar but I think it is a reasonable start. >>>>> To make things sadder: when I need to write some short ârichish" Iâm >>>>> using markdown instead for pillar because in ATOM I can open the >>>>> rendered version of my document that will update while i type (and >>>>> will >>>>> display images and so on). It could be nice to have the same >>>>> functionality in Pharo, but Iâm really busy with improving other >>>>> parts. >>>>> Additionally Iâm not sure that it makes sense to reimplement rich >>>>> text >>>>> editor in Pharo. >>>>> >>>>> Uko >>>>> >>>> For me it would be really nice to have this kind of support for >>>> markdown. >>>> That's the language I'm using for writing my PhD thesis in Pharo, >>>> and in >>>> fact now that I'm in hackademia Summer School[1] is nice to find >>>> some other >>>> PhD students that in fact are using markdown in their writing. >>>> >>>> [1] >>>> http://www.leuphana.de/en/research-centers/cdc/digital-cultures-research-la… >>>> >>>> Having syntax highlighting and graphics preview for markdown would >>>> be a way >>>> to introduce some new non-technical users and researchers to the Pharo >>>> world, reproducible research, interactive documentation and modable >>>> tools, >>>> but we need to start in a place they know, for example its markup >>>> language. >>> I don't really see the benefit of pushing Markdown into Pharo at >>> _this moment_ (there is PetitParser for some flavor of md though). >>> If you want to use Markdown, then there is already fifteen billion >>> of other tools outside. >>> >>> If you want deep integration with Pharo, then that takes a lot of >>> effort, which is being invested into Pillar, because Pillar is >>> aiming to be a much more powerful format --- maybe one day >>> comparable to reStructuredText and to what Python does with rst/sphinx. >> >> Yes a lot of effort has already been put on Pillar and should continue >> this effort. >> If you want to use Markdown, you can use existing tools outside the >> image. >> >>> Don't forget that markdown, although an excellent markup for what it >>> knows, is also very simplistic. >>> So if you want to use Markdown for PhD, then you are actually not >>> using markdown, but most likely pandoc (or some richer syntax, such >>> as scholarly markdown)... and support for either is another order of >>> magnitude more complex. >>> >>> Bottom line(s): >>> * there's a continuous investment into improvement and deep >>> integration of Pillar >>> * not enough resources to go around and implement any notation >>> * Markdown is too simplistic for any advanced writing (and >>> yes, I used it to write papers and my thesis, but it also includes >>> pandoc and many make/bash/ruby scripts to hack around) >> Markdown is not a good idea for thesis, but org-mode+org-babel is >> quite good for papers. You might have a look to >> Scimax that is based on these tools: >> http://kitchingroup.cheme.cmu.edu/scimax >> > > >

Aug. 31, 2016

Re: [Pharo-users] Spec Label is Black on Dark theme

by stepharo

Le 30/8/16 Ã 22:16, Nicolai Hess a Ã©crit : > > > 2016-08-30 20:01 GMT+02:00 Brad Selfridge <bsselfridge(a)gmail.com > <mailto:bsselfridge@gmail.com>>: > > How does one change Spec labels so that they don't show as black > on Dark > Theme but do show as black on standard Pharo theme? > > > > Looks like ListModel should overwrite #defaultColor > > defaultColor > ^ Smalltalk ui theme textColor > > But I am not sure how spec is supposed to work with theming, maybe > only the widget adapter should do this. Me neither :) and we never thought about it. Now I would introduce theme in a point high in the hierarchy and provide way to set it and avoid this plague: Smalltalk ui theme Stef > > > ----- > Brad Selfridge > -- > View this message in context: > http://forum.world.st/Spec-Label-is-Black-on-Dark-theme-tp4913253.html > <http://forum.world.st/Spec-Label-is-Black-on-Dark-theme-tp4913253.html> > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >

Aug. 31, 2016

Re: [Pharo-users] GTPlayground status: open or close

by Federico.Balaguer

Hello Andrei, Thanks for your kind reply. What I needed was close to your first example code. Thanks a lot! Federico -- View this message in context: http://forum.world.st/GTPlayground-status-open-or-close-tp4913257p4913285.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2016

Re: [Pharo-users] Spec Label is Black on Dark theme

by Peter Uhnak

On Tue, Aug 30, 2016 at 10:16:03PM +0200, Nicolai Hess wrote: > 2016-08-30 20:01 GMT+02:00 Brad Selfridge <bsselfridge(a)gmail.com>: > > > How does one change Spec labels so that they don't show as black on Dark > > Theme but do show as black on standard Pharo theme? > > > > > > > Looks like ListModel should overwrite #defaultColor > > defaultColor > ^ Smalltalk ui theme textColor > > But I am not sure how spec is supposed to work with theming, maybe only the > widget adapter should do this. Spec should not do any coloring anywhere, that should be done by the underlying Moprhic. However I think there was an issue with disabled label being render black (I had this issue in Merlin Wizard, which is in pure morphic). But don't really have time to look into that deeply. P

Aug. 30, 2016

Re: [Pharo-users] Spec Label is Black on Dark theme

by Nicolai Hess

2016-08-30 20:01 GMT+02:00 Brad Selfridge <bsselfridge(a)gmail.com>: > How does one change Spec labels so that they don't show as black on Dark > Theme but do show as black on standard Pharo theme? > > > Looks like ListModel should overwrite #defaultColor defaultColor ^ Smalltalk ui theme textColor But I am not sure how spec is supposed to work with theming, maybe only the widget adapter should do this. > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/Spec- > Label-is-Black-on-Dark-theme-tp4913253.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 30, 2016

Re: [Pharo-users] GTPlayground status: open or close

by Andrei Chis

Hi Frederico, Do you want to verify that a particular instance of GTPlayground is opened or if there is just any GTPlayground opened in the current image? For the first case a playground knows it's window. So you can check if there is a window and the window is in the world: aPlayground window ifNotNil: [ :aWindow | aWindow isInWorld ] ifNil: [ false ] For the second case something like the following script should work: (World submorphs select: [ :aMorph | aMorph isSystemWindow ]) detect: [ :aWindow | aWindow model class = GTPlayground ] ifFound: [ true ] ifNone: [ false ] Cheers, Andrei On Tue, Aug 30, 2016 at 8:51 PM, Federico.Balaguer < federico.balaguer(a)gmail.com> wrote: > Hello, > > BotArena is a tool for teaching objects that we are using in my University. > The tool allow students to enter Smalltalk expressions using an instance of > GTPlayground. > > There is a "reset" scenario where BotArena needs to know if there is a > Playground open so it does refresh bindings to given objects. > > So how can someone check whether a Playground is open or closed? > > Thanks! Federico > > > > > -- > View this message in context: http://forum.world.st/ > GTPlayground-status-open-or-close-tp4913257.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 30, 2016

GTPlayground status: open or close

by Federico.Balaguer

Hello, BotArena is a tool for teaching objects that we are using in my University. The tool allow students to enter Smalltalk expressions using an instance of GTPlayground. There is a "reset" scenario where BotArena needs to know if there is a Playground open so it does refresh bindings to given objects. So how can someone check whether a Playground is open or closed? Thanks! Federico -- View this message in context: http://forum.world.st/GTPlayground-status-open-or-close-tp4913257.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 30, 2016

Spec Label is Black on Dark theme

by Brad Selfridge

How does one change Spec labels so that they don't show as black on Dark Theme but do show as black on standard Pharo theme? ----- Brad Selfridge -- View this message in context: http://forum.world.st/Spec-Label-is-Black-on-Dark-theme-tp4913253.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 30, 2016