bouncyferret / nops Goto Github PK

Use /fonts/font.map to switch font after each launch, selecting randomly from /csvs/fonts.csv

Bonus:
Random font per "type", see /config/resources file. We could set it per element instead having the same font everywhere.

https://www.sidefx.com/forum/topic/29783/

could be useful

To make sure that NOPs™ is ran in a clean environment prepare some startup scripts for each platform.
Only start if houdini20 is installed?

I'm finding myself needing to generate random stuff and I think it'd be nice to start a file with random functions etc

This kinda shit is tedious to write so I think I'm gonna make functions that you can call to make that easier
let me know what you think

Launch scripts that makes sure that Houdini is launched with a clean slate, only loading NOPs™

• No other packages
• No user config files
• No custom houdini.env

Finish launch scripts for each platform

• - linux
• - windows
• - mac

Ophiding a ton of common nodes : box, sphere, copytopoints
could think about ophiding anything that isnt a python,wrangle or opencl sop

We should have some promotional material to get more eyes on the release.

Ideas:

• Tease it with some vague images e.g. MLOPs
• Release a fake tutorial where everything goes wrong
• Some sexy promo video, camera sailing over monitor showing the sexy pixels (Comic sans UI font)
• Get some other people to hype it up on twitter (SquidBean, Mestela . . .)

Nothing that should take too long

Launch flipbooks for no reason at random times

Shuffle/swap panes tabs around.

Trigger at random intervals using QTimer to to schedule the changes.

Spawn network dots in the network, make them built stuff ? maybe just spell out NOPs or something

Using hou.ParameterEditor.filter* to hide or expose EVERYTHING

Exposing everything should be especially fun for mega nodes such as attribute adjust/noise, material fracture etc.

Nodes try to hide outside the network view.

https://www.youtube.com/watch?v=3f53T2-vmy4&

link to his git in the description

rotating nodes is a cool one

Procedural to mess up renders because fun and techy and nerdy

so when you cache a file or go to render, it first opens browser + rick roll ?
dont know how feasible this is

Some ideas for how to mess with node shapes

1. Have the node shape be random for each node or just sometimes
2. Node shape(s) that have the inputs backwards order
3. Node shape(s) that have only outputs, only inputs or neither
4. Mega huge nodes somehow? Tiny?

So I think the user should be able to choose how horrible his experience is. Like we'd have an env var define in the package that would define the frequency of the annoying stuff maybe ?
1 Nightmare
2 I love Pain
3 Stroke Inducing

names to be determined (wip)

Some Cool Messages here, maybe some stats, something dynamic would be cool

Let's try and follow these rules

variable names are snake case : my_variable = "snek"

functions/methods are camelcase and start with a capital : mycoolobject.GetAllTheNops()

prefix to all modules should be lowercase nops : nops_utils ; nops_desktop

if the package is multiple words, use camelcase : nops_nodeUtils

type annotations make pythonistas feel cooler so lets use them : MyCoolFunction (node : hou.Node) -> str :

some light reading about type annotations : https://docs.python.org/3/library/typing.html

keep OnCreated and all the Houdini files clean ; write custom functions in their respective .py file : nops_nodeUtils, nops_paneShuffle

Say you want to set the group parameter on a wrangle, when you accept your string gets sent to the vex snippet instead.

Would be great to shuffle toggles

A nops_config.toml to control some base settings.
Right now only used to control if font is randomized or not,

Ideas:

• Store current difficulty #11

what it says

At random intervals have some or all nodes get repelled by the cursor.
Secondary mode could be that they are attracted to the cursor instead.