From kyle.shank at gmail.com Wed Aug 24 10:54:29 2005 From: kyle.shank at gmail.com (Kyle Shank) Date: Wed Aug 24 10:48:03 2005 Subject: [Rubish-devel] Welcome to the list Message-ID: <1165359305082407545ee4652b@mail.gmail.com> Hey everyone. Please give a ping back to ensure this is setup correctly. Cheers, Kyle From zabouti at gmail.com Wed Aug 24 17:07:54 2005 From: zabouti at gmail.com (George Entenman) Date: Wed Aug 24 17:01:20 2005 Subject: [Rubish-devel] Welcome to the list In-Reply-To: <1165359305082407545ee4652b@mail.gmail.com> References: <1165359305082407545ee4652b@mail.gmail.com> Message-ID: <87c6dde705082414075327cd88@mail.gmail.com> I got it. -- ge On 8/24/05, Kyle Shank wrote: > Hey everyone. > > Please give a ping back to ensure this is setup correctly. > > Cheers, > Kyle > > _______________________________________________ > Rubish-devel mailing list > Rubish-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubish-devel > -- Besta ? tu se voc? n?o viver nesse mundo My blogs: http://george.entenman.name http://capitalistcontradictions.com From zabouti at gmail.com Sat Aug 27 09:49:14 2005 From: zabouti at gmail.com (George Entenman) Date: Sat Aug 27 09:42:36 2005 Subject: [Rubish-devel] tags in rubish Message-ID: <87c6dde705082706497db4c242@mail.gmail.com> I just noticed that TxD has made LightPress, a frontend to WordPress, into an officially supported TxD project. Check out a post on their use of tags: http://lightpress.org/post/lighttags Then go here and click on the Tags menu: http://vapourtrails.ca/ That makes sense. I still like to navigate websites (old guy, remember) and wonder if arbitrary user tags can somehow be dynamically grafted onto a site's fixed menu/navigation system? Suppose I come into my local political party's site and navigate thusly: home announcements precincts district 1 district 2 precinct 1 precinct 2 -- I post here and add a tag 'house party' precinct 3 precinct 4 district 3 district 4 volunteer Now, when someone navigates down to my precinct, they see: home announcements precincts district 1 district 2 precinct 1 precinct 2 house party precinct 3 precinct 4 district 3 district 4 volunteer And 'house party' would also show up in a tag 'cloud' like http://vapourtrails.ca/tag/ if it's one of the top 50 tags, say. Or maybe each node of the navigation tree would have its own little tag cloud, showing only tags that were posted at or below that level.... Perhaps if I posted my article under two categories (thinking in drupal terms), it would appear as a menu item and in the tag cloud in two places: home announcements precincts district 1 district 2 precinct 1 precinct 2 house party precinct 3 precinct 4 district 3 district 4 volunteer phone banking neighborhood activism house party party support tables street fairs Kyle and Matt, I know you have lots more experience with navigation schemes and you probably have a clearer idea of how navigation, categories and tagging will work and interact. I think of navigation as a directed, often cyclic, graph allowing navigation to a given node in multiple ways, and I want tags to be part of that. I guess I want to add some bit of hierarchy (categorization) to each tag to help prevent the tag cloud from getting too big, to the point where all we can do is list the top 50 tags rather than, say, the top 50 under volunteering. -- ge P.S. Had a nice irc chat with Marc last night. I like starting with people who are physically nearby. -- Besta ? tu se voc? n?o viver nesse mundo http://george.entenman.name http://capitalistcontradictions.com From kyle.shank at gmail.com Mon Aug 29 15:04:08 2005 From: kyle.shank at gmail.com (Kyle Shank) Date: Mon Aug 29 14:57:26 2005 Subject: [Rubish-devel] Module Framework Message-ID: <1165359305082912046ebc0bec@mail.gmail.com> The module framework will be the most important piece to the foundation of the rubish CMS. Every successful CMS in the past (e.g. Drupal,Nuke) has implemented some variation on a modular framework that allows for the plugging in and out of pre-packaged features. Modularity is a key component of any content management system that wants to leave an open door to future functionality. While discussing a system built with nice and cleanly seperate modules sounds like a given, actually achieving it is something else altogether. Several issues arise when trying to design a modular framework: * Performance * Packaging * Integration * Cross-Module communication Ok, so we want rubish to have a modular framework that performs well, can be packaged up easily, integrates seamless with Rails and allows for simple cross module communication (e.g. A Podcast module talking to a Blog module in order to post shownotes). I'll have more on this on the wiki soon, just wanted to circulate the primer to get everyone thinking about this. -Kyle From kyle.shank at gmail.com Mon Aug 29 15:15:06 2005 From: kyle.shank at gmail.com (Kyle Shank) Date: Mon Aug 29 15:08:24 2005 Subject: [Rubish-devel] tags in rubish In-Reply-To: <87c6dde705082706497db4c242@mail.gmail.com> References: <87c6dde705082706497db4c242@mail.gmail.com> Message-ID: <1165359305082912152b3ca145@mail.gmail.com> George, I like your approach to public tagging. As we discussed before there is a difference between public/private tagging. Public tagging could be really cool and neat; we just have to ensure that the basic navigation structure remains so that people can get around the site. The risk with public tagging is that its open format lets things get out of control and we obviously don't want someone blowing away the primary home/about/contact links on a website, etc. So I think we can accomplish some neat, community driven navigation with clever interface (possibly some AJAX etc) design. We just need to decide where we would draw certain access or permissions lines. For example, do we limit people to contributing to the second or their tier of navigation etc. Discuss. Cheers, Kyle On 8/27/05, George Entenman wrote: > I just noticed that TxD has made LightPress, a frontend to WordPress, > into an officially supported TxD project. > > Check out a post on their use of tags: http://lightpress.org/post/lighttags > Then go here and click on the Tags menu: http://vapourtrails.ca/ > > That makes sense. > > I still like to navigate websites (old guy, remember) and wonder if > arbitrary user tags can somehow be dynamically grafted onto a site's > fixed menu/navigation system? > > Suppose I come into my local political party's site and navigate thusly: > > home > announcements > precincts > district 1 > district 2 > precinct 1 > precinct 2 > -- I post here and add a tag 'house party' > precinct 3 > precinct 4 > district 3 > district 4 > volunteer > > Now, when someone navigates down to my precinct, they see: > > home > announcements > precincts > district 1 > district 2 > precinct 1 > precinct 2 > house party > precinct 3 > precinct 4 > district 3 > district 4 > volunteer > > And 'house party' would also show up in a tag 'cloud' like > http://vapourtrails.ca/tag/ if it's one of the top 50 tags, say. > > Or maybe each node of the navigation tree would have its own little > tag cloud, showing only tags that were posted at or below that > level.... > > Perhaps if I posted my article under two categories (thinking in > drupal terms), it would appear as a menu item and in the tag cloud in > two places: > > home > announcements > precincts > district 1 > district 2 > precinct 1 > precinct 2 > house party > precinct 3 > precinct 4 > district 3 > district 4 > volunteer > phone banking > neighborhood activism > house party > party support > tables > street fairs > > Kyle and Matt, I know you have lots more experience with navigation > schemes and you probably have a clearer idea of how navigation, > categories and tagging will work and interact. I think of navigation > as a directed, often cyclic, graph allowing navigation to a given node > in multiple ways, and I want tags to be part of that. I guess I want > to add some bit of hierarchy (categorization) to each tag to help > prevent the tag cloud from getting too big, to the point where all we > can do is list the top 50 tags rather than, say, the top 50 under > volunteering. > > -- ge > > P.S. Had a nice irc chat with Marc last night. I like starting with > people who are physically nearby. > > > -- > Besta ? tu se voc? n?o viver nesse mundo > http://george.entenman.name > http://capitalistcontradictions.com > > _______________________________________________ > Rubish-devel mailing list > Rubish-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubish-devel > From zabouti at gmail.com Mon Aug 29 22:34:05 2005 From: zabouti at gmail.com (George Entenman) Date: Mon Aug 29 22:27:22 2005 Subject: [Rubish-devel] Module Framework In-Reply-To: <1165359305082912046ebc0bec@mail.gmail.com> References: <1165359305082912046ebc0bec@mail.gmail.com> Message-ID: <87c6dde70508291934445aa8d2@mail.gmail.com> On 8/29/05, Kyle Shank wrote: > The module framework will be the most important piece to the > foundation of the rubish CMS. Every successful CMS in the past (e.g. > Drupal,Nuke) has implemented some variation on a modular framework > that allows for the plugging in and out of pre-packaged features. > Modularity is a key component of any content management system that > wants to leave an open door to future functionality. While discussing > a system built with nice and cleanly seperate modules sounds like a > given, actually achieving it is something else altogether. > > Several issues arise when trying to design a modular framework: > > * Performance > * Packaging > * Integration > * Cross-Module communication > > Ok, so we want rubish to have a modular framework that performs well, > can be packaged up easily, integrates seamless with Rails and allows > for simple cross module communication (e.g. A Podcast module talking > to a Blog module in order to post shownotes). > > I'll have more on this on the wiki soon, just wanted to circulate the > primer to get everyone thinking about this. > > -Kyle Kyle, I've mainly dealt with modules as someone installing them, not as someone writing them. >From a programming point of view, it seems to me that modules should subclass the main rubish modules. Is that how modules are usually implemented? Not even sure this is a well-formed question, but thought I'd toss it out. -- ge -- Besta ? tu se voc? n?o viver nesse mundo http://george.entenman.name http://capitalistcontradictions.com From kyle.shank at gmail.com Mon Aug 29 22:43:26 2005 From: kyle.shank at gmail.com (Kyle Shank) Date: Mon Aug 29 22:36:44 2005 Subject: [Rubish-devel] Module Framework In-Reply-To: <87c6dde70508291934445aa8d2@mail.gmail.com> References: <1165359305082912046ebc0bec@mail.gmail.com> <87c6dde70508291934445aa8d2@mail.gmail.com> Message-ID: <11653593050829194325617597@mail.gmail.com> Yes there will be some superclass structure etc. That part is not hard. The hard issue we're going to run into is: how do we integrate our module framework with the rails framework itself. -Kyle On 8/29/05, George Entenman wrote: > On 8/29/05, Kyle Shank wrote: > > The module framework will be the most important piece to the > > foundation of the rubish CMS. Every successful CMS in the past (e.g. > > Drupal,Nuke) has implemented some variation on a modular framework > > that allows for the plugging in and out of pre-packaged features. > > Modularity is a key component of any content management system that > > wants to leave an open door to future functionality. While discussing > > a system built with nice and cleanly seperate modules sounds like a > > given, actually achieving it is something else altogether. > > > > Several issues arise when trying to design a modular framework: > > > > * Performance > > * Packaging > > * Integration > > * Cross-Module communication > > > > Ok, so we want rubish to have a modular framework that performs well, > > can be packaged up easily, integrates seamless with Rails and allows > > for simple cross module communication (e.g. A Podcast module talking > > to a Blog module in order to post shownotes). > > > > I'll have more on this on the wiki soon, just wanted to circulate the > > primer to get everyone thinking about this. > > > > -Kyle > > Kyle, > > I've mainly dealt with modules as someone installing them, not as > someone writing them. > > From a programming point of view, it seems to me that modules should > subclass the main rubish modules. Is that how modules are usually > implemented? > > Not even sure this is a well-formed question, but thought I'd toss it out. > > -- ge > > > -- > Besta ? tu se voc? n?o viver nesse mundo > http://george.entenman.name > http://capitalistcontradictions.com >