Seditio ve Ldu hakkında sınırsız arama yapın
 
 
> 1 <

Etiketler: temaları seditio cevirme yardım

Author Message

immortal

Members


Online status

86 posts
http://www.cehennemindibi.com
Pagerank: 0

Location: Turkey
Occupation:
Age:

#9077   2007-12-13 13:02 GMT      

herkese slm
neocromede gezinirken bi konu dikkatimi çekti ldu temaları seditioya çevirmek dedim bizimde işimize yarıyabilir ancak ingilizce olmadıgı için buraya taşıdım türkçeye çevirip yayınlarsanız güzel bir döküman olur..


How to convert a template into a usable LDU/Seditio Skin

1. Find your template that you want to use. Some popular sites are www.zymic.com and www.clantemplates.com. Please, if you use one of these templates, follow the copyrights of their authors. Each of these templates usually only cost . That's a small price to pay for someone's work.

2. The template will be one file, usually named index.html We need to split this index.html into three different parts. I'm going to try to cover both LDU and Seditio in this tutorial, as there is minor differences.

3. Most templates have a layout that can easily be seperated into three different parts, which is neccessary for our LDU/Seditio skin. Upon browsing zymic.com, I found that this would be a good template to learn with: http://www.zymic.com/template_preview.php?id=119&cat_id=1 It can be downloaded here: http://www.zymic.com/download_template.php?id=119

4. We need to slice this template into three different areas. The easiest solution being that shown below:

MISSING IMAGE

However, you can also slice the template in different ways, such as this:

MISSING IMAGE

MISSING IMAGE


5. Now we start editing code. Download the LDU or Seditio package. We are going to be using the default skin that comes with the package(s). Open up your favorite text editor, preferrably one that supports multiple documents being open. Open the index.html that came with the template and open header.tpl, index.tpl, and footer.tpl that comes with the default skin(s).

6. First, let's start with header.tpl. Remember we said we were going to split the template according to the guidelines above. So, following that guideline, we are going to see that the header in index.html that came with the template, only contains this portion of code:

Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>YourSite</title>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<link rel="stylesheet" href="lib/style.css" />
</head>
<body>

<div id="content">

<ul id="top">
<li><a href="" id="active_top">Home</a></li>
<li><a href="">Forums</a></li>
</ul>


This is going to replace the entire header.tpl of the default skin package. But, we must first convert the tags. Never forget the <!-- BEGIN/END: X--> tags. In this case it will be <!-- BEGIN: HEADER --> and <!-- END: HEADER -->
Start with the BEGIN tag and the !DOCTYPE tag and replacing the entire lines with

Code:
<!-- BEGIN: HEADER -->
{HEADER_DOCTYPE}


The one you think would be next would be the title, but we must first remember to inser the header metas and header javascript popup tags. Place

Code:
{HEADER_METAS}
{HEADER_COMPOPUP}


Right after the <head> tag, and before the <title> tag. Inside the <title> we replace "YourSite" with {HEADER_TITLE}
Remove the <meta> tag below that. Next we see the style sheet reference. Let's remove the <link> tag, and replace with:
Code:
<link href="skins/{PHP.skin}/{PHP.skin}.css" type="text/css" rel="stylesheet" />

Don't worry about the style sheet just yet, we'll get to that later.

The next thing that comes is a matter of personal choice/opinion. We see links to Home and Forums. You can place these links, starting and ending at the <ul> tag, inside one of the many available menu slots in the Administration section of LDU or Seditio. Or, you can leave them how they are, and change the links to suit your needs. This might also be a good place to put the <!-- BEGIN/END: USER/GUEST --> tags. Such as:

Code:
<!-- BEGIN: GUEST -->

<ul>

<li><a href="users.php?m=auth">Login here</a></li>
<li><a href="users.php?m=register">Register</a></li>
<li><a href="plug.php?e=passrecover">Lost your password ?</a></li>

</ul>

<!-- END: GUEST -->


7. Apply these same methods for index.tpl and footer.tpl, replacing the tags as you go along.

8. The style sheet and images. I probably should have mentioned before while editing the code, that it's a good idea to keep your images contained in one place. By default, the skin packages all point to /skin/img You'll find that most of these templates point to /images or some other variant. A good idea would be to batch replace, in this case the template is /lib/, with skins/{PHP.skin}/img/ That way, you can place all of your images into the skin/img/ folder and keep them all contained within one area.

8b. The style sheet. Our template uses a file called style.css and our skin uses a file called manta.css or pandora.css. Copy the code from the template's css file into the skin's css file. Some of you might notice a problem with this, but that's ok because the solution is relatively simple. The problem that may arise is that your template might be calling a div called "container" which will require different formatting than the one defined in the skin's style sheet. When we pasted the code from the template's style sheet into the skin's style sheet, the formatting information twords the top always gets priority, which will obviously throw everything out of wack. So, an easy solution would be to find duplicate entires, such in our case one would be "content" And replace with something reasonable, like "content_b". And change the code we pated into the template's style sheet to match. This way, we can keep the formatting we need for the template, and keep the formatting we need for the rest of the skin as well.

9. Save all of your files, change the skin name to something different. I pray you did not overwrite the default skin. Always make backups first. Call this skin something like "manta-mod" or "pandora-mod". Upload to your webserver and test.


-This is just a fairly easy solution. Obviously there may be some problems along the way to work out. Remember, if you use one of these templates, be fair and respect their copyright information. As you can see, this template costs a measly . That's not a lot of money.

I hope this helps someone. If you have any questions, don't hestitate to ask.

samba

Members


Online status

64 posts

Location: Turkey
Occupation:
Age:

#9084   2007-12-13 15:29 GMT      
bu templateleri sed tema yapma değil mi
sambac?
> 1 <

Benzer konular (Similar topics) #BETA

Keywords (beta):

Forum Arşiv (beta):

[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [96] [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122] [123] [124] [125] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139] [140] [141] [142] [143] [144] [145] [146] [147] [148] [149] [150] [151] [152] [153] [154] [155] [156] [157] [158] [159] [160] [161] [162] [163] [164] [165] [166] [167] [168] [169] [170] [171] [172] [173] [174] [175] [176] [177] [178] [179] [180] [181] [182] [183] [184] [185] [186] [187] [188] [189] [190] [191] [192] [193] [194] [195] [196] [197] [198] [199] [200] [201] [202] [203] [204] [205] [206] [207] [208] [209] [210] [211] [212] [213] [214] [215] [216] [217] [218] [219] [220] [221] [222] [223] [224] [225] [226] [227]