Re: [Pharo-users] [Pharo-dev] ESUG Pharo GIT BOFs
Wednesday after Martin talk we will have a consortium discussions Thursday after esteban talk we will have the git Pharo BOF 16h-16h45 Git 16h45- on BOF On Wed, Sep 6, 2017 at 2:50 AM, John Pfersichwrote: > Birds of a Feather, sort of an informal get-together. > > Sent from my iPad > > On Sep 5, 2017, at 14:47, Peter Uhnák wrote: > > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > > On Tue, Sep 5, 2017 at 9:18 AM, Stéphane Ducasse > wrote: >> >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> >> Stéphane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >
Re: [Pharo-users] [Pharo-dev] ESUG Pharo GIT BOFs
Birds of a Feather, sort of an informal get-together. Sent from my iPad > On Sep 5, 2017, at 14:47, Peter Uhnákwrote: > > I don't see Esteban's talk in the conference schedule. > > Also, what is BOF shortcut for? > > P > >> On Tue, Sep 5, 2017 at 9:18 AM, Stéphane Ducasse >> wrote: >> Thursday after the talk of Esteban 16h45 >> Please pass the message and join. >> Stef >> >> >> >> Stéphane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >
Re: [Pharo-users] Usability issues with Calypso
BTW - Is it intended that when you save a method in a Calypso tab, it shifts focus to the first non saved tab? I find this quite confusing as suddenly I'm not where I thought I was and wonder if I saved my method? This said, I love the fact you can move to a new method with unsaved changes and no nag prompt. Tim Sent from my iPhone Sent from my iPhone > On 3 Sep 2017, at 22:25, Tim Mackinnonwrote: > > Ah - you are right that rename is in there (I’d never noticed it was in the > suggestions menu - which I find a confusingly named sub-menu ) - but I am > missing the more appropriately named “Source Code Refactoring” menu, which it > also appears along with extract method etc. This menu is not in Calypso right? > > Tim > >> On 3 Sep 2017, at 17:24, Denis Kudriashov wrote: >> >> Hi Tim. >> >> No. It is available by cmd+r and from suggestions menu like in Nautilus. But >> maybe I do not know other place which you use for this >> >> 2017-09-03 17:03 GMT+02:00 Tim Mackinnon : >>> Hi Denis - I just noticed that the source refactoring menu is missing in >>> Calypso as well? (So you can’t rename a temp for example). >>> >>> Tim >>> On 2 Sep 2017, at 10:30, Denis Kudriashov wrote: Hi 2017-09-01 14:26 GMT+02:00 kmo : > I have been keen to use Calypso (I love the way it shows inherited > methods) > as my browser but I am finding some usability issues. It may be just me > but > some things I find off-putting. Any feedback is very important. > > I don't really like the way that adding a new class is done by a new tab > that appears now and then in the editing area. To my mind the Nautilus way > of launching a dialog to create a class seems more natural - and opens the > way in future for a class creation wizard - something that can't be done > in > a code window. If we have to do it in a code tab then it would be better > if > the tab remained there all the time - I don't like the way it appears and > disappears. It takes a while to learn what to click to do this. In fact current behaviour is not replacement of old context menu command. It is just rethinking of classic single source code pane of old browsers. So we will add missing command to context menu. But I think the command should open the current "New class" tab instead of old dialog request. Also old browser behaviour is still working. You can create new class from the class editor tab. Just type new class name in the definition of selected class. > > Also, all class creation presumes a subclass of Object in Calypso. i miss > the ability in Nautilus to select a class and immediately create a > subclass > of it. Am I missing something here? Is there a way? You are right. It is missing command like previous one. We will add it. > > On the topic of my ignorance - what is a /project /in Calypso? How do you > create one? Now it is more like a stub. There is integration with new package management Cargo (Christophe is working on it). But it is probably not ready yet. I think we should also implement Metacello backend. Anyway project mode will become default view in future. > > And what does realize do? It creates stub implementation of abstract methods (found in superclasses). I think in Calypso this command is not needed anymore because there is "should be implemented" method group which shows all these abstract methods. > > Also I think that the pop up menus could be subdivided into categories > rather than present all the options in an unbroken list. And the order of > options seems odd. To my mind/ senders /and /implementers /are two menu > options that should always go together - not be separated by/ rename/ and > /move to class side/ et cetera. Yes, I will add it. You can report issues directly at github project https://github.com/dionisiydk/Calypso/issues. Thank's for you feedback. > > Just my two cents. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
Re: [Pharo-users] Brea wiki software
Hi, Hannes, Sorry it took so long. I'm now finishing my PhD and entering into a focused writing mode, so is difficult to keep with mailing lists these days. New version contains an example. Please load the ConfigurationOfBrea as showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run: BreaWebsite example and visit - http://localhost:8080/demo/ - http://localhost:8080/members/test - http://localhost:8080/members/add There are still some issues with CSS and data persistence must be implemented, but this should give you and overview of how to combine Teapot + Mustache. Cheers, Offray On 23/08/17 13:44, H. Hirzel wrote: > On 8/23/17, Offraywrote: >> Hi, >> >> On the Teapot + Mustache integration, Hannes, you may want to see my early >> prototype: >> >> http://smalltalkhub.com/#!/~Offray/Brea >> >> At some point, it will contain distributed wiki, backed by Fossil, now that >> we're thinking in empower community driven wiki like documentation. >> >> Offray > > Hi Offray > > I found Name: Brea-OffrayLuna.8 > Author: OffrayLuna > Time: 1 June 2017, 4:18:20.860411 pm > > There is no test to show me how to use it and I none of the class > comments of the 4 classes gives enough clues. > > > Interesting method so far > > routes > "I define how the website behaves accordingly to particular routes." > self server > serveStatic: 'demo' from: '/opt/gig/'; > GET: 'members/test' -> [ :req | BreaMember new > renderTestUserAsHtml ]; > GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; > POST: 'members/summit' -> [ :req | self processNewMember: req ] > > > May I ask you to give a few hints how to start it? > Is it possible to use it without Fossil, just with image persistence? > > Regards > Hannes > >
Re: [Pharo-users] Spec "bindings"
Rob Spec deserves another pass. I see your point with showOn: now I do not see how you could avoid the presenter building. But may be I'm not enough into it. So I'm interested in your feedback. Stef Stef On Tue, Sep 5, 2017 at 8:49 PM, Rob Rothwellwrote: > Hello, > > I was wondering what more experienced users than myself thought of the idea > of an explicit Spec "connection point" to a domain model object similar to > Dolphin's "showOn:" method, like: > > CounterApp showOn: counter. > > This would perhaps trigger something like Dolphin's Presenter>>model: > message (although I've always found the use of "model" confusing when there > are so many "models" involved.) after the widgets had been created: > > ComposableModel>>initializeBindings: anObject > > In many cases, if your domain model uses ValueHolders as well (like Spec > does), making a connection could just mean replacing the Spec ValueHolder > with your domain ValueHolder so changes to the domain model would > automatically propagate to the UI presentation without providing explicit > code in ComposableModel>>initializePresenter. > > However, since I am still trying to understand and learn Spec, it's quite > possible I am missing some key point and there are reasons not to explore > this line of thinking! > > Thank you, > > Rob >
Re: [Pharo-users] [Pharo-dev] ESUG Pharo GIT BOFs
I don't see Esteban's talk in the conference schedule. Also, what is BOF shortcut for? P On Tue, Sep 5, 2017 at 9:18 AM, Stéphane Ducassewrote: > Thursday after the talk of Esteban 16h45 > Please pass the message and join. > Stef > > > > Stéphane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, Bât.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >
[Pharo-users] Spec "bindings"
Hello, I was wondering what more experienced users than myself thought of the idea of an explicit Spec "connection point" to a domain model object similar to Dolphin's "showOn:" method, like: CounterApp showOn: counter. This would perhaps trigger something like Dolphin's Presenter>>model: message (although I've always found the use of "model" confusing when there are so many "models" involved.) after the widgets had been created: ComposableModel>>initializeBindings: anObject In many cases, if your domain model uses ValueHolders as well (like Spec does), making a connection could just mean replacing the Spec ValueHolder with your domain ValueHolder so changes to the domain model would automatically propagate to the UI presentation without providing explicit code in ComposableModel>>initializePresenter. However, since I am still trying to understand and learn Spec, it's quite possible I am missing some key point and there are reasons not to explore this line of thinking! Thank you, Rob
Re: [Pharo-users] The Spec UI Framework. first translation to korean finish.
:) Stef On Tue, Sep 5, 2017 at 10:35 AM, peter yoowrote: > to Stephane. > > of course. not use korean cahracter in directory location then compile > successful. :D
[Pharo-users] Teapot and Websockets
Hello, Is it somehow possible to have a Teapot server running within there a WebsocketHandler (for instance ZnWebSocketChatroomHandler). Something like: Teapot on WS: '/ws-chatroom' -> [: aWebSocket | self registerWebSocket: aWebSocket ]; start. Or is this totally wrong? Georges -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Re: [Pharo-users] Write documentation with wiki like syntax -- how do I activate the rendering?
Hello Torsten Thank you for the demo that it is actually possible to make it work! Thus I managed to build help topics for my app. It really very easy to add help topics! The source of the error was that I had spaces before the ! marks which mark a section title. Reason is that I had just copied the wiki text example from the help text to do the test. So this is clearly a bug leading people to think that wiki style help does not work. See at the bottom for a wiki string which works (just spaces removed in front of !) [1] Good that this is compatible with the Pillar syntax which I am using for other things. It offers many options, for example the class side method #helpString can pull out part or the whole of the class comment. Regards Hannes [1] Example of wiki style help text to be added on the class side The help browser parses this text when being opened Notes - There are no spaced in front of the ! marks - The class WikiStyleHelpBuilder does the job of parsing a subset of the Pillar/Pier syntax and building up the help nodes tree. helpString ^ ' ! Section 1 Some text for this section !! Subsection 1.1 !!! Subsection 1.1.1 !! Subsection 1.2 ! Section 2' On 9/5/17, Torsten Bergmannwrote: > Hi Hannes, > > make sure > - it is a class side method > - you have no spaces before the ! marks > - you reopen the help browser > > then it works and creates subtopics. See screenshot attached. > > Bye > T.
Re: [Pharo-users] [DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager
On 9/5/17, Torsten Bergmannwrote: >>How can I de-activate the ctrl-D shortcut for the Desktop manager for >>the time being? > > By not using DesktopManager. Sure... What I was asking for: How can I use it _without_ the ctrl-D short cut. Or how can I replace the ctrl - D shortcut with another short cut. >The shortcut handlers are installed upon load > initialize. And how can I bypass or adapt this initialize method? What is the initialization code in case I load the classes manually? > best wishes --Hannes
Re: [Pharo-users] The Spec UI Framework. first translation to korean finish.
to Stephane. of course. not use korean cahracter in directory location then compile successful. :D
Re: [Pharo-users] Pharo 6 FileSystem>>changeDirectory: is missing
Thanks for reporting. I do not remember an action around me for this change. Do you have the definition in Pharo 50 at hand? Stef On Wed, Aug 30, 2017 at 11:09 PM, Andreas Sunardiwrote: > I found FileSystem class has changed from Pharo 5 to Pharo 6. I've been > using FileSystem>>changeDirectory to make my program (Pharo 5) runs in the > current working directory (thus able to find local files). > > This is now broken because #changeDirectory doesn't exist anymore. The > change seems intentional. > > Question: Is there a different way in Pharo 6 do set working directory or is > this a bug? > > -- > Andreas
Re: [Pharo-users] The Spec UI Framework. first translation to korean finish.
Can you try to avoid to have korean characters in file name? On Fri, Sep 1, 2017 at 8:34 AM, peter yoowrote: > Hi damien. > > 1. compile location issue > - filesystem using UTF-8 with NFC(because linux) > - all book source is plain. im not editing anything. only from git > repository > > === > ./pillar export --to="latex:sbabook" --outputFile=SpecBooklet > SpecBooklet.pillar > CCConfigurationError: /mnt/USERDISK/onion/99_SpecUI한글/BuildingUIWithSpec > is not a valid directory. > === > > error is this line. maybe pillar process then can not acceptable korea > charactor in directory location. > before i look similar problem. > a few years ago, im using pharo in linux then can take input from XIM. but > can not process korean charactor to pharo workspace. because input charactor > process standard is NFD. > > work is here. written in korean. but can read. many text is "source code" > http://workspace.onionmixer.net/mediawiki/index.php?title=Linux_cogvm_xim_howto#XIM_.EC.9C.BC.EB.A1.9C_.EB.93.A4.EC.96.B4.EC.98.A4.EB.8A.94_.EC.9E.85.EB.A0.A5.EA.B0.92.EC.97.90_.EB.8C.80.ED.95.9C_.EC.B6.94.EC.A0.81_.EB.B0.8F_.EC.A0.95.EC.83.81.EB.8F.99.EC.9E.91.EC.9D.84_.EC.9C.84.ED.95.9C_.EC.88.98.EC.A0.95 > > I do not know if it will be a reference. > > > > 2. sbabook issue > > oh.. no.. no need more oblivoir. because oblivoir is only for CJK env. > example for thai then oblivoir cannot show all charactor. oblivoir have a > limit. i know already. > > I think the current situation is a new one. my work need many language > processing at web, mobile, and.. pdf. generate pdf using xetex with > oblivoir. have a little problem now. > > need study polyglossia a few days soon. dont worry. and thanks to you. I was > motivated. really :D
[Pharo-users] Pharo BOF at ESUG
Thursday after the talk of Esteban 16h45 Please pass the message and join. Stef
[Pharo-users] [DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager
>How can I de-activate the ctrl-D shortcut for the Desktop manager for >the time being? By not using DesktopManager. The shortcut handlers are installed upon load initialize. Bye T.
[Pharo-users] Write documentation with wiki like syntax -- how do I activate the rendering?
Hi Hannes, make sure - it is a class side method - you have no spaces before the ! marks - you reopen the help browser then it works and creates subtopics. See screenshot attached. Bye T.