Re: [Pharo-users] Make Smalltalk Great Again!

2016-10-21 Thread p...@highoctane.be
Nice. A mention of PharoJS makes sense in it as you mention Amber and PharoJS is another option. Not sure I want to make Smalltalk great "again" but we've been through this a few times. Phil On Sat, Oct 22, 2016 at 3:03 AM, horrido wrote: > Today, my Smalltalk article at TechBeacon >

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Dimitris Chloupis
Yeah I agree the format is unreadable for github users .The reason is like that is that it makes merges more fine grained. Indeed a fileout will give you what you want. You can also use gist which will make it easier for them to view and you won't have to version control it. The playground also ha

[Pharo-users] Make Smalltalk Great Again!

2016-10-21 Thread horrido
Today, my Smalltalk article at TechBeacon surpassed 17,000 page views!!! I am so proud. My message has reached far more businesses and IT professionals than I could've possibly imagined! (TechBeacon is a “digital hub” f

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Charlie Robbats
I'd like to suggest you teach people Smalltalk natively, so they don't get distracted by the false view of a filetree of classes. One huge differentiator of Smalltalk, from any other language out there, is the live object environment. You should use that environment to teach from or the nuance

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Martin McClure
On 10/21/2016 05:51 PM, Vitor Medina Cruz wrote: > Thank you for the answers! Actually my question has a rather silly > reason: I find it difficult to navigate and peek at code in the current > format. I would like to show ST code to other people through GitHub — it > is pretty common for me to dis

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Vitor Medina Cruz
Thank you for the answers! Actually my question has a rather silly reason: I find it difficult to navigate and peek at code in the current format. I would like to show ST code to other people through GitHub — it is pretty common for me to discuss implementations of katas, for example, from multiple

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Dimitris Chloupis
Do you have something specific in your mind ? What are your needs and desires for an alternate Filetree format ? What you want to see changed in Filetreee ? On Fri, Oct 21, 2016 at 7:02 PM Vitor Medina Cruz wrote: > Hello, > > I was wondering: is there another format available for Filetree? > >

Re: [Pharo-users] Other format to Filetree

2016-10-21 Thread Martin McClure
Vitor Medina Cruz wrote: > I was wondering: is there another format available for Filetree? Hi Vitor, I'm not sure exactly what you're looking for. The current package formats in Pharo are, as you probably know, Filetree and MCZ (Monticello archives). I find Filetree easier to use, managing sou

[Pharo-users] Other format to Filetree

2016-10-21 Thread Vitor Medina Cruz
Hello, I was wondering: is there another format available for Filetree? Regards, Vitor

Re: [Pharo-users] Understanding Pillar

2016-10-21 Thread Dimitris Chloupis
Next question is it possible to have separate pillar files generate separate HTML so I can have multiple {{{content}}} instead of one big one ? On Fri, Oct 21, 2016 at 3:58 PM Dimitris Chloupis wrote: > Ok found a solution in pillar documentation > On Fri, 21 Oct 2016 at 14:12, Dimitris Chloupis

Re: [Pharo-users] Understanding Pillar

2016-10-21 Thread Dimitris Chloupis
Ok found a solution in pillar documentation On Fri, 21 Oct 2016 at 14:12, Dimitris Chloupis wrote: > So I feel andventurous and decided to use Pillar to make my personal > website > > I have started using the welcome example and I see that ! creates a > heading but also adds a number to it probab

[Pharo-users] Understanding Pillar

2016-10-21 Thread Dimitris Chloupis
So I feel andventurous and decided to use Pillar to make my personal website I have started using the welcome example and I see that ! creates a heading but also adds a number to it probably to mark chapters, sections etc Is there a way to avoid this numbering and still have a header ?