You are not logged in.
Pages: 1
Hi. I just made some new skins for everyone to use the first, I is an original design by me. The other two are based off of the Microsoft Office Word 2003 - WAIT! before you get all anti-Microsoft on me, I would just like to say that I'm not a huge fan of them either. I made the other two skins so my clients and users (most of whom are computer illiterate and use Windows) can have a familiar interface to work with on my CMS.
The downloads are in zip format. due to laziness, I have not made tar/gzip versions yet.
Offline
Cool. I submited a ticket.
Offline
hi, added in changeset 201.
I am wondering about the "creatice commons" licence and the file cc.html provided with inditreuse.zip, as far i can understand the licence, it must be added with the skins.
But should we add one licence file in every directory of the 3 skins, or is it enough if completesite name is mentioned (as required from licence) and a link to the online CC licence added in a generic licence.txt in the directory /skins/ (where we could add a link to every licence used and author's name for every skins in the directory) ?
http://creativecommons.org/licenses/by-sa/2.0/legalcode
I didnt add any licence file yet until everyone is agree on what should be done with it, because i dont want to pollute the SVN (so scared to mess something in this, would result you hating me and i dont want that
Offline
I made the Inditreuse skin for my commercial CMS that I am working on but I wanted to share it to give back to the open source community (Xinha in this case). The license has the same essentials as the htmlArea License except that it requires that I get the credit for it. As the creator of the skin, I am completely fine with the cc.htm file taken out since the htmlArea License already has most of it covered. However, I would like something (perhaps a .txt file or maybe a comment in the skin.css) that says that Kyle Kochis made it and it is free to be redistrobuted as desired as long as the original is attributed to Kyle Kochis. I don't need a link or anything more than something simple like that. I probably should have made it that way in the beginning.
Offline
for some reason the css file keeps getting corrupted when I zip the files. I'll figure out the problem tomorrow and fix it. When I do, I'll change the license on Inditreuse so there will only be a couple lines of comments in the css file and it will have nothing to do with a creative commons license.
Offline
Licenses are not really a problem (as long are they are freely distributable and open source) as the base code is under the htmlArea licence which is just a renamed BSD licence, so pretty much compatable with any other licence out there.
I think a README should be placed in each skin directory that has the licence information in it if it's different to Xinha itself.
James Sleeman
Offline
Hello,
does a README file like the following text, in the directory /skin/inditreuse/ would be what is needed ?
Skin inditreuse
Author: Kyle Kochis (http://completesiteservices.com/)
Creative Commons
Attribution-ShareAlike 2.0
You are free:
* to copy, distribute, display, and perform the work
* to make derivative works
* to make commercial use of the work
Under the following conditions:
* by Kyle Kochis
* If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.
* For any reuse or distribution, you must make clear to others the license terms of this work.
* Any of these conditions can be waived if you get permission from the copyright holder.
Your fair use and other rights are in no way affected by the above.
This is a human-readable summary of the Legal Code.
Get the full license at http://creativecommons.org/licenses/by-sa/2.0/legalcode
Offline
Actually mokhet,
Here is all you need to put:
Skin inditreuse
Author: Kyle Kochis (http://completesiteservices.com/)
This work is licensed under the Creative Commons Attribution-ShareAlike License.
To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/2.0/
or send a letter to
Creative Commons,
559 Nathan Abbott Way
Stanford, California 94305
USA
Last edited by completesite (2005-05-29 01:03:46)
Offline
Ok I have a question here - maby Im to lazy to accually chech this out, smack on me in that case, :)
The current plugin system applies images from the plugins own folder, how will this affect the skins? I mean, if we are to have a buttonskin altleast all the official plugins should be supported for the skins. Anyone checked this?
EDIT :
If this is true, I would suggest that all the official plugins get their images removed from their own directories and movied into the main images folder. If someone want to use special icons they can still modify the images in the images folder, and the overhead would not be much - a few extra gifs in the folder, who cares really (Compared to having a skin that accually doesnt work since its not complete). Again, I might (hopefully) be wrong here.
Last edited by kimss (2005-05-31 11:17:09)
Offline
Hello,
The skin system is still a very new feature and i'm sure gogo and others have billions of idea in mind to improve it.
The current plugin system applies images from the plugins own folder, how will this affect the skins? I mean, if we are to have a buttonskin altleast all the official plugins should be supported for the skins. Anyone checked this?
I am not sure about the question (damn english) but if you mean : are the buttons added in toolbar from plugins get the skin applied ?
Then the answer is yes
Offline
Pages: 1