Pages: (6) 1 2 3 ... Last » ( Go to first unread post ) ClosedNew TopicNew Poll

 Import & Export Skin Content [complete]
#
Feature: Import and Export Skin Content

A suggested feature would make a few changes to the skin system that I believe would help make things easier for both skin developers and users. Currently, in the Admin CP options to export downloadable file versions of macros, and the skin sets is unavailable. Import options are also unavailable unless you decide to use our own built-in skin importer.

I want to change that.

Goals for this feature include:

-> Export any piece of CSS, Macro Set, and Wrapper data into 1 solid .xml file
-> Upload the XML file anywhere to import the pieces back in.

This will allow people to create their own skin packages and upload them to this forum, or share them.

So they have the option of simply upping the whole XML file and bam. skin, or piecing things together the way they want. It's a one-click skin install solution - doesn't get any easier than that.

Initially, this feature won't be of much use since no skins will be compatible with it... however, you guys can help me with that. I'll release the final design of the XML file during development for skinners to look at, and you guys can give it a shot at making your own if you want. When the import/export is setup and complete enough to let some developers beta test it for problems, I'll post here. I want to get feedback from actual skin creators before the whole system goes live to work out any format or feature issues that there might be. Since this will set a standard for future skin purposes, it has to be done right the first time.

I'll gladly provide links to some skins that are posted here if developers make use of the system, so that users here have something to do with it on the day it gets released. One or two skins per developer though. I don't know how many testers we will need, but I'll post when ready.

Any initial questions/comments/etc are welcome. smile.gif

EDIT: Change of design plan as per posiden's suggestion that he just came up with.

signature
email: admin@jcink.com :: blog: John C.
#
It sounds like a great idea! I would gladly help design some skins if I can(time wise) if needed smile.gif

signature
bl0t@aol.com.au
user posted image
#
thanks for starting this Jcink

This post has been edited by card123: Oct 12 2009, 01:25 PM

Attached 1 File(s)

signature
Need a Code? I will help if I can =]
PM
#
I'll make some designs now. Possibly convert old ones also. Let me know about beta testing.

signature
user posted image

Shift UI Development Thread
"Design is not just what it looks like. Design is how it works." - Steve Jobs
#
I has some one the way.

signature
Thanks,
JordanH

JcinkNet Family Grandpa
#
Possible different way of doing it:

CODE
<?xml version="1.0"?>

<skin>
<skinname>Name here</skinname>

<wrappers>
 <% TITLE %>
 blah
 blah
 blah
</wrappers>

<stylesheet>
 BODY {
  CSS
 }
</stylesheet>


<macros>
 <item name='LOGO'>
  <img src='logo url here' />
 </item>
 <item name='C_ON'>
  <img src='some other image' />
 </item>
</macros>

</skin>


An XML document kinda like that example. Easy to navigate the document and edit things, and easy to program something to use the data.


Thoughts?


EDIT: spacing got messed up on the post for the xml blocks

signature
ΣAE
The True Gentlemen
#
I actually like that way a lot better, it will be easier for me to code that too. I can bypass the entire need for a *.tar file, and so can everyone else. Unless someone objects, I'm going with that. I do not know why I didn't think of that to begin with.

signature
email: admin@jcink.com :: blog: John C.
#
xml is always the better choice

signature
user posted image

Shift UI Development Thread
"Design is not just what it looks like. Design is how it works." - Steve Jobs
#
Oh freakin sweet biggrin.gif love posidens format idea

signature
QUOTE
There is a war going on for your mind. Those who seek to occupy it will stop at nothing. The battlefield is everywhere. There is no sanctuary. There are no civilians. You have two choices: surrender or enlist

QUOTE
Why do people feel the need to copyright codes in a way that prevents further editing. As long as the copyright remains intact your work is noted; allowing further editing/release spreads your name as a coder further and creates greater possibilities from something you created - that cannot be a bad thing. Next time you release a code, allow it to be modified and I won't set my zombie minions upon your cookie stash user posted image

My To-Do List

* I miss when this had stuff in it user posted image *

Or Check Out My Test Forum For All My Custom Codes/Skins!
Codes: 11 || Skins: 3 || Macro Sets: 3
#
Modified the first post to reflect the new plans... this project just got 10 times easier.

signature
email: admin@jcink.com :: blog: John C.
#
I was bored.
CODE
<?php

function getMacros($document){
 //Get the macro items
 //Create empty array that macros will be put in.
 $macroList = array();
 
 //Get all the item tags
 $items = $document->getElementsByTagName("item");
 //Loop through all tags found
 for($i = 0; $i < $items->length; $i++){
  //Put the tag found into a temporary $macro variable
  $macro = $items->item($i);
  //Put into the array another array the first element being the name of the macro
  //The second element the node value
  $macroList[] = array($macro->getAttribute("name"), $macro->nodeValue);
 }
 
 //Return the macro list
 return $macroList;
}

$document = new DOMDocument;
$document->load("test.xml");


$macroListing = getMacros($document);
$wrappers = $document->getElementsByTagName("wrappers")->item(0)->nodeValue;
$styleSheets = $document->getElementsByTagName("stylesheet")->item(0)->nodeValue;
?>

signature
ΣAE
The True Gentlemen
#
Thank you; that will be of use.

signature
email: admin@jcink.com :: blog: John C.
#
So all the skins will be in XTML instead of HTML?

signature
user posted image
[Memento Mori/Remember You Are Mortal]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

#
XML is just a method of formatting. Skin pieces will still be HTML and CSS based.

signature
email: admin@jcink.com :: blog: John C.
#
Well the parsing part of this is basically done. I ended up having to do my own parser largely out of being stubborn and a bit lazy, but it wasn't that hard anyway. The next thing to be done is to set up the uploaders and make solid "idiot proof" checks for when uploading the xml files. Should be easy.

signature
email: admin@jcink.com :: blog: John C.
0 User(s) are reading this topic (0 Guests and 0 Anonymous Users)
0 Members:
Share this topic:
« Next Oldest | Development News | Next Newest »

OptionsPages: (6) 1 2 3 ... Last » ClosedNew TopicNew Poll