September 2017 - Pharo-users

Re: [Pharo-users] Brea wiki software

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 06/09/17 02:12, H. Hirzel wrote: > So at the moment I am fine to get it up and running using a FossilRepo. > Later on I will work on replacing it with a JSON data store. Please let me know if you need any permissions into the repository to make JSON data store available in Brea. > > On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> I understand that it makes a lot of sense to reuse the functions >> implemented in the FossilRepo. >> >> Installation of the Fossil version control system seems to be very >> simple, just put a single executable file into the pharo folder for >> example >> >> https://fossil-scm.org/index.html/doc/trunk/www/index.wiki Yes. Fossil is simpler and self-contained. A lot of friendly and powerful user experience without importing the external complexities of other developer cultures, like the popular systems (*coff... Git). I use the one provided by my package manager, but we have installed Fossil and started to use in our workshops and is a lot easier to start being productive without the almost always gratuitous extra complexities, specially for non tekies. Fossil gives me and easy distributed wiki out of the box. >> On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> What I wanted to write is that the class FossilRepo is not included. >>> >>> And that the setup of the Teapot server should not be hidden in lazy >>> initialisation method but made explicit with some methods in a method >>> category called 'setup' or 'configuration'. Please update your ConfigurationOfBrea, which fixes this two issues. >>>> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> >>>> wrote: >>>>> Hi, Hannes, >>>>> >>>>> Sorry it took so long. >>>> No problem. It was actually less than 14 days which is not long ..... >>>> >>>> :-) Despite of being just one week after I told you I would look at the issue, because the first one I have not access to my computer, is kind of a lot considering the good support times in this community (with rare exceptions, like when I feedback GT Tools and get no response :-/). Cheers, Offray

Sept. 6, 2017

Let's prepare for Google Code-In 2017 with Pharo Consortium

by Jigyasa Grover

Hello Pharo-ers ! On behalf of the community, I would like to thank each one of you for their significant contribution in the recently concluded *Google Summer of Code 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after this successful stint. In this spirit, I proposed at ESUG 2017 that we take part in the upcoming *Google Code-In 2017*. GCI is a contest to introduce pre-university students (ages 13-17) to open source software development. Because Google Code-in is often the first experience many students have with open source, the contest is designed to make it easy for students to jump right in with /bite-sized tasks/ (3 to 5 days) having categorised as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Students search for a task from the list created by us that interests them and claim it. They have at least three days to complete it. The student works on the task, getting guidance from mentors, if needed. Once the student is ready, they submit their work for review through the contest website. Mentors from the organisation evaluate the work, provide feedback, and if it's complete, accept it so that student can claim a new task. Otherwise, specific feedback is provided, and the student goes back to improving it. Participants who complete at least 1 task get a digital certificate. Participants who complete 3 or more tasks receive a t-shirt too. At the end of the contest, each organisation chooses five finalists to receive limited edition Google Code-in hoodies. Two finalists from each organisation get to be the grand prize winners and go on a trip to Google Headquarters in California ! The contest runs for about 6-8 weeks in December & January generally. With organisation applications beginning in October/November, we need to be well prepared for this seasonâs application with a hope to get selected. As an open source evangelist and a Pharo developer, I would like to invite all the experienced members to be a part of the "GCI with Pharo Consortium" Team and mentor students. To get added to the âprivate repositoryâ (we need to keep prospective students away from the task list before the program begins ð ) where you can put in your tasks/suggestions kindly EMail me or any of the previously added mentor. Looking forward to an appreciable representation from the Pharo community. Best regards Jigyasa Grover Pharo Consortium Org Admin, Google Summer of Code 2017 grover.jigyasa1(a)gmail.com Link to know more about GCI: https://codein.withgoogle.com/archive/ <https://codein.withgoogle.com/archive/ > Link to sample tasks: https://developers.google.com/open-source/gci/resources/example-tasks <https://developers.google.com/open-source/gci/resources/example-tasks> Link to FAQs: https://developers.google.com/open-source/gci/faq <https://developers.google.com/open-source/gci/faq > Link to contest rules: https://developers.google.com/open-source/gci/resources/contest-rules <https://developers.google.com/open-source/gci/resources/contest-rules> Link to GCI presentation for outreach: https://developers.google.com/open-source/gci/resources/downloads/Google-Co… <https://developers.google.com/open-source/gci/resources/downloads/Google-Co…> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 6, 2017

BlockStyler: Make Blocks more recognizable in source code

by Manuel Leuenberger

Hi everyone, I built a little syntax highlighting extension for the Nautilus source code pane, which puts a background color behind blocks, so that nested blocks are easily recognizable. Install with: Metacello new baseline: 'BlockStyler'; repository: 'github://maenu/BlockStyler/repository'; load GitHub: https://github.com/maenu/BlockStyler <https://github.com/maenu/BlockStyler> Doesnât work with âFormat as you readâ, just as the IconStyler. If anybody has an idea how to integrate it properly into Nautilus as a plugin, let me know. Currently itâs an ugly meta-link hack to get access to the sourceTextModel. Cheers, Manuel

Sept. 6, 2017

Re: [Pharo-users] Usability issues with Calypso

by Tim Mackinnon

Hey Denis - I didn't mean to interrupt your ESUG (I should have mentioned it was something to follow up on afterwards). Enjoy it and help lots of ideas. Should I raise a bug for the saving issue in fogbugz? I'll have to look at how you add define shortcuts in Calypso as I'm not familiar with that bit - so I'm using both browsers at the moment. Tim Sent from my iPhone > On 6 Sep 2017, at 10:45, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim. > > Sorry for late response. During Esug I am a bit out of mails. > > About saving method problem it is definitely a bug. Thank's for the report. > > About source code refactoring: > Supporting source code commands was easy to do with suggestions. In fact text editor menu is still working old way. That's why some extra source code menus of Nautilus is not supported in Calypso. > But general Idea is to redo all these commands with Commander. So it is todo. It is not complex task. And it will be available soon. > Now it is already possible to define shortcuts for missing source code refactorings. So if you need some concrete command we can add it very fast using shortcut . > > > > 2017-09-06 1:14 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> 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 Mackinnon <tim(a)testit.works> wrote: >>> >> >>> 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 <dionisiydk(a)gmail.com> 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 <tim(a)testit.works>: >>>>> 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 <dionisiydk(a)gmail.com> wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com>: >>>>>>> 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 >>>>>>> >>>>>> >>>>> >>>> >>> >

Sept. 6, 2017

Re: [Pharo-users] Usability issues with Calypso

by Denis Kudriashov

Hi Tim. Sorry for late response. During Esug I am a bit out of mails. About saving method problem it is definitely a bug. Thank's for the report. About source code refactoring: Supporting source code commands was easy to do with suggestions. In fact text editor menu is still working old way. That's why some extra source code menus of Nautilus is not supported in Calypso. But general Idea is to redo all these commands with Commander. So it is todo. It is not complex task. And it will be available soon. Now it is already possible to define shortcuts for missing source code refactorings. So if you need some concrete command we can add it very fast using shortcut . 2017-09-06 1:14 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > 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 Mackinnon <tim(a)testit.works> wrote: > > 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 <dionisiydk(a)gmail.com> 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 <tim(a)testit.works>: > >> 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 <dionisiydk(a)gmail.com> wrote: >> >> Hi >> >> 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com>: >> >>> 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/dio >> nisiydk/Calypso/issues. >> Thank's for you feedback. >> >> >> >>> >>> Just my two cents. >>> >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >> >> > >

Sept. 6, 2017

[ESUG] Looking for a job?

by Norbert Hartl

We are looking for new developers at ZWEIDENKER (the company formerly known as 2denker :) ). So if you are at ESUG right now and you are interested please either contact me in person or reply to this email and I will get in contact with you. See you, Norbert

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

So at the moment I am fine to get it up and running using a FossilRepo. Later on I will work on replacing it with a JSON data store. On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > I understand that it makes a lot of sense to reuse the functions > implemented in the FossilRepo. > > Installation of the Fossil version control system seems to be very > simple, just put a single executable file into the pharo folder for > example > > https://fossil-scm.org/index.html/doc/trunk/www/index.wiki > > The global state of a fossil repository is an unordered set of artifacts. > > An artifact might be a source code file, the text of a wiki page, part > of a trouble ticket, a description of a check-in including all the > files in that check-in with the check-in comment and so forth. > > Artifacts are broadly grouped into two types: > - content artifacts and > - structural artifacts. > > Content artifacts are the raw project source-code files that are > checked into the repository. > > Structural artifacts have special formatting rules and are used to > show the relationships between other artifacts in the repository. It > is possible for an artifact to be both a structure artifact and a > content artifact, though this is rare. Artifacts can be text or > binary. > > https://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki > > On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> What I wanted to write is that the class FossilRepo is not included. >> >> And that the setup of the Teapot server should not be hidden in lazy >> initialisation method but made explicit with some methods in a method >> category called 'setup' or 'configuration'. >> >> HH >> >> On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> Hi Offray >>> >>> Thank you for answering and the new release. I will look at it in >>> detail. Here is a first feedback. >>> >>> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> >>> wrote: >>>> Hi, Hannes, >>>> >>>> Sorry it took so long. >>> >>> No problem. It was actually less than 14 days which is not 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. >>> >>> >>> I followed the instructions but encountered a problem that the class >>> FossilRepo >>> >>> BreaWebsite >>> fossilRepo >>> ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] >>> >>> >>> This made that >>> >>> BreaWebsite example >>> >>> did not complete and thus there was no website. >>> Another thing is that the port number which is currently in >>> >>> BreaWebsite>>server >>> >>> server >>> ^ server ifNil: [ server := Teapot configure: { #port ->8500 . >>> #debugMode -> true } ] >>> >>> should be at a more prominent place so that it is easier to find and >>> thus configure. >>> >>> >>> Kind regards >>> Hannes >>> >>>> Cheers, >>>> >>>> Offray >>>> >>>> On 23/08/17 13:44, H. Hirzel wrote: >>>>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

I understand that it makes a lot of sense to reuse the functions implemented in the FossilRepo. Installation of the Fossil version control system seems to be very simple, just put a single executable file into the pharo folder for example https://fossil-scm.org/index.html/doc/trunk/www/index.wiki The global state of a fossil repository is an unordered set of artifacts. An artifact might be a source code file, the text of a wiki page, part of a trouble ticket, a description of a check-in including all the files in that check-in with the check-in comment and so forth. Artifacts are broadly grouped into two types: - content artifacts and - structural artifacts. Content artifacts are the raw project source-code files that are checked into the repository. Structural artifacts have special formatting rules and are used to show the relationships between other artifacts in the repository. It is possible for an artifact to be both a structure artifact and a content artifact, though this is rare. Artifacts can be text or binary. https://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > What I wanted to write is that the class FossilRepo is not included. > > And that the setup of the Teapot server should not be hidden in lazy > initialisation method but made explicit with some methods in a method > category called 'setup' or 'configuration'. > > HH > > On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Hi Offray >> >> Thank you for answering and the new release. I will look at it in >> detail. Here is a first feedback. >> >> On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>> Hi, Hannes, >>> >>> Sorry it took so long. >> >> No problem. It was actually less than 14 days which is not 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. >> >> >> I followed the instructions but encountered a problem that the class >> FossilRepo >> >> BreaWebsite >> fossilRepo >> ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] >> >> >> This made that >> >> BreaWebsite example >> >> did not complete and thus there was no website. >> Another thing is that the port number which is currently in >> >> BreaWebsite>>server >> >> server >> ^ server ifNil: [ server := Teapot configure: { #port ->8500 . >> #debugMode -> true } ] >> >> should be at a more prominent place so that it is easier to find and >> thus configure. >> >> >> Kind regards >> Hannes >> >>> Cheers, >>> >>> Offray >>> >>> On 23/08/17 13:44, H. Hirzel wrote: >>>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>>> 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 >>>> >>>> >>> >>> >>> >>> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

What I wanted to write is that the class FossilRepo is not included. And that the setup of the Teapot server should not be hidden in lazy initialisation method but made explicit with some methods in a method category called 'setup' or 'configuration'. HH On 9/6/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hi Offray > > Thank you for answering and the new release. I will look at it in > detail. Here is a first feedback. > > On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> Hi, Hannes, >> >> Sorry it took so long. > > No problem. It was actually less than 14 days which is not 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. > > > I followed the instructions but encountered a problem that the class > FossilRepo > > BreaWebsite > fossilRepo > ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] > > > This made that > > BreaWebsite example > > did not complete and thus there was no website. > Another thing is that the port number which is currently in > > BreaWebsite>>server > > server > ^ server ifNil: [ server := Teapot configure: { #port ->8500 . > #debugMode -> true } ] > > should be at a more prominent place so that it is easier to find and > thus configure. > > > Kind regards > Hannes > >> Cheers, >> >> Offray >> >> On 23/08/17 13:44, H. Hirzel wrote: >>> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>>> 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 >>> >>> >> >> >> >> >

Sept. 6, 2017

Re: [Pharo-users] Brea wiki software

by H. Hirzel

Hi Offray Thank you for answering and the new release. I will look at it in detail. Here is a first feedback. On 9/6/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > Hi, Hannes, > > Sorry it took so long. No problem. It was actually less than 14 days which is not 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. I followed the instructions but encountered a problem that the class FossilRepo BreaWebsite fossilRepo ^ fossilRepo ifNil: [ fossilRepo := FossilRepo new ] This made that BreaWebsite example did not complete and thus there was no website. Another thing is that the port number which is currently in BreaWebsite>>server server ^ server ifNil: [ server := Teapot configure: { #port ->8500 . #debugMode -> true } ] should be at a more prominent place so that it is easier to find and thus configure. Kind regards Hannes > Cheers, > > Offray > > On 23/08/17 13:44, H. Hirzel wrote: >> On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: >>> 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 >> >> > > > >

Sept. 6, 2017