- Pharo-users - lists.pharo.org

Re: [Pharo-users] rethinking compilation notifications

by Yuriy Tymchuk

On 04 Aug 2014, at 12:06, Werner Kassens <wkassens(a)libello.com> wrote: > Hi, > makes a lot of sense to me. btw i dont like the printit thing too much: there was a a thread about scientists using programming languages with a notebook interface somewhere. in order to document what i do, i often use print it and then press '"' to make a comment out of the result. iow this printit version would need a 'make it a comment' command additionally to the inspectit command. Or make is a sticky ;). I think that non-text solutions still have greater possibilities Uko > werner > > On 08/03/2014 10:09 PM, Tudor Girba wrote: >> Hi, >> >> The next stop in our little tour around code actions was the compilation >> notifications. Again, we used a popper interface to show the error >> without affecting the underlying text editor: > http://www.humane-assessment.com/blog/rethinking-compilation-notifications-… >> >> Please let us know what you think. >

Aug. 4, 2014

Re: [Pharo-users] rethinking compilation notifications

by Werner Kassens

Hi, makes a lot of sense to me. btw i dont like the printit thing too much: there was a a thread about scientists using programming languages with a notebook interface somewhere. in order to document what i do, i often use print it and then press '"' to make a comment out of the result. iow this printit version would need a 'make it a comment' command additionally to the inspectit command. werner On 08/03/2014 10:09 PM, Tudor Girba wrote: > Hi, > > The next stop in our little tour around code actions was the compilation > notifications. Again, we used a popper interface to show the error > without affecting the underlying text editor: http://www.humane-assessment.com/blog/rethinking-compilation-notifications-… > > Please let us know what you think.

Aug. 4, 2014

Re: [Pharo-users] Syncing local cache and SmalltalkHub

by stepharo

On 3/8/14 20:56, Offray Vladimir Luna CÃ¡rdenas wrote: > Juan, Ben and Stef, > > Thanks. I tested first Ben's suggestion but Juan's seems to work > better (first one gave me an error... don't remember well which one). > Now I have my repo online: > > http://smalltalkhub.com/#!/~Offray/Ubakye > > When I try to browse the source, I can find .mcz files, but I wonder > if there is a way to point to a specific method of an specific version > and see it online. you can do that from the monticello browser. explore. > > Cheers, > > Offray > > On 08/02/2014 05:10 PM, Juan Ignacio Vaccarezza wrote: >> Hi Offray, >> >> I recently faced the same problem, the way I solved it by using >> Gofer to sync >> the repos. >> >> go := Gofer new. >> >> go repository: (MCSmalltalkhubRepository >> owner: 'You' >> project: 'yourProjectName' >> user: 'userName' >> password: 'yourSecretPass'). >> >> go package: 'PackageName'; push. >> >> >> I got the example from here: >> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Gofer.pdf >> >> Hope it helps. >> >> Regards, >> Juan >> >> >> >> On Sat, Aug 2, 2014 at 5:02 PM, Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>> wrote: >> >> Hi Offray, >> >> Once you create your StHub repository and define it in your >> image, you can >> just copy versions (mcz files) from your package cache to the >> new repository >> using the Copy button in the Repository browser (which you get >> by selecting >> your local package cache in the Monticello browser and clicking >> the Open >> button). >> >> HTH, >> >> Sven >> >> On 02 Aug 2014, at 21:25, Offray Vladimir Luna CÃ¡rdenas >> <offray(a)riseup.net >> <mailto:offray@riseup.net>> wrote: >> >> > Hi, >> > >> > I have my outliner buggy mockup on local cache, and I would >> like to share >> the code and point to it online using SmalltalkHub for my >> questions. I have >> followed the chapter on Source code management with Monticello y >> PBE2, and >> it says that you can have your code on SmalltalkHub, but says >> nothing about >> how to sync from local cache to your SmalltalkHub account. Can >> some one >> could point me the way to do it? >> > >> > Cheers, >> > >> > Offray >> > >> >> >> > > >

Aug. 4, 2014

Re: [Pharo-users] [Pharo-dev] rethinking compilation notifications

by Santiago Bragagnolo

So beautiful :) 2014-08-03 22:09 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > The next stop in our little tour around code actions was the compilation > notifications. Again, we used a popper interface to show the error without > affecting the underlying text editor: > > [image: Inline image 2] > > You can find more details here: > > http://www.humane-assessment.com/blog/rethinking-compilation-notifications-… > > Please let us know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Aug. 4, 2014

Re: [Pharo-users] rethinking compilation notifications

by Sven Van Caekenberghe

On 04 Aug 2014, at 00:07, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> compilation notifications... we used a popper interface to show the error >> without >> affecting the underlying text editor: > > Thank god! At least it used to be highlighted so you could delete it easily, > but now we don't even have that. Any chance this could be ported easily to > Pharo core? +1 Please > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/rethinking-compilation-notifications-tp4771635p477164… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 4, 2014

Re: [Pharo-users] rethinking compilation notifications

by Guillermo Polito

Just <3 Le 3 aoÃ»t 2014 22:09, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > Hi, > > The next stop in our little tour around code actions was the compilation > notifications. Again, we used a popper interface to show the error without > affecting the underlying text editor: > > [image: Inline image 2] > > You can find more details here: > > http://www.humane-assessment.com/blog/rethinking-compilation-notifications-… > > Please let us know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Aug. 4, 2014

Re: [Pharo-users] rethinking compilation notifications

by Sean P. DeNigris

Tudor Girba-2 wrote > compilation notifications... we used a popper interface to show the error > without > affecting the underlying text editor: Thank god! At least it used to be highlighted so you could delete it easily, but now we don't even have that. Any chance this could be ported easily to Pharo core? ----- Cheers, Sean -- View this message in context: http://forum.world.st/rethinking-compilation-notifications-tp4771635p477164… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 3, 2014

rethinking compilation notifications

by Tudor Girba

Hi, The next stop in our little tour around code actions was the compilation notifications. Again, we used a popper interface to show the error without affecting the underlying text editor: [image: Inline image 2] You can find more details here: http://www.humane-assessment.com/blog/rethinking-compilation-notifications-… Please let us know what you think. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 3, 2014

Re: [Pharo-users] Syncing local cache and SmalltalkHub

by Offray Vladimir Luna CÃ¡rdenas

Juan, Ben and Stef, Thanks. I tested first Ben's suggestion but Juan's seems to work better (first one gave me an error... don't remember well which one). Now I have my repo online: http://smalltalkhub.com/#!/~Offray/Ubakye When I try to browse the source, I can find .mcz files, but I wonder if there is a way to point to a specific method of an specific version and see it online. Cheers, Offray On 08/02/2014 05:10 PM, Juan Ignacio Vaccarezza wrote: > Hi Offray, > > I recently faced the same problem, the way I solved it by using Gofer to sync > the repos. > > go := Gofer new. > > go repository: (MCSmalltalkhubRepository > owner: 'You' > project: 'yourProjectName' > user: 'userName' > password: 'yourSecretPass'). > > go package: 'PackageName'; push. > > > I got the example from here: > http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Gofer.pdf > > Hope it helps. > > Regards, > Juan > > > > On Sat, Aug 2, 2014 at 5:02 PM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > Hi Offray, > > Once you create your StHub repository and define it in your image, you can > just copy versions (mcz files) from your package cache to the new repository > using the Copy button in the Repository browser (which you get by selecting > your local package cache in the Monticello browser and clicking the Open > button). > > HTH, > > Sven > > On 02 Aug 2014, at 21:25, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net > <mailto:offray@riseup.net>> wrote: > > > Hi, > > > > I have my outliner buggy mockup on local cache, and I would like to share > the code and point to it online using SmalltalkHub for my questions. I have > followed the chapter on Source code management with Monticello y PBE2, and > it says that you can have your code on SmalltalkHub, but says nothing about > how to sync from local cache to your SmalltalkHub account. Can some one > could point me the way to do it? > > > > Cheers, > > > > Offray > > > > >

Aug. 3, 2014

Re: [Pharo-users] Syncing local cache and SmalltalkHub

by Ben Coman

Offray Vladimir Luna CÃ¡rdenas wrote: > Hi, > > I have my outliner buggy mockup on local cache, and I would like to > share the code and point to it online using SmalltalkHub for my > questions. I have followed the chapter on Source code management with > Monticello y PBE2, and it says that you can have your code on > SmalltalkHub, but says nothing about how to sync from local cache to > your SmalltalkHub account. Can some one could point me the way to do it? > > Cheers, > > Offray > > There is no sync function, but if you open your local repository you can use the 'Copy' button to push to SmalltalkHub. Note that while the usual 'Save' button will prompt for your credentials if you haven't configured them, 'Copy' will not prompt and you need to have configured them, via 'Edit' from the context menu of the repository. cheers -ben

Aug. 3, 2014