date:20160917

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

2016-09-17 Thread stepharo

Le 17/9/16 à 08:21, Tudor Girba a écrit :

Hi,

Great. I also started to use it, and I would be interested in working also on
creating a webpage out of the box.

It is also unclear to me how to deal with pillar.conf (I did not look at the
code yet.). Should I rely on a book.pillar root class that embeds the chapter
files? Or is there a way to still rely on a declarative way like we had in
pillar.conf to embed those files?

Hi doru

I did not try yet. My plan is to migrate all my books to archetype and
pillar 40.

I hope to get some time to try today.

Stef

Cheers,
Doru

On Sep 16, 2016, at 10:02 PM, Damien Pollet wrote:

Yes, I will first cleanup the one in the book archetype, and unify it with the
Enterprise & Spec books, since they seem to be the most up-to-date with Pillar.

On 16 September 2016 at 21:19, stepharo wrote:
Damien Pollet started to have a look at the makefile and this is on my todo to
try.

Stef

Le 15/9/16 à 00:13, Johan Fabry a écrit :

Hi Doru,

it looks like there’s a problem with copySupport.mk, I had the same problem
with the Spec booklet. The file is using Linux only syntax for the cp command.
This was fixed for the Spec booklet after I raised an issue there, but it seems
the fix was not propagated everywhere it needs to be. Have a look at
https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/copySupport.mk
and try to update your copySupport, it may fix your problem.

--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please
see http://emailcharter.org .

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD and RyCh labs - Computer Science Department (DCC) - University of
Chile

On Sep 14, 2016, at 18:40, Tudor Girba wrote:

Hi,

Ok, I found this document:
https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html

And now I tried this:

wget --no-check-certificate
https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh
chmod +x download.sh
./download.sh
./pillar archetype book

and I got the book template. But, I do not know how to compile the book. I tried

make

or
make book

but I get:

make
mkdir -p ./book-result
find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp {}
--parents -r ./book-result \;
cp: ./Chapters/Chapter1/figures is a directory (not copied).
cp: --parents: No such file or directory
cp: -r: No such file or directory
cp: ./figures is a directory (not copied).
cp: --parents: No such file or directory
cp: -r: No such file or directory
cp: ./support/figures is a directory (not copied).
cp: --parents: No such file or directory
cp: -r: No such file or directory
cp -r support/ ./book-result
cp .latexmkrc ./book-result
cp: .latexmkrc: No such file or directory
make: *** [copySupport] Error 1

I must be doing something wrong, but I do not know what. I am on a Mac 10.11
and I am using bash. Could someone point me in the right direction?

Cheers,
Doru

On Sep 14, 2016, at 10:49 PM, Tudor Girba wrote:

Hi,

Where can I find the new template system for Pillar?

Cheers,
Doru

On Jul 22, 2016, at 3:41 PM, Thibault ARLOING
wrote:

Hello,

I'm happy to announce the latest release of Pillar.
This release has been possible because of the hard work of Damien Cassou, Cyril
Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek.
What did it bring and what are the largest changes ?

• Huge cleaning of code and Dependencies
• Many bug fixes
• Huge refactoring of internal parts
• Extract phase management into an external project
(LightPhaser)
• Transformers and Phases are all Pipes
Remove Compilation cycle
• Remove template handling from Pillar
• Remove generation of pillarpostExport.sh
• Pillar now exports files to JSON format
• Command for pillar archetypes "./pillar archetype book", book can be
replaced by other archetype names (see Pillar documentation)
• Possibility to load an archetype with a Makefile to compile pillar
files
Features
• Check phase to check syntax
• EPub exporter for e-books (use pillar archetypes for this)
• Semantic links to Youtube and Wikipedia
• Citations for LaTeX
• Structures (see Pillar documentation)
• Footnotes for HTML, Markdown, LaTeX and AsciiDoc
• Improvement of parsing configuration failure message
Major changes
• Metadata field in configuration to separate data from configuration
properties
• Support files in configuration does no longer exists
• "disableTransformers" property is now named "disabledPhases"
• AsciiDoc file extension is now ".asciidoc"
• Pillar now manages one

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

2016-09-17 Thread Damien Pollet

I think the book.pillar root file is the way.

On 17 September 2016 at 08:21, Tudor Girba  wrote:

> Hi,
>
> Great. I also started to use it, and I would be interested in working also
> on creating a webpage out of the box.
>
> It is also unclear to me how to deal with pillar.conf (I did not look at
> the code yet.). Should I rely on a book.pillar root class that embeds the
> chapter files? Or is there a way to still rely on a declarative way like we
> had in pillar.conf to embed those files?
>
> Cheers,
> Doru
>
>
> > On Sep 16, 2016, at 10:02 PM, Damien Pollet 
> wrote:
> >
> > Yes, I will first cleanup the one in the book archetype, and unify it
> with the Enterprise & Spec books, since they seem to be the most up-to-date
> with Pillar.
> >
> > On 16 September 2016 at 21:19, stepharo  wrote:
> > Damien Pollet started to have a look at the makefile and this is on my
> todo to try.
> >
> >
> > Stef
> >
> >
> > Le 15/9/16 à 00:13, Johan Fabry a écrit :
> >
> > Hi Doru,
> >
> > it looks like there’s a problem with copySupport.mk, I had the same
> problem with the Spec booklet. The file is using Linux only syntax for the
> cp command. This was fixed for the Spec booklet after I raised an issue
> there, but it seems the fix was not propagated everywhere it needs to be.
> Have a look at https://github.com/SquareBracketAssociates/
> BuildingUIWithSpec/blob/master/copySupport.mk and try to update your
> copySupport, it may fix your problem.
> >
> > --
> > Does this mail seem too brief? Sorry for that, I don’t mean to be rude!
> Please see http://emailcharter.org .
> >
> > Johan Fabry   -   http://pleiad.cl/~jfabry
> > PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -
> University of Chile
> >
> > On Sep 14, 2016, at 18:40, Tudor Girba  wrote:
> >
> > Hi,
> >
> > Ok, I found this document:
> > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/
> lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html
> >
> > And now I tried this:
> >
> > wget --no-check-certificate https://raw.githubusercontent.
> com/pillar-markup/pillar/master/download.sh
> > chmod +x download.sh
> > ./download.sh
> > ./pillar archetype book
> >
> > and I got the book template. But, I do not know how to compile the book.
> I tried
> >
> > make
> >
> > or
> > make book
> >
> > but I get:
> >
> > make
> > mkdir -p ./book-result
> > find . -type d -path ./book-result -prune -o -wholename "*/figures"
> -exec cp {} --parents -r ./book-result \;
> > cp: ./Chapters/Chapter1/figures is a directory (not copied).
> > cp: --parents: No such file or directory
> > cp: -r: No such file or directory
> > cp: ./figures is a directory (not copied).
> > cp: --parents: No such file or directory
> > cp: -r: No such file or directory
> > cp: ./support/figures is a directory (not copied).
> > cp: --parents: No such file or directory
> > cp: -r: No such file or directory
> > cp -r support/ ./book-result
> > cp .latexmkrc ./book-result
> > cp: .latexmkrc: No such file or directory
> > make: *** [copySupport] Error 1
> >
> >
> > I must be doing something wrong, but I do not know what. I am on a Mac
> 10.11 and I am using bash. Could someone point me in the right direction?
> >
> > Cheers,
> > Doru
> >
> >
> > On Sep 14, 2016, at 10:49 PM, Tudor Girba  wrote:
> >
> > Hi,
> >
> > Where can I find the new template system for Pillar?
> >
> > Cheers,
> > Doru
> >
> >
> > On Jul 22, 2016, at 3:41 PM, Thibault ARLOING <
> thibault.arlo...@hotmail.fr> wrote:
> >
> > Hello,
> >
> > I'm happy to announce the latest release of Pillar.
> > This release has been possible because of the hard work of Damien
> Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek.
> > What did it bring and what are the largest changes ?
> >
> > • Huge cleaning of code and Dependencies
> > • Many bug fixes
> > • Huge refactoring of internal parts
> > • Extract phase management into an external project
> (LightPhaser)
> > • Transformers and Phases are all Pipes
> > Remove Compilation cycle
> > • Remove template handling from Pillar
> > • Remove generation of pillarpostExport.sh
> > • Pillar now exports files to JSON format
> > • Command for pillar archetypes "./pillar archetype book", book
> can be replaced by other archetype names (see Pillar documentation)
> > • Possibility to load an archetype with a Makefile to compile
> pillar files
> > Features
> > • Check phase to check syntax
> > • EPub exporter for e-books (use pillar archetypes for this)
> > • Semantic links to Youtube and Wikipedia
> > • Citations for LaTeX
> > • Structures (see Pillar documentation)
> > • Footnotes for HTML, Markdown, LaTeX and AsciiDoc
> > • Improvement of parsing

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

2016-09-17 Thread Tudor Girba

Hi,

Great. I also started to use it, and I would be interested in working also on 
creating a webpage out of the box.

It is also unclear to me how to deal with pillar.conf (I did not look at the 
code yet.). Should I rely on a book.pillar root class that embeds the chapter 
files? Or is there a way to still rely on a declarative way like we had in 
pillar.conf to embed those files?

Cheers,
Doru


> On Sep 16, 2016, at 10:02 PM, Damien Pollet  wrote:
> 
> Yes, I will first cleanup the one in the book archetype, and unify it with 
> the Enterprise & Spec books, since they seem to be the most up-to-date with 
> Pillar.
> 
> On 16 September 2016 at 21:19, stepharo  wrote:
> Damien Pollet started to have a look at the makefile and this is on my todo 
> to try.
> 
> 
> Stef
> 
> 
> Le 15/9/16 à 00:13, Johan Fabry a écrit :
> 
> Hi Doru,
> 
> it looks like there’s a problem with copySupport.mk, I had the same problem 
> with the Spec booklet. The file is using Linux only syntax for the cp 
> command. This was fixed for the Spec booklet after I raised an issue there, 
> but it seems the fix was not propagated everywhere it needs to be. Have a 
> look at 
> https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/copySupport.mk
>  and try to update your copySupport, it may fix your problem.
> 
> --
> Does this mail seem too brief? Sorry for that, I don’t mean to be rude! 
> Please see http://emailcharter.org .
> 
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
> Chile
> 
> On Sep 14, 2016, at 18:40, Tudor Girba  wrote:
> 
> Hi,
> 
> Ok, I found this document:
> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html
> 
> And now I tried this:
> 
> wget --no-check-certificate 
> https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh
> chmod +x download.sh
> ./download.sh
> ./pillar archetype book
> 
> and I got the book template. But, I do not know how to compile the book. I 
> tried
> 
> make
> 
> or
> make book
> 
> but I get:
> 
> make
> mkdir -p ./book-result
> find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec cp 
> {} --parents -r ./book-result \;
> cp: ./Chapters/Chapter1/figures is a directory (not copied).
> cp: --parents: No such file or directory
> cp: -r: No such file or directory
> cp: ./figures is a directory (not copied).
> cp: --parents: No such file or directory
> cp: -r: No such file or directory
> cp: ./support/figures is a directory (not copied).
> cp: --parents: No such file or directory
> cp: -r: No such file or directory
> cp -r support/ ./book-result
> cp .latexmkrc ./book-result
> cp: .latexmkrc: No such file or directory
> make: *** [copySupport] Error 1
> 
> 
> I must be doing something wrong, but I do not know what. I am on a Mac 10.11 
> and I am using bash. Could someone point me in the right direction?
> 
> Cheers,
> Doru
> 
> 
> On Sep 14, 2016, at 10:49 PM, Tudor Girba  wrote:
> 
> Hi,
> 
> Where can I find the new template system for Pillar?
> 
> Cheers,
> Doru
> 
> 
> On Jul 22, 2016, at 3:41 PM, Thibault ARLOING  
> wrote:
> 
> Hello,
> 
> I'm happy to announce the latest release of Pillar.
> This release has been possible because of the hard work of Damien Cassou, 
> Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek.
> What did it bring and what are the largest changes ?
> 
> • Huge cleaning of code and Dependencies
> • Many bug fixes
> • Huge refactoring of internal parts
> • Extract phase management into an external project 
> (LightPhaser)
> • Transformers and Phases are all Pipes
> Remove Compilation cycle
> • Remove template handling from Pillar
> • Remove generation of pillarpostExport.sh
> • Pillar now exports files to JSON format
> • Command for pillar archetypes "./pillar archetype book", book can 
> be replaced by other archetype names (see Pillar documentation)
> • Possibility to load an archetype with a Makefile to compile pillar 
> files
> Features
> • Check phase to check syntax
> • EPub exporter for e-books (use pillar archetypes for this)
> • Semantic links to Youtube and Wikipedia
> • Citations for LaTeX
> • Structures (see Pillar documentation)
> • Footnotes for HTML, Markdown, LaTeX and AsciiDoc
> • Improvement of parsing configuration failure message
> Major changes
> • Metadata field in configuration to separate data from configuration 
> properties
> • Support files in configuration does no longer exists
> • "disableTransformers" property is now named "disabledPhases"
> • AsciiDoc file extension

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

2016-09-17 Thread Tudor Girba

Hi,

> On Sep 16, 2016, at 8:37 PM, stepharo  wrote:
> 
> + 1
> 
> Changing the language metamodel for simple validated comments is a huge 
> effort for nothing. 
> Clement is good at VM level but not at other level :)

I think there is a misunderstanding :). I do not see any implication to the 
language meta-model in the remark of Clement.

In fact, I expressed exactly the same opinion, that the design of things like 
PythonDoc comes from the fact that those people do not rely on an IDE, so their 
design focuses on the only thing they have: source code. Clement remarked that 
we already have SUnit tests and he suggested that we could just enhance the IDE 
to present them next to the methods. This might actually be less 
straightforward with SUnit because it was not made for preserving links to the 
code, but it can work out of the box with something like GTExamples.

Cheers,
Doru

> Stef
> 
> Le 16/9/16 à 14:18, Denis Kudriashov a écrit :
>> 
>> 2016-09-16 13:42 GMT+02:00 Clément Bera :
>> Why don't you just change nautilus to have two text areas, one with the test 
>> corresponding to the method and the other one with the method's code ? 
>> 
>> You're saying:
>> Their values is active documentation that can be automatically validated.
>> That can also be applied to test we've already had with SUnit. If the only 
>> difference you want is to display the test next to the method, then it's an 
>> IDE problem, nothing has to be changed but the IDE.
>> 
>> In python they have no other choices than putting tests in comments because 
>> their IDE is a text editor, they cannot create other panes or anything like 
>> that.
>> 
>> It is of course true. But Stef suggestion is really much much simpler. It is 
>> just convention how to write examples inside comments. Then tools could work 
>> with them and Nicolai already provide simple extension for Nautilus.
>> We already has a lot of comments with examples inside. Making them 
>> discoverable and testable will be nice. 
>> 
> 

--
www.tudorgirba.com
www.feenk.com

"Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

2016-09-17 Thread stepharo




Le 16/9/16 à 21:58, Damien Pollet a écrit :
On 16 September 2016 at 20:42, stepharo > wrote:


Daemons of over-engineering are tempting us because this is cooler
to to design something complex.


Dreaming of crazy features is a good thing. Talking from experience, I 
prefer that to not dreaming, which is pretty dull.


Yes now create a thread:
the dreams for a cool documentation system in Pharo and I will 
follow and add to it happily,
What I was asking in this thread is how can we catch a low hanging fruit 
and get an immmediate impact because it looks

so easy to do.

Stef


And over-engineering is of course the wrong path. But the temptation 
to do so is revealing of where the system is too complex.


--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

Re: [Pharo-dev] [Pharo-users] [ANN] Pillar 4.0.0

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest

5 matches

Site Navigation

Mail list logo

Footer information