Textpattern CMS support forum

You are not logged in. Register | Login | Help

#21 2011-01-17 15:03:34

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 960
Website

Re: [mention] Wordpress < > Textpattern

Bloke wrote:

Google Code doesn’t appear to allow both that and SVN at the same time, and we’re not sure of the impact on the existing repos if we start a new repo using a different system.

If Mercurial is preferred for going forward, and the desire is to stay with Google Code, why not convert the existing repos to Mercurial as well?

Offline

#22 2011-01-17 15:16:24

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,629
Website

Re: [mention] Wordpress < > Textpattern

maverick wrote:

why not convert the existing repos to Mercurial as well?

This sentence: “If want to migrate your whole history, the process is much more involved” scares me and sounds like a lot of work, compared with leaving the existing repos alone and starting a new one somewhere else :-)


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#23 2011-01-17 15:40:52

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 960
Website

Re: [mention] Wordpress < > Textpattern

Bloke wrote:

Comments should, imho, be relegated to a (core-sanctioned) plugin that you can choose to include during install or add later.

In the past I was nervous when this idea has been suggested.

  1. Minor: It meant yet another plugin
  2. While commenting may not be a universal need, it seems too important to risk letting it fall by the wayside of neglect

However, I’m completely supportive of the idea these days.

  1. As noted in other threads, Textpattern is meant to be a broadly focused CMS, not just a blogging CMS. Not every one needs comments.
  2. Commenting is part of the core, but hasn’t received a lot of attention anyway (not a criticism – just an observation). So being part of the core doesn’t guarantee active development.
  3. A basic core-sanctioned plugin means at least basic functionality will continue
  4. I already usually add several plugins to make commenting more powerful/useful on sites requiring comment functionality.
  5. If Txp’s core was refactored to enable robust feedback plugins, we are more likely to see several other plugins pop up – with different capabilities, etc. I can envision (but not code) a plugin that could make comments robust enough that it could be used as a light weight forum. (I know there’s some code out there already to that end ;) ).

So, Stef, I hope the you guys go for it on this change.

Last edited by maverick (2011-01-17 15:42:09)

Offline

#24 2011-01-17 15:47:41

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 960
Website

Re: [mention] Wordpress < > Textpattern

Bloke wrote:

compared with leaving the existing repos alone and starting a new one somewhere else :-)

fair enough :-D

Enough of our active plugin developers are on GitHub, I’m sure that has come up, and offers synergies. So moving from Google Code to somewhere else is promising.

But I’ve read that for those on Windows platforms git is not as good of an experience as Mercurial. Which is a drawback I’m assuming (since one or more of our devs are on Windows)?

Last edited by maverick (2011-01-17 15:48:32)

Offline

#25 2011-01-17 16:01:52

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,629
Website

Re: [mention] Wordpress < > Textpattern

Continuing your list:

6. A commenting plugin would mean that other plugins could more easily be used instead of the core version if somebody wanted to come up with a stonking commenting system to perhaps do what you suggested in (5). That would also keep the posse who claim they can’t live with trackback happy as they could roll their own.

I’ve no idea if such a core-sanctioned commenting idea will come to fruition as there are a large number of factors to consider (for example, some semblance of backwards compatibility, time/desire to code it when it already works1, etc). But as I say, things may fall into place.

1 this is a rather subjective term :-D

P.S. your mention of a forum reminds me that one day I should tidy up and release the refactored TXPhorum code that we worked on for a project. It’s pretty neat.

Last edited by Bloke (2011-01-17 16:03:06)


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#26 2011-01-17 16:40:08

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: [mention] Wordpress < > Textpattern

Here’s a good article on the merits of Git vs. SVN, by the author of Pro Git.

As for Windows support, most IDE’s have built in support for Git already, I know my Komodo IDE has a plugin, and honestly, the command line tools are simple.

What I envision with a system like GitHub is that rather than have people submitting patches or working on stuff on the side, which may never see the light of day (news to me that Gocom has refactored commenting), these project contributions can be branches where they can be pulled into the master when and if they prove to be worthwhile core additions.

Offline

#27 2011-01-17 16:46:02

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,629
Website

Re: [mention] Wordpress < > Textpattern

hcgtv wrote:

rather than have people submitting patches or working on stuff on the side… these project contributions can be branches where they can be pulled into the master when and if they prove to be worthwhile core additions.

fwiw, that’s how I’d prefer to work too. Just gotta set it all up on our repo of choice (I’m not doing that bit). Some stuff to iron out first though, hence the delay.

Last edited by Bloke (2011-01-17 16:47:48)


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#28 2011-01-17 17:06:36

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 960
Website

Re: [mention] Wordpress < > Textpattern

Bloke wrote:

6. A commenting plugin would mean that other plugins could more easily be used instead of the core version

That was what I was trying to get to in my overly wordy manner. You were much more articulate than I! :)

I’ve no idea if such a core-sanctioned commenting idea will come to fruition

Understood. Just wanted to add support to the idea.

I should tidy up and release the refactored TXPhorum code that we worked on for a project. It’s pretty neat.

Cool!

Offline

#29 2011-01-18 12:49:54

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 5,068
Website

Re: [mention] Wordpress < > Textpattern

Bloke wrote:

This sentence: “If want to migrate your whole history, the process is much more involved” scares me and sounds like a lot of work, compared with leaving the existing repos alone and starting a new one somewhere else :-)

The advantage of migrating the whole history is that it makes it easier to track why a certain change was made in the past, which can be helpful in understanding what a particular piece of code is/was for (I’ve used “svn blame” quite a few times for that purpose). One could argue that this could also be done by documenting the code better.

Offline

#30 2011-01-18 13:38:19

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: [mention] Wordpress < > Textpattern

ruud wrote:

One could argue that this could also be done by documenting the code better.

That would be great, more is better even though some documentation exists on a per function basis.

How about a would be programmer’s cheat sheet?

a) Database reference – Textbookmy version.
b) The Textpattern flow, index.php calls foo.php, etc.
c) An explanation of what’s where and what it does (include is the admin area).
d) If we’re doing c. why not add an explantion to each php file – as per ruud’s suggestion.

Yes, if you work with the code long enough you end up figuring things out, but it’s time taken away from productive work if you want to start contributing. I may knock WordPress here and there, but their code is very well documented.

Edit: Wordpress to WordPress dangit.

Last edited by hcgtv (2011-01-18 13:50:54)

Offline

Board footer

Powered by FluxBB