Assets and incremental saving.
-
Just starting out , couple of questions.
-
How can I make incremental saves , it seems it only ever allows me to overwrite the preset ?
Do I use the xml for that or am I missing something? -
Say I make a Meter using strips , can I save that as an asset that i can easily bring into an ongoing project ?
I am aware of snippets but they always load as a "project" and erase what i have going .
How could I go about this ?
Thanks
-
-
@lalalandsynth There's no incremental saving, but if you use Github (and it's fairly recommended), you don't need increment
If you make a widget you want to reuse, create it entirely by script (don't insert it manually and don't use the property editor) and save this scritpt in an external file (something like right click move to external file I reckon)
In your projetct/script folder you'll get a .fs file you can reuse anywhere -
Thanks , guess I will have to learn to use Github :)
Seems strange that there is no incremental saving though ?
Maybe everyone here is so accustomed to using Git ?Btw , would Github then do automatic saving , or do I manually commit every now and then ?
Can snippets not serve this purpose , or would I need to save the snippet as a script for future use or reference ?
-
@lalalandsynth Honestly, I don't think anyone uses snippets for saving purpose. We use them only for sharing on the forum afaik
Github is definitely the way to go. The advantage (among other) is that it allows you to easily keep track of the modifications and comment the different commits.
I don't use the terminal though. I know it's the most powerful way, but for my purpose I like to use Github Desktop. It just makes the burden less a burden to me
-
You don't need to use github, just git. It's not automatic, you have to make commits manually. I have a tutorial on my YouTube channel.
-
@d-healey said in Assets and incremental saving.:
You don't need to use github, just git. It's not automatic, you have to make commits manually. I have a tutorial on my YouTube channel.
It's not necessary but it would be a pity not to benefit from the online storage security with one click
-
@ustk said in Assets and incremental saving.:
f you make a widget you want to reuse, create it entirely by script (don't insert it manually and don't use the property editor) and save this scritpt in an external file (something like right click move to external file I reckon)
So if i make a meter with Png strips , i cannot save that as an asset somehow ?
-
@lalalandsynth - click on the widget in the components list that you want to save, press control-J - this will display the re-usable JSON definition of your widget - you will have to save your png seperately...
-
@Lindon Awesome ! Thanks
-
One more question :)
When just playing around , making assets , testing things out etc , do you always start that as a project or what is the procedure here ?
-
@lalalandsynth Since the JSON can be scripted, it is not necessary to copy it from the component.
I mean, it's useful once or twice, but if you plan to keep it for every project, having everything in one unique script is easier since this script can create the component and prepare all the JSON properties. But as @Lindon said, you still have to keep the png file separately.My workflow is that I have a sandbox project where I create a quick preset every time I need to work on something specific, don't want to mess with my actual project, or create a complex widget... When I'm happy with the result I just copy-paste the script in my main project (or move to an external file and include it in main project)