Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2008-01-07 06:09:27
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: state of crockery
(There is no private forum for the devs.)
Offline
Re: state of crockery
Nope, there isn’t. I was refering to this subforum, which is open to the public.
Offline
Re: state of crockery
Two things I hear over and over again (I’m paraphrasing)
- “We are not doing this for free”
- “We don’t have time, resources”
A blindingly obvious solution would be to find a way to involve more people in an organized and concerted way. It wouldn’t have to mean things spin out of control. Yet every time I bring up this idea, offer my help, I meet with resistance.
So I’ll just keep using TXP, a platform I love, until it falls behind the curve enough for me to move to something more mature or better suited to my needs.
It’s a pity, because TXP has vast potential.
Offline
Re: state of crockery
mrdale wrote:
It’s a pity, because TXP has vast potential.
+1
We Love TXP . TXP Themes . TXP Tags . TXP Planet . TXP Make
Offline
Re: state of crockery
Even innocent questions and well intended criticism can sometimes feel discouraging.
fwiwI see the beginning of subsection support. I like. I also see we can expire articles. I like. I like the progress made so far.
Thanks to each of you.
Mike
Offline
Re: state of crockery
maverick wrote:
I like the progress made so far. Thanks to each of you.
+1
Offline
Re: state of crockery
- “We are not doing this for free”
Um… but I am doing this for free. Which of us isn’t?
Offline
Re: state of crockery
ruud wrote:
Um… but I am doing this for free. Which of us isn’t?
I code plugins the same reason I studied computer science in college…to meet women. ;)
Offline
Re: state of crockery
Um… but I am doing this for free. Which of us isn’t?
I think mrdale’s point was that more people could be involved developing for free. Then there’s less burden on all.
Personally, I use textpattern despite all of its faults. Since I have never posted on this before I will be explicit. Yes, I’m being critical, but no I’m not being negative — I hope everyone sees the difference.
Problems:- written in PHP, a braindead bastard of a language :-)
- code completely undocumented and almost unhackable except by an expert
- confusing documentation with stale info, much good stuff hidden in the fora, outdated plugins, etc.
- inconsistent tag syntax with much necessary stuff hidden away in plugins
- no real article workflow
- admin site not geared to end users
- lack of definitive info on future direction, progress, etc.
- architecture that is too database-dependent for my liking
- it’s free
- it’s open
- decent OOBE — easy setup
- minimal server requirements — easy to host
- good selection of plugins… though I wish fewer were required to do basic tasks
- brilliant user community with tons of timely pertinent help
I would use EE (and might in the future) except it is not free and open. I am not against paying for software but for the customers I have the price makes a real difference.
However it is the last point that really makes the difference. There are at least two other products I would have used over textpattern except that their support fora were relatively dead. Thank you everyone here for being so brilliant!
If someone wants to write an open free Python CMS that’s lightweight and easy to host, has structured, documented code and stores posts using the file system I would use it in a heartbeat. Maybe someday I’ll have time to do it myself, but I do so much other stuff in my life for free I doubt it.
robin
Offline
Re: state of crockery
OK, I’m a dork…
I meant “we’re not getting paid for this”, hopefully the larger point about involving more people in the development process was not lost.
And I should have also expressed my appreciation to all the devs for their excellent work, thus far… Again Kudos!
Last edited by mrdale (2008-01-07 22:03:42)
Offline
#23 2008-01-07 23:46:56
- guiguibonbon
- Member
- Registered: 2006-02-20
- Posts: 296
Re: state of crockery
FWIW, I’m still praying for an early pre-crockery release. (not talking about 4.0.6) Even if it’s unsupported.
Actually, somebody better go reserve appetizerPattern on google code before I make up my mind about once releasing a local txp build that’s slowly taking shape on my hard drive.
Reminds me I should turn some of it into patches. Knowing very well they won’t be accepted, but ok.
PS : tagline for appetizerPattern : “waiting for the crockery”. Got it? Got it?
Offline
Re: state of crockery
guiguibonbon wrote:
Reminds me I should turn some of it into patches. Knowing very well they won’t be accepted, but ok.
Getting patches in to crockery is not really a challenge as long as you keep the patches isolated to a single feature. Getting them in to 4.0 dev branch is a lot more difficult.
Offline