YOUR ACCOUNT

Login or Register to post new topics or replies
Fluxtah
Ian Warwick
Posts: 27
Filters: 11
I am not sure if this has been mentioned or thought of already but it would be nice to be able to create a filter that can be used as a component.

What I mean is create a simple filter, define all the input controls and then save it. Then, when creating new filters the previous filter (Composite Component?) will be listed to be used like any other componenet.

Hope that makes sense, What do you think? smile:)

This would be a great way to manage snippets and use them as components smile:D

EDIT: Looks like you guys have already discussed this - http://www.filterforge.com/forum/read...essage1972
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
it's not been presented excactly as you laid it out, but various other forms have. there are a number of threads on 'grouped components' and 'snippets' and their uses.

you can already do some of what you're asking for. in any given filter, select a group of them and right click and pick 'copy'. exit the filter and open another or create a new one. right click in that filter and select 'paste' and your entire group will be pasted into the workspace.
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail
Fluxtah
Ian Warwick
Posts: 27
Filters: 11
copy/paste is very handy, although it does break encapsulation.

Well its good that it has been discussed before, it will be interesting to see the solution smile:)
  Details E-Mail
Kraellin
Kraellin

Posts: 12749
Filters: 99
well, effectively, any group of components can be considered as one component and can be created in or moved to any other filter for use and it will still operate the same way. thus, effectively, it's one component.

but i know what you're getting at. and yes, it's a good idea. it would be like having a sort of library of snippets, premade and existing in our components list as a single entity and extended just a bit, would show up in the workspace as a single component. and yes, that could be quite handy.

the downside is, it could also get quite messy and i cant even imagine the coding nightmare to do this. imagine taking just something simple like a refraction snippet that used perlin noise, refraction, image and blend. hmmm,... you'd only need two input nodes and one output. so, that wouldnt be too hard. you'd have to break down all the sliders within a given component into data objects (if they arent already) and re-combine them and reconstruct the component base.

so, if the internal codes/data structure of any given component is already broken down like this on an individual basis, maybe you could do it. interesting.

the other messy part might be in keeping a sane organization of all these new components. imagine adding 50 new components to your components list. it would be almost easier to just build a new group rather than having to find that one you'd built a year ago and saved.

still, an interesting idea.

(p.s. dont mind me, i'm just thinking out loud smile:) )
If wishes were horses... there'd be a whole lot of horse crap to clean up!

Craig
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,737 Registered Users
+5 new in 7 days!

153,582 Posts
+26 new in 30 days!

15,355 Topics
+5 new in 30 days!

Create an Account

Online Users Last minute:

7 unregistered users.