[geeklog-devel] [geeklog-cvs] Geeklog-1.x
Mark R. Evans
mevans at ecsnet.com
Sun Nov 25 20:14:57 EST 2007
I appreciate the support and that the XHTML code was committed. My comment
was that this is now a great new feature for Geeklog.
My point was that the template caching library could also be a great new
feature as well. It has been decided that it will wait until the next
release. I don't buy the code freeze argument, as the freeze really wasn't
a freeze at all, or at least for all.
I honestly don't care anymore. As much fun as this all has been, I've tried
to make my point, it was either received or not. I accomplished what I
wanted, that was to voice one man's opinion on all this. That I've done,
now I'm done.
I'll go back to working on my plugins and theme enhancements and leave the
release stuff to you guys.
On 11/25/07, Blaine Lang <devel at portalparts.com> wrote:
> Mark R. Evans wrote:
> > Let's see, Blaine committed a new feature just this week. I'm sure I
> > could go dig through CVS and find a few more, but why bother...
> > The reason I am so passionate about this is that there are a few
> > things with Geeklog v1.5 that really bring Geeklog to a point that it
> > is truly an incredible CMS. The new installation and online
> > configuration are wonderful enhancements that addressed an area where
> > Geeklog needed a shot in the arm.
> > The XHTML capability now opens up Geeklog to some incredible options.
> > Eric and I will be releasing some theming tools and techniques that
> > will allow pure CSS driven designs and still maintain Geeklog's
> > flexibility of having dynamic layouts (1,2 or 3 columns).
> > The final area where Geeklog needs improvement is the template
> > engine. What Joe has done is perfect. It is 100% backward
> > compatible, it provides a speed improvement and introduces new
> > features to significantly improve how templates are used.
> > As I sit on the sidelines and watch all this unfold, it basically
> > pisses me off that Joe goes to all this effort, I champion it and
> > provide benchmarking, testing and validation and it is completely
> > ignored, over and over. After 3 months of begging on this list for at
> > least a response, we get 'Better luck next time' with a reference to a
> > freeze that was selective at best.
> > If I could actually find an ounce of logic in all this I wouldn't
> > bother with this post, but it simply makes no sense to me. How do you
> > ignore something that provides such value with little risk. How do
> > you ignore all this work and effort for so long to end it with 'Better
> > luck next time'. How do you believe there will be a next time when
> > this is how it was treated this time?
> > Confused....
> > Mark
> Mark, I thought Dirk, Oliver and I had already mentioned, you had our
> support and we were committing the XHTML patch and supporting the Theme
> work that you and Eric have been doing. It sounds like we have not made
> that clear by these comments - but maybe we are just not moving fast
> But sure, if you guys want me to pull that admin feature out I will not
> that I see the sense in that.
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel