Re: [Trac] About including jQuery UI in Trac ...
Quoting W. Martin Borgert deba...@debian.org: If e.g. a security bug is found in JQuery, we need only to update the JQuery package with a fixed version and do not need to care about Trac and e.g. half a dozen other packages. Just checked: 58 Debian packages depend on jQuery. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
On Wed, Dec 23, 2009 at 6:34 PM, W. Martin Borgert deba...@debian.org wrote: Quoting Noah Kantrowitz n...@coderanger.net: Just remember the alternative is that every plugin has its own copy. However much work it might be to retrofit Trac to use a central version, it will be much harder to do this for every plugin that wants to use jQuery UI. No question: This would be worse. If plugin X (packaged as deb) depends on `trac` for obvious reasons, and Trac depends on jQuery then there is a transitive deps relationship. So I suppose that no further work will be needed (`trac` will always be a dependency for the plugin ;o), isn't it ? In the end he will end up making reference to the js files using `/chrome/common` If a plugin author doesn't wanna assume the challenge that's (his|her) choice in the end, and he will have one of three options : - do not include the widgets (... and IMHO that means to be frozen in time and obviate the benefits of lovely useful widgets provided by JS UI libs ;o) - bundle jQuery UI with the plugin code (i.e. a lot of copies of the lib js files and an even worst scenario than a single copy inside Trac if packaged as a deb ;o) - reinvent jQuery UI (no further comments) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Assessment of unittest 2.7 API : new features and opinions - http://feedproxy.google.com/~r/simelo-en/~3/cVOgG8NIBFY/assessment-of-unittest-27-api-new.html -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
Quoting Christian Boos cb...@neuf.fr: Ok, I just checked the Deban Changelog (1), the upgrade to 1.3.3 corresponds to some internal debian packaging issues, quite confusing though. Seems to be an error of the Debian maintainer. Trac 0.11.5 had some issues with 1.3.x (2), so I hope you have Trac 0.11.6 in Debian ;-) Yes, at least in unstable, testing, and lenny-backports. Trac 0.11.6 works with jQuery 1.3.x, but we still bundle jQuery 1.2.6 in order to not break Trac plugins which might use the deprecated XPath selector syntax, no longer supported in 1.3.x. OK, such plugins might not work in the forementioned Debian versions. Debian stable has Trac 0.11.1 and jQuery 1.2.6. Therefore the switch to jQuery 1.3.x will be done at the occasion of the Trac 0.12 release, as advertised in TracDev/ApiChanges/0.12 (since 2 minutes ;-) ). What can I say? Congratulations and many thanks! -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
W. Martin Borgert wrote: For distributions such as Debian or Ubuntu it is very important not to duplicate software in the archive, mainly, but not only, for security reasons. Therefore, JQuery is packaged as a Debian package that is used by Trac, but also by other web applications. If e.g. a security bug is found in JQuery, we need only to update the JQuery package with a fixed version and do not need to care about Trac and e.g. half a dozen other packages. While I understand (and agree with) the general idea, I wonder if that situation really applies to jQuery (core, not jQuery UI, see below): - Maybe I'm a bit naive, but what security issues could be in a JavaScript library? Security is provided by the browser, not the libraries, isn't it? - Trac expects to find jquery.js in trac/htdocs/js. So in the Debian packaging, you replace the file provided with Trac with a symlink to the separately-packaged jquery.js? - Do you keep several versions of jQuery installed at the same time on a system, and for every package you link to the required version? Packaging jQuery with Trac (besides simplifying dependencies) ensures that we can make changes to the Trac code required by a jQuery update in sync with the update. If Trac would use an embedded copy of JQuery, why not also include Genshi, Pygments, PySQLite/PsycoPG etc.? I hope, you don't do that :~) Certainly not. There's (at least) one difference with jQuery: it doesn't have a standard packaging, and therefore no standard location in the filesystem where we could easily find it. And even if it did, it's a single file, so I guess it seemed simpler to just include it. I also notice that Gentoo doesn't have a jQuery package (just a data point, certainly not an authoritative argument). This would probably be different for jQuery UI, though. I assume it includes images for the UI controls, so the single file argument drops. Does Debian package jQuery UI? How does it link it into the packages that need it? -- Remy signature.asc Description: OpenPGP digital signature
Re: [Trac] About including jQuery UI in Trac ...
On Tue, Dec 22, 2009 at 11:44 PM, W. Martin Borgert deba...@debian.org wrote: Quoting Olemis Lang ole...@gmail.com: - Why not to include jQuery UI so that plugin developers be able to use those widgets in their own plugins and also custom widgets without bundling jQuery UI core files ? - The same for a jQuey UI theme for Trac ;o) Looking forward to your comments ;o) As one of the packagers of Trac for Debian I have to oppose. (Well, not strongly, but oppose.) For distributions such as Debian or Ubuntu it is very important not to duplicate software in the archive, mainly, but not only, for security reasons. +1 In any case, as Debian packager of Trac I would have to use the Debian JQuery package, not an embedded copy in the Trac archive. If, however, the JQuery version embedded in Trac and the one in Debian diverge, if Debian uses a newer version, I fear, that resulting problems would not have high priority, because the embedded copy works. Well, the risk is probably not so high, but in any case I would prefer to not include any 3rd party SW in the Trac release. Which is cool from a packager perspective but, what about the programmers outside the (great) Debian world ? They have to bundle jQuery UI over and over in every plugin to ensure that it will work everywhere ... If Trac would use an embedded copy of JQuery, why not also include Genshi, Pygments, PySQLite/PsycoPG etc.? I hope, you don't do that :~) I agree with you about not including Py libs in trac package, but perhaps we are talking about two different things. I am mentioning a poor little JS lib bundled with Trac since a long time ago whereas all you mention are Python libs . Isn't it possible to do for jQuery UI (i.e. libjs-jquery-ui) the same thing you do (and I can't figure out ;o) when packaging Trac w/ jQuery (i.e. libjs-jquery) ? @ Remy Blank Q: - Does Debian package jQuery UI? How does it link it into the packages that need it? `libjs-jquery-ui`, and `libjs-jquery` is in recommends so I suppose there's another copy inside Trac ? PS: Hey ! Everybody ! I talked to Santa and he'll bring us many great Trac plugins, so Merry Christmas ! o|;o) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Implemented common `/rpc` path. HTTP 415 error if no match found. Details : - Use content typ... - http://bitbucket.org/osimons/trac-rpc-mq/changeset/1933a7c9c607/ -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
On Wed, Dec 23, 2009 at 11:30 AM, Olemis Lang ole...@gmail.com wrote: On Tue, Dec 22, 2009 at 11:44 PM, W. Martin Borgert deba...@debian.org wrote: Quoting Olemis Lang ole...@gmail.com: [...] PS: Hey ! Everybody ! I talked to Santa and he'll bring us many great Trac plugins, so Merry Christmas ! o|;o) /me hoping for an international conspiration for a 0.12 + jQuery UI release (but Santa told me it's top-secret, and if I insisted he wouldn't take me to Dream-land and I'd miss the big party :( ...) sight :P -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Protocol tab(s) selected in docs on accessing protocol page - http://bitbucket.org/osimons/trac-rpc-mq/changeset/183f38fc0fe9/ -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
Olemis Lang wrote: On Wed, Dec 23, 2009 at 11:30 AM, Olemis Lang ole...@gmail.com wrote: On Tue, Dec 22, 2009 at 11:44 PM, W. Martin Borgert deba...@debian.org wrote: Quoting Olemis Lang ole...@gmail.com: [...] PS: Hey ! Everybody ! I talked to Santa and he'll bring us many great Trac plugins, so Merry Christmas ! o|;o) /me hoping for an international conspiration for a 0.12 + jQuery UI release (but Santa told me it's top-secret, and if I insisted he wouldn't take me to Dream-land and I'd miss the big party :( ...) I think it's a bit premature for 0.12. We don't have yet any use for jQuery UI in Trac itself, so if we would add it just for the plugins without a good internal use case, we will probably not do it correctly. Such an use case could be the date picker for the date fields in the custom query ... some attempts have been made, but nothing satisfying yet. Once 0.12 is out, hopefully someone will send a good patch. Btw, I don't see it as a problem to bundle it with Trac. We would have our own copy, with a well tested version, so what? Debian or other packagers can decide to strip it out and add whatever hoops they want. It will then be up to them to ensure that in the end, the .js files will still be installed when doing a trac-admin env deploy folder. But for Windows for example, it would be silly to require a separate download. So maybe for 0.12.1, once we have a good example usage in Trac core. Ah, and o|;o) too ;-) -- Christian -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
Quoting Remy Blank remy.bl...@pobox.com: - Maybe I'm a bit naive, but what security issues could be in a JavaScript library? Security is provided by the browser, not the libraries, isn't it? In the case of JavaScript, the code runs in the browser, so maybe it could influence client-side security. But in any case, there can be errors in jQuery that need fixes, and there is no need to replace Trac plus other servers, if you can just update jQuery. - Trac expects to find jquery.js in trac/htdocs/js. So in the Debian packaging, you replace the file provided with Trac with a symlink to the separately-packaged jquery.js? Yes. - Do you keep several versions of jQuery installed at the same time on a system, and for every package you link to the required version? There is only one jQuery package in Debian. I hope, that no need arises to keep multiple versions around. Debian could cope with that (we have a lot of libraries etc. in multiple versions), but currently this is not supported for the jQuery package. Packaging jQuery with Trac (besides simplifying dependencies) ensures that we can make changes to the Trac code required by a jQuery update in sync with the update. This is also my fear: If jQuery is packaged with Trac, Trac will maybe depend on a specific version of jQuery and it might be harder for Debian and other distributions to make it work with the version that is supported by the distribution. For jQuery this is risk is probably very low, but it exists. I also notice that Gentoo doesn't have a jQuery package (just a data point, certainly not an authoritative argument). I have a friend at Gentoo, I will immediately tell him, how much better Debian and Ubuntu are, because we have this package :~) This would probably be different for jQuery UI, though. I assume it includes images for the UI controls, so the single file argument drops. Does Debian package jQuery UI? How does it link it into the packages that need it? Currently we have in Debian: libjs-jquery: 1.3.3 libjs-jquery-ui: 1.7.2 libjs-flot: 0.5 Any package that needs a JavaScript Library just symlinks to file it needs. E.g. libjs-jquery provides (among others) the file /usr/share/javascript/jquery/jquery.js The Trac package has a symlink /usr/share/pyshared/trac/htdocs/js/jquery.js to the above file. For Windows-Users it might better to have a kind of Trac meta-package, which contains not only Trac and jQuery, but also other important dependencies, i.e. Python libraries. Whenever I have to work with Windows, I feel relieved, when there is an installer with all I need. Cheers -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
On Wed, Dec 23, 2009 at 6:04 PM, W. Martin Borgert deba...@debian.org wrote: Quoting Remy Blank remy.bl...@pobox.com: [...] Packaging jQuery with Trac (besides simplifying dependencies) ensures that we can make changes to the Trac code required by a jQuery update in sync with the update. This is also my fear: If jQuery is packaged with Trac, Trac will maybe depend on a specific version of jQuery and it might be harder for Debian and other distributions to make it work with the version that is supported by the distribution. For jQuery this is risk is probably very low, but it exists. I am not an expert but I thought `apt` solved this kind of things if e.g. jquery=1.2 was specified in dependencies. Then if there were multiple versions then it selects =1.2.6 (probably multiple repos in sources.list ...) I also notice that Gentoo doesn't have a jQuery package (just a data point, certainly not an authoritative argument). I have a friend at Gentoo, I will immediately tell him, how much better Debian and Ubuntu are, because we have this package :~) lol This would probably be different for jQuery UI, though. I assume it includes images for the UI controls, so the single file argument drops. Does Debian package jQuery UI? How does it link it into the packages that need it? Currently we have in Debian: libjs-jquery: 1.3.3 libjs-jquery-ui: 1.7.2 Hehehe ... and trac works with jquery 1.3.3. or 1.2.6 ? Well, probably does not matter . The only thing that would be needed is a symlink to compatible versions of jQuery + jQuery UI . In the end , major changes are included by Debian packagers too , isn't it ? In the end what programmers (me) care about is about relying on the fact that jQuery UI is there and therefore they won't need to bundle it with each plugin (and not all are in Debian ;o) . Whether it is a symlink or another copy, it's just an implementation detail. libjs-flot: 0.5 cool ! Any package that needs a JavaScript Library just symlinks to file it needs. Love Debian ! -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: All tabs synchronized in RPC docs UI. - http://bitbucket.org/osimons/trac-rpc-mq/changeset/9689e6018102/ -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
RE: [Trac] About including jQuery UI in Trac ...
-Original Message- From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] On Behalf Of W. Martin Borgert Sent: Wednesday, December 23, 2009 3:04 PM To: trac-users@googlegroups.com; Remy Blank Subject: Re: [Trac] About including jQuery UI in Trac ... Quoting Remy Blank remy.bl...@pobox.com: - Maybe I'm a bit naive, but what security issues could be in a JavaScript library? Security is provided by the browser, not the libraries, isn't it? In the case of JavaScript, the code runs in the browser, so maybe it could influence client-side security. But in any case, there can be errors in jQuery that need fixes, and there is no need to replace Trac plus other servers, if you can just update jQuery. - Trac expects to find jquery.js in trac/htdocs/js. So in the Debian packaging, you replace the file provided with Trac with a symlink to the separately-packaged jquery.js? Yes. - Do you keep several versions of jQuery installed at the same time on a system, and for every package you link to the required version? There is only one jQuery package in Debian. I hope, that no need arises to keep multiple versions around. Debian could cope with that (we have a lot of libraries etc. in multiple versions), but currently this is not supported for the jQuery package. Packaging jQuery with Trac (besides simplifying dependencies) ensures that we can make changes to the Trac code required by a jQuery update in sync with the update. This is also my fear: If jQuery is packaged with Trac, Trac will maybe depend on a specific version of jQuery and it might be harder for Debian and other distributions to make it work with the version that is supported by the distribution. For jQuery this is risk is probably very low, but it exists. I also notice that Gentoo doesn't have a jQuery package (just a data point, certainly not an authoritative argument). I have a friend at Gentoo, I will immediately tell him, how much better Debian and Ubuntu are, because we have this package :~) This would probably be different for jQuery UI, though. I assume it includes images for the UI controls, so the single file argument drops. Does Debian package jQuery UI? How does it link it into the packages that need it? Currently we have in Debian: libjs-jquery: 1.3.3 libjs-jquery-ui: 1.7.2 libjs-flot: 0.5 Any package that needs a JavaScript Library just symlinks to file it needs. E.g. libjs-jquery provides (among others) the file /usr/share/javascript/jquery/jquery.js The Trac package has a symlink /usr/share/pyshared/trac/htdocs/js/jquery.js to the above file. For Windows-Users it might better to have a kind of Trac meta-package, which contains not only Trac and jQuery, but also other important dependencies, i.e. Python libraries. Whenever I have to work with Windows, I feel relieved, when there is an installer with all I need. Just remember the alternative is that every plugin has its own copy. However much work it might be to retrofit Trac to use a central version, it will be much harder to do this for every plugin that wants to use jQuery UI. --Noah -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
RE: [Trac] About including jQuery UI in Trac ...
Quoting Noah Kantrowitz n...@coderanger.net: Just remember the alternative is that every plugin has its own copy. However much work it might be to retrofit Trac to use a central version, it will be much harder to do this for every plugin that wants to use jQuery UI. No question: This would be worse. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] About including jQuery UI in Trac ...
Olemis Lang wrote: - Why not to include jQuery UI so that plugin developers be able to use those widgets in their own plugins and also custom widgets without bundling jQuery UI core files ? I haven't used jQuery UI yet, but assuming it has the same exceptional quality as jQuery (I'm sure it has), and the license permits direct inclusion, I'm sure this would come in handy. -- Remy signature.asc Description: OpenPGP digital signature
Re: [Trac] About including jQuery UI in Trac ...
Quoting Olemis Lang ole...@gmail.com: - Why not to include jQuery UI so that plugin developers be able to use those widgets in their own plugins and also custom widgets without bundling jQuery UI core files ? - The same for a jQuey UI theme for Trac ;o) Looking forward to your comments ;o) As one of the packagers of Trac for Debian I have to oppose. (Well, not strongly, but oppose.) For distributions such as Debian or Ubuntu it is very important not to duplicate software in the archive, mainly, but not only, for security reasons. Therefore, JQuery is packaged as a Debian package that is used by Trac, but also by other web applications. If e.g. a security bug is found in JQuery, we need only to update the JQuery package with a fixed version and do not need to care about Trac and e.g. half a dozen other packages. In any case, as Debian packager of Trac I would have to use the Debian JQuery package, not an embedded copy in the Trac archive. If, however, the JQuery version embedded in Trac and the one in Debian diverge, if Debian uses a newer version, I fear, that resulting problems would not have high priority, because the embedded copy works. Well, the risk is probably not so high, but in any case I would prefer to not include any 3rd party SW in the Trac release. If Trac would use an embedded copy of JQuery, why not also include Genshi, Pygments, PySQLite/PsycoPG etc.? I hope, you don't do that :~) -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
