Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Tabless in future
I think “should I wait for crockery ?” is what many plugin devs are wondering
I think that you’re projecting your own thoughts on the rest of the plugin devs.
No, you should not wait for crockery (or 4.0.6 for that matter). Now is what matters.
But you’ll have to agree that at one point it will have to be fixed. And that’s not what I had in mind when I said crockery is not being developed with plugin devs in mind. I’m thinking of all the plugins that will be broke.
Sure it will have to be fixed… but seriously, do you really think it takes that much time to update a plugin for such a backend change? I think not. Also, some plugins will no longer be needed in 4.1, so there’s no need to fix those plugins. I’m guessing the amount of plugins that would break by switching to a tableless design is minimal. Doing so in 4.0.x would have a larger impact.
4.1.0 shouldn’t have that many bells and whistles
What bells and whistles are you talking about?
Offline
#26 2007-09-05 17:16:45
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: Tabless in future
What bells and whistles are you talking about?
Most of these, actually, for a starter (ok, maybe not nested sections and the new database query functions). Rewriting the whole section-admin. Hell, most of what I’ve read so far you’re planning to add. Many are nice, but certainly not a priority. What I would love to be able to work with already is the new parser, the new image-class, the exclude attribute, nested categories that work,….
No, you should not wait for crockery (or 4.0.6 for that matter). Now is what matters.
We’ve been waiting to tackle image management, admin-looks etc. for ages, yet the conclusion is always ‘those will be done in crockery’. So here we are, waiting.
Offline
#27 2007-09-05 17:33:19
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: Tabless in future
Also, some plugins will no longer be needed in 4.1, so there’s no need to fix those plugins.
I think those are rarely back-end plugins.
do you really think it takes that much time to update a plugin for such a backend change?
Not on its own, no, but together with all the other changes, yes. That’s why I’m suggesting you start off as early as possible with a release (or candidate) that includes all the changes that will break stuff. That way everyone will be prepared. Don’t delay the hard pill, make it quick to swallow.
Last edited by guiguibonbon (2007-09-05 17:33:35)
Offline
Re: Tabless in future
Not nearly all the changes that might break stuff are in crockery at the moment.
Personally, I think ‘release early, release often’ is nice for some software projects, but not for all.
Btw, the history file hasn’t been updated since the end of 2005, so that’s not really an accurate source of info on the state of crockery.
Offline
#29 2007-09-05 17:57:56
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: Tabless in future
Not nearly all the changes that might break stuff are in crockery at the moment.
That’s exactly what I’m pinpointing here. That’s where it should all have started.
Personally, I think ‘release early, release often’ is nice for some software projects, but not for all.
If you guys are sure about your stuff, so be it :) Let’s hope you’re right and I’m too easily worried. (But please, don’t be too precautious with 4.0.x)
Btw, the history file hasn’t been updated since the end of 2005, so that’s not really an accurate source of info on the state of crockery.
I know (see above); it was just an easy place to start. Please update it though, that would be cool.
Last edited by guiguibonbon (2007-09-05 18:00:48)
Offline