Started my own fork - Luke Tools

Feature Suggestions
#22

Luke Tools scripts are my intellectual property. They may only be used through the Luke Tools WickObject bridge, and the code itself must not be copied.

The bridge forms part of the Creative Commons arrangement we all have with Wick Editor. So you can copy the bridge up to a point. I have no problem with you including it/hardwireing it into your own fork. You just can’t copy the scripts for the tools and make them stand alone in your build.

My Wick ED fork is not available yet, as I am still working on it.

///////////////////////

Great you want to make animations with my Luke Tools though.

The instructions are:

  • Download the Zip file
  • Unzip it
  • Upload the wickobj to Wickeditor and place it on the WE stage
  • Hit play and then pause the panel object will load.
  • My tools are in the panel that loads.
  • I am working on videos in my spare time. But for now you need to do your own tests.

///////////////////////

#23

Im on android tablet… how CAN I DO ALL OF THAT WITHOUT A PC OR A LAPTOP

#24

I can’t help with that!

#25

Actually @lukeo25, the Wick-ED fork can be accessed by anybody who knows the link. This is because the repository forks Candlestick, and forks (atleast on GitHub) must be public.

I did actually find and test it once, but it really is not finished, as (when I looked into it) it just looked like Candlestick pre-injected with the bridge.

You can also pre-inject the bridge by putting the its code into TamperMonkey (or any browser userscript plugin), as the core bridge appears to be a userscript.

#26

Yes the bridge is within the copy-left license so not a problem. The individual scripts that run inside it and Wick are my IP they are not to be copied unless I give consent.

#27

A repo does not automatically own every script that a plugin fetches.

Think of it like this:

1. Code inside the repo
If the script file is committed into the repo, then it is part of that repo’s distributed content. If the repo has a licence, GitHub’s terms say contributions/content added to a licensed repository are generally licensed under that repository’s licence unless there is a separate agreement.

2. Code fetched from somewhere else
If your repo only contains a plugin/loader that fetches your scripts from another server, CDN, API, GitHub raw URL, etc., then those fetched scripts are not necessarily part of the repo . They remain separate works owned by whoever wrote/owns them.

3. Ownership stays with the author
GitHub itself says users retain ownership of content they upload; GitHub gets rights needed to host/display it, but does not take ownership.

4. Licence matters
If your public repo is MIT/GPL/Apache/etc., that licence may cover what is actually included in the repo. But it does not automatically cover separate external scripts unless you say so or bundle them into the licensed project. GitHub also says that if a repo has no licence, default copyright applies and the owner retains all rights.

I spoke with my lawers when I started this, and that is why this is a plugin/wickobject not a complete fork.

:)

1 Like
#28

To be firmer:
Yes, the fork/bridge may be public because it is based on Wick/Candlestick. That is fine. The bridge is not the same thing as the Luke Tools scripts. The scripts loaded through the bridge remain separate works and are not licensed for copying, repackaging, or standalone inclusion in another build without my permission.
So no copy my property!

1 Like
#29

I had a think about this. It might work if I give you a default Wick to load. You should see my V3 Yellow Luke tool Icon and the LT Tab. Delete the Yellow icon if it loads as a Tab.
LukeToolsDefaultWick.wick (86.1 KB)

Hope this helps.
L

#30

Luke I cant add mouths to my lipsync service

#31

Most likely, you have named them wrong.
They should get named:
A.svg
B.svg
C.svg
D.svg
E.svg
F.svg
G.svg
H.svg
I.svg
Rest.svg

image
image1912×852 183 KB

image
image1912×867 201 KB

Its working for me!

L

#32

Luke can you make your tools open source.

#33

Ishanth, no, I have plans for them.

#34

oh ok thanks for conforming