[pLog-svn] Announcing SoylentX.com powered by a souped up Plog

Jason King jason at pixellation.com
Tue Jun 21 16:52:06 GMT 2005


What you say makes sense AND I have often thought of using Plog as a 
framework, because I like its implementation of MVC, kudos to the 
developers, but I'm not even going that far. I'm just saying that even 
to customize plog for applications for which it is intended, multi-user 
blogging that it would be really nice if there was a  way to architect 
it so that folding core code back into a mod would be easier...that 
would make customizing plog easier because it would reduce the time and 
cost of maintaining plog based projects as well as make it easier to 
share mods, hacks with the community. Right now I personally am leery of 
sharing hacks, plugins are fine, because it will cause me too much work 
to extract the stuff that people want or need, clean it up, and then 
support the questions that are invariably going to come.



Allan Sun wrote:

>     THE BIGGEST PROBLEM with customizing Plog is one that every OS project
>     faces. I as the user/developer want to hack the core so I can make
>     Plog
>     do exactly what I want it to. BUT I also want to take advantage of
>     developments and new versions. How do I do this? (That's
>     rhetorical, but
>     if you have any really good suggestions....) 
>
>  
> I've been using the Plog framework to develop my own product for a 
> long while, I got the same problem with upgrading the existing code 
> with newer version of Plog core. I think it's  because the programme 
> architecture is not cleared enough.
>  
> I do realise it's because of the performance, we have to put more 
> Plog-dedicated methods/ properties into a very generic class, e.g. 
> Model/ Template / View and even Action, the result is when I try to 
> use the Plog framework to do my own project ( which is not blog 
> related at all), I have to spend several hours on splitting the core 
> from the Plog programmes and delete lots of the Plog only methods, and 
> maybe change some methods to make more generic ( e.g the View, it's 
> using BlogInfo, which is to special).
>
> I've talked this is Oscar, and he said Plog is only a blog software, 
> and the Plog team is not aiming to provide a general framework, which 
> I think he's pretty right, so what I'm doing now is for each new 
> project I split the core from latest Plog again and again. :P
>  
> But I still wander that one day the architecture of Plog can go very 
> clear and we can easily use the Plog framework to do the re-development.
>  
> Regards,
> Allan
>  
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>pLog-svn mailing list
>pLog-svn at devel.plogworld.net
>http://devel.plogworld.net/mailman/listinfo/plog-svn
>




More information about the pLog-svn mailing list