Sounds great! Just one question though... I'm thinking upgrade paths, what happens when upgrading the plugin... I know I made some changes to the your wiki code on my mac (some good, and most probably bad ;)). The point is, I didn't document my changes (at least what I think were good changes for me), and I"m not sure what happens behind the scenes when installing the plugin, but do we consider upgrade paths (i.e. checking against version for such things as version to version core differences? oh, and changes to app configuration files (i.e. maybe I added some updated jQuery resources, I'm not saying that any of this is worth saving, but... I guess, I'm asking if you would recommend upgrading apps to the new version, or would you recommend it for new applications?
Thanks, Mart :) On Sep 25, 7:37 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > No. > > The main changes are > > 1) you can set: > > plugins.wiki.widgets=['youtube','slideshow'] > > to limit the number of available widgets. > > plugins.wiki.widgets='all' > > for all. > > 2) you can pass a url to plugin_wiki.render to use a different URL. > This is because I want to use the render function to render content > that is not stored in plugin_wiki_page and want to be able to > redefined the meaning of [[link page:name]] to <a href="...name">link</ > a> where ... is what you can now pass to render. > > 3) Fixed a bug in slideshow and allowed a new fields "links" where you > can simply pass a list of comma separated urls. > > Massimo > > On Sep 25, 6:23 pm, Bruno Rocha <rochacbr...@gmail.com> wrote: > > > Is there a repository or another place where we can see the change log for > > plugin_wiki? > > > I am going to try this now. > > > Tks Massimo. > > > 2010/9/25 mdipierro <mdipie...@cs.depaul.edu> > > > > fixed some bugs and made it more general. > > > -- > > >http://rochacbruno.com.br > >
