Let us talk here!

(Related: this comment)

I think it would be nice if there was some shorthand for pyfancy().parse("...") because it seems like it's a really useful function for static text, such as in a text-based game (e.g. things like pyfancy().parse("You open your {bold,green INVENTORY}").output())

I'm not quite sure what a good shorthand name would be, or if we would want shorthand names for other functions too, or maybe if we would want to leave creating these functions to the user rather than the library (after all, it's not particularly hard to implement).

Thoughts?

It would be nice to have an actual testing framework implemented that runs on our TravisCI script. We really don't care which one is used.

This should test all of the colors and functionality of the Pyfancy 2 library.

What are you requesting?

We should have this published on pip so it can be more accessible.

Moved from TheMonsterFromTheDeep#8

I want to start thinking about creating the next version of Pyfancy. Just some things I want to do. Instead of just styling the terminal I now want Pyfancy to work for all things terminal such as progress bars, menus and better inputs. I also want it to be cross-compatible and light weight.

• Better formatting based on bbcode or markdown.
• Progress bars
• Menu select
• Long console prints with "scroll bars"
• Plugins?

Also some non-coding things:

• Better website
• Pip (finally)
• Better review system
• Cleaner file system

Problem Template

#31 is not working so I need to remove pip stuff until I can fix it

A user @joker314 sugested a rewrite that instead of pyfancy.<color> do <color>(). Tell me how you guys think about this...

Note this would be Pyfancy 2.0!

What SHOULD happen?

Import should be parsed.

What DOES happen?

Import is printed

Steps to reproduce

1. Run demo in travis

Python version and OS

Travisci
Python 2.7 and MacOS High Siera

Other (logs, code or anything else that is important)

Two things:

a) Please may I be added to the repo
b) Make sure we use the peer-reviewed pull request system, how about one person must review your code before it is merged?

I'm not suuuper concerned about this, but the current credit, which simply points to the contributions graph, puts me as one of the smallest contributors to the project, which makes me a little uncomfortable, as I have contributed most of the current codebase.

I'm not actually entirely sure how the contribution graph got to the place that it is.

Perhaps the document should also link to the graph for my fork, which is where a lot of the current code comes from?

Is there any more colors available to the terminal? If there are can we add more to pyfancy?

I guess we are working on this again so I guess we need to lay out how to contribute.

• Every PR must be reviewed by one other person at the least before getting merged.
• Proper tags must be used for organization + communication reasons.
• Travis must pass before merging (after I fix it).
• If you want to tackle an issue assign yourself or if you want to suggest someone else assign them.

Anything else?

Tagging @TheMonsterFromTheDeep @joker314 @Jonathan50

What are you requesting?

It would be great if the pyfancy parsing also had basic markdown/bbcode or other markup language support.
Related #36

How could this be implemented.

pyfancy("#Bold").output()

pyfancy().parse("[color=red]RED![/color]")

after run demo(), the following error came out in Python 2.7 or 3.5 on Mac El Capitan

File "<stdin>", line 1, in <module>
  File "pyfancy/pyfancy.py", line 27, in <module>
    get = idleorcommandline()
  File "pyfancy/pyfancy.py", line 17, in idleorcommandline
    c = a[b - 1]
IndexError: string index out of range

What are you requesting?

Ability to easily import text files with the parse codes in them.

How could this be implemented.

pyfancy().import("format.txt").output()

I got #1 when I ran import * from pyfancy inside of python:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "pyfancy.py", line 27, in <module>
    get = idleorcommandline()
   File "pyfancy.py", line 17, in idleorcommandline
    c = a[b - 1]
IndexError: string index out of range

Moved from TheMonsterFromTheDeep#14

Do you have one? Where is it found, there should be a licence file and a comment at the top of every pertinent (how do you spell pertanant?) file

What are you requesting?

We have implemented pyfancy("stuff to parse") should we remove .parse()?

What are you requesting?

Make a function that simply clears the output just in case for some reason you need to use the same chain.

How could this be implemented.

Really easy working on PR

• We have added multiple features that have not appeared in the readme.md yet.