• Shortcuts : 'n' next unread feed - 'p' previous unread feed • Styles : 1 2

» Publishers, Monetize your RSS feeds with FeedShow:  More infos  (Show/Hide Ads)


Date: Thursday, 06 Dec 2007 19:16
ICMS - General Discussions:: Starting to work on the code
Aweome ! I did not know we could do that ! I don' know how to do it, but we definatly need to do this !!!
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 19:15
ICMS - General Discussions:: Not commiting my own mainfile - Please help me !!!
Oh I understand now steve. Yes this could work.

Anyway, again :
Quote:
So the best thing is probably to accept that our mainfile on the SVN will get changed from time to time, but we can live with it. We can always revert the changes, it's no big deal...

Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 18:26
ICMS - General Discussions:: Keeping the changelog
I rather like how Nekro arranged them - separating fixes, etc - so it is easier to read.
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 17:09
ICMS - General Discussions:: ImpressCMS IRC channel
Quote:

Dave_L wrote:
You realize, of course, that we'll be talking about you behind your back.


HAHAHA! I'm use to it.
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 17:05
ICMS - General Discussions:: Splashscreen on ImpressCMS.org
Orange is a bit mambo-ish ... perhaps that is not a bad thing?
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 17:04
ICMS - General Discussions:: ImpressCMS Theme
WOW! #6 is Stunning! I love it!
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 16:48
ICMS - Current Release Discussions:: The "XOOPS" words all around the code
+1
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 10:15
ICMS - Current Release Discussions:: Following XOOPS changes in the futur
steve :
Quote:
Should we begin a regular code review of the commits at xo, as well as reviewing our own commits?

I think from this point on, we need to review all code derived from the xo svn - we don't want to introduce any of their problems into our code stream

This is exactly what I meant in the first post of this thread .

I absolutely agree. Would someone step to take that role ?
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 10:10
ICMS - General Discussions:: ImpressCMS nearly public yet
Ok, I have reformatted the second post I made on the Reboot group which started all this. I would like this document to become kind of the blue print document on where this project is going. Of course, it will need to evolve as time goes.

The document is hehttp://groups.google.com/group/xoops-reboot/web/impresscms

Given that document and our discussion, I would say the overall objectives of ImpressCMS are :

  • Uncompromising opened development

  • A balance between a simple and effective Content Management System and a powerfull Content Management Framework

  • Evolution of XOOPS

  • Strong emphasis on the look and feel

  • A Professional CMS, one that could be easily use in corporate and business world

  • Strong emphasis on creating communities

  • Strong emphasis on social networking tools

  • Strong emphasis on modularize development


Is this a base on something we could build a consensus on ?
Author: "--"
Send by mail Print  Save  Delicious 
Date: Thursday, 06 Dec 2007 09:51
ICMS - Future Release Discussions:: Port Team
Having a fairly good understanding of one of the products, phpGedView, here are some thoughts I have -

It would be fantastic if we could get them to produce a modularized version, or a pluggable version that hooked to iCMS! I'm just not sure how flexible they will be at this stage of their development.

Many of the other applications are quite complete, with their own user management, database factories, pdf classes, theming conventions, etc. My biggest challenge has been making PGV look like a part of the site. In fact, most of my effort goes into modifying the page outputs and stylesheets because of conflicting style definitions. Another problem is how they separate the logic from presentation (many don't, or they use a different template system)

As we go forward with this, which I definitely support, I would encourage a lot of collaboration with these projects, but we also need to understand their development strategy. If they are hell-bent on being a standalone application, an integration project will be all on us.
Author: "--"
Send by mail Print  Save  Delicious 
» You can also retrieve older items : Read
» © All content and copyrights belong to their respective authors.«
» © FeedShow - Online RSS Feeds Reader