That's the one I have in mind.Timbalu wrote:https://github.com/mathiasbynens/jquery-details ?
YL
Code: Select all
- Visual groupings of <fieldset>s for plugin output in the entry editor need to look better, coordinate with Yellowled
- Karma plugin has no output
- Create example version switch for plugins to utilize 2.0 functions
- Check where serendipity_jsSetCookie is used in plugins, because that function got removed.
- Check how "codeschmiede" and other custom admin backend templates perform in 2.0
- Create a draft blog entry for the 2.0 beta announcement
- Check why the captcha plugin does not show output in 2.0 in the plugin configuration (it results in a jquery JS output)
- Make toggling event/sidebar plugins in the plugin overview savable in a cookie
- Create a central "plugin httpPath" variable
- Check where the "use advanced javascripts" option was previously used
Please remind me that I wanted to create a screencast for this. No idea when I'll have the time for that, though. Did we have a date in mind for the beta announcement?garvinhicking wrote:- Create a draft blog entry for the 2.0 beta announcement
Not yet. I was thinking maybe end of the month / beginning of April?yellowled wrote:Please remind me that I wanted to create a screencast for this. No idea when I'll have the time for that, though. Did we have a date in mind for the beta announcement?garvinhicking wrote:- Create a draft blog entry for the 2.0 beta announcement
I wish you would call my name instead. "Timbalu" is ~10 years old and was created in a time when I did not expect to rest that long...! I still wish, I could be able to change my nick.garvinhicking wrote:you could use the Code that Timbalu posted earlier
Yes, that change was related to the template plugin hook we use to generate the smartified js, https://github.com/s9y/Serendipity/blob ... c.php#L117.garvinhicking wrote:6. I fixed the captcha plugin which did not display because the plugin API hook "external_plugin" included the genpage.inc.php handler. This shouldn't happen, is there any reason it was introduced? onli?
Please no! :/ They are designs. A template is the file with a .tpl, a style is a superficial look, but what we are providing in that section is a choice of different designs. I would reallly very much like to have finally a proper and clear wording here, and I am pretty sure that we need to have Design here for that. Not having it mixed is exactly the goal, and sticking to template - with template already used for the .tpl-files - will fortify the problem. I thought long about that change…7. I changed the wording of "Design" to "Template". We previously used the term "Theme", "Style" and "Template" in Serendpity. I do not want to add a fourth version to the mix. I checked the language file and removed "Theme" and "Style", so that everywhere we now use Template.
Hm, can't we integrate this into the plugin api, to not have to write it again and again as a plugin option?8. I promised to take a look for adding a central "plugin http path" option. Turns out, this is not feasible. The reason is that each plugin could be in its own path, so you need this option actually per-plugin, and not globally, because every plugin could be in another directory. So we need to handle it like before.
Do you want to see my suggestion (not here ofc) and discuss on this basis?3. We need to agree on some kind of "default bundled" and "default enabled" plugins. I tried to re-read the thread about this, but it's reaaaaly complicated.
Could work, I guess. I'm going to be at my girlfriend's then, which gives me a bigger upload (which is always nice for screencasts). I guess I would put this on either YouTube or Vimeo so you can just embed it in the blog post or even just link to it. Any preference?garvinhicking wrote:I was thinking maybe end of the month / beginning of April?
I'll try that. And I'll come screaming for help if I screw it up.garvinhicking wrote:So ideally, if the need arises, you could use the Code that Timbalu posted earlier in the thread, that would be good enough.
Is that the reason the Karma plugin didn't generate any backend output? (Haven't updated the dev blog to the latest 2.0 yet, just got back from a field trip.)garvinhicking wrote:5. I fixed the karma DB structure for the karmalog table, and specified the "no entries to print" option (you need to enable logging for this)
My 2 cents on that:garvinhicking wrote:7. I changed the wording of "Design" to "Template". We previously used the term "Theme", "Style" and "Template" in Serendpity. I do not want to add a fourth version to the mix. I checked the language file and removed "Theme" and "Style", so that everywhere we now use Template.
On my todo list for as soon as I get the time.garvinhicking wrote:1. <fieldset>design
Someone start a new thread for that as well, I reckon that discussion is going to get long.garvinhicking wrote:3. We need to agree on some kind of "default bundled" and "default enabled" plugins. I tried to re-read the thread about this, but it's reaaaaly complicated.
Grrrr. I was afraid that was going to happen, sorry. Will check.garvinhicking wrote:4. Please check the .tpl files for any missing i18n strings. I saw that some strings ("More") occured, without a {* i18n *} comment.
I can't think of any other system which uses “Design” to describe what we're talking about here, so it's also not very recognizable. You could even argue that while “Templates” describes the template files (.tpl), “Design” describes the stylesheets and images used. So both words don't describe very accurately what is meant. (Unfortunately.)onli wrote:I prefer Design especially because it is not overloaded with different functionality and old definitions.
I don't think WP compatibility should be a factor here, but the word does in fact describe best (even to non-devs!) what is meant …onli wrote:But I prefer Theme to Template. At least Wordpress-compatible.