Thank you for providing excellent tools. I''d like to know about the partial site generation provided by webgen 0.5.2. http://rubyforge.org/forum/forum.php?forum_id=26516> When a file that was in the menu changed, all files which > included a menu with a link to this file got regenerated, > too. However, that was not always necessary since the content > of the changed file does not appear in the menu, only its meta > information `title`. Therefore the new system checks if the > meta information of the changed file has changed and only then > regenerates all menus. This system is now also used by all > other extensions like the breadcrumb trail or the langbar tag.I''m using webgen 0.5.2 on Windows Vista. with Ruby 1.8.6. I simply created a sample site using command ''webgen create test'', and created two pages ''test1.page'' and ''test2.page''. test |- src |- index.page |- test1.page |- test2.page |- metainfo I specified the all meta information of the pages in ''metainfo'' file. metainfo: --- name:paths index.page: title: Index page in_menu: true routed_title: New Website test1.page: title: Test Page 1 in_menu: true test2.page: title: Test Page 2 in_menu: true In the files, ''index.page'', ''test1.page'', and ''test2.page'', I only wrote their content without the meta information as below. test1.page: ## Page 1 This is Page 1. Although I guessed wrong, I understood that, if I change the content of a file without changing its meta information, other files in the menu are not regenerated. But, whenever I change the content of ''test2.page'', ''index.html'' and ''test1.html'' are always regenerated. Did I misunderstand what the partial generation means? -- Kensuke Hoshitani
Am Sat, 16 Aug 2008 21:06:28 +0900 schrieb Kensuke Hoshitani <ml at hoshitani.com>:> Thank you for providing excellent tools. > I''d like to know about the partial site generation provided by webgen > 0.5.2. > > http://rubyforge.org/forum/forum.php?forum_id=26516 > > When a file that was in the menu changed, all files which > > included a menu with a link to this file got regenerated, > > too. However, that was not always necessary since the content > > of the changed file does not appear in the menu, only its meta > > information `title`. Therefore the new system checks if the > > meta information of the changed file has changed and only then > > regenerates all menus. This system is now also used by all > > other extensions like the breadcrumb trail or the langbar tag. > > I''m using webgen 0.5.2 on Windows Vista. with Ruby 1.8.6. > I simply created a sample site using command ''webgen create test'', > and created two pages ''test1.page'' and ''test2.page''. > > <SNIP> > > Although I guessed wrong, I understood that, if I change the content > of a file without changing its meta information, other files in the > menu are not regenerated. But, whenever I change the content of > ''test2.page'', ''index.html'' and ''test1.html'' are always regenerated. > Did I misunderstand what the partial generation means?No, you did not misunderstand partial generation. I forgot to update Webgen::SourceHandler::Metainfo to set Node#dirt_meta_info instead of Node#dirty and just uncovered two other bugs in the code which prevented your example from working. I have fixed all these issues and the repo version now works fine on your provided test case. I have pushed the updated code to the Rubyforge and Github repositories! -- Thomas
Hello, On Sun, 17 Aug 2008 08:39:35 +0200 Thomas Leitner <t_leitner at gmx.at> wrote:> > No, you did not misunderstand partial generation. I forgot to update > Webgen::SourceHandler::Metainfo to set Node#dirt_meta_info instead of > Node#dirty and just uncovered two other bugs in the code which > prevented your example from working. I have fixed all these issues and > the repo version now works fine on your provided test case. > > I have pushed the updated code to the Rubyforge and Github repositories!Thank you for the quick response and great work. I have downloaded the updated code from Github repositories. Now everything works fine. The partial site generation is very helpful. This is what I really wanted to use. -- Kensuke Hoshitani