From devel at portalparts.com Mon Feb 2 19:18:22 2009 From: devel at portalparts.com (Blaine Lang) Date: Mon, 02 Feb 2009 19:18:22 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments Message-ID: Dirk is in the process of moving the Wiki and had been waiting to start this on the Wiki but in light of some recent other discussions, I will start that discussion here on the DEV list. For some time (ok, a couple years), I have wanted to add a more comprehensive Javascript library with AJAX capabilities to the core GL framework. Although, the initial focus is on adding a JS libray to make it easier to add AJAX, there is clearly a need for a JS library to made it easier to code the functions and UI components to handle and enrich the user interface. AJAX enabled forms or screens can all be coded in plan Javascript but the optimizations and proven library functions can not only make the coding easier, faster and cleaner but we easier to develop common methods and reference code. Thats without leveraging some of the sophisticated widgets, plugins these libraries can offer. This thread is then to ask for suggestions on the JS Library to use and why. We may need to setup prototyped code for comparison. I will start with my preference and reasons - let the debate begin .... ------ As part of our Nextide projects, we have been doing AJAX powered Geeklog plugins for a few years. Many of the nexpro plugins like nexFlow, nexList are good examples but that code was done a few years ago. Since then we have further optimized the coding style of using YUI and our latest projects (not public releases) are much cleaner. There are probably 100 AJAX libraries that could work with PHP and I started into this a few years ago rolling my own to better understand the issues. After looking at and trying a few, I settled on YUI because about 2+ years ago, it was developing a strong community and had a big name behind it. JQuery and others like qooxdoo,MooTools, Prototype,Dojo where also starting out. YUI's AJAX has some nice features like automatic linking to a target form and posting the form fields with no additional Javascript and can easily handle files. The library supports both POST and GET and easily used in non-form applications like links where you still want to use AJAX. The library has configurable timeout plus support for success and error handlers as well as custom event handlers. I've been using it with the YUI JSON library this past few months and it's been working nicely and easy to code. The YUI library is quite extensive now, but we only need to use Connection Manager Library which needs the minimum version of theirYahoo-Core and Event libraries. Additionally, they have the JSON library which is optional but highly recommended that we standardize on with any AJAX returning data. http://developer.yahoo.com/yui - main site, with links to their blog, examples, documentation and community forum. http://developer.yahoo.com/yui/connection/ - the AJAX connection library YUI has a very complete documented API, plus examples, tutorials and active development community. YUI 3.0 is in Pre-Release and shows that this library has a forward looking roadmap. http://developer.yahoo.com/yui/3/ Using YUI and JQuery for some of JQuery's nice UI and DOM manipulation is very doable and I have recently started to use JQuery for a new project. I really like the way JQuery has fostered active development and extensions and don't see any reason why we can't use both JQuery and YUI where they fit best. In both cases, minified and CDN hosted libraries are available. - Blaine From websitemaster at cogeco.net Mon Feb 2 19:57:11 2009 From: websitemaster at cogeco.net (Website Master) Date: Mon, 2 Feb 2009 19:57:11 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: References: Message-ID: <023401c9859a$58f0be80$0ad23b80$@net> I agree this is something that needs to be added soon as more and more plugins will start to implement this and it would be nice to get a standard settled for Geeklog (not that the plugin author couldn't use whatever he or she wanted). I've used mootools for implementing AJAX in the rating plugin. The main reason I used it was because I had a good code sample to use, since Media Gallery uses mootools as well. 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: February-02-09 7:18 PM To: Geeklog Development Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments Dirk is in the process of moving the Wiki and had been waiting to start this on the Wiki but in light of some recent other discussions, I will start that discussion here on the DEV list. For some time (ok, a couple years), I have wanted to add a more comprehensive Javascript library with AJAX capabilities to the core GL framework. Although, the initial focus is on adding a JS libray to make it easier to add AJAX, there is clearly a need for a JS library to made it easier to code the functions and UI components to handle and enrich the user interface. AJAX enabled forms or screens can all be coded in plan Javascript but the optimizations and proven library functions can not only make the coding easier, faster and cleaner but we easier to develop common methods and reference code. Thats without leveraging some of the sophisticated widgets, plugins these libraries can offer. This thread is then to ask for suggestions on the JS Library to use and why. We may need to setup prototyped code for comparison. I will start with my preference and reasons - let the debate begin .... ------ As part of our Nextide projects, we have been doing AJAX powered Geeklog plugins for a few years. Many of the nexpro plugins like nexFlow, nexList are good examples but that code was done a few years ago. Since then we have further optimized the coding style of using YUI and our latest projects (not public releases) are much cleaner. There are probably 100 AJAX libraries that could work with PHP and I started into this a few years ago rolling my own to better understand the issues. After looking at and trying a few, I settled on YUI because about 2+ years ago, it was developing a strong community and had a big name behind it. JQuery and others like qooxdoo,MooTools, Prototype,Dojo where also starting out. YUI's AJAX has some nice features like automatic linking to a target form and posting the form fields with no additional Javascript and can easily handle files. The library supports both POST and GET and easily used in non-form applications like links where you still want to use AJAX. The library has configurable timeout plus support for success and error handlers as well as custom event handlers. I've been using it with the YUI JSON library this past few months and it's been working nicely and easy to code. The YUI library is quite extensive now, but we only need to use Connection Manager Library which needs the minimum version of theirYahoo-Core and Event libraries. Additionally, they have the JSON library which is optional but highly recommended that we standardize on with any AJAX returning data. http://developer.yahoo.com/yui - main site, with links to their blog, examples, documentation and community forum. http://developer.yahoo.com/yui/connection/ - the AJAX connection library YUI has a very complete documented API, plus examples, tutorials and active development community. YUI 3.0 is in Pre-Release and shows that this library has a forward looking roadmap. http://developer.yahoo.com/yui/3/ Using YUI and JQuery for some of JQuery's nice UI and DOM manipulation is very doable and I have recently started to use JQuery for a new project. I really like the way JQuery has fostered active development and extensions and don't see any reason why we can't use both JQuery and YUI where they fit best. In both cases, minified and CDN hosted libraries are available. - Blaine _______________________________________________ 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 3819 (20090202) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From info at heatherengineering.com Mon Feb 2 19:58:41 2009 From: info at heatherengineering.com (Euan McKay) Date: Tue, 3 Feb 2009 09:58:41 +0900 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: References: Message-ID: First off, I agree with Blaine that a good JS library that is well integrated would be a good thing. I have no real preference, but I've always used Prototype and Scriptaculous. Both are easy to use, and reasonably documented (but not great - YUI documentation seems much, much better at a glance). They are also pretty easy to implement, with enough examples out there if you google. http://www.prototypejs.org/ http://script.aculo.us/ One example: when looking for a tree implementation a couple of years ago, Prototype was the best at the time. A tree with draggable items is now possible with YUI (http://andrewroth.ca/others/treeview_dragdrop/), but appears to be a little more complicated than Protoype, where you just set a "tree" flag to a sortable item. (Unfortunately, the Scriptaculous example in their wiki is not working right now - which may be indicative.) I'm not sure how much javascript you end up writing for YUI, but for Prototype/Scriptaculous, it really isn't a lot - perhaps the greatest benefit. Having several libraries would cover the problem of needing to stick to just one, but how would that affect the way it is integrated into Geeklog? Sounds like extra work creating another interface to me. Euan. On Tue, Feb 3, 2009 at 09:18, Blaine Lang wrote: > Dirk is in the process of moving the Wiki and had been waiting to start this > on the Wiki but in light of some recent other discussions, I will start that > discussion here on the DEV list. For some time (ok, a couple years), I have > wanted to add a more comprehensive Javascript library with AJAX capabilities > to the core GL framework. > > Although, the initial focus is on adding a JS libray to make it easier to > add AJAX, there is clearly a need for a JS library to made it easier to code > the functions and UI components to handle and enrich the user interface. > AJAX enabled forms or screens can all be coded in plan Javascript but the > optimizations and proven library functions can not only make the coding > easier, faster and cleaner but we easier to develop common methods and > reference code. Thats without leveraging some of the sophisticated widgets, > plugins these libraries can offer. > > This thread is then to ask for suggestions on the JS Library to use and why. > We may need to setup prototyped code for comparison. > > I will start with my preference and reasons - let the debate begin .... > ------ > > As part of our Nextide projects, we have been doing AJAX powered Geeklog > plugins for a few years. Many of the nexpro plugins like nexFlow, nexList > are good examples but that code was done a few years ago. Since then we have > further optimized the coding style of using YUI and our latest projects (not > public releases) are much cleaner. > > There are probably 100 AJAX libraries that could work with PHP and I started > into this a few years ago rolling my own to better understand the issues. > After looking at and trying a few, I settled on YUI because about 2+ years > ago, it was developing a strong community and had a big name behind it. > JQuery and others like qooxdoo,MooTools, Prototype,Dojo where also starting > out. > > YUI's AJAX has some nice features like automatic linking to a target form > and posting the form fields with no additional Javascript and can easily > handle files. The library supports both POST and GET and easily used in > non-form applications like links where you still want to use AJAX. The > library has configurable timeout plus support for success and error handlers > as well as custom event handlers. I've been using it with the YUI JSON > library this past few months and it's been working nicely and easy to code. > > The YUI library is quite extensive now, but we only need to use Connection > Manager Library which needs the minimum version of theirYahoo-Core and Event > libraries. Additionally, they have the JSON library which is optional but > highly recommended that we standardize on with any AJAX returning data. > > http://developer.yahoo.com/yui - main site, with links to their blog, > examples, documentation and community forum. > http://developer.yahoo.com/yui/connection/ - the AJAX connection library > > YUI has a very complete documented API, plus examples, tutorials and active > development community. > YUI 3.0 is in Pre-Release and shows that this library has a forward looking > roadmap. > http://developer.yahoo.com/yui/3/ > > Using YUI and JQuery for some of JQuery's nice UI and DOM manipulation is > very doable and I have recently started to use JQuery for a new project. I > really like the way JQuery has fostered active development and extensions > and don't see any reason why we can't use both JQuery and YUI where they fit > best. In both cases, minified and CDN hosted libraries are available. > > - Blaine > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From mark at the-howards.net Tue Feb 3 13:03:17 2009 From: mark at the-howards.net (Mark Howard) Date: Tue, 3 Feb 2009 13:03:17 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: References: Message-ID: <020d01c98629$b152e230$13f8a690$@net> Hey Blaine - I know I'm in the 'cheap seats', but I thought I'd share with you - I like simplicity/modularity, and don't always like to have to load something as big as Scriptaculous/MooTools, etc., and so when I just want to do some simple/straightforward Ajax I use SACK, which is the Ajax lib that Wordpress happens to use. It's very small, lightweight, and the code is mature and of course in use in about a million Wordpress blogs everwhere ... http://www.twilightuniverse.com/projects/sack/ Best regards. -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Blaine Lang Sent: Monday, February 02, 2009 7:18 PM To: Geeklog Development Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments Dirk is in the process of moving the Wiki and had been waiting to start this on the Wiki but in light of some recent other discussions, I will start that discussion here on the DEV list. For some time (ok, a couple years), I have wanted to add a more comprehensive Javascript library with AJAX capabilities to the core GL framework. Although, the initial focus is on adding a JS libray to make it easier to add AJAX, there is clearly a need for a JS library to made it easier to code the functions and UI components to handle and enrich the user interface. AJAX enabled forms or screens can all be coded in plan Javascript but the optimizations and proven library functions can not only make the coding easier, faster and cleaner but we easier to develop common methods and reference code. Thats without leveraging some of the sophisticated widgets, plugins these libraries can offer. This thread is then to ask for suggestions on the JS Library to use and why. We may need to setup prototyped code for comparison. I will start with my preference and reasons - let the debate begin .... ------ As part of our Nextide projects, we have been doing AJAX powered Geeklog plugins for a few years. Many of the nexpro plugins like nexFlow, nexList are good examples but that code was done a few years ago. Since then we have further optimized the coding style of using YUI and our latest projects (not public releases) are much cleaner. There are probably 100 AJAX libraries that could work with PHP and I started into this a few years ago rolling my own to better understand the issues. After looking at and trying a few, I settled on YUI because about 2+ years ago, it was developing a strong community and had a big name behind it. JQuery and others like qooxdoo,MooTools, Prototype,Dojo where also starting out. YUI's AJAX has some nice features like automatic linking to a target form and posting the form fields with no additional Javascript and can easily handle files. The library supports both POST and GET and easily used in non-form applications like links where you still want to use AJAX. The library has configurable timeout plus support for success and error handlers as well as custom event handlers. I've been using it with the YUI JSON library this past few months and it's been working nicely and easy to code. The YUI library is quite extensive now, but we only need to use Connection Manager Library which needs the minimum version of theirYahoo-Core and Event libraries. Additionally, they have the JSON library which is optional but highly recommended that we standardize on with any AJAX returning data. http://developer.yahoo.com/yui - main site, with links to their blog, examples, documentation and community forum. http://developer.yahoo.com/yui/connection/ - the AJAX connection library YUI has a very complete documented API, plus examples, tutorials and active development community. YUI 3.0 is in Pre-Release and shows that this library has a forward looking roadmap. http://developer.yahoo.com/yui/3/ Using YUI and JQuery for some of JQuery's nice UI and DOM manipulation is very doable and I have recently started to use JQuery for a new project. I really like the way JQuery has fostered active development and extensions and don't see any reason why we can't use both JQuery and YUI where they fit best. In both cases, minified and CDN hosted libraries are available. - 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 Tue Feb 3 14:00:15 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 3 Feb 2009 20:00:15 +0100 Subject: [geeklog-devel] [geeklog-cvs] geeklog: Implemented Search Improvements In-Reply-To: References: Message-ID: <20090203190015.919913113@smtp.haun-online.de> Hey Sami, >changeset: 6757:6db77ef26a37 >user: Sami Barakat >date: Mon Feb 02 23:04:14 2009 +0000 >description: >Implemented Search Improvements Ah, excellent :) As you may have seen, I've already started to poke around in the code a bit. I tried to get it working with error_reporting(E_ALL) but ran into some code that I didn't understand and so I decided to leave that to you ;-) Some other observations: - I sometimes get SQL errors due to negative values for the limit, e.g. LIMIT 0,-76 - I sometimes get empty results that look like this: 7. Not available... Not available... by on 01. Jan, 01:00 Uhr - Site Content Search - 0 Hits Where the headline links to .../search.php?query=mill&type=all&mode=search# and the "Site Content Search" links to .../search.php?query=mill&keyType=phrase&type=&mode=search Not sure where those are coming from. - It seems Links, Events, and Static Pages are missing the author: The search result only shows "by", followed by some blanks (as in the "empty" example above, only with proper links to the actual result this time). - Links to events have the &query parameter twice: .../calendar/event.php?eid=ws-db_mill_de&query=mill&query=mill - For Events, the date and time always seems to be 01/01 01:33am, for some reason. Do you still have the copy of the geeklog.net database? Try searching for "geeklog", "froscon", or "handful", to see some of those issues. The "empty" results and SQL errors were with a copy of the database for the company website that I don't have here. I'll try to dig a bit deeper again at work, when I find the time. Okay, that's quite some list. So let me add that I like what I see. It looks much better and, to the casual visitor, should make much more sense then results grouped by plugin. Looking forward to have that on geeklog.net :-) bye, Dirk -- http://www.haun-online.de/accu/ From devel at portalparts.com Tue Feb 3 14:45:44 2009 From: devel at portalparts.com (Blaine Lang) Date: Tue, 03 Feb 2009 14:45:44 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <020d01c98629$b152e230$13f8a690$@net> References: <020d01c98629$b152e230$13f8a690$@net> Message-ID: Hi Mark, Sack is not much different then my original code and library I created a couple years ago which use the Sarissa library to encapsulate the cross-browser XML API's. I agree, that it is small but also is not as flexible or efficient to code as the other more mature libraries. Have a look at this piece of javascript below that uses YUI and hooked to the submit button on a form. No need to setup what fields to send to the AJAX Server script and this piece of code also updates the on-page content with the returning formatted HTML - all parsed by the PHP server site script from templates. This form could have also included file attachments and no extra Javascript code. I think this code example is quite easy to read, hides all the complexity but is very flexible. Projects often start small but then grow and get more complex in ways we had not initially considered. A plugin that I am currently working on now has about 1200 lines of javascript and much of that is AJAX related functions. I have high confidence that my code will work across browsers and that's worth a few extra KB on initial download. function makeAJAXUpdateFolderPerms(formObject) { YAHOO.util.Connect.setForm(formObject, false); var callback = { success: function(o) { var json = o.responseText.substring(o.responseText.indexOf('{'), o.responseText.lastIndexOf('}') + 1); var oResults = eval('(' + json + ')'); if (oResults.retcode == 200) { Dom.get('folderperms_content').innerHTML = oResults.html; } else { alert('Error retrieving folder permissions'); } }, failure: function(o) { alert('AJAX Update Error: ' + o.status); }, argument: {}, timeout:55000 } YAHOO.util.Connect.asyncRequest('POST', ajax_post_handler_url, callback); }; Mark Howard wrote: > Hey Blaine - > > I know I'm in the 'cheap seats', but I thought I'd share with you - I like > simplicity/modularity, and don't always like to have to load something as > big as Scriptaculous/MooTools, etc., and so when I just want to do some > simple/straightforward Ajax I use SACK, which is the Ajax lib that Wordpress > happens to use. > > It's very small, lightweight, and the code is mature and of course in use in > about a million Wordpress blogs everwhere ... > > http://www.twilightuniverse.com/projects/sack/ > > > Best regards. > > -m > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Blaine Lang > Sent: Monday, February 02, 2009 7:18 PM > To: Geeklog Development > Subject: [geeklog-devel] AJAX and Javascript Libraries - request for > comments > > Dirk is in the process of moving the Wiki and had been waiting to start > this on the Wiki but in light of some recent other discussions, I will > start that discussion here on the DEV list. For some time (ok, a couple > years), I have wanted to add a more comprehensive Javascript library > with AJAX capabilities to the core GL framework. > > Although, the initial focus is on adding a JS libray to make it easier > to add AJAX, there is clearly a need for a JS library to made it easier > to code the functions and UI components to handle and enrich the user > interface. AJAX enabled forms or screens can all be coded in plan > Javascript but the optimizations and proven library functions can not > only make the coding easier, faster and cleaner but we easier to develop > common methods and reference code. Thats without leveraging some of the > sophisticated widgets, plugins these libraries can offer. > > This thread is then to ask for suggestions on the JS Library to use and > why. We may need to setup prototyped code for comparison. > > I will start with my preference and reasons - let the debate begin .... > ------ > > As part of our Nextide projects, we have been doing AJAX powered Geeklog > plugins for a few years. Many of the nexpro plugins like nexFlow, > nexList are good examples but that code was done a few years ago. Since > then we have further optimized the coding style of using YUI and our > latest projects (not public releases) are much cleaner. > > There are probably 100 AJAX libraries that could work with PHP and I > started into this a few years ago rolling my own to better understand > the issues. After looking at and trying a few, I settled on YUI because > about 2+ years ago, it was developing a strong community and had a big > name behind it. JQuery and others like qooxdoo,MooTools, Prototype,Dojo > where also starting out. > > YUI's AJAX has some nice features like automatic linking to a target > form and posting the form fields with no additional Javascript and can > easily handle files. The library supports both POST and GET and easily > used in non-form applications like links where you still want to use > AJAX. The library has configurable timeout plus support for success and > error handlers as well as custom event handlers. I've been using it with > the YUI JSON library this past few months and it's been working nicely > and easy to code. > > The YUI library is quite extensive now, but we only need to use > Connection Manager Library which needs the minimum version of > theirYahoo-Core and Event libraries. Additionally, they have the JSON > library which is optional but highly recommended that we standardize on > with any AJAX returning data. > > http://developer.yahoo.com/yui - main site, with links to their blog, > examples, documentation and community forum. > http://developer.yahoo.com/yui/connection/ - the AJAX connection library > > YUI has a very complete documented API, plus examples, tutorials and > active development community. > YUI 3.0 is in Pre-Release and shows that this library has a forward > looking roadmap. > http://developer.yahoo.com/yui/3/ > > Using YUI and JQuery for some of JQuery's nice UI and DOM manipulation > is very doable and I have recently started to use JQuery for a new > project. I really like the way JQuery has fostered active development > and extensions and don't see any reason why we can't use both JQuery and > YUI where they fit best. In both cases, minified and CDN hosted > libraries are available. > > - Blaine > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > From dirk at haun-online.de Tue Feb 3 15:11:29 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 3 Feb 2009 21:11:29 +0100 Subject: [geeklog-devel] [geeklog-cvs] geeklog: Implemented Search Improvements In-Reply-To: <20090203190015.919913113@smtp.haun-online.de> References: <20090203190015.919913113@smtp.haun-online.de> Message-ID: <20090203201129.934798443@smtp.haun-online.de> >Hey Sami, Whoops, that was supposed to be a private email. Oh well, nothing to embarrassing in it ;-) bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Tue Feb 3 15:16:57 2009 From: dirk at haun-online.de (Dirk Haun) Date: Tue, 3 Feb 2009 21:16:57 +0100 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: References: Message-ID: <20090203201657.1265997185@smtp.haun-online.de> >there is clearly a need for a JS library to made it easier >to code the functions and UI components to handle and enrich the user >interface. So, after only 4 posts I'm already counting recommendations for 6 different JS libraries :-) Which is why my original idea was to set up a GSoC project "Find us an AJAX library" where we pre-select some candidates and then the student would implement some tasks with each of them to get a better idea what's working and what isn't. Okay, so maybe a GSoC project would be overkill. Still, I'd like to see us base a decision on something a bit more substantial than "I'm familiar with it". For example, how do these libraries compare on things like - security - footprint / overhead / load times - ease of use / learning curve bye, Dirk -- http://www.haun-online.de/ http://spam.tinyweb.net/ From cordiste at free.fr Tue Feb 3 15:48:53 2009 From: cordiste at free.fr (cordiste) Date: Tue, 3 Feb 2009 21:48:53 +0100 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <20090203201657.1265997185@smtp.haun-online.de> References: <20090203201657.1265997185@smtp.haun-online.de> Message-ID: <364575ed0902031248h6294aa17vff246b8636c4b684@mail.gmail.com> Today I saw a google way : The AJAX Libraries API is a content distribution network and loading architecture for the most popular, open source JavaScript libraries. By using the Google AJAX API Loader's google.load() method, your application has high speed, globaly available access to a growing list of the most popular, open source JavaScript libraries including: * jQuery * jQuery UI * Prototype * script.aculo.us * MooTools * Dojo * SWFObject * Yahoo! User Interface Library (YUI) http://code.google.com/intl/fr/apis/ajaxlibs/ ::Ben 2009/2/3 Dirk Haun : >>there is clearly a need for a JS library to made it easier >>to code the functions and UI components to handle and enrich the user >>interface. > > So, after only 4 posts I'm already counting recommendations for 6 > different JS libraries :-) > > Which is why my original idea was to set up a GSoC project "Find us an > AJAX library" where we pre-select some candidates and then the student > would implement some tasks with each of them to get a better idea what's > working and what isn't. > > Okay, so maybe a GSoC project would be overkill. Still, I'd like to see > us base a decision on something a bit more substantial than "I'm > familiar with it". > > For example, how do these libraries compare on things like > - security > - footprint / overhead / load times > - ease of use / learning curve > > bye, Dirk > > > -- > http://www.haun-online.de/ > http://spam.tinyweb.net/ > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > From vfuria at gmail.com Tue Feb 3 16:30:13 2009 From: vfuria at gmail.com (Vincent Furia) Date: Tue, 3 Feb 2009 14:30:13 -0700 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <364575ed0902031248h6294aa17vff246b8636c4b684@mail.gmail.com> References: <20090203201657.1265997185@smtp.haun-online.de> <364575ed0902031248h6294aa17vff246b8636c4b684@mail.gmail.com> Message-ID: <8319e2d60902031330i66b0b17o63ed80cba13ea530@mail.gmail.com> Just a warning, while there are some nice advantages to using Google to load these libraries (speed, and only forcing users to have one copy of the libraries cached are the big ones), there are some considerations that need to be made... 1. Geeklog would not control when updated versions get loaded (including security fixes and bug upgrades). 2. If Google is down (or the part of google that hosts the libraries), AJAX won't work on your site. 3. While I doubt Google would go away, there is chance they could stop supporting this service. On the "third" hand, the first and third points are mitigated by this statement: "Google works directly with the key stake holders for each library effort and accepts the latest stable versions as they are released. Once we host a release of a given library, we are committed to hosting that release indefinitely." -Vinny On Tue, Feb 3, 2009 at 1:48 PM, cordiste wrote: > Today I saw a google way : > > The AJAX Libraries API is a content distribution network and loading > architecture for the most popular, open source JavaScript libraries. > By using the Google AJAX API Loader's google.load() method, your > application has high speed, globaly available access to a growing list > of the most popular, open source JavaScript libraries including: > > * jQuery > * jQuery UI > * Prototype > * script.aculo.us > * MooTools > * Dojo > * SWFObject > * Yahoo! User Interface Library (YUI) > > http://code.google.com/intl/fr/apis/ajaxlibs/ > > ::Ben > > > 2009/2/3 Dirk Haun : > >>there is clearly a need for a JS library to made it easier > >>to code the functions and UI components to handle and enrich the user > >>interface. > > > > So, after only 4 posts I'm already counting recommendations for 6 > > different JS libraries :-) > > > > Which is why my original idea was to set up a GSoC project "Find us an > > AJAX library" where we pre-select some candidates and then the student > > would implement some tasks with each of them to get a better idea what's > > working and what isn't. > > > > Okay, so maybe a GSoC project would be overkill. Still, I'd like to see > > us base a decision on something a bit more substantial than "I'm > > familiar with it". > > > > For example, how do these libraries compare on things like > > - security > > - footprint / overhead / load times > > - ease of use / learning curve > > > > bye, Dirk > > > > > > -- > > http://www.haun-online.de/ > > http://spam.tinyweb.net/ > > > > _______________________________________________ > > geeklog-devel mailing list > > geeklog-devel at lists.geeklog.net > > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Randy.Kolenko at nextide.ca Tue Feb 3 16:23:51 2009 From: Randy.Kolenko at nextide.ca (Randy Kolenko) Date: Tue, 3 Feb 2009 16:23:51 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F112139@nex-pluto.nextide.ca> > So, after only 4 posts I'm already counting recommendations > for 6 different JS libraries :-) > Which is "a good thing"(tm) since it should allow the GL community to pick the best one. I vote for Jquery (not for any specific reason other than to make the list of recommendations grow to 7 :-) ) > Which is why my original idea was to set up a GSoC project > "Find us an AJAX library" where we pre-select some candidates > and then the student would implement some tasks with each of > them to get a better idea what's working and what isn't. > > Okay, so maybe a GSoC project would be overkill. Still, I'd > like to see us base a decision on something a bit more > substantial than "I'm familiar with it". > > For example, how do these libraries compare on things like > - security > - footprint / overhead / load times > - ease of use / learning curve > What you list above is really the reason why there are so many different libraries out there. To balance and pick one out should really boil down to the merits of each -- which is easily put into a matrix of sorts to determine and weigh out what is most important to include, and conversely, exclude from a GL distribution. Using the biggest is not always the best, but so too is the exact opposite of not using something big enough. It would seem that we've all got some level of familiarity or expertise with Ajax -- it would probably be in our best collective interest to sort out the details of which library to use and come up with an implementation strategy that could help us ride out a scenario where our chosen library falls out of favour and has to be replaced with a different one. Just my $0.02 worth. -randy From geeklog.nwo at neverbox.com Tue Feb 3 19:02:15 2009 From: geeklog.nwo at neverbox.com (LWC) Date: Wed, 04 Feb 2009 03:02:15 +0300 Subject: [geeklog-devel] Contents of file: message.txt In-Reply-To: <8319e2d60902031330i66b0b17o63ed80cba13ea530@mail.gmail.com> Message-ID: <01c98664$Blat.v2.6.2$39483a7a$e50c0d84a89@weissbrod.com> Let's not forget Google requires each admin to register an API key. In other words, registered a Google API key would be part of Geeklog's system requirements. From dirk at haun-online.de Wed Feb 4 01:54:53 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 4 Feb 2009 07:54:53 +0100 Subject: [geeklog-devel] Contents of file: message.txt In-Reply-To: <01c98664$Blat.v2.6.2$39483a7a$e50c0d84a89@weissbrod.com> References: <8319e2d60902031330i66b0b17o63ed80cba13ea530@mail.gmail.com> <01c98664$Blat.v2.6.2$39483a7a$e50c0d84a89@weissbrod.com> Message-ID: <20090204065453.1203528193@smtp.haun-online.de> LWC wrote: >Let's not forget Google requires each admin to register an API key. In >other words, registered a Google API key would be part of Geeklog's >system requirements. Dependency on an external service for core functionality is not acceptable. The requirement for a personalized key only makes it worse (see SLV vs. Akismet). bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From dirk at haun-online.de Wed Feb 4 13:48:42 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 4 Feb 2009 19:48:42 +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: <20090204184842.1443693924@smtp.haun-online.de> Coming back to this: >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? I'm not so sure about these 3 ideas: * Implement a theme based on the YUI CSS Foundation Libraries * Implement Open Web Analytics * Google Translation API I don't really see them addressing any issues we're currently facing. So my suggestion would be to remove them. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From websitemaster at cogeco.net Thu Feb 5 20:44:31 2009 From: websitemaster at cogeco.net (Website Master) Date: Thu, 5 Feb 2009 20:44:31 -0500 Subject: [geeklog-devel] Word of warning about COM_makeClickableLinks In-Reply-To: <000a01c97f66$177f24d0$467d6e70$@net> References: <01cc01c97d84$72bd8d70$5838a850$@net> <20090124125603.786123483@smtp.haun-online.de> <6D6B99E2-D246-41D3-8C00-3B2A4D1D30FE@griffsweb.com> <000a01c97f66$177f24d0$467d6e70$@net> Message-ID: <005801c987fc$74e4cd70$5eae6850$@net> Question about COM_makeClickableLinks, I haven't look at the recent code but does this still effect autotags in the text? I have an autotag setup that I sometimes pass links into which this function always touches. Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Website Master Sent: January-25-09 10:28 PM To: 'Geeklog Development' Subject: Re: [geeklog-devel] Word of warning about COM_makeClickableLinks 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 _______________________________________________ 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 3799 (20090125) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From info at heatherengineering.com Thu Feb 5 22:03:30 2009 From: info at heatherengineering.com (Euan McKay) Date: Fri, 6 Feb 2009 12:03:30 +0900 Subject: [geeklog-devel] Feature request: cancel edit options Message-ID: When cancelling an edit, the user is sent back to the main admin screen of the plugin or stories etc. I would like to have a config option to send the user back to either the top page, the admin screen, the plugin public page, or the plugin admin page, or the public page of the item that was being edited (if relevant). This is particularly useful for novice users, who get confused when they don't recognise their surroundings. Added to mantis with code example of how I implement this in one plugin: http://project.geeklog.net/tracking/view.php?id=810 Euan. From dirk at haun-online.de Sun Feb 8 05:33:20 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sun, 8 Feb 2009 11:33:20 +0100 Subject: [geeklog-devel] Summer is coming In-Reply-To: <20090204184842.1443693924@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> <20090204184842.1443693924@smtp.haun-online.de> Message-ID: <20090208103320.2050910683@smtp.haun-online.de> >> >> 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? > >I'm not so sure about these 3 ideas: > >* Implement a theme based on the YUI CSS Foundation Libraries >* Implement Open Web Analytics >* Google Translation API > >I don't really see them addressing any issues we're currently facing. So >my suggestion would be to remove them. Since there were no complaints, I moved those to the "leftover ideas" page. I've also added 2 new project ideas, so that we're back up to 10 projects now. I think that's a good amount and a good mix. I couldn't help noticing the absence of any updates for AptitudeCMS projects, though (hint, hint) ... bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Wed Feb 11 15:43:35 2009 From: dirk at haun-online.de (Dirk Haun) Date: Wed, 11 Feb 2009 21:43:35 +0100 Subject: [geeklog-devel] Summer is coming In-Reply-To: <20090204184842.1443693924@smtp.haun-online.de> References: <20090118191539.146575220@smtp.haun-online.de> <20090204184842.1443693924@smtp.haun-online.de> Message-ID: <20090211204335.330461620@smtp.haun-online.de> Seems I can always rely on my local PHP user group for coming up with a presentation on a topic at the right time ... We have this Social Networking project on our GSoC ideas page: http://wiki.geeklog.net/index.php/SoC_socialnetworking It makes a vague reference to the OpenSocial API. After tonight's presentation and a little research, I'd say that would be one heck of a project on its own. Here's a handy list of the required specifications that a conforming server-side application would need to implement: http://groups.google.com/group/opensocial-container/msg/dcaa9862269d4599 The reference implementation (shindig) is licensed under the Apache license and therefore not available for use (unless we wanted to switch to the GPLv3). So I guess the reference to OpenSocial in our project description should be toned down a bit. If at all, that can only be the next step after a project has laid the groundwork and actually added some social network stuff in the first place. bye, Dirk -- http://www.haun-online.de/ http://geeklog.info/ From dirk at haun-online.de Sat Feb 14 13:40:28 2009 From: dirk at haun-online.de (Dirk Haun) Date: Sat, 14 Feb 2009 19:40:28 +0100 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: References: Message-ID: <20090214184028.1608692304@smtp.haun-online.de> So where do we stand? Blaine made a case for YUI and I've seen a few others mentioned. What I haven't seen is a suggested way as to how to arrive at a decision. Saying that we're going with library "X" without really looking at the others doesn't sound right. So, at the risk of sounding like a broken record: How about my idea of trying to implement one or two features with a variety of libraries? If you don't like that idea, please suggest something else. I'll happily bow to the combined expertise of the Geeklog community. Hey, this isn't always a dictatorship ;-) bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From richardsw at nc.rr.com Sun Feb 15 19:25:35 2009 From: richardsw at nc.rr.com (richardsw at nc.rr.com) Date: Sun, 15 Feb 2009 19:25:35 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: Message-ID: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> What is the actual objective of using interactive javascript? (Sorry, just recently joined the list again) From the visitors perspective, much of the content is static to them. Its the editor that is editing content - so in the long run, does using these libraries save you or them any time, or is it there just to be flashy? I hope that actual content rendering isn't littered with javascript, otherwise it will completely kill the SEO advantage that geeklog has by default. If this is a complete rework of the framework, I'd say save this for GL2/AptitudeCMS. Lots of us are used to the way the code is now... that's my non-developer 2 cents. :P Thanks, Rick ---- geeklog-devel-request at lists.geeklog.net wrote: > Send geeklog-devel mailing list submissions to > geeklog-devel at lists.geeklog.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > or, via email, send a message with subject or body 'help' to > geeklog-devel-request at lists.geeklog.net > > You can reach the person managing the list at > geeklog-devel-owner at lists.geeklog.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of geeklog-devel digest..." > > > Today's Topics: > > 1. Re: AJAX and Javascript Libraries - request for comments > (Dirk Haun) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 14 Feb 2009 19:40:28 +0100 > From: "Dirk Haun" > Subject: Re: [geeklog-devel] AJAX and Javascript Libraries - request > for comments > To: geeklog-devel > Message-ID: <20090214184028.1608692304 at smtp.haun-online.de> > Content-Type: text/plain; charset=ISO-8859-1 > > So where do we stand? Blaine made a case for YUI and I've seen a few > others mentioned. What I haven't seen is a suggested way as to how to > arrive at a decision. > > Saying that we're going with library "X" without really looking at the > others doesn't sound right. So, at the risk of sounding like a broken > record: How about my idea of trying to implement one or two features > with a variety of libraries? > > If you don't like that idea, please suggest something else. I'll happily > bow to the combined expertise of the Geeklog community. Hey, this isn't > always a dictatorship ;-) > > 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 > > > End of geeklog-devel Digest, Vol 25, Issue 8 > ******************************************** From dirk at haun-online.de Mon Feb 16 16:40:53 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 16 Feb 2009 22:40:53 +0100 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> References: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> Message-ID: <20090216214053.371860248@smtp.haun-online.de> richardsw at nc.rr.com wrote: >What is the actual objective of using interactive javascript? Well, interactivity ;-) So far the only really useful application would be an auto-save for the editors. You can't really do that any other way. >From the visitors perspective, >much of the content is static to them. Its the editor that is editing >content - so in the long run, does using these libraries save you or >them any time, or is it there just to be flashy? I'm with you on this one - adding flashy things just to be able to say "we're flashy now" shouldn't be the reason. Somebody mentioned editors that open up right on the page where you are. Not sure I see any real advantage in that over getting redirected to the editor when you click on an "edit" link. It may be a solution for the problem of not being able to see a story when you're commenting on it, though. >I hope that actual >content rendering isn't littered with javascript I wouldn't want the either. It does make sense for widgets or something like that (I'm thinking of the rating plugin, for example). But it shouldn't be necessary to display actual content. bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/ From mark at the-howards.net Mon Feb 16 17:39:17 2009 From: mark at the-howards.net (Mark Howard) Date: Mon, 16 Feb 2009 17:39:17 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <20090216214053.371860248@smtp.haun-online.de> References: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> <20090216214053.371860248@smtp.haun-online.de> Message-ID: <005001c99087$670befb0$3523cf10$@net> Couldn't resist jumping in here ... There are obviously a lot of things that can be done on the 'client side' with Javascript, but the two things that I use the JavaScript functions most for are: 1) Populating dynamic content based upon input (dynamic selects) 2) Asynchronous lookup, such as populating/auto-completion based upon partial input 3) Field validation, or modification, such as inline capitalization/formatting/masking, etc. Not necessary 'flashy' stuff, although that can be fun too (and what's wrong with that) ... ;^) -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun Sent: Monday, February 16, 2009 4:41 PM To: geeklog-devel Subject: Re: [geeklog-devel] AJAX and Javascript Libraries - request for comments richardsw at nc.rr.com wrote: >What is the actual objective of using interactive javascript? Well, interactivity ;-) So far the only really useful application would be an auto-save for the editors. You can't really do that any other way. >From the visitors perspective, >much of the content is static to them. Its the editor that is editing >content - so in the long run, does using these libraries save you or >them any time, or is it there just to be flashy? I'm with you on this one - adding flashy things just to be able to say "we're flashy now" shouldn't be the reason. Somebody mentioned editors that open up right on the page where you are. Not sure I see any real advantage in that over getting redirected to the editor when you click on an "edit" link. It may be a solution for the problem of not being able to see a story when you're commenting on it, though. >I hope that actual >content rendering isn't littered with javascript I wouldn't want the either. It does make sense for widgets or something like that (I'm thinking of the rating plugin, for example). But it shouldn't be necessary to display actual content. 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 websitemaster at cogeco.net Mon Feb 16 19:32:46 2009 From: websitemaster at cogeco.net (Website Master) Date: Mon, 16 Feb 2009 19:32:46 -0500 Subject: [geeklog-devel] AJAX and Javascript Libraries - request for comments In-Reply-To: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> References: <20090216002535.MQFAW.39606.root@cdptpa-web12-z01> Message-ID: <004d01c99097$41a84ce0$c4f8e6a0$@net> I don't remember if this was mentioned but Wikipedia is a good place to start for comparisons http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks Tom -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of richardsw at nc.rr.com Sent: February-15-09 7:26 PM To: geeklog-devel at lists.geeklog.net Cc: geeklog-devel-request at lists.geeklog.net Subject: Re: [geeklog-devel] AJAX and Javascript Libraries - request for comments What is the actual objective of using interactive javascript? (Sorry, just recently joined the list again) From the visitors perspective, much of the content is static to them. Its the editor that is editing content - so in the long run, does using these libraries save you or them any time, or is it there just to be flashy? I hope that actual content rendering isn't littered with javascript, otherwise it will completely kill the SEO advantage that geeklog has by default. If this is a complete rework of the framework, I'd say save this for GL2/AptitudeCMS. Lots of us are used to the way the code is now... that's my non-developer 2 cents. :P Thanks, Rick ---- geeklog-devel-request at lists.geeklog.net wrote: > Send geeklog-devel mailing list submissions to > geeklog-devel at lists.geeklog.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > or, via email, send a message with subject or body 'help' to > geeklog-devel-request at lists.geeklog.net > > You can reach the person managing the list at > geeklog-devel-owner at lists.geeklog.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of geeklog-devel digest..." > > > Today's Topics: > > 1. Re: AJAX and Javascript Libraries - request for comments > (Dirk Haun) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 14 Feb 2009 19:40:28 +0100 > From: "Dirk Haun" > Subject: Re: [geeklog-devel] AJAX and Javascript Libraries - request > for comments > To: geeklog-devel > Message-ID: <20090214184028.1608692304 at smtp.haun-online.de> > Content-Type: text/plain; charset=ISO-8859-1 > > So where do we stand? Blaine made a case for YUI and I've seen a few > others mentioned. What I haven't seen is a suggested way as to how to > arrive at a decision. > > Saying that we're going with library "X" without really looking at the > others doesn't sound right. So, at the risk of sounding like a broken > record: How about my idea of trying to implement one or two features > with a variety of libraries? > > If you don't like that idea, please suggest something else. I'll happily > bow to the combined expertise of the Geeklog community. Hey, this isn't > always a dictatorship ;-) > > 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 > > > End of geeklog-devel Digest, Vol 25, Issue 8 > ******************************************** _______________________________________________ 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 3856 (20090216) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com From richardsw at nc.rr.com Tue Feb 17 11:48:22 2009 From: richardsw at nc.rr.com (richardsw at nc.rr.com) Date: Tue, 17 Feb 2009 16:48:22 +0000 Subject: [geeklog-devel] geeklog-devel Digest, Vol 25, Issue 10 In-Reply-To: Message-ID: <20090217164822.18Z0B.38500.root@hrndva-web14-z02> Date: Mon, 16 Feb 2009 22:40:53 +0100 From: "Dirk Haun" Subject: Re: [geeklog-devel] AJAX and Javascript Libraries - request for comments To: geeklog-devel Message-ID: <20090216214053.371860248 at smtp.haun-online.de> Content-Type: text/plain; charset=ISO-8859-1 richardsw at nc.rr.com wrote: >>What is the actual objective of using interactive javascript? > >Well, interactivity ;-) > >So far the only really useful application would be an auto-save for the >editors. You can't really do that any other way. Popup the article editor in a separate window. Add a "Save Draft" button that saves your work with a post and refresh, but keeps you in the window. You can add a very simple javascript refresh that counts up how much typing you've done in the forms. This doesn't really require an entire JS Library does it? Rick From mark at the-howards.net Tue Feb 17 13:00:51 2009 From: mark at the-howards.net (Mark Howard) Date: Tue, 17 Feb 2009 13:00:51 -0500 Subject: [geeklog-devel] geeklog-devel Digest, Vol 25, Issue 10 In-Reply-To: <20090217164822.18Z0B.38500.root@hrndva-web14-z02> References: <20090217164822.18Z0B.38500.root@hrndva-web14-z02> Message-ID: <013301c99129$acc666a0$065333e0$@net> Isn't most of this a whats-in-the-theme conversation? If not, shouldn't it be? To that extent, I agree with Richard, the core should contain no critical dependence upon JS, eg. if JS is enabled then the auto-save doesn't work, no big deal. If folks really don't mean to delete things, then they shouldn't. (the 'are you sure' thing should be a global config option anyway) On the other hand, I'm hopeful that the development team realizes that there are some folks out there that are serving a constituency/client base that are now spoiled by sites like cnet, google and other web 9.4 sites or whatever they're calling them now. For them - let them have their themes and eat them too. -m -----Original Message----- From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of richardsw at nc.rr.com richardsw at nc.rr.com wrote: >>What is the actual objective of using interactive javascript? > >Well, interactivity ;-) > >So far the only really useful application would be an auto-save for the >editors. You can't really do that any other way. Popup the article editor in a separate window. Add a "Save Draft" button that saves your work with a post and refresh, but keeps you in the window. You can add a very simple javascript refresh that counts up how much typing you've done in the forms. This doesn't really require an entire JS Library does it? Rick From Randy.Kolenko at nextide.ca Sat Feb 21 10:55:00 2009 From: Randy.Kolenko at nextide.ca (Randy Kolenko) Date: Sat, 21 Feb 2009 10:55:00 -0500 Subject: [geeklog-devel] geeklog-devel Digest, Vol 25, Issue 10 Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F112149@nex-pluto.nextide.ca> While its true that Geeklog as a core framework is technically sound without the inclusion of javascript libraries for Ajax, the fact is that the core abilities of the framework could use some much needed sprucing up. Yes, you can get away with pop up windows with the editor in it, but that is simply one area that Geeklog needs improvement. In reality, nearly every administration component could benefit greatly from Ajax. New User creation would benefit greatly from look-ahead queries to ensure an admin is not re-creating the same user account -- In reality, all of the fields in the user admin creation area could be Ajax enabled to provide some sort of lookup or general data scrubbing ability so that a whole page POST and refresh is eliminated. Same goes for group adding/editing. Same is true for just about every admin component for nearly all plugins. The calendar could be totally revamped to provide JS overlays to show per-day or per-week events while maintaining the calendar in the background which would totally eliminate a total page re-POST/GET to a whole new page. Simple things like that make the difference in adding polish to the entire portal. (sounds like a good GSoC project :-) ) In fact, the inclusion of a Ajax JS library for Geeklog to use has nothing to do with plugin developers if they so choose not to use THAT specific library. If Geeklog is shipped with Jquery and a plugin author is partial to YUI, then so be it. The plugin is shipped with YUI. Just my $0.02 worth. -randy > -----Original Message----- > From: Mark Howard [mailto:mark at the-howards.net] > Sent: February-17-09 1:01 PM > To: 'Geeklog Development' > Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 25, Issue 10 > > > Isn't most of this a whats-in-the-theme conversation? If > not, shouldn't it be? > > To that extent, I agree with Richard, the core should contain > no critical dependence upon JS, eg. if JS is enabled then the > auto-save doesn't work, no big deal. If folks really don't > mean to delete things, then they shouldn't. (the 'are you > sure' thing should be a global config option anyway) > > On the other hand, I'm hopeful that the development team > realizes that there are some folks out there that are serving > a constituency/client base that are now spoiled by sites like > cnet, google and other web 9.4 sites or whatever they're > calling them now. For them - let them have their themes and > eat them too. > > -m > > -----Original Message----- > From: geeklog-devel-bounces at lists.geeklog.net > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of > richardsw at nc.rr.com > > richardsw at nc.rr.com wrote: > > >>What is the actual objective of using interactive javascript? > > > >Well, interactivity ;-) > > > >So far the only really useful application would be an > auto-save for the > >editors. You can't really do that any other way. > > Popup the article editor in a separate window. Add a "Save > Draft" button that saves your work with a post and refresh, > but keeps you in the window. You can add a very simple > javascript refresh that counts up how much typing you've done > in the forms. This doesn't really require an entire JS > Library does it? > > Rick > > > > _______________________________________________ > geeklog-devel mailing list > geeklog-devel at lists.geeklog.net > http://eight.pairlist.net/mailman/listinfo/geeklog-devel > From dirk at haun-online.de Mon Feb 23 09:13:07 2009 From: dirk at haun-online.de (Dirk Haun) Date: Mon, 23 Feb 2009 15:13:07 +0100 Subject: [geeklog-devel] GSoC: Call for mentors Message-ID: <20090223141307.1170371564@smtp.haun-online.de> As the application period for this year's Summer of Code is drawing closer (March 9-13 for organizations), I'd like to reach out to the Geeklog community and call for people interested in becoming a GSoC mentor. Current and former core developers, former GSoC students, plugin authors and other active members of the Geeklog community: Have you considered becoming a mentor and help our (potential - assuming we get accepted) students with their GSoC project? You would be their first point of contact during the summer (roughly: April 20 - August 25) to discuss ideas and problems. So we're mainly looking for people who are familiar with at least parts of Geeklog's code. But you can always rely on the support of the community, here and in the forums, should you need help. Not sure yet? Here's some more information from Google: And this is the timeline for the Summer of Code: Looking forward to hearing from you! bye, Dirk -- http://www.geeklog.net/ http://geeklog.info/