I'm with Dave, although I now know my servers support php5, there are still some hosts which don't and maybe won't for a while.
I think at least we could phase it out slowly and include it within a road map, rather than going whole hog now.
I have to say sorry... i was working at the same time than skenow and at the same time i was making some mistakes in the code (SORRY SKENOW!!!!) ... i think that we keep going in the same way with the changelog... i just make some mistakes in that moments... sorry again boys!...
i agree skenow ... another point is that PHP4 lose official PHP support at the begin of the 2008 ... soo ... i think most hosting server will migrate forced... i dont see the point or supporting a non supported PHP Version
Similar to our discussion about 'xoops' in the code and output, I think we should follow the same philosophy - for compatibility, we leave existing code at PHP4. For new functionality, use PHP5
Quote:
Should we should keep ImpressCMS compatible with PHP4 at least until we gain a "critical mass" of XOOPS users? I suppose it would be helpful to know how many people are still using PHP4.
Indeed, I did update my changelog from svn just before committing the other files. But, if even one person doesn't, the problem occurs.
I didn't know if there was something else that could be set for the changelog to enforce more careful commits to it.
If I recall correctly, the XOOPS core team tentatively decided to retain PHP4 compatibility for 2.0, 2.2 and 2.3/2.4 (2.0 + 2.2 merge), and that 2.5/2.6 would be the first version to require PHP5.
If we abandon PHP4 compatibility too soon, XOOPS users whose servers don't have PHP5 will be forced to stay with XOOPS rather than upgrading to ImpressCMS.
Should we should keep ImpressCMS compatible with PHP4 at least until we gain a "critical mass" of XOOPS users? I suppose it would be helpful to know how many people are still using PHP4.
yes, i made it a practice, that before i even do any committing I always do an update of my local svn repository beforehand, and then merge my local changes/edits into the freshly updated version, then I commit my changes.
There may be a better method for the language support later on - but for now, this is generally thought to be one of the easiest methods to maintain.
I think this would be a very sensible move.
Something to put on the roadmap for sure.
Before committing the new change log, did you update your working copy from the repository? I thought that SVN had the ability to deal with this kind of issue (people making different changes to the same file).
References:
Basic Work Cycle
Resolve Conflicts (Merging Others' Changes)
IMHO, yes. Given that PHP4 is EOL, I think we should only focus on PHP5 compatibility.
IMHO, percent. Perhaps 95%.
Hi to all. Some time ago i had to do some work with Xoops, and i really like it. However i disagree in some points on how xoops is going on.I was looking what do you want for ImpressCms and i really like it, more than xoops. So talking with nekro, a friend of mine, I told him i wanted to participate in ImpressCms.
So if you are agree, i want to contribute in the way is needed. Making documentation, translating or writing code.
I liked A LOT!! the purpose for the new impress theme. It 's great.
Best regards,
Saganxis
No2, green
Loose the !
Quote:
3. A logo consists of an imagemark and a wordmark. It would be great to have both.
Ok, anyone has something to suggest so we don't have this problem ?
thanks for all the motivating comments. I'm ready to work on it this weekend.
But then I do need to know at least the width, because percent and fixed width would have different layouts. If I made the 960 fixed width and then was asked to change to percent it could be I need to redo some of the css and html.
960px fixed with or percent?