From dirk at haun-online.de Thu Mar 3 15:19:34 2011 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 3 Mar 2011 21:19:34 +0100 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: <1297429107.2690.31.camel@roccivic-pc> References: <20110124120102.18566t3vg8gswu0g@webmail.df.eu> <1297429107.2690.31.camel@roccivic-pc> Message-ID: Rouslan Placella wrote: > More ideas: > > * Add support for SQLite databases (self-explanatory). We talked about this on IRC - not sure if adding even more DB engines that hardly anyone uses is buying us anything at this point. But I dug out a somewhat related idea: Add support for MySQLi http://php.net/manual/en/book.mysqli.php Does anyone know more about MySQLi? From my understanding, it's a more modern API for MySQL. This could be interesting from a performance point of view. No idea if it's enough to make a full GSoC project, but it's probably a bit of work in any case. bye, Dirk From vfuria at gmail.com Thu Mar 3 15:48:13 2011 From: vfuria at gmail.com (Vincent Furia) Date: Thu, 3 Mar 2011 13:48:13 -0700 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: References: <20110124120102.18566t3vg8gswu0g@webmail.df.eu> <1297429107.2690.31.camel@roccivic-pc> Message-ID: Maybe we should consider moving to a "real" database abstraction layer? That would definitely be enough work for a GSOC program and it could automatically provide support for all these lesser used database types. It would, I hope, also make maintenance a bit easier (especially for, say, MSSQL). On a similar topic, we could look at a GSOC program to change up our template library. It's a bit silly that we still don't have compiled templates (to the detriment of our performance). Joe's work could be used as a basis or the student could look at implementing an existing template library (preferably one that could be backward compatible with existing templates). These might both be too big for a GSOC project, but worth thinking about? Finally, many may not remember, but years and years ago (2002 or 2003) I pushed a big set of patches to improve page load performance. If I recall correctly, I eliminated (through combination or caching) a bunch of SQL queries, cleaned up PHP code (including getting rid of some recursion), and completely rewrote the comment display code. Doing something similar again today as a GSOC project could be beneficial to Geeklog. I hadn't brought this up before because this is an awfully non-specific task. I'm not sure it will fit well all that well into GSOC project. Any thoughts? -Vinny On Thu, Mar 3, 2011 at 13:19, Dirk Haun wrote: > Rouslan Placella wrote: > > > More ideas: > > > > * Add support for SQLite databases (self-explanatory). > > We talked about this on IRC - not sure if adding even more DB engines that > hardly anyone uses is buying us anything at this point. > > But I dug out a somewhat related idea: Add support for MySQLi > > http://php.net/manual/en/book.mysqli.php > > Does anyone know more about MySQLi? From my understanding, it's a more > modern API for MySQL. This could be interesting from a performance point of > view. No idea if it's enough to make a full GSoC project, but it's probably > a bit of work in any case. > > bye, Dirk > > _______________________________________________ > 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 cordiste at free.fr Thu Mar 3 17:40:56 2011 From: cordiste at free.fr (cordiste) Date: Thu, 3 Mar 2011 23:40:56 +0100 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: References: <20110124120102.18566t3vg8gswu0g@webmail.df.eu> <1297429107.2690.31.camel@roccivic-pc> Message-ID: Maybe we could spent a slot to finish our plugin repository, our new calendar plugin and our SocNet plugin? Ben 2011/3/3 Vincent Furia : > Maybe we should consider moving to a "real" database abstraction layer? That > would definitely be enough work for a GSOC program and it could > automatically provide support for all these lesser used database types. It > would, I hope, also make maintenance a bit easier (especially for, say, > MSSQL). > > On a similar topic, we could look at a GSOC program to change up our > template library. It's a bit silly that we still don't have compiled > templates (to the detriment of our performance). Joe's work could be used as > a basis or the student could look at implementing an existing template > library (preferably one that could be backward compatible with existing > templates). > > These might both be too big for a GSOC project, but worth thinking about? > > Finally, many may not remember, but years and years ago (2002 or 2003) I > pushed a big set of patches to improve page load performance. If I recall > correctly, I eliminated (through combination or caching) a bunch of SQL > queries, cleaned up PHP code (including getting rid of some recursion), and > completely rewrote the comment display code. Doing something similar again > today as a GSOC project could be beneficial to Geeklog. I hadn't brought > this up before because this is an awfully non-specific task. I'm not sure it > will fit well all that well into GSOC project. Any thoughts? > > -Vinny > > On Thu, Mar 3, 2011 at 13:19, Dirk Haun wrote: >> >> Rouslan Placella wrote: >> >> > More ideas: >> > >> > * Add support for SQLite databases (self-explanatory). >> >> We talked about this on IRC - not sure if adding even more DB engines that >> hardly anyone uses is buying us anything at this point. >> >> But I dug out a somewhat related idea: Add support for MySQLi >> >> http://php.net/manual/en/book.mysqli.php >> >> Does anyone know more about MySQLi? From my understanding, it's a more >> modern API for MySQL. This could be interesting from a performance point of >> view. No idea if it's enough to make a full GSoC project, but it's probably >> a bit of work in any case. >> >> bye, Dirk >> >> _______________________________________________ >> 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 jmucchiello at yahoo.com Thu Mar 3 23:23:13 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Thu, 3 Mar 2011 20:23:13 -0800 (PST) Subject: [geeklog-devel] more GSoC project ideas Message-ID: <606420.7661.qm@web31408.mail.mud.yahoo.com> The database idea is either too big or a little small depending on how you do it. I think the easy (and perhaps too small) way is to just make a PDO.class.php in the databases directory and use that to handle "legacy" database access. Then expose the PDO connection object as a global so new code can code against PDO directly. The GSOC part would be ensuring the legacy code works through PDO with as little change as possible. By the time the GSOC code was plugged into core, core would no longer support PHP4 (PDO is PHP5 only). > On a similar topic, we could look at a GSOC program to change up our > template library. It's a bit silly that we still don't have compiled > templates (to the detriment of our performance). Joe's work could be used > as a basis or the student could look at implementing an existing template > library (preferably one that could be backward compatible with existing > templates). Or you could just ask me to write it. Ben said he was going to put in my change to allow "alternate" template engines. Once that gets in, I promised to release a plugin containing my template library. The current version on my harddrive contain IF/ELSE processing, LOOPs over arrays and database, better block handling, fully backward compatible with the phplib library, and can be cached to disk or memcache (although I need to reinstall memcache since my last computer rebuild). Oh, it also has a test suite. > These might both be too big for a GSOC project, but worth thinking about? Most likely. > Finally, many may not remember, but years and years ago (2002 or 2003) I > pushed a big set of patches to improve page load performance. If I recall > correctly, I eliminated (through combination or caching) a bunch of SQL > queries, cleaned up PHP code (including getting rid of some recursion), > and > completely rewrote the comment display code. Doing something similar again > today as a GSOC project could be beneficial to Geeklog. I hadn't brought > this up before because this is an awfully non-specific task. I'm not sure > it will fit well all that well into GSOC project. Any thoughts? And I did the same thing 2007. I still have a bunch of diffs I like to apply to lib-security and lib-common because it hits the database far too many times. I tried to sneak a couple of those into the socnet changes that still aren't released. If I thought the patches would be applied, I'd make feature requests and post patches. But since there's no track record there, I don't do it. Want to reduce Geeklog's memory footprint? Compartmentalize the core functions: In public_html/search.php: define('INCL_SEARCH',1); // yes, before the include, it is safe include 'lib-common.php'; In every plugin/function.inc: if (defined('INCL_SEARCH')) include $plugin_path . 'search.inc'; And in search.inc, each plugin puts all the search related plugin_ functions. Repeat this for most of the global php files: comment, search, user, usersettings, stats!!, submit, trackback/pingback, etc. and you will reduce the load time of all pages. I've also been working on lib-smallcommon. A drop-in replacement for lib-common that can be used in AJAX calls that don't need most of the COM_ library. The code is just sitting on my hard drive since Geeklog 1.4.1 going out of date. Geeklog is not a good foundation for "web 2.0" apps as it loads the moon to deliver cosmic motes. From dilantha.tyrant at gmail.com Fri Mar 4 03:19:09 2011 From: dilantha.tyrant at gmail.com (dilantha silva) Date: Fri, 4 Mar 2011 13:49:09 +0530 Subject: [geeklog-devel] How to delete a patch Message-ID: Hi All, Can anyone please tell my how can i delete a patch in the bug tracker which is uploaded by myself. because i accidentally uploaded a patch with a bug and now i want to replace it with the new patch. Thanks in advance. -- Regards, Dilantha Silva, http://twitter.com/dilanthasilva | http://www.linkedin.com/in/dilanthasilva| https://launchpad.net/~dilantha -------------- next part -------------- An HTML attachment was scrubbed... URL: From cordiste at free.fr Fri Mar 4 03:39:08 2011 From: cordiste at free.fr (cordiste) Date: Fri, 4 Mar 2011 09:39:08 +0100 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: <606420.7661.qm@web31408.mail.mud.yahoo.com> References: <606420.7661.qm@web31408.mail.mud.yahoo.com> Message-ID: Joe, > Ben said he was going to put in my change to allow "alternate" template engines. Did I say something like that... because I don't remember... Thanks, Ben 2011/3/4 Joe Mucchiello : > The database idea is either too big or a little small depending on how you do > it. I think the easy (and perhaps too small) way is to just make a PDO.class.php > in the databases directory and use that to handle "legacy" database access. Then > expose the PDO connection object as a global so new code can code against PDO > directly. The GSOC part would be ensuring the legacy code works through PDO with > as little change as possible. By the time the GSOC code was plugged into core, > core would no longer support PHP4 (PDO is PHP5 only). > >> On a similar topic, we could look at a GSOC program to change up our >> template library. It's a bit silly that we still don't have compiled >> templates (to the detriment of our performance). Joe's work could be used >> as a basis or the student could look at implementing an existing template >> library (preferably one that could be backward compatible with existing >> templates). > > Or you could just ask me to write it. Ben said he was going to put in my change > to allow "alternate" template engines. Once that gets in, I promised to release > a plugin containing my template library. The current version on my harddrive > contain IF/ELSE processing, LOOPs over arrays and database, better block > handling, fully backward compatible with the phplib library, and can be cached > to disk or memcache (although I need to reinstall memcache since my last > computer rebuild). Oh, it also has a test suite. > >> These might both be too big for a GSOC project, but worth thinking about? > > Most likely. > >> Finally, many may not remember, but years and years ago (2002 or 2003) I >> pushed a big set of patches to improve page load performance. If I recall >> correctly, I eliminated (through combination or caching) a bunch of SQL >> queries, cleaned up PHP code (including getting rid of some recursion), >> and >> completely rewrote the comment display code. Doing something similar again >> today as a GSOC project could be beneficial to Geeklog. I hadn't brought >> this up before because this is an awfully non-specific task. I'm not sure >> it will fit well all that well into GSOC project. Any thoughts? > > And I did the same thing 2007. I still have a bunch of diffs I like to apply to > lib-security and lib-common because it hits the database far too many times. I > tried to sneak a couple of those into the socnet changes that still aren't > released. If I thought the patches would be applied, I'd make feature requests > and post patches. But since there's no track record there, I don't do it. > > Want to reduce Geeklog's memory footprint? Compartmentalize the core functions: > > In public_html/search.php: > define('INCL_SEARCH',1); // yes, before the include, it is safe > include 'lib-common.php'; > > In every plugin/function.inc: > if (defined('INCL_SEARCH')) include $plugin_path . 'search.inc'; > > And in search.inc, each plugin puts all the search related plugin_ functions. > > Repeat this for most of the global php files: comment, search, user, > usersettings, stats!!, submit, trackback/pingback, ?etc. and you will reduce the > load time of all pages. > > I've also been working on lib-smallcommon. A drop-in replacement for lib-common > that can be used in AJAX calls that don't need most of the COM_ library. The > code is just sitting on my hard drive since Geeklog 1.4.1 going out of date. > Geeklog is not a good foundation for "web 2.0" apps as it loads the moon to > deliver cosmic motes. > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From websitemaster at cogeco.net Fri Mar 4 09:09:42 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Mar 2011 09:09:42 -0500 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: References: <606420.7661.qm@web31408.mail.mud.yahoo.com> Message-ID: <006001cbda75$cef01360$6cd03a20$@cogeco.net> It was actually me Joe was talking to. -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: March-04-11 3:39 AM To: Geeklog Development Subject: Re: [geeklog-devel] more GSoC project ideas Joe, > Ben said he was going to put in my change to allow "alternate" template engines. Did I say something like that... because I don't remember... Thanks, Ben 2011/3/4 Joe Mucchiello : > The database idea is either too big or a little small depending on how > you do it. I think the easy (and perhaps too small) way is to just > make a PDO.class.php in the databases directory and use that to handle > "legacy" database access. Then expose the PDO connection object as a > global so new code can code against PDO directly. The GSOC part would > be ensuring the legacy code works through PDO with as little change as > possible. By the time the GSOC code was plugged into core, core would no longer support PHP4 (PDO is PHP5 only). > >> On a similar topic, we could look at a GSOC program to change up our >> template library. It's a bit silly that we still don't have compiled >> templates (to the detriment of our performance). Joe's work could be >> used as a basis or the student could look at implementing an existing >> template library (preferably one that could be backward compatible >> with existing templates). > > Or you could just ask me to write it. Ben said he was going to put in > my change to allow "alternate" template engines. Once that gets in, I > promised to release a plugin containing my template library. The > current version on my harddrive contain IF/ELSE processing, LOOPs over > arrays and database, better block handling, fully backward compatible > with the phplib library, and can be cached to disk or memcache > (although I need to reinstall memcache since my last computer rebuild). Oh, it also has a test suite. > >> These might both be too big for a GSOC project, but worth thinking about? > > Most likely. > >> Finally, many may not remember, but years and years ago (2002 or >> 2003) I pushed a big set of patches to improve page load performance. >> If I recall correctly, I eliminated (through combination or caching) >> a bunch of SQL queries, cleaned up PHP code (including getting rid of >> some recursion), and completely rewrote the comment display code. >> Doing something similar again today as a GSOC project could be >> beneficial to Geeklog. I hadn't brought this up before because this >> is an awfully non-specific task. I'm not sure it will fit well all >> that well into GSOC project. Any thoughts? > > And I did the same thing 2007. I still have a bunch of diffs I like to > apply to lib-security and lib-common because it hits the database far > too many times. I tried to sneak a couple of those into the socnet > changes that still aren't released. If I thought the patches would be > applied, I'd make feature requests and post patches. But since there's no track record there, I don't do it. > > Want to reduce Geeklog's memory footprint? Compartmentalize the core functions: > > In public_html/search.php: > define('INCL_SEARCH',1); // yes, before the include, it is safe > include 'lib-common.php'; > > In every plugin/function.inc: > if (defined('INCL_SEARCH')) include $plugin_path . 'search.inc'; > > And in search.inc, each plugin puts all the search related plugin_ functions. > > Repeat this for most of the global php files: comment, search, user, > usersettings, stats!!, submit, trackback/pingback, ?etc. and you will > reduce the load time of all pages. > > I've also been working on lib-smallcommon. A drop-in replacement for > lib-common that can be used in AJAX calls that don't need most of the > COM_ library. The code is just sitting on my hard drive since Geeklog 1.4.1 going out of date. > Geeklog is not a good foundation for "web 2.0" apps as it loads the > moon to deliver cosmic motes. > > > > > _______________________________________________ > 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 Fri Mar 4 09:11:24 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Mar 2011 09:11:24 -0500 Subject: [geeklog-devel] How to delete a patch In-Reply-To: References: Message-ID: <006101cbda76$0c2d42c0$2487c840$@cogeco.net> You could just upload the new file and just include a comment saying use the latest file as a patch. From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of dilantha silva Sent: March-04-11 3:19 AM To: Geeklog Development Subject: [geeklog-devel] How to delete a patch Hi All, Can anyone please tell my how can i delete a patch in the bug tracker which is uploaded by myself. because i accidentally uploaded a patch with a bug and now i want to replace it with the new patch. Thanks in advance. -- Regards, Dilantha Silva, http://twitter.com/dilanthasilva | http://www.linkedin.com/in/dilanthasilva| https://launchpad.net/~dilantha -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Fri Mar 4 09:22:42 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Mar 2011 09:22:42 -0500 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: <606420.7661.qm@web31408.mail.mud.yahoo.com> References: <606420.7661.qm@web31408.mail.mud.yahoo.com> Message-ID: <006601cbda77$9f9f4610$deddd230$@cogeco.net> >> Or you could just ask me to write it. Ben said he was going to put in my change to allow "alternate" template engines. Once that gets in, I promised to release a plugin containing my template library. The current version on >> >> my harddrive contain IF/ELSE processing, LOOPs over arrays and database, better block handling, fully backward compatible with the phplib library, and can be cached to disk or memcache (although I need to reinstall >> >> >> memcache since my last computer rebuild). Oh, it also has a test suite. Hey Joe, I was still planning to put it in. You mentioned that you were probably not going to start until this spring so I was going to wait until you started. >>And I did the same thing 2007. I still have a bunch of diffs I like to apply to lib-security and lib-common because it hits the database far too many times. I tried to sneak a couple of those into the socnet changes that still aren't >>released. If I thought the patches would be applied, I'd make feature requests and post patches. But since there's no track record there, I don't do it. I would like to start to keep more on top of patches. If they make sense, Move Geeklog forward and are complete I have no problem adding them in. (If it is a major change obviously it should be discussed on the mailing list) >>Want to reduce Geeklog's memory footprint? Compartmentalize the core functions: In public_html/search.php: define('INCL_SEARCH',1); // yes, before the include, it is safe include 'lib-common.php'; In every plugin/function.inc: if (defined('INCL_SEARCH')) include $plugin_path . 'search.inc'; >>And in search.inc, each plugin puts all the search related plugin_ functions. >>Repeat this for most of the global php files: comment, search, user, usersettings, stats!!, submit, trackback/pingback, etc. and you will reduce the load time of all pages. That seems like a good way to do it. The problem is getting someone to sit down to do maintenance stuff like this :-) Tom _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From jmucchiello at yahoo.com Fri Mar 4 10:14:02 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Fri, 4 Mar 2011 07:14:02 -0800 (PST) Subject: [geeklog-devel] more GSoC project ideas Message-ID: <868794.8159.qm@web31405.mail.mud.yahoo.com> >>> Or you could just ask me to write it. Ben said he was going to put in Shortly after I mailed it I went "Ben? No, Tom, Arrgggh" But I figured you two would figure it out. :-) > Hey Joe, I was still planning to put it in. You mentioned that you were > probably not going to start until this spring so I was going to wait until > you started. I have it started. I'm writing it somewhat test-driven to make sure there are tests when I'm done. But I'd still like to see the patch made before 1.8 so that plugins can be adapted to the COM_newTemplate function. > I would like to start to keep more on top of patches. If they make sense, > Move Geeklog forward and are complete I have no problem adding them in. > (If > it is a major change obviously it should be discussed on the mailing list) Once the socnet patch is made I'll see if there's anything else in lib-security to patch to remove redundant SQL. >>>Want to reduce Geeklog's memory footprint? Compartmentalize the core > functions: > > That seems like a good way to do it. The problem is getting someone to sit > down to do maintenance stuff like this :-) I'd do it if I thought it would be committed. The problem with me doing it is "nightly" can be a stable for weeks and then gets a flurry of hits. Depending on when the patch is uploaded, merging can be easy or hard. Here's my short list of projects like this that I'd love to tackle: * Split lib-common into a small bootstrap (loads everything, common stuff like COM_isAnonUser, COM_getUserName) file and lib-html (block stuff, header/footer, etc). * add defines to core functionality to reduce memory footprint * Create a SEARCH_newResponder function that currently would return "new plugin". Then next version rename the plugin.class.php plugin class to "search_object" or "plugin_search" or "searcher" anything but plugin * Move $LANG* into functions: Normal: LANG('core1',23), With positional substitution: LANG('plg','wrong_ver','1.7.1',$plugin_version) The latter two I haven't really started. From websitemaster at cogeco.net Fri Mar 4 15:40:39 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 4 Mar 2011 15:40:39 -0500 Subject: [geeklog-devel] Geeklog New Scripts Class Message-ID: <005001cbdaac$6c46cb00$44d46100$@cogeco.net> Hi All, I just pushed an update that adds a script class to Geeklog. This scripts class is meant to handle all CSS files and JavaScript in Geeklog as we move forward. It is pretty much complete but will probably need some tweaking here and there. I have also updated Geeklog Core to use this new class. Further work needs to be done (like with the plugins) but for now the advance editor for Comments and Articles uses the new class along with the Configuration and My Account page. This also means in the header.thml file, css_url and advanced_editor template variables are not needed any more. JavaScript in general also needs a bit of cleanup in Geeklog which I hope to get to in the future. Things like common.js is always loaded. This now doesn't have to be the case with the new Scripts class but I have not taken the time yet to find all the spots that use the functions in this file. When I do (or someone else) all they would have to do is tell it to load when needed in the php code. Here are some highlights of the class: - When the class is used, only the JavaScript and CSS files that are needed will load - Admin can specify to use Google's CDN files for jQuery - Class will fall back and use Google's CDN files if jQuery files missing from Geeklog - Will do away with inline scripting (ie scripts in template files) as you will now pass the required Javascript to the class - Can specify to load JavaScript in header or footer (defaults to footer and jQuery always loads in the footer) - Possible future feature includes Caching/Compressing of regularly included JavaScript Files and CSS files (hence the unused constant variable in some of the classes functions) (As I am writing this I just realized I forgot to add in the config option in the Configuration to enable the use of Google's CDN files, I will push this change later this week) The class is set near the beginning of lib-common.php as $_SCRIPTS. It uses the template variable plg_headercode in COM_SiteHeader to put information in the header and COM_SiteFooter with plg_footercode to put JavaScript in the footer. Obviously all your JavaScript code (and CSS files) needs to be set in the class before COM_SiteHeader is run (at least for the CSS files and any JavaScript in the header). All JavaScript must be set by the time you call COM_SiteFooter (this shouldn't be a problem since this is one of the last functions you should be calling anyways on a page). So how do you use the new class? To pass in some JavaScript code and a JavaScript file to the footer you would do something like so: // Add JavaScript $js = 'geeklogEditorBasePath = "' . $_CONF['site_url'] . '/fckeditor/";'; $_SCRIPTS->setJavaScript($js, true); $_SCRIPTS->setJavaScriptFile('submitcomment_fckeditor', '/javascript/submitcomment_fckeditor.js'); Or if you wanted to tell Geeklog to include a jQuery library $_SCRIPTS->setJavaScriptLibrary('jquery'); Or to use a widget of the jquery ui plugin $_SCRIPTS->setJavaScriptLibrary('jquery.ui.autocomplete'); If you tell the script to use a widget there is no need to tell the Scripts class to load jQuery as it will automatically add it in. To add a CSS file you would do something like this $this->setCSSFile('theme', $theme_path . '/style.css'); If JavaScript is included in any page a bunch of Core JavaScript variables will automatically be inserted for use by any JavaScript code that needs them. These variables are geeklogSiteUrl, geeklogLayoutUrl, geeklogAdminUrl and geeklogThemeName. Finally, the order of placement for JavaScript in the footer is 1. Core JavaScript variables 2. JavaScript Library files (jQuery, etc..) 3. JavaScript Code (from setJavaScript) 4. JavaScript Files (from setJavaScriptFile) Thanks Tom From dilantha.tyrant at gmail.com Fri Mar 4 22:58:28 2011 From: dilantha.tyrant at gmail.com (dilantha silva) Date: Sat, 5 Mar 2011 09:28:28 +0530 Subject: [geeklog-devel] How to delete a patch In-Reply-To: <006101cbda76$0c2d42c0$2487c840$@cogeco.net> References: <006101cbda76$0c2d42c0$2487c840$@cogeco.net> Message-ID: Hi Tom, I thought it might be possible to delete the previous unwanted patches to make it more clean. Thanks for the idea. On Fri, Mar 4, 2011 at 7:41 PM, Tom wrote: > You could just upload the new file and just include a comment saying use > the latest file as a patch. > > > > > > > > *From:* geeklog-devel-bounces at lists.geeklog.net [mailto: > geeklog-devel-bounces at lists.geeklog.net] *On Behalf Of *dilantha silva > *Sent:* March-04-11 3:19 AM > *To:* Geeklog Development > *Subject:* [geeklog-devel] How to delete a patch > > > > Hi All, > > Can anyone please tell my how can i delete a patch in the bug tracker which > is uploaded by myself. because i accidentally uploaded a patch with a bug > and now i want to replace it with the new patch. Thanks in advance. > > -- > Regards, > > Dilantha Silva, > http://twitter.com/dilanthasilva | > http://www.linkedin.com/in/dilanthasilva| > https://launchpad.net/~dilantha > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > -- Regards, Dilantha Silva, http://twitter.com/dilanthasilva | http://www.linkedin.com/in/dilanthasilva| https://launchpad.net/~dilantha -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sat Mar 5 09:09:08 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 5 Mar 2011 15:09:08 +0100 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <005801cbd3c1$da6d82f0$8f4888d0$@cogeco.net> References: <005801cbd3c1$da6d82f0$8f4888d0$@cogeco.net> Message-ID: Tom wrote: > Well let's not drop the SPAMX one until we have flushed out some other > ideas. :-) Okay, I rewrote the Spam-X project proposal again for the third year in a row. There's a bunch of thoughts regarding the install script on the "brainstorming" page, but they don't make for a coherent project (and most of them are small changes). Any further ideas to maybe make a project out of those? Regarding the DB abstraction layer: Ignoring the question about which one to pick, the most obvious consequence is that we would have to maintain two layers then: the new one and the old one. Obviously, all those legacy plugins with no current maintainer should continue working. Are these DB abstractions layers even supporting this parallel mode? What if they're caching something that is then changed behind their back by some legacy code that uses the old API? If anyone thinks these sorts of problems can be solved, then please go ahead and write up a project description. bye, Dirk From Randy.Kolenko at nextide.ca Sat Mar 5 09:16:05 2011 From: Randy.Kolenko at nextide.ca (Randy Kolenko) Date: Sat, 5 Mar 2011 09:16:05 -0500 Subject: [geeklog-devel] Our application for GSoC 2011 Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F3838E8@nex-pluto.nextide.ca> > Regarding the DB abstraction layer: Ignoring the question about which > one to pick, the most obvious consequence is that we would have to > maintain two layers then: the new one and the old one. Obviously, all > those legacy plugins with no current maintainer should continue > working. Are these DB abstractions layers even supporting this parallel > mode? What if they're caching something that is then changed behind > their back by some legacy code that uses the old API? Could this not be accomplished by actually rolling a Geeklog v2.0 release that would support PDO? 1.x branch would support the current DBs. It's been years since GL2 was even mentioned and finally renamed. Why not just go with Geeklog 2.0 for any new major caching and db enhancements? From websitemaster at cogeco.net Sat Mar 5 09:31:40 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Mar 2011 09:31:40 -0500 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <063B8B70CB9DA141B2FC1DB483561B9F3838E8@nex-pluto.nextide.ca> References: <063B8B70CB9DA141B2FC1DB483561B9F3838E8@nex-pluto.nextide.ca> Message-ID: <001b01cbdb42$0a9a9b20$1fcfd160$@cogeco.net> >>Why not just go with Geeklog 2.0 for any new major caching and db enhancements? While I would hate to cut off older plugins I think this would be a better decision than supporting 2 layers. We would give the community plenty of warning and then do something similar as we did when moving from PHP4 to PHP5. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Randy Kolenko Sent: March-05-11 9:16 AM To: Geeklog Development Subject: Re: [geeklog-devel] Our application for GSoC 2011 > Regarding the DB abstraction layer: Ignoring the question about which > one to pick, the most obvious consequence is that we would have to > maintain two layers then: the new one and the old one. Obviously, all > those legacy plugins with no current maintainer should continue > working. Are these DB abstractions layers even supporting this parallel > mode? What if they're caching something that is then changed behind > their back by some legacy code that uses the old API? Could this not be accomplished by actually rolling a Geeklog v2.0 release that would support PDO? 1.x branch would support the current DBs. It's been years since GL2 was even mentioned and finally renamed. Why not just go with Geeklog 2.0 for any new major caching and db enhancements? _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sat Mar 5 09:43:20 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Mar 2011 09:43:20 -0500 Subject: [geeklog-devel] more GSoC project ideas In-Reply-To: <868794.8159.qm@web31405.mail.mud.yahoo.com> References: <868794.8159.qm@web31405.mail.mud.yahoo.com> Message-ID: <001c01cbdb43$ac3494d0$049dbe70$@cogeco.net> >> I have it started. I'm writing it somewhat test-driven to make sure there are tests when I'm done. But I'd still like to see the patch made before 1.8 so that plugins can be adapted to the COM_newTemplate function. Great. Did you want to double check your patch then? Also once the plugin reaches a stable state I can help with some testing. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: March-04-11 10:14 AM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] more GSoC project ideas >>> Or you could just ask me to write it. Ben said he was going to put >>> in Shortly after I mailed it I went "Ben? No, Tom, Arrgggh" But I figured you two would figure it out. :-) > Hey Joe, I was still planning to put it in. You mentioned that you > were probably not going to start until this spring so I was going to > wait until you started. I have it started. I'm writing it somewhat test-driven to make sure there are tests when I'm done. But I'd still like to see the patch made before 1.8 so that plugins can be adapted to the COM_newTemplate function. > I would like to start to keep more on top of patches. If they make > sense, Move Geeklog forward and are complete I have no problem adding them in. > (If > it is a major change obviously it should be discussed on the mailing > list) Once the socnet patch is made I'll see if there's anything else in lib-security to patch to remove redundant SQL. >>>Want to reduce Geeklog's memory footprint? Compartmentalize the core > functions: > > That seems like a good way to do it. The problem is getting someone to > sit down to do maintenance stuff like this :-) I'd do it if I thought it would be committed. The problem with me doing it is "nightly" can be a stable for weeks and then gets a flurry of hits. Depending on when the patch is uploaded, merging can be easy or hard. Here's my short list of projects like this that I'd love to tackle: * Split lib-common into a small bootstrap (loads everything, common stuff like COM_isAnonUser, COM_getUserName) file and lib-html (block stuff, header/footer, etc). * add defines to core functionality to reduce memory footprint * Create a SEARCH_newResponder function that currently would return "new plugin". Then next version rename the plugin.class.php plugin class to "search_object" or "plugin_search" or "searcher" anything but plugin * Move $LANG* into functions: Normal: LANG('core1',23), With positional substitution: LANG('plg','wrong_ver','1.7.1',$plugin_version) The latter two I haven't really started. _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Sat Mar 5 13:29:21 2011 From: cordiste at free.fr (cordiste) Date: Sat, 5 Mar 2011 19:29:21 +0100 Subject: [geeklog-devel] Geeklog New Scripts Class In-Reply-To: <005001cbdaac$6c46cb00$44d46100$@cogeco.net> References: <005001cbdaac$6c46cb00$44d46100$@cogeco.net> Message-ID: Thank you Tom, this will be a nice feature. Is this will be available with geeklog 1.8 ? Ben 2011/3/4 Tom : > Hi All, > > I just pushed an update that adds a script class to Geeklog. This scripts > class is meant to handle all CSS files and JavaScript in Geeklog as we move > forward. It is pretty much complete but will probably need some tweaking > here and there. > > I have also updated Geeklog Core to use this new class. Further work needs > to be done (like with the plugins) but for now the advance editor for > Comments and Articles uses the new class along with the Configuration and My > Account page. This also means in the header.thml file, css_url and > advanced_editor template variables are not needed any more. JavaScript in > general also needs a bit of cleanup in Geeklog which I hope to get to in the > future. Things like common.js is always loaded. This now doesn't have to be > the case with the new Scripts class but I have not taken the time yet to > find all the spots that use the functions in this file. When I do (or > someone else) all they would have to do is tell it to load when needed in > the php code. > > Here are some highlights of the class: > > - ? ? ? When the class is used, only the JavaScript and CSS files that are > needed will load > - ? ? ? Admin can specify to use Google's CDN files for jQuery > - ? ? ? Class will fall back and use Google's CDN files if jQuery files > missing from Geeklog > - ? ? ? Will do away with inline scripting (ie scripts in template files) as > you will now pass the required Javascript to the class > - ? ? ? Can specify to load JavaScript in header or footer (defaults to > footer and jQuery always loads in the footer) > - ? ? ? Possible future feature includes Caching/Compressing of regularly > included JavaScript Files and CSS files (hence the unused constant variable > in some of the classes functions) > > (As I am writing this I just realized I forgot to add in the config option > in the Configuration to enable the use of Google's CDN files, I will push > this change later this week) > > The class is set near the beginning of lib-common.php as $_SCRIPTS. It uses > the template variable plg_headercode in COM_SiteHeader to put information in > the header and COM_SiteFooter with plg_footercode to put JavaScript in the > footer. Obviously all your JavaScript code (and CSS files) needs to be set > in the class before COM_SiteHeader is run (at least for the CSS files and > any JavaScript in the header). All JavaScript must be set by the time you > call COM_SiteFooter (this shouldn't be a problem since this is one of the > last functions you should be calling anyways on a page). > > So how do you use the new class? > > To pass in some JavaScript code and a JavaScript file to the footer you > would do something like so: > > ? ? ? ? ? ? ? ?// Add JavaScript > ? ? ? ? ? ? ? ?$js = 'geeklogEditorBasePath = "' . $_CONF['site_url'] . > '/fckeditor/";'; > ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScript($js, true); > ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScriptFile('submitcomment_fckeditor', > '/javascript/submitcomment_fckeditor.js'); > > > Or if you wanted to tell Geeklog to include a jQuery library > > ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery'); > > Or to use a widget of the jquery ui plugin > > ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery.ui.autocomplete'); > > If you tell the script to use a widget there is no need to tell the Scripts > class to load jQuery as it will automatically add it in. > > To add a CSS file you would do something like this > > ? ? ? ?$this->setCSSFile('theme', $theme_path . '/style.css'); > > If JavaScript is included in any page a bunch of Core JavaScript variables > will automatically be inserted for use by any JavaScript code that needs > them. These variables are geeklogSiteUrl, geeklogLayoutUrl, geeklogAdminUrl > and geeklogThemeName. > > Finally, the order of placement for JavaScript in the footer is > > 1. Core JavaScript variables > 2. JavaScript Library files (jQuery, etc..) > 3. JavaScript Code (from setJavaScript) > 4. JavaScript Files (from setJavaScriptFile) > > > Thanks > > Tom > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From jmucchiello at yahoo.com Sat Mar 5 14:35:07 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Sat, 5 Mar 2011 11:35:07 -0800 (PST) Subject: [geeklog-devel] Our application for GSoC 2011 Message-ID: <562259.68104.qm@web31401.mail.mud.yahoo.com> > Regarding the DB abstraction layer: Ignoring the question about which one > to pick, the most obvious consequence is that we would have to maintain > two layers then: the new one and the old one. Obviously, all those legacy > plugins with no current maintainer should continue working. Are these DB > abstractions layers even supporting this parallel mode? What if they're > caching something that is then changed behind their back by some legacy > code that uses the old API? My idea doesn't work? You create a pdo.class.php that implements the exist DB class. In the configuration, you add a drop down item: MySQL, PostgreSQL, MS SQL, and PDO. As long as pdo.class.php implement the existing interface, everything should continue working including older plugins. After that, you declare Geeklog 1.9 core will drop independent use of mysql.classs.php, pgsql.class.php and mssql.class.php. And core 1.9 would start using the PDO library directly for new code. This gives Geeklog access to bind parameters finally. Old plugins would continue working through the legacy library. I suspect you are thinking about using something kind of ORM. Don't. Retrofitting an ORM onto existing SQL is a pain. Joe From websitemaster at cogeco.net Sat Mar 5 15:06:13 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 5 Mar 2011 15:06:13 -0500 Subject: [geeklog-devel] Geeklog New Scripts Class In-Reply-To: References: <005001cbdaac$6c46cb00$44d46100$@cogeco.net> Message-ID: <005301cbdb70$c75270c0$55f75240$@cogeco.net> Thanks and yes it will. I was actually going to ask you if you could update one of your plugins that use jQuery to use the new scripts class just to help me weed out any potential bugs. Hmmm, I just thought of an issue. Plugins that use JavaScript and not the new Scripts class should be fine since most of the JavaScript for plugins are based on their own JavaScript files. I see a problem happening though where jQuery could be set twice if the Scripts class sets it and then an older plugin sets it using their own copy. Should we just assume older plugins that use jQuery will need to be updated to be used with 1.8.0 OR Should I add in a config option to disable setting jQuery by the Scripts class? If a config option is set to true then the plugin will have to make sure jQuery is set all the time and is the proper version. The config option doesn't really fix all cases so I wonder if we should just go with option 1. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste Sent: March-05-11 1:29 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog New Scripts Class Thank you Tom, this will be a nice feature. Is this will be available with geeklog 1.8 ? Ben 2011/3/4 Tom : > Hi All, > > I just pushed an update that adds a script class to Geeklog. This > scripts class is meant to handle all CSS files and JavaScript in > Geeklog as we move forward. It is pretty much complete but will > probably need some tweaking here and there. > > I have also updated Geeklog Core to use this new class. Further work > needs to be done (like with the plugins) but for now the advance > editor for Comments and Articles uses the new class along with the > Configuration and My Account page. This also means in the header.thml > file, css_url and advanced_editor template variables are not needed > any more. JavaScript in general also needs a bit of cleanup in Geeklog > which I hope to get to in the future. Things like common.js is always > loaded. This now doesn't have to be the case with the new Scripts > class but I have not taken the time yet to find all the spots that use > the functions in this file. When I do (or someone else) all they would > have to do is tell it to load when needed in the php code. > > Here are some highlights of the class: > > - ? ? ? When the class is used, only the JavaScript and CSS files that > are needed will load > - ? ? ? Admin can specify to use Google's CDN files for jQuery > - ? ? ? Class will fall back and use Google's CDN files if jQuery > files missing from Geeklog > - ? ? ? Will do away with inline scripting (ie scripts in template > files) as you will now pass the required Javascript to the class > - ? ? ? Can specify to load JavaScript in header or footer (defaults > to footer and jQuery always loads in the footer) > - ? ? ? Possible future feature includes Caching/Compressing of > regularly included JavaScript Files and CSS files (hence the unused > constant variable in some of the classes functions) > > (As I am writing this I just realized I forgot to add in the config > option in the Configuration to enable the use of Google's CDN files, I > will push this change later this week) > > The class is set near the beginning of lib-common.php as $_SCRIPTS. It > uses the template variable plg_headercode in COM_SiteHeader to put > information in the header and COM_SiteFooter with plg_footercode to > put JavaScript in the footer. Obviously all your JavaScript code (and > CSS files) needs to be set in the class before COM_SiteHeader is run > (at least for the CSS files and any JavaScript in the header). All > JavaScript must be set by the time you call COM_SiteFooter (this > shouldn't be a problem since this is one of the last functions you should be calling anyways on a page). > > So how do you use the new class? > > To pass in some JavaScript code and a JavaScript file to the footer > you would do something like so: > > ? ? ? ? ? ? ? ?// Add JavaScript > ? ? ? ? ? ? ? ?$js = 'geeklogEditorBasePath = "' . $_CONF['site_url'] . > '/fckeditor/";'; > ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScript($js, true); > ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScriptFile('submitcomment_fckeditor', > '/javascript/submitcomment_fckeditor.js'); > > > Or if you wanted to tell Geeklog to include a jQuery library > > ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery'); > > Or to use a widget of the jquery ui plugin > > ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery.ui.autocomplete'); > > If you tell the script to use a widget there is no need to tell the > Scripts class to load jQuery as it will automatically add it in. > > To add a CSS file you would do something like this > > ? ? ? ?$this->setCSSFile('theme', $theme_path . '/style.css'); > > If JavaScript is included in any page a bunch of Core JavaScript > variables will automatically be inserted for use by any JavaScript > code that needs them. These variables are geeklogSiteUrl, > geeklogLayoutUrl, geeklogAdminUrl and geeklogThemeName. > > Finally, the order of placement for JavaScript in the footer is > > 1. Core JavaScript variables > 2. JavaScript Library files (jQuery, etc..) 3. JavaScript Code (from > setJavaScript) 4. JavaScript Files (from setJavaScriptFile) > > > Thanks > > 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 cordiste at free.fr Sat Mar 5 17:40:05 2011 From: cordiste at free.fr (cordiste) Date: Sat, 5 Mar 2011 23:40:05 +0100 Subject: [geeklog-devel] Geeklog New Scripts Class In-Reply-To: <005301cbdb70$c75270c0$55f75240$@cogeco.net> References: <005001cbdaac$6c46cb00$44d46100$@cogeco.net> <005301cbdb70$c75270c0$55f75240$@cogeco.net> Message-ID: Tom, To avoid twice and more jquery loadings, I built all my plugins using jquery like this: //jQuery $jquery = ''; if(!defined('JQUERY')) { $jquery .= ' ' . LB; $jquery .= ' '. LB; define('JQUERY', 'true'); } $header->set_var( 'jquery', $jquery); So we could make something like this and ask to author to update their plugins. Ben 2011/3/5 Tom : > Thanks and yes it will. > > I was actually going to ask you if you could update one of your plugins that > use jQuery to use the new scripts class just to help me weed out any > potential bugs. > > Hmmm, I just thought of an issue. Plugins that use JavaScript and not the > new Scripts class should be fine since most of the JavaScript for plugins > are based on their own JavaScript files. I see a problem happening though > where > jQuery could be set twice if the Scripts class sets it and then an older > plugin sets it using their own copy. > > Should we just assume older plugins that use jQuery will need to be updated > to be used with 1.8.0 > > OR > > Should I add in a config option to disable setting jQuery by the Scripts > class? If a config option is set to true then the plugin will have to make > sure jQuery is set all the time and is the proper version. The config option > doesn't really fix all cases so I wonder if we should just go with option 1. > > Tom > > > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste > Sent: March-05-11 1:29 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog New Scripts Class > > Thank you Tom, this will be a nice feature. > > Is this will be available with geeklog 1.8 ? > > Ben > > 2011/3/4 Tom : >> Hi All, >> >> I just pushed an update that adds a script class to Geeklog. This >> scripts class is meant to handle all CSS files and JavaScript in >> Geeklog as we move forward. It is pretty much complete but will >> probably need some tweaking here and there. >> >> I have also updated Geeklog Core to use this new class. Further work >> needs to be done (like with the plugins) but for now the advance >> editor for Comments and Articles uses the new class along with the >> Configuration and My Account page. This also means in the header.thml >> file, css_url and advanced_editor template variables are not needed >> any more. JavaScript in general also needs a bit of cleanup in Geeklog >> which I hope to get to in the future. Things like common.js is always >> loaded. This now doesn't have to be the case with the new Scripts >> class but I have not taken the time yet to find all the spots that use >> the functions in this file. When I do (or someone else) all they would >> have to do is tell it to load when needed in the php code. >> >> Here are some highlights of the class: >> >> - ? ? ? When the class is used, only the JavaScript and CSS files that >> are needed will load >> - ? ? ? Admin can specify to use Google's CDN files for jQuery >> - ? ? ? Class will fall back and use Google's CDN files if jQuery >> files missing from Geeklog >> - ? ? ? Will do away with inline scripting (ie scripts in template >> files) as you will now pass the required Javascript to the class >> - ? ? ? Can specify to load JavaScript in header or footer (defaults >> to footer and jQuery always loads in the footer) >> - ? ? ? Possible future feature includes Caching/Compressing of >> regularly included JavaScript Files and CSS files (hence the unused >> constant variable in some of the classes functions) >> >> (As I am writing this I just realized I forgot to add in the config >> option in the Configuration to enable the use of Google's CDN files, I >> will push this change later this week) >> >> The class is set near the beginning of lib-common.php as $_SCRIPTS. It >> uses the template variable plg_headercode in COM_SiteHeader to put >> information in the header and COM_SiteFooter with plg_footercode to >> put JavaScript in the footer. Obviously all your JavaScript code (and >> CSS files) needs to be set in the class before COM_SiteHeader is run >> (at least for the CSS files and any JavaScript in the header). All >> JavaScript must be set by the time you call COM_SiteFooter (this >> shouldn't be a problem since this is one of the last functions you should > be calling anyways on a page). >> >> So how do you use the new class? >> >> To pass in some JavaScript code and a JavaScript file to the footer >> you would do something like so: >> >> ? ? ? ? ? ? ? ?// Add JavaScript >> ? ? ? ? ? ? ? ?$js = 'geeklogEditorBasePath = "' . $_CONF['site_url'] . >> '/fckeditor/";'; >> ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScript($js, true); >> ? ? ? ? ? ? ? ?$_SCRIPTS->setJavaScriptFile('submitcomment_fckeditor', >> '/javascript/submitcomment_fckeditor.js'); >> >> >> Or if you wanted to tell Geeklog to include a jQuery library >> >> ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery'); >> >> Or to use a widget of the jquery ui plugin >> >> ? ? ? ?$_SCRIPTS->setJavaScriptLibrary('jquery.ui.autocomplete'); >> >> If you tell the script to use a widget there is no need to tell the >> Scripts class to load jQuery as it will automatically add it in. >> >> To add a CSS file you would do something like this >> >> ? ? ? ?$this->setCSSFile('theme', $theme_path . '/style.css'); >> >> If JavaScript is included in any page a bunch of Core JavaScript >> variables will automatically be inserted for use by any JavaScript >> code that needs them. These variables are geeklogSiteUrl, >> geeklogLayoutUrl, geeklogAdminUrl and geeklogThemeName. >> >> Finally, the order of placement for JavaScript in the footer is >> >> 1. Core JavaScript variables >> 2. JavaScript Library files (jQuery, etc..) 3. JavaScript Code (from >> setJavaScript) 4. JavaScript Files (from setJavaScriptFile) >> >> >> Thanks >> >> 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 > > From dilantha.tyrant at gmail.com Sun Mar 6 00:57:56 2011 From: dilantha.tyrant at gmail.com (dilantha silva) Date: Sun, 6 Mar 2011 11:27:56 +0530 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: References: <005801cbd3c1$da6d82f0$8f4888d0$@cogeco.net> Message-ID: On Sat, Mar 5, 2011 at 7:39 PM, Dirk Haun wrote: > Tom wrote: > > > Well let's not drop the SPAMX one until we have flushed out some other > > ideas. :-) > > Okay, I rewrote the Spam-X project proposal again for the third year in a > row. > > There's a bunch of thoughts regarding the install script on the > "brainstorming" page, but they don't make for a coherent project (and most > of them are small changes). Any further ideas to maybe make a project out of > those? > > Regarding the DB abstraction layer: Ignoring the question about which one > to pick, the most obvious consequence is that we would have to maintain two > layers then: the new one and the old one. Obviously, all those legacy > plugins with no current maintainer should continue working. Are these DB > abstractions layers even supporting this parallel mode? What if they're > caching something that is then changed behind their back by some legacy code > that uses the old API? > > Yes. I think this is possible. I have done this before using doctrine ORM for some other purposes.For example you can use existing DSN to create PDO connection and new modules will use that PDO connection to access the DB while older plugins will continue working with out any problem. If anyone thinks these sorts of problems can be solved, then please go ahead > and write up a project description. > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -- Regards, Dilantha Silva, http://twitter.com/dilanthasilva | http://www.linkedin.com/in/dilanthasilva| https://launchpad.net/~dilantha -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Sun Mar 6 13:35:42 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 06 Mar 2011 19:35:42 +0100 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: References: Message-ID: <20110306193542.10035g749hadwe0w@webmail.df.eu> Just a heads-up: I was planning to send in our GSoC application today, but my computer's hard drive chose this day to die. Work permitting, I'll try it from work tomorrow. May take me another day or two before I'm fully online again. So please bear with me while I try to do things from my iPad ... bye, Dirk -- http://www.themobilepresenter.com/ From dirk at haun-online.de Sun Mar 6 13:36:02 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 06 Mar 2011 19:36:02 +0100 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: References: Message-ID: <20110306193602.20507fxvza55odoo@webmail.df.eu> Just a heads-up: I was planning to send in our GSoC application today, but my computer's hard drive chose this day to die. Work permitting, I'll try it from work tomorrow. May take me another day or two before I'm fully online again. So please bear with me while I try to do things from my iPad ... bye, Dirk -- http://www.themobilepresenter.com/ From n.prasath.002 at gmail.com Mon Mar 7 06:26:12 2011 From: n.prasath.002 at gmail.com (prasath nadarajah) Date: Mon, 7 Mar 2011 16:56:12 +0530 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <20110306193602.20507fxvza55odoo@webmail.df.eu> References: <20110306193602.20507fxvza55odoo@webmail.df.eu> Message-ID: Hi, I,m interested in providing metaweblog API support for geeklog?? Most of the web/mobile clients supports metaweblog API. I intend to support the basic method for publishing/retrieving content what you think?? On Mon, Mar 7, 2011 at 12:06 AM, Dirk Haun wrote: > Just a heads-up: I was planning to send in our GSoC application today, but > my computer's hard drive chose this day to die. Work permitting, I'll try it > from work tomorrow. May take me another day or two before I'm fully online > again. So please bear with me while I try to do things from my iPad ... > > bye, Dirk > > -- > http://www.themobilepresenter.com/ > > > > _______________________________________________ > 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 dirk at haun-online.de Mon Mar 7 16:31:18 2011 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 7 Mar 2011 22:31:18 +0100 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: References: <20110306193602.20507fxvza55odoo@webmail.df.eu> Message-ID: prasath nadarajah wrote: > Hi, > I,m interested in providing metaweblog API support for geeklog?? > Most of the web/mobile clients supports metaweblog API. > I intend to support the basic method for publishing/retrieving content what you think?? Geeklog already uses AtomPub which provides the same functionality. Unfortunately, AtomPub never really caught on. So there may be a point in implementing a second protocol, if it's one that is more popular. Our webservices API was written with that in mind, actually. See http://wiki.geeklog.net/index.php/Using_the_Webservices bye, Dirk -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Tue Mar 8 07:43:53 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 08 Mar 2011 13:43:53 +0100 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <20110306193542.10035g749hadwe0w@webmail.df.eu> References: <20110306193542.10035g749hadwe0w@webmail.df.eu> Message-ID: <20110308134353.7315346kit6htncw@webmail.df.eu> > Work permitting, I'll try it from work tomorrow. May take me another > day or two before I'm fully online again. GSoC application sent. Keep fingers crossed until March 18th :) Also: new hard drive installed & backup reinstalled over night. I should re-appear on IRC later today. bye, Dirk http://www.flickr.com/photos/dhaun/5507256544/ From websitemaster at cogeco.net Tue Mar 8 09:09:31 2011 From: websitemaster at cogeco.net (Tom) Date: Tue, 8 Mar 2011 09:09:31 -0500 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <20110308134353.7315346kit6htncw@webmail.df.eu> References: <20110306193542.10035g749hadwe0w@webmail.df.eu> <20110308134353.7315346kit6htncw@webmail.df.eu> Message-ID: <014501cbdd9a$71e842a0$55b8c7e0$@cogeco.net> Crossed! -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: March-08-11 7:44 AM To: Geeklog Development Subject: Re: [geeklog-devel] Our application for GSoC 2011 > Work permitting, I'll try it from work tomorrow. May take me another > day or two before I'm fully online again. GSoC application sent. Keep fingers crossed until March 18th :) Also: new hard drive installed & backup reinstalled over night. I should re-appear on IRC later today. bye, Dirk http://www.flickr.com/photos/dhaun/5507256544/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Tue Mar 8 09:48:47 2011 From: rouslan at placella.com (Rouslan Placella) Date: Tue, 08 Mar 2011 14:48:47 +0000 Subject: [geeklog-devel] Our application for GSoC 2011 In-Reply-To: <014501cbdd9a$71e842a0$55b8c7e0$@cogeco.net> References: <20110306193542.10035g749hadwe0w@webmail.df.eu> <20110308134353.7315346kit6htncw@webmail.df.eu> <014501cbdd9a$71e842a0$55b8c7e0$@cogeco.net> Message-ID: <1299595727.2268.0.camel@roccivic-pc> +1 On Tue, 2011-03-08 at 09:09 -0500, Tom wrote: > Crossed! > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun > Sent: March-08-11 7:44 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Our application for GSoC 2011 > > > Work permitting, I'll try it from work tomorrow. May take me another > > day or two before I'm fully online again. > > GSoC application sent. Keep fingers crossed until March 18th :) > > Also: new hard drive installed & backup reinstalled over night. I should > re-appear on IRC later today. > > bye, Dirk > > http://www.flickr.com/photos/dhaun/5507256544/ > > > > _______________________________________________ > 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 gidraharsh at gmail.com Wed Mar 9 13:18:53 2011 From: gidraharsh at gmail.com (harsh gidra) Date: Wed, 9 Mar 2011 23:48:53 +0530 Subject: [geeklog-devel] GSoC 2011 Message-ID: Hi, I am Harsh Gidra, a UG student from India. I am currently pursuing Bachelor of Technology (B.Tech.) in Information Technology from Malaviya National Institute of Technology Jaipur, India [1] and will graduate in May 2011. I am well versed with HTML, PHP, MySQL, Javascript, jQuery and CakePHP (MVC Paradigm) and have a deep interest in Web Development. I have completed a number of web-based projects using Open Source technologies. I was also associated with an Open Source organization (Limesurvey) last year [2]. Here is my complete resume [3]. I am interested in applying for Geeklog in GSoC 2011. I am done with the 'Beginner's Guide to Programming' [4] and am diving into the source code. I have gone through the ideas list and hope to produce some code snippets/screenshots related to the same very soon. -- [1]. http://en.wikipedia.org/wiki/Malaviya_National_Institute_of_Technology_Jaipur [2]. http://www.ohloh.net/p/limesurvey/contributors/1159641215474 [3]. http://gidraharsh.in/resume/ [4]. http://wiki.geeklog.net/index.php/Beginner%27s_Guide_to_Programming Thanks and regards,Harsh Gidra Department of Computer Engineering Malaviya National Institute of Technology Jaipur-302017 India Website: http://gidraharsh.in IRC Nickname: harsh -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk at haun-online.de Thu Mar 10 16:34:48 2011 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 10 Mar 2011 22:34:48 +0100 Subject: [geeklog-devel] GSoC 2011 In-Reply-To: References: Message-ID: harsh gidra wrote: > I am interested in applying for Geeklog in GSoC 2011. I am done with the 'Beginner's Guide to Programming' [4] and am diving into the source code. I have gone through the ideas list and hope to produce some code snippets/screenshots related to the same very soon. Welcome and thanks. As we're slowly wrapping up 1.8.0 development, we could also need some help in testing that version. That will also be the version students would be working on (assuming that we're accepted as a mentoring organization). I see there are already some bugreports for 1.8.0 in the bugtracker. Thanks and keep them coming! If anyone wants to help testing, you can use the nightly tarball, which is packaged like a regular Geeklog release, or check out from our Mercurial repository. Details on the wiki: http://wiki.geeklog.net/index.php/Installing_from_the_Mercurial_Repository bye, Dirk From dirk at haun-online.de Sat Mar 12 09:08:02 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 12 Mar 2011 15:08:02 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule Message-ID: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Okay, if we want to keep that vague April release date, it's about time we wrap up 1.8.0 development (and avoid further feature creep). Suggested timeline: Feature freeze this coming Monday, March 14. No new features to be added after that date - bugfixes only. Testing and bugfixes (old and new bugs). Beta 1 release on March 27. Further beta or release candidate releases on every following weekend. Switch from beta to rc as soon as there aren't any new bugs (i.e. newly introduced in 1.8.0 or related to new features in 1.8.0) left. Preferred release date: April 17. Does that sound feasible? April 17 may be a bit optimistic, given that I'm at the ACCU Conference from April 12-16. But we should certainly try. bye, Dirk From websitemaster at cogeco.net Sat Mar 12 09:44:41 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 12 Mar 2011 09:44:41 -0500 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Message-ID: <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> Sounds Good. Are we planning to use the OAuth remote service on Geeklog? I hope we do. If so then we will need to create accounts for Geeklog at the OAuth providers. Tom PS Does our host have the PHP extension OPENSLL loaded? -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: March-12-11 9:08 AM To: Geeklog Development Subject: [geeklog-devel] Geeklog 1.8.0 release schedule Okay, if we want to keep that vague April release date, it's about time we wrap up 1.8.0 development (and avoid further feature creep). Suggested timeline: Feature freeze this coming Monday, March 14. No new features to be added after that date - bugfixes only. Testing and bugfixes (old and new bugs). Beta 1 release on March 27. Further beta or release candidate releases on every following weekend. Switch from beta to rc as soon as there aren't any new bugs (i.e. newly introduced in 1.8.0 or related to new features in 1.8.0) left. Preferred release date: April 17. Does that sound feasible? April 17 may be a bit optimistic, given that I'm at the ACCU Conference from April 12-16. But we should certainly try. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sat Mar 12 10:44:01 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 12 Mar 2011 16:44:01 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> Message-ID: Tom wrote: > Are we planning to use the OAuth remote service on Geeklog? I hope we do. I guess so. Which ones should we use? Probably not all 3 of them. Twitter? Facebook? > If so then we will need to create accounts for Geeklog at the OAuth > providers. I'm not on Facebook, so if we were to use that, someone else would have to generate that account. > PS Does our host have the PHP extension OPENSLL loaded? Whoops, good point. --- snip --- openssl OpenSSL support enabled OpenSSL Version OpenSSL 0.9.8k 25 Mar 2009 --- snip --- Looks like it does. bye, Dirk From websitemaster at cogeco.net Sat Mar 12 11:01:56 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 12 Mar 2011 11:01:56 -0500 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> Message-ID: <003e01cbe0ce$cff536f0$6fdfa4d0$@cogeco.net> I would say Facebook for sure. 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: March-12-11 10:44 AM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule Tom wrote: > Are we planning to use the OAuth remote service on Geeklog? I hope we do. I guess so. Which ones should we use? Probably not all 3 of them. Twitter? Facebook? > If so then we will need to create accounts for Geeklog at the OAuth > providers. I'm not on Facebook, so if we were to use that, someone else would have to generate that account. > PS Does our host have the PHP extension OPENSLL loaded? Whoops, good point. --- snip --- openssl OpenSSL support enabled OpenSSL Version OpenSSL 0.9.8k 25 Mar 2009 --- snip --- Looks like it does. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From jmucchiello at yahoo.com Sat Mar 12 16:18:15 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Sat, 12 Mar 2011 13:18:15 -0800 (PST) Subject: [geeklog-devel] Feature Freeze for 1.8.0 Message-ID: <686182.97106.qm@web31405.mail.mud.yahoo.com> Is two days of notice really sufficient? So what made it in? There are 33 "Patches" sitting in "Feedback". They won't make it. The Socnet patch I made last April is still merely "assigned". I'd like to be able to code against those change in core Geeklog. Still waiting. From rouslan at placella.com Sat Mar 12 17:40:04 2011 From: rouslan at placella.com (Rouslan Placella) Date: Sat, 12 Mar 2011 22:40:04 +0000 Subject: [geeklog-devel] Feature Freeze for 1.8.0 In-Reply-To: <686182.97106.qm@web31405.mail.mud.yahoo.com> References: <686182.97106.qm@web31405.mail.mud.yahoo.com> Message-ID: <1299969604.13692.4.camel@roccivic-pc> I agree that the notice is a bit short. I was hoping for a week since I still have to check in the new modified professional_css theme and resolve Feature Request #0001288, which will require a small tweak to the new version control feature in the plugin autoinstall. Rouslan On Sat, 2011-03-12 at 13:18 -0800, Joe Mucchiello wrote: > Is two days of notice really sufficient? > > So what made it in? There are 33 "Patches" sitting in "Feedback". They won't > make it. The Socnet patch I made last April is still merely "assigned". I'd like > to be able to code against those change in core Geeklog. Still waiting. > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sun Mar 13 08:55:15 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 13 Mar 2011 13:55:15 +0100 Subject: [geeklog-devel] Feature Freeze for 1.8.0 In-Reply-To: <1299969604.13692.4.camel@roccivic-pc> References: <686182.97106.qm@web31405.mail.mud.yahoo.com> <1299969604.13692.4.camel@roccivic-pc> Message-ID: <1A56C2A0-246E-45D2-8193-F28932C570E0@haun-online.de> Rouslan Placella wrote: > I agree that the notice is a bit short. I was hoping for a week since I > still have to check in the new modified professional_css theme and > resolve Feature Request #0001288, which will require a small tweak to > the new version control feature in the plugin autoinstall. Right, it's an arbitrary date. I just wanted to draw a line somewhere, to avoid further feature creep. Tom also seems to be struggling with some issues. Let's move it some more days. How about Friday? Btw, what's the plan for professional_css? I thought we would not ship that with 1.8.0, at least not bundled with it. Instead, install it on geeklog.net as an alternative theme to get some more feedback, and possibly offer it as a separate download (which could be a bit of a pain as long as it is work in progress). Tom? bye, Dirk From websitemaster at cogeco.net Sun Mar 13 10:44:53 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 13 Mar 2011 10:44:53 -0400 Subject: [geeklog-devel] Feature Freeze for 1.8.0 In-Reply-To: <1A56C2A0-246E-45D2-8193-F28932C570E0@haun-online.de> References: <686182.97106.qm@web31405.mail.mud.yahoo.com> <1299969604.13692.4.camel@roccivic-pc> <1A56C2A0-246E-45D2-8193-F28932C570E0@haun-online.de> Message-ID: <009401cbe18d$3675a8b0$a360fa10$@cogeco.net> Dirk, Friday sounds good if that is fine with everyone else. Joe, >>So what made it in? There are 33 "Patches" sitting in "Feedback". They won't make it. The Socnet patch I made last April is still merely "assigned". I'd like to be able to code against those change in core Geeklog. Still waiting. We may get some bug patches in but I know I have enough on my plate at the moment (time wise) that I do not want to be responsible for any further new features in 1.8.0. That being said I know you wanted your (and I do too) your patch in for "Want an overridable COM_newTemplate function" http://project.geeklog.net/tracking/view.php?id=1220 If you can update your patch against the current repository and make sure all the core plugins are included then I could apply it. Also if you could keep an eye on any bugs that get reported that the patch could be responsible for (and include fixes) that would be great. Do you think you will be able to have the patch to me before Friday? Regarding the SOCNET patch "Core support of user owned groups desired": http://project.geeklog.net/tracking/view.php?id=1106 As far as I know the SOCNET plugin has had no work done on it since last summer. Therefore I had assumed we wouldn't apply the patch until it got picked up again or someone else needed it. Do you have plans to use it in something else? If others agree and it is needed this patch could get applied but I assume it will need some updating as well. i.e. I am not sure if the patch includes the new table changes in the Geeklog install and upgrade scripts. 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: March-13-11 8:55 AM To: Geeklog Development Subject: Re: [geeklog-devel] Feature Freeze for 1.8.0 Rouslan Placella wrote: > I agree that the notice is a bit short. I was hoping for a week since > I still have to check in the new modified professional_css theme and > resolve Feature Request #0001288, which will require a small tweak to > the new version control feature in the plugin autoinstall. Right, it's an arbitrary date. I just wanted to draw a line somewhere, to avoid further feature creep. Tom also seems to be struggling with some issues. Let's move it some more days. How about Friday? Btw, what's the plan for professional_css? I thought we would not ship that with 1.8.0, at least not bundled with it. Instead, install it on geeklog.net as an alternative theme to get some more feedback, and possibly offer it as a separate download (which could be a bit of a pain as long as it is work in progress). Tom? bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Sun Mar 13 12:58:34 2011 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 13 Mar 2011 16:58:34 +0000 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <003e01cbe0ce$cff536f0$6fdfa4d0$@cogeco.net> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> <003e01cbe0ce$cff536f0$6fdfa4d0$@cogeco.net> Message-ID: <1300035514.2251.27.camel@roccivic-pc> Will it be possible to link accounts? For example, will I be able to login to my existing geeklog.net account with Facebook? Rouslan On Sat, 2011-03-12 at 11:01 -0500, Tom wrote: > I would say Facebook for sure. > > 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: March-12-11 10:44 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > > Tom wrote: > > > Are we planning to use the OAuth remote service on Geeklog? I hope we do. > > I guess so. Which ones should we use? Probably not all 3 of them. Twitter? > Facebook? > > > > If so then we will need to create accounts for Geeklog at the OAuth > > providers. > > I'm not on Facebook, so if we were to use that, someone else would have to > generate that account. > > > > PS Does our host have the PHP extension OPENSLL loaded? > > Whoops, good point. > > --- snip --- > openssl > > OpenSSL support enabled > OpenSSL Version OpenSSL 0.9.8k 25 Mar 2009 > --- snip --- > > Looks like it does. > > bye, Dirk > > _______________________________________________ > 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 Mar 13 13:48:58 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 13 Mar 2011 13:48:58 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <1300035514.2251.27.camel@roccivic-pc> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <003a01cbe0c4$04ed1810$0ec74830$@cogeco.net> <003e01cbe0ce$cff536f0$6fdfa4d0$@cogeco.net> <1300035514.2251.27.camel@roccivic-pc> Message-ID: <00a701cbe1a6$eebb63b0$cc322b10$@cogeco.net> No, not at this time. 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: March-13-11 12:59 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule Will it be possible to link accounts? For example, will I be able to login to my existing geeklog.net account with Facebook? Rouslan On Sat, 2011-03-12 at 11:01 -0500, Tom wrote: > I would say Facebook for sure. > > 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: March-12-11 10:44 AM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > > Tom wrote: > > > Are we planning to use the OAuth remote service on Geeklog? I hope we do. > > I guess so. Which ones should we use? Probably not all 3 of them. Twitter? > Facebook? > > > > If so then we will need to create accounts for Geeklog at the OAuth > > providers. > > I'm not on Facebook, so if we were to use that, someone else would > have to generate that account. > > > > PS Does our host have the PHP extension OPENSLL loaded? > > Whoops, good point. > > --- snip --- > openssl > > OpenSSL support enabled > OpenSSL Version OpenSSL 0.9.8k 25 Mar 2009 > --- snip --- > > Looks like it does. > > bye, Dirk > > _______________________________________________ > 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 jmucchiello at yahoo.com Sun Mar 13 16:17:31 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Sun, 13 Mar 2011 13:17:31 -0700 (PDT) Subject: [geeklog-devel] Feature Freeze for 1.8.0 Message-ID: <278162.26404.qm@web31406.mail.mud.yahoo.com> > If you can update your patch against the current repository and make sure > all the core plugins are included then I could apply it. Also if you could > keep an eye on any bugs that get reported that the patch could be > responsible for (and include fixes) that would be great. Do you think you > will be able to have the patch to me before Friday? I will attempt to get it done by Thursday. Nightly should not be too far removed from the old patch so I should be able to get it done. > As far as I know the SOCNET plugin has had no work done on it since last > summer. Therefore I had assumed we wouldn't apply the patch until it got > picked up again or someone else needed it. Do you have plans to use it in > something else? I have a private plugin that uses the private group functionality but that codebase is still1.7. After I get template patch done I will see if I have time to update this patch. There might not be enough time though as I'll be busy the next couple nights. Joe From websitemaster at cogeco.net Mon Mar 14 13:06:09 2011 From: websitemaster at cogeco.net (Tom) Date: Mon, 14 Mar 2011 13:06:09 -0400 Subject: [geeklog-devel] Feature Freeze for 1.8.0 In-Reply-To: <278162.26404.qm@web31406.mail.mud.yahoo.com> References: <278162.26404.qm@web31406.mail.mud.yahoo.com> Message-ID: <012f01cbe26a$1d06d970$57148c50$@cogeco.net> >> I will attempt to get it done by Thursday. Nightly should not be too far removed from the old patch so I should be able to get it done. Okay, a wiki update should be done on this as well to let Plugin authors know about it. >> I have a private plugin that uses the private group functionality but that codebase is still1.7. After I get template patch done I will see if I have time to update this patch. There might not be enough time though as I'll be busy the next couple nights. Okay it's good to know you have been testing it with a private plugin along with the other testing and work done with it on the SOCNet project. If no one has any problems with this then and if I can get it by Saturday I will apply the patch for 1.8.0. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: March-13-11 4:18 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] Feature Freeze for 1.8.0 > If you can update your patch against the current repository and make > sure all the core plugins are included then I could apply it. Also if > you could keep an eye on any bugs that get reported that the patch > could be responsible for (and include fixes) that would be great. Do > you think you will be able to have the patch to me before Friday? I will attempt to get it done by Thursday. Nightly should not be too far removed from the old patch so I should be able to get it done. > As far as I know the SOCNET plugin has had no work done on it since > last summer. Therefore I had assumed we wouldn't apply the patch until > it got picked up again or someone else needed it. Do you have plans to > use it in something else? I have a private plugin that uses the private group functionality but that codebase is still1.7. After I get template patch done I will see if I have time to update this patch. There might not be enough time though as I'll be busy the next couple nights. Joe _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Tue Mar 15 14:36:45 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 15 Mar 2011 19:36:45 +0100 Subject: [geeklog-devel] Beginner-type bugs needed Message-ID: As part of their GSoC application, we are asking students for a patch. Right now, our bugtracker is a bit short on bugs or feature requests that are tagged with "beginner". We need more of them and ASAP. So, if you know of a nuissance or minor bug that you haven't added to the bugtracker yet, now would be a good time. The existing entries should also be reviewed to identify ones that are "easy". I'm not sure, actually - can normal users of the bugtracker tag entries? If not, post suggestions here and we'll take care of it. Thanks. bye, Dirk From cordiste at free.fr Wed Mar 16 12:43:03 2011 From: cordiste at free.fr (cordiste) Date: Wed, 16 Mar 2011 17:43:03 +0100 Subject: [geeklog-devel] Beginner-type bugs needed In-Reply-To: References: Message-ID: Implement a Related Stories section http://project.geeklog.net/tracking/view.php?id=1289 could be a task to begin with Geeklog. Ben 2011/3/15 Dirk Haun : > As part of their GSoC application, we are asking students for a patch. Right now, our bugtracker is a bit short on bugs or feature requests that are tagged with "beginner". We need more of them and ASAP. > > So, if you know of a nuissance or minor bug that you haven't added to the bugtracker yet, now would be a good time. The existing entries should also be reviewed to identify ones that are "easy". > > I'm not sure, actually - can normal users of the bugtracker tag entries? If not, post suggestions here and we'll take care of it. > > Thanks. > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From dirk at haun-online.de Wed Mar 16 15:35:19 2011 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 16 Mar 2011 20:35:19 +0100 Subject: [geeklog-devel] Beginner-type bugs needed In-Reply-To: References: Message-ID: <46972633-DBC3-45E9-AAB3-4A766AAF66F1@haun-online.de> cordiste wrote: > Implement a Related Stories section > http://project.geeklog.net/tracking/view.php?id=1289 > > could be a task to begin with Geeklog. It actually looks more like half a GSoC project now ;-) bye, Dirk From dirk at haun-online.de Wed Mar 16 15:48:39 2011 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 16 Mar 2011 20:48:39 +0100 Subject: [geeklog-devel] Updating the changelog Message-ID: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> The changelog (aka history) in our Mercurial repository is not up to date. Exactly how to best keep it up to date is actually something that I've been wondering about for a while. I used to update the changelog in the same commit, i.e. together with the code that fixed a bug or implemented a feature. However, that makes it more complicated to reuse that changeset on another branch, since in that other branch, the update for the changelog will usually fail. So what else could one do? You could do a second commit, just for the changelog update. Other than some minor additional "noise" and extra work, I don't see anything wrong with that. Or we could only update the changelog from time to time and/or near a release. That requires keeping track somewhere else, e.g. in the bugtracker, which already provides a changelog: http://project.geeklog.net/tracking/changelog_page.php?version_id=28 Of course that also requires that everone sets the "fixed in" field properly when resolving an issue, but that seems to be working just fine already. So we only need to be careful not to forget entries when copying them over to the "real" changelog. Other thoughts? Or am I making a simple thing too complicated (again)? bye, Dirk From websitemaster at cogeco.net Wed Mar 16 16:44:47 2011 From: websitemaster at cogeco.net (Tom) Date: Wed, 16 Mar 2011 16:44:47 -0400 Subject: [geeklog-devel] Updating the changelog In-Reply-To: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> References: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> Message-ID: <000601cbe41a$fcf0e740$f6d2b5c0$@cogeco.net> >>http://project.geeklog.net/tracking/changelog_page.php?version_id=28 >>Of course that also requires that everone sets the "fixed in" field properly when resolving an issue, but that seems to be working just fine already. So we only need to be careful not to forget entries when copying them over >>to the "real" changelog. This sounds like the best solution to me. I will continue to always use the "Fixed in" field then. Also at some point, someone should update 1.8.0 to include 1.7.2. The upgrade SQL scripts go from 1.7.1 to 1.8.0. I guess the plugins would be affected too. 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: March-16-11 3:49 PM To: Geeklog Development Subject: [geeklog-devel] Updating the changelog The changelog (aka history) in our Mercurial repository is not up to date. Exactly how to best keep it up to date is actually something that I've been wondering about for a while. I used to update the changelog in the same commit, i.e. together with the code that fixed a bug or implemented a feature. However, that makes it more complicated to reuse that changeset on another branch, since in that other branch, the update for the changelog will usually fail. So what else could one do? You could do a second commit, just for the changelog update. Other than some minor additional "noise" and extra work, I don't see anything wrong with that. Or we could only update the changelog from time to time and/or near a release. That requires keeping track somewhere else, e.g. in the bugtracker, which already provides a changelog: http://project.geeklog.net/tracking/changelog_page.php?version_id=28 Of course that also requires that everone sets the "fixed in" field properly when resolving an issue, but that seems to be working just fine already. So we only need to be careful not to forget entries when copying them over to the "real" changelog. Other thoughts? Or am I making a simple thing too complicated (again)? bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Wed Mar 16 17:17:49 2011 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 16 Mar 2011 22:17:49 +0100 Subject: [geeklog-devel] Updating the changelog In-Reply-To: <000601cbe41a$fcf0e740$f6d2b5c0$@cogeco.net> References: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> <000601cbe41a$fcf0e740$f6d2b5c0$@cogeco.net> Message-ID: <003C2E2F-06A4-403F-9341-0DBEC73E9890@haun-online.de> Tom wrote: > Also at some point, someone should update 1.8.0 to include 1.7.2. The > upgrade SQL scripts go from 1.7.1 to 1.8.0. I guess the plugins would be > affected too. Right, 1.7.2 is missing from the history there. No problem with the SQL files, though, since there aren't any. The upgrade from 1.7.1 to 1.7.2 didn't require any DB changes. bye, Dirk From jmucchiello at yahoo.com Wed Mar 16 23:22:50 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Wed, 16 Mar 2011 20:22:50 -0700 (PDT) Subject: [geeklog-devel] Feature Freeze for 1.8.0 Message-ID: <468696.8349.qm@web31407.mail.mud.yahoo.com> I've updated the COM_newTemplate patch on the bug tracker: 1220 >>> I will attempt to get it done by Thursday. Nightly should not be too >>> far > removed from the old patch so I should be able to get it done. > > Okay, a wiki update should be done on this as well to let Plugin authors > know about it. I don't have a wiki login and the only template page in the wiki is for the long lost GL2. Is the forum in the geeklog hg repository? What's the URL? You want a beginner job? Go through the wiki and find all the GL2 pages and mark them for deletion/archiving. Joe From vfuria at gmail.com Thu Mar 17 01:20:57 2011 From: vfuria at gmail.com (Vincent Furia) Date: Wed, 16 Mar 2011 23:20:57 -0600 Subject: [geeklog-devel] Updating the changelog In-Reply-To: <003C2E2F-06A4-403F-9341-0DBEC73E9890@haun-online.de> References: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> <000601cbe41a$fcf0e740$f6d2b5c0$@cogeco.net> <003C2E2F-06A4-403F-9341-0DBEC73E9890@haun-online.de> Message-ID: I wonder if we really need to maintain a separate change log any longer, or if we do, if we can't just generate it from the Mercurial Log. It seems silly to have the information (what changed) maintained in multiple locations... Using the Mercurial Log will also make it easy to keep what changed in each branche straight. -Vinny On Wed, Mar 16, 2011 at 15:17, Dirk Haun wrote: > Tom wrote: > > > Also at some point, someone should update 1.8.0 to include 1.7.2. The > > upgrade SQL scripts go from 1.7.1 to 1.8.0. I guess the plugins would be > > affected too. > > Right, 1.7.2 is missing from the history there. > > No problem with the SQL files, though, since there aren't any. The upgrade > from 1.7.1 to 1.7.2 didn't require any DB changes. > > bye, Dirk > > _______________________________________________ > 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 dirk at haun-online.de Thu Mar 17 06:00:40 2011 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 17 Mar 2011 11:00:40 +0100 Subject: [geeklog-devel] Updating the changelog In-Reply-To: References: <50D131BF-0582-4822-905A-5A27BEECF17E@haun-online.de> <000601cbe41a$fcf0e740$f6d2b5c0$@cogeco.net> <003C2E2F-06A4-403F-9341-0DBEC73E9890@haun-online.de> Message-ID: <20110317110040.196035aozmc4wcmc@webmail.df.eu> Quoting Vincent Furia : > I wonder if we really need to maintain a separate change log any longer, or > if we do, if we can't just generate it from the Mercurial Log. It seems > silly to have the information (what changed) maintained in multiple > locations... The Mercurial log contains too much noise to be useful. When we change things during development, we don't want all of those commits to show up in a changelog - only the result is of interest. We could try filtering, but that would require everyone to stick to a certain format for commit messages. My experience is that this isn't working (I see it at work all the time), especially considering that we are trying to encourage newcomers to send patches, who may not be familiar with our format then (in a Mercurial export file, the commit message is part of the patch). What we do at work is to generate the changelog from our bugtracker (JIRA - haven't checked what Mantis offers in terms of APIs). But even there we had to add a field "summary for the changelog" and have a person performing the task of an editor to ensure that what ends up in the changelog is presentable to our customers ... But if we were to automate extraction of the changelog from the bugtracker, it would we easy to do just that. I.e. run the process, check contents, edit description where necessary, re-run process. bye, Dirk From websitemaster at cogeco.net Thu Mar 17 09:49:34 2011 From: websitemaster at cogeco.net (Tom) Date: Thu, 17 Mar 2011 09:49:34 -0400 Subject: [geeklog-devel] Feature Freeze for 1.8.0 In-Reply-To: <468696.8349.qm@web31407.mail.mud.yahoo.com> References: <468696.8349.qm@web31407.mail.mud.yahoo.com> Message-ID: <002d01cbe4aa$263baf10$72b30d30$@cogeco.net> >> I don't have a wiki login and the ... I just sent you your Wiki account information >> ... only template page in the wiki is for the long lost GL2. That's not good. I did find this page. http://wiki.geeklog.net/index.php/Using_Templates_and_Language_Files It doesn't say much of anything. You could add your information here and when someone has more time we can go back and add more info. Or better yet if you have time, I would split the page into 2 (one for template and one for language files. There is an example here that should be changed http://wiki.geeklog.net/index.php/Using_Templates_and_Language_Files Geeklog 1.8.0 contains a few new features for Plugin developers. I want to make sure that the information and examples are in the wiki so we can include links in the announcement story on Geeklog.net. >> I've updated the COM_newTemplate patch on the bug tracker: 1220 I will work on this today >> Is the forum in the geeklog hg repository? What's the URL? http://project.geeklog.net/cgi-bin/hgwebdir.cgi/forum/ Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: March-16-11 11:23 PM To: geeklog-devel at lists.geeklog.net Subject: Re: [geeklog-devel] Feature Freeze for 1.8.0 I've updated the COM_newTemplate patch on the bug tracker: 1220 >>> I will attempt to get it done by Thursday. Nightly should not be too >>> far > removed from the old patch so I should be able to get it done. > > Okay, a wiki update should be done on this as well to let Plugin > authors know about it. I don't have a wiki login and the only template page in the wiki is for the long lost GL2. Is the forum in the geeklog hg repository? What's the URL? You want a beginner job? Go through the wiki and find all the GL2 pages and mark them for deletion/archiving. Joe _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dionet at gmail.com Thu Mar 17 18:27:21 2011 From: dionet at gmail.com (=?ISO-8859-1?Q?Diogo_Gon=E7alves?=) Date: Thu, 17 Mar 2011 22:27:21 +0000 Subject: [geeklog-devel] Google Summer of Code 2011 Message-ID: Hello, I'm Diogo and I'm a student interested in participating on Google Summer of Code 2011. I plan to apply for the "Remote Authentication using OpenID and OAuth" idea, if Geeklog is accepted as a mentoring organization. In a few days I'll start working on my application and I hope you'll be willing to review it. Thank you, -- Diogo Gon?alves http://www.diporg.com From dirk at haun-online.de Fri Mar 18 04:59:21 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 18 Mar 2011 09:59:21 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: References: Message-ID: <20110318095921.64914nydakrqib6s@webmail.df.eu> Quoting Diogo Gon?alves : > if Geeklog is accepted as a mentoring organization. We'll know in a few hours :) > In a few days I'll start working on my application and I hope you'll > be willing to review it. Sure, we'll happily review draft applications as long as time permits. Once the deadline for student applications is coming closer, we're usually swamped with such review requests, so the earlier you send something, the better are the chances that we'll actually be able to review it. bye, Dirk From dirk at haun-online.de Fri Mar 18 15:28:25 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 18 Mar 2011 20:28:25 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: <20110318095921.64914nydakrqib6s@webmail.df.eu> References: <20110318095921.64914nydakrqib6s@webmail.df.eu> Message-ID: <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> >> if Geeklog is accepted as a mentoring organization. > > We'll know in a few hours :) And the answer is - nope, we didn't get in this time. I'm a bit disappointed, of course, but we had 4 great years in a row. I'd like to thank Google for giving us the opportunity. There's an IRC meeting for the rejected orgs on Wednesday where I'll try to find out more about why we didn't make the cut this year. And of course learn what we can do to get in again in a possible future GSoC :) In the meantime, we have an upcoming release to take care of. And on the plus side, we now have some breathing room to take care of the successful GSoC projects from past years that haven't been rolled into Geeklog yet. So, let's roll up our sleeves and get some coding done. bye, Dirk From dirk at haun-online.de Fri Mar 18 16:25:43 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 18 Mar 2011 21:25:43 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> Message-ID: <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> > There's an IRC meeting for the rejected orgs on Wednesday Err, make that Tuesday (16:00 UTC). bye, Dirk From dirk at haun-online.de Fri Mar 18 16:49:05 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 18 Mar 2011 21:49:05 +0100 Subject: [geeklog-devel] Future of the Forum plugin Message-ID: <1E059EB7-9CC7-4A33-82FB-29A96294C1E7@haun-online.de> This discussion shouldn't be buried in the bugtracker[1] ... The Forum plugin is one of the most popular non-core plugins for Geeklog. Unfortunately, it is currently without a maintainer. Since there were some security issues to address, we took it under our wings[2] - so to speak - for the time being. I, at least, never intended this to be a permanent thing, though. There's enough to do in Geeklog itself and I don't think we should add maintenance for yet another plugin on top of that. In other words, we should be looking for a maintainer or group of maintainers to ensure further development of the Forum plugin, but outside of the Geeklog core team. Now back to the discussion on the bugtracker: It was about adding support for features that will be new in Geeklog 1.8.0 to the Forum plugin. Which would mean that the Forum would require Geeklog 1.8.0 at the minimum. I don't think this is a good idea at this point. We should try to keep it available for older Geeklog versions, too. Of course, we could create a branch, but that would then mean twice the amount of work. Which is really too much for us to shoulder, IMO. So in my opinion, we should keep the Forum backward-compatible for now (nothing wrong with adding features, just make sure they don't require a current Geeklog version). And in parallel, we should be looking for a new maintainer or maintainers to ensure the further and proper development of that plugin. There's a lot to do there and I have some ideas myself (and would possibly be contributing some code as well). We just should get it into someone else's hands again soon(ish). Thoughts? bye, Dirk [1] [2] From jmucchiello at yahoo.com Fri Mar 18 21:37:28 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Fri, 18 Mar 2011 18:37:28 -0700 (PDT) Subject: [geeklog-devel] Future of the Forum plugin Message-ID: <54682.66986.qm@web31407.mail.mud.yahoo.com> Of course this is not just the forum. Filemgnt is also a high profile plugin that has been adrift since Blaine moved on. Arguably the PM plugin is also important because it is featured on geeklog.net. From cordiste at free.fr Sat Mar 19 04:00:55 2011 From: cordiste at free.fr (cordiste) Date: Sat, 19 Mar 2011 09:00:55 +0100 Subject: [geeklog-devel] Future of the Forum plugin In-Reply-To: <1E059EB7-9CC7-4A33-82FB-29A96294C1E7@haun-online.de> References: <1E059EB7-9CC7-4A33-82FB-29A96294C1E7@haun-online.de> Message-ID: I volunteered as a mentor for GSOC 2011 but we were not successful, so I will have some time to participate in the forum project. As english is not my first language, I'm certainly not the best and I will not have enough time to take alone the project, writing documentation, and provide support for users but I will be happy to write some code and implement some features. And this can be a nice community project, a sort of CSoC 2011 - Community Summer of Code. ::Ben 2011/3/18 Dirk Haun : > This discussion shouldn't be buried in the bugtracker[1] ... > > The Forum plugin is one of the most popular non-core plugins for Geeklog. Unfortunately, it is currently without a maintainer. Since there were some security issues to address, we took it under our wings[2] - so to speak - for the time being. > > I, at least, never intended this to be a permanent thing, though. There's enough to do in Geeklog itself and I don't think we should add maintenance for yet another plugin on top of that. In other words, we should be looking for a maintainer or group of maintainers to ensure further development of the Forum plugin, but outside of the Geeklog core team. > > Now back to the discussion on the bugtracker: It was about adding support for features that will be new in Geeklog 1.8.0 to the Forum plugin. Which would mean that the Forum would require Geeklog 1.8.0 at the minimum. I don't think this is a good idea at this point. We should try to keep it available for older Geeklog versions, too. > > Of course, we could create a branch, but that would then mean twice the amount of work. Which is really too much for us to shoulder, IMO. > > So in my opinion, we should keep the Forum backward-compatible for now (nothing wrong with adding features, just make sure they don't require a current Geeklog version). And in parallel, we should be looking for a new maintainer or maintainers to ensure the further and proper development of that plugin. There's a lot to do there and I have some ideas myself (and would possibly be contributing some code as well). We just should get it into someone else's hands again soon(ish). > > Thoughts? > > bye, Dirk > > [1] > [2] > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From dirk at haun-online.de Sat Mar 19 04:34:28 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 19 Mar 2011 09:34:28 +0100 Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) In-Reply-To: <54682.66986.qm@web31407.mail.mud.yahoo.com> References: <54682.66986.qm@web31407.mail.mud.yahoo.com> Message-ID: <82A7BD50-6BD9-4DCF-9390-1E4D419F2DEA@haun-online.de> > Filemgnt is also a high profile plugin > that has been adrift since Blaine moved on. I did some work on the File Management plugin[1]. That's also the version that is running on geeklog.net. The upgrade code needs some work - I suspect that it won't work for upgrades from rather old versions. Again, this is mainly maintenance work that I only did since we're using it on geeklog.net. I'm not too happy with the plugin's functionality, actually. Ironically, it doesn't really offer a lot of file management options, despite the name. There's also the Downloads plugin[2] which, as I understand it, can be used as a drop-in replacement (haven't tried it myself). > Arguably the PM plugin is also > important because it is featured on geeklog.net. That has always been a bit of a showcase install. But I guess we can't simply disable it now ... bye, Dirk [1] [2] From dirk at haun-online.de Sat Mar 19 09:00:50 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 19 Mar 2011 14:00:50 +0100 Subject: [geeklog-devel] Feature freeze Message-ID: <57C39EB5-B1D6-402F-A443-80056A25B04C@haun-online.de> Just checking: Is everyone happy with declaring a feature freeze for Geeklog 1.8.0 now? I was hoping to be able to cram in at least the Geeklog side of the plugin repository project from Tim from 2 years ago, but ended up with a half-merged repository. Oh well, for 1.8.1 then. Can everyone please check the roadmap page for 1.8.0 and either complete the outstanding feature requests and patches or push them to 1.8.1? http://project.geeklog.net/tracking/roadmap_page.php?version_id=28 I'm doing some housekeeping in the meantime. The nightly tarball is now created twice per day. Would have preferred an even higher frequency, but the script to create it isn't so great and puts a lot of load on the server for a few minutes. Have to review that - maybe let Jenkins do it. Btw, the nightly tarball includes both the Professional and the Professional CSS theme, but as discussed before we will only ship the old Professional theme in 1.8.0 (though slightly revamped with some new icons). The language files should all be in snyc now. If possible, I'd like to avoid language file changes from now on so that the translators can start working on them soon ... Hmm, this reminds me that I spotted a hard-coded text string in a JavaScript somewhere. So maybe not quite cut-and-dried yet ... Anything else? bye, Dirk From websitemaster at cogeco.net Sat Mar 19 09:42:41 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 19 Mar 2011 09:42:41 -0400 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> Message-ID: <00f301cbe63b$84c62c30$8e528490$@cogeco.net> >> There's an IRC meeting for the rejected orgs on Wednesday where I'll try to find out more about why we didn't make the cut this year. And of course learn what we can do to get in again in a possible future GSoC :) Sounds good >> In the meantime, we have an upcoming release to take care of. And on the plus side, we now have some breathing room to take care of the successful GSoC projects from past years that haven't been rolled into Geeklog yet. So, let's roll up our sleeves and get some coding done. It is too bad we didn't get into GSOC but as you said there is an upside to it all as we can concentrate on previous GSOC projects and other features. Since Rouslan is working on the theme and Joe plans to work on his template plugin I will be concentrating on allowing topics to be associated with other objects: http://project.geeklog.net/tracking/view.php?id=1155 I will also work on the Geeklog.net redesign http://wiki.geeklog.net/index.php/Geeklog.net_Redesign With the redesign I will be obviously be looking for feedback after each step along with volunteers to help write the new pages once we figure out the layout. 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: March-18-11 3:28 PM To: Geeklog Development Subject: Re: [geeklog-devel] Google Summer of Code 2011 >> if Geeklog is accepted as a mentoring organization. > > We'll know in a few hours :) And the answer is - nope, we didn't get in this time. I'm a bit disappointed, of course, but we had 4 great years in a row. I'd like to thank Google for giving us the opportunity. There's an IRC meeting for the rejected orgs on Wednesday where I'll try to find out more about why we didn't make the cut this year. And of course learn what we can do to get in again in a possible future GSoC :) In the meantime, we have an upcoming release to take care of. And on the plus side, we now have some breathing room to take care of the successful GSoC projects from past years that haven't been rolled into Geeklog yet. So, let's roll up our sleeves and get some coding done. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sat Mar 19 10:27:02 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 19 Mar 2011 10:27:02 -0400 Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) In-Reply-To: <82A7BD50-6BD9-4DCF-9390-1E4D419F2DEA@haun-online.de> References: <54682.66986.qm@web31407.mail.mud.yahoo.com> <82A7BD50-6BD9-4DCF-9390-1E4D419F2DEA@haun-online.de> Message-ID: <00f701cbe641$b6ad8940$24089bc0$@cogeco.net> >> There's also the Downloads plugin[2] which, as I understand it, can be used as a drop-in replacement (haven't tried it myself). The downloads plugin does look like a viable option (especially since it is being actively developed). I haven't used it either but I believe Cordiste has (how do you like it?). >> That has always been a bit of a showcase install. But I guess we can't simply disable it now ... > Arguably the PM plugin is also > important because it is featured on geeklog.net. I would use the features of this plugin on Geeklog.net but I have found that I never get emails when I receive a new message. I believe it is supposed to send one out. 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: March-19-11 4:34 AM To: Geeklog Development Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) > Filemgnt is also a high profile plugin that has been adrift since > Blaine moved on. I did some work on the File Management plugin[1]. That's also the version that is running on geeklog.net. The upgrade code needs some work - I suspect that it won't work for upgrades from rather old versions. Again, this is mainly maintenance work that I only did since we're using it on geeklog.net. I'm not too happy with the plugin's functionality, actually. Ironically, it doesn't really offer a lot of file management options, despite the name. There's also the Downloads plugin[2] which, as I understand it, can be used as a drop-in replacement (haven't tried it myself). > Arguably the PM plugin is also > important because it is featured on geeklog.net. That has always been a bit of a showcase install. But I guess we can't simply disable it now ... bye, Dirk [1] [2] _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Sat Mar 19 10:35:16 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 19 Mar 2011 10:35:16 -0400 Subject: [geeklog-devel] Future of the Forum plugin In-Reply-To: <1E059EB7-9CC7-4A33-82FB-29A96294C1E7@haun-online.de> References: <1E059EB7-9CC7-4A33-82FB-29A96294C1E7@haun-online.de> Message-ID: <00f801cbe642$dd97bc50$98c734f0$@cogeco.net> >> So in my opinion, we should keep the Forum backward-compatible for now Okay I will update my tooltip patch to support older versions then. 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: March-18-11 4:49 PM To: Geeklog Development Subject: [geeklog-devel] Future of the Forum plugin This discussion shouldn't be buried in the bugtracker[1] ... The Forum plugin is one of the most popular non-core plugins for Geeklog. Unfortunately, it is currently without a maintainer. Since there were some security issues to address, we took it under our wings[2] - so to speak - for the time being. I, at least, never intended this to be a permanent thing, though. There's enough to do in Geeklog itself and I don't think we should add maintenance for yet another plugin on top of that. In other words, we should be looking for a maintainer or group of maintainers to ensure further development of the Forum plugin, but outside of the Geeklog core team. Now back to the discussion on the bugtracker: It was about adding support for features that will be new in Geeklog 1.8.0 to the Forum plugin. Which would mean that the Forum would require Geeklog 1.8.0 at the minimum. I don't think this is a good idea at this point. We should try to keep it available for older Geeklog versions, too. Of course, we could create a branch, but that would then mean twice the amount of work. Which is really too much for us to shoulder, IMO. So in my opinion, we should keep the Forum backward-compatible for now (nothing wrong with adding features, just make sure they don't require a current Geeklog version). And in parallel, we should be looking for a new maintainer or maintainers to ensure the further and proper development of that plugin. There's a lot to do there and I have some ideas myself (and would possibly be contributing some code as well). We just should get it into someone else's hands again soon(ish). Thoughts? bye, Dirk [1] [2] _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From cordiste at free.fr Sat Mar 19 13:54:43 2011 From: cordiste at free.fr (cordiste) Date: Sat, 19 Mar 2011 18:54:43 +0100 Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) In-Reply-To: <00f701cbe641$b6ad8940$24089bc0$@cogeco.net> References: <54682.66986.qm@web31407.mail.mud.yahoo.com> <82A7BD50-6BD9-4DCF-9390-1E4D419F2DEA@haun-online.de> <00f701cbe641$b6ad8940$24089bc0$@cogeco.net> Message-ID: >> I haven't used it either but I believe Cordiste I installed the Downloads plugin once on a test site but I do not use it, so I can't tell you more. Ben 2011/3/19 Tom : >>> There's also the Downloads plugin[2] which, as I understand it, can be > used as a drop-in replacement (haven't tried it myself). > > The downloads plugin does look like a viable option (especially since it is > being actively developed). ?I haven't used it either but I believe Cordiste > has (how do you like it?). > >>> That has always been a bit of a showcase install. But I guess we can't > simply disable it now ... > >> Arguably the PM plugin is also >> important because it is featured on geeklog.net. > > I would use the features of this ?plugin on Geeklog.net ?but I have found > that I never get emails when I receive a new message. ?I believe it is > supposed to send one out. > > 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: March-19-11 4:34 AM > To: Geeklog Development > Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) > >> Filemgnt is also a high profile plugin that has been adrift since >> Blaine moved on. > > I did some work on the File Management plugin[1]. That's also the version > that is running on geeklog.net. The upgrade code needs some work - I suspect > that it won't work for upgrades from rather old versions. > > Again, this is mainly maintenance work that I only did since we're using it > on geeklog.net. I'm not too happy with the plugin's functionality, actually. > Ironically, it doesn't really offer a lot of file management options, > despite the name. > > There's also the Downloads plugin[2] which, as I understand it, can be used > as a drop-in replacement (haven't tried it myself). > > >> Arguably the PM plugin is also >> important because it is featured on geeklog.net. > > > That has always been a bit of a showcase install. But I guess we can't > simply disable it now ... > > bye, Dirk > > [1] > [2] > > _______________________________________________ > 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 cordiste at free.fr Sat Mar 19 14:18:51 2011 From: cordiste at free.fr (cordiste) Date: Sat, 19 Mar 2011 19:18:51 +0100 Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) In-Reply-To: References: <54682.66986.qm@web31407.mail.mud.yahoo.com> <82A7BD50-6BD9-4DCF-9390-1E4D419F2DEA@haun-online.de> <00f701cbe641$b6ad8940$24089bc0$@cogeco.net> Message-ID: I remember I was looking for an important feature when I tried Downloads plugin, the ability to store files outside the web root. And neither Downloads plugin nor the filemgmt plugin does. It would be really appreciable. Ben 2011/3/19 cordiste : >>> I haven't used it either but I believe Cordiste > > I installed the Downloads plugin once on a test site but I do not use > it, so I can't tell you more. > > Ben > > 2011/3/19 Tom : >>>> There's also the Downloads plugin[2] which, as I understand it, can be >> used as a drop-in replacement (haven't tried it myself). >> >> The downloads plugin does look like a viable option (especially since it is >> being actively developed). ?I haven't used it either but I believe Cordiste >> has (how do you like it?). >> >>>> That has always been a bit of a showcase install. But I guess we can't >> simply disable it now ... >> >>> Arguably the PM plugin is also >>> important because it is featured on geeklog.net. >> >> I would use the features of this ?plugin on Geeklog.net ?but I have found >> that I never get emails when I receive a new message. ?I believe it is >> supposed to send one out. >> >> 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: March-19-11 4:34 AM >> To: Geeklog Development >> Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) >> >>> Filemgnt is also a high profile plugin that has been adrift since >>> Blaine moved on. >> >> I did some work on the File Management plugin[1]. That's also the version >> that is running on geeklog.net. The upgrade code needs some work - I suspect >> that it won't work for upgrades from rather old versions. >> >> Again, this is mainly maintenance work that I only did since we're using it >> on geeklog.net. I'm not too happy with the plugin's functionality, actually. >> Ironically, it doesn't really offer a lot of file management options, >> despite the name. >> >> There's also the Downloads plugin[2] which, as I understand it, can be used >> as a drop-in replacement (haven't tried it myself). >> >> >>> Arguably the PM plugin is also >>> important because it is featured on geeklog.net. >> >> >> That has always been a bit of a showcase install. But I guess we can't >> simply disable it now ... >> >> bye, Dirk >> >> [1] >> [2] >> >> _______________________________________________ >> 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 Mar 20 10:35:29 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 20 Mar 2011 10:35:29 -0400 Subject: [geeklog-devel] JavaScript, Template Variables and Autotags Message-ID: <004b01cbe70c$0f603c20$2e20b460$@cogeco.net> Does anyone see the need for our template engine to be searching for template variables in JavaScript? I have run into a problem where curly brackets are used in JavaScript code and then our template engine is stripping them out when nothing was found matching it. Since we introduced autotags to templates this problem also happens with autotags. If an autotag is listed in JavaScript (for example in alert message box as a help message or something) if found the autotag will be replaced. To fix this problem for now I have disabled autotags in the footer template file (that is where by default JavaScript goes in the scripts class). For template variables I think we should at least disable removing of unused template variables in the footer This can be easily done in COM_siteFooter by adding the line $footer->unknowns = 'keep'; These 2 fixes are temporarily since it doesn't fix the entire problem. JavaScript could appear in other template files. I think ideally we would want template variables and autotags to remain as is, if found in any JavaScript code (ie between ). I am not sure if I have the time to fix this right now before 1.8.0 release. Thoughts? Tom From dirk at haun-online.de Sun Mar 20 10:51:05 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 20 Mar 2011 15:51:05 +0100 Subject: [geeklog-devel] JavaScript, Template Variables and Autotags In-Reply-To: <004b01cbe70c$0f603c20$2e20b460$@cogeco.net> References: <004b01cbe70c$0f603c20$2e20b460$@cogeco.net> Message-ID: Tom wrote: > Thoughts? You could also write your JavaScript in a less compact and more readable format, i.e. leave spaces and/or line breaks before / after the curly brackets. The template class is pretty strict (or stupid, depending on point of view ;-) in what it considers a template variable. So I don't think this is a major problem right now. bye, Dirk From websitemaster at cogeco.net Sun Mar 20 11:08:11 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 20 Mar 2011 11:08:11 -0400 Subject: [geeklog-devel] JavaScript, Template Variables and Autotags In-Reply-To: References: <004b01cbe70c$0f603c20$2e20b460$@cogeco.net> Message-ID: <005101cbe710$a135c620$e3a15260$@cogeco.net> >> So I don't think this is a major problem right now. I agree, but it still is a problem. In PHP I am using json_encode to pass in an array of Config variables to JavaScript. json_encode produces output that is wrapped in { } which is how I discovered the problem. Your fix of adding spaces (I am not sure why I didn't think of that) works so there is a work around. Should I just add a bug report in the tracker about this problem so when we have time we can tackle it in the future? 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: March-20-11 10:51 AM To: Geeklog Development Subject: Re: [geeklog-devel] JavaScript, Template Variables and Autotags Tom wrote: > Thoughts? You could also write your JavaScript in a less compact and more readable format, i.e. leave spaces and/or line breaks before / after the curly brackets. The template class is pretty strict (or stupid, depending on point of view ;-) in what it considers a template variable. So I don't think this is a major problem right now. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From jmucchiello at yahoo.com Sun Mar 20 11:11:44 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Sun, 20 Mar 2011 08:11:44 -0700 (PDT) Subject: [geeklog-devel] JavaScript, Template Variables and Autotags Message-ID: <610902.43927.qm@web31401.mail.mud.yahoo.com> As for braces, my solution is to suggest a gradual shift from {templatevar} to {{templatevar}}. It should not be too hard to code for both methods in the template engine and then drop support for single braces in Geeklog 1.9. With COM_newTemplate in place, you can even leave the existing single brace engine in place for use with plugins that still call "new Template" directly to ease plugin migration. From dirk at haun-online.de Sun Mar 20 11:16:54 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 20 Mar 2011 16:16:54 +0100 Subject: [geeklog-devel] JavaScript, Template Variables and Autotags In-Reply-To: <005101cbe710$a135c620$e3a15260$@cogeco.net> References: <004b01cbe70c$0f603c20$2e20b460$@cogeco.net> <005101cbe710$a135c620$e3a15260$@cogeco.net> Message-ID: Tom wrote: > Should I just add a bug report in the tracker about this problem so when we > have time we can tackle it in the future? Yep. It's been like this for a while. Also see bugs #1156 and #1157 bye, Dirk From ironmax at spacequad.com Sun Mar 20 16:26:21 2011 From: ironmax at spacequad.com (Michael Brusletten) Date: Sun, 20 Mar 2011 16:26:21 -0400 Subject: [geeklog-devel] Other plugins (was: Future of the Forum References: Message-ID: <001901cbe73d$13ca7dd0$fe00a8c0@node1> I've used the filemgmt plugin from Blaine without any problems for storing files outside the web root without any problems. But then again, this was using it on a windows server platform. I have not tried it on a NIX system yet, however, I think it is still doable. Michael > ------------------------------ > > Date: Sat, 19 Mar 2011 19:18:51 +0100 > From: cordiste > Subject: Re: [geeklog-devel] Other plugins (was: Future of the Forum > plugin) > To: Geeklog Development > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > I remember I was looking for an important feature when I tried > Downloads plugin, the ability to store files outside the web root. And > neither Downloads plugin nor the filemgmt plugin does. It would be > really appreciable. > > Ben > > > 2011/3/19 cordiste : > >>> I haven't used it either but I believe Cordiste > > > > I installed the Downloads plugin once on a test site but I do not use > > it, so I can't tell you more. > > > > Ben > > > > 2011/3/19 Tom : > >>>> There's also the Downloads plugin[2] which, as I understand it, can be > >> used as a drop-in replacement (haven't tried it myself). > >> > >> The downloads plugin does look like a viable option (especially since it is > >> being actively developed). ?I haven't used it either but I believe Cordiste > >> has (how do you like it?). > >> > >>>> That has always been a bit of a showcase install. But I guess we can't > >> simply disable it now ... > >> > >>> Arguably the PM plugin is also > >>> important because it is featured on geeklog.net. > >> > >> I would use the features of this ?plugin on Geeklog.net ?but I have found > >> that I never get emails when I receive a new message. ?I believe it is > >> supposed to send one out. > >> > >> 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: March-19-11 4:34 AM > >> To: Geeklog Development > >> Subject: [geeklog-devel] Other plugins (was: Future of the Forum plugin) > >> > >>> Filemgnt is also a high profile plugin that has been adrift since > >>> Blaine moved on. > >> > >> I did some work on the File Management plugin[1]. That's also the version > >> that is running on geeklog.net. The upgrade code needs some work - I suspect > >> that it won't work for upgrades from rather old versions. > >> > >> Again, this is mainly maintenance work that I only did since we're using it > >> on geeklog.net. I'm not too happy with the plugin's functionality, actually. > >> Ironically, it doesn't really offer a lot of file management options, > >> despite the name. > >> > >> There's also the Downloads plugin[2] which, as I understand it, can be used > >> as a drop-in replacement (haven't tried it myself). > >> > >> > >>> Arguably the PM plugin is also > >>> important because it is featured on geeklog.net. > >> > >> > >> That has always been a bit of a showcase install. But I guess we can't > >> simply disable it now ... > >> > >> bye, Dirk > >> From dirk at haun-online.de Sun Mar 20 17:22:44 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 20 Mar 2011 22:22:44 +0100 Subject: [geeklog-devel] Other plugins (was: Future of the Forum In-Reply-To: <001901cbe73d$13ca7dd0$fe00a8c0@node1> References: <001901cbe73d$13ca7dd0$fe00a8c0@node1> Message-ID: Michael Brusletten wrote: > I've used the filemgmt plugin from Blaine without any problems for storing > files outside the web root without any problems. But then again, this was > using it on a windows server platform. I have not tried it on a NIX system > yet, however, I think it is still doable. The plugin doesn't support this. It may be possible to do that with some symlinking on the server side, but I'm not sure. All downloads go via visit.php to get some statistics and all that script then does is to send a meta redirect to the actual file. In other words, the file must be web-accessible - if you know the full URL, you can download it directly. That would still work if you somehow managed to place the files outside the webroot and symlink them in. To serve files from outside the webroot properly (so that they're not directly accessible) you would need to use Geeklog's downloader class. But the File Management plugin doesn't use it. bye, Dirk From dirk at haun-online.de Tue Mar 22 14:48:29 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 22 Mar 2011 19:48:29 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> Message-ID: >> There's an IRC meeting for the rejected orgs on Wednesday > > Err, make that Tuesday (16:00 UTC). And here's the outcome (just now - long queue of orgs waiting for feedback): --- snip --- carols ? hey dhaun dhaun ? hey Carol, hope you're not too exhausted by now 19:37 dhaun ? thanks for doing this, our ideas page is http://wiki.geeklog.net/index.php/Google_Summer_of_Code 19:37 carols ? no problem, just give me a sec 19:37 carols ? yeah, another bad news one. i see you guys were in until our very final round of cuts and we just had to get to a specific number -------------- next part -------------- A non-text attachment was scrubbed... Name: frown.tif Type: image/tiff Size: 9402 bytes Desc: not available URL: -------------- next part -------------- 19:39 carols ? i liked your app, i like your org 19:39 carols ? but we were making way for new orgs this year 19:39 dhaun ? thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: smile.tif Type: image/tiff Size: 9606 bytes Desc: not available URL: -------------- next part -------------- 19:39 carols ? i'm sorry this isn't more satisfying -------------- next part -------------- A non-text attachment was scrubbed... Name: frown.tif Type: image/tiff Size: 9402 bytes Desc: not available URL: -------------- next part -------------- 19:39 dhaun ? right, that's what I was "hoping", sort-of, to hear 19:39 carols ? please keep doing what you're doing -------------- next part -------------- A non-text attachment was scrubbed... Name: smile.tif Type: image/tiff Size: 9606 bytes Desc: not available URL: -------------- next part -------------- 19:39 carols ? we really cut into bone this year 19:40 dhaun ? well, that should be easy then -------------- next part -------------- A non-text attachment was scrubbed... Name: smile.tif Type: image/tiff Size: 9606 bytes Desc: not available URL: -------------- next part -------------- 19:40 carols ? please do apply next year, of course 19:40 dhaun ? okay, anything else you can think of or just "keep it up"? 19:40 carols ? seriously, just keep it up. this had nothing to do with your app -------------- next part -------------- A non-text attachment was scrubbed... Name: slant.tif Type: image/tiff Size: 9604 bytes Desc: not available URL: -------------- next part -------------- 19:41 dhaun ? well, that's good to hear - thank you 19:41 carols ? you're welcome 19:41 dhaun ? we'll be back -------------- next part -------------- A non-text attachment was scrubbed... Name: smile.tif Type: image/tiff Size: 9606 bytes Desc: not available URL: -------------- next part -------------- --- snip -- So, this was pretty much what I expected. Nothing wrong with the application as such, we just had to make room for some new orgs. Fair enough. The full channel log will be available tomorrow at . The feedback the other orgs got is also interesting. bye, Dirk From dirk at haun-online.de Tue Mar 22 15:02:09 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 22 Mar 2011 20:02:09 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> Message-ID: Okay, let me try that again, without the smilies and timestamps. Sorry about that ... --- snip --- carols ? hey dhaun dhaun ? hey Carol, hope you're not too exhausted by now dhaun ? thanks for doing this, our ideas page is http://wiki.geeklog.net/index.php/Google_Summer_of_Code carols ? no problem, just give me a sec carols ? yeah, another bad news one. i see you guys were in until our very final round of cuts and we just had to get to a specific number carols ? i liked your app, i like your org carols ? but we were making way for new orgs this year dhaun ? thanks carols ? i'm sorry this isn't more satisfying dhaun ? right, that's what I was "hoping", sort-of, to hear carols ? please keep doing what you're doing carols ? we really cut into bone this year dhaun ? well, that should be easy then carols ? please do apply next year, of course dhaun ? okay, anything else you can think of or just "keep it up"? carols ? seriously, just keep it up. this had nothing to do with your app dhaun ? well, that's good to hear - thank you carols ? you're welcome dhaun ? we'll be back --- snip --- Also, 417 organizations applied this year, 175 were selected which was already more than last year. Obviously, there had to be some hard decisions somewhere. bye, Dirk From websitemaster at cogeco.net Tue Mar 22 17:49:59 2011 From: websitemaster at cogeco.net (Tom) Date: Tue, 22 Mar 2011 17:49:59 -0400 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> Message-ID: <007c01cbe8db$173a4e10$45aeea30$@cogeco.net> Hmm, Good to see it was nothing we did or prepared. 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: March-22-11 3:02 PM To: Geeklog Development Subject: Re: [geeklog-devel] Google Summer of Code 2011 Okay, let me try that again, without the smilies and timestamps. Sorry about that ... --- snip --- carols ? hey dhaun dhaun ? hey Carol, hope you're not too exhausted by now dhaun ? thanks for doing this, our ideas page is http://wiki.geeklog.net/index.php/Google_Summer_of_Code carols ? no problem, just give me a sec carols ? yeah, another bad news one. i see you guys were in until our very final round of cuts and we just had to get to a specific number carols ? i liked your app, i like your org carols ? but we were making way for new orgs this year dhaun ? thanks carols ? i'm sorry this isn't more satisfying dhaun ? right, that's what I was "hoping", sort-of, to hear carols ? please keep doing what you're doing carols ? we really cut into bone this year dhaun ? well, that should be easy then carols ? please do apply next year, of course dhaun ? okay, anything else you can think of or just "keep it up"? carols ? seriously, just keep it up. this had nothing to do with your app dhaun ? well, that's good to hear - thank you carols ? you're welcome dhaun ? we'll be back --- snip --- Also, 417 organizations applied this year, 175 were selected which was already more than last year. Obviously, there had to be some hard decisions somewhere. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Wed Mar 23 07:51:30 2011 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 23 Mar 2011 12:51:30 +0100 Subject: [geeklog-devel] Google Summer of Code 2011 In-Reply-To: References: <20110318095921.64914nydakrqib6s@webmail.df.eu> <028F07DE-0B47-4F85-B523-C2D0F31DD00F@haun-online.de> <380139F8-D2E4-4066-8E30-E5A1A36CC3AE@haun-online.de> Message-ID: <20110323125130.1469420vut9t0v6s@webmail.df.eu> The full log of yesterday's IRC session for the rejected organization is now online: http://ibot.rikers.org/%23gsoc/20110322.html.gz Meeting starts at 16:09.37 Even though we got a "thumbs up" for our ideas page, there's always room for improvement, of course. The feedback that some of the other orgs got on theirs includes some hints on what we could improve. For example: The ideas page being the main starting point for students, so it should contain all the necessary information, not only on GSoC but also about the organization itself. That makes sense, considering that the ideas page is linked from the list of accepted orgs and may be the first thing the student sees about an organization. Our ideas page currently doesn't really say what we're doing. The entire feedback session lasted 4 hours(!). Kudos to Carol for that. Read through it if you have some time - lots of interesting tidbits in there. bye, Dirk From websitemaster at cogeco.net Thu Mar 24 17:50:23 2011 From: websitemaster at cogeco.net (Tom) Date: Thu, 24 Mar 2011 17:50:23 -0400 Subject: [geeklog-devel] JavaScript, Template Variables and Autotags In-Reply-To: <610902.43927.qm@web31401.mail.mud.yahoo.com> References: <610902.43927.qm@web31401.mail.mud.yahoo.com> Message-ID: <014001cbea6d$7aaaf470$7000dd50$@cogeco.net> >> With COM_newTemplate in place, you can even leave the existing single brace engine in place for use with plugins that still call "new Template" directly to ease plugin migration. That makes the most sense. -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello Sent: March-20-11 11:12 AM To: geeklog-devel at lists.geeklog.net Subject: [geeklog-devel] JavaScript, Template Variables and Autotags As for braces, my solution is to suggest a gradual shift from {templatevar} to {{templatevar}}. It should not be too hard to code for both methods in the template engine and then drop support for single braces in Geeklog 1.9. With COM_newTemplate in place, you can even leave the existing single brace engine in place for use with plugins that still call "new Template" directly to ease plugin migration. _______________________________________________ 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 Mar 25 13:51:04 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 25 Mar 2011 18:51:04 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Message-ID: <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> > Beta 1 release on March 27. Everyone still on track for this coming Sunday? There seems to be only one bug open, according to the Roadmap view. Just checking if anything important is missing. bye, Dirk From websitemaster at cogeco.net Fri Mar 25 15:31:43 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 25 Mar 2011 15:31:43 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> Message-ID: <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> I believe the 1.7.2 upgrade stuff still needs to be added. 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: March-25-11 1:51 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > Beta 1 release on March 27. Everyone still on track for this coming Sunday? There seems to be only one bug open, according to the Roadmap view. Just checking if anything important is missing. bye, Dirk _______________________________________________ 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 Mar 25 15:33:18 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 25 Mar 2011 20:33:18 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> Message-ID: <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> Tom wrote: > I believe the 1.7.2 upgrade stuff still needs to be added. There is no 1.7. 2 upgrade stuff. The only thing missing is the version number 1.7.2 in that list in the install script somewhere that acts as a fallback when it can't identify the Geeklog version. I'll add that. bye, Dirk From dirk at haun-online.de Fri Mar 25 15:36:09 2011 From: dirk at haun-online.de (Dirk Haun) Date: Fri, 25 Mar 2011 20:36:09 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> Message-ID: <31D0272B-9A00-4ECA-BDC6-4B5C7CA199D5@haun-online.de> > Tom wrote: > >> I believe the 1.7.2 upgrade stuff still needs to be added. > > There is no 1.7. 2 upgrade stuff. Okay, I see what you mean now (or did you?) - the install script jumps from 1.7.1 to 1.8.0 directly. Doesn't hurt (since there were no DB changes in 1.7.2), but it should also handle 1.7.2 in that case statement. The entry I thought was missing was already there, though ... bye, Dirk From rouslan at placella.com Fri Mar 25 15:56:34 2011 From: rouslan at placella.com (Rouslan Placella) Date: Fri, 25 Mar 2011 19:56:34 +0000 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> Message-ID: <1301082994.2298.44.camel@roccivic-pc> I need to fix a bug that I introduced with new plugin admin list (and didn't file a bug report about it). When clicking the enable/disable links, on some remote servers a cached copy of the plugin list is served after the operation and the plugin state change is not reflected. Possible solutions are: * issue a no-cache directive with a header in the appropriate place (right now COM_refresh is used for reloading the page) * append some dummy variable to the url (this will look ugly in the address bar, but IMO will be most effective) * issue a POST request via the "pluginenabler" form (I would hate to reintroduce this) instead of the current GET request. * other? Let me know what you think is the best. Rouslan On Fri, 2011-03-25 at 20:33 +0100, Dirk Haun wrote: > Tom wrote: > > > I believe the 1.7.2 upgrade stuff still needs to be added. > > There is no 1.7. 2 upgrade stuff. > > The only thing missing is the version number 1.7.2 in that list in the install script somewhere that acts as a fallback when it can't identify the Geeklog version. I'll add that. > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Fri Mar 25 17:18:52 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 25 Mar 2011 17:18:52 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <31D0272B-9A00-4ECA-BDC6-4B5C7CA199D5@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01cb01cbeb23$45966ce0$d0c346a0$@cogeco.net> <271EE693-ED44-40B4-9118-10A86EABA7C9@haun-online.de> <31D0272B-9A00-4ECA-BDC6-4B5C7CA199D5@haun-online.de> Message-ID: <01cc01cbeb32$3e8f6c30$bbae4490$@cogeco.net> >>Okay, I see what you mean now (or did you?) - the install script jumps from 1.7.1 to 1.8.0 directly. Doesn't hurt (since there were no DB changes in 1.7.2), but it should also handle 1.7.2 in that case statement. Yeah that's what I meant. The file names need to be changed along with the case statement (which I guess is already there). 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: March-25-11 3:36 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > Tom wrote: > >> I believe the 1.7.2 upgrade stuff still needs to be added. > > There is no 1.7. 2 upgrade stuff. Okay, I see what you mean now (or did you?) - the install script jumps from 1.7.1 to 1.8.0 directly. Doesn't hurt (since there were no DB changes in 1.7.2), but it should also handle 1.7.2 in that case statement. The entry I thought was missing was already there, though ... bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Fri Mar 25 17:37:42 2011 From: websitemaster at cogeco.net (Tom) Date: Fri, 25 Mar 2011 17:37:42 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> Message-ID: <01d601cbeb34$df4fd950$9def8bf0$@cogeco.net> Do we decide on what OAuth account types to allow? Is Facebook enough or should we have Twitter and/or LinkedIn? Also Dirk we will need to create an application for each OAuth account type we choose (so we can get the keys). These will have to be created under someone's account at each service. Do you want to do this or should I? 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: March-25-11 1:51 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > Beta 1 release on March 27. Everyone still on track for this coming Sunday? There seems to be only one bug open, according to the Roadmap view. Just checking if anything important is missing. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From jmucchiello at yahoo.com Fri Mar 25 21:07:11 2011 From: jmucchiello at yahoo.com (Joe Mucchiello) Date: Fri, 25 Mar 2011 18:07:11 -0700 (PDT) Subject: [geeklog-devel] Geeklog 1.8.0 release schedule Message-ID: <320242.67603.qm@web31405.mail.mud.yahoo.com> >> Beta 1 release on March 27. > > Everyone still on track for this coming Sunday? There seems to be only one > bug open, according to the Roadmap view. Just checking if anything > important is missing. > > bye, Dirk I never got the time to update the core patch for private groups. I might be able to look at it tomorrow but I suspect that's not a lot time before Sunday. Joe From dirk at haun-online.de Sat Mar 26 11:30:32 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Mar 2011 16:30:32 +0100 Subject: [geeklog-devel] XMLSitemap Admin Message-ID: Hmm. I was just testing the Migration option with a copy of the geeklog.net database. It failed: 1062: Duplicate entry 'XMLSitemap Admin' for key 'grp_name'. SQL in question: INSERT INTO groups (grp_name, grp_descr, grp_gl_core) VALUES ('XMLSitemap Admin', 'Has full access to XMLSitemap features', 0); So we do already have a XMLSitemap Admin group (and a xmlsitemap.edit) permission on geeklog.net. Not sure where it's coming from, though, since I don't see it on any other site where the plugin is installed. Probably from an earlier version of the plugin, before we started bundling it with Geeklog. Anyone else seeing it? Anyway, I guess that needs to be handled ... bye, Dirk From websitemaster at cogeco.net Sat Mar 26 11:49:16 2011 From: websitemaster at cogeco.net (Tom) Date: Sat, 26 Mar 2011 11:49:16 -0400 Subject: [geeklog-devel] XMLSitemap Admin In-Reply-To: References: Message-ID: <01fb01cbebcd$5ca7b970$15f72c50$@cogeco.net> Nope. -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: March-26-11 11:31 AM To: Geeklog Development Subject: [geeklog-devel] XMLSitemap Admin Hmm. I was just testing the Migration option with a copy of the geeklog.net database. It failed: 1062: Duplicate entry 'XMLSitemap Admin' for key 'grp_name'. SQL in question: INSERT INTO groups (grp_name, grp_descr, grp_gl_core) VALUES ('XMLSitemap Admin', 'Has full access to XMLSitemap features', 0); So we do already have a XMLSitemap Admin group (and a xmlsitemap.edit) permission on geeklog.net. Not sure where it's coming from, though, since I don't see it on any other site where the plugin is installed. Probably from an earlier version of the plugin, before we started bundling it with Geeklog. Anyone else seeing it? Anyway, I guess that needs to be handled ... bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sat Mar 26 12:12:02 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Mar 2011 17:12:02 +0100 Subject: [geeklog-devel] DB_insertId and the link identifier Message-ID: <26B3D99D-90CC-44DD-AA26-F802168801FD@haun-online.de> The MS SQL driver contains a big fat warning not to call DB_insertId without a link identifier since it could potentially return the last insert id from some other connection. So far, so good. The problem, though, is that there is no valid way to get the current link identifier in the first place, since it's a local variable in the DB class. So, would it not make more sense that if the link identifier is empty, to use $this->_db instead, i.e. the link identifier which was used to establish the DB connection for this instance? The same is probably true for MySQL. The Postgres driver does things differently and doesn't use the link identifier at all, so it looks like it isn't a problem there. There are quite a few places in Geeklog where we call DB_insertId without a link identifier, e.g. in lib-comment.php bye, Dirk From cordiste at free.fr Sat Mar 26 13:25:47 2011 From: cordiste at free.fr (cordiste) Date: Sat, 26 Mar 2011 18:25:47 +0100 Subject: [geeklog-devel] XMLSitemap Admin In-Reply-To: References: Message-ID: http://eight.pairlist.net/pipermail/geeklog-cvs/2009-May/005867.html Thank you to google search ;) Ben 2011/3/26 Dirk Haun : > Hmm. I was just testing the Migration option with a copy of the geeklog.net database. It failed: > > 1062: Duplicate entry 'XMLSitemap Admin' for key 'grp_name'. SQL in question: INSERT INTO groups (grp_name, grp_descr, grp_gl_core) VALUES ('XMLSitemap Admin', 'Has full access to XMLSitemap features', 0); > > So we do already have a XMLSitemap Admin group (and a xmlsitemap.edit) permission on geeklog.net. Not sure where it's coming from, though, since I don't see it on any other site where the plugin is installed. Probably from an earlier version of the plugin, before we started bundling it with Geeklog. Anyone else seeing it? > > Anyway, I guess that needs to be handled ... > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From dirk at haun-online.de Sat Mar 26 13:48:37 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Mar 2011 18:48:37 +0100 Subject: [geeklog-devel] XMLSitemap Admin In-Reply-To: References: Message-ID: cordiste wrote: > http://eight.pairlist.net/pipermail/geeklog-cvs/2009-May/005867.html > > Thank you to google search ;) Good catch. Thanks. Well, I guess I need to have a word with that guy for not cleaning up the database ... bye, Dirk From Randy.Kolenko at nextide.ca Sat Mar 26 14:42:55 2011 From: Randy.Kolenko at nextide.ca (Randy Kolenko) Date: Sat, 26 Mar 2011 14:42:55 -0400 Subject: [geeklog-devel] DB_insertId and the link identifier Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F383979@nex-pluto.nextide.ca> The mssql driver works fine without that link identifier. I put that big fat warning in there originally as the original development of the driver didn't seem to work properly without it. > -----Original Message----- > From: Dirk Haun [mailto:dirk at haun-online.de] > Sent: Saturday, March 26, 2011 12:12 PM > To: Geeklog Development > Subject: [geeklog-devel] DB_insertId and the link identifier > > The MS SQL driver contains a big fat warning not to call DB_insertId > without a link identifier since it could potentially return the last > insert id from some other connection. So far, so good. The problem, > though, is that there is no valid way to get the current link > identifier in the first place, since it's a local variable in the DB > class. > > So, would it not make more sense that if the link identifier is empty, > to use $this->_db instead, i.e. the link identifier which was used to > establish the DB connection for this instance? > > The same is probably true for MySQL. The Postgres driver does things > differently and doesn't use the link identifier at all, so it looks > like it isn't a problem there. > > There are quite a few places in Geeklog where we call DB_insertId > without a link identifier, e.g. in lib-comment.php > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sat Mar 26 15:03:22 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Mar 2011 20:03:22 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <01d601cbeb34$df4fd950$9def8bf0$@cogeco.net> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01d601cbeb34$df4fd950$9def8bf0$@cogeco.net> Message-ID: Tom wrote: > Do we decide on what OAuth account types to allow? Is Facebook enough or > should we have Twitter and/or LinkedIn? > > Also Dirk we will need to create an application for each OAuth account type > we choose (so we can get the keys). These will have to be created under > someone's account at each service. Do you want to do this or should I? I just registered a Twitter application "geeklog.net" (since "Geeklog" was already taken). I'm not on Facebook and don't intend to join but I guess we should have it as an option on geeklog.net. Would you register it? Do we need LinkedIn? Not sure if a lot of people would use it. bye, Dirk From dirk at haun-online.de Sat Mar 26 15:15:26 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 26 Mar 2011 20:15:26 +0100 Subject: [geeklog-devel] DB_insertId and the link identifier In-Reply-To: <063B8B70CB9DA141B2FC1DB483561B9F383979@nex-pluto.nextide.ca> References: <063B8B70CB9DA141B2FC1DB483561B9F383979@nex-pluto.nextide.ca> Message-ID: <5A8B4B85-D5A3-4994-9CD0-D93B7B098364@haun-online.de> Randy Kolenko wrote: > The mssql driver works fine without that link identifier. > I put that big fat warning in there originally as the original > development of the driver didn't seem to work properly without it. Thanks. So I guess that comment can be removed? bye, Dirk From websitemaster at cogeco.net Sun Mar 27 09:11:03 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 27 Mar 2011 09:11:03 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <46E08747-723C-47BA-9CB4-2176F8257C44@haun-online.de> <01d601cbeb34$df4fd950$9def8bf0$@cogeco.net> Message-ID: <024901cbec80$6cf13ff0$46d3bfd0$@cogeco.net> >> I'm not on Facebook and don't intend to join but I guess we should have it as an option on geeklog.net. Would you register it? I will do it today and send you the details. 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: March-26-11 3:03 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule Tom wrote: > Do we decide on what OAuth account types to allow? Is Facebook enough > or should we have Twitter and/or LinkedIn? > > Also Dirk we will need to create an application for each OAuth account > type we choose (so we can get the keys). These will have to be created > under someone's account at each service. Do you want to do this or should I? I just registered a Twitter application "geeklog.net" (since "Geeklog" was already taken). I'm not on Facebook and don't intend to join but I guess we should have it as an option on geeklog.net. Would you register it? Do we need LinkedIn? Not sure if a lot of people would use it. bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Sun Mar 27 12:33:05 2011 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 27 Mar 2011 18:33:05 +0200 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Message-ID: I ran into a tiny little last-minute problem ... I've set the Geeklog version number to 1.8.0b1. All the bundled plugins require Geeklog 1.8.0. Due to the new version check, however, they all refuse to install since 1.8.0b1 < 1.8.0 Oops ... Not sure how to go from here. The comparison is correct - it's the data that isn't. So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), but that looks odd, though it would be technically correct. Opinions? bye, Dirk From websitemaster at cogeco.net Sun Mar 27 13:35:48 2011 From: websitemaster at cogeco.net (Tom) Date: Sun, 27 Mar 2011 13:35:48 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Message-ID: <025301cbeca5$6938a4f0$3ba9eed0$@cogeco.net> Hmmmm.... >> So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), but that looks odd I agree and it may confuse some users. I am not sure if this would work but could we make the new version check just worry about the 1.8.0 part and anything past the third number will be assumed to be compatible? This would mean no new features or DB changes could take place in a beta, service release, etc. I am not sure if this would work for how Geeklog JP distinguishes between their upgraded japan versions of some plugins though... Another idea would be to have a standard way for beta, service release and release candidate version numbers. For example if 1.8.0b## is found then it is assumed a beta and will consider 1.8.0 and 1.8.0b## to be compatible. We could then use sr for service release (1.8.0sr##) and rs for release candidate (or whatever we decide) I think I like the second idea better 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: March-27-11 12:33 PM To: Geeklog Development Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule I ran into a tiny little last-minute problem ... I've set the Geeklog version number to 1.8.0b1. All the bundled plugins require Geeklog 1.8.0. Due to the new version check, however, they all refuse to install since 1.8.0b1 < 1.8.0 Oops ... Not sure how to go from here. The comparison is correct - it's the data that isn't. So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), but that looks odd, though it would be technically correct. Opinions? bye, Dirk _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Sun Mar 27 14:07:51 2011 From: rouslan at placella.com (Rouslan Placella) Date: Sun, 27 Mar 2011 19:07:51 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <025301cbeca5$6938a4f0$3ba9eed0$@cogeco.net> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <025301cbeca5$6938a4f0$3ba9eed0$@cogeco.net> Message-ID: <1301249271.6572.37.camel@roccivic-pc> Hmmm indeed... I didn't foresee this problem at all when implementing plugin version control. But yeah, after the version is fed to COM_versionConvert(), 1.8.0 becomes 1.8.0.0.3.0 and 1.8.0b1 becomes 1.8.0.0.1.0 So, as Dirk mentioned, the logic is correct when 1.8.0b1 < 1.8.0. I'm guessing that we should update the plugin requirements to look for 1.8.0b1 for this beta release and then we look further into this issue later and maybe create a way to override these settings. Rouslan On Sun, 2011-03-27 at 13:35 -0400, Tom wrote: > Hmmmm.... > > >> So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), but > that looks odd > > I agree and it may confuse some users. > > I am not sure if this would work but could we make the new version check > just worry about the 1.8.0 part and anything past the third number will be > assumed to be compatible? This would mean no new features or DB changes > could take place in a beta, service release, etc. I am not sure if this > would work for how Geeklog JP distinguishes between their upgraded japan > versions of some plugins though... > > Another idea would be to have a standard way for beta, service release and > release candidate version numbers. > > For example if 1.8.0b## is found then it is assumed a beta and will consider > 1.8.0 and 1.8.0b## to be compatible. > > We could then use sr for service release (1.8.0sr##) and rs for release > candidate (or whatever we decide) > > I think I like the second idea better > > 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: March-27-11 12:33 PM > To: Geeklog Development > Subject: Re: [geeklog-devel] Geeklog 1.8.0 release schedule > > I ran into a tiny little last-minute problem ... > > I've set the Geeklog version number to 1.8.0b1. All the bundled plugins > require Geeklog 1.8.0. Due to the new version check, however, they all > refuse to install since 1.8.0b1 < 1.8.0 > > Oops ... > > Not sure how to go from here. The comparison is correct - it's the data that > isn't. So the plugins could indicate that they require 1.8.0b1 (or 1.8.0hg), > but that looks odd, though it would be technically correct. > > Opinions? > > bye, Dirk > > _______________________________________________ > 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 dirk at haun-online.de Mon Mar 28 15:06:47 2011 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 28 Mar 2011 21:06:47 +0200 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> Message-ID: <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> > I've set the Geeklog version number to 1.8.0b1. All the bundled plugins require Geeklog 1.8.0. Due to the new version check, however, they all refuse to install since 1.8.0b1 < 1.8.0 Well, I've changed the version number back to just 1.8.0 for now. That way, it'll install the plugins. That would probably be fine for a beta but still needs a solution for RCs and the final release. Rouslan had an idea (from IRC): roccivic ? how about checking if we are running a beta/rc and if yes, to limit the comparison to the first three numbers in the version? I guess that could work: As long as we're in "prerelease mode", ignore the details. bye, Dirk From rouslan at placella.com Mon Mar 28 16:36:41 2011 From: rouslan at placella.com (Rouslan Placella) Date: Mon, 28 Mar 2011 21:36:41 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> Message-ID: <1301344601.2307.9.camel@roccivic-pc> Proposed patch to fix this issue: http://www.placella.com/gl/rev8203.patch.gz It will basically give a free upgrade from 'beta' and 'rc' to 'stable' to the geeklog installation. And, of course, there will be no free upgrades to the versions that we are comparing to. I couldn't think of anything better right now. What do you guys think? Rouslan On Mon, 2011-03-28 at 21:06 +0200, Dirk Haun wrote: > > I've set the Geeklog version number to 1.8.0b1. All the bundled plugins require Geeklog 1.8.0. Due to the new version check, however, they all refuse to install since 1.8.0b1 < 1.8.0 > > Well, I've changed the version number back to just 1.8.0 for now. That way, it'll install the plugins. That would probably be fine for a beta but still needs a solution for RCs and the final release. > > Rouslan had an idea (from IRC): > > roccivic ? how about checking if we are running a beta/rc and if yes, to limit the comparison to the first three numbers in the version? > > I guess that could work: As long as we're in "prerelease mode", ignore the details. > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From rouslan at placella.com Mon Mar 28 16:58:31 2011 From: rouslan at placella.com (Rouslan Placella) Date: Mon, 28 Mar 2011 21:58:31 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <1301344601.2307.9.camel@roccivic-pc> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> <1301344601.2307.9.camel@roccivic-pc> Message-ID: <1301345911.2307.11.camel@roccivic-pc> That last patch didn't actually work, so let's try one more time: http://www.placella.com/gl/rev8205.patch.gz Rouslan On Mon, 2011-03-28 at 21:36 +0100, Rouslan Placella wrote: > Proposed patch to fix this issue: > http://www.placella.com/gl/rev8203.patch.gz > It will basically give a free upgrade from 'beta' and 'rc' to 'stable' > to the geeklog installation. And, of course, there will be no free > upgrades to the versions that we are comparing to. I couldn't think of > anything better right now. What do you guys think? > > Rouslan > > > On Mon, 2011-03-28 at 21:06 +0200, Dirk Haun wrote: > > > I've set the Geeklog version number to 1.8.0b1. All the bundled plugins require Geeklog 1.8.0. Due to the new version check, however, they all refuse to install since 1.8.0b1 < 1.8.0 > > > > Well, I've changed the version number back to just 1.8.0 for now. That way, it'll install the plugins. That would probably be fine for a beta but still needs a solution for RCs and the final release. > > > > Rouslan had an idea (from IRC): > > > > roccivic ? how about checking if we are running a beta/rc and if yes, to limit the comparison to the first three numbers in the version? > > > > I guess that could work: As long as we're in "prerelease mode", ignore the details. > > > > bye, Dirk > > > > _______________________________________________ > > 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 dirk at haun-online.de Tue Mar 29 14:38:45 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 29 Mar 2011 20:38:45 +0200 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <1301345911.2307.11.camel@roccivic-pc> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> <1301344601.2307.9.camel@roccivic-pc> <1301345911.2307.11.camel@roccivic-pc> Message-ID: <8EB8F578-E76D-4009-A000-2CEA912A909A@haun-online.de> Rouslan Placella wrote: > That last patch didn't actually work, so let's try one more time: > http://www.placella.com/gl/rev8205.patch.gz Clever. But doesn't that somewhat restrict the use of COM_versionCompare? What happens if a plugin happens to have the same version number as Geeklog? The version number of the Static Pages plugin happened to be in sync with Geeklog's version number for a couple of releases, for example. bye, Dirk From rouslan at placella.com Tue Mar 29 14:46:59 2011 From: rouslan at placella.com (Rouslan Placella) Date: Tue, 29 Mar 2011 19:46:59 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <8EB8F578-E76D-4009-A000-2CEA912A909A@haun-online.de> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> <1301344601.2307.9.camel@roccivic-pc> <1301345911.2307.11.camel@roccivic-pc> <8EB8F578-E76D-4009-A000-2CEA912A909A@haun-online.de> Message-ID: <1301424419.5478.3.camel@roccivic-pc> That's why in this patch I switched to using the plain 'version_compare' for plugins and databases and only used COM_versionCompare() for Geeklog itself. Rouslan On Tue, 2011-03-29 at 20:38 +0200, Dirk Haun wrote: > Rouslan Placella wrote: > > > That last patch didn't actually work, so let's try one more time: > > http://www.placella.com/gl/rev8205.patch.gz > > Clever. But doesn't that somewhat restrict the use of COM_versionCompare? What happens if a plugin happens to have the same version number as Geeklog? The version number of the Static Pages plugin happened to be in sync with Geeklog's version number for a couple of releases, for example. > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From dirk at haun-online.de Tue Mar 29 16:27:27 2011 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 29 Mar 2011 22:27:27 +0200 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: <1301424419.5478.3.camel@roccivic-pc> References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> <1301344601.2307.9.camel@roccivic-pc> <1301345911.2307.11.camel@roccivic-pc> <8EB8F578-E76D-4009-A000-2CEA912A909A@haun-online.de> <1301424419.5478.3.camel@roccivic-pc> Message-ID: Rouslan Placella wrote: > That's why in this patch I switched to using the plain 'version_compare' > for plugins and databases and only used COM_versionCompare() for Geeklog > itself. Hmm. Did we say that COM_versionCompare is only meant to compare Geeklog version numbers? Or was it supposed to be used for Geeklog-style version numbers, i.e. could plugins also make use of it for their own version numbers? bye, Dirk From rouslan at placella.com Tue Mar 29 18:25:45 2011 From: rouslan at placella.com (Rouslan Placella) Date: Tue, 29 Mar 2011 23:25:45 +0100 Subject: [geeklog-devel] Geeklog 1.8.0 release schedule In-Reply-To: References: <54636157-3A9E-4368-BE46-DAD505FA5BD6@haun-online.de> <57B5EA23-D01B-454D-A9B8-60751C5DC922@haun-online.de> <1301344601.2307.9.camel@roccivic-pc> <1301345911.2307.11.camel@roccivic-pc> <8EB8F578-E76D-4009-A000-2CEA912A909A@haun-online.de> <1301424419.5478.3.camel@roccivic-pc> Message-ID: <1301437545.4469.10.camel@roccivic-pc> I think that no-one explicitly defined the use cases for this function. Initially I also thought that it may be useful for plugins, but now I guess that I'm changing my mind. IIRC the problem with the plain version_compare() were mostly the bugfix suffixes, but do plugins make use of these? Rouslan On Tue, 2011-03-29 at 22:27 +0200, Dirk Haun wrote: > Rouslan Placella wrote: > > > That's why in this patch I switched to using the plain 'version_compare' > > for plugins and databases and only used COM_versionCompare() for Geeklog > > itself. > > Hmm. Did we say that COM_versionCompare is only meant to compare Geeklog version numbers? Or was it supposed to be used for Geeklog-style version numbers, i.e. could plugins also make use of it for their own version numbers? > > bye, Dirk > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From websitemaster at cogeco.net Thu Mar 31 11:40:19 2011 From: websitemaster at cogeco.net (Tom) Date: Thu, 31 Mar 2011 11:40:19 -0400 Subject: [geeklog-devel] Geeklog 1.8.0 Beta release Message-ID: <00c101cbefb9$f0e5eea0$d2b1cbe0$@cogeco.net> Hey Dirk, I have a few Wiki pages I need to finish up for the release, is there anything else you need help with at the moment? Tom