» Project Templates
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Project Templates

misc structure stage folder structure project
Credits: focus4 GmbH for my consistent financing :)

about

This is a bit experimental contribution, it needs a discussion, but from my experience it's ultra important and not solved in vvvv at all.
consisting of two parts:

Project Templates

First, using it speeds up your work. That is proved and well tested.
Second, you know the feeling, when you open your patch a month after you created it and have no clue, how a hell could it work? This should help, keeping structure pushes you to follow the most basic rules. In worst case it moves the mess from root patch two levels down :) Fixed project structure is actually very good in case you ever wanted to cooperate with somebody and even more beneficial to companies. Its all prepared and empty, just about to start patching.

The idea behind is to have template projects prepared for typical use cases. We do similar things many times (like a touch-table). Lets just prepare a template for it. Forcing you to keep the structure goes with it like a by the way detail.

StageCounter

is an alternative to Automata for project stage-logics. The problem I have with Automata is that I usually end with a number of "all to all" goto connections.

StageCounter outputs one stage, represented by a number or a name, to control your project, inputs change to state from Send nodes. It's usually all you need, because information about transition is just in a change of stage from last frame. It works with Send and Receive nodes and is not spreadable, so you shouldn't go crazy with it. This one global variable is generally not vvvv way of doing things, I just found it very useful in this specific case where v4 guys often have problems. And its clean and ultra fast way to make programs with it. There is an example included. This time I'm very curious about your responses as now it is very useful for me, but should be more open to others.

Both parts work together and help me to create projects much faster.

download

ProjectTemplates.zip - 03.02.16 [01:07 UTC] by Martin Zrcek | 299 downloads
notes: small update - naming and dx11 window handle

other/older revisions

ProjectTemplates.zip - 29.01.16 [04:45 UTC] by Martin Zrcek | 100 downloads
notes: Blank, Stages, Example

vjc4 07/02/2016 - 21:59

Great idea, love the Template for DX11 and the quick acces to develop, shutup and kill just in case :)

Martin Zrcek 10/02/2016 - 22:00

Hey, Andres! :) cool that you like it. It actually could be the most useful and is the he most ignored thing I ever contributed. It is strongly affected by my personal experience and should be more general. Would be nice, if more people added their tools and habits they use all the time, so we can choose.

Noir 10/02/2016 - 22:04

useful

metrowave 15/04/2017 - 20:55

Good job Martin!

anonymous user login

Shoutbox

~13h ago

drehwurm: Nevermind... my fault.. had an old DX11 pack installed

~13h ago

drehwurm: Nevermind... my fault.. had an old DX11 pack installed

~13h ago

drehwurm: PointEditor (DX11 2d) help needs a checkup. Replace Renderstate with Rasterizer?

~1d ago

joreg: @mediadog: indeed, fixed that!

~1d ago

mediadog: @microdee @joreg Aha! I had glanced at that list, but assignment was lurking beyond the scrollbar. Athankew!

~1d ago

joreg: first-come-first-serve tickets are now sold out except the "delegate" ones. others are still available from here: https://nodeforum.org/journal/node17-tickets/

~1d ago

~1d ago

microdee: @mediadog: default is set via assignment (equal sign)

~2d ago

mediadog: No default for effect parameters, just min and max?

~2d ago

microdee: regular *fcfs tickets for #node17 are already sold out, and non lowered regular ticket isn't available straight from main page