Tables in Pillar

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Tables in Pillar

philippeback
How is one doing a cell with content wrapping on multiple lines?

With the

| X | Y
| abcd | some very long text that should be wrapping but apparently
doesn't. So it is very annoying when one attempts to describe a long
thing, which is one purpose for a table.

I get one single line for each entry.

How to do that?

TIA
Phil

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

stepharo
I do not think that you can since pillar is line based.


Le 27/2/15 09:05, [hidden email] a écrit :

> How is one doing a cell with content wrapping on multiple lines?
>
> With the
>
> | X | Y
> | abcd | some very long text that should be wrapping but apparently
> doesn't. So it is very annoying when one attempts to describe a long
> thing, which is one purpose for a table.
>
> I get one single line for each entry.
>
> How to do that?
>
> TIA
> Phil
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

philippeback
In reply to this post by philippeback
bump

On Fri, Feb 27, 2015 at 9:05 AM, [hidden email] <[hidden email]> wrote:

> How is one doing a cell with content wrapping on multiple lines?
>
> With the
>
> | X | Y
> | abcd | some very long text that should be wrapping but apparently
> doesn't. So it is very annoying when one attempts to describe a long
> thing, which is one purpose for a table.
>
> I get one single line for each entry.
>
> How to do that?
>
> TIA
> Phil

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Damien Cassou
In reply to this post by philippeback


On Feb 27, 2015 3:06 AM, "[hidden email]" <[hidden email]> wrote:
>
> How is one doing a cell with content wrapping on multiple lines?
>
> With the
>
> | X | Y
> | abcd | some very long text that should be wrapping but apparently
> doesn't. So it is very annoying when one attempts to describe a long
> thing, which is one purpose for a table.
>
> I get one single line for each entry.
>
> How to do that?

That's not possible (but contributions are accepted)

>
> TIA
> Phil
>

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

philippeback

how does one makes that in LaTeX?

Le 5 mars 2015 15:20, "Damien Cassou" <[hidden email]> a écrit :


On Feb 27, 2015 3:06 AM, "[hidden email]" <[hidden email]> wrote:
>
> How is one doing a cell with content wrapping on multiple lines?
>
> With the
>
> | X | Y
> | abcd | some very long text that should be wrapping but apparently
> doesn't. So it is very annoying when one attempts to describe a long
> thing, which is one purpose for a table.
>
> I get one single line for each entry.
>
> How to do that?

That's not possible (but contributions are accepted)

>
> TIA
> Phil
>

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Damien Pollet-2
AFAIK, LaTeX does not wrap text in table cells unless you explicitly fix the column's width.

On 5 March 2015 at 17:21, [hidden email] <[hidden email]> wrote:

how does one makes that in LaTeX?

Le 5 mars 2015 15:20, "Damien Cassou" <[hidden email]> a écrit :


On Feb 27, 2015 3:06 AM, "[hidden email]" <[hidden email]> wrote:
>
> How is one doing a cell with content wrapping on multiple lines?
>
> With the
>
> | X | Y
> | abcd | some very long text that should be wrapping but apparently
> doesn't. So it is very annoying when one attempts to describe a long
> thing, which is one purpose for a table.
>
> I get one single line for each entry.
>
> How to do that?

That's not possible (but contributions are accepted)

>
> TIA
> Phil
>


Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Esteban A. Maringolo
Was this fixed, considered for a roadmap (if there is one), etc?

Regards!
Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Damien Cassou-2
"Esteban A. Maringolo" <[hidden email]> writes:

> Was this fixed, considered for a roadmap (if there is one), etc?

an issue is in the tracker. 2 brilliant students will work on Pillar for
the next 5 months starting next Monday. I'm quite sure we will see a lot
of new stuff.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

NorbertHartl

> Am 31.03.2016 um 12:39 schrieb Damien Cassou <[hidden email]>:
>
> "Esteban A. Maringolo" <[hidden email]> writes:
>
>> Was this fixed, considered for a roadmap (if there is one), etc?
>
> an issue is in the tracker. 2 brilliant students will work on Pillar for
> the next 5 months starting next Monday. I'm quite sure we will see a lot
> of new stuff.

Wow that sounds a lot of things are possible. Do you have a roadmap?

Norbert


Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Damien Cassou-2
Norbert Hartl <[hidden email]> writes:

> Wow that sounds a lot of things are possible. Do you have a roadmap?

There are plenty of things we would like to do:

- clean the issue tracker by doing all the simple things (it's time for
  users to write their ideas there)

- facilitate the creation of new Pillar projects. Currently, it's a hell
  to start a new book or a new lecture.

- simplify Pillar to avoid the current transformation to a build system.
  We want to remove the dependency to the Mustache template engine. We
  also want to remove Pillar's ability to compile LaTeX files to PDF. I
  want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*.
  The rest will move to external projects, reusing as much as possible
  of what's already there (e.g., GNU/Make) and leveraging other tools
  (e.g., other template engines, even not implemented in Pharo).

- refactor and recompose Pillar's source code to break all package
  cycles. Also make sure no new cycle is created in the future by adding
  a check in the test suite.

- add a new XML-based exporter to publish the Mooc on a dedicated
  platform

- take care of all the user's feedback during the internship


--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

stepharo


Le 31/3/16 17:56, Damien Cassou a écrit :

> Norbert Hartl <[hidden email]> writes:
>
>> Wow that sounds a lot of things are possible. Do you have a roadmap?
> There are plenty of things we would like to do:
>
> - clean the issue tracker by doing all the simple things (it's time for
>    users to write their ideas there)
>
> - facilitate the creation of new Pillar projects. Currently, it's a hell
>    to start a new book or a new lecture.
>
> - simplify Pillar to avoid the current transformation to a build system.
>    We want to remove the dependency to the Mustache template engine. We
>    also want to remove Pillar's ability to compile LaTeX files to PDF. I
>    want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*.
>    The rest will move to external projects, reusing as much as possible
>    of what's already there (e.g., GNU/Make) and leveraging other tools
>    (e.g., other template engines, even not implemented in Pharo).
     - Well I would prefer to improve mustache if necessary. Controlling
the stack of external great tools
     is important.
>
> - refactor and recompose Pillar's source code to break all package
>    cycles. Also make sure no new cycle is created in the future by adding
>    a check in the test suite.

     - make a minimal Pillar renderer so that class comment could be
nicely rendered :)
>
> - add a new XML-based exporter to publish the Mooc on a dedicated
>    platform
>
> - take care of all the user's feedback during the internship

- better support for ecstatic

   - epub? :)
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

Damien Cassou-2
stepharo <[hidden email]> writes:

> Le 31/3/16 17:56, Damien Cassou a écrit :
>> Norbert Hartl <[hidden email]> writes:
>>
>>> Wow that sounds a lot of things are possible. Do you have a roadmap?
>> There are plenty of things we would like to do:
>>
>> - clean the issue tracker by doing all the simple things (it's time for
>>    users to write their ideas there)
>>
>> - facilitate the creation of new Pillar projects. Currently, it's a hell
>>    to start a new book or a new lecture.
>>
>> - simplify Pillar to avoid the current transformation to a build system.
>>    We want to remove the dependency to the Mustache template engine. We
>>    also want to remove Pillar's ability to compile LaTeX files to PDF. I
>>    want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*.
>>    The rest will move to external projects, reusing as much as possible
>>    of what's already there (e.g., GNU/Make) and leveraging other tools
>>    (e.g., other template engines, even not implemented in Pharo).

> - Well I would prefer to improve mustache if necessary. Controlling
> the stack of external great tools is important.

The idea is not to make Mustache perfect for every possible use case,
the idea is that users should be able to pick the template engine that
fits best.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: Tables in Pillar

stepharo


Le 3/4/16 10:55, Damien Cassou a écrit :

> stepharo <[hidden email]> writes:
>
>> Le 31/3/16 17:56, Damien Cassou a écrit :
>>> Norbert Hartl <[hidden email]> writes:
>>>
>>>> Wow that sounds a lot of things are possible. Do you have a roadmap?
>>> There are plenty of things we would like to do:
>>>
>>> - clean the issue tracker by doing all the simple things (it's time for
>>>     users to write their ideas there)
>>>
>>> - facilitate the creation of new Pillar projects. Currently, it's a hell
>>>     to start a new book or a new lecture.
>>>
>>> - simplify Pillar to avoid the current transformation to a build system.
>>>     We want to remove the dependency to the Mustache template engine. We
>>>     also want to remove Pillar's ability to compile LaTeX files to PDF. I
>>>     want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*.
>>>     The rest will move to external projects, reusing as much as possible
>>>     of what's already there (e.g., GNU/Make) and leveraging other tools
>>>     (e.g., other template engines, even not implemented in Pharo).
>> - Well I would prefer to improve mustache if necessary. Controlling
>> the stack of external great tools is important.
> The idea is not to make Mustache perfect for every possible use case,

Damien can you read what I wrote?
Did I say make mustache perfect?
No so what is your point?

> the idea is that users should be able to pick the template engine that
> fits best.
and also have a solution that works without relying on a specific tools
runnning
on a single OS and that we cannot debug.

"Je dis juste si mustache a une limitation et qu’elle est facile a enlever
alors c’est mieux d’ameliorer mustache car
     on ameliore mustache
     on amerliore pillar
Et moins on doit maintenir de trucs exterieurs plus on a une solution
perenne.
Je suis sur que si on demande a norbert d’ameliorer mustache il le fera
en plus.

Am I clear?
Now if you do not want that I work and push Pillar tell it to me too and
I can do something
else.
In this moment I'm about to rethink what I want to spend my energy so
pillar could be also
one less.

Stef