I seem to recall an extension for VIM that allowed you to edit stuff
in Radiant using VIM. You might give that a try. I can't imagine file-
based stuff making it into core though. Perhaps the closest we would
get to that would be an import/export feature.
--John
On Aug 25, 2008, at 1:03
The file_system extension exists for this purpose. Check it out:
http://github.com/nelstrom/radiant-file-system-extension/tree/master
I should warn you that it is still under development, so if you do use
it, take care! I would appreciate feedback on any problems you
encounter.
Drew
On
Yes,
as I told in a previous post
(http://www.ruby-forum.com/topic/163688#new) I'm actually using Andrew's
extension to dump my Radiant layout for the following pourposes:
- backup versioning:
via rake file_system:save I dump the layout onto the filesystem, than
I make some html/css changes
Andrew Neil wrote:
The file_system extension exists for this purpose. Check it out:
http://github.com/nelstrom/radiant-file-system-extension/tree/master
I should warn you that it is still under development, so if you do use
it, take care! I would appreciate feedback on any problems you
On 25 Aug 2008, at 14:13, Arik Jones wrote:
Andrew Neil wrote:
The file_system extension exists for this purpose. Check it out:
http://github.com/nelstrom/radiant-file-system-extension/tree/master
I should warn you that it is still under development, so if you do
use
it, take care! I
I think it would be quite straightforward to add the functionality in
a similar fashion for 'text-assets' such as stylesheets and javascript
files. If I understand Sean's design correctly, I think his intention
was that extension authors could make their custom models play with
the
I just had a crazy idea.
I'm looking for a way for users to have a draft version of the site.
When it's ready, they click a button and the pages/snippets/layouts
that are published get transferred over to the new site.
What if:
When they click Publish Site:
* test site does a rake
Back in December 2007 I wrote a quickie extension for someone to have
two separate sites, one being preview and one being live. In the end,
we decided it would be easiest to copy a SQLite3 database file from the
preview site to the live site (luckily on the same box). No version
control, but
I wrote an extension that is being used in production that does
something very similar. We have a staging environment and a
production environment. The production environment is read-only. The
users make all their changes on the staging environment. When they
are ready to migrate the changes
I just sent a pull request to make RedCloth a gem dependency, so
hopefully edge will have that ability soon.
In the meantime, I used some code like this in an extension:
# Get the latest version of RedCloth
Object.send :remove_const, :RedCloth if Object.const_defined?(:RedCloth)
$:.delete
Make that:
# Get the latest version of RedCloth
Object.send :remove_const, :RedCloth if Object.const_defined?
(:RedCloth) RedCloth::VERSION.is_a?(String)
$:.delete File.join(RADIANT_ROOT, 'vendor', 'redcloth', 'lib')
gem 'RedCloth', '= 4.0.3'
require 'RedCloth'
On Aug 25, 2008, at 4:24 PM,
It just so happens that I was playing around with getting the
file_system extension to work with SNS when I came across a nasty
conflict. It seems that SNS uses the attribute filename instead of
name. Because the file_system extension uses this as well, it leads to
all sorts of nasty
On Aug 25, 2008, at 4:35 PM, Sean Cribbs wrote:
I think it would be quite straightforward to add the functionality
in a similar fashion for 'text-assets' such as stylesheets and
javascript files. If I understand Sean's design correctly, I think
his intention was that extension authors
Oh, I forgot to mention that your extension must load before the
file_system extension for this to work:
config.extensions = [:all, :file_system]
-- should do the trick in config/environment.rb.
Sean
Keith Bingman wrote:
On Aug 25, 2008, at 4:35 PM, Sean Cribbs wrote:
I think it would
14 matches
Mail list logo
