alyssarosenzweig / upresent Goto Github PK

• Add support for Windows

In certain (unknown) conditions, bullet points will be visible in presentations despite transitions being enabled, resulting in an odd, inverted behaviour of the transitions.

See #9

Hopefully a pretty one with a screenshot ( http://hardmath123.github.io/terminal-screenies.html ) :)

Realistically, a node.js command-line application is awesome but there should be nicer front-end. Most notably, as nearley runs in-browser, some sort of lightweight markdown editor in the browser would be nice.

Thoughts?

It's worth noting _ **text** _ works

Umm, now it does stuff like

    <div class='slide' id='slide1'>
        <ul>
            <h1> Etymology</h1>
            <p>
                <li>Likely comes from <em>Latin</em></li>
            </p>
            <p>
                <li>Might also come from <em>Greek</em></li>
            </p>
            <p>
                <li>Some even believe it originates from <strong>German</strong></li>
            </p>
            <p>So this should be a paragraph, not included in the UL tag.</p>
            <p>
                <li>That was a lie.</li>
            </p>
        </ul>
    </div>

Input being

-----------------
# Etymology

~ Likely comes from _Latin_
~ Might also come from _Greek_
~ Some even believe it originates from **German**

So this should be a paragraph, not included in the UL tag.

~ That was a lie.

To be clear, I expect it to print out something like:

    <div class='slide' id='slide1'>

            <h1> Etymology</h1>
<ul>
                <li>Likely comes from <em>Latin</em></li>
                <li>Might also come from <em>Greek</em></li>
                <li>Some even believe it originates from <strong>German</strong></li>
</ul>
            <p>So this should be a paragraph, not included in the UL tag.</p>
<ul>
                <li>That was a lie.</li>
</ul>
    </div>

(Sorry about the bad indentation, but you get it, right?)

Pressing F1-F12 moves to the next slide instead of performing the key's intended function.

The Ελληνικά letter μ sounds like /moo/ so isn't it pronounced /moo present/? lol 😋

The grammar needs a cleanup (again)... I broke something, again, it seems.

Once #7 is completed, we should be able to pick from multiple CSS templates easily

Not sure what settings @Hardmath123 uses, but there's a lot of inconsistencies which is ugly. We probably need a style guide for the project.

• Proper ul/li-based lists
• Proper slide navigation, using arrow keys, so that I can go forward and back. It needs to work with one of those wireless clickey things that speakers on stage use.
• Use p tags instead of brs all over the place.
• Use em for italics and strong for bold, instead of b and i tags. b and i are deprecated, and I can control typography better with em and strong.
• I'll take care of prettifying the CSS.

Tested in Firefox/Iceweasel 38.0.1

You should make an organization for all the sources and the site. lol

Currently cuts off last charcaters

At the moment, publish.js works for testing as a developer, but not for actually publishing. A few improvements come to mind:

• Optionally minify HTML, JS, and CSS in output
• Optionally embed the accompanying JS and CSS into the HTML for single file distribution
• Refactor publisher to be cleaner and to work with browser JavaScript; see #18
• Integration with some sort of uploading service?

Any thoughts would be appreciated

• Natural syntax for slide transitions for the entire presentation
• Syntax to override transitions on a per-slide basis
• Generic CSS3 Slide Transition Setup
• Slide from all 8 core directions
• Fade in / out

E.g.: if there exists a list:

~ A
~ B
~~ B2
~ C

Only A should show up when the slide is changed. B should only show up when the slide is clicked again, etc.

Images are supported; hyperlinks should be too.

Both named links and "automatic" links should work.

This enables linking and the browser back button to work as expected.

(labels are only 20% satirical)

uPresent should be pretty out of the box.

My wireless clicker has a button for it!

Specifically, browser fullscreen is awkward as the address bar doesn't match the presentation, in addition to taking up space. A simple key command (or button press on the clicker) should toggle true fullscreen mode.

See #8 for desire as well as #16 for implications on uPresent itself