From dirk at haun-online.de Mon Jan 5 09:14:52 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 05 Jan 2009 15:14:52 +0100 Subject: [geeklog-devel] Still offline ... Message-ID: <20090105151452.gado16jmec0g40o0@webmail.df.eu> FYI: I'm still offline. Why do all ISPs suck and why can you never reach somebody on a hotline between Christmas and New Year? Oh well. I hope to get this resolved finally some time this week ... As you can see from the Mercurial repository, I've spent some time with the install script and plugin installation. More on the latter later, but the install script is now in a state that I consider usable. It could use some makeup on the first page, though (Matt?). Haven't seen much activity lately. How are things regarding porting Sami's and Jared's changes over? Oh, and a Happy New Year to all :) bye, Dirk From devel at portalparts.com Tue Jan 6 09:26:38 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 06 Jan 2009 09:26:38 -0500 Subject: [geeklog-devel] Still offline ... In-Reply-To: <20090105151452.gado16jmec0g40o0@webmail.df.eu> References: <20090105151452.gado16jmec0g40o0@webmail.df.eu> Message-ID: Happy New Year! Dirk and hopefully, your internet will be restored this year. You should pay your bills on time :) I have been working on a few more net new items but they are not yet ready to surface. - Blaine Dirk Haun wrote: > FYI: I'm still offline. Why do all ISPs suck and why can you never > reach somebody on a hotline between Christmas and New Year? Oh well. I > hope to get this resolved finally some time this week ... > > As you can see from the Mercurial repository, I've spent some time > with the install script and plugin installation. More on the latter > later, but the install script is now in a state that I consider > usable. It could use some makeup on the first page, though (Matt?). > > Haven't seen much activity lately. How are things regarding porting > Sami's and Jared's changes over? > > Oh, and a Happy New Year to all :) > > 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 Jan 7 06:53:45 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 07 Jan 2009 12:53:45 +0100 Subject: [geeklog-devel] RFC: Plugin auto install Message-ID: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> Part of Matt's GSoC project was to make the plugin installation easier. In case you haven't tried out the current version from our Mercurial repository: You can now install plugins by simply uploading their tarball. Also, the bundled plugins have now been properly separated from Geeklog, i.e. they are no longer contained in the mysql_tableanddata.php file. To remove, say, the Polls plugin, you can simply remove its 3 directories from the Geeklog tarball - the rest will still install just fine. One thing we didn't get resolved during the summer was how to handle automatic installation of plugins now. The standard plugin install scripts are made for user interaction and also check for permissions, which simply may not exist during an initial install. So we need a new approach. The idea is that plugins can supply a new file, autoinstall.php. From this file, Geeklog will get the plugin's data (permissions, groups, etc.). The plugin can also provide functions that check the prerequisites and do any post-install operations necessary. Most of the install process, though, will be done by Geeklog now, based on the information it gets from autoinstall.php. If you ever had a look at the plugin install scripts for the bundled plugins in 1.5.x, you'll see that they are pretty generic already and only have a plugin-specific section at their start. All that generic code has now been rolled into Geeklog and the autoinstall.php is simply the new way of that plugin-specific section. There are 4 functions that can be present in an autoinstall.php, only one of which is mandatory: - plugin_autoinstall_foo Provides the information about the plugin: Name, permissions, groups, ... - plugin_load_configuration_foo For plugins using Geeklog's Configuration GUI - plugin_postinstall_foo For any post-install operations that the plugin may need to perform - plugin_compatible_with_this_version_foo To check the prerequisites Only the plugin_autoinstall_ function is required. It should only return information, not perform any operations, as it will be called more than once (and being called doesn't mean that the plugin will be installed). Plugins using an old-style install script will continue to work, of course. They will simply require one extra step (calling the install script) to be installed. All plugin authors: Please have a look at the autoinstall.php files of the bundled plugins - they are pretty straightforward and easy to understand - and let us know if you see any problems with this approach. bye, Dirk P.S. You can get the latest development version by checking it out through Mercurial or download the Nightly Tarball, as explained here: http://www.geeklog.net/staticpages/index.php/CVS From cordiste at free.fr Thu Jan 8 05:11:39 2009 From: cordiste at free.fr (cordiste) Date: Thu, 8 Jan 2009 11:11:39 +0100 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> Message-ID: <364575ed0901080211y2f492140p5923d6f9e856082e@mail.gmail.com> Hello everyone. I wish you an happy Geeklog year :) I try to install Geeklog with the last nightly tarball but the install script don't want to connect to the db. Message is :"Incorrect database information. Sorry, but the database information you entered does not appear to be correct. Please go back and try again." I checked twice and I can install the Geeklog 1.5.1 stable release with the same database informations. ::Ben 2009/1/7 Dirk Haun > > You can get the latest development version by checking it out through Mercurial or download the Nightly Tarball, as explained here: > http://www.geeklog.net/staticpages/index.php/CVS > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From dirk at haun-online.de Thu Jan 8 07:45:32 2009 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 08 Jan 2009 13:45:32 +0100 Subject: [geeklog-devel] RFC: Plugin auto install Message-ID: <20090108134532.0nbbvq0rkk4s44c0@webmail.df.eu> cordiste wrote: > I try to install Geeklog with the last nightly tarball but the install > script don't want to connect to the db. Works for me - just tried it with the same tarball. The only issue I could see is that the db-config.php is named db-config.php.dist (same for siteconfig.php). But then you should get an error message from the install script that it can not find them. I fixed that in the script that creates the tarball now. bye, Dirk From dirk at haun-online.de Tue Jan 13 06:37:59 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 13 Jan 2009 12:37:59 +0100 Subject: [geeklog-devel] RFC: Plugin migration Message-ID: <20090113123759.jl3ty2156m84s0c4@webmail.df.eu> I'm still interested in any feedback from plugin authors regarding the plugin auto install in Geeklog 1.6 [1] In the meantime, here's a somewhat related topic: Migration of plugins. In 1.6, we now have that nifty Migration option in the install script (the other part of Matt's GSoC project). That's what you use when your site moves to another server. It also handles path changes, URL changes, provides warnings about missing files and plugins, etc. When your site's URL changed during the migration, it will also update most of the content now. What's missing are the plugins. So the obvious idea would be to have a PLG_migrate call that informs plugins about the migration and gives them a chance to update paths and URLs where needed. However, the migration can also perform database updates. Which raises the question: What comes first? PLG_upgrade or PLG_migrate? Alternatively, we could call PLG_upgrade for the migration case (with a flag indicating that a migration is underway) and let the plugins figure out the proper order themselves. The downside of this approach is that it would call PLG_upgrade in cases where the plugin doesn't need to be upgraded, which could confuse some plugins. To summarize the options: 1) PLG_upgrade first, then PLG_migrate 2) PLG_migrate first, then PLG_upgrade 3) PLG_upgrade($mode = 'migration') Opinions? bye, Dirk [1] http://eight.pairlist.net/pipermail/geeklog-devel/2009-January/003953.html From devel at portalparts.com Tue Jan 13 23:15:01 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 13 Jan 2009 23:15:01 -0500 Subject: [geeklog-devel] RFC: Plugin migration In-Reply-To: <20090113123759.jl3ty2156m84s0c4@webmail.df.eu> References: <20090113123759.jl3ty2156m84s0c4@webmail.df.eu> Message-ID: Hi Dirk, I have updated my local CVS and am trying to free up my time to test the plugin install out and explore it further before commenting but it sure looks good. Without really getting into the code and working thru a few examples, I am thinking it would be best to migrate and then call upgrade. If there are any new settings for the upgrade, they need to be based on the post migrate version. - Blaine Dirk Haun wrote: > I'm still interested in any feedback from plugin authors regarding the > plugin auto install in Geeklog 1.6 [1] > > In the meantime, here's a somewhat related topic: Migration of plugins. > > In 1.6, we now have that nifty Migration option in the install script > (the other part of Matt's GSoC project). That's what you use when your > site moves to another server. It also handles path changes, URL > changes, provides warnings about missing files and plugins, etc. > > When your site's URL changed during the migration, it will also update > most of the content now. What's missing are the plugins. > > So the obvious idea would be to have a PLG_migrate call that informs > plugins about the migration and gives them a chance to update paths > and URLs where needed. > > However, the migration can also perform database updates. Which raises > the question: What comes first? PLG_upgrade or PLG_migrate? > > Alternatively, we could call PLG_upgrade for the migration case (with > a flag indicating that a migration is underway) and let the plugins > figure out the proper order themselves. The downside of this approach > is that it would call PLG_upgrade in cases where the plugin doesn't > need to be upgraded, which could confuse some plugins. > > To summarize the options: > > 1) PLG_upgrade first, then PLG_migrate > 2) PLG_migrate first, then PLG_upgrade > 3) PLG_upgrade($mode = 'migration') > > Opinions? > > bye, Dirk > > > [1] > http://eight.pairlist.net/pipermail/geeklog-devel/2009-January/003953.html > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From devel at portalparts.com Sat Jan 17 00:27:57 2009 From: devel at portalparts.com (Blaine Lang) Date: Sat, 17 Jan 2009 00:27:57 -0500 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> Message-ID: Dirk, I have been testing the auto-install and the upload feature to create/copy the required directories and files on Windows (Vista) this evening and it's working well. Only issue I had was in creating an archive in the format the PEAR archive class would support. The zip files were being recognized as 'PK' for pkzip I figure and that format is not defined in the class. I found a windows utility to create a compressed TAR (tgz) and that worked fine. It successfully created the directories if they were missing and over-wrote files as required. This definitely will make plugin installs easier. Nice Job! I have an idea now for SOC 2009: Implement a REST based plugin DEPOT service and we can host the plugins on geeklog.net (or other locations). Add blocks to this service adn we will have a way for sites to explore and add components online and query if updates are available - like firefox does. - Blaine From dirk at haun-online.de Sat Jan 17 02:14:07 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 17 Jan 2009 08:14:07 +0100 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> Message-ID: <20090117071407.913559321@smtp.haun-online.de> Blaine Lang wrote: >Only issue I had was in creating an archive in the format the PEAR >archive class would support. The zip files were being recognized as 'PK' >for pkzip I figure and that format is not defined in the class. For .zip file support, you need the Archive_Zip class. We need to add that to the PEAR classes we're shipping. >This definitely will make plugin installs easier. Nice Job! I would hope so :-) >I have an idea now for SOC 2009: Implement a REST based plugin DEPOT That would be the next logical step, yes. I've already thought of a "plugin repository" plugin but didn't have the time to add it to our GSoC ideas list. Doesn't have to be REST, btw. I was thinking plain HTTP_Request and RSS feeds. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From devel at portalparts.com Sat Jan 17 10:38:11 2009 From: devel at portalparts.com (Blaine Lang) Date: Sat, 17 Jan 2009 10:38:11 -0500 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: <20090117071407.913559321@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090117071407.913559321@smtp.haun-online.de> Message-ID: Dirk Haun wrote: > For .zip file support, you need the Archive_Zip class. We need to add that to the PEAR classes we're shipping. I definitely have the PEAR class and I was tracing into the class and why I know the archive type code it was reading when it open'ed the file and effectively returned without uncompressing it. - Blaine From dirk at haun-online.de Sat Jan 17 10:46:45 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 17 Jan 2009 16:46:45 +0100 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090117071407.913559321@smtp.haun-online.de> Message-ID: <20090117154645.1337652114@smtp.haun-online.de> Blaine Lang wrote: >I definitely have the PEAR class and I was tracing into the class and >why I know the archive type code it was reading when it open'ed the >file and effectively returned without uncompressing it. Ah, okay. I did try a few of your plugins and that did work for me. Can you point me to a file that you can not uncompress? Eventually, we should roll all the code for unpacking archives into an unpack class, so that it will be easier to add support for other formats. Or switch to some other way of unpacking, e.g. the Zip extension from PECL. But one step at a time ... bye, Dirk -- http://www.haun-online.de/accu/ From dirk at haun-online.de Sat Jan 17 11:56:55 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 17 Jan 2009 17:56:55 +0100 Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved Message-ID: <20090117165655.1288452353@smtp.haun-online.de> This is the third (and last, I promise) Request For Comments on plugin API changes for Geeklog 1.6. I'm still interested in any feedback on my previous two, regarding Plugin auto install[1] and Plugin migration[2]. Almost 4 years ago[3], Blaine and myself came up with the idea for PLG_itemSaved. The hope was to provide an API into which plugins could hook and that would inform them whenever something was saved in Geeklog, so that they could act on it. Part of the concept was an abort and rollback mechanism, where plugins could report an error and signal to Geeklog (and other plugins) that there was a problem and that the save operation should be aborted. In which case the user would be taken back to the editor where s/he was informed of the problem and could try again. Fast-forward four years and that mechanism has only been implemented for stories. And, looking at the code (in 1.4 and 1.5), not even been implemented correctly. And it hasn't caught on either (i.e. isn't being used by any plugins, to the best of my knowledge). Neither has it been implemented anywhere else. Why is that? I think it's because the API is too complicated. Namely, the abort and rollback isn't really needed. My suggestion would be: Get rid of the abort. When something is saved (a story, a static page, etc.), it calls PLG_itemSaved. Plugins interested in that information can still hook into it, but they can no longer abort the process (why should a plugin be able to tell Geeklog - and the user - that a story should not be saved anyway?). Over the years, we had a lot of scenarios where something like PLG_itemSaved (implemented everywhere) would have come in handy. I think it's time we finally do that. And if the complexity of the API is holding us back here, then we need to fix that. I realize there's also PLG_itemPreSave, which is supposed to be called before the save, and which _can_ cause an abort. We should keep that and implement it everywhere, too, so that every call to PLG_itemSaved is preceded by a call to PLG_itemPreSave. That should handle situations where plugins still want to abort, for whatever reason. Only then it would happen before the object ended up in the database, which gets rid of the rollback and makes things much easier. Comments? bye, Dirk [1] [2] [3] -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Sat Jan 17 12:49:32 2009 From: websitemaster at cogeco.net (Website Master) Date: Sat, 17 Jan 2009 12:49:32 -0500 Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved In-Reply-To: <20090117165655.1288452353@smtp.haun-online.de> References: <20090117165655.1288452353@smtp.haun-online.de> Message-ID: <00b801c978cb$f47a4dc0$dd6ee940$@net> Sounds good, How about a PLG_itemDelete, PLG_itemEdit which will notify plugins and Geeklog about delete or edits of stories and other plugins objects. As example with the rating plugin it would be nice to delete any ratings associated with a story or some other plugin object automatically. While we are the topic some mods to PLG_getItemInfo would be helpful in the future. Along with information like: 'url' - the complete URL of the item 'title' - the item's title or subject 'excerpt' - a short description of the item 'description' - the full description of the item, e.g. the article text some plugins also need information about what table the plugin object(s) is stored in, the name of the id field(s) and security information. Also some plugins have multiple object types, the current API does not handle this. As example the forum has topics and messages. Also it would be a good idea to get the Universal Plugin Toolkit up to speed once everything has been figured out so people know about these APIs (along with the core plugins). Thanks 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: January-17-09 11:57 AM To: geeklog-devel Cc: Geeklog Modules List Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved This is the third (and last, I promise) Request For Comments on plugin API changes for Geeklog 1.6. I'm still interested in any feedback on my previous two, regarding Plugin auto install[1] and Plugin migration[2]. Almost 4 years ago[3], Blaine and myself came up with the idea for PLG_itemSaved. The hope was to provide an API into which plugins could hook and that would inform them whenever something was saved in Geeklog, so that they could act on it. Part of the concept was an abort and rollback mechanism, where plugins could report an error and signal to Geeklog (and other plugins) that there was a problem and that the save operation should be aborted. In which case the user would be taken back to the editor where s/he was informed of the problem and could try again. Fast-forward four years and that mechanism has only been implemented for stories. And, looking at the code (in 1.4 and 1.5), not even been implemented correctly. And it hasn't caught on either (i.e. isn't being used by any plugins, to the best of my knowledge). Neither has it been implemented anywhere else. Why is that? I think it's because the API is too complicated. Namely, the abort and rollback isn't really needed. My suggestion would be: Get rid of the abort. When something is saved (a story, a static page, etc.), it calls PLG_itemSaved. Plugins interested in that information can still hook into it, but they can no longer abort the process (why should a plugin be able to tell Geeklog - and the user - that a story should not be saved anyway?). Over the years, we had a lot of scenarios where something like PLG_itemSaved (implemented everywhere) would have come in handy. I think it's time we finally do that. And if the complexity of the API is holding us back here, then we need to fix that. I realize there's also PLG_itemPreSave, which is supposed to be called before the save, and which _can_ cause an abort. We should keep that and implement it everywhere, too, so that every call to PLG_itemSaved is preceded by a call to PLG_itemPreSave. That should handle situations where plugins still want to abort, for whatever reason. Only then it would happen before the object ended up in the database, which gets rid of the rollback and makes things much easier. Comments? bye, Dirk [1] [2] [3] -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 3773 (20090117) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Sat Jan 17 13:42:17 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 17 Jan 2009 19:42:17 +0100 Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved In-Reply-To: <00b801c978cb$f47a4dc0$dd6ee940$@net> References: <20090117165655.1288452353@smtp.haun-online.de> <00b801c978cb$f47a4dc0$dd6ee940$@net> Message-ID: <20090117184217.1221383915@smtp.haun-online.de> Website Master wrote: >How about a PLG_itemDelete, PLG_itemEdit which will notify plugins and >Geeklog about delete or edits of stories and other plugins objects. A "delete" would certainly make sense. PLG_itemSaved will be called on edit, too. Would that be enough? >While we are the topic some mods to PLG_getItemInfo would be helpful in the >future. Some extensions will be coming in 1.6.0: http://wiki.geeklog.net/wiki/index.php/PLG_getItemInfo >some plugins also need information about what table the plugin object(s) is >stored in, the name of the id field(s) and security information. Not sure if it's a good idea to let plugins mess with other plugin's tables. The actual information you're after should be routed through PLG_getItemInfo instead, IMO. >Also some >plugins have multiple object types, the current API does not handle this. As >example the forum has topics and messages. Okay, so the $type is actually the name of the plugin. I don't see why the forum plugin couldn't provide information about topics through PLG_getItemInfo, though. >Also it would be a good idea to get the Universal Plugin Toolkit up to speed >once everything has been figured out so people know about these APIs (along >with the core plugins). I guess providing a plugin skeleton would help. That should not be based on the plugin API, though, but be rewritten from the ground up to use autoinstall.php and all the nice new APIs. The most important help, however, would be updated documentation. Any volunteers? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Sat Jan 17 14:27:51 2009 From: websitemaster at cogeco.net (Website Master) Date: Sat, 17 Jan 2009 14:27:51 -0500 Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved In-Reply-To: <20090117184217.1221383915@smtp.haun-online.de> References: <20090117165655.1288452353@smtp.haun-online.de> <00b801c978cb$f47a4dc0$dd6ee940$@net> <20090117184217.1221383915@smtp.haun-online.de> Message-ID: <00c901c978d9$b08089a0$11819ce0$@net> >A "delete" would certainly make sense. PLG_itemSaved will be called on >edit, too. Would that be enough? Yup it should be as long as if an id changes in an edit we know the old and the new. >Not sure if it's a good idea to let plugins mess with other plugin's >tables. The actual information you're after should be routed through > PLG_getItemInfo instead, IMO. Your right, I wasn't thinking clearly. I had forgotten that PLG_getItemInfo will supply a URL, Title, and summary (that's what I use the table,id column info for to retrieve the title, desc). I guess PLG_getItemInfo would take care of any security as well. 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: January-17-09 1:42 PM To: geeklog-devel Subject: Re: [geeklog-devel] RFC: Simplifying PLG_itemSaved Website Master wrote: >How about a PLG_itemDelete, PLG_itemEdit which will notify plugins and >Geeklog about delete or edits of stories and other plugins objects. A "delete" would certainly make sense. PLG_itemSaved will be called on edit, too. Would that be enough? >While we are the topic some mods to PLG_getItemInfo would be helpful in the >future. Some extensions will be coming in 1.6.0: http://wiki.geeklog.net/wiki/index.php/PLG_getItemInfo >some plugins also need information about what table the plugin object(s) is >stored in, the name of the id field(s) and security information. Not sure if it's a good idea to let plugins mess with other plugin's tables. The actual information you're after should be routed through PLG_getItemInfo instead, IMO. >Also some >plugins have multiple object types, the current API does not handle this. As >example the forum has topics and messages. Okay, so the $type is actually the name of the plugin. I don't see why the forum plugin couldn't provide information about topics through PLG_getItemInfo, though. >Also it would be a good idea to get the Universal Plugin Toolkit up to speed >once everything has been figured out so people know about these APIs (along >with the core plugins). I guess providing a plugin skeleton would help. That should not be based on the plugin API, though, but be rewritten from the ground up to use autoinstall.php and all the nice new APIs. The most important help, however, would be updated documentation. Any volunteers? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 3773 (20090117) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Sat Jan 17 17:18:00 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 17 Jan 2009 23:18:00 +0100 Subject: [geeklog-devel] Mercurial and line endings Message-ID: <20090117221800.1387857041@smtp.haun-online.de> As can be seen from the recent commits, we have a small problem with line endings. All our files files have Unix line endings (linefeeds). So can our Windows users please try to make sure they *don't* change the line endings (to carriage return + linefeed) when checking things in? Alternatively, someone could try to get these instructions to work: http://www.selenic.com/mercurial/wiki/index.cgi/EncodeDecodeFilter The last section there, "Tempfile example" is what you would need, replacing the **.txt with **.php. You probably need to add additional rules for *.inc, *.html, *.thtml (anything else?). And if someone figures our how that works, please update our wiki page with instructions. Thanks. http://wiki.geeklog.net/wiki/index.php/Using_Mercurial bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From cordiste at free.fr Sun Jan 18 06:47:18 2009 From: cordiste at free.fr (cordiste) Date: Sun, 18 Jan 2009 12:47:18 +0100 Subject: [geeklog-devel] RFC: Plugin auto install In-Reply-To: <20090117154645.1337652114@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090117071407.913559321@smtp.haun-online.de> <20090117154645.1337652114@smtp.haun-online.de> Message-ID: <364575ed0901180347l48cd43ckfc9dc1ffc156f98d@mail.gmail.com> Hello, Yes this morning it's working for me too. Testing with Wampserver, I needed to copy pear files from a geeklog 1.5.1 to the pear folder, then created a .tar archive of captcha plugin 3.1.0. Plugin upload from admin plugins area was ok and then captcha install too. It's work for vthemes plugin 1.5.1.1 too. Very nice feature. ::Ben 2009/1/17 Dirk Haun : > Blaine Lang wrote: > >>I definitely have the PEAR class and I was tracing into the class and >>why I know the archive type code it was reading when it open'ed the >>file and effectively returned without uncompressing it. > > Ah, okay. I did try a few of your plugins and that did work for me. Can > you point me to a file that you can not uncompress? > > Eventually, we should roll all the code for unpacking archives into an > unpack class, so that it will be easier to add support for other > formats. Or switch to some other way of unpacking, e.g. the Zip > extension from PECL. But one step at a time ... > > bye, Dirk > > > -- > http://www.haun-online.de/accu/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From tomw at pigstye.net Sun Jan 18 09:33:48 2009 From: tomw at pigstye.net (tom) Date: Sun, 18 Jan 2009 09:33:48 -0500 Subject: [geeklog-devel] Geeklog Wiki Message-ID: <49733DCC.6010603@pigstye.net> I have been hosting the Geeklog wiki internally since its inception. I am in the process of changing my hosting setup and the wiki will go off line in a few weeks if someone does not step up and take over hosting of the wiki. Any takers? I will ok any changeover with Dirk. Tom From info at heatherengineering.com Sun Jan 18 10:20:40 2009 From: info at heatherengineering.com (Euan McKay) Date: Mon, 19 Jan 2009 00:20:40 +0900 Subject: [geeklog-devel] Geeklog Wiki In-Reply-To: <49733DCC.6010603@pigstye.net> References: <49733DCC.6010603@pigstye.net> Message-ID: Tom, What is the average monthly bandwidth? Euan. On Sun, Jan 18, 2009 at 23:33, tom wrote: > I have been hosting the Geeklog wiki internally since its inception. I am > in the process of changing my hosting setup and the wiki will go off line in > a few weeks if someone does not step up and take over hosting of the wiki. > Any takers? I will ok any changeover with Dirk. > > Tom > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From 1000ideen at gmx.de Sun Jan 18 10:34:32 2009 From: 1000ideen at gmx.de (Markus Wollschlaeger) Date: Sun, 18 Jan 2009 16:34:32 +0100 Subject: [geeklog-devel] Geeklog Wiki Message-ID: <20090118153432.99590@gmx.net> I could also help out with that from Germany. What is the required space and traffic in MB? Thanks, MArkus -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger From dirk at haun-online.de Sun Jan 18 14:15:39 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 18 Jan 2009 20:15:39 +0100 Subject: [geeklog-devel] Summer is coming Message-ID: <20090118191539.146575220@smtp.haun-online.de> So now that we know that the Google Summer of Code is going to happen again this year, it's about time we get our act together. Given that the GSoC will be downsized somewhat (meaning less projects than last year), our application has to be top notch this time. As we know, the list of ideas is very important. So let's have a look at it: http://wiki.geeklog.net/wiki/index.php/Google_Summer_of_Code There's a bunch of ideas there already. Are they still relevant? Do they need to be reviewed or rewritten? What about additional ideas? Better add them early. Also, by the time that Google will make the decision on which projects will take part (mid March, if we go by last year's timeline), I'd like to see a story on the geeklog.net front page that mentions Summer of Code. Preferrably, an announcement of Geeklog 1.6.0 that includes the accomplishments of last year's GSoC. So can we get a 1.6.0 beta out until then? And the finished version before the start of the coding period (really this time)? I would think so. The first stop is 1.5.2, but that is already pretty much finished. The only important issue left is the problem with COM_makeClickableLinks. Sami already has a patch for that and it should land in our Mercurial repository soon (Sami?). Then it's only a short release cycle (1.5.2rc1, followed by the final release a week or two later), if all goes well. So, 1.6.0: Matt's GSoC project is all there and working. Some loose ends to finish (see my RFC posts), but nothing that can't be solved until March. The other two GSoC projects are missing completely, though. Randy / Sami? Mike / Jared? What's the plan? Also, there are over 70 open issues in our bugtracker. The ones that are currently scheduled for 1.6.0 can be seen on the "Roadmap" page. Are those the most important issues to implement for 1.6.0? Are there other issues in the bugtracker that are more important? I'd be willing to sacrifice almost anything if it helps us to get a 1.6.0 out in time. Everybody (users and developers): Please make use of the bugtracker. Indicate interest in issues to be resolved. Check for comments made to issues you may have reported. Report new issues. And finally, an early call for mentors: Who's interested in mentoring a student? Help them see things the Geeklog Way, bring another round of useful features and, hopefully, another couple of permanent members to the Geeklog community. Please apply within :-) bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From tomw at pigstye.net Mon Jan 19 08:54:56 2009 From: tomw at pigstye.net (Tom Willett) Date: Mon, 19 Jan 2009 08:54:56 -0500 Subject: [geeklog-devel] Geeklog Wiki In-Reply-To: <20090118153432.99590@gmx.net> References: <20090118153432.99590@gmx.net> Message-ID: <49748630.7050700@pigstye.net> Markus and Euan -- the wiki gets about 1 million page views a month. I never calculated bandwidth, but it is not bad. The database is about 1.7MB in size. The disk space required is only a standard install of mediawiki. Markus Wollschlaeger wrote: > I could also help out with that from Germany. What is the required space and traffic in MB? > > Thanks, MArkus > -- Tom Willett tomw at pigstye.net From chipper at llamas.net Mon Jan 19 10:44:18 2009 From: chipper at llamas.net (Chris 'Chipper' Chiapusio) Date: Mon, 19 Jan 2009 10:44:18 -0500 Subject: [geeklog-devel] Geeklog Wiki In-Reply-To: <49748630.7050700@pigstye.net> References: <20090118153432.99590@gmx.net> <49748630.7050700@pigstye.net> Message-ID: <20090119154418.GA20179@chipsworld.llamas.net> On Mon, Jan 19, 2009 at 08:54:56AM -0500, Tom Willett wrote: > Markus and Euan -- the wiki gets about 1 million page views a month. I > never calculated bandwidth, but it is not bad. The database is about 1.7MB > in size. The disk space required is only a standard install of mediawiki. > > Markus Wollschlaeger wrote: >> I could also help out with that from Germany. What is the required space and traffic in MB? >> >> Thanks, MArkus >> > > -- > > Tom Willett > tomw at pigstye.net > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel I can provide hosting for it as I've offered in the past. As a side benefit I have experience setting up and maintaining a MediaWiki. Chip -- ------ **** Warning **** This e-mail message, without warrant or warning, and despite US law as set forth in the Foreign Intelligence Surveillance Act of 1978, may be subject to monitoring by the United States National Security Agency and/or the Department of Defense. Information contained in this message may be used against any senders or recipients, now or in the future, in a public trial or secret tribunal. Please encrypt anything important. PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x6CFA486D From dirk at haun-online.de Mon Jan 19 14:14:07 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 19 Jan 2009 20:14:07 +0100 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> Message-ID: <20090119191407.1786996304@smtp.haun-online.de> Blaine Lang wrote: >I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >service and we can host the plugins on geeklog.net (or other locations). >Add blocks to this service adn we will have a way for sites to explore >and add components online and query if updates are available - like >firefox does. First draft: http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From s.m.barakat at googlemail.com Mon Jan 19 17:02:45 2009 From: s.m.barakat at googlemail.com (Sami Barakat) Date: Mon, 19 Jan 2009 22:02:45 +0000 Subject: [geeklog-devel] Summer is coming In-Reply-To: <20090118191539.146575220@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> Message-ID: > The first stop is 1.5.2, but that is already pretty much finished. The > only important issue left is the problem with COM_makeClickableLinks. > Sami already has a patch for that and it should land in our Mercurial > repository soon (Sami?). Then it's only a short release cycle (1.5.2rc1, > followed by the final release a week or two later), if all goes well. > > It should be landing in Mercurial tomorrow hopefully. After committing the code locally I noticed a bug that I was not expecting. When making a comment on a story in plain text it goes through htmlspecialchars before going into COM_makeClickableLinks (which seems logical). So this sort of threw a few things off with some links that were enclosed by quotes or <>. Which reminded me of the original bug post that led to this function being changed in the first place: http://project.geeklog.net/tracking/view.php?id=691 Sami -------------- next part -------------- An HTML attachment was scrubbed... URL: From cordiste at free.fr Mon Jan 19 16:03:38 2009 From: cordiste at free.fr (cordiste) Date: Mon, 19 Jan 2009 22:03:38 +0100 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: <20090119191407.1786996304@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> Message-ID: <364575ed0901191303v20101a73j956f629430b0c62f@mail.gmail.com> Hello, Plugin auto install is a very good feature and plugin repository is a very good idea [ Mode bonus +1 to Blaine :) ]. ::Ben 2009/1/19 Dirk Haun : > Blaine Lang wrote: > >>I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >>service and we can host the plugins on geeklog.net (or other locations). >>Add blocks to this service adn we will have a way for sites to explore >>and add components online and query if updates are available - like >>firefox does. > > First draft: > > http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From devel at portalparts.com Mon Jan 19 17:31:16 2009 From: devel at portalparts.com (Blaine Lang) Date: Mon, 19 Jan 2009 17:31:16 -0500 Subject: [geeklog-devel] Plugin repository In-Reply-To: <364575ed0901191303v20101a73j956f629430b0c62f@mail.gmail.com> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <364575ed0901191303v20101a73j956f629430b0c62f@mail.gmail.com> Message-ID: cordiste wrote: > Hello, > > Plugin auto install is a very good feature and plugin repository is a > very good idea [ Mode bonus +1 to Blaine :) ]. > Thanks Ben but I found out later that Dirk was already thinking of it as well :) Cheers, Blaine From matt.danger.west at gmail.com Mon Jan 19 18:04:18 2009 From: matt.danger.west at gmail.com (Matt West) Date: Mon, 19 Jan 2009 18:04:18 -0500 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: <20090119191407.1786996304@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> Message-ID: A plugin repository is an excellent idea for several reasons: - It centralizes the location of plugins. Users would be able to go and browse through 1 central location for plugins, either from within the Geeklog plugin administration area or through the Geeklog.net site. - It could allow us to better standardize plugin structures and possibly update the plugin development guidelines. The only downsides that I can think of is that we would be adding another hosting service that may carry an additional cost and require additional administration. How will the plugin hosting process work? We may want to think about a moderation process for the public repository to try and mitigate any malicious plugins. I think the way that Adium manages plugins and add-ons works well: http://www.adiumxtras.com Plugin authors need to register with the site (we could just use Geeklog.net accounts) and plugins are reviewed after they're uploaded. My experience when submitting my own plugins has been a 6 hour to 1 day wait. I consider this reasonable. I think this could be extended for Themes as well. On Jan 19, 2009, at 2:14 PM, Dirk Haun wrote: > Blaine Lang wrote: > >> I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >> service and we can host the plugins on geeklog.net (or other >> locations). >> Add blocks to this service adn we will have a way for sites to >> explore >> and add components online and query if updates are available - like >> firefox does. > > First draft: > > http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel From info at heatherengineering.com Mon Jan 19 20:36:48 2009 From: info at heatherengineering.com (Euan McKay) Date: Tue, 20 Jan 2009 10:36:48 +0900 Subject: [geeklog-devel] Geeklog Wiki In-Reply-To: <20090119154418.GA20179@chipsworld.llamas.net> References: <20090118153432.99590@gmx.net> <49748630.7050700@pigstye.net> <20090119154418.GA20179@chipsworld.llamas.net> Message-ID: Thanks for the information Tom. I can offer to host it on my Mosso account - I have enough spare overhead. Also means that it's scalable. No SSH, but that's not needed for MediaWiki and I can give SFTP access and admin control to whoever needs it too. Cheers, Euan. On Tue, Jan 20, 2009 at 00:44, Chris 'Chipper' Chiapusio wrote: > On Mon, Jan 19, 2009 at 08:54:56AM -0500, Tom Willett wrote: >> >> Markus and Euan -- the wiki gets about 1 million page views a month. I >> never calculated bandwidth, but it is not bad. The database is about 1.7MB >> in size. The disk space required is only a standard install of mediawiki. >> >> Markus Wollschlaeger wrote: >>> >>> I could also help out with that from Germany. What is the required space >>> and traffic in MB? >>> >>> Thanks, MArkus >>> >> >> -- >> >> Tom Willett >> tomw at pigstye.net >> >> _______________________________________________ >> geeklog-devel mailing list >> geeklog-devel at lists.geeklog.net >> http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > I can provide hosting for it as I've offered in the past. As a side benefit > I have experience setting up and maintaining a MediaWiki. > > Chip > -- > ------ > **** Warning **** > This e-mail message, without warrant or warning, and despite US law as set > forth in the Foreign Intelligence Surveillance Act of 1978, may be subject > to monitoring by the United States National Security Agency and/or the > Department of Defense. Information contained in this message may be used > against any senders or recipients, now or in the future, in a public trial > or secret tribunal. > Please encrypt anything important. > PGP Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x6CFA486D > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -- ----------------------------------------------------------------------------- Euan McKay PhD Candidate in International Relations Department of Advanced Social and International Studies Graduate School of Arts and Sciences The University of Tokyo From dirk at haun-online.de Tue Jan 20 01:59:12 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 07:59:12 +0100 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> Message-ID: <20090120065912.1982475476@smtp.haun-online.de> Matt West wrote: >The only downsides that I can think of is that we would be adding >another hosting service that may carry an additional cost and require >additional administration. How will the plugin hosting process work? The traffic on geeklog.net could increase ten-fold and we still wouldn't be anywhere near our monthly allowance. So in a way, that would be a nice problem to have ;-) But we should probably ask for something to be built into the repository to allow hosting the files elsewhere. Good point. >http://www.adiumxtras.com I'll have a look at that. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From cordiste at free.fr Tue Jan 20 10:13:33 2009 From: cordiste at free.fr (cordiste) Date: Tue, 20 Jan 2009 16:13:33 +0100 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: <20090119191407.1786996304@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> Message-ID: <364575ed0901200713w72949a96xe7d8687ac0ddd975@mail.gmail.com> Dokuwiki can upload plugins from url, so it can be a good exemple to extend the plugin admin panel in Geeklog to allow download from a plugin repository. See the Dokuwiki plugin For Geeklog. ::Ben 2009/1/19 Dirk Haun : > Blaine Lang wrote: > >>I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >>service and we can host the plugins on geeklog.net (or other locations). >>Add blocks to this service adn we will have a way for sites to explore >>and add components online and query if updates are available - like >>firefox does. > > First draft: > > http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository > > bye, Dirk > > > -- > http://www.geeklog.net/ > http://geeklog.info/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From devel at portalparts.com Tue Jan 20 10:21:16 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 20 Jan 2009 10:21:16 -0500 Subject: [geeklog-devel] Plugin repository In-Reply-To: <20090120065912.1982475476@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <20090120065912.1982475476@smtp.haun-online.de> Message-ID: What if we had a master feed file on geeklog.net that defined the URL's for registered plugin depot's - or it's just a default GL ships with. We can then have a block that returns a listing of updates from these registered depots. Sites should be able to add/remove URL's from this feed so they are not restricted. Users can click on a depot link which redirects them to that site where they get a detailed listing of all updates -- like an RSS Feed does. Maybe we have an area on the Plugin Editor page that also shows available updates or new plugins. This spec should be extended to also support blocks so that we can browse and install blocks on our sites from depot's. From websitemaster at cogeco.net Tue Jan 20 13:19:33 2009 From: websitemaster at cogeco.net (Website Master) Date: Tue, 20 Jan 2009 13:19:33 -0500 Subject: [geeklog-devel] Plugin repository In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <20090120065912.1982475476@smtp.haun-online.de> Message-ID: <014a01c97b2b$a53c6a60$efb53f20$@net> So are you suggesting a new type of plugin? Sort of what a component is to a module in Joomla? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Blaine Lang Sent: January-20-09 10:21 AM To: Geeklog Development Subject: Re: [geeklog-devel] Plugin repository What if we had a master feed file on geeklog.net that defined the URL's for registered plugin depot's - or it's just a default GL ships with. We can then have a block that returns a listing of updates from these registered depots. Sites should be able to add/remove URL's from this feed so they are not restricted. Users can click on a depot link which redirects them to that site where they get a detailed listing of all updates -- like an RSS Feed does. Maybe we have an area on the Plugin Editor page that also shows available updates or new plugins. This spec should be extended to also support blocks so that we can browse and install blocks on our sites from depot's. _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 3780 (20090120) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Tue Jan 20 13:25:29 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 19:25:29 +0100 Subject: [geeklog-devel] Plugin repository In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <20090120065912.1982475476@smtp.haun-online.de> Message-ID: <20090120182529.555101088@smtp.haun-online.de> Blaine Lang wrote: >What if we had a master feed file on geeklog.net that defined the URL's >for registered plugin depot's - or it's just a default GL ships with. I haven't given the "discovery" of new repositories much thought. Only acknowledged that we need a way to do it ... >Users can click on a depot link which redirects them to that site where >they get a detailed listing of all updates -- like an RSS Feed does. Which would require minimal effort if the plugin repository would publish RSS (or Atom) feeds, as suggested. >Maybe we have an area on the Plugin Editor page that also shows >available updates or new plugins. Yep. I also think that plugins could come with their own update feed. So maybe I'm not interested in any new plugins from repository X, but I'm certainly interested in updates for the plugin that I just installed. >This spec should be extended to also support blocks so that we can >browse and install blocks on our sites from depot's. Hmm. We don't have the necessary infrastructure in place (in Geeklog) to do that. And I don't think I like the idea of some process messing around in lib-custom.php (to add the block code). Why not go the mini-plugin route? All you would need is a functions.inc and a autoinstall.php, both neatly placed in a directory. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Tue Jan 20 13:34:29 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 19:34:29 +0100 Subject: [geeklog-devel] Plugin repository In-Reply-To: <014a01c97b2b$a53c6a60$efb53f20$@net> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <20090120065912.1982475476@smtp.haun-onli ne.de> <014a01c97b2b$a53c6a60$efb53f20$@net> Message-ID: <20090120183429.1099748730@smtp.haun-online.de> Website Master wrote: >So are you suggesting a new type of plugin? Sort of what a component is to a >module in Joomla? I, at least, wasn't :) I would make the autoinstall.php a requirement for inclusion in a plugin repository. But we shouldn't forget that this upload / install over the internet process will not work for all of our users. So plugins should still be downloadable and installable the old way. Of course, for those that can use the new process, we should make it a pleasant and convenient experience (ugh - excuse the marketing speak ...). bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Tue Jan 20 13:39:31 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 19:39:31 +0100 Subject: [geeklog-devel] [geeklog-cvs] geeklog: Update FCKeditor to ver 2.6.4 In-Reply-To: References: Message-ID: <20090120183931.1404493254@smtp.haun-online.de> >description: >Update FCKeditor to ver 2.6.4 That's still in beta, isn't it? Btw, I had to do a merge after downloading these changes. Please make sure that your local repository is up to date before you push anything. Thanks. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From devel at portalparts.com Tue Jan 20 13:48:09 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 20 Jan 2009 13:48:09 -0500 Subject: [geeklog-devel] [geeklog-cvs] geeklog: Update FCKeditor to ver 2.6.4 In-Reply-To: <20090120183931.1404493254@smtp.haun-online.de> References: <20090120183931.1404493254@smtp.haun-online.de> Message-ID: It is but has a number of good fixes and enhancements included. My local repository was taken from Sunday - what was changed in the FCKeditor directory that needed merging? I had a warning and needed to use the force option but figured that had something to do with the size of my update and the related directories and files. I was updating 100's of files. - Blaine Dirk Haun wrote: >> description: >> Update FCKeditor to ver 2.6.4 >> > > That's still in beta, isn't it? > > Btw, I had to do a merge after downloading these changes. Please make > sure that your local repository is up to date before you push anything. > Thanks. > > bye, Dirk > > > From devel at portalparts.com Tue Jan 20 13:54:20 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 20 Jan 2009 13:54:20 -0500 Subject: [geeklog-devel] Plugin repository In-Reply-To: <20090120182529.555101088@smtp.haun-online.de> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <20090120065912.1982475476@smtp.haun-online.de> <20090120182529.555101088@smtp.haun-online.de> Message-ID: Dirk Haun wrote: > Hmm. We don't have the necessary infrastructure in place (in Geeklog) to > do that. And I don't think I like the idea of some process messing > around in lib-custom.php (to add the block code). > > Why not go the mini-plugin route? All you would need is a functions.inc > and a autoinstall.php, both neatly placed in a directory. > > Dirk Maybe we need a new blocks directory where we could auto-install from an archive pulled down from the depot. Each block would have it's own directory and related code. We would also need a public_html directory to contain any needed resources. We can leverage much from the plugin auto-install structure but I think it would be best to keep them separate from plugins. - Blaine From dirk at haun-online.de Tue Jan 20 14:10:32 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 20:10:32 +0100 Subject: [geeklog-devel] [geeklog-cvs] geeklog: Update FCKeditor to ver 2.6.4 In-Reply-To: References: <20090120183931.1404493254@smtp.haun-online.de> Message-ID: <20090120191032.1380762278@smtp.haun-online.de> Blaine Lang wrote: >My local repository was taken from Sunday - what was changed in the >FCKeditor directory that needed merging? It's just the way a DVCS works: We were doing changes on our local repositories in parallel. >I had a warning and needed to use the force option Don't use the force, Luke. bye, Dirk -- http://www.haun-online.de/accu/ From dirk at haun-online.de Tue Jan 20 15:19:33 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 20 Jan 2009 21:19:33 +0100 Subject: [geeklog-devel] Summer is coming In-Reply-To: <20090118191539.146575220@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> Message-ID: <20090120201933.1261847081@smtp.haun-online.de> Dirk Haun wrote: >So now that we know that the Google Summer of Code is going to happen >again this year Btw, Google are developing a new web application to run Summer of Code- type of events, codenamed "Melange". If anyone's interested in learning more about it, here's your chance: It's open source, written in Python, runs on top of the Google App Engine - and they're looking for contributors. So in case anyone wants to do some Python on the side ... bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Wed Jan 21 14:21:12 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 21 Jan 2009 20:21:12 +0100 Subject: [geeklog-devel] Geeklog 1.5.2 and 1.6.0 (was: Summer is coming) In-Reply-To: <20090118191539.146575220@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> Message-ID: <20090121192112.1018844967@smtp.haun-online.de> >The first stop is 1.5.2, but that is already pretty much finished. Sami's patches for COM_makeClickableLinks have now landed (thanks!), so from my point of view, 1.5.2 is finished (apart from stuff like documentation updates and maybe some language files). I'd say we release 1.5.2rc1 next weekend, followed by the final version a week or two later (depending on feedback). And then on to 1.6.0. Looking at the calendar, I'd say we should commit to having a beta out by March 1st. That's 5 weeks from now. It should, at the very least, include Jared's and Sami's projects in a working condition. As mentioned before, I'd consider anything else optional, but I'm sure we'll find enough time to address a variety of issues from the bugtracker. So let's review them and see what looks doable. I'll start working on the plugin API changes next. Last chance for comments ... bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From devel at portalparts.com Thu Jan 22 10:21:46 2009 From: devel at portalparts.com (Blaine Lang) Date: Thu, 22 Jan 2009 10:21:46 -0500 Subject: [geeklog-devel] Geeklog 1.5.2 and 1.6.0 In-Reply-To: <20090121192112.1018844967@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> <20090121192112.1018844967@smtp.haun-online.de> Message-ID: Dirk, Is 1.6 only what is on the roadmap page as I'd like to open this up for discussion or understand if some of the ideas we have been discussing are to in a 1.7 and follow shortly after 1.6. http://project.geeklog.net/tracking/roadmap_page.php Blaine Dirk Haun wrote: >> The first stop is 1.5.2, but that is already pretty much finished. >> > > Sami's patches for COM_makeClickableLinks have now landed (thanks!), so > from my point of view, 1.5.2 is finished (apart from stuff like > documentation updates and maybe some language files). > > I'd say we release 1.5.2rc1 next weekend, followed by the final version > a week or two later (depending on feedback). > > > And then on to 1.6.0. > > Looking at the calendar, I'd say we should commit to having a beta out > by March 1st. That's 5 weeks from now. It should, at the very least, > include Jared's and Sami's projects in a working condition. > > As mentioned before, I'd consider anything else optional, but I'm sure > we'll find enough time to address a variety of issues from the > bugtracker. So let's review them and see what looks doable. > > I'll start working on the plugin API changes next. Last chance for > comments ... > > bye, Dirk > > > From s.m.barakat at googlemail.com Thu Jan 22 11:35:53 2009 From: s.m.barakat at googlemail.com (Sami Barakat) Date: Thu, 22 Jan 2009 16:35:53 +0000 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks Message-ID: Before some people start seeing unexpected result from the new COM_makeClickableLinks function this is just a little word of warning. The function relies on the text being passed through htmlspecialchars first. So: $text = htmlspecialchars($text); $text = COM_makeClickableLinks($text); This is due to difficulties recognising both & and & in the url as well as terminating before reaching any other entities, such as " or   It should not be much of an issue as the only places this function is used in are the files: lib-comment.php, story.class.php, lib-admin.php and SLVbase.class.php. I have checked the first two, comments and stories, and it can be clearly seen as going through htmlspecialchars but the other two I'm still a little unclear about. This should only affect urls with html entities in or around the url, such as: $text = "\"www.url.com/?foo=bar&bar=foo\""; $text = htmlspecialchars($text); echo $text; // "www.url.com/?foo=bar&bar=foo" Plugin developers should also keep this in mind if you are making use of the function. The function as it is now will work well, a lot better than what we had before, but I would appreciate it if users could test this in the upcoming 1.5.2rc1 release and post any bugs they might find. Sami From dirk at haun-online.de Thu Jan 22 14:14:00 2009 From: dirk at haun-online.de (Dirk Haun) Date: Thu, 22 Jan 2009 20:14:00 +0100 Subject: [geeklog-devel] Geeklog 1.5.2 and 1.6.0 In-Reply-To: References: <20090118191539.146575220@smtp.haun-online.de> <20090121192112.1018844967@smtp.haun-online.de> Message-ID: <20090122191400.1818282102@smtp.haun-online.de> Blaine Lang wrote: >Is 1.6 only what is on the roadmap page as I'd like to open this up for >discussion or understand if some of the ideas we have been discussing >are to in a 1.7 and follow shortly after 1.6. In my opinion, what absolutely has to be in 1.6 are - the GSoC projects by Matt, Sami, and Jared - the 3 plugin RFCs I posted - raising the minimum requirements to PHP 4.4 (maybe those should also be in the bugtracker?) Because those (especially the first two) are the most invasive code changes. Everything else that hasn't already been implemented is up for discussion. Some of the items on the roadmap are only there because they got pushed up from an earlier target. We should really aim for having a stable and released version out in time this year, should we be part of the Summer of Code again. That, plus Mercurial, and giving each of our potential students their own repository will also help that results can find their way back into the mainline earlier and easier. There is, of course, nothing stopping us from making 1.6.1, 1.6.2, ... releases, even during the summer. Looking at the open items that currently have a 1.6.0 target - it's a mixed bag. Some should be easy to implement. Other could probably be pushed back further. Which issues did you have in mind (and for which releases)? I've added a 1.6.1 to the list of versions in the bugtracker. Feel free to push some targets around when you feel it's appropriate. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Fri Jan 23 13:00:16 2009 From: websitemaster at cogeco.net (Website Master) Date: Fri, 23 Jan 2009 13:00:16 -0500 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: References: Message-ID: <01cc01c97d84$72bd8d70$5838a850$@net> In Geeklog 1.4.1 this function would not convert a domain name to a link (like Geeklog.net). Since 1.5 it does which messed with a lot of my articles and I had to disable this code. Has the new code switched back to the original way? If not, can we implement a disable feature in the admin section? Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Sami Barakat Sent: January-22-09 11:36 AM To: Geeklog Development Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks Before some people start seeing unexpected result from the new COM_makeClickableLinks function this is just a little word of warning. The function relies on the text being passed through htmlspecialchars first. So: $text = htmlspecialchars($text); $text = COM_makeClickableLinks($text); This is due to difficulties recognising both & and & in the url as well as terminating before reaching any other entities, such as " or   It should not be much of an issue as the only places this function is used in are the files: lib-comment.php, story.class.php, lib-admin.php and SLVbase.class.php. I have checked the first two, comments and stories, and it can be clearly seen as going through htmlspecialchars but the other two I'm still a little unclear about. This should only affect urls with html entities in or around the url, such as: $text = "\"www.url.com/?foo=bar&bar=foo\""; $text = htmlspecialchars($text); echo $text; // "www.url.com/?foo=bar&bar=foo" Plugin developers should also keep this in mind if you are making use of the function. The function as it is now will work well, a lot better than what we had before, but I would appreciate it if users could test this in the upcoming 1.5.2rc1 release and post any bugs they might find. Sami _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 3790 (20090122) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From dirk at haun-online.de Sat Jan 24 07:56:03 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 24 Jan 2009 13:56:03 +0100 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: <01cc01c97d84$72bd8d70$5838a850$@net> References: <01cc01c97d84$72bd8d70$5838a850$@net> Message-ID: <20090124125603.786123483@smtp.haun-online.de> Website Master wrote: >In Geeklog 1.4.1 this function would not convert a domain name to a link >(like Geeklog.net). Since 1.5 it does which messed with a lot of my articles >and I had to disable this code. Has the new code switched back to the >original way? In 1.4.1 and earlier you had to have a "www." in front of domain names for them to be recognized and turned into links. The code in 1.5.0 and 1.5.1 was a bit too casual and made some expressions clickable if they only contained a dot in the middle of a word. That has been fixed now, but it will now make geeklog.net clickable (which it didn't do in 1.4.1), as it recognizes the ".net". Is that a problem? >If not, can we implement a disable feature in the admin section? Not in 1.5.2, but feel free to submit a feature request for 1.6. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From robg at griffsweb.com Sat Jan 24 08:38:54 2009 From: robg at griffsweb.com (Rob Griffiths) Date: Sat, 24 Jan 2009 05:38:54 -0800 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: <20090124125603.786123483@smtp.haun-online.de> References: <01cc01c97d84$72bd8d70$5838a850$@net> <20090124125603.786123483@smtp.haun-online.de> Message-ID: <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> On Jan 24, 2009, at 4:56 AM, Dirk Haun wrote: > That has been fixed now, but it will now make geeklog.net clickable > (which it didn't do in 1.4.1), as it recognizes the ".net". Is that > a problem? Personally, I don't want my CMS making any assumptions about what I want to do. If I want a link, I'll code it explicitly. Count me strongly in favor of an option to disable this "feature." One of the things that I've always liked about Geeklog (vs say WordPress) is that it didn't go about changing my code of its own volition (OK, other than deleting my backslashes :) ). -rob. From lwc4nwo at gmail.com Sat Jan 24 10:00:43 2009 From: lwc4nwo at gmail.com (Lior2) Date: Sat, 24 Jan 2009 17:00:43 +0200 Subject: [geeklog-devel] Crediting translators by a link Message-ID: <20090124.150043.765.3@LWC> Other CMSes allow translators to supply a link in the footer. So if you enter a CMS enabled site (well, at least non English ones), you frequently see a "translated by" link alongside the "powered by" one. That way, the casual surfer knows who allowed the site to be in the language it's currently in. It's just like we want the casual surfer to know which CMS made the site possible in the first place and perhaps use it for their own site. I see translations as sort of plugins. It takes a lot of work to translate and a translator is expected (at least by him/herself) not to ruin a new upgrade (that could have no further upgrade in a long time) by not translating in time for the release. While plugins also cannot touch the footer, they are able to inject code after all, so they can just inject footers of their own, like Media Gallery does. Theme makers have even greater power. They can control the official footer directly (or leave their links elsewhere). My suggestion is 3 strings: $_EXAMPLE = array( 'translator_link' => true, 'translator_url' => 'http://...', // or 'mailto:...' 'translator_name' => 'Name of site/translator' ); Then the footer would include this: if ($_EXAMPLE['translator_link']) { $translator_link = COM_buildUrl($_EXAMPLE['translator_url']); $translator_link = COM_createLink($translator_link, $_EXAMPLE['translator_name']); $footer->set_var( 'translated_by', $translator_link); } Please share your opinions. Note that translators who will rather use mailto can use protective javascript like in this mailing list (or maybe have Geeklog use protective javascript itself if it spots the term "mailto:"). From dirk at haun-online.de Sat Jan 24 11:10:07 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 24 Jan 2009 17:10:07 +0100 Subject: [geeklog-devel] Demo site option? Message-ID: <20090124161007.1791033447@smtp.haun-online.de> Seeing that there are quite a few Geeklog demo sites out there now and given the fact that we're adding more and more "dangerous" features (PHP in static pages, plugin upload, ...), I was wondering if it wouldn't be a good idea to have an option to switch a site into a demo mode that doesn't allow using those features. That option would obviously have to go into the siteconfig.php and not into the config GUI. What should be included? Should this be a binary option (enable demo mode? yes/no) or should it have a list of possible options to disable? At the very least, it should disable - PHP in static pages - plugin uploads (as of 1.6.0) What about features that could be used for spam, e.g. - trackbacks - sending emails Opinions? bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From devel at portalparts.com Sat Jan 24 12:03:11 2009 From: devel at portalparts.com (Blaine Lang) Date: Sat, 24 Jan 2009 12:03:11 -0500 Subject: [geeklog-devel] Demo site option? In-Reply-To: <20090124161007.1791033447@smtp.haun-online.de> References: <20090124161007.1791033447@smtp.haun-online.de> Message-ID: I think we may want to define what 'demo' mode is as I can see another mode called 'restricted' mode which could be used on a live site to lock it down. Sounds like demo mode is one where you would be giving admin access to other users. Restricted mode would be a case where you would not. In Demo mode, I think users would not be installing/upgrading any plugins and possibly not able to even un-install or change the enabled status. Suggest we create an array to hold restricted config options so that will allow us to extend it to disable any of the config manager options. Blaine Dirk Haun wrote: > Seeing that there are quite a few Geeklog demo sites out there now and > given the fact that we're adding more and more "dangerous" features (PHP > in static pages, plugin upload, ...), I was wondering if it wouldn't be > a good idea to have an option to switch a site into a demo mode that > doesn't allow using those features. > > That option would obviously have to go into the siteconfig.php and not > into the config GUI. > > What should be included? Should this be a binary option (enable demo > mode? yes/no) or should it have a list of possible options to disable? > > At the very least, it should disable > > - PHP in static pages > - plugin uploads (as of 1.6.0) > > What about features that could be used for spam, e.g. > > - trackbacks > - sending emails > > Opinions? > > bye, Dirk > > > From dirk at haun-online.de Sun Jan 25 05:17:22 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 25 Jan 2009 11:17:22 +0100 Subject: [geeklog-devel] RFC: Simplifying PLG_itemSaved In-Reply-To: <00b801c978cb$f47a4dc0$dd6ee940$@net> References: <20090117165655.1288452353@smtp.haun-online.de> <00b801c978cb$f47a4dc0$dd6ee940$@net> Message-ID: <20090125101722.1918160968@smtp.haun-online.de> Website Master wrote: >Also some >plugins have multiple object types, the current API does not handle this. As >example the forum has topics and messages. Okay, I just ran into this same problem with the Links plugin, which has links and categories. Obviously, I can do PLG_itemSaved($lid, 'links'); for a link. But what do I call when a link category changed? Claiming 'category' for the Links plugin would be rude. Suggestion: PLG_itemSaved($cid, 'links.category'); i.e. allow plugins to have subtypes, separated by a dot. Comments? bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From vfuria at gmail.com Sun Jan 25 12:44:03 2009 From: vfuria at gmail.com (Vincent Furia) Date: Sun, 25 Jan 2009 10:44:03 -0700 Subject: [geeklog-devel] Crediting translators by a link In-Reply-To: <20090124.150043.765.3@LWC> References: <20090124.150043.765.3@LWC> Message-ID: <8319e2d60901250944hbb6be6bob06c7108d7ee845f@mail.gmail.com> I don't think that it is necessary or a particullary fair idea. Translators are an important part of the team that creates Geeklog, but so are the coders, the documentors, and the forum contributors. In fact, everyone who contributes to Geeklog is an important part of the community. The Geekog link in the footer is meant to be recognition of everyone's efforts. There simply isn't room in the footer for everyone to put their own byline (and still have a reasonable footer). Just my $0.02... -Vinny On 1/24/09, Lior2 wrote: > Other CMSes allow translators to supply a link in the footer. So if you > enter a CMS enabled site (well, at least non English ones), you > frequently see a "translated by" link alongside the "powered by" one. > That way, the casual surfer knows who allowed the site to be in the > language it's currently in. It's just like we want the casual surfer to > know which CMS made the site possible in the first place and perhaps use > it for their own site. > > I see translations as sort of plugins. It takes a lot of work to translate > and a translator is expected (at least by him/herself) not to ruin a new > upgrade (that could have no further upgrade in a long time) by not > translating in time for the release. While plugins also cannot touch the > footer, they are able to inject code after all, so they can just inject > footers of their own, like Media Gallery does. Theme makers have even > greater power. They can control the official footer directly (or leave > their links elsewhere). > > My suggestion is 3 strings: > $_EXAMPLE = array( > 'translator_link' => true, > 'translator_url' => 'http://...', // or 'mailto:...' > 'translator_name' => 'Name of site/translator' > ); > > Then the footer would include this: > > if ($_EXAMPLE['translator_link']) { > $translator_link = COM_buildUrl($_EXAMPLE['translator_url']); > $translator_link = COM_createLink($translator_link, > $_EXAMPLE['translator_name']); > $footer->set_var( 'translated_by', $translator_link); > } > > Please share your opinions. Note that translators who will rather use > mailto can use protective javascript like in this mailing list (or maybe > have Geeklog use protective javascript itself if it spots the term > "mailto:"). > _______________________________________________ > 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 Jan 25 17:24:29 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 25 Jan 2009 23:24:29 +0100 Subject: [geeklog-devel] Crediting translators by a link In-Reply-To: <8319e2d60901250944hbb6be6bob06c7108d7ee845f@mail.gmail.com> References: <20090124.150043.765.3@LWC> <8319e2d60901250944hbb6be6bob06c7108d7ee845f@mail.gmail.com> Message-ID: <20090125222429.815763896@smtp.haun-online.de> Vincent Furia wrote: >I don't think that it is necessary or a particullary fair idea. >Translators are an important part of the team that creates Geeklog, >but so are the coders, the documentors, and the forum contributors. In >fact, everyone who contributes to Geeklog is an important part of the >community. The Geekog link in the footer is meant to be recognition of >everyone's efforts. There simply isn't room in the footer for everyone >to put their own byline (and still have a reasonable footer). Thanks, Vinny. That's exactly my position on this as well. I realize everybody would like to see their name in the light, so to speak, and we do try our best to give proper credit where due. But in the end, there's only room (in the footer) to give credit to the community as a whole. The translators are an important part of that community, of course, and if someone's interested in who made, say, the Hebrew translation, then that is easy to find out (or so I would think). >> Other CMSes allow translators to supply a link in the footer. So if you >> enter a CMS enabled site (well, at least non English ones), you >> frequently see a "translated by" link alongside the "powered by" one. To be honest, I've never noticed this. I remember seeing references to theme authors, e.g. on Wordpress sites, but not for translators. Got an example? I wonder if those couldn't be confused with translating the content of the site. At least that's what I would assume when seeing such a note. >> and a translator is expected (at least by him/herself) not to ruin a new >> upgrade (that could have no further upgrade in a long time) by not >> translating in time for the release. What do you mean by that? We have several translations that haven't been updated in a while. They do work, though - they're just not translated entirely, so some of the texts will show up in English. I don't think that counts as "ruining" anything. And there's always the option to upload new translations to geeklog.net bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From info at heatherengineering.com Sun Jan 25 17:37:16 2009 From: info at heatherengineering.com (Euan McKay) Date: Mon, 26 Jan 2009 07:37:16 +0900 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: <364575ed0901200713w72949a96xe7d8687ac0ddd975@mail.gmail.com> References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <364575ed0901200713w72949a96xe7d8687ac0ddd975@mail.gmail.com> Message-ID: I think adding language files to this repository might be a good idea too. Even if that is beyond this project, it is worth bearing in mind when planning to ensure flexibility for future extension. Cheers, Euan. On Wed, Jan 21, 2009 at 00:13, cordiste wrote: > Dokuwiki can upload plugins from url, so it can be a good exemple to > extend the plugin admin panel in Geeklog to allow download from a > plugin repository. > > See the Dokuwiki plugin For Geeklog. > > ::Ben > > > 2009/1/19 Dirk Haun : >> Blaine Lang wrote: >> >>>I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >>>service and we can host the plugins on geeklog.net (or other locations). >>>Add blocks to this service adn we will have a way for sites to explore >>>and add components online and query if updates are available - like >>>firefox does. >> >> First draft: >> >> http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository >> >> bye, Dirk >> >> >> -- >> http://www.geeklog.net/ >> http://geeklog.info/ >> >> _______________________________________________ >> 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 Jan 25 22:28:00 2009 From: websitemaster at cogeco.net (Website Master) Date: Sun, 25 Jan 2009 22:28:00 -0500 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> References: <01cc01c97d84$72bd8d70$5838a850$@net> <20090124125603.786123483@smtp.haun-online.de> <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> Message-ID: <000a01c97f66$177f24d0$467d6e70$@net> My reasoning exactly. I'll put in a feature request. -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rob Griffiths Sent: January-24-09 8:39 AM To: Geeklog Development Subject: Re: [geeklog-devel] Word of warning about COM_makeClickableLinks On Jan 24, 2009, at 4:56 AM, Dirk Haun wrote: > That has been fixed now, but it will now make geeklog.net clickable > (which it didn't do in 1.4.1), as it recognizes the ".net". Is that > a problem? Personally, I don't want my CMS making any assumptions about what I want to do. If I want a link, I'll code it explicitly. Count me strongly in favor of an option to disable this "feature." One of the things that I've always liked about Geeklog (vs say WordPress) is that it didn't go about changing my code of its own volition (OK, other than deleting my backslashes :) ). -rob. _______________________________________________ geeklog-devel mailing list geeklog-devel at lists.geeklog.net http://eight.pairlist.net/mailman/listinfo/geeklog-devel __________ Information from ESET NOD32 Antivirus, version of virus signature database 3795 (20090123) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From websitemaster at cogeco.net Sun Jan 25 22:36:24 2009 From: websitemaster at cogeco.net (Website Master) Date: Sun, 25 Jan 2009 22:36:24 -0500 Subject: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) In-Reply-To: References: <20090107125345.gxrl8ocxes040k8w@webmail.df.eu> <20090119191407.1786996304@smtp.haun-online.de> <364575ed0901200713w72949a96xe7d8687ac0ddd975@mail.gmail.com> Message-ID: <000b01c97f67$44105590$cc3100b0$@net> I would think themes should be added as well to the repository (in the future). For all items (plugins, language files, themes) besides version requirements and the authors website, a description field could be used for any of the authors requests (like putting a link in the footer). Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Euan McKay Sent: January-25-09 5:37 PM To: Geeklog Development Subject: Re: [geeklog-devel] Plugin repository (was: RFC: Plugin auto install) I think adding language files to this repository might be a good idea too. Even if that is beyond this project, it is worth bearing in mind when planning to ensure flexibility for future extension. Cheers, Euan. On Wed, Jan 21, 2009 at 00:13, cordiste wrote: > Dokuwiki can upload plugins from url, so it can be a good exemple to > extend the plugin admin panel in Geeklog to allow download from a > plugin repository. > > See the Dokuwiki plugin For Geeklog. > > ::Ben > > > 2009/1/19 Dirk Haun : >> Blaine Lang wrote: >> >>>I have an idea now for SOC 2009: Implement a REST based plugin DEPOT >>>service and we can host the plugins on geeklog.net (or other locations). >>>Add blocks to this service adn we will have a way for sites to explore >>>and add components online and query if updates are available - like >>>firefox does. >> >> First draft: >> >> http://wiki.geeklog.net/wiki/index.php/SoC_plugin_repository >> >> bye, Dirk >> >> >> -- >> http://www.geeklog.net/ >> http://geeklog.info/ >> >> _______________________________________________ >> 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 __________ Information from ESET NOD32 Antivirus, version of virus signature database 3798 (20090125) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From mike at fuckingbrit.com Mon Jan 26 02:32:19 2009 From: mike at fuckingbrit.com (Michael Jervis) Date: Mon, 26 Jan 2009 07:32:19 +0000 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> References: <01cc01c97d84$72bd8d70$5838a850$@net> <20090124125603.786123483@smtp.haun-online.de> <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> Message-ID: <7b42e7470901252332i6149bd5bifc02079cf1eae42e@mail.gmail.com> > liked about Geeklog (vs say WordPress) is that it didn't go about changing > my code of its own volition (OK, other than deleting my backslashes :) ). And that's fixed... From geeklog.nwo at neverbox.com Mon Jan 26 06:01:42 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Mon, 26 Jan 2009 14:01:42 +0300 Subject: [geeklog-devel] crediting translators by a link In-Reply-To: 8319e2d60901250944hbb6be6bob06c7108d7ee845f@mail.gmail.com Message-ID: <01c97fad$Blat.v2.6.2$db93891e$e149fa1f7cc@weissbrod.com> >I wonder if those couldn't be confused with translating the content of the site. At least that's what I would assume when seeing such a note. Not at all, because multilingual CMS sites are the exception. I only meant single language sites, such as http://www.thesnake.co.il Anyway, I do not think it's pretty easy to find who made what, except plugins which have a list. Translations specifically are only found if there was a reason to upload them between releases. Unless more subscribers here show support for the original request, I guess I have an alternate request: make a list of newest languages/translators (e.g. Chinese - v1.5.1 - by ...). From geeklog.nwo at neverbox.com Mon Jan 26 09:39:54 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Mon, 26 Jan 2009 17:39:54 +0300 Subject: [geeklog-devel] Crediting translators by a link In-Reply-To: 8319e2d60901250944hbb6be6bob06c7108d7ee845f@mail.gmail.com Message-ID: <01c97fcc$Blat.v2.6.2$5733e226$6e8b683f4ea@weissbrod.com> >I wonder if those couldn't be confused with translating the content of >the site. At least that's what I would assume when seeing such a note. Not at all, because multilingual CMS sites are the exception. I only meant single language sites, such as http://www.thesnake.co.il Anyway, I do not think it's pretty easy to find who made what, except plugins which have a list. Translations specifically are only found if there was a reason to upload them between releases. Unless more subscribers here show support for the original request, I guess I have an alternate request: make a list of newest languages/translators (e.g. Chinese - v1.5.1 - by ...). From info at heatherengineering.com Tue Jan 27 10:47:19 2009 From: info at heatherengineering.com (Euan McKay) Date: Wed, 28 Jan 2009 00:47:19 +0900 Subject: [geeklog-devel] Suggestion: simple mode Message-ID: Some people may have noticed that I made a simple "blog" plugin last month. This replicates some basic functionality of stories - you can have just a title, content, permissions, comments. That's it. Another thing I have done on sites is set display:none on many of the items in the staticpages editor. The reason is that many users find the interface for editing things in Geeklog too intimidating. There are too many features for some users. Naturally, lots of features is a good thing, but not everyone needs everything. (This is sort of relevant: http://www.joelonsoftware.com/items/2006/11/21.html the following article linked from the bottom of that page is also.) I would like to suggest a config option to use a "simple" interface for the admin pages, or perhaps the ability to hide certain options. This could be accomplished by having two templates for the editors for items such as stories and staticpages, and making sure that any missing items are either in hidden fields or are simply set to default. I realise that the stories page is greatly improved by having tabs, but simply having the options there is confusing for some people. And others just click and tweak randomly because they can't choose what to ignore, and end up in a mess. Removing the clutter will make it much easier to create sites for people who are less computer literate, and help differentiate Geeklog from other CMSs. Thoughts? Euan. ----------------------------------------------------------------------------- Euan McKay PhD Candidate in International Relations Department of Advanced Social and International Studies Graduate School of Arts and Sciences The University of Tokyo From vfuria at gmail.com Tue Jan 27 11:58:58 2009 From: vfuria at gmail.com (Vincent Furia) Date: Tue, 27 Jan 2009 09:58:58 -0700 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: References: Message-ID: <8319e2d60901270858y4ac9abddv3e76a6625359ad2f@mail.gmail.com> Couldn't this be handled through templates? You can release a template patch or an entire theme that has a simple "blog" and "admin" interface. If the user ever needs more advanced options they can simply switch themes. You could even prefix themes of this type with "Simple". So you'd have themes like "Simple Professional" and "Simple Blue". -Vinny On Tue, Jan 27, 2009 at 8:47 AM, Euan McKay wrote: > Some people may have noticed that I made a simple "blog" plugin last > month. This replicates some basic functionality of stories - you can > have just a title, content, permissions, comments. That's it. Another > thing I have done on sites is set display:none on many of the items in > the staticpages editor. > > The reason is that many users find the interface for editing things in > Geeklog too intimidating. There are too many features for some users. > Naturally, lots of features is a good thing, but not everyone needs > everything. (This is sort of relevant: > http://www.joelonsoftware.com/items/2006/11/21.html the following > article linked from the bottom of that page is also.) > > I would like to suggest a config option to use a "simple" interface > for the admin pages, or perhaps the ability to hide certain options. > This could be accomplished by having two templates for the editors for > items such as stories and staticpages, and making sure that any > missing items are either in hidden fields or are simply set to > default. I realise that the stories page is greatly improved by having > tabs, but simply having the options there is confusing for some > people. And others just click and tweak randomly because they can't > choose what to ignore, and end up in a mess. > > Removing the clutter will make it much easier to create sites for > people who are less computer literate, and help differentiate Geeklog > from other CMSs. > > Thoughts? > > Euan. > > > ----------------------------------------------------------------------------- > Euan McKay > PhD Candidate in International Relations > Department of Advanced Social and International Studies > Graduate School of Arts and Sciences > The University of Tokyo > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From websitemaster at cogeco.net Tue Jan 27 13:51:48 2009 From: websitemaster at cogeco.net (Website Master) Date: Tue, 27 Jan 2009 13:51:48 -0500 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <8319e2d60901270858y4ac9abddv3e76a6625359ad2f@mail.gmail.com> References: <8319e2d60901270858y4ac9abddv3e76a6625359ad2f@mail.gmail.com> Message-ID: <005d01c980b0$4fa172f0$eee458d0$@net> I would see this more as user based. When I am on the website as an administrator I want all options but someone who is just plugging in stories (like most clients) do not. Tom From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Vincent Furia Sent: January-27-09 11:59 AM To: Geeklog Development Subject: Re: [geeklog-devel] Suggestion: simple mode Couldn't this be handled through templates? You can release a template patch or an entire theme that has a simple "blog" and "admin" interface. If the user ever needs more advanced options they can simply switch themes. You could even prefix themes of this type with "Simple". So you'd have themes like "Simple Professional" and "Simple Blue". -Vinny On Tue, Jan 27, 2009 at 8:47 AM, Euan McKay wrote: Some people may have noticed that I made a simple "blog" plugin last month. This replicates some basic functionality of stories - you can have just a title, content, permissions, comments. That's it. Another thing I have done on sites is set display:none on many of the items in the staticpages editor. The reason is that many users find the interface for editing things in Geeklog too intimidating. There are too many features for some users. Naturally, lots of features is a good thing, but not everyone needs everything. (This is sort of relevant: http://www.joelonsoftware.com/items/2006/11/21.html the following article linked from the bottom of that page is also.) I would like to suggest a config option to use a "simple" interface for the admin pages, or perhaps the ability to hide certain options. This could be accomplished by having two templates for the editors for items such as stories and staticpages, and making sure that any missing items are either in hidden fields or are simply set to default. I realise that the stories page is greatly improved by having tabs, but simply having the options there is confusing for some people. And others just click and tweak randomly because they can't choose what to ignore, and end up in a mess. Removing the clutter will make it much easier to create sites for people who are less computer literate, and help differentiate Geeklog from other CMSs. Thoughts? Euan. ---------------------------------------------------------------------------- - Euan McKay PhD Candidate in International Relations Department of Advanced Social and International Studies Graduate School of Arts and Sciences The University of Tokyo _______________________________________________ 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 1000ideen at gmx.de Tue Jan 27 14:32:33 2009 From: 1000ideen at gmx.de (1000ideen at gmx.de) Date: Tue, 27 Jan 2009 20:32:33 +0100 Subject: [geeklog-devel] Suggestion: simple mode Message-ID: <20090127193233.312130@gmx.net> I posted several postings on usability but I never had problems with the editor. The tabs make it quite overlookable. Nevertheless anything may be a problem and it is good to suggest ideas for usability. E.g. the archive tick box is difficult to understand. Also the rights management. On the other hand there are default settings and editors should be more wise than the average user. What is definitely a problem is the profile settings: http://project.geeklog.net/tracking/view.php?id=787 http://project.geeklog.net/tracking/view.php?id=786 I only have inexperienced users (non editors) and they try to do anything wrong that is possible... Markus -- NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL f?r nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a From 1000ideen at gmx.de Tue Jan 27 14:40:41 2009 From: 1000ideen at gmx.de (1000ideen at gmx.de) Date: Tue, 27 Jan 2009 20:40:41 +0100 Subject: [geeklog-devel] Crediting translators by a link Message-ID: <20090127194041.88050@gmx.net> I am also a translator but I feel my work is nothing in comparison to the programmers, well almost. Yes, there are examples where translators and theme designers are being mentioned. But honestly, isn`t this a bit too much? As for me I don`t need a link. http://www.deineex-board.com/tmp/board/index.php Powered by phpBB ? 2000, 2002, 2005, 2007 phpBB Group. Designed by Vjacheslav Trushkin for Free Forums/DivisionCore. Deutsche ?bersetzung durch phpBB.de On the other hand I could imagine a page like that: http://www.openarchitectureware.org/staticpages/index.php/team It shows the whole team of a site. I`d add everybody who thinks he belongs there and say what he is working on. Would that be an alternative? Markus -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger From dirk at haun-online.de Tue Jan 27 14:57:25 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 27 Jan 2009 20:57:25 +0100 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <005d01c980b0$4fa172f0$eee458d0$@net> References: <8319e2d60901270858y4ac9abddv3e76a6625359ad2f@mail.gmail.com> <005d01c980b0$4fa172f0$eee458d0$@net> Message-ID: <20090127195725.2132682143@smtp.haun-online.de> Website Master wrote: >I would see this more as user based. In which case it should be based on permissions. bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From dirk at haun-online.de Tue Jan 27 16:25:24 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 27 Jan 2009 22:25:24 +0100 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: References: Message-ID: <20090127212524.1013999715@smtp.haun-online.de> Euan McKay wrote: >http://www.joelonsoftware.com/items/2006/11/21.html Coincidences ... That article is also contained in the book "More Joel on Software", which I'm currently reading. Now guess which article I happened to be reading on the way to work today ... >I would like to suggest a config option to use a "simple" interface >for the admin pages, or perhaps the ability to hide certain options. I guess there would be a similar issue here as with the demo mode I suggested recently: Either we define a fixed set of options that are available in that simple interface or we make the set configurable. The first option will most likely not satisfy everybody and the second option is a lot of work. To exaggerate: Choose between unhappy users or unhappy developers. Oh, and maybe even unhappy admins, because then the interface to configure this is going to be complicated. I agree with the general idea (yours and Joel's). I'm just not sure if it works for something like the story editor. Actually, if you do make a simple story editor, you end up with the form that normal users get when they submit a story. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From geeklog.nwo at neverbox.com Tue Jan 27 16:47:54 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Tue, 27 Jan 2009 23:47:54 +0200 Subject: [geeklog-devel] Crediting translators by a link Message-ID: <20090127.214754.500.1@LWC> > Would that be an alternative? That indeed was I later suggested. From geeklog.nwo at neverbox.com Wed Jan 28 05:53:01 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 28 Jan 2009 13:53:01 +0300 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: Message-ID: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> Keep in mind there's also a paradox: the advanced editor makes things more complicated and yet more simple at the same time. From geeklog.nwo at neverbox.com Wed Jan 28 06:11:45 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 28 Jan 2009 14:11:45 +0300 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: References: Message-ID: <01c98141$Blat.v2.6.2$97a43bf0$cc09e8ea53b@weissbrod.com> What I mean is, it looks a lot more simple if you disablethe advanced editor, but then there's no user friendly editor. From geeklog.nwo at neverbox.com Wed Jan 28 06:19:05 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 28 Jan 2009 14:19:05 +0300 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: Message-ID: <01c98142$Blat.v2.6.2$9e607fde$dac7c5f7f64@weissbrod.com> BTW, if it's fixed options, when can we suggest them? From geeklog.nwo at neverbox.com Wed Jan 28 06:30:49 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 28 Jan 2009 14:30:49 +0300 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: References: Message-ID: <01c98144$Blat.v2.6.2$41c2c514$dec9aad1628@weissbrod.com> I don't understand why my posts are always threaded in level 2. When you click a sender's link in here, the only special header the mailto link includes is in-reply-to and I do use it (otherwise I wouldn't even be in level 2. From 1000ideen at gmx.de Wed Jan 28 08:00:07 2009 From: 1000ideen at gmx.de (1000ideen at gmx.de) Date: Wed, 28 Jan 2009 14:00:07 +0100 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> References: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> Message-ID: <20090128130007.153370@gmx.net> I don`t really understand what the problem is with the editor. Are these theoretical ideas or practical current and frequent problems? I have quite a few inexperinced users. The only 2 things I can imagine to be a problem is the archieve. Solution -> This should only turn up if there is a topic defined as archive. And the owner rights. One guy ticked them off and couldn`t see nor edit his posts any more. Solution -> Owner rights should only be accessible by root admin. If you meant to improove usability by taking away icons you may edit the icon lines in FCKeditor. What other problems are there? Markus -- NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL f?r nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a From info at heatherengineering.com Wed Jan 28 08:21:39 2009 From: info at heatherengineering.com (Euan McKay) Date: Wed, 28 Jan 2009 22:21:39 +0900 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <20090127212524.1013999715@smtp.haun-online.de> References: <20090127212524.1013999715@smtp.haun-online.de> Message-ID: Thanks for the comments. I agree with Vinny that this could be done with templates - that is how I usually end up hacking things to achieve what I want. My suggestion would be to have two templates, one showing all options for advanced users and admins, and the other showing less options for less IT-savvy users. This could be a single choice in the user's preferences: simple or advanced interface. Then, any plugin/feature supporting that option could choose the template to use from that setting. This would also satisfy Tom's requirement that admins have full access to all features. A permissions-based solution would be too complicated and time-consuming to create, as Dirk noted. While I would like to see this, maybe it is part of a wider issue of usability and interface design? Perhaps it would be better to have someone (an SoC student?) working on usability and the interface in general? Euan. On Wed, Jan 28, 2009 at 06:25, Dirk Haun wrote: ... > the interface to configure this is going to be complicated. > > I agree with the general idea (yours and Joel's). I'm just not sure if > it works for something like the story editor. Actually, if you do make a > simple story editor, you end up with the form that normal users get when > they submit a story. ... From devel at portalparts.com Wed Jan 28 09:50:54 2009 From: devel at portalparts.com (Blaine Lang) Date: Wed, 28 Jan 2009 09:50:54 -0500 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <20090128130007.153370@gmx.net> References: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> <20090128130007.153370@gmx.net> Message-ID: The Advanced Editor was created with that main purpose to simplify the interface and hide all the non-needed options for basic content creation and editing. If users need or want to explore, the editor's many options are broken out into 4 other tabs to further keep things more simplified and organized. The default FCKeditor toolbar options are set in a config file so it can be simplified to just a few icons. Only more adventurous users are going to check out the other toolbar modes. I believe the fields on the 'Editor' tab are pretty much the most basic we could get it to now. Are your sites not using the Advanced Editor or should we call it the Simple Editor? Are they clicking on the other tabs and getting confused? Blaine From geeklog.nwo at neverbox.com Wed Jan 28 09:57:54 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 28 Jan 2009 16:57:54 +0200 Subject: [geeklog-devel] A patch for mailman threading Message-ID: <20090128.145754.656.1@LWC> I've used the web archive itself to reply and thus had a few problems threading before. My posts showed up as either level 1 or 2. Turns out it's an official bug in mailman that was fixed by now. I'm not sure how much control pairlist.net gives you, but they stopped upgrading mailman just before the version that fixed the threading bug. Can you have mailman upgraded (even by one version would be enough)? If not, can you at least run the official short patch? https://bugs.launchpad.net/mailman/+bug/266414 Thanks! From info at heatherengineering.com Wed Jan 28 11:23:08 2009 From: info at heatherengineering.com (Euan McKay) Date: Thu, 29 Jan 2009 01:23:08 +0900 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: References: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> <20090128130007.153370@gmx.net> Message-ID: Blaine, I do use the advanced editor with these sites, but even with the tabs (which are a great improvement on how things were) there are still too many options for some people, particularly older users. I'm concerned with the general usability of Geeklog - I think it could be much better, with a little more tweaking of what is already there. Perhaps that would be a more productive path to follow than considering just the story editor - that was just one example I was raising. As I mentioned earlier, the problem with usability is that many users don't have the experience to select what to ignore and what to focus on. Just having the archive/draft/access rights/etc. options there is enough to confuse them so much that they lose confidence. Which is a shame, because they could very easily be creating something. One example of a simple improvement then might be to have more tabs in other plugins (e.g. the staticpages plugin would benefit greatly from tabs like the story editor), and consider the placing of things on those tabs. So, for example, the basic editor tab for stories should perhaps show the title, the introduction edit area, the body edit area, and the save / cancel / delete buttons only. OK, I've convinced myself anyway: I think that there should be a more rigourous consideration of the interface layout of Geeklog, focusing on presenting core functionality to users in as simple a fashion as possible, and reducing barriers to access for inexperienced users. Starting with stories and staticpages as perhaps the most important features. Sounds like a good SoC project to me. Euan. On Wed, Jan 28, 2009 at 23:50, Blaine Lang wrote: > The Advanced Editor was created with that main purpose to simplify the > interface and hide all the non-needed options for basic content creation and > editing. > If users need or want to explore, the editor's many options are broken out > into 4 other tabs to further keep things more simplified and organized. > The default FCKeditor toolbar options are set in a config file so it can be > simplified to just a few icons. > Only more adventurous users are going to check out the other toolbar modes. > I believe the fields on the 'Editor' tab are pretty much the most basic we > could get it to now. > > Are your sites not using the Advanced Editor or should we call it the Simple > Editor? > Are they clicking on the other tabs and getting confused? > > Blaine > > _______________________________________________ > 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 Jan 28 14:33:03 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 28 Jan 2009 20:33:03 +0100 Subject: [geeklog-devel] A patch for mailman threading In-Reply-To: <20090128.145754.656.1@LWC> References: <20090128.145754.656.1@LWC> Message-ID: <20090128193303.1743960503@smtp.haun-online.de> LWC wrote: >I'm not sure how much control pairlist.net gives you Not much, at least not on that level. But I can ask nicely, which I just did. bye, Dirk -- http://www.haun-online.de/accu/ From dirk at haun-online.de Wed Jan 28 17:01:52 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 28 Jan 2009 23:01:52 +0100 Subject: [geeklog-devel] A patch for mailman threading In-Reply-To: <20090128193303.1743960503@smtp.haun-online.de> References: <20090128.145754.656.1@LWC> <20090128193303.1743960503@smtp.haun-online.de> Message-ID: <20090128220152.11329500@smtp.haun-online.de> Dirk Haun wrote: >But I can ask nicely, which I just did. Well, that was quick. Try again now. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From geeklog.nwo at neverbox.com Wed Jan 28 16:24:11 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Thu, 29 Jan 2009 00:24:11 +0300 Subject: [geeklog-devel] A patch for mailman threading In-Reply-To: <20090128193303.1743960503@smtp.haun-online.de> Message-ID: <01c98197$Blat.v2.6.2$26589d5a$c3ccbb9ce0c@weissbrod.com> >Well, that was quick. Try again now. Here's a test. I hope it worked. If it did, they really were quick running that patch. BTW, I wonder why they removed the other half of the patch, the half that added the word Re: before the subject in the link. From geeklog.nwo at neverbox.com Wed Jan 28 16:28:24 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Thu, 29 Jan 2009 00:28:24 +0300 Subject: [geeklog-devel] A patch for mailman threading In-Reply-To: <01c98197$Blat.v2.6.2$26589d5a$c3ccbb9ce0c@weissbrod.com> Message-ID: <01c98197$Blat.v2.6.2$bcd90e9a$e24be07109c@weissbrod.com> Well, it only worked partially - I got to level 3 but not 4. The reason it's supposed to work now in THIS post is because I did it from the e-mail. From 1000ideen at gmx.de Thu Jan 29 16:27:17 2009 From: 1000ideen at gmx.de (1000ideen at gmx.de) Date: Thu, 29 Jan 2009 22:27:17 +0100 Subject: [geeklog-devel] Suggestion: simple mode In-Reply-To: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> References: <01c9813e$Blat.v2.6.2$f9eb0cba$ad8482e7524@weissbrod.com> Message-ID: <20090129212717.153230@gmx.net> I made several feature requests over the last 3 years, almost all of them were about usability and almost all of them have been discussed on the forum. I rewrote them now in the new bug tracker and added a few: http://project.geeklog.net/tracking/view.php?id=154 http://project.geeklog.net/tracking/view.php?id=807 http://project.geeklog.net/tracking/view.php?id=798 http://project.geeklog.net/tracking/view.php?id=721 Select cookie http://project.geeklog.net/tracking/view.php?id=155 permalink http://project.geeklog.net/tracking/view.php?id=192 routing http://project.geeklog.net/tracking/view.php?id=157 mail users http://project.geeklog.net/tracking/view.php?id=152 topic.delete http://project.geeklog.net/tracking/view.php?id=191 user.mass.delete Tabs for the static page editor sounds good to me but also better wording. E.g. "add to horizontal menu" instead of "add to menu" or what is a block template... Anyway, is there any case that an owner will tick off his own right to edit or read his stories or static page? Shouldn`t the first two tick boxes be greyed out? Markus -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger