Etria Lists

Justin Ryan wrote:
> Hi everyone. :)
> 
> I thought I should mention that I got my migration to work last week:
> 
>   http://svn.qutang.net/svn/projects/COREBlog2QuillsMigration/trunk/migrateCOREBlog2Quills.py

Cool :).

[...]

> In that light, I'm thinking of copying some of Tim's work
> from QuillsEnabled to do a COREBlog2Enabled.
> 
> I'm not really a huge fan of COREBlog2 so this will be a back burner
> project, but it could really improve the story.  If several Ploneable
> blogging modules go the 'enabled' route, and have their own maintained
> migration from custom types to ATCTs, it will naturally be very easy
> to switch between blogging tools, and even to experiment with more
> than one or two over a period of time on one set of content, with no
> pain.

I'm not sure I understand what you propose.  If it's some code that 
adapts COREBlog objects to the quills.core interfaces so that they can 
use the quills views, remote blogging, etc, then that sounds great.

But then you talk about migrating COREBlog-ish content to ATCT.  That 
makes sense in that once it's ATCT content, it becomes simple to just 
use QuillsEnabled.  However, it then sounds like you are talking about 
somehow reinventing the QuillsEnabled code as COREBlog2Enabled.  I'm not 
sure what that buys you, expect a duplication of effort ;-).

If you've got time to spare, there are several things that could help 
get QuillsEnabled up to speed :)...


Tim