Re: [SPMSDev] Starting SPMS4

[Dan T. <da...@ta...>]

A bit of last minute revision for me saw me testing out Apache Forrest, 
a site generation system. It uses XML files to store the pages and 
either displays them dynamically or generates static HTML.

I have put together the start of a forrest powered site for SPMS which 
can be found here http://www.taylord1.co.uk/forrest/ personnally I 
prefer this over Mambo, for the sort of site we are creating the static 
and dynamic capabilities of Forrest will suit us well.

Please let me know what you guys think of this.

~Dan


Fleet Admiral Sorac Dunar wrote:

>I agree with those server specs.
>
>-Ed
>
>Dan Taylor wrote:
>
>  
>
>>Ed,
>>
>>That is my plan so far, the only thing thats currently in code are the
>>core classes. These are all code I'm importing from another project I
>>did this year to save us re-inventing the wheel. This means we have a
>>database API, Theme Class API and Error Logging API already to use for
>>SPMS4 (The phpdocumentor documentation for them will be online when I
>>am finished tweaking the comments.)
>>
>>I've set up some tasks on the sourceforge site detailing what needs to
>>be done and in what order, feel free to add to them or modify them as
>>necessary. They have mainly been written for me by me.
>>
>>I've given over my domain taylord1.co.uk to SPMS Development, I'm not
>>sure Mambo is the correct software for the site. I'm playing around
>>with using Apache Forrest and Apache Lenya to generate the site.
>>
>>As I type this I am preparing to upload some changes to the SPMS3
>>repositry, I have found a few bugs in the copy of 3.0.3 that need to
>>be fixed. The main changes I'm making are cleaning up some of the
>>admin area code that needed cleaning up this time last year, and
>>updating the application form (Implementing client side validation,
>>and cleaning up the emails which are sent). When my changes are in
>>there, I'll give you and Darian the nod that its ready for another
>>test. Then we can put out a 3.0.4 release (http://serenity.tf72.org/
>>currently reports as being SPMS 3.0.4 Alpha because I'm implementing
>>these fixes there).
>>
>>So far I've had some feedback from SPMS users regarding my ideas for
>>SPMS4, I'm hoping to generate some community backing for this project.
>>The only way to describe what they have requested is a full content
>>management system. So thats the direction my Version 4 design is
>>heading to.
>>
>>I've had one person step forward and offer thier assistance with a
>>SPMS Documentation Project, to provide user guides for version 4. It's
>>DrDanielJackson from AceIRC, so Darian and I already know him. Once he
>>has a sourceforge account I'm going to add him to the project and give
>>him access to the SourceForge Documentation Manager, once the design
>>is complete we can begin writting the documentation as each section is
>>completed.
>>
>>One thing I do want to throw in the air now is the hosting
>>requirements of SPMS4,  I'm aiming for it to be deployed to web
>>servers running PHP 4.X and MySQL 3 or above. Are you and Darian happy
>>with this? I still feel its too early to create PHP5 only software,
>>and most webhosts haven't moved to MySQL 4, so there is little point
>>using the features provided by either.
>>
>>~Dan
>>
>>Fleet Admiral Sorac Dunar wrote:
>>
>>    
>>
>>>Dan,
>>>
>>>I would like for the Requirements listing you are putting together to be
>>>public before we get started on any coding.
>>>
>>>I would like us to have a solid requirements document put together, and
>>>then additionally a solid design document detailing how each of the
>>>requirements will be implemented. they should be two documents and the
>>>three of us as project admins should review both documents before they
>>>are made public.
>>>
>>>Once that is done it makes it easier to assign tasks to other developers
>>>for them to start working on.
>>>
>>>Once you get your thgouhts together start posting them here and we can
>>>work throguh the whole thing.
>>>
>>>-Ed
>>>
>>>Dan Taylor wrote:
>>>
>>> 
>>>
>>>      
>>>
>>>>Hey Folks,
>>>>
>>>>As your both aware I've started doing things towards a new version of
>>>>SPMS, despite my leanings towards Java code recently SPMS will
>>>>continue to be a PHP project (However, I have considered a Java Port
>>>>;)).
>>>>
>>>>Initially I'm calling this SPMS4 rather than SPMS 3.1, all of the
>>>>version 3 source code and database layout has been dropped. I'm
>>>>re-developing SPMS from the ground up, this is in response to the
>>>>feedback I've been given by users and because of my own experiences
>>>>with SPMS. The main aim of the project is to remove a series of
>>>>security concerns I have with version 3, and to re-build the core of
>>>>SPMS in to a series of objects. Additionally I am going to be adding
>>>>functionality beyond that provided by previous versions of SPMS.
>>>>
>>>>I tidied up the Sourceforge site a little yesterday, I have disabled
>>>>CVS access for everyone but us at the moment. While I'm working on the
>>>>SPMSCore package I would prefer it if I was the only person committing
>>>>code to the repository, I have set up a CVS ACL which limits commit
>>>>rights to the three of us (Yeah, we're the only ones on this list
>>>>right now too, I'll add other people back if they request it).
>>>>
>>>>Currently I have a draft requirements list for SPMS4, as I analyse
>>>>each requirement I'm designing it too. Currently I have a firm design
>>>>for the SPMSCore Package and for the manifest system, other sections
>>>>of the system will be designed as a get through the mountain of
>>>>possible additions and modifications to version 3.
>>>>
>>>>As I get further through this I'll send out more updates, because I'm
>>>>LOA from stuff Thursday and Friday this week I suspect I'll have most
>>>>of the Core written (hotel rooms are lonely places ;))
>>>>
>>>>~Dan
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>SF.Net email is Sponsored by the Better Software Conference & EXPO
>>>>September 19-22, 2005 * San Francisco, CA * Development Lifecycle
>>>>Practices
>>>>Agile & Plan-Driven Development * Managing Projects & Teams * Testing
>>>>& QA
>>>>Security * Process Improvement & Measurement *
>>>>http://www.sqe.com/bsce5sf
>>>>_______________________________________________
>>>>Spms-developer mailing list
>>>>Spm...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/spms-developer
>>>>
>>>>
>>>>  
>>>>        
>>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>SF.Net email is Sponsored by the Better Software Conference & EXPO
>>>September 19-22, 2005 * San Francisco, CA * Development Lifecycle
>>>Practices
>>>Agile & Plan-Driven Development * Managing Projects & Teams * Testing
>>>& QA
>>>Security * Process Improvement & Measurement *
>>>http://www.sqe.com/bsce5sf
>>>_______________________________________________
>>>Spms-developer mailing list
>>>Spm...@li...
>>>https://lists.sourceforge.net/lists/listinfo/spms-developer
>>>
>>>
>>>
>>>
>>> 
>>>
>>>      
>>>
>>
>>-------------------------------------------------------
>>SF.Net email is Sponsored by the Better Software Conference & EXPO
>>September 19-22, 2005 * San Francisco, CA * Development Lifecycle
>>Practices
>>Agile & Plan-Driven Development * Managing Projects & Teams * Testing
>>& QA
>>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>>_______________________________________________
>>Spms-developer mailing list
>>Spm...@li...
>>https://lists.sourceforge.net/lists/listinfo/spms-developer
>>
>>
>>    
>>
>
>
>
>
>-------------------------------------------------------
>SF.Net email is Sponsored by the Better Software Conference & EXPO
>September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>_______________________________________________
>Spms-developer mailing list
>Spm...@li...
>https://lists.sourceforge.net/lists/listinfo/spms-developer
>
>
>
>
>  
>