> Btw, I hope the actual LSP content won't be ereased during any major move
> with the site...
>
Agreed. We may have issues with user ids, but the plan is to migrate the
content. This is all hypothetical at this point. Building out the
silverstripe content types to match at least the functionality we already
have would be step 1. Migrating it all can vary in complexity.
There's of course the option of keeping all of the custom LSP code, but
CMSs don't work well that way so it will take more investigation (CMSs tend
to prefer their own frameworks requiring one of three directions... A.
Migration of LSP code to framework, convert data. B. Leverage what
silverstripe already has, convert data. C. Do nothing and use LSP as-is.
Option A. tends to be a lot of work. Option B. tends to require some
scripted data conversion. Option C sort of defeats the purpose of
switching to a CMS.
My approach would be Option B as rewriting the LSP would be a project in
itself. Converting the data can get tricky for stuff like genres, tags,
star ratings, download counters and owners. Even the views can be a
considerable amount of tweaking to get right (stuff that's been long
documented in the prevalent CMSs like Wordpress and Drupal). We'll see
how feasible this all is and we will keep the valuable data we have today.
:)
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
