Creating .dsa Script for Info
StarLabz
Posts: 74
Is there a asset here or inside DAZ that can create the dsa script for like INFO. I have seen these in many PA's products. I looked at it in Notepad++ and it looks straight forward if i want to create it, but i want to make sure it is legit and legal to place this into my product.
To clarify it appears in the Content area as a thumbnail that you basically double click to open and it displays a larger message, like a HOW TO USE info within DAZ as a script window.
Thanks.
Comments
Certainly it's legal to put the info. scripts into your Products... as long as the scripts are written by you.
Do you have an example of such products, it could help to look into the script you're speaking about.
Having said that, here's the documentation to create Message box, it seems straighforward:
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/messagebox_dz
Edit:
Daz has a couple of scripts they shared under a CC 3.0 licence and in this cas, as long as proper attribution is given, it's possible to use them: I regularly see mention of them in documentations of products either sold here at Daz or elsewhere.
Yea, like the example I wrote as below. If you don't adopt any scripts from those Samples on Daz wiki, but just write the scripts yourself with Daz Script language, you don't need to quote the source and / or CC x.0 relevance. That's my understanding.
I saw none of quotation in this sort of Info *.DSA file(s) in the products from this store and 3rd-party sites.
Thanks for the info. I dont have to be a DAZ PA to use them correct? I am not changing or modifying the script, besides entering in my own info for my product i am selling elsewhere. I did see the script state to just leave in the licence and links, etc...
here is the example i am using for the script
/**********************************************************************
Copyright (C) 2002-2019 Daz 3D, Inc. All Rights Reserved.
This script is provided as part of the Daz Script Documentation. The
contents of this script, and\or any portion thereof, may only be used
in accordance with the following license:
Creative Commons Attribution 3.0 Unported (CC BY 3.0)
- http://creativecommons.org/licenses/by/3.0
To contact Daz 3D or for more information about Daz Script visit the
Daz 3D website:
- http://www.daz3d.com
**********************************************************************/
// Source: http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/messagebox_dz
MessageBox.information( qsTr("My Info: <h2>Application Process</h2><ol> <li>Title 1.</li><li>Step 1.</li><li>Step 2.</li><li>Step 3.</li><li>Step 4.</li></ol> <h3>NOTE:Info......</h3>CharInfo. <h2>Other Info</h2>"), qsTr("-------- Instructions"), qsTr("&OK") );
Sorry for the lack of clarity, the examples I have in mind have link and / or credits in the PDF included in the product. If you have a Manfriday's product with a PDF, there is usually a section crediting the use of some scripts shared by Daz.
At third party, if you have any product by AciKay, there is a link in the PDF to send people to the page where Daz shared the script to open a PDF.
According to the licence in the script, it's shared under a CC 3.0 licence:
https://creativecommons.org/licenses/by/3.0/
As far as I understand the licence (I'm not a lawyer), as long as you're crediting Daz for writing the script with a link to where someone else can find it and a link to the licence, three requirements that should be fullfiled by keeping the licence block in the script, you're free to do whatever you want with the script, even including it in a product you want to sell.
No, you don't have to be a PA to use them... and it's also just fine if you want to keep those info. there ~~ though I don't it's necessary, IMO ...
Right, I know... some people do and some don't, like RiverSoftArt, Zev0, etc. depending on the different case. I still think if you re-use the codes in those samples, you need to put in the info. as there's a disclamer and/or requirement. If you just refer to the language syntax to write your codes, you don't have to...
However putting those info. there should be the safest way... no harm at all ~~
It is if using the sample script, in whole or in part.