I feel like the wheel is being reinvented. What I was thinking of doing
actually with LSP is setting it up
a local dev version on my server and work on overall improvements offline
and slowly push changes to the live server. What I am not sure how to deal
with yet is if a new database is created and the current database content
gets dumped, or just get rid of all the current content on LSP and build it
up from scratch.
I am willing to host LSP, but have all the files uploaded to SF as well as
use django. I can get something more up to date in terms of the back end
compared to what SF uses.
On Tue, Apr 22, 2014 at 7:13 PM, Tobias Doerffel
<tobias.doerf...@gmail.com>wrote:
> Hi,
>
> 2014-04-22 19:10 GMT+02:00 Jonathan Aquilina <eagles051...@gmail.com>:
> > What I am trying to avoid is starting from scratch. We have the code
> ready
> > to go. And I already see ways I can improve on the current lsp code.
>
> I won't stop you from doing so but the current code base really is a
> mess and the DB model etc. very inflexible. Are you sure want to work
> on this code base instead of starting something clean with the help of
> a modern and powerful framework (like Django) so you can save lots of
> code?
>
> Toby
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Lmms-users mailing list
Lmms-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-users
