[1.7] - ToDo and urgent feature requests...

[Timbalu]

before Summer is over...

Hi

I really would like to have Spartacus perform its upgradable tasks when fetching the xml, half or once a day.
This would improve the backend management and we could highlight these plugins on /serendipity_admin.php?serendipity[adminModule]=plugins (Plugin Startpage) and this also could help to check by type and upgradable(true) to pronounce 'none', 'event', 'sidebar', 'theme', 'check current status', (maybe even later diff) upgrade buttons.

For now these buttons just pop up all the time, as only checked by get_config('enable_plugins').
I need this for the Dashboard.

I'll come back, as I dimly remember there is some more for 1.7...

[Timbalu]

One of these dimly reminds is the one that just dropped in:

Keeping in mind we had YL's request to change the default backend to 2k11, we would need to make the core support a default/config.inc.php file too (i.e. registerPlugin('modifier'... etc. - or support all needed function in core). As this could be problematic due to other templates using the the global nav template_global_config (?), we might just allow a php config file without them... Is this possible? What do you think about it?

[yellowled]

Keeping in mind we had YL's request to change the default backend to 2k11

Huh?

* 2k11 is not a backend.
* 2k11 currently does not come with a backend theme.
* The upcoming new backend theme (yes, I do still have it on my todo list; yes, it is going very slow) is nowhere near finished.
* Said backend theme doesn't have any relation to 2k11.

(That's the smiley for “confused”.)

YL

[Timbalu]

HUH!
Certainly I meant default frontend replacing BP - this Dashboard backend makes me dizzy!

[yellowled]

I'm in no hurry to make 2k11 the default template. I guess it could be made the standard template (i.e. the one pre-selected in new installations), but it would probably require some more work to make it the default depending on whether it would be the ultimate fallback in our template fallback mechanism or not. Making it the ultimate fallback might also require an HTML5 backend as well as changes to most plugins to have a proper HTML5 experience in the frontend. This would only be possible if the plugins had some kind of “internal” fallback to deliver XHTML if any given blog did not use an HTML5 template for the frontend.

And now my brain hurts.

So, bottom line: I don't think we're in a hurry to make 2k11 either the standard or default template. I would certainly like to switch s9y to HTML5 within the next few versions, but given our manpower, I doubt it would be a smart idea …

YL

[Don Chambers]

this Dashboard backend makes me dizzy!

Because of the existing backend design, or because of the dashboard design? I've been looking at the dashboard prototype today, and had planned to post some of my personal thoughts on it if you are still looking for input. I would do so on the plugins forum where you first introduced it.

[Timbalu]

@YL, yes to be more clear, I talked about it to be the standard template.
I just remembered this config question as pending ... and it wouldn't be that much to replace PB with 2k11 for the 1.7 version.
It was my intention to have 1.7 to be a real upgrade, as its main change is Smarty 3 by now. A corresponding new standard template (maybe also optimized for Smarty 3) would be nice to have too. That would complete the package IMHO...
The other thing, which really has to wait, are those backend changes to HTML5 and being Smartified. But this is independent against a drop out of a new standard template now, isn't it?!

Because of the existing backend design, or because of the dashboard design?

Well, "both" by now, as I am trying to make all dashboard backend links to pop up in a modal container. To layer this well working, but not to much optimized, backend html/script scrumble into something new, without touching the old, is a pain.

I would do so on the plugins forum where you first introduced it.

If its a need for the public go on, or the teasing thread, else drop me a PM, please. The last post in that thread is a pending question, which I don't really want to write again as moving upwards....

[yellowled]

A corresponding new standard template (maybe also optimized for Smarty 3) would be nice to have too.

Are there any more optimizations for Smarty 3 you have in mind for 2k11?

But this is independent against a drop out of a new standard template now, isn't it?!

It's been good practice (for me) to ultimately let Garvin decide this. Switching the standard template is not that big of a deal because it really only affects new installations, but I agree that if it is done, it should be done in a major release.

2k11 is very well tested, over 30 blogs (that I know of) already use it in live blogs. It still has a few open issues in GitHub, but mostly for improvements or long-term changes. Of course, it would be nice if more plugins would emit proper HTML5 markups to go with it, but that's not a blocker, either.

YL

[Timbalu]

Are there any more optimizations for Smarty 3 you have in mind for 2k11?

Well yes, as it now considers to be working with both Smarty's and "old" vs 1.7 Serendipity versions.
If going as a standard template with a major release, named 2k12 for example, you could stick to the much better syntax of Smarty3, like foreach etc...., That would still support the further development of 2k11.

[yellowled]

Well yes, as it now considers to be working with both Smarty's and "old" vs 1.7 Serendipity versions. If going as a standard template with a major release, named 2k12 for example, you could stick to the much better syntax of Smarty3, like foreach etc...., That would still support the further development of 2k11.

I will most definitely not maintain two versions of 2k11.

Maintaining the one is enough work for a free template as it is, especially since the responsive design and the fact that it's not as easy to customize as BP (which is a good thing and will never change) brings up quite a lot of user feedback. That's likely to become even more if it's made the standard template.

So any adaptation to Smarty 3 would have to be backwards compatible for older Serendipity versions. The only alternative would be to make 2k11 work with s9y > 1.7 only. I really don't want to do that.

YL

[Timbalu]

Just to document it...:

Code: Select all

[defaultTemplate] => bulletproof

it is likely called standard, but (inner) named default... tztztz
the other one is [template_engine] = default.

[yellowled]

The default/standard terminology is just something I came up with to differentiate the two here in discussions. The whole area is very confusing in s9y – for instance, we often refer to the same thing by “template”, “theme” or even “style”. Luckily, this doesn't seem to bother anyone but me.

YL