Since everyone else is, I'll add my comments to the mix here. :-)

Wishlist. I no coder, but the metaphors *seem* to match


*** 1. Refactoring

Problem:
QC is rejiggery heaven…but as soon as you start putting patches into
macros, you're locking yourself into a design because of the 'cost' of
pulling those patches out again, reconnecting etc. Same problem exists
with Virtual Macros currently — there's a cost of work to using them
which prevents me from using them.

Suggestion: How about spring-loading the Edit Parent button. Selecting
some of the patch, and dragging over that would 'pull' all selected
patches up 1 level, while maintaining connections

Suggestion: Support Virtual Macros as Toby Suggests

*** 2. Debugging
…if I can call it that is tricky. I know you can mouse over patches
points to see the output, but that's slow and cumbersome. Also this
doesn't work with iterators.

Suggestion: Allow the animation of pipes to show data. Add 'inspector'
widget to watch data flowing through. Add support for reviewing
contents of iterators

*** 3. Commenting

The Add Note feature is really only useful for commenting on
completely frozen patches, because moving them doesn't move the note.

Suggestion: I would love to be able to 'stick' these notes to
patches/macros, with support for images.

*** 4. Variables
I'm forever using a Math patch to just hold a number.

Suggestion: I know it breaks the model, but would LOVE global + local
variable widgets.

*** 5. Logic
I'm always struggling to express some interaction logic . I find
Javascript to be really clunky to use as well, so I tend to avoid
that.

Suggestion: Would love a 'logic/step sequencer' patch


*** 6. Buttons/ sliders
I'm forever inventing my own little button macros etc, even just for
testing purposes.

Suggestion: Some standard OS X widgets (button, slider, radio button) patches.


I can provide more info, and mockups as required.



Keith


On Thu, Apr 29, 2010 at 11:11 AM, George Toledo <[email protected]> wrote:
> Dropping a qtz into your Quartz Composer Patches folder, with published
> inputs and outputs (as needed), will load a patch into your Patch
> Creator/Library. When you want to edit it, open up the "patch" qtz, and it
> will load the new version in all of your qtz's that use it.
> I'm not in SL this moment, so I can't comment on if the help menu referred
> to is talking about the same thing I'm describing.
> On Wed, Apr 28, 2010 at 8:37 PM, Christopher Wright
> <[email protected]> wrote:
>>
>> Hi Toby,  (long time no see :)
>>
>> > useability-wise, they are a barely supported kludge, however.
>>
>>
>> Can you be a bit more constructive on that?  (I'm not calling you out or
>> anything -- I'm genuinely interested in some discussion on things that are
>> missing to make this feature more complete/useful).
>>
>> It'd be handy to get some chatter on it with perspectives of users "in the
>> trenches" as it were, to know the largest/most-annoying aspects :)
>>
>
> Chris, I know I've thrown this out there before, but I'll do so again
> on-list. The most useful updates would be for environments to be supported
> (as in, saving a bunch of GLSL environments for quick loading from the
> patcherator), and for an "explode/edit" function to be available from any
> composition, with prompts to have changes apply either globally, or just to
> the qtz being worked on.
> Also, issues that effect virtual macros not flattening correctly and being
> portable between systems, as well as restoration issues that can cause
> infinite loops are nasty.
> Being able to be able to pull out patch groups from the patcherator, where
> all of the patches pop onto a surface all connected, and as actually
> programmed (so that an Environment would be an environment, and that
> everything wouldn't just be renderers), would be extremely better.
> -George Toledo
>
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/quartzcomposer-dev/songcarver%40gmail.com
>
> This email sent to [email protected]
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to