- Pharo-users - lists.pharo.org

Re: [Pharo-users] Warning Newbie Question: Bootstrap Navbar example works my copy and paste fails?

by jtuchel＠objektfabrik.de

Ian, the first thing to do (imo) is to look for implementers of #navigationBar. I would guess there is none to be found in your image. That would mean you most probably don't have the code required for Seaside/Bootstrap loaded into your image. I am not a Pharo user, so I cannot tell you exactly how to load Seaside-Bootstrap in Pharo, but I am sure this is relatively easy to solve by the help of either Ecosia/DuckDuckGo/Yahoo or some Pharoer on this list. The steps to follow: 1. See if the method is implemented somewhere in your image 2. Try to find out whether your are sending Â Â Â a. the wrong message to the right object Â Â Â b. the right message to the wrong object Â Â Â c. a message that should be understood by the reciever but isn't I guess a) and b) can be excluded in your case, your code looks good to me. So the problem seems to be c). I am pretty sure the Seaside-Bootstrap package is missing in your image, it adds extension methods to WAHtmlCanvas, and I guess #navigationBar is one of them... HTH, Joachim Am 29.07.19 um 03:02 schrieb ian: > Hi All, > > Hopefully this is an easy one? > > I have been going through the MOOC exercises and have come across something I can't seem to figure out. > > In the example the code reads: > > ---- > renderExampleOn: html > > | bar id| > id := 'navbarSupportedContent'. > bar := html navigationBar. > bar beLight; expandLarge. > bar background beLight. > bar with: [ > html navigationBarBrand: 'Navbar'. ] > > ---- > > Mine reads exactly the same but errors in the browser with: > > ---- > > Seaside Walkback > MessageNotUnderstood: WAHtmlCanvas>>navigationBar > > Debug Proceed Full Stack > Possible Causes > > you sent a message this type of object doesn't understand > > Stack Trace > > thisContext > WAHtmlCanvas(Object)>>doesNotUnderstand: #navigationBar > self > a WAHtmlCanvas > > thisContext > VIHeaderComponent>>renderContentOn: > self > a VIHeaderComponent > > thisContext > WARenderVisitor>>visitPainter: > self > a WARenderVisitor > > thisContext > WARenderVisitor(WAPainterVisitor)>>visitPresenter: > self > a WARenderVisitor > > thisContext > WARenderVisitor(WAPainterVisitor)>>visitComponent: > self > a WARenderVisitor > > ---- > > When using Finder to locate the selector, navigationBar, I notice that it is a selector of SBSHtmlCanvas. > > So my question is: How to I set up my rendering class in seaside properly? Currently, as per all I can find I am properly using WAComponent as application super class. > > I don't see anything in the seaside book regarding bootstrap and I am fallowing the MOOC section on bootstrap almost to a tee. Accepting the fact that the library is now SBSDeploymentLibrary rather than TBSDeploymentLibrary. > > Any help would be greatly appreciated. > > Kindly, > > Ian > > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

July 29, 2019

Warning Newbie Question: Bootstrap Navbar example works my copy and paste fails?

by ian

Hi All, Hopefully this is an easy one? I have been going through the MOOC exercises and have come across something I can't seem to figure out. In the example the code reads: ---- renderExampleOn: html | bar id| id := 'navbarSupportedContent'. bar := html navigationBar. bar beLight; expandLarge. bar background beLight. bar with: [ html navigationBarBrand: 'Navbar'. ] ---- Mine reads exactly the same but errors in the browser with: ---- Seaside Walkback MessageNotUnderstood: WAHtmlCanvas>>navigationBar Debug Proceed Full Stack Possible Causes you sent a message this type of object doesn't understand Stack Trace thisContext WAHtmlCanvas(Object)>>doesNotUnderstand: #navigationBar self a WAHtmlCanvas thisContext VIHeaderComponent>>renderContentOn: self a VIHeaderComponent thisContext WARenderVisitor>>visitPainter: self a WARenderVisitor thisContext WARenderVisitor(WAPainterVisitor)>>visitPresenter: self a WARenderVisitor thisContext WARenderVisitor(WAPainterVisitor)>>visitComponent: self a WARenderVisitor ---- When using Finder to locate the selector, navigationBar, I notice that it is a selector of SBSHtmlCanvas. So my question is: How to I set up my rendering class in seaside properly? Currently, as per all I can find I am properly using WAComponent as application super class. I don't see anything in the seaside book regarding bootstrap and I am fallowing the MOOC section on bootstrap almost to a tee. Accepting the fact that the library is now SBSDeploymentLibrary rather than TBSDeploymentLibrary. Any help would be greatly appreciated. Kindly, Ian

July 29, 2019

Re: [Pharo-users] Personal Programming

by Hilaire

Thanks Richard for your review of the article and your pedagogical explanations. For me writing these interactive documents are not that much work. But it is true you need to know the DrGeo API. Which can be discovered by exploring the DrGeoSketch class. I am used to the DrGeo API, so my view is biased. A more user discoverable programming interface will be easier. So the interest on Trygve work. I am finishing writing a textbook on DrGeo math programming for my middle high school students. But the resources is in French :( Le 27/07/2019 Ã 16:26, Richard O'Keefe a Ã©critÂ : > There are some spelling issues in the PDF one finds at the > Newton-Raphson link. > "bellow" and "below" mean different things and sound quite different > (BELL-owe vs b'-LOW).Â In "In the sketch bellow" the one you want is > "below". > "bloc" and "block" sound the same but also mean different things, and > the Smalltalk [...] forms are "blocks" not "blocs". > > Is writing these interactive documents as much work as it looks like? > -- Dr. Geo http://drgeo.eu

July 28, 2019

Re: [Pharo-users] How to modify a non-forked Iceberg repository to create a pull request

by Esteban Maringolo

Thank you Gabriel. It was even simpler. Esteban A. Maringolo On Sat, Jul 27, 2019 at 5:37 PM Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Forth the repo > Add the remote > And just push to your remote > Then use the usual flow for pr > > On Sat, Jul 27, 2019, 16:33 Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> I was working on something using Glorp, loaded as a Metacello >> dependency cloned directly from the pharo-rdbms/Glorp GitHub repo. >> >> Then I found what I think is a bug, make a few modifications and make >> created a new commit. >> >> I cannot commit to the `origin` remote since I'm not a member, but I >> can't create a pull request, because I started from the "upstream" >> repo as my base. >> >> What should be the way to solve this without losing the local changes >> (commited but not pushed)? >> >> I thought: >> - Fork the pharo-rdbms/Glorp repository in my own GitHub user >> - Add a new remote (via CLI) to my Glorp local (pharo) >> repositorypointing to the one at my user (emaringolo/Glorp). >> - Fetch and checkout from the remote pointing to my repository >> - Merge my local changes into my repository >> - Push my changes >> - Create a pull request from eMaringolo/Glorp to pharo-rdbms/Glorp >> >> Is this wrong? What do you suggest? >> I think this might happen to anyone who started working on some >> repository that is not a fork of the canonical and then tries to make >> changes to it. >> >> Regards, >> >> Esteban A. Maringolo >>

July 27, 2019

Re: [Pharo-users] How to modify a non-forked Iceberg repository to create a pull request

by Gabriel Cotelli

Forth the repo Add the remote And just push to your remote Then use the usual flow for pr On Sat, Jul 27, 2019, 16:33 Esteban Maringolo <emaringolo(a)gmail.com> wrote: > I was working on something using Glorp, loaded as a Metacello > dependency cloned directly from the pharo-rdbms/Glorp GitHub repo. > > Then I found what I think is a bug, make a few modifications and make > created a new commit. > > I cannot commit to the `origin` remote since I'm not a member, but I > can't create a pull request, because I started from the "upstream" > repo as my base. > > What should be the way to solve this without losing the local changes > (commited but not pushed)? > > I thought: > - Fork the pharo-rdbms/Glorp repository in my own GitHub user > - Add a new remote (via CLI) to my Glorp local (pharo) > repositorypointing to the one at my user (emaringolo/Glorp). > - Fetch and checkout from the remote pointing to my repository > - Merge my local changes into my repository > - Push my changes > - Create a pull request from eMaringolo/Glorp to pharo-rdbms/Glorp > > Is this wrong? What do you suggest? > I think this might happen to anyone who started working on some > repository that is not a fork of the canonical and then tries to make > changes to it. > > Regards, > > Esteban A. Maringolo > >

July 27, 2019

How to modify a non-forked Iceberg repository to create a pull request

by Esteban Maringolo

I was working on something using Glorp, loaded as a Metacello dependency cloned directly from the pharo-rdbms/Glorp GitHub repo. Then I found what I think is a bug, make a few modifications and make created a new commit. I cannot commit to the `origin` remote since I'm not a member, but I can't create a pull request, because I started from the "upstream" repo as my base. What should be the way to solve this without losing the local changes (commited but not pushed)? I thought: - Fork the pharo-rdbms/Glorp repository in my own GitHub user - Add a new remote (via CLI) to my Glorp local (pharo) repositorypointing to the one at my user (emaringolo/Glorp). - Fetch and checkout from the remote pointing to my repository - Merge my local changes into my repository - Push my changes - Create a pull request from eMaringolo/Glorp to pharo-rdbms/Glorp Is this wrong? What do you suggest? I think this might happen to anyone who started working on some repository that is not a fork of the canonical and then tries to make changes to it. Regards, Esteban A. Maringolo

July 27, 2019

Re: [Pharo-users] Personal Programming

by Richard O'Keefe

There are some spelling issues in the PDF one finds at the Newton-Raphson link. "bellow" and "below" mean different things and sound quite different (BELL-owe vs b'-LOW). In "In the sketch bellow" the one you want is "below". "bloc" and "block" sound the same but also mean different things, and the Smalltalk [...] forms are "blocks" not "blocs". Is writing these interactive documents as much work as it looks like? On Sat, 27 Jul 2019 at 17:59, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Trygve, > > Personal programming is something I always been fascinated by, since > decades, to empower users. > > In the domain of teaching, the concept can go as far as giving the > ability to teachers to craft their own numeric tools in their respective > area. > > This is for this exact reason I ported DrGeo to Squeak, then Pharo, in > 2005. The end user programming gives the power to design very advanced > teaching models[1]. > > However, Smalltalk scripting can be tricky, so this is with profound > interest I will read your paper in the later days. > > Hilaire > > [1] http://blog.drgeo.eu/post/2019/The-Newton-Raphson-Method > > Le 25/07/2019 Ã 11:29, Trygve a Ã©crit : > > The final draft of my magnum opus about Personal Programming is now > > ready for review: > > http://folk.uio.no/trygver/themes/Personal/PP-019%20-%20Copy%20(17).pdf > > -- > Dr. Geo > http://drgeo.eu > > > >

July 27, 2019

[ANN] Pharo Newsletter July 2019

by Marcus Denker

The Pharo Newsletter July 2019 has been sent to subscribers one week ago. https://mailchi.mp/pharo/pharo-newsletter-july-2019 <https://mailchi.mp/pharo/pharo-newsletter-july-2019> To get it as soon as it is released, please subscribe here: http://eepurl.com/bykqWn <http://eepurl.com/bykqWn>

July 27, 2019

Re: [Pharo-users] Personal Programming

by Hilaire

Hi Trygve, Personal programming is something I always been fascinated by, since decades, to empower users. In the domain of teaching, the concept can go as far as giving the ability to teachers to craft their own numeric tools in their respective area. This is for this exact reason I ported DrGeo to Squeak, then Pharo, in 2005. The end user programming gives the power to design very advanced teaching models[1]. However, Smalltalk scripting can be tricky, so this is with profound interest I will read your paper in the later days. Hilaire [1] http://blog.drgeo.eu/post/2019/The-Newton-Raphson-Method Le 25/07/2019 Ã 11:29, Trygve a Ã©critÂ : > The final draft of my magnum opus about Personal Programming is now > ready for review: > http://folk.uio.no/trygver/themes/Personal/PP-019%20-%20Copy%20(17).pdf -- Dr. Geo http://drgeo.eu

July 27, 2019

Re: [Pharo-users] P7 regression

by Hilaire

Not at the same time on the same file. #put:into is use in one situation to write out a sketch as a XML file, and in another situation to write out a PNG image. However, It is true DrGeo xml document can embed bitmap, but it is base64 encoded, so saving with readStream is not a problem. I am still curious how I will use wrappedStream inÂ case DrGeo's XML document contained binary data. Le 26/07/2019 Ã 08:03, Sven Van Caekenberghe a Ã©critÂ : > You said you wanted to write both character data (XML) as binary data (images) to the same stream, or so I understood. > >> On 26 Jul 2019, at 00:22, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> I don't understand how #wrappedStream works in my situation? >> >> Is #isBinary not good enougth? >> >> Le 25/07/2019 Ã 21:53, Sven Van Caekenberghe a Ã©crit : >>> If you have a character read or write stream, you can use #wrappedStream to access the underlying binary stream, should you need to do that. >>> >>>> On 25 Jul 2019, at 20:31, Hilaire <hilaire(a)drgeo.eu> wrote: >>>> >>>> Thanks for the tips. It is definitely a left over from porting DrGeo to >>>> P7 from P4/5/6 (not sure) >>>> >>>> But it can't really work as put:into: is used to write both sktech >>>> content (XML file) and its PNG preview. >>>> >>>> At some point in Pharo history both UTF8 and bitmap were using binary >>>> stream. >>>> >>>> Likely a putBinary:into: is needed too. >>>> >>>> -- >>>> Dr. Geo >>>> http://drgeo.eu >>>> >>>> >>>> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> > -- Dr. Geo http://drgeo.eu

July 26, 2019