From websitemaster at cogeco.net Thu Apr 5 09:57:15 2012 From: websitemaster at cogeco.net (Tom) Date: Thu, 5 Apr 2012 09:57:15 -0400 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> Message-ID: <05ee01cd1334$021e26d0$065a7470$@cogeco.net> Hey Rouslan, After thinking about it a bit more. Did you want to go this route? In the future I see us wanting to know more about the themes themselves, like what version of Geeklog it is for, author, etc. and this would be a good spot to put this information. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: March-29-12 9:20 PM To: Geeklog Development Subject: Re: [geeklog-devel] Constant XHTML > 2) Create a new theme file that contains the doc type info that can be > loaded before the language files. I would think this would be the cleanest solution. I suspect themes that don't have the file accept the default site-wide doctype. I would also make this a .php file as there might be other $_CONF vars the theme needs control of. -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Thu Apr 5 10:04:56 2012 From: websitemaster at cogeco.net (Tom) Date: Thu, 5 Apr 2012 10:04:56 -0400 Subject: [geeklog-devel] Geeklog error.log Message-ID: <05fc01cd1335$14fc35c0$3ef4a140$@cogeco.net> Does anyone have any problem with me adding the remote ip address of the user that caused the log entry in the error log? This is just to help identify any hack attempts and make it easier for admins to ban ips. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From cordiste at free.fr Thu Apr 5 12:10:37 2012 From: cordiste at free.fr (cordiste) Date: Thu, 5 Apr 2012 18:10:37 +0200 Subject: [geeklog-devel] Geeklog error.log In-Reply-To: <05fc01cd1335$14fc35c0$3ef4a140$@cogeco.net> References: <05fc01cd1335$14fc35c0$3ef4a140$@cogeco.net> Message-ID: +1 adding the remote ip address Ben 2012/4/5 Tom : > Does anyone have any problem with me adding the remote ip address of the > user that caused ?the log entry in the error log? > > > > This is just to help identify any hack attempts and make it easier for > admins to ban ips. > > > > Tom > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From rouslan at placella.com Thu Apr 5 14:06:29 2012 From: rouslan at placella.com (Rouslan Placella) Date: Thu, 05 Apr 2012 19:06:29 +0100 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <05ee01cd1334$021e26d0$065a7470$@cogeco.net> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> Message-ID: <4F7DDF25.4020104@placella.com> Ok for me :) On 05/04/12 14:57, Tom wrote: > Hey Rouslan, > > > > After thinking about it a bit more. Did you want to go this route? > > > > In the future I see us wanting to know more about the themes themselves, > like what version of Geeklog it is for, author, etc. and this would be a > good spot to put this information. > > > > Tom > > > > > > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello > Sent: March-29-12 9:20 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Constant XHTML > > > >> 2) Create a new theme file that contains the doc type info that can be >> loaded before the language files. > > > > I would think this would be the cleanest solution. I suspect themes that > don't have the file accept the default site-wide doctype. > > > > I would also make this a .php file as there might be other $_CONF vars the > theme needs control of. > > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Fri Apr 6 10:58:25 2012 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 6 Apr 2012 16:58:25 +0200 Subject: [geeklog-devel] Geeklog 2.0.0 Schedule In-Reply-To: References: <011401cd0b58$0711ff60$1535fe20$@cogeco.net> Message-ID: <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> Vincent Furia wrote: > I would suggest a beta release now with a note that these last issues are outstanding. The more eyes on this release the better. Right. The issues that have been discussed on here all seem to be closed now, but there are still a few listed in the Roadmap section: http://project.geeklog.net/tracking/roadmap_page.php In order to avoid further feature creep and delay, I'd suggest moving them to the next release. I've added versions 2.0.1 and 2.1.0 to the bugtracker - move as you see fit. > Name the new Theme - Ideas? > I'm not all that creative when it comes to the naming of things like this, but if we're going to use it on geeklog.net, we could name it after the release: "Geeklog2.0" I'm notoriously bad with this as well, but the name "Open" just popped into my head. How do we proceed? Vote? bye, Dirk -- http://www.themobilepresenter.com/ From websitemaster at cogeco.net Fri Apr 6 15:21:54 2012 From: websitemaster at cogeco.net (Tom) Date: Fri, 6 Apr 2012 15:21:54 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Schedule In-Reply-To: <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> References: <011401cd0b58$0711ff60$1535fe20$@cogeco.net> <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> Message-ID: <007101cd142a$87afa6b0$970ef410$@cogeco.net> Sounds good. Though a few of them have been handled and just need to be closed 0001384: [Feature Requests] Improve strength of password hashing (vinny) - assigned. 0001255: [Feature Requests] Update the Professional theme to use divs, etc.. instead of tables - confirmed. (this is the new theme being worked on now I guess) So what is this release then a beta or RC? Stuff that really needs to be tested is the topic stuff (from the list I posted a while ago). Plus nothing evolving mssql or pgsql has been tested as far as I know. Theme Name suggestions so far is Modern Curve Geeklog2 Open It doesn't really matter to me ... all are fine ... I guess I would vote for Geeklog2 then So it looks like before this release as well we will be adding another file to the theme called initial or theme (or something else) that will be a php file and will solve the problem of declaring the doc type of the theme first so the language files will know what to do. If the file is not present then the doc type defined in the configuration will be assumed. I don't think we need to wait for the new theme to be ready before this beta/rc release but it should be ready for the final release. I do think we should include the new theme (along with the professional theme) in the beta/rc release at whatever state it is in so users can see where we are at. Thoughts? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: April-06-12 10:58 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 2.0.0 Schedule Vincent Furia wrote: > I would suggest a beta release now with a note that these last issues are outstanding. The more eyes on this release the better. Right. The issues that have been discussed on here all seem to be closed now, but there are still a few listed in the Roadmap section: http://project.geeklog.net/tracking/roadmap_page.php In order to avoid further feature creep and delay, I'd suggest moving them to the next release. I've added versions 2.0.1 and 2.1.0 to the bugtracker - move as you see fit. > Name the new Theme - Ideas? > I'm not all that creative when it comes to the naming of things like this, but if we're going to use it on geeklog.net, we could name it after the release: "Geeklog2.0" I'm notoriously bad with this as well, but the name "Open" just popped into my head. How do we proceed? Vote? bye, Dirk -- http://www.themobilepresenter.com/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Fri Apr 6 15:43:37 2012 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 6 Apr 2012 21:43:37 +0200 Subject: [geeklog-devel] Geeklog 2.0.0 Schedule In-Reply-To: <007101cd142a$87afa6b0$970ef410$@cogeco.net> References: <011401cd0b58$0711ff60$1535fe20$@cogeco.net> <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> <007101cd142a$87afa6b0$970ef410$@cogeco.net> Message-ID: <41C1517C-7A1D-40B6-83DE-46D6C96B77FD@haun-online.de> Tom wrote: > So what is this release then a beta or RC? I'd say we should go with a beta. And make it really clear that it's going to break things. > I don't think we need to wait for the new theme to be ready before this > beta/rc release but it should be ready for the final release. Agreed. We could ship both Professional and the new one in the beta. Speaking of themes, what happened to the page navigation? It looks really ugly right now (screenshot from Professional attached - hope it makes it through). bye, Dirk -- http://www.themobilepresenter.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Firefox088.png Type: image/png Size: 2069 bytes Desc: not available URL: From rouslan at placella.com Fri Apr 6 16:31:40 2012 From: rouslan at placella.com (Rouslan Placella) Date: Fri, 06 Apr 2012 21:31:40 +0100 Subject: [geeklog-devel] Geeklog 2.0.0 Schedule In-Reply-To: <41C1517C-7A1D-40B6-83DE-46D6C96B77FD@haun-online.de> References: <011401cd0b58$0711ff60$1535fe20$@cogeco.net> <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> <007101cd142a$87afa6b0$970ef410$@cogeco.net> <41C1517C-7A1D-40B6-83DE-46D6C96B77FD@haun-online.de> Message-ID: <4F7F52AC.1050401@placella.com> On 06/04/12 20:43, Dirk Haun wrote: > Tom wrote: > >> So what is this release then a beta or RC? > > I'd say we should go with a beta. And make it really clear that it's going to > break things. > > >> I don't think we need to wait for the new theme to be ready before this >> beta/rc release but it should be ready for the final release. > > Agreed. We could ship both Professional and the new one in the beta. > > > Speaking of themes, what happened to the page navigation? It looks really ugly > right now (screenshot from Professional attached - hope it makes it through). > This: http://project.geeklog.net/tracking/view.php?id=1422 Bye, Rouslan From dirk at haun-online.de Fri Apr 6 16:50:12 2012 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 6 Apr 2012 22:50:12 +0200 Subject: [geeklog-devel] Geeklog 2.0.0 Schedule In-Reply-To: <4F7F52AC.1050401@placella.com> References: <011401cd0b58$0711ff60$1535fe20$@cogeco.net> <42BF9816-ED13-402E-B630-AC297930135F@haun-online.de> <007101cd142a$87afa6b0$970ef410$@cogeco.net> <41C1517C-7A1D-40B6-83DE-46D6C96B77FD@haun-online.de> <4F7F52AC.1050401@placella.com> Message-ID: <41E68DD0-370A-4282-B894-F62BB7F62E1F@haun-online.de> Rouslan Placella wrote: >> Speaking of themes, what happened to the page navigation? It looks really ugly >> right now (screenshot from Professional attached - hope it makes it through). >> > > This: http://project.geeklog.net/tracking/view.php?id=1422 Ah okay, I thought I saw something about changes to the page navigation but couldn't remember where. Anyway, as I said, it's ugly. Specifically, the screenshot in that issue has a box around the current page which doesn't show up for me (Firefox 11). Also, the colors look the wrong way around to me, i.e. the non-current pages seem highlighted. I appreciate the attempt to make the clickable area larger and easier to hit, but the huge boxes look out of place there. Steal from Flickr if you must, but someone please make this a little more aesthetically pleasing. Thanks. bye, Dirk -- http://www.themobilepresenter.com/ From rouslan at placella.com Mon Apr 9 07:47:22 2012 From: rouslan at placella.com (Rouslan Placella) Date: Mon, 09 Apr 2012 12:47:22 +0100 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <05ee01cd1334$021e26d0$065a7470$@cogeco.net> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> Message-ID: <4F82CC4A.2080208@placella.com> How about dropping functions.php and having a file with actual functions in it for the theme? e.g.: // returns an array, where one of the entries is the doctype theme_getConfig_newpro() // returns an array of CSS files theme_getCss_newpro() // returns an array of JS files theme_getJS_newpro() // other stuff theme_init_newpro() Then we can include the file at any point and only call the functions when needed. Bye, Rouslan On 05/04/12 14:57, Tom wrote: > Hey Rouslan, > > > > After thinking about it a bit more. Did you want to go this route? > > > > In the future I see us wanting to know more about the themes themselves, > like what version of Geeklog it is for, author, etc. and this would be a > good spot to put this information. > > > > Tom > > > > > > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello > Sent: March-29-12 9:20 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Constant XHTML > > > >> 2) Create a new theme file that contains the doc type info that can be >> loaded before the language files. > > > > I would think this would be the cleanest solution. I suspect themes that > don't have the file accept the default site-wide doctype. > > > > I would also make this a .php file as there might be other $_CONF vars the > theme needs control of. > > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Mon Apr 9 09:34:02 2012 From: websitemaster at cogeco.net (Tom) Date: Mon, 9 Apr 2012 09:34:02 -0400 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <4F82CC4A.2080208@placella.com> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> <4F82CC4A.2080208@placella.com> Message-ID: <010201cd1655$6d6502a0$482f07e0$@cogeco.net> Hmmm... I didn't think of doing it this way. It makes sense to only have one file with functions in it. Do we need theme_getCss_newpro and theme_getJS_newpro though? Can't they just set this in theme_init_newpro? Also, should we still partially support functions.php for now if found (for a few Geeklog versions) or just the new file? We are at Geeklog 2.0 so if we did do a straight switch I guess the time would be now since we have other incompatibilities. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan Placella Sent: April-09-12 7:47 AM To: Geeklog Development Subject: Re: [geeklog-devel] Constant XHTML How about dropping functions.php and having a file with actual functions in it for the theme? e.g.: // returns an array, where one of the entries is the doctype theme_getConfig_newpro() // returns an array of CSS files theme_getCss_newpro() // returns an array of JS files theme_getJS_newpro() // other stuff theme_init_newpro() Then we can include the file at any point and only call the functions when needed. Bye, Rouslan On 05/04/12 14:57, Tom wrote: > Hey Rouslan, > > > > After thinking about it a bit more. Did you want to go this route? > > > > In the future I see us wanting to know more about the themes > themselves, like what version of Geeklog it is for, author, etc. and > this would be a good spot to put this information. > > > > Tom > > > > > > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe > Mucchiello > Sent: March-29-12 9:20 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Constant XHTML > > > >> 2) Create a new theme file that contains the doc type info that can >> be loaded before the language files. > > > > I would think this would be the cleanest solution. I suspect themes > that don't have the file accept the default site-wide doctype. > > > > I would also make this a .php file as there might be other $_CONF vars > the theme needs control of. > > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Mon Apr 9 09:49:42 2012 From: rouslan at placella.com (Rouslan Placella) Date: Mon, 09 Apr 2012 14:49:42 +0100 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <010201cd1655$6d6502a0$482f07e0$@cogeco.net> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> <4F82CC4A.2080208@placella.com> <010201cd1655$6d6502a0$482f07e0$@cogeco.net> Message-ID: <4F82E8F6.9080708@placella.com> On 09/04/12 14:34, Tom wrote: > Hmmm... > > I didn't think of doing it this way. > > It makes sense to only have one file with functions in it. > > Do we need theme_getCss_newpro and theme_getJS_newpro though? Can't they > just set this in theme_init_newpro? We don't _need_ them, but I think that it's cleaner that way. > Also, should we still partially support functions.php for now if found (for > a few Geeklog versions) or just the new file? We are at Geeklog 2.0 so if we > did do a straight switch I guess the time would be now since we have other > incompatibilities. I vote for breaking things once again :) > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan > Placella > Sent: April-09-12 7:47 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Constant XHTML > > How about dropping functions.php and having a file with actual functions in > it for the theme? > > e.g.: > // returns an array, where one of the entries is the doctype > theme_getConfig_newpro() > // returns an array of CSS files > theme_getCss_newpro() > // returns an array of JS files > theme_getJS_newpro() > // other stuff > theme_init_newpro() > > Then we can include the file at any point and only call the functions when > needed. > > Bye, > Rouslan > > > On 05/04/12 14:57, Tom wrote: >> Hey Rouslan, >> >> >> >> After thinking about it a bit more. Did you want to go this route? >> >> >> >> In the future I see us wanting to know more about the themes >> themselves, like what version of Geeklog it is for, author, etc. and >> this would be a good spot to put this information. >> >> >> >> Tom >> >> >> >> >> >> From: geeklog-devel-bounces at lists.geeklog.net >> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe >> Mucchiello >> Sent: March-29-12 9:20 PM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] Constant XHTML >> >> >> >>> 2) Create a new theme file that contains the doc type info that can >>> be loaded before the language files. >> >> >> >> I would think this would be the cleanest solution. I suspect themes >> that don't have the file accept the default site-wide doctype. >> >> >> >> I would also make this a .php file as there might be other $_CONF vars >> the theme needs control of. >> >> >> >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From komma at ivywe.co.jp Mon Apr 9 15:33:47 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Tue, 10 Apr 2012 04:33:47 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: Message-ID: Hi, Ben You are right, I think. Non table layout is important. WordPress and XOOPS cube CMS use non table layout and responsive web design as default theme. Responsive web design is very important because we use iPad, iPhone, Android, too. And all of them support JavaScript. HTML does not require table tag for layout. Table layout is old fashioned web design. 2012/3/15 cordiste : > Can someone explain to me where is the issue with non table layout? > Purepro theme [1] can use 1, 2 or 3 columns even with JS disabled. > > Ben From danstoner at gmail.com Mon Apr 9 17:00:52 2012 From: danstoner at gmail.com (Dan Stoner) Date: Mon, 9 Apr 2012 17:00:52 -0400 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: Message-ID: I would definitely like to be able to blog more easily from my (Android) phone. - Dan Stoner 2012/4/9 ???? Geeklog IvyWe : > Hi, Ben > > You are right, I think. > Non table layout is important. > > WordPress and XOOPS cube CMS use non table layout and > responsive web design as default theme. > > Responsive web design is very important because we use iPad, iPhone, > Android, too. > And all of them support JavaScript. > > HTML does not require table tag for layout. > Table layout is old fashioned web design. > > > 2012/3/15 cordiste : >> Can someone explain to me where is the issue with non table layout? >> Purepro theme [1] can use 1, 2 or 3 columns even with JS disabled. >> >> Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Tue Apr 10 10:03:39 2012 From: websitemaster at cogeco.net (Tom) Date: Tue, 10 Apr 2012 10:03:39 -0400 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <4F82E8F6.9080708@placella.com> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> <4F82CC4A.2080208@placella.com> <010201cd1655$6d6502a0$482f07e0$@cogeco.net> <4F82E8F6.9080708@placella.com> Message-ID: <01a301cd1722$baa058d0$2fe10a70$@cogeco.net> Okay, Does this sound good to you Vinny? (asking since hopefully at some point the GSOC Template Engine Upgrade project may happen) We might as well use the same file then (functions.php). This way it will get included and old themes will still work most of the time (with the default setting of error reporting) even if they do not include the new functions. Could you also do a quick update in the wiki with the new functions then (since functions.php is only mentioned in the tips section) http://wiki.geeklog.net/index.php/Theme_Developers_Guide http://wiki.geeklog.net/index.php/Themes_and_XHTML Thanks Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan Placella Sent: April-09-12 9:50 AM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] Constant XHTML On 09/04/12 14:34, Tom wrote: > Hmmm... > > I didn't think of doing it this way. > > It makes sense to only have one file with functions in it. > > Do we need theme_getCss_newpro and theme_getJS_newpro though? Can't > they just set this in theme_init_newpro? We don't _need_ them, but I think that it's cleaner that way. > Also, should we still partially support functions.php for now if found > (for a few Geeklog versions) or just the new file? We are at Geeklog > 2.0 so if we did do a straight switch I guess the time would be now > since we have other incompatibilities. I vote for breaking things once again :) > Tom > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan > Placella > Sent: April-09-12 7:47 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Constant XHTML > > How about dropping functions.php and having a file with actual > functions in it for the theme? > > e.g.: > // returns an array, where one of the entries is the doctype > theme_getConfig_newpro() > // returns an array of CSS files > theme_getCss_newpro() > // returns an array of JS files > theme_getJS_newpro() > // other stuff > theme_init_newpro() > > Then we can include the file at any point and only call the functions > when needed. > > Bye, > Rouslan > > > On 05/04/12 14:57, Tom wrote: >> Hey Rouslan, >> >> >> >> After thinking about it a bit more. Did you want to go this route? >> >> >> >> In the future I see us wanting to know more about the themes >> themselves, like what version of Geeklog it is for, author, etc. and >> this would be a good spot to put this information. >> >> >> >> Tom >> >> >> >> >> >> From: geeklog-devel-bounces at lists.geeklog.net >> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe >> Mucchiello >> Sent: March-29-12 9:20 PM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] Constant XHTML >> >> >> >>> 2) Create a new theme file that contains the doc type info that can >>> be loaded before the language files. >> >> >> >> I would think this would be the cleanest solution. I suspect themes >> that don't have the file accept the default site-wide doctype. >> >> >> >> I would also make this a .php file as there might be other $_CONF >> vars the theme needs control of. >> >> >> >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From vfuria at gmail.com Tue Apr 10 10:42:57 2012 From: vfuria at gmail.com (Vincent Furia) Date: Tue, 10 Apr 2012 08:42:57 -0600 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <01a301cd1722$baa058d0$2fe10a70$@cogeco.net> References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> <4F82CC4A.2080208@placella.com> <010201cd1655$6d6502a0$482f07e0$@cogeco.net> <4F82E8F6.9080708@placella.com> <01a301cd1722$baa058d0$2fe10a70$@cogeco.net> Message-ID: On Tue, Apr 10, 2012 at 08:03, Tom wrote: > Does this sound good to you Vinny? (asking since hopefully at some point > the > GSOC Template Engine Upgrade project may happen) > I don't really have a strong opinion. I suspect no matter what we do theme developers will have a little bit of work when we replace the template engine. Wherever possible let's try to keep as much backward compatibility as possible (PHP's *function_exists* function is really helpful for that...). > We might as well use the same file then (functions.php). This way it will > get included and old themes will still work most of the time (with the > default setting of error reporting) even if they do not include the new > functions. > This sounds like a good idea. Let's keep all the themes' php code in one place; a location that already exists is even better. > Could you also do a quick update in the wiki with the new functions then > (since functions.php is only mentioned in the tips section) > http://wiki.geeklog.net/index.php/Theme_Developers_Guide > http://wiki.geeklog.net/index.php/Themes_and_XHTML > I assume this was for Rouslon? -Vinny -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmucchiello at yahoo.com Tue Apr 10 12:52:40 2012 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Tue, 10 Apr 2012 09:52:40 -0700 (PDT) Subject: [geeklog-devel] Constant XHTML Message-ID: <1334076760.11914.YahooMailNeo@web161405.mail.bf1.yahoo.com> What about HTML5? HTML5 and HTML4 are not consistent in their requirements for close tags. I haven't looked too deeply into this but I don't know if setting XHTML to '' works with HTML5. Is the new theme XHTML based or HTML5 based? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rouslan at placella.com Tue Apr 10 13:06:18 2012 From: rouslan at placella.com (Rouslan Placella) Date: Tue, 10 Apr 2012 18:06:18 +0100 Subject: [geeklog-devel] Constant XHTML In-Reply-To: <1334076760.11914.YahooMailNeo@web161405.mail.bf1.yahoo.com> References: <1334076760.11914.YahooMailNeo@web161405.mail.bf1.yahoo.com> Message-ID: <4F84688A.4090903@placella.com> On 10/04/12 17:52, Joe Mucchiello wrote: > Is the new theme XHTML based or HTML5 based? XHTML From tani.os2 at gmail.com Wed Apr 11 04:18:06 2012 From: tani.os2 at gmail.com (Yuji Tsuchida) Date: Wed, 11 Apr 2012 17:18:06 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: Message-ID: Hi all. I consider that the essence of this problem is that the element (ex.right_block) needed for a whole layout is not decided, before making a HEAD element in COM_siteHeader(). If the element needed for a whole layout at the time of execution of COM_siteHeader() is decided, I think that we can switch style.css or etc., if needed. Supposing this problem is solved, I believe that use of a much more dynamic and flexible layout is enabled in Geeklog. It's is not limited to CSS layaut, in case Table layout too. My question is, why not change those functions forever? B) I think it is difficulte to keeping back-compatibility, but it's necessary to get Geeklog's bright future. :) But I don't have good idea, maybe someone have good idea. Tani (Yuji Tsuchida) 2012/4/10, Dan Stoner : > I would definitely like to be able to blog more easily from my (Android) > phone. > > - Dan Stoner > > > 2012/4/9 ???? Geeklog IvyWe : >> Hi, Ben >> >> You are right, I think. >> Non table layout is important. >> >> WordPress and XOOPS cube CMS use non table layout and >> responsive web design as default theme. >> >> Responsive web design is very important because we use iPad, iPhone, >> Android, too. >> And all of them support JavaScript. >> >> HTML does not require table tag for layout. >> Table layout is old fashioned web design. >> >> >> 2012/3/15 cordiste : >>> Can someone explain to me where is the issue with non table layout? >>> Purepro theme [1] can use 1, 2 or 3 columns even with JS disabled. >>> >>> Ben From websitemaster at cogeco.net Wed Apr 11 13:14:49 2012 From: websitemaster at cogeco.net (Tom) Date: Wed, 11 Apr 2012 13:14:49 -0400 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: Message-ID: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> Hey Tani, I think we are all in agreement with you, the head element and the footer (where we place JavaScript) needs to be pretty much the last thing decided before Geeklog displays something. Reworking this properly most likely would require changes that would not make Geeklog backwards compatible with most plugins. The thing is this we plan on releasing Geeklog 2.0 soon and we do not want to push the release back for these changes (it already has been pushed back a number of months now :-) We also hope to update the template engine so there may be other changes required as well for plugins. Once Geeklog 2.0.0 is released I hope to see a discussion happen on what the best way is to solve these problems so we can work these changes into the next version of Geeklog. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yuji Tsuchida Sent: April-11-12 4:18 AM To: Geeklog Development Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) Hi all. I consider that the essence of this problem is that the element (ex.right_block) needed for a whole layout is not decided, before making a HEAD element in COM_siteHeader(). If the element needed for a whole layout at the time of execution of COM_siteHeader() is decided, I think that we can switch style.css or etc., if needed. Supposing this problem is solved, I believe that use of a much more dynamic and flexible layout is enabled in Geeklog. It's is not limited to CSS layaut, in case Table layout too. My question is, why not change those functions forever? B) I think it is difficulte to keeping back-compatibility, but it's necessary to get Geeklog's bright future. :) But I don't have good idea, maybe someone have good idea. Tani (Yuji Tsuchida) 2012/4/10, Dan Stoner : > I would definitely like to be able to blog more easily from my > (Android) phone. > > - Dan Stoner > > > 2012/4/9 ???? Geeklog IvyWe : >> Hi, Ben >> >> You are right, I think. >> Non table layout is important. >> >> WordPress and XOOPS cube CMS use non table layout and responsive web >> design as default theme. >> >> Responsive web design is very important because we use iPad, iPhone, >> Android, too. >> And all of them support JavaScript. >> >> HTML does not require table tag for layout. >> Table layout is old fashioned web design. >> >> >> 2012/3/15 cordiste : >>> Can someone explain to me where is the issue with non table layout? >>> Purepro theme [1] can use 1, 2 or 3 columns even with JS disabled. >>> >>> Ben _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From taharaxp at gmail.com Thu Apr 12 13:30:03 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Fri, 13 Apr 2012 02:30:03 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> Message-ID: Hi, All. I have a solution. And, actually wrote the code. Since I had prepared a Mercurial repository to Google Code, Please clone or pull and evaluate it. geeklog-im home https://code.google.com/p/geeklog-im/ Table layout is so old-school. COM_siteHeader and COM_siteFooter should be abolished at a time. But in the foreseeable future, these functions must leave for backward compatibility. I created the theme 'Denim', making the best use of the flexibility of CSS layout. It has adopted a responsive Web design. If you use a Table layout, it is absolutely not achieved. Go try it out on iPhone, iPad or Android. If you do not have these device, please try to resize the width with the browser on your PC. If you jump up to 2.0.0 version of Geeklog, please indicate the bright prospects. Please do not disappoint us, leaving the Table layout. -- Yoshinori Tahara - dengen 2012?4?12?2:14 Tom : > Hey Tani, > > I think we are all in agreement with you, the head element and the footer > (where we place JavaScript) needs to be pretty much the last thing decided > before Geeklog displays something. Reworking this properly most likely would > require changes that would not make Geeklog backwards compatible with most > plugins. > > The thing is this we plan on releasing Geeklog 2.0 soon and we do not want > to push the release back for these changes (it already has been pushed back > a number of months now :-) > > We also hope to update the template engine so there may be other changes > required as well for plugins. Once Geeklog 2.0.0 is released I hope to see a > discussion happen on what the best way is to solve these problems so we can > work these changes into the next version of Geeklog. > > Tom > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yuji Tsuchida > Sent: April-11-12 4:18 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog > 2.0.0?) > > Hi all. > > I consider that the essence of this problem is that the element > (ex.right_block) needed for a whole layout is not decided, before making a > HEAD element in COM_siteHeader(). > > If the element needed for a whole layout at the time of execution of > COM_siteHeader() is decided, I think that we can switch style.css or etc., > if needed. > > Supposing this problem is solved, I believe that use of a much more dynamic > and flexible layout is enabled in Geeklog. > It's is not limited to CSS layaut, in case Table layout too. > > > My question is, why not change those functions forever? B) > > > I think it is difficulte to keeping back-compatibility, but it's necessary > to get Geeklog's bright future. :) > > But I don't have good idea, maybe someone have good idea. > > > > Tani (Yuji Tsuchida) > > > 2012/4/10, Dan Stoner : >> I would definitely like to be able to blog more easily from my >> (Android) phone. >> >> - Dan Stoner >> >> >> 2012/4/9 ???? Geeklog IvyWe : >>> Hi, Ben >>> >>> You are right, I think. >>> Non table layout is important. >>> >>> WordPress and XOOPS cube CMS use non table layout and responsive web >>> design as default theme. >>> >>> Responsive web design is very important because we use iPad, iPhone, >>> Android, too. >>> And all of them support JavaScript. >>> >>> HTML does not require table tag for layout. >>> Table layout is old fashioned web design. >>> >>> >>> 2012/3/15 cordiste : >>>> Can someone explain to me where is the issue with non table layout? >>>> Purepro theme [1] can use 1, 2 or 3 columns even with JS disabled. >>>> >>>> Ben > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From geeklog at mystral-kk.net Fri Apr 13 08:03:48 2012 From: geeklog at mystral-kk.net (geeklog at mystral-kk.net) Date: Fri, 13 Apr 2012 21:03:48 +0900 (JST) Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> Message-ID: <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> Yoshinori Tahara as dengen wrote: > I have a solution. And, actually wrote the code. > Since I had prepared a Mercurial repository to Google Code, Please > clone or pull and evaluate it. > > geeklog-im home > https://code.google.com/p/geeklog-im/ I have tried and found it good. > Table layout is so old-school. > COM_siteHeader and COM_siteFooter should be abolished at a time. > But in the foreseeable future, these functions must leave for backward > compatibility. > > I created the theme 'Denim', making the best use of the flexibility of > CSS layout. > It has adopted a responsive Web design. > If you use a Table layout, it is absolutely not achieved. > Go try it out on iPhone, iPad or Android. > If you do not have these device, please try to resize the width with > the browser on your PC. > > If you jump up to 2.0.0 version of Geeklog, please indicate the bright > prospects. > Please do not disappoint us, leaving the Table layout. Layout with tables is many years old-fashioned. Only a few users may need table layout, but most users, especially users with mobile devices, would surely prefer a responsive Web design. That said, I don't think it is good to include dengen's work into Geeklog-2.0.0. As other people said, it will break backward compatibility too much. In addition, it is efficient and desirable to introduce a new template engine (e.g. Smarty or Twig?) to make the best of his work. So how about making this a project for this summer: 1. Introducing a new responsive Web design based on dengen's work. 2. Introducing a new template engine. -- mystral-kk geeklog at mystral-kk.net http://mystral-kk.net From websitemaster at cogeco.net Fri Apr 13 09:55:19 2012 From: websitemaster at cogeco.net (Tom) Date: Fri, 13 Apr 2012 09:55:19 -0400 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> Message-ID: <00cf01cd197d$10079070$3016b150$@cogeco.net> If I get a chance I am going to look at his work today. I like the idea of the summer project. It goes along with the GSOC project http://wiki.geeklog.net/index.php/SoC_template_engine and it's feature requests listed at the bottom. We should discuss things first here before any major decisions are made. I am willing to help out once Geeklog 2.0.0 gets out the door and hopefully a few other people are as well. As far as the new theme is concerned we have made the decisions already for the theme currently being worked on by Rouslan. The plan is that this will be the new default theme for Geeklog.net once Geeklog 2.0.0 is officially released. However, I personally do not have a problem including in a future version of Geeklog an additional theme that is more mobile device friendly especially if it takes advantage of the "new template engine". Geeklog 2.0.0 will include Rouslans new theme (lets decide a name for this BTW) along with the professional theme. Once the "new template engine" is finished, for that version I could see dropping the professional theme and including a new responsive Web design theme. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of geeklog at mystral-kk.net Sent: April-13-12 8:04 AM To: Geeklog Development Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) Yoshinori Tahara as dengen wrote: > I have a solution. And, actually wrote the code. > Since I had prepared a Mercurial repository to Google Code, Please > clone or pull and evaluate it. > > geeklog-im home > https://code.google.com/p/geeklog-im/ I have tried and found it good. > Table layout is so old-school. > COM_siteHeader and COM_siteFooter should be abolished at a time. > But in the foreseeable future, these functions must leave for backward > compatibility. > > I created the theme 'Denim', making the best use of the flexibility of > CSS layout. > It has adopted a responsive Web design. > If you use a Table layout, it is absolutely not achieved. > Go try it out on iPhone, iPad or Android. > If you do not have these device, please try to resize the width with > the browser on your PC. > > If you jump up to 2.0.0 version of Geeklog, please indicate the bright > prospects. > Please do not disappoint us, leaving the Table layout. Layout with tables is many years old-fashioned. Only a few users may need table layout, but most users, especially users with mobile devices, would surely prefer a responsive Web design. That said, I don't think it is good to include dengen's work into Geeklog-2.0.0. As other people said, it will break backward compatibility too much. In addition, it is efficient and desirable to introduce a new template engine (e.g. Smarty or Twig?) to make the best of his work. So how about making this a project for this summer: 1. Introducing a new responsive Web design based on dengen's work. 2. Introducing a new template engine. -- mystral-kk geeklog at mystral-kk.net http://mystral-kk.net _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Fri Apr 13 10:00:31 2012 From: websitemaster at cogeco.net (Tom) Date: Fri, 13 Apr 2012 10:00:31 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Beta 1 Message-ID: <00d001cd197d$ca3b9040$5eb2b0c0$@cogeco.net> So is there anything left (code wise) that we need to work on for this release? Once Rouslan updates the themes and the code for the functions.php changes to fix the doc type and language issues I think we would be ready for a release. Tom From dirk at haun-online.de Fri Apr 13 11:18:23 2012 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 13 Apr 2012 17:18:23 +0200 Subject: [geeklog-devel] Geeklog 2.0.0 Beta 1 In-Reply-To: <00d001cd197d$ca3b9040$5eb2b0c0$@cogeco.net> References: <00d001cd197d$ca3b9040$5eb2b0c0$@cogeco.net> Message-ID: <4ABB31A7-F48C-4CCA-88B7-17CEEDDAE0E0@haun-online.de> Tom wrote: > So is there anything left (code wise) that we need to work on for this > release? The roadmap has a few open issues left: http://project.geeklog.net/tracking/roadmap_page.php Anything that's a Feature Request or Patch can be moved to 2.0.1, I guess. What about the 3 remaining bugs? http://project.geeklog.net/tracking/view.php?id=1308 http://project.geeklog.net/tracking/view.php?id=1316 http://project.geeklog.net/tracking/view.php?id=1399 None of those seem critical (or new). Move to 2.0.1 as well? > Once Rouslan updates the themes and the code for the functions.php changes > to fix the doc type and language issues I think we would be ready for a > release. That's the bit with the XHTML constant that shows up verbatim in the HTML currently? bye, Dirk -- http://www.themobilepresenter.com/ From komma at ivywe.co.jp Fri Apr 13 17:45:39 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Sat, 14 Apr 2012 06:45:39 +0900 Subject: [geeklog-devel] Geeklog 2.0.0 Beta 1 In-Reply-To: <4ABB31A7-F48C-4CCA-88B7-17CEEDDAE0E0@haun-online.de> References: <00d001cd197d$ca3b9040$5eb2b0c0$@cogeco.net> <4ABB31A7-F48C-4CCA-88B7-17CEEDDAE0E0@haun-online.de> Message-ID: Hi, all Please remove table tag in source and templates. And test dengen's responsive web design theme for default theme. Geeklog 2.0 is the last chance for Geeklog theme's reform. Otherwise Geeklog Japanese have to fork, but I don't want to fork In fact. -- Ivy 2012/4/14 Dirk Haun : > Tom wrote: > >> So is there anything left (code wise) that we need to work on for this >> release? > > The roadmap has a few open issues left: > > http://project.geeklog.net/tracking/roadmap_page.php > > Anything that's a Feature Request or Patch can be moved to 2.0.1, I guess. What about the 3 remaining bugs? > > http://project.geeklog.net/tracking/view.php?id=1308 > http://project.geeklog.net/tracking/view.php?id=1316 > http://project.geeklog.net/tracking/view.php?id=1399 > > None of those seem critical (or new). Move to 2.0.1 as well? > > >> Once Rouslan updates the themes and the code for the functions.php changes >> to fix the doc type and language issues I think we would be ready for a >> release. > > > That's the bit with the XHTML constant that shows up verbatim in the HTML currently? > > bye, Dirk From taharaxp at gmail.com Sat Apr 14 03:05:08 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Sat, 14 Apr 2012 16:05:08 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <00cf01cd197d$10079070$3016b150$@cogeco.net> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> Message-ID: > If I get a chance I am going to look at his work today. Thanks. Please note that there is backward compatibility. I do not expect to be the standard theme Denim. I wanted to emphasize the benefits of CSS layout only. If possible, it is desirable to introduce a new template engine. There is a future. Table layout? Has nothing, not even a future. The version 2.0.0 has a special meaning. Since the vertion 1.9.0 was skipped. It is necessary to promote the vision of the future along with the version 2.0.0! -- Yoshinori Tahara - dengen 2012?4?13?22:55 Tom : > If I get a chance I am going to look at his work today. > > I like the idea of the summer project. It goes along with the GSOC project > http://wiki.geeklog.net/index.php/SoC_template_engine and it's feature > requests listed at the bottom. > > We should discuss things first here before any major decisions are made. I > am willing to help out once Geeklog 2.0.0 gets out the door and hopefully a > few other people are as well. > > As far as the new theme is concerned we have made the decisions already for > the theme currently being worked on by Rouslan. The plan is that this will > be the new default theme for Geeklog.net once Geeklog 2.0.0 is officially > released. > > However, I personally do not have a problem including in a future version of > Geeklog an additional theme that is more mobile device friendly especially > if it takes advantage of the "new template engine". Geeklog 2.0.0 will > include Rouslans new theme (lets decide a name for this BTW) along with the > professional theme. Once the "new template engine" is finished, for that > version I could see dropping the professional theme and including a new > responsive Web design theme. > > Tom > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of > geeklog at mystral-kk.net > Sent: April-13-12 8:04 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog > 2.0.0?) > > Yoshinori Tahara as dengen wrote: > >> I have a solution. And, actually wrote the code. >> Since I had prepared a Mercurial repository to Google Code, Please >> clone or pull and evaluate it. >> >> geeklog-im home >> https://code.google.com/p/geeklog-im/ > > I have tried and found it good. > >> Table layout is so old-school. >> COM_siteHeader and COM_siteFooter should be abolished at a time. >> But in the foreseeable future, these functions must leave for backward >> compatibility. >> >> I created the theme 'Denim', making the best use of the flexibility of >> CSS layout. >> It has adopted a responsive Web design. >> If you use a Table layout, it is absolutely not achieved. >> Go try it out on iPhone, iPad or Android. >> If you do not have these device, please try to resize the width with >> the browser on your PC. >> >> If you jump up to 2.0.0 version of Geeklog, please indicate the bright >> prospects. >> Please do not disappoint us, leaving the Table layout. > > Layout with tables is many years old-fashioned. Only a few users may need > table layout, but most users, especially users with mobile devices, would > surely prefer a responsive Web design. > > That said, I don't think it is good to include dengen's work into > Geeklog-2.0.0. As other people said, it will break backward compatibility > too much. In addition, it is efficient and desirable to introduce a new > template engine (e.g. Smarty or Twig?) to make the best of his work. > > So how about making this a project for this summer: > 1. Introducing a new responsive Web design based on dengen's work. > 2. Introducing a new template engine. > -- > mystral-kk > geeklog at mystral-kk.net > http://mystral-kk.net > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From tani.os2 at gmail.com Sat Apr 14 09:24:33 2012 From: tani.os2 at gmail.com (Yuji Tsuchida) Date: Sat, 14 Apr 2012 22:24:33 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> Message-ID: Thanks for agreement me. And I am in agreement you do not want to push the release back. I personally think this discussion will be not finish before release 2.0.0, and solution is not obtained now. 2012/04/12 2:14 Tom : > We also hope to update the template engine so there may be other changes > required as well for plugins. Once Geeklog 2.0.0 is released I hope to see a > discussion happen on what the best way is to solve these problems so we can > work these changes into the next version of Geeklog. My proposal is determining the API(s) and argument of those first. denden proposed API COM_createHTML(), but if arguments are changed when changing new template engine, we need big change twice. but API(s) and arguments is fixed, we no need twice. My idea is... ex. COM_createHTML($display,$elements_array,$engine_name,$engine_optArray) $display : main content $element_array : array('menu','left_block'.......) $engine_name : template engine name ex. 'v1engine' , 'v2engine' or 'new_engine'.... $engine_optArray : additional options to template engine. and maybe more configuration parameter is needed. Let's discuss. From rouslan at placella.com Sun Apr 15 09:41:22 2012 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 15 Apr 2012 14:41:22 +0100 Subject: [geeklog-devel] Constant XHTML In-Reply-To: References: <1333070392.68140.YahooMailNeo@web161401.mail.bf1.yahoo.com> <05ee01cd1334$021e26d0$065a7470$@cogeco.net> <4F82CC4A.2080208@placella.com> <010201cd1655$6d6502a0$482f07e0$@cogeco.net> <4F82E8F6.9080708@placella.com> <01a301cd1722$baa058d0$2fe10a70$@cogeco.net> Message-ID: <4F8AD002.2090704@placella.com> Implemented in http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/f0455add3e06 Bye, Rouslan On 10/04/12 15:42, Vincent Furia wrote: > On Tue, Apr 10, 2012 at 08:03, Tom wrote: > >> Does this sound good to you Vinny? (asking since hopefully at some point >> the >> GSOC Template Engine Upgrade project may happen) >> > I don't really have a strong opinion. I suspect no matter what we do theme > developers will have a little bit of work when we replace the template > engine. Wherever possible let's try to keep as much backward compatibility > as possible (PHP's *function_exists* function is really helpful for > that...). > > >> We might as well use the same file then (functions.php). This way it will >> get included and old themes will still work most of the time (with the >> default setting of error reporting) even if they do not include the new >> functions. >> > This sounds like a good idea. Let's keep all the themes' php code in one > place; a location that already exists is even better. > > >> Could you also do a quick update in the wiki with the new functions then >> (since functions.php is only mentioned in the tips section) > > >> http://wiki.geeklog.net/index.php/Theme_Developers_Guide >> http://wiki.geeklog.net/index.php/Themes_and_XHTML >> > I assume this was for Rouslon? > > -Vinny > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sun Apr 15 10:34:16 2012 From: websitemaster at cogeco.net (Tom) Date: Sun, 15 Apr 2012 10:34:16 -0400 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> Message-ID: <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> Hey Dengen, I just wanted to let you know we are looking into your work now. We didn't know you were working on these changes so you caught us by surprise. We will not release Geeklog 2.0 until things get sorted out. I see that your work is indeed backwards compatible not only with themes but plugins that do not yet support COM_createHTMLDocument I also see that you have updated Geeklog and all the core plugins to work with COM_createHTMLDocument I see that you have adding a variable called $_GLOBAL_WHAT used for backwards compatibility to keep track of COM_siteHeader $what function variable. You have also added a variable called $_CONF['support_theme_2.0'] that can be set in a theme's function.php file. If set the theme will use COM_createHTMLDocument. If not COM_createHTMLDocument will call COM_siteHeader and COM_siteFooter for backwards compatibility instead. I see that there also is a new template variable for the header called layout_columns that enables the theme to know how many columns there are. Is there any other major changes that I am missing here when I took a look at your code and new theme? Thanks Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yoshinori Tahara Sent: April-14-12 3:05 AM To: Geeklog Development Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) > If I get a chance I am going to look at his work today. Thanks. Please note that there is backward compatibility. I do not expect to be the standard theme Denim. I wanted to emphasize the benefits of CSS layout only. If possible, it is desirable to introduce a new template engine. There is a future. Table layout? Has nothing, not even a future. The version 2.0.0 has a special meaning. Since the vertion 1.9.0 was skipped. It is necessary to promote the vision of the future along with the version 2.0.0! -- Yoshinori Tahara - dengen 2012?4?13?22:55 Tom : > If I get a chance I am going to look at his work today. > > I like the idea of the summer project. It goes along with the GSOC > project http://wiki.geeklog.net/index.php/SoC_template_engine and it's > feature requests listed at the bottom. > > We should discuss things first here before any major decisions are > made. I am willing to help out once Geeklog 2.0.0 gets out the door > and hopefully a few other people are as well. > > As far as the new theme is concerned we have made the decisions > already for the theme currently being worked on by Rouslan. The plan > is that this will be the new default theme for Geeklog.net once > Geeklog 2.0.0 is officially released. > > However, I personally do not have a problem including in a future > version of Geeklog an additional theme that is more mobile device > friendly especially if it takes advantage of the "new template > engine". Geeklog 2.0.0 will include Rouslans new theme (lets decide a > name for this BTW) along with the professional theme. Once the "new > template engine" is finished, for that version I could see dropping > the professional theme and including a new responsive Web design theme. > > Tom > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of > geeklog at mystral-kk.net > Sent: April-13-12 8:04 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or > Geeklog > 2.0.0?) > > Yoshinori Tahara as dengen wrote: > >> I have a solution. And, actually wrote the code. >> Since I had prepared a Mercurial repository to Google Code, Please >> clone or pull and evaluate it. >> >> geeklog-im home >> https://code.google.com/p/geeklog-im/ > > I have tried and found it good. > >> Table layout is so old-school. >> COM_siteHeader and COM_siteFooter should be abolished at a time. >> But in the foreseeable future, these functions must leave for >> backward compatibility. >> >> I created the theme 'Denim', making the best use of the flexibility >> of CSS layout. >> It has adopted a responsive Web design. >> If you use a Table layout, it is absolutely not achieved. >> Go try it out on iPhone, iPad or Android. >> If you do not have these device, please try to resize the width with >> the browser on your PC. >> >> If you jump up to 2.0.0 version of Geeklog, please indicate the >> bright prospects. >> Please do not disappoint us, leaving the Table layout. > > Layout with tables is many years old-fashioned. Only a few users may > need table layout, but most users, especially users with mobile > devices, would surely prefer a responsive Web design. > > That said, I don't think it is good to include dengen's work into > Geeklog-2.0.0. As other people said, it will break backward > compatibility too much. In addition, it is efficient and desirable to > introduce a new template engine (e.g. Smarty or Twig?) to make the best of his work. > > So how about making this a project for this summer: > 1. Introducing a new responsive Web design based on dengen's work. > 2. Introducing a new template engine. > -- > mystral-kk > geeklog at mystral-kk.net > http://mystral-kk.net > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Sun Apr 15 10:36:39 2012 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 15 Apr 2012 15:36:39 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> Message-ID: <4F8ADCF7.5060909@placella.com> I thought I'd mention that I've reverted the new default theme back to the CSS layout found in professional_css theme ;) Bye, Rouslan On 15/04/12 15:34, Tom wrote: > Hey Dengen, > > I just wanted to let you know we are looking into your work now. > > We didn't know you were working on these changes so you caught us by > surprise. > > We will not release Geeklog 2.0 until things get sorted out. > > I see that your work is indeed backwards compatible not only with themes but > plugins that do not yet support COM_createHTMLDocument > > I also see that you have updated Geeklog and all the core plugins to work > with COM_createHTMLDocument > > I see that you have adding a variable called $_GLOBAL_WHAT used for > backwards compatibility to keep track of COM_siteHeader $what function > variable. > > You have also added a variable called $_CONF['support_theme_2.0'] that can > be set in a theme's function.php file. If set the theme will use > COM_createHTMLDocument. If not COM_createHTMLDocument will call > COM_siteHeader and COM_siteFooter for backwards compatibility instead. > > I see that there also is a new template variable for the header called > layout_columns that enables the theme to know how many columns there are. > > Is there any other major changes that I am missing here when I took a look > at your code and new theme? > > Thanks > > Tom > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yoshinori > Tahara > Sent: April-14-12 3:05 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog > 2.0.0?) > >> If I get a chance I am going to look at his work today. > > Thanks. > Please note that there is backward compatibility. > > I do not expect to be the standard theme Denim. > I wanted to emphasize the benefits of CSS layout only. > > If possible, it is desirable to introduce a new template engine. There is a > future. > Table layout? Has nothing, not even a future. > The version 2.0.0 has a special meaning. Since the vertion 1.9.0 was > skipped. > It is necessary to promote the vision of the future along with the version > 2.0.0! > > -- > Yoshinori Tahara - dengen > > 2012?4?13?22:55 Tom : >> If I get a chance I am going to look at his work today. >> >> I like the idea of the summer project. It goes along with the GSOC >> project http://wiki.geeklog.net/index.php/SoC_template_engine and it's >> feature requests listed at the bottom. >> >> We should discuss things first here before any major decisions are >> made. I am willing to help out once Geeklog 2.0.0 gets out the door >> and hopefully a few other people are as well. >> >> As far as the new theme is concerned we have made the decisions >> already for the theme currently being worked on by Rouslan. The plan >> is that this will be the new default theme for Geeklog.net once >> Geeklog 2.0.0 is officially released. >> >> However, I personally do not have a problem including in a future >> version of Geeklog an additional theme that is more mobile device >> friendly especially if it takes advantage of the "new template >> engine". Geeklog 2.0.0 will include Rouslans new theme (lets decide a >> name for this BTW) along with the professional theme. Once the "new >> template engine" is finished, for that version I could see dropping >> the professional theme and including a new responsive Web design theme. >> >> Tom >> >> >> >> -----Original Message----- >> From: geeklog-devel-bounces at lists.geeklog.net >> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of >> geeklog at mystral-kk.net >> Sent: April-13-12 8:04 AM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or >> Geeklog >> 2.0.0?) >> >> Yoshinori Tahara as dengen wrote: >> >>> I have a solution. And, actually wrote the code. >>> Since I had prepared a Mercurial repository to Google Code, Please >>> clone or pull and evaluate it. >>> >>> geeklog-im home >>> https://code.google.com/p/geeklog-im/ >> >> I have tried and found it good. >> >>> Table layout is so old-school. >>> COM_siteHeader and COM_siteFooter should be abolished at a time. >>> But in the foreseeable future, these functions must leave for >>> backward compatibility. >>> >>> I created the theme 'Denim', making the best use of the flexibility >>> of CSS layout. >>> It has adopted a responsive Web design. >>> If you use a Table layout, it is absolutely not achieved. >>> Go try it out on iPhone, iPad or Android. >>> If you do not have these device, please try to resize the width with >>> the browser on your PC. >>> >>> If you jump up to 2.0.0 version of Geeklog, please indicate the >>> bright prospects. >>> Please do not disappoint us, leaving the Table layout. >> >> Layout with tables is many years old-fashioned. Only a few users may >> need table layout, but most users, especially users with mobile >> devices, would surely prefer a responsive Web design. >> >> That said, I don't think it is good to include dengen's work into >> Geeklog-2.0.0. As other people said, it will break backward >> compatibility too much. In addition, it is efficient and desirable to >> introduce a new template engine (e.g. Smarty or Twig?) to make the best of > his work. >> >> So how about making this a project for this summer: >> 1. Introducing a new responsive Web design based on dengen's work. >> 2. Introducing a new template engine. >> -- >> mystral-kk >> geeklog at mystral-kk.net >> http://mystral-kk.net >> >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From taharaxp at gmail.com Sun Apr 15 15:11:57 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Mon, 16 Apr 2012 04:11:57 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8ADCF7.5060909@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> Message-ID: Hi, Tom Thanks for your looking into my work. I want to add a little explanation. I have dropped the table layout from the configuration. Changes to config.class.php is relatively large. I have dropped the table layout from the templates of the default plugins. I have modified style.css of the Professional theme in order to adapt to the classes for the CSS layout. I have modified the fckeditor for Responsive Web design. The Denim theme has been created based on the professional_css theme. I have improved some of the professional_css theme. To reduce the number of HTTP requests, merged into single style sheet. I've optimized the CSS. Take a look at the next page. Writing efficient CSS https://developer.mozilla.org/en/Writing_Efficient_CSS -- Yoshinori Tahara - dengen 2012?4?15?23:36 Rouslan Placella : > I thought I'd mention that I've reverted the new default theme back to > the CSS layout found in professional_css theme ;) > > Bye, > Rouslan > > On 15/04/12 15:34, Tom wrote: >> Hey Dengen, >> >> I just wanted to let you know we are looking into your work now. >> >> We didn't know you were working on these changes so you caught us by >> surprise. >> >> We will not release Geeklog 2.0 until things get sorted out. >> >> I see that your work is indeed backwards compatible not only with themes but >> plugins that do not yet support COM_createHTMLDocument >> >> I also see that you have updated Geeklog and all the core plugins to work >> with COM_createHTMLDocument >> >> I see that you have adding a variable called $_GLOBAL_WHAT used for >> backwards compatibility to keep track of COM_siteHeader $what function >> variable. >> >> You have also added a variable called $_CONF['support_theme_2.0'] that can >> be set in a theme's function.php file. If set the theme will use >> COM_createHTMLDocument. If not COM_createHTMLDocument will call >> COM_siteHeader and COM_siteFooter for backwards compatibility instead. >> >> I see that there also is a new template variable for the header called >> layout_columns that enables the theme to know how many columns there are. >> >> Is there any other major changes that I am missing here when I took a look >> at your code and new theme? >> >> Thanks >> >> Tom >> >> >> -----Original Message----- >> From: geeklog-devel-bounces at lists.geeklog.net >> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yoshinori >> Tahara >> Sent: April-14-12 3:05 AM >> To: Geeklog Development >> Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog >> 2.0.0?) >> >>> If I get a chance I am going to look at his work today. >> >> Thanks. >> Please note that there is backward compatibility. >> >> I do not expect to be the standard theme Denim. >> I wanted to emphasize the benefits of CSS layout only. >> >> If possible, it is desirable to introduce a new template engine. There is a >> future. >> Table layout? Has nothing, not even a future. >> The version 2.0.0 has a special meaning. Since the vertion 1.9.0 was >> skipped. >> It is necessary to promote the vision of the future along with the version >> 2.0.0! >> >> -- >> Yoshinori Tahara - dengen >> >> 2012?4?13?22:55 Tom : >>> If I get a chance I am going to look at his work today. >>> >>> I like the idea of the summer project. It goes along with the GSOC >>> project http://wiki.geeklog.net/index.php/SoC_template_engine and it's >>> feature requests listed at the bottom. >>> >>> We should discuss things first here before any major decisions are >>> made. I am willing to help out once Geeklog 2.0.0 gets out the door >>> and hopefully a few other people are as well. >>> >>> As far as the new theme is concerned we have made the decisions >>> already for the theme currently being worked on by Rouslan. The plan >>> is that this will be the new default theme for Geeklog.net once >>> Geeklog 2.0.0 is officially released. >>> >>> However, I personally do not have a problem including in a future >>> version of Geeklog an additional theme that is more mobile device >>> friendly especially if it takes advantage of the "new template >>> engine". Geeklog 2.0.0 will include Rouslans new theme (lets decide a >>> name for this BTW) along with the professional theme. Once the "new >>> template engine" is finished, for that version I could see dropping >>> the professional theme and including a new responsive Web design theme. >>> >>> Tom >>> >>> >>> >>> -----Original Message----- >>> From: geeklog-devel-bounces at lists.geeklog.net >>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of >>> geeklog at mystral-kk.net >>> Sent: April-13-12 8:04 AM >>> To: Geeklog Development >>> Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or >>> Geeklog >>> 2.0.0?) >>> >>> Yoshinori Tahara as dengen wrote: >>> >>>> I have a solution. And, actually wrote the code. >>>> Since I had prepared a Mercurial repository to Google Code, Please >>>> clone or pull and evaluate it. >>>> >>>> geeklog-im home >>>> https://code.google.com/p/geeklog-im/ >>> >>> I have tried and found it good. >>> >>>> Table layout is so old-school. >>>> COM_siteHeader and COM_siteFooter should be abolished at a time. >>>> But in the foreseeable future, these functions must leave for >>>> backward compatibility. >>>> >>>> I created the theme 'Denim', making the best use of the flexibility >>>> of CSS layout. >>>> It has adopted a responsive Web design. >>>> If you use a Table layout, it is absolutely not achieved. >>>> Go try it out on iPhone, iPad or Android. >>>> If you do not have these device, please try to resize the width with >>>> the browser on your PC. >>>> >>>> If you jump up to 2.0.0 version of Geeklog, please indicate the >>>> bright prospects. >>>> Please do not disappoint us, leaving the Table layout. >>> >>> Layout with tables is many years old-fashioned. Only a few users may >>> need table layout, but most users, especially users with mobile >>> devices, would surely prefer a responsive Web design. >>> >>> That said, I don't think it is good to include dengen's work into >>> Geeklog-2.0.0. As other people said, it will break backward >>> compatibility too much. In addition, it is efficient and desirable to >>> introduce a new template engine (e.g. Smarty or Twig?) to make the best of >> his work. >>> >>> So how about making this a project for this summer: >>> 1. Introducing a new responsive Web design based on dengen's work. >>> 2. Introducing a new template engine. >>> -- >>> mystral-kk >>> geeklog at mystral-kk.net >>> http://mystral-kk.net >>> >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From taharaxp at gmail.com Sun Apr 15 15:13:17 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Mon, 16 Apr 2012 04:13:17 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> Message-ID: Hi, Rouslan Thanks for your approval and work. -- Yoshinori Tahara - dengen 2012?4?16?4:11 Yoshinori Tahara : > Hi, Tom > > Thanks for your looking into my work. > I want to add a little explanation. > > I have dropped the table layout from the configuration. Changes to > config.class.php is relatively large. > I have dropped the table layout from the templates of the default plugins. > I have modified style.css of the Professional theme in order to adapt > to the classes for the CSS layout. > I have modified the fckeditor for Responsive Web design. > > The Denim theme has been created based on the professional_css theme. > I have improved some of the professional_css theme. > To reduce the number of HTTP requests, merged into single style sheet. > I've optimized the CSS. Take a look at the next page. > > Writing efficient CSS > https://developer.mozilla.org/en/Writing_Efficient_CSS > > -- > Yoshinori Tahara - dengen > > 2012?4?15?23:36 Rouslan Placella : >> I thought I'd mention that I've reverted the new default theme back to >> the CSS layout found in professional_css theme ;) >> >> Bye, >> Rouslan >> >> On 15/04/12 15:34, Tom wrote: >>> Hey Dengen, >>> >>> I just wanted to let you know we are looking into your work now. >>> >>> We didn't know you were working on these changes so you caught us by >>> surprise. >>> >>> We will not release Geeklog 2.0 until things get sorted out. >>> >>> I see that your work is indeed backwards compatible not only with themes but >>> plugins that do not yet support COM_createHTMLDocument >>> >>> I also see that you have updated Geeklog and all the core plugins to work >>> with COM_createHTMLDocument >>> >>> I see that you have adding a variable called $_GLOBAL_WHAT used for >>> backwards compatibility to keep track of COM_siteHeader $what function >>> variable. >>> >>> You have also added a variable called $_CONF['support_theme_2.0'] that can >>> be set in a theme's function.php file. If set the theme will use >>> COM_createHTMLDocument. If not COM_createHTMLDocument will call >>> COM_siteHeader and COM_siteFooter for backwards compatibility instead. >>> >>> I see that there also is a new template variable for the header called >>> layout_columns that enables the theme to know how many columns there are. >>> >>> Is there any other major changes that I am missing here when I took a look >>> at your code and new theme? >>> >>> Thanks >>> >>> Tom >>> >>> >>> -----Original Message----- >>> From: geeklog-devel-bounces at lists.geeklog.net >>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yoshinori >>> Tahara >>> Sent: April-14-12 3:05 AM >>> To: Geeklog Development >>> Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog >>> 2.0.0?) >>> >>>> If I get a chance I am going to look at his work today. >>> >>> Thanks. >>> Please note that there is backward compatibility. >>> >>> I do not expect to be the standard theme Denim. >>> I wanted to emphasize the benefits of CSS layout only. >>> >>> If possible, it is desirable to introduce a new template engine. There is a >>> future. >>> Table layout? Has nothing, not even a future. >>> The version 2.0.0 has a special meaning. Since the vertion 1.9.0 was >>> skipped. >>> It is necessary to promote the vision of the future along with the version >>> 2.0.0! >>> >>> -- >>> Yoshinori Tahara - dengen >>> >>> 2012?4?13?22:55 Tom : >>>> If I get a chance I am going to look at his work today. >>>> >>>> I like the idea of the summer project. It goes along with the GSOC >>>> project http://wiki.geeklog.net/index.php/SoC_template_engine and it's >>>> feature requests listed at the bottom. >>>> >>>> We should discuss things first here before any major decisions are >>>> made. I am willing to help out once Geeklog 2.0.0 gets out the door >>>> and hopefully a few other people are as well. >>>> >>>> As far as the new theme is concerned we have made the decisions >>>> already for the theme currently being worked on by Rouslan. The plan >>>> is that this will be the new default theme for Geeklog.net once >>>> Geeklog 2.0.0 is officially released. >>>> >>>> However, I personally do not have a problem including in a future >>>> version of Geeklog an additional theme that is more mobile device >>>> friendly especially if it takes advantage of the "new template >>>> engine". Geeklog 2.0.0 will include Rouslans new theme (lets decide a >>>> name for this BTW) along with the professional theme. Once the "new >>>> template engine" is finished, for that version I could see dropping >>>> the professional theme and including a new responsive Web design theme. >>>> >>>> Tom >>>> >>>> >>>> >>>> -----Original Message----- >>>> From: geeklog-devel-bounces at lists.geeklog.net >>>> [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of >>>> geeklog at mystral-kk.net >>>> Sent: April-13-12 8:04 AM >>>> To: Geeklog Development >>>> Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or >>>> Geeklog >>>> 2.0.0?) >>>> >>>> Yoshinori Tahara as dengen wrote: >>>> >>>>> I have a solution. And, actually wrote the code. >>>>> Since I had prepared a Mercurial repository to Google Code, Please >>>>> clone or pull and evaluate it. >>>>> >>>>> geeklog-im home >>>>> https://code.google.com/p/geeklog-im/ >>>> >>>> I have tried and found it good. >>>> >>>>> Table layout is so old-school. >>>>> COM_siteHeader and COM_siteFooter should be abolished at a time. >>>>> But in the foreseeable future, these functions must leave for >>>>> backward compatibility. >>>>> >>>>> I created the theme 'Denim', making the best use of the flexibility >>>>> of CSS layout. >>>>> It has adopted a responsive Web design. >>>>> If you use a Table layout, it is absolutely not achieved. >>>>> Go try it out on iPhone, iPad or Android. >>>>> If you do not have these device, please try to resize the width with >>>>> the browser on your PC. >>>>> >>>>> If you jump up to 2.0.0 version of Geeklog, please indicate the >>>>> bright prospects. >>>>> Please do not disappoint us, leaving the Table layout. >>>> >>>> Layout with tables is many years old-fashioned. Only a few users may >>>> need table layout, but most users, especially users with mobile >>>> devices, would surely prefer a responsive Web design. >>>> >>>> That said, I don't think it is good to include dengen's work into >>>> Geeklog-2.0.0. As other people said, it will break backward >>>> compatibility too much. In addition, it is efficient and desirable to >>>> introduce a new template engine (e.g. Smarty or Twig?) to make the best of >>> his work. >>>> >>>> So how about making this a project for this summer: >>>> 1. Introducing a new responsive Web design based on dengen's work. >>>> 2. Introducing a new template engine. >>>> -- >>>> mystral-kk >>>> geeklog at mystral-kk.net >>>> http://mystral-kk.net >>>> >>>> >>>> _______________________________________________ >>>> geeklog-devel mailing list >>>> geeklog-devel at lists.geeklog.net >>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >>>> >>>> _______________________________________________ >>>> geeklog-devel mailing list >>>> geeklog-devel at lists.geeklog.net >>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >>> >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Sun Apr 15 15:27:12 2012 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 15 Apr 2012 20:27:12 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> Message-ID: <4F8B2110.9000807@placella.com> On 15/04/12 20:11, Yoshinori Tahara wrote: > Hi, Tom > > Thanks for your looking into my work. > I want to add a little explanation. > > I have dropped the table layout from the configuration. Changes to > config.class.php is relatively large. > I have dropped the table layout from the templates of the default plugins. > I have modified style.css of the Professional theme in order to adapt > to the classes for the CSS layout. > I have modified the fckeditor for Responsive Web design. > > The Denim theme has been created based on the professional_css theme. > I have improved some of the professional_css theme. > To reduce the number of HTTP requests, merged into single style sheet. This is done in newpro theme as well, although in a different way [0]. The stylesheets are still kept in separate files (easier to work with for developers), but they are assembled on the server side and then cached on the client side. This also allows a really easy way to implement RTL display by using placeholders. See the implementation for RTL here [1] and sample usage here [2]. Bye, Rouslan [0]: http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/f4c599db456f [1]: http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/26812a66e857 [2]: http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/810c7e4b9dec > I've optimized the CSS. Take a look at the next page. > > Writing efficient CSS > https://developer.mozilla.org/en/Writing_Efficient_CSS > From taharaxp at gmail.com Mon Apr 16 08:27:08 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Mon, 16 Apr 2012 21:27:08 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8B2110.9000807@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> Message-ID: > Rouslan wrote: > This is done in newpro theme as well, although in a different way [0]. > The stylesheets are still kept in separate files (easier to work with > for developers), but they are assembled on the server side and then > cached on the client side. This also allows a really easy way to > implement RTL display by using placeholders. See the implementation for > RTL here [1] and sample usage here [2]. For this matter, I have a different opinion with you. Your solution is not common. I think that you cope with complicated techniques to complex situations. Indeed, separate the stylesheets properly, readability is increasing. However, the number of stylesheets of professional_css is too many. If you bring them all into one, the problem is easier. For display of RTL, there is an easier way. If you select a stylesheet depending on the value of a variable $ LANG_DIRECTION in a theme's function.php, the matter is resolved. $cssfile = ($LANG_DIRECTION == 'rtl') ? '/style_rtl.css' : '/style.css'; $_SCRIPTS->setCSSFile('theme', '/layout/' . $_CONF['theme'] . $cssfile); -- Yoshinori Tahara - dengen 2012?4?16?4:27 Rouslan Placella : > On 15/04/12 20:11, Yoshinori Tahara wrote: >> Hi, Tom >> >> Thanks for your looking into my work. >> I want to add a little explanation. >> >> I have dropped the table layout from the configuration. Changes to >> config.class.php is relatively large. >> I have dropped the table layout from the templates of the default plugins. >> I have modified style.css of the Professional theme in order to adapt >> to the classes for the CSS layout. >> I have modified the fckeditor for Responsive Web design. >> >> The Denim theme has been created based on the professional_css theme. >> I have improved some of the professional_css theme. >> To reduce the number of HTTP requests, merged into single style sheet. > > This is done in newpro theme as well, although in a different way [0]. > The stylesheets are still kept in separate files (easier to work with > for developers), but they are assembled on the server side and then > cached on the client side. This also allows a really easy way to > implement RTL display by using placeholders. See the implementation for > RTL here [1] and sample usage here [2]. > > Bye, > Rouslan > > [0]: > http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/f4c599db456f > [1]: > http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/26812a66e857 > [2]: > http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/rev/810c7e4b9dec > >> I've optimized the CSS. Take a look at the next page. >> >> Writing efficient CSS >> https://developer.mozilla.org/en/Writing_Efficient_CSS >> > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Mon Apr 16 13:43:19 2012 From: rouslan at placella.com (Rouslan Placella) Date: Mon, 16 Apr 2012 18:43:19 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> Message-ID: <4F8C5A37.4030104@placella.com> On 16/04/12 13:27, Yoshinori Tahara wrote: >> Rouslan wrote: >> This is done in newpro theme as well, although in a different way [0]. >> The stylesheets are still kept in separate files (easier to work with >> for developers), but they are assembled on the server side and then >> cached on the client side. This also allows a really easy way to >> implement RTL display by using placeholders. See the implementation for >> RTL here [1] and sample usage here [2]. > > For this matter, I have a different opinion with you. > Your solution is not common. > I think that you cope with complicated techniques to complex situations. > > Indeed, separate the stylesheets properly, readability is increasing. > However, the number of stylesheets of professional_css is too many. > If you bring them all into one, the problem is easier. I'm not sure what you are trying to say here, but I find dealing with one really big stylesheet quite painful :) > For display of RTL, there is an easier way. > If you select a stylesheet depending on the value of a variable $ > LANG_DIRECTION in a theme's function.php, the matter is resolved. > > $cssfile = ($LANG_DIRECTION == 'rtl') ? '/style_rtl.css' : '/style.css'; > $_SCRIPTS->setCSSFile('theme', '/layout/' . $_CONF['theme'] . $cssfile); But then you need to maintain two copies of almost the same stylesheet. At some point in time they may, and probably will, diverge. So it's extra work for developers and maintainers. Bye, Rouslan From taharaxp at gmail.com Mon Apr 16 16:56:04 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Tue, 17 Apr 2012 05:56:04 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8C5A37.4030104@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> Message-ID: > I'm not sure what you are trying to say here, but I find dealing with > one really big stylesheet quite painful :) Smaller than lib-common.php :) Because I optimized, the total size is smaller than professional_css. However, the size increased for Responsive Web Design :( > But then you need to maintain two copies of almost the same stylesheet. > At some point in time they may, and probably will, diverge. So it's > extra work for developers and maintainers. Yes, almost the same stylesheet. Therefore, I maintain a main style.css. Then, I merge to style_rtl.css by using tool (WinMerge). It would be also possible to make a difference coding style_rtl.css, and override the style.css. In any case, the size will not be a problem. For maintenance, there is a problem in your style.css.php a little. Because it is processed on the server side, the location of the real stylesheet files can not be determined. Not find by using Firebug :) -- Yoshinori Tahara - dengen From rouslan at placella.com Tue Apr 17 11:16:04 2012 From: rouslan at placella.com (Rouslan Placella) Date: Tue, 17 Apr 2012 16:16:04 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> Message-ID: <4F8D8934.9080605@placella.com> On 16/04/12 21:56, Yoshinori Tahara wrote: >> I'm not sure what you are trying to say here, but I find dealing with >> one really big stylesheet quite painful :) > > Smaller than lib-common.php :) > Because I optimized, the total size is smaller than professional_css. > However, the size increased for Responsive Web Design :( > >> But then you need to maintain two copies of almost the same stylesheet. >> At some point in time they may, and probably will, diverge. So it's >> extra work for developers and maintainers. > > Yes, almost the same stylesheet. Therefore, I maintain a main style.css. > Then, I merge to style_rtl.css by using tool (WinMerge). > It would be also possible to make a difference coding style_rtl.css, > and override the style.css. > > In any case, the size will not be a problem. > > For maintenance, there is a problem in your style.css.php a little. > Because it is processed on the server side, the location of the real > stylesheet files can not be determined. > Not find by using Firebug :) It is possible to see which file a particular line is from. In the CSS tab from Firebug, simply select "Source edit" and you will see that there are comments that tell you which section comes from which file. Bye, Rouslan From komma at ivywe.co.jp Wed Apr 18 15:00:13 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Thu, 19 Apr 2012 04:00:13 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8D8934.9080605@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> Message-ID: Hi, Rouslan Thank you so much for your work. Design is cool but I wonder about using style.css,php. I installed Geeklog-ede42628dc11. New Geeklog site display faster than Geeklog1.8.1 site indeed. But Newpro theme and Professional_css and professional were the same display speed. Why style.css.php is used in Newpro theme? Geeklog-ede42628dc11: - Created this page in 0.08 seconds by using newpro ...using style.css,php - Created this page in 0.08 seconds by using professional_css ...not using style.css,php - Created this page in 0.08 seconds by using professional ...using only style.css Geeklog-1.8.1 - Created this page in 0.11 seconds by using professional_css Theme system is very important. Theme designer's opinion is so important. I saw Firebug and I understood your opinion, but many other designer will be puzzled about theme system, probably. -- Geeklog Japanese Ivy 2012/4/18 Rouslan Placella : > On 16/04/12 21:56, Yoshinori Tahara wrote: >>> I'm not sure what you are trying to say here, but I find dealing with >>> one really big stylesheet quite painful :) >> >> Smaller than lib-common.php :) >> Because I optimized, the total size is smaller than professional_css. >> However, the size increased for Responsive Web Design :( >> >>> But then you need to maintain two copies of almost the same stylesheet. >>> At some point in time they may, and probably will, diverge. So it's >>> extra work for developers and maintainers. >> >> Yes, almost the same stylesheet. Therefore, I maintain a main style.css. >> Then, I merge to style_rtl.css by using tool (WinMerge). >> It would be also possible to make a difference coding style_rtl.css, >> and override the style.css. >> >> In any case, the size will not be a problem. >> >> For maintenance, there is a problem in your style.css.php a little. >> Because it is processed on the server side, the location of the real >> stylesheet files can not be determined. >> Not find by using Firebug :) > > It is possible to see which file a particular line is from. In the CSS > tab from Firebug, simply select "Source edit" and you will see that > there are comments that tell you which section comes from which file. > > Bye, > Rouslan From rouslan at placella.com Wed Apr 18 15:12:30 2012 From: rouslan at placella.com (Rouslan Placella) Date: Wed, 18 Apr 2012 20:12:30 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> Message-ID: <4F8F121E.2030300@placella.com> Hi Ivy, The times that you have posted are for processing PHP code and have nothing to do with the theme. The CSS is loaded asynchronously and you can only see the overhead for those with a network monitor (e.g.: wireshark or firebug's "Net" panel). Anyway, I can assure you that firing one HTTP request is much faster than firing a dozen of them... Bye, Rouslan On 18/04/12 20:00, ???? Geeklog IvyWe wrote: > Hi, Rouslan > > Thank you so much for your work. > Design is cool but I wonder about using style.css,php. > > I installed Geeklog-ede42628dc11. > New Geeklog site display faster than Geeklog1.8.1 site indeed. > But Newpro theme and Professional_css and professional were the same > display speed. > Why style.css.php is used in Newpro theme? > > Geeklog-ede42628dc11: > - Created this page in 0.08 seconds by using newpro > ...using style.css,php > - Created this page in 0.08 seconds by using professional_css ...not > using style.css,php > - Created this page in 0.08 seconds by using professional > ...using only style.css > > Geeklog-1.8.1 > - Created this page in 0.11 seconds by using professional_css > > Theme system is very important. > Theme designer's opinion is so important. > I saw Firebug and I understood your opinion, but many other designer > will be puzzled about theme system, probably. > > -- > Geeklog Japanese > Ivy > > > > 2012/4/18 Rouslan Placella : >> On 16/04/12 21:56, Yoshinori Tahara wrote: >>>> I'm not sure what you are trying to say here, but I find dealing with >>>> one really big stylesheet quite painful :) >>> >>> Smaller than lib-common.php :) >>> Because I optimized, the total size is smaller than professional_css. >>> However, the size increased for Responsive Web Design :( >>> >>>> But then you need to maintain two copies of almost the same stylesheet. >>>> At some point in time they may, and probably will, diverge. So it's >>>> extra work for developers and maintainers. >>> >>> Yes, almost the same stylesheet. Therefore, I maintain a main style.css. >>> Then, I merge to style_rtl.css by using tool (WinMerge). >>> It would be also possible to make a difference coding style_rtl.css, >>> and override the style.css. >>> >>> In any case, the size will not be a problem. >>> >>> For maintenance, there is a problem in your style.css.php a little. >>> Because it is processed on the server side, the location of the real >>> stylesheet files can not be determined. >>> Not find by using Firebug :) >> >> It is possible to see which file a particular line is from. In the CSS >> tab from Firebug, simply select "Source edit" and you will see that >> there are comments that tell you which section comes from which file. >> >> Bye, >> Rouslan > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From geeklog at mystral-kk.net Wed Apr 18 19:00:49 2012 From: geeklog at mystral-kk.net (geeklog at mystral-kk.net) Date: Thu, 19 Apr 2012 08:00:49 +0900 (JST) Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8F121E.2030300@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> <4F8F121E.2030300@placella.com> Message-ID: <44209.183.90.182.17.1334790049.squirrel@www.s215.xrea.com> Hi all, > Hi Ivy, > > The times that you have posted are for processing PHP code and have > nothing to do with the theme. The CSS is loaded asynchronously and you > can only see the overhead for those with a network monitor (e.g.: > wireshark or firebug's "Net" panel). Anyway, I can assure you that > firing one HTTP request is much faster than firing a dozen of them... Yoshinori Tahara decreases the number of HTTP request by combining all CSS files into one by the theme designer's hand, while Rouslan does so by merging all CSS files on the server-side (PHP). The ways look different, but what is done is similar. So, which is the more suitable for encouraging theme designers to create a new work? I mean "theme designers" are ones who don't know much about PHP. I am not a theme designer, so I don't know the answer. However, it is important whether theme designers, not developers, feel it easy to produce a new theme. As for Rouslan's way, why don't you use tools to optimize CSS and JavaScript files, such as minify[1]? You should do minify CSS files better and cache them on the **server** side. [1] http://code.google.com/p/minify/ (New BSD License) -- mystral-kk geeklog at mystral-kk.net http://mystral-kk.net From websitemaster at cogeco.net Wed Apr 18 20:13:28 2012 From: websitemaster at cogeco.net (Tom) Date: Wed, 18 Apr 2012 20:13:28 -0400 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <44209.183.90.182.17.1334790049.squirrel@www.s215.xrea.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> <4F8F121E.2030300@placella.com> <4 4209.183.90.182.17.133 4790049.squirrel@www.s215.xrea.com> Message-ID: <016201cd1dc1$403a0410$c0ae0c30$@cogeco.net> At some point in the future I plan on adding caching of css files to the Geeklog scripts class. This way the entire sites css files (plugins, etc) will be compressed and cached along with a themes. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of geeklog at mystral-kk.net Sent: April-18-12 7:01 PM To: Geeklog Development Subject: Re: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) Hi all, > Hi Ivy, > > The times that you have posted are for processing PHP code and have > nothing to do with the theme. The CSS is loaded asynchronously and you > can only see the overhead for those with a network monitor (e.g.: > wireshark or firebug's "Net" panel). Anyway, I can assure you that > firing one HTTP request is much faster than firing a dozen of them... Yoshinori Tahara decreases the number of HTTP request by combining all CSS files into one by the theme designer's hand, while Rouslan does so by merging all CSS files on the server-side (PHP). The ways look different, but what is done is similar. So, which is the more suitable for encouraging theme designers to create a new work? I mean "theme designers" are ones who don't know much about PHP. I am not a theme designer, so I don't know the answer. However, it is important whether theme designers, not developers, feel it easy to produce a new theme. As for Rouslan's way, why don't you use tools to optimize CSS and JavaScript files, such as minify[1]? You should do minify CSS files better and cache them on the **server** side. [1] http://code.google.com/p/minify/ (New BSD License) -- mystral-kk geeklog at mystral-kk.net http://mystral-kk.net _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From komma at ivywe.co.jp Thu Apr 19 12:36:27 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Fri, 20 Apr 2012 01:36:27 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F8F121E.2030300@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> <4F8F121E.2030300@placella.com> Message-ID: Hi, Rouslan > The times that you have posted are for processing PHP code and have > nothing to do with the theme. The CSS is loaded asynchronously and you > can only see the overhead for those with a network monitor (e.g.: > wireshark or firebug's "Net" panel). Anyway, I can assure you that > firing one HTTP request is much faster than firing a dozen of them... I see! my mistake. I understand your style.css,php. If I want to test theme, functions.php change normal type, after that, I can change functions.php using style.css,php type for speed. Is it okay? By the way, I like responsive web design theme. What about responsive web design? Thanks. -- Geeklog Japanese Ivy 2012/4/19 Rouslan Placella : > Hi Ivy, > > The times that you have posted are for processing PHP code and have > nothing to do with the theme. The CSS is loaded asynchronously and you > can only see the overhead for those with a network monitor (e.g.: > wireshark or firebug's "Net" panel). Anyway, I can assure you that > firing one HTTP request is much faster than firing a dozen of them... > > Bye, > Rouslan > > On 18/04/12 20:00, ???? Geeklog IvyWe wrote: >> Hi, Rouslan >> >> Thank you so much for your work. >> Design is cool but I wonder about using style.css,php. >> >> I installed Geeklog-ede42628dc11. >> New Geeklog site display faster than Geeklog1.8.1 site indeed. >> But Newpro theme and Professional_css and professional were the same >> display speed. >> Why style.css.php is used in Newpro theme? >> >> Geeklog-ede42628dc11: >> - Created this page in 0.08 seconds by using newpro >> ...using style.css,php >> - Created this page in 0.08 seconds by using professional_css ...not >> using style.css,php >> - Created this page in 0.08 seconds by using professional >> ...using only style.css >> >> Geeklog-1.8.1 >> - Created this page in 0.11 seconds by using professional_css >> >> Theme system is very important. >> Theme designer's opinion is so important. >> I saw Firebug and I understood your opinion, but many other designer >> will be puzzled about theme system, probably. >> >> -- >> Geeklog Japanese >> Ivy >> >> >> >> 2012/4/18 Rouslan Placella : >>> On 16/04/12 21:56, Yoshinori Tahara wrote: >>>>> I'm not sure what you are trying to say here, but I find dealing with >>>>> one really big stylesheet quite painful :) >>>> >>>> Smaller than lib-common.php :) >>>> Because I optimized, the total size is smaller than professional_css. >>>> However, the size increased for Responsive Web Design :( >>>> >>>>> But then you need to maintain two copies of almost the same stylesheet. >>>>> At some point in time they may, and probably will, diverge. So it's >>>>> extra work for developers and maintainers. >>>> >>>> Yes, almost the same stylesheet. Therefore, I maintain a main style.css. >>>> Then, I merge to style_rtl.css by using tool (WinMerge). >>>> It would be also possible to make a difference coding style_rtl.css, >>>> and override the style.css. >>>> >>>> In any case, the size will not be a problem. >>>> >>>> For maintenance, there is a problem in your style.css.php a little. >>>> Because it is processed on the server side, the location of the real >>>> stylesheet files can not be determined. >>>> Not find by using Firebug :) >>> >>> It is possible to see which file a particular line is from. In the CSS >>> tab from Firebug, simply select "Source edit" and you will see that >>> there are comments that tell you which section comes from which file. >>> >>> Bye, >>> Rouslan >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Fri Apr 20 09:26:11 2012 From: rouslan at placella.com (Rouslan Placella) Date: Fri, 20 Apr 2012 14:26:11 +0100 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> <4F8F121E.2030300@placella.com> Message-ID: <4F9163F3.70703@placella.com> On 19/04/12 17:36, ???? Geeklog IvyWe wrote: > Hi, Rouslan > >> The times that you have posted are for processing PHP code and have >> nothing to do with the theme. The CSS is loaded asynchronously and you >> can only see the overhead for those with a network monitor (e.g.: >> wireshark or firebug's "Net" panel). Anyway, I can assure you that >> firing one HTTP request is much faster than firing a dozen of them... > > I see! my mistake. > I understand your style.css,php. > > If I want to test theme, functions.php change normal type, > after that, I can change functions.php using style.css,php type for speed. > Is it okay? Not sure what you are asking here... > By the way, I like responsive web design theme. > What about responsive web design? It's out of scope for the newpro theme for now, maybe later. > Thanks. > > -- > Geeklog Japanese > Ivy > > > 2012/4/19 Rouslan Placella : >> Hi Ivy, >> >> The times that you have posted are for processing PHP code and have >> nothing to do with the theme. The CSS is loaded asynchronously and you >> can only see the overhead for those with a network monitor (e.g.: >> wireshark or firebug's "Net" panel). Anyway, I can assure you that >> firing one HTTP request is much faster than firing a dozen of them... >> >> Bye, >> Rouslan >> >> On 18/04/12 20:00, ???? Geeklog IvyWe wrote: >>> Hi, Rouslan >>> >>> Thank you so much for your work. >>> Design is cool but I wonder about using style.css,php. >>> >>> I installed Geeklog-ede42628dc11. >>> New Geeklog site display faster than Geeklog1.8.1 site indeed. >>> But Newpro theme and Professional_css and professional were the same >>> display speed. >>> Why style.css.php is used in Newpro theme? >>> >>> Geeklog-ede42628dc11: >>> - Created this page in 0.08 seconds by using newpro >>> ...using style.css,php >>> - Created this page in 0.08 seconds by using professional_css ...not >>> using style.css,php >>> - Created this page in 0.08 seconds by using professional >>> ...using only style.css >>> >>> Geeklog-1.8.1 >>> - Created this page in 0.11 seconds by using professional_css >>> >>> Theme system is very important. >>> Theme designer's opinion is so important. >>> I saw Firebug and I understood your opinion, but many other designer >>> will be puzzled about theme system, probably. >>> >>> -- >>> Geeklog Japanese >>> Ivy >>> >>> >>> >>> 2012/4/18 Rouslan Placella : >>>> On 16/04/12 21:56, Yoshinori Tahara wrote: >>>>>> I'm not sure what you are trying to say here, but I find dealing with >>>>>> one really big stylesheet quite painful :) >>>>> >>>>> Smaller than lib-common.php :) >>>>> Because I optimized, the total size is smaller than professional_css. >>>>> However, the size increased for Responsive Web Design :( >>>>> >>>>>> But then you need to maintain two copies of almost the same stylesheet. >>>>>> At some point in time they may, and probably will, diverge. So it's >>>>>> extra work for developers and maintainers. >>>>> >>>>> Yes, almost the same stylesheet. Therefore, I maintain a main style.css. >>>>> Then, I merge to style_rtl.css by using tool (WinMerge). >>>>> It would be also possible to make a difference coding style_rtl.css, >>>>> and override the style.css. >>>>> >>>>> In any case, the size will not be a problem. >>>>> >>>>> For maintenance, there is a problem in your style.css.php a little. >>>>> Because it is processed on the server side, the location of the real >>>>> stylesheet files can not be determined. >>>>> Not find by using Firebug :) >>>> >>>> It is possible to see which file a particular line is from. In the CSS >>>> tab from Firebug, simply select "Source edit" and you will see that >>>> there are comments that tell you which section comes from which file. >>>> >>>> Bye, >>>> Rouslan >>> _______________________________________________ >>> geeklog-devel mailing list >>> geeklog-devel at lists.geeklog.net >>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From komma at ivywe.co.jp Fri Apr 20 14:03:31 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Sat, 21 Apr 2012 03:03:31 +0900 Subject: [geeklog-devel] Non table layout (was Geeklog 1.9.0 or Geeklog 2.0.0?) In-Reply-To: <4F9163F3.70703@placella.com> References: <001401cd1806$99cef500$cd6cdf00$@cogeco.net> <38139.183.90.182.17.1334318628.squirrel@www.s215.xrea.com> <00cf01cd197d$10079070$3016b150$@cogeco.net> <000101cd1b14$d5d45250$817cf6f0$@cogeco.net> <4F8ADCF7.5060909@placella.com> <4F8B2110.9000807@placella.com> <4F8C5A37.4030104@placella.com> <4F8D8934.9080605@placella.com> <4F8F121E.2030300@placella.com> <4F9163F3.70703@placella.com> Message-ID: 2012?4?20?22:26 Rouslan Placella : > On 19/04/12 17:36, ???? Geeklog IvyWe wrote: >> Hi, Rouslan >> >>> The times that you have posted are for processing PHP code and have >>> nothing to do with the theme. The CSS is loaded asynchronously and you >>> can only see the overhead for those with a network monitor (e.g.: >>> wireshark or firebug's "Net" panel). Anyway, I can assure you that >>> firing one HTTP request is much faster than firing a dozen of them... >> >> I see! my mistake. >> I understand your style.css,php. >> >> If I want to test theme, functions.php change normal type, >> after that, I can change functions.php using style.css,php type for speed. >> Is it okay? > > Not sure what you are asking here... I understand that we can choose to use style.css.php or not by coding functions.php. So It's okay. >> By the way, I like responsive web design theme. >> What about responsive web design? > > It's out of scope for the newpro theme for now, maybe later. I see. Thanks. -- Geeklog Japanse Ivy From websitemaster at cogeco.net Sun Apr 22 10:32:51 2012 From: websitemaster at cogeco.net (Tom) Date: Sun, 22 Apr 2012 10:32:51 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Message-ID: <008601cd2094$cc6b5fd0$65421f70$@cogeco.net> Hey All, We would like to welcome Dengen (Yoshinori Tahara) to the Geeklog Development team! We look forward to his valued contributions to Geeklog. His first job will be adding his latest work related to COM_createHTMLDocument and his new theme to the upcoming release of Geeklog 2.0.0. With this in mind we hope to see Geeklog 2.0.0 first beta release happen in the first part of May. Once the final release of Geeklog 2.0.0 happens I would like to have a discussion to see what new features we would like to add to later versions of Geeklog. Once that happens and we flush out a timeline and have people committed to writing these updates I will update the Wiki Page (http://wiki.geeklog.net/index.php/Proposed_Roadmap). The Wiki Proposed Roadmap will be more of a general overview/timeline of where we hope Geeklog is headed. The actual features and bugs being worked on will be added as always to the Geeklog Bugtracker. From this our actual Roadmap will be created (http://project.geeklog.net/tracking/roadmap_page.php). This is an easy way to see what people are working on and what new features and bug fixes are expected in the next release. Moving forward I hope to keep this better updated so we can keep the Geeklog Community better informed. Tom From cordiste at free.fr Sun Apr 22 11:00:10 2012 From: cordiste at free.fr (cordiste) Date: Sun, 22 Apr 2012 17:00:10 +0200 Subject: [geeklog-devel] Geeklog 2.0.0 In-Reply-To: <008601cd2094$cc6b5fd0$65421f70$@cogeco.net> References: <008601cd2094$cc6b5fd0$65421f70$@cogeco.net> Message-ID: Welcome to Dengen and thank you for all your work. Also a big thanks to the Geeklog Community. Ben 2012/4/22 Tom > Hey All, > > We would like to welcome Dengen (Yoshinori Tahara) to the Geeklog > Development team! We look forward to his valued contributions to Geeklog. > > His first job will be adding his latest work related to > COM_createHTMLDocument and his new theme to the upcoming release of Geeklog > 2.0.0. > > With this in mind we hope to see Geeklog 2.0.0 first beta release happen in > the first part of May. > > Once the final release of Geeklog 2.0.0 happens I would like to have a > discussion to see what new features we would like to add to later versions > of Geeklog. Once that happens and we flush out a timeline and have people > committed to writing these updates I will update the Wiki Page > (http://wiki.geeklog.net/index.php/Proposed_Roadmap). The Wiki Proposed > Roadmap will be more of a general overview/timeline of where we hope > Geeklog > is headed. > > The actual features and bugs being worked on will be added as always to the > Geeklog Bugtracker. From this our actual Roadmap will be created > (http://project.geeklog.net/tracking/roadmap_page.php). This is an easy > way > to see what people are working on and what new features and bug fixes are > expected in the next release. Moving forward I hope to keep this better > updated so we can keep the Geeklog Community better informed. > > Tom > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taharaxp at gmail.com Sun Apr 22 11:07:46 2012 From: taharaxp at gmail.com (Yoshinori Tahara) Date: Mon, 23 Apr 2012 00:07:46 +0900 Subject: [geeklog-devel] Geeklog 2.0.0 In-Reply-To: References: <008601cd2094$cc6b5fd0$65421f70$@cogeco.net> Message-ID: Hi all, Thank you for having me. > My idea is if a theme does not contain the config option > ($_CONF['supported_version_theme']) or if it is set to 1.8.1 then the theme > is considered to support Geeklog 1.8.1 and then Geeklog will run the > backwards compatible option. If it is set to 2.0.0 a theme is considered > compatible with COM_createHTMLDocument . I agree with your ideas. It is that the same handling as a constant VERSION. -- Yoshinori Tahara - dengen From komma at ivywe.co.jp Sun Apr 22 23:06:07 2012 From: komma at ivywe.co.jp (=?ISO-2022-JP?B?GyRCOiM2cEUvO1IbKEIgR2Vla2xvZyBJdnlXZQ==?=) Date: Mon, 23 Apr 2012 12:06:07 +0900 Subject: [geeklog-devel] Geeklog 2.0.0 In-Reply-To: References: <008601cd2094$cc6b5fd0$65421f70$@cogeco.net> Message-ID: Hi, all We Japanese member are so glad. Thank you to the Geeklog community. -- Geeklog Japanese Ivy From websitemaster at cogeco.net Mon Apr 23 10:08:57 2012 From: websitemaster at cogeco.net (Tom) Date: Mon, 23 Apr 2012 10:08:57 -0400 Subject: [geeklog-devel] Breadcrumbs Message-ID: <003301cd215a$9fbd29c0$df377d40$@cogeco.net> As you probably already know Geeklog 2.0.0 supports breadcrumbs. There are 2 things I just wanted to review... 1) This is more for theme developers. Geeklog's breadcrumbs are setup to support Google's Rich Snippets which allows Google to easily determine the structure of the website and include it in the search results. Messing with the Breadcrumb template files too much may cause Google not to be able to recognize the structure. If you update the breadcrumb template files I would suggest testing the Geeklog page with the breadcrumbs on it with Google's Rich Snippets testing tool: http://www.google.com/webmasters/tools/richsnippets 2) Since articles and other objects can belong to more than one topic, when that article is viewed all breadcrumb trails for that article are returned and display. This happens independent of the topic the article is currently being displayed in. This functionality is supported by Google. See this page for more details and an example: http://project.geeklog.net/tracking/view.php?id=1441 What I was wondering is should there be a config option that disables displaying more than one breadcrumb trail at a time (ie the object would only display the breadcrumb trail of the topic it currently is in and not all of the others it may belong too). Tom From vfuria at gmail.com Mon Apr 23 11:26:46 2012 From: vfuria at gmail.com (Vincent Furia) Date: Mon, 23 Apr 2012 09:26:46 -0600 Subject: [geeklog-devel] Breadcrumbs In-Reply-To: <003301cd215a$9fbd29c0$df377d40$@cogeco.net> References: <003301cd215a$9fbd29c0$df377d40$@cogeco.net> Message-ID: On Mon, Apr 23, 2012 at 08:08, Tom wrote: > What I was wondering is should there be a config option that disables > displaying more than one breadcrumb trail at a time (ie the object would > only display the breadcrumb trail of the topic it currently is in and not > all of the others it may belong too). > Tony, do you check for user access to the breadcrumb location? I'm curious if a user with access to Topic A and *not* Topic B will see breadcrumbs to both locations for a story that is in both topic A and B. If so, that might be an "information leak" that should be plugged. -Vinny -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Mon Apr 23 13:26:12 2012 From: websitemaster at cogeco.net (Tom) Date: Mon, 23 Apr 2012 13:26:12 -0400 Subject: [geeklog-devel] Breadcrumbs In-Reply-To: References: <003301cd215a$9fbd29c0$df377d40$@cogeco.net> Message-ID: <004001cd2176$2e024290$8a06c7b0$@cogeco.net> Good catch. The breadcrumb trail would display but the links would be disabled. It shouldn't display at all. Also caught another bug. Currently you can only view the full story if you have access to both topics (the story still comes up in the topic view fine though). Obviously if you have access to one topic you should still be able to view the story in that topic. Looking at the code I see this probably happen because we take the min access value of all topics it belongs to when allowing a story edit to happen. You can only edit a story if you have edit access to the story and edit access to all of the topics. I will have to look into this further. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Vincent Furia Sent: April-23-12 11:27 AM To: Geeklog Development Subject: Re: [geeklog-devel] Breadcrumbs On Mon, Apr 23, 2012 at 08:08, Tom wrote: What I was wondering is should there be a config option that disables displaying more than one breadcrumb trail at a time (ie the object would only display the breadcrumb trail of the topic it currently is in and not all of the others it may belong too). Tony, do you check for user access to the breadcrumb location? I'm curious if a user with access to Topic A and not Topic B will see breadcrumbs to both locations for a story that is in both topic A and B. If so, that might be an "information leak" that should be plugged. -Vinny -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sat Apr 28 10:45:21 2012 From: websitemaster at cogeco.net (Tom) Date: Sat, 28 Apr 2012 10:45:21 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Themes Message-ID: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> Okay, We currently have 4 themes in the Geeklog Repository. denim, newpro, professional, and professional_css. Both professional themes support the Geeklog 1.8.1 theme engine while denim and soon newpro will support the upgraded version When we release Geeklog 2.0.0 I would like to include 3 themes denim, newpro and professional in the install. I figure we should include the professional theme since that is the theme most people probably have based their own themes on and it will make it easier for them to update their site. I think once we have done one or two bug fix releases of Geeklog (ie Geeklog 2.0.x) we can drop the professional theme from the install and just add it to the themes downloads directory if people are still looking for it. This way we can just concentrate on the 2 main themes (denim, newpro) going forward. Also Developers remember if we add any new template variables or make changes to Geeklog code that affects themes we need to make sure all themes in the repository receives the updates (if it is for their supported theme engine). The last few things I plan to do before the release: 1) Upgrade jQuery and jQuery UI to the latest version 2) Add Breadcrumb support to the new theme engine so breadcrumbs can be displayed in the header template. Thoughts, Questions, Suggestions, Comments? :-) Tom From trinity93 at gmail.com Sat Apr 28 20:51:52 2012 From: trinity93 at gmail.com (Trinity) Date: Sat, 28 Apr 2012 19:51:52 -0500 Subject: [geeklog-devel] Geeklog 2.0.0 Themes In-Reply-To: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> References: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> Message-ID: perhaps include a clean "template" theme that is just basic block css for devs to use as a starter base theme for new themes also some one should create a 2.0 version of the plugin development example plugin and update any plugin api docs. On Sat, Apr 28, 2012 at 9:45 AM, Tom wrote: > Okay, > > We currently have 4 themes in the Geeklog Repository. denim, newpro, > professional, and professional_css. Both professional themes support the > Geeklog 1.8.1 theme engine while denim and soon newpro will support the > upgraded version > > When we release Geeklog 2.0.0 I would like to include 3 themes denim, > newpro > and professional in the install. I figure we should include the > professional > theme since that is the theme most people probably have based their own > themes on and it will make it easier for them to update their site. > > I think once we have done one or two bug fix releases of Geeklog (ie > Geeklog > 2.0.x) we can drop the professional theme from the install and just add it > to the themes downloads directory if people are still looking for it. > This > way we can just concentrate on the 2 main themes (denim, newpro) going > forward. > > Also Developers remember if we add any new template variables or make > changes to Geeklog code that affects themes we need to make sure all themes > in the repository receives the updates (if it is for their supported theme > engine). > > The last few things I plan to do before the release: > > 1) Upgrade jQuery and jQuery UI to the latest version > > 2) Add Breadcrumb support to the new theme engine so breadcrumbs can be > displayed in the header template. > > Thoughts, Questions, Suggestions, Comments? :-) > > Tom > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Sun Apr 29 09:33:15 2012 From: websitemaster at cogeco.net (Tom) Date: Sun, 29 Apr 2012 09:33:15 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Themes In-Reply-To: References: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> Message-ID: <003401cd260c$a18f0460$e4ad0d20$@cogeco.net> Hi Trinity, I think for the most part the plugin API docs have been kept updated. I know the themes wiki docs need a good update now, hopefully that will get down when we release Geeklog 2.0.0 (which reminds me I have to finish up the topics wiki page). The Universal Plugin Toolkit does need a rather large upgrade though. I think it has been a few years since anyone has touched it. I almost think we need to include it the repository to make it easier for developers to remember to keep it updated. Then when we release a new version of Geeklog we can just release the plugin separately with any new updates. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Trinity Sent: April-28-12 8:52 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 2.0.0 Themes perhaps include a clean "template" theme that is just basic block css for devs to use as a starter base theme for new themes also some one should create a 2.0 version of the plugin development example plugin and update any plugin api docs. On Sat, Apr 28, 2012 at 9:45 AM, Tom wrote: Okay, We currently have 4 themes in the Geeklog Repository. denim, newpro, professional, and professional_css. Both professional themes support the Geeklog 1.8.1 theme engine while denim and soon newpro will support the upgraded version When we release Geeklog 2.0.0 I would like to include 3 themes denim, newpro and professional in the install. I figure we should include the professional theme since that is the theme most people probably have based their own themes on and it will make it easier for them to update their site. I think once we have done one or two bug fix releases of Geeklog (ie Geeklog 2.0.x) we can drop the professional theme from the install and just add it to the themes downloads directory if people are still looking for it. This way we can just concentrate on the 2 main themes (denim, newpro) going forward. Also Developers remember if we add any new template variables or make changes to Geeklog code that affects themes we need to make sure all themes in the repository receives the updates (if it is for their supported theme engine). The last few things I plan to do before the release: 1) Upgrade jQuery and jQuery UI to the latest version 2) Add Breadcrumb support to the new theme engine so breadcrumbs can be displayed in the header template. Thoughts, Questions, Suggestions, Comments? :-) Tom _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From rouslan at placella.com Sun Apr 29 09:35:13 2012 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 29 Apr 2012 14:35:13 +0100 Subject: [geeklog-devel] Geeklog 2.0.0 Themes In-Reply-To: <003401cd260c$a18f0460$e4ad0d20$@cogeco.net> References: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> <003401cd260c$a18f0460$e4ad0d20$@cogeco.net> Message-ID: <4F9D4391.3060702@placella.com> The plugin toolkit *is* in the repo: http://project.geeklog.net/cgi-bin/hgwebdir.cgi/plugin-toolkit/ Bye, Rouslan On 29/04/12 14:33, Tom wrote: > Hi Trinity, > > > > I think for the most part the plugin API docs have been kept updated. I > know the themes wiki docs need a good update now, hopefully that will get > down when we release Geeklog 2.0.0 (which reminds me I have to finish up the > topics wiki page). > > > > The Universal Plugin Toolkit does need a rather large upgrade though. I > think it has been a few years since anyone has touched it. I almost think we > need to include it the repository to make it easier for developers to > remember to keep it updated. Then when we release a new version of Geeklog > we can just release the plugin separately with any new updates. > > > > Tom > > > > > > > > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Trinity > Sent: April-28-12 8:52 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog 2.0.0 Themes > > > > perhaps include a clean "template" theme that is just basic block css for > devs to use as a starter base theme for new themes also some one should > create a 2.0 version of the plugin development example plugin and update any > plugin api docs. > > On Sat, Apr 28, 2012 at 9:45 AM, Tom wrote: > > Okay, > > We currently have 4 themes in the Geeklog Repository. denim, newpro, > professional, and professional_css. Both professional themes support the > Geeklog 1.8.1 theme engine while denim and soon newpro will support the > upgraded version > > When we release Geeklog 2.0.0 I would like to include 3 themes denim, newpro > and professional in the install. I figure we should include the professional > theme since that is the theme most people probably have based their own > themes on and it will make it easier for them to update their site. > > I think once we have done one or two bug fix releases of Geeklog (ie Geeklog > 2.0.x) we can drop the professional theme from the install and just add it > to the themes downloads directory if people are still looking for it. This > way we can just concentrate on the 2 main themes (denim, newpro) going > forward. > > Also Developers remember if we add any new template variables or make > changes to Geeklog code that affects themes we need to make sure all themes > in the repository receives the updates (if it is for their supported theme > engine). > > The last few things I plan to do before the release: > > 1) Upgrade jQuery and jQuery UI to the latest version > > 2) Add Breadcrumb support to the new theme engine so breadcrumbs can be > displayed in the header template. > > Thoughts, Questions, Suggestions, Comments? :-) > > Tom > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sun Apr 29 10:02:57 2012 From: websitemaster at cogeco.net (Tom) Date: Sun, 29 Apr 2012 10:02:57 -0400 Subject: [geeklog-devel] Geeklog 2.0.0 Themes In-Reply-To: <4F9D4391.3060702@placella.com> References: <000101cd254d$89ed1d20$9dc75760$@cogeco.net> <003401cd260c$a18f0460$e4ad0d20$@cogeco.net> <4F9D4391.3060702@placella.com> Message-ID: <003f01cd2610$c79d7610$56d86230$@cogeco.net> :-) -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan Placella Sent: April-29-12 9:35 AM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] Geeklog 2.0.0 Themes The plugin toolkit *is* in the repo: http://project.geeklog.net/cgi-bin/hgwebdir.cgi/plugin-toolkit/ Bye, Rouslan On 29/04/12 14:33, Tom wrote: > Hi Trinity, > > > > I think for the most part the plugin API docs have been kept updated. > I know the themes wiki docs need a good update now, hopefully that > will get down when we release Geeklog 2.0.0 (which reminds me I have > to finish up the topics wiki page). > > > > The Universal Plugin Toolkit does need a rather large upgrade though. > I think it has been a few years since anyone has touched it. I almost > think we need to include it the repository to make it easier for > developers to remember to keep it updated. Then when we release a new > version of Geeklog we can just release the plugin separately with any new updates. > > > > Tom > > > > > > > > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Trinity > Sent: April-28-12 8:52 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog 2.0.0 Themes > > > > perhaps include a clean "template" theme that is just basic block css > for devs to use as a starter base theme for new themes also some one > should create a 2.0 version of the plugin development example plugin > and update any plugin api docs. > > On Sat, Apr 28, 2012 at 9:45 AM, Tom wrote: > > Okay, > > We currently have 4 themes in the Geeklog Repository. denim, newpro, > professional, and professional_css. Both professional themes support > the Geeklog 1.8.1 theme engine while denim and soon newpro will > support the upgraded version > > When we release Geeklog 2.0.0 I would like to include 3 themes denim, > newpro and professional in the install. I figure we should include the > professional theme since that is the theme most people probably have > based their own themes on and it will make it easier for them to update their site. > > I think once we have done one or two bug fix releases of Geeklog (ie > Geeklog > 2.0.x) we can drop the professional theme from the install and just > add it to the themes downloads directory if people are still looking > for it. This way we can just concentrate on the 2 main themes (denim, > newpro) going forward. > > Also Developers remember if we add any new template variables or make > changes to Geeklog code that affects themes we need to make sure all > themes in the repository receives the updates (if it is for their > supported theme engine). > > The last few things I plan to do before the release: > > 1) Upgrade jQuery and jQuery UI to the latest version > > 2) Add Breadcrumb support to the new theme engine so breadcrumbs can > be displayed in the header template. > > Thoughts, Questions, Suggestions, Comments? :-) > > Tom > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel