SMF Development > Next SMF Discussion

What would it take to remove the calendar?

<< < (8/10) > >>

akyhne:
Problem is there's no "straight line" in Curve. And if you make a new theme from scratch, you can't as well know how it will turn out. You need to install all official modifications to make a theme.

bloc:
Well, I won't disagree with that lol, since its also something I don't particular like. BUT, you can make complex and new themes if you keep the style names and at least the header and container markup, and change some of the underlying CSS instead. Problem is that the CSS is very complex to start from scratch. So the freedom to do what you want isn't there, but its not impossible to make new things either. The main problem is, or has been lol, that mods also want to mod the templates, which makes creating new markup impossible.

But theres no need to install mods to be sure it works. I never do, nor should any theme designer have to, simply because its the MOD's responsibility to adhere to presentation logic/classes/styles/markup - not the other way around.

akyhne:
Someone should rewrite Curve from scratch to make it more easy to modify.

Angelina Belle:
There are so many new ideas since CURVE was first designed, and there were so many changes to CURVE before it was released, that starting over is a very good idea.

I am sure it will happen for the next major version of SMF.

Norv:
igirisjin,
You're right. In the current state of SMF 2.0 and the ecosystem of official mods and themes we're barely starting to have around it (please do note: I meant intently "official" mods and themes, not third-party only), we wouldn't have good support for all we're thinking of.
But the issue is not really about "removing" anyway: it's about modularity. At the level of the code (I actually mean architecture of course), SMF should have its components written in a modular way, loosely coupled with the rest, not embedded one in another in a too messy way. And this *is* the clear goal of future versions of SMF: to separate components such that we are able then, to simply tick a box in the installer, and have a calendar - for example - with the forum, or not have it. As a good example there may be some of the current core features in Admin panel: coming by default, but able to be enabled/disabled anytime, perhaps including at installation stage.

For SMF 3.0, we do aim to disentangle the *code* of the calendar from the rest of the code, and reimplement it in its own files (no, not parts of the calendar code in the post function, parts anywhere else, but a module containing the calendar implementation on its own). Once that is done, the calendar means a piece of functionality which can then be simply added to a forum or a blog, without direct code modifications. So, no "mods" involved, only the right design and implementation for the functionality, such that it is loosely coupled with the rest. No issue with the download package either: the download package can very well contain the calendar, or the installer can download it on the fly (such as the next webinstaller should be able to do ;) ), and enable it on the forum at admin's choice.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version