Go present questions

[Tong Sun]

Hi, 

Some questions regarding Go present. 

First, it doesn't support nested bullets, right, like the following?

- bullets

- more bullets

- more bullets with nested bullets

  - bullets

  - bullets

I think such nested bullets is a fundamental requirement for presentations. Hope it will be added soon. 

Second, what would you think the following should come out as? 

-------------------------------------

* Title three

** Subsection

- bullets `code`

- more bullets

- a bullet with

** Sub-subsection

Some More text

- more bullets

- more bullets

-------------------------------------

I found the outcome is totally surprising: http://go-talks.appspot.com/github.com/suntong001/lang/lang/Go/src/text/slide-subsection-test.slide#4

Even this one is not delivered as anticipated:

-------------------------------------

* Title two

** Subsection

- bullets `code`

- more bullets

- a bullet with

*** Sub-subsection

Some More text

- more bullets

- more bullets

-------------------------------------

http://go-talks.appspot.com/github.com/suntong001/lang/lang/Go/src/text/slide-subsection-test.slide#3

The order of "Subsection" and "Sub-subsection" is wrong. 

Comments? 

The slide source is at

https://github.com/suntong001/lang/blob/master/lang/Go/src/text/slide-subsection-test.slide

Thanks

[HaWe]

Hi,
I noticed the same, some time ago.
When I recall correctly, **Subsection and ***Sub-subsection only work for '.article' files and not for slides.
IMO that's ok; **Subsection and ***Sub-subsection are way too complicated for slides.

[Egon]

I think it's good that it doesn't support bullet nesting, it's too complicated for a slide&talk. Same for sub-sub sections.

If you want to use more complicated structure, then use some other medium that works better, e.g. blog post, article.

+ Egon

[Andrew Gerrand]

As the other have said, present doesn't support nested bullets, and the slide output of present doesn't support sub-sections.

The former is by design (for better or worse). The latter is mostly that it was never implemented, as I've never needed it. When you find yourself reaching for a sub-section, ask yourself whether you're putting too much information on a slide.

There's an open issue to fix the latter problem: https://github.com/golang/go/issues/11434

Andrew

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Kortschak]

On Mon, 2015-06-29 at 11:23 +1000, Andrew Gerrand wrote:
> The latter is mostly that it was never implemented, as I've never
> needed it.

> When you find yourself reaching for a sub-section, ask yourself
> whether you're putting too much information on a slide.

This is the right answer, though possibly present should fail more
noisily when there are two subsection stanzas on a slide.

[Gonzalo Serrano]

5 years later, I just hacked some ASCII bullets and non-standard spaces like this:

* More DDD

*Strategical* *patterns*

- Bounded Context

- Ubiquitous Language

*Tactical* *patterns*

●   Entities: do the stuff, generate events

●   Repositories: abstract the persistence ops

●   Aggregates: transactional clusters of entites

      ●   keep them small

      ●   refer other aggregates by ID

      ●   change 1 aggregate per Tx

      ●   persist entities + events in the same Tx (Transactional Outbox pattern)

: aggregate design is sometimes hard

: need to thin about what can be eventual consistent

: need to talk to frontend/PO

Looks good enough to me.