Re: [Radiant] Re: Layouts, snippets and site assets on the file system?
Nice work, Andrew. I wonder how hard it would to get this extension to also dump and load SnS text assets. Not that any of the extensions should have a dependency on the other, but the file-system-extension could perhaps check for the presence of SnS and dump that too, if present? Cheers, Casper On 31/07/2008, at 8:28, Andrew Neil wrote: On 14 Jun 2008, at 18:51, Sean Cribbs wrote: Jonathan McCoy wrote: Highly unlikely. FUSE is a modular file system API - basically a simple means to build your own file system without actually having to do anything majorly complex. Although yes, what you linked to would be a cool solution - it still lacks version control. You'd also have to make it uber-bespoke to Radiant, and to each model in the Radiant schema, otherwise you'll be working with YAML etc. If somebody did build a FUSE interface for Radiant, it would be nice if each page is represented by a folder, with files corresponding to each page part, with the extension being the filter used. A meta file could contain the overall page settings. You just described the file_system extension written for Redken to a T. I would like to release it but I'm not ready to support it yet or to detox the code. I asked Sean if I could have a go at detoxing his code myself. I've stripped out all of the Redken specific functionality, and got the extension working on a vanilla Radiant site (i.e. with no other extensions). Here it is: http://github.com/nelstrom/radiant-file-system-extension/tree/master I'd be happy to hear any feedback. Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Layouts, snippets and site assets on the file system?
When I designed the extension, I toyed with the idea of providing a way for extensions to specify how to dump/load their own models. IIRC, you can just create an appropriately named module and then add the model to the constant array in the FileSystem module. You should probably do all of that in your extension file. Sean Casper Fabricius wrote: Nice work, Andrew. I wonder how hard it would to get this extension to also dump and load SnS text assets. Not that any of the extensions should have a dependency on the other, but the file-system-extension could perhaps check for the presence of SnS and dump that too, if present? Cheers, Casper On 31/07/2008, at 8:28, Andrew Neil wrote: On 14 Jun 2008, at 18:51, Sean Cribbs wrote: Jonathan McCoy wrote: Highly unlikely. FUSE is a modular file system API - basically a simple means to build your own file system without actually having to do anything majorly complex. Although yes, what you linked to would be a cool solution - it still lacks version control. You'd also have to make it uber-bespoke to Radiant, and to each model in the Radiant schema, otherwise you'll be working with YAML etc. If somebody did build a FUSE interface for Radiant, it would be nice if each page is represented by a folder, with files corresponding to each page part, with the extension being the filter used. A meta file could contain the overall page settings. You just described the file_system extension written for Redken to a T. I would like to release it but I'm not ready to support it yet or to detox the code. I asked Sean if I could have a go at detoxing his code myself. I've stripped out all of the Redken specific functionality, and got the extension working on a vanilla Radiant site (i.e. with no other extensions). Here it is: http://github.com/nelstrom/radiant-file-system-extension/tree/master I'd be happy to hear any feedback. Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Layouts, snippets and site assets on the file system?
Nice - thanks, Sean On 31/07/2008, at 15:00, Sean Cribbs wrote: When I designed the extension, I toyed with the idea of providing a way for extensions to specify how to dump/load their own models. IIRC, you can just create an appropriately named module and then add the model to the constant array in the FileSystem module. You should probably do all of that in your extension file. Sean Casper Fabricius wrote: Nice work, Andrew. I wonder how hard it would to get this extension to also dump and load SnS text assets. Not that any of the extensions should have a dependency on the other, but the file- system-extension could perhaps check for the presence of SnS and dump that too, if present? Cheers, Casper On 31/07/2008, at 8:28, Andrew Neil wrote: On 14 Jun 2008, at 18:51, Sean Cribbs wrote: Jonathan McCoy wrote: Highly unlikely. FUSE is a modular file system API - basically a simple means to build your own file system without actually having to do anything majorly complex. Although yes, what you linked to would be a cool solution - it still lacks version control. You'd also have to make it uber-bespoke to Radiant, and to each model in the Radiant schema, otherwise you'll be working with YAML etc. If somebody did build a FUSE interface for Radiant, it would be nice if each page is represented by a folder, with files corresponding to each page part, with the extension being the filter used. A meta file could contain the overall page settings. You just described the file_system extension written for Redken to a T. I would like to release it but I'm not ready to support it yet or to detox the code. I asked Sean if I could have a go at detoxing his code myself. I've stripped out all of the Redken specific functionality, and got the extension working on a vanilla Radiant site (i.e. with no other extensions). Here it is: http://github.com/nelstrom/radiant-file-system-extension/tree/master I'd be happy to hear any feedback. Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
