Got a question:
Let's say I want to edit the header and move items around. With skins, will the header be placed in a template function for me to override like a plugin?
// Start the header layer.
function template_header_before()
{
echo '
<div id="header"><div class="frame">';
}
function template_top_bar_before()
{
echo '
<div id="top_section"><div class="frame">';
}
function template_top_bar_after()
{
echo '
</div></div>';
}
// End the header layer.
function template_header_after()
{
global $context, $settings, $options;
echo '
<div id="upper_section"', empty($options['collapse_header']) ? '' : ' class="hide"', '><div class="frame"><we:banner title="',
$context['header_logo_url_html_safe'], '" url="', !empty($settings['home_url']) && !empty($settings['home_link']) ?
$settings['home_url'] : '<URL>', '">', $context['site_slogan'], '</we:banner>
</div></div>
</div></div>';
}Thanks, likewise. :) The fact that you stuck with your vision and haven't not given up, is commendable.
True, I did more experiments in ViennaBBS as it were..but I thinks thats mainly because I've been more focused on having Protendo going in the right direction under the hood - so less time for graphical things.
The current theme is on the minimalist side - its my current "phase" :D -
but I see that it needs more themes, more diverse ones. And that I can do easily, but the old fashion way of replacing themes rather than skins/variations only.
In any case - theres a lot of freedom for themers in Protendo, the css is been transformed to much more use of classes - which is the IMHO only way to make sure one change reverberate back into default templates.
Making Wedge skins? I know I mentioned it before, and that it didn't pan out to anything then, but I think I need to really use Wedge for a while, see its way of working, under and over the hood, before dreaming up new designs. But I also know, I will prob. want to shift so much around that it might not be possible...but, can't say no until you tried - as the saying goes. ;)
Is the alpha 2 from 2012 the latest release?
I am not asking you to heighten my involvement or anything, because honestly, I will prob. be poor on feedback(due to working also on my own things) but it would be great to try stuff with the latest code - or what you deem close enough to make skins for.
Hm, I wasn't aware of the masking of anchors..does it do it now, still? You may need a hard refresh. And no, I am not using JS for that, only CSS.
Sure, I have an account on bitbucket already, but no problem getting another.
Heh, just watched latest "Homeland" (s3e7), time for bed me think, if I am to function at work tomorrow. :D
Quinn is the mystery now, wondering if he might have something to do with the delivering of the bomb at Langley..but at least his ghost of earlier kills are haunting him it seems. Remains to see, the infidelity scene at the end was also painful. But Saul is strong, he'll survive once he finds out..or she just tells him.
Oh, I changed it last night. :)
Yes, with negative margins..I first added a "relative" class to the anchor in the template, then added "position: absolute" and top: -145px" which is roughly the height of the header. Not optimal since you have to change that if the header is higher, but still.
Homeland is great. :) Only a few series I look forward with excitement nowadays: Homeland, Person of Interest and the Blacklist.
(click to show/hide) Quinn is the mystery now, wondering if he might have something to do with the delivering of the bomb at Langley..but at least his ghost of earlier kills are haunting him it seems. Remains to see, the infidelity scene at the end was also painful. But Saul is strong, he'll survive once he finds out..or she just tells him.
/Smileys/* /assets/smileys/
/Themes/default/aeva/* /assets/aeva/
/Themes/default/fonts/* /assets/fonts/
/Themes/default/images/* /assets/ (including aeva, so --> merge folders)
/Themes/default/languages/* /languages/
/Themes/default/scripts/* /scripts/
/Themes/default/skins/* /skins/
/Themes/default/* /templates/lol, fun times it seems, for you removing that. :)
About series, I like some of them you mention, but most of them is too light for me , Agents of Shield was promising, but now I just see it of curiosity.
Person of interest is kind of silly, true..but I love the characters in them, well, most of the time. Spader acting I am mostly unaware of, apart from the old Stargate movie, but then I rarely watch cop series anyway, so Boston legal I haven't seen.
Sherlock is great, look forward to new season, others I follow now are CSI and Supernatural, still exciting!
but I started and ended alot of series..lately i saw Broadchurch though, that was a keeper.
but did you know about another, similar but less bloody, called "Les revenants"? :D It was slow at first(well, first episode was quite fascinating), but it soon got me hooked all the way in. And yes, its indeed true what they say about french girls :) Look forward to second season of that too.
My bitbucket account is bloc67 - I think you mentioned it a bit back.
As for the fixed header..uhm, I haven't even checked on mobiles yet. I might get rid of it again, its a fad really, maybe not worth doing "hacks" for it. I'll make my mind up soon hah. :)
Y'know, I started something similar for Protendo, renaming and changing that is..but it was too much work lol.
But, I have actually made folders = name, same as you have done. Also, Protendo just reads all theme folders at startup, then check if its installed and show the thumbs so one can see what theme it is easily. Those that are not installed will have a install checkbox.
You are right - themes are a real confusing feature in SMF, even if I spent most of my time with them, I still have lots of things I want to change internally.
It just shows that the theme feature was a highpoint from Unknown - but less attention have been given to it since(internally that is).
On another note: I have installed and tried out Wedge latest. I have to be honest though, its quite another way to work for me.
I am not sure where the border between whats user-adjustable, whats auto-generated and whats left to a themer in the skins/themes code.
Of course, the skins and its css..but the skeleton, if you change that in a theme, what are the chances it will not be changed by a plugin or the core..or the user?
It seems, to me, and pardon me again for being forward :) that theres less "to do" for a themer other than provide the "look" of it.
Maybe shift things around - but thats as much the job for the admin as for a themer.
This is a bit difficult atm..but I will persevere in it, although it may take some time to then come up with good designs - without being too much alike each other. ;) Thats my drive in it anyhow, it may not be that for others of course.
I think it will be better to split this thread (add a poll?)
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
Yeah, I *think* I remember SMF having a reason for capitalization, but I really can't remember it.
I'll go for all lowercase in the final version.
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
Yeah, I *think* I remember SMF having a reason for capitalization, but I really can't remember it.
I'll go for all lowercase in the final version.
A more radical structure (and naming scheme) for the src folder could be:
/src <-- empty
/php <-- Sources
/css <-- skins
/js <-- scripts
/lng_fr <-- languages/French
/lng_en <-- languages/English
/tpl <-- Themes/default
Probably a bit scary, though... :lol:
| 1. | Although I'm very open to discussing other possibilities, of course. |
| 2. | Pros of having them in /src/php: easy to create new sub-folders, as is the case in SMF, Elk or current Wedge. Clean structure. Cons of having them: it takes one extra step to update the website by FTP. I don't like the idea of an extra step, hmm... |
/core
/javascript
/languages
/plugins
/skins
/sources
/templatesI'm good with it. It's straightforward and logical. Uncluttered too which is a bonus.
Well given I'm not particularly techie, and I do not understand some of what you say, please go easy on me.
In your current structure (reply 57), where do the media and attachment folders go? Could attachments be a subfolder of media?
Why is there a template folder if templates are no more?
When you talk about a 'core' folder, do you mean the public_html folder or will there be a folder named 'core' with all the other folders off of it? And if so will a site's address be "mysite.tld/core/" ?
It looks mush better to have the languages folder straight off the root, however I don't quite understand the folder's structure.
In the ./languages/ folder there'll be admin.english.php admin.french.php and all the other english and french files, but the other languages' files will be put where?
And then moved somewhere? Will they come with the original product download or will each language pack be on wedge.org as an optional extra?
Scripts: is there any danger of a different scripting language becoming popular?
If not jscript then perhaps something that's not widely heard of - yet. If so should the js folder be named 'scripts' in case someone wants to script in this other as yet unnamed and unknown scripting language and there isn't a natural home for it. As for confusion of putting php files into it, surely people will see what's what when they look and see that the folder only contains js files and php files are elsewhere.
/wedge
/assets
/attachments
/cache
/media
/core
/javascript
/languages <-- contains english only
/your-language-downloaded
/plugins
/skins
/sources
/templatesAh! So the full folder structure is something like:
I guess I need to do some homework on skins / themes / templates (I thought they were just different names for the same thing).
You could rename core to weave, because you want to use the name and because it'll confuse people :)
| 1. | Possibly duplicated on BitBucket, too. I have yet to determine which will be the final resting place for the public repo; while Github is a much more popular website, I still like BitBucket's design more, and if the GH repo doesn't get any popular, then there's no reason to stick to Github. |
And this last one, I really need to get right... I need help for folder names!
I need to fine a folder name for what used to be the 'Sources' folder. It contains, of course, all the main PHP files that power Wedge.
The new name needs to:
- show up before 'languages' in the folder list, and even preferably before 'javascript'. So, it needs to start with a letter between 'A' and 'L' at best, or 'A' and 'I' at worst.
- Reflect the fact that it contains PHP files, or Source files, or things that power the software.
I consider 'code' but it's too close to 'core'.
I also considered 'engine', but maybe it's a bit over the top for that folder.
Anything else, guys..? Don't forget you'll be updating that folder quite often, so might as well help in finding its name... ;)
And this last one, I really need to get right... I need help for folder names!
I need to fine a folder name for what used to be the 'Sources' folder. It contains, of course, all the main PHP files that power Wedge.
The new name needs to:
- show up before 'languages' in the folder list, and even preferably before 'javascript'. So, it needs to start with a letter between 'A' and 'L' at best, or 'A' and 'I' at worst.
- Reflect the fact that it contains PHP files, or Source files, or things that power the software.
I consider 'code' but it's too close to 'core'.
I also considered 'engine', but maybe it's a bit over the top for that folder.
Anything else, guys..? Don't forget you'll be updating that folder quite often, so might as well help in finding its name... ;)
@Pentaxian, it would sound silly to have a sub-sub-folder that's called 'base'.