On Mon, Jan 17, 2011 at 6:19 PM, Garrett Smith <[email protected]>wrote:
> On 1/17/11, Miller Medeiros <[email protected]> wrote: > > since in your case it seems to be just one, I would just store a single > > cookie with the name of the setting and since you are already using > jQuery > > search for a cookie plugin, > > JQ plugins are not known for robust. And they tend to have problems > when updating JQ. > > Better to analyze the problem and come up with a solution that matches > that. The idea of solving the unknown with JQ is a trend that needs to > die. > jQuery is fairly easy to use and has a lot of info available online.. not my preferred code style but for DOM manipulation does it job well... easy to write spaggethi code but not impossible to keep it organized.. if you are a beginner it is way easier to find information and understand jQuery tutorials than find out how to generate a Date object with a future Date (eg. 5 hours in the future) and find out that you have to convert it to a UTC String and append to the document.cookie string... PS: I'm against jQuery plugins as well (in most of the cases) and avoid using them as much as I can.. I even wrote about it here: http://blog.millermedeiros.com/2010/08/stop-writing-plugins-start-writing-components/ PS2: the cookie API sucks.. who thought that using a string was a good idea? -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
