Re: [Radiant] new user questions

[John W. Long]

David Minor wrote:
> On Mar 8, 2007, at 9:37 AM, John W. Long wrote:
> 
>> I'd suggest the "Edit in Textmate"
>> command (if you are a Textmate user or something similar if you use
>> another editor).
> 
> sorry john,  I'm not following you.  what?

TextMate has a feature which allows you to press a special hotkey that 
you can press when you are in a browser which allows you edit the text 
of the current textarea from within the TextMate editor. It's great when 
you need to edit a complex stylesheet or layout.

--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] new user questions

[David Minor]

On Mar 8, 2007, at 9:37 AM, John W. Long wrote:

> I'd suggest the "Edit in Textmate"
> command (if you are a Textmate user or something similar if you use
> another editor).

sorry john,  I'm not following you.  what?


___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant 0.6 RC2 and extensions (Was: Radiant 0.6 RC2)

[John W. Long]

Erik van Oosten wrote:
> Instance mode is the mode where the whole Radiant code is copied into 
> your project?

No. Application mode is where you are running straight off the source.

> If I understand correctly, instance mode is required to develop 
> extensions (which I intend to to). Or are there other means?

No. Instance mode is not required to develop extensions.

> I am sorry, its all a bit vague to me. Perhaps I have not yet seen the 
> right documentation. Or perhaps there are just too many options :)

The documentation for it is a bit poor. Instance mode is what you get 
when you install radiant from a gem and run:

% radiant /path/to/my/project

To create the default structure for your site. The main benefit to 
instance mode is that the source code for Radiant can reside in the gem 
but the Radiant project contains all of your configuration. This makes 
it easy to upgrade. In the future the upgrade process will be as simple as:

1. Install the new gem:

% gem update radiant

2. Update your config/environment.rb so that it uses the latest gem.

3. Update your radiant project:

% rake radiant:update

4. Run any migrations:

% rake production db:migrate

The other way of installing Radiant is known as "Application" mode. 
Application mode is what you get when you install Radiant by extracting 
the source into your project directory. If you install Radiant this way 
you will be on your own when it comes to upgrading your version of 
Radiant. Because of this instance mode is the recommended way of 
installing Radiant.

> What would be the appropriate way to operate when you want to develop an 
> extension which will be available for others, potentially through svn, 
> but definitely through some other way (gem?)? (Perhaps important: I 
> still did not have time to finish my svn setup.)

You can develop extensions in instance mode or application mode. To get 
started just run the following command from your project root:

% script/generate MyExtensionName

--
John Long
http://wiseheartdesign.com

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Radiant 0.6 RC2 and extensions (Was: Radiant 0.6 RC2)

[Erik van Oosten]

Instance mode is the mode where the whole Radiant code is copied into 
your project?
If I understand correctly, instance mode is required to develop 
extensions (which I intend to to). Or are there other means?

I am sorry, its all a bit vague to me. Perhaps I have not yet seen the 
right documentation. Or perhaps there are just too many options :)

What would be the appropriate way to operate when you want to develop an 
extension which will be available for others, potentially through svn, 
but definitely through some other way (gem?)? (Perhaps important: I 
still did not have time to finish my svn setup.)

I wrote a camping application to manage a virtual e-mail domain with 
postfix (redirects only). I would like to convert it to a Radiant extension.

Regards,
Erik.


John W. Long wrote:
> John W. Long wrote:
>   
>> Read all about it:
>>
>> http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/
>> 
>
> I should also add that RC2 includes recent changes in Mental that allow 
> you to run script/generate in instance mode:
>
>script/generate extension AssetManager
>
> --
> John Long
> http://wiseheartdesign.com
>   

-- 
Erik van Oosten
http://day-to-day-stuff.blogspot.com/

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant 0.6 RC2

[John W. Long]

John W. Long wrote:
> Read all about it:
> 
> http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/

I should also add that RC2 includes recent changes in Mental that allow 
you to run script/generate in instance mode:

   script/generate extension AssetManager

--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant 0.6 RC2

[John W. Long]

Erik van Oosten wrote:
> How do you upgrade from RC1?

Uninstall the old gem and install the new one. Then run:

rake radiant:update

--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant 0.6 RC2

[Erik van Oosten]

Great!

How you upgrade from RC1?

Regards,
Erik.


John W. Long wrote:
> Read all about it:
>
> http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/
>
>   

-- 
Erik van Oosten
http://day-to-day-stuff.blogspot.com/

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Help on Extension: EmbedPage

[Sean Cribbs]

Colin,

You might be better off with an IFRAME or something similar, otherwise 
you will have to create a bunch of workarounds in your Rails application 
to deal with a different HTTP_REFERER.


The other option, of course, is to fuse Radiant with your application, 
i.e. making your application into an extension, but that may not be 
appropriate.


Sean

Colin Nederkoorn wrote:
Im building an extension to embed another RoR app in Radiant. I 
followed the instructions at - 
http://dev.radiantcms.org/radiant/wiki/HowToWriteAnExtension 
 to 
generate the skeleton called M7Embed


The main file is: embed_extension.rb
--
class M7embedExtension < Radiant::Extension
  version "1.0"
  description "Allows you to embed other sites in Radiant"
  url ""
 
  def activate

 EmbedPage
  end
 
  def deactivate

  end
   
end

--
and a model embed_page.rb:
---

class EmbedPage < Page
  tag 'embed_page' do |tag|
require 'open-uri'
  
open(tag.attr['url']).read

  end
end
---

The issue I am running into is that generally the application I am 
trying to load has relative references, and when it is embedded, it 
assumes everything is coming from the embedding page, and not the 
application... can anyone suggest how to remedy this?


As an example of this code embedding google - 
http://beta.method-seven.com/embed


Thanks in advance for your help,

Colin

P.s. - Credit to Joannou Ng for submitting a behavior to this list on 
Jan 18th that was used as the basis for this extension.



___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Help on Extension: EmbedPage

[Colin Nederkoorn]

Im building an extension to embed another RoR app in Radiant. I followed the
instructions at -
http://dev.radiantcms.org/radiant/wiki/HowToWriteAnExtension to generate the
skeleton called M7Embed

The main file is: embed_extension.rb
--
class M7embedExtension < Radiant::Extension
 version "1.0"
 description "Allows you to embed other sites in Radiant"
 url ""

 def activate
EmbedPage
 end

 def deactivate
 end

end
--
and a model embed_page.rb:
---

class EmbedPage < Page
 tag 'embed_page' do |tag|
   require 'open-uri'

   open(tag.attr['url']).read
 end
end
---

The issue I am running into is that generally the application I am trying to
load has relative references, and when it is embedded, it assumes everything
is coming from the embedding page, and not the application... can anyone
suggest how to remedy this?

As an example of this code embedding google -
http://beta.method-seven.com/embed

Thanks in advance for your help,

Colin

P.s. - Credit to Joannou Ng for submitting a behavior to this list on Jan
18th that was used as the basis for this extension.
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Radiant 0.6 RC2

[John W. Long]

Read all about it:

http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/

--
John Long
http://wisheartdesign.com
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Mislav Marohnić]

... or you could just use the regexp without the
first part: "/\d{4}/\d{2}/\d{2}/"

On 3/8/07, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> You could replace anything inside those parens with an appropriate
> character class... probably [\w-]+ would work.
>
> Sean
> > Thanks! I know how to write regular expressions. I was wondering if
> > there was a way to make this more automatic. The DRY-principles
> > should apply to layouts as well, no? Can anyone think of a way to
> > reduce the number of places I need to change when I add a new project
> > blog. Right now I do this:
> >
> > Create a new child of the root, say "food".
> > Copy the content from a previous blog, say "cars".
> > Change some stuff in the page content.
> > Create an RSS-feed.
> > Change the Normal layout.
> >
> > I'd like to find a smarter and less redundant way to do this.
> >
> > /Martin
> > http://smpl.se
> >
> >
> >
> >
> >
> > On 8 mar 2007, at 14.52, Sean Cribbs wrote:
> >
> >
> >> Change the first part of the if_url to look like so:
> >>
> >> Posted by on
> >>
> >> You can keep chaining on other "categories" with the | character.
> >>
> >> Sean
> >>
> >> Martin Olsson wrote:
> >>
> >>> So what do I do to make it work with a "multi-blog" site? I need
> >>> something that matches /blog//MM/DD, /blog//MM/DD, /car/
> >>> / MM/DD, and I don't really want to have to change it or add
> >>> to it every time I add a new "project blog". Regards, Martin
> >>> Olsson http://smpl.se On 8 mar 2007, at 11.07, Mislav Marohnić
> >>> wrote:
> >>>
>  On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote: There is one
>  piece of code in the "Normal" layout that I don't quite understand:
>  Posted by on
> 
>  It's simple really - you read it out like English :) If the
>  current URL starts with "/articles//MM/DD" (generic blog
>  format), print out "Posted by [author] on [date]" in a paragraph.
>  However, the URL must not end in "-archives/". This is because
>  archives are pages with that URL format, too, but you don't want
>  them to look like blog posts.
>  ___ Radiant mailing
>  list Post: Radiant@lists.radiantcms.org Search: http://
>  radiantcms.org/mailing-list/search/ Site: http://
>  lists.radiantcms.org/mailman/listinfo/radiant
> 
> >>> ___ Radiant mailing
> >>> list Post: Radiant@lists.radiantcms.org Search: http://
> >>> radiantcms.org/mailing-list/search/ Site: http://
> >>> lists.radiantcms.org/mailman/listinfo/radiant
> >>>
> >> ___
> >> Radiant mailing list
> >> Post:   Radiant@lists.radiantcms.org
> >> Search: http://radiantcms.org/mailing-list/search/
> >> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> >>
> >
> > ___
> > Radiant mailing list
> > Post:   Radiant@lists.radiantcms.org
> > Search: http://radiantcms.org/mailing-list/search/
> > Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
>
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] new user questions

[John W. Long]

Raphael Bauduin wrote:
> - an applicaiton created with the radiant command doesn't apparently
> contain the radiant code. Is there a way to freeze it to the gems used
> like for rails applications? (I saw in environment.rb that the gem
> used is referenced)  I didn't see it in the rake tasks available.

With 0.6rc1 the easiest way to do this is to extract the gem into the 
vendor/radiant directory, or to check radiant out using subversion into 
your vendor/radiant directory. (I like to use SVN externals to simplify 
this.)

There is now a series rake tasks in the repository to make this a little 
easier:

$ rake radiant:freeze:gems

~ or ~

$ rake radiant:freeze:edge BRANCH=mental


> - a related question: Will there be attention paid to upgrade
> procedures to future versions? I'd like to follow the latest release,
> but won't be able to afford long downtimes.

If you are using instance mode the upgrade procedure looks like this:

$ gem update radiant

Now edit config/environment.rb so that RADIANT_GEM_VERSION is set to the 
new version. Continue with:

$ cd /path/to/radiant/install
$ rake radiant:update

The radiant:update rake tasks are new in the repository as of last night.

> - Having all templates and layouts in the database is not the most
> user friendly to edit. Only for my tests I have lost time because the
> 'Save and continue editing' looses the position of my cursor when the
> page reload. Is there a way to store layouts in files? An "ajax" way
> of saving the changes when editing in the browser would be a
> workaround. I would still prefer templates in files (that way, if you
> want to change the design, you can do it in development on all layouts
> to be changed, and have it all transfered at once, to the production
> server. In this case I find it much easier to sync files and
> directories than DBs)

At the moment, templates must be stored in the DB. If you are looking 
for an easier way to edit layouts, I'd suggest the "Edit in Textmate" 
command (if you are a Textmate user or something similar if you use 
another editor).

I'd like to eventually add better export and import functionality to 
Radiant. This would certainly simplify what you are talking about.

> - If I want to let people register on the site, what's the best way to
> do it? Add a controller in the radiant installation? Run an additional
> rails app to just handle this?

Create an extension with a custom controller.

--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Sean Cribbs]

You could replace anything inside those parens with an appropriate 
character class... probably [\w-]+ would work.


Sean
Thanks! I know how to write regular expressions. I was wondering if  
there was a way to make this more automatic. The DRY-principles  
should apply to layouts as well, no? Can anyone think of a way to  
reduce the number of places I need to change when I add a new project  
blog. Right now I do this:


Create a new child of the root, say "food".
Copy the content from a previous blog, say "cars".
Change some stuff in the page content.
Create an RSS-feed.
Change the Normal layout.

I'd like to find a smarter and less redundant way to do this.

/Martin
http://smpl.se





On 8 mar 2007, at 14.52, Sean Cribbs wrote:

  

Change the first part of the if_url to look like so:

Posted by on

You can keep chaining on other "categories" with the | character.

Sean

Martin Olsson wrote:

So what do I do to make it work with a "multi-blog" site? I need  
something that matches /blog//MM/DD, /blog//MM/DD, /car/ 
/ MM/DD, and I don't really want to have to change it or add  
to it every time I add a new "project blog". Regards, Martin  
Olsson http://smpl.se On 8 mar 2007, at 11.07, Mislav Marohnić  
wrote:
  
On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote: There is one  
piece of code in the "Normal" layout that I don't quite understand:

Posted by on

It's simple really - you read it out like English :) If the  
current URL starts with "/articles//MM/DD" (generic blog  
format), print out "Posted by [author] on [date]" in a paragraph.  
However, the URL must not end in "-archives/". This is because  
archives are pages with that URL format, too, but you don't want  
them to look like blog posts.  
___ Radiant mailing  
list Post: Radiant@lists.radiantcms.org Search: http:// 
radiantcms.org/mailing-list/search/ Site: http:// 
lists.radiantcms.org/mailman/listinfo/radiant

___ Radiant mailing  
list Post: Radiant@lists.radiantcms.org Search: http:// 
radiantcms.org/mailing-list/search/ Site: http:// 
lists.radiantcms.org/mailman/listinfo/radiant
  

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Martin Olsson]

Thanks! I know how to write regular expressions. I was wondering if  
there was a way to make this more automatic. The DRY-principles  
should apply to layouts as well, no? Can anyone think of a way to  
reduce the number of places I need to change when I add a new project  
blog. Right now I do this:

Create a new child of the root, say "food".
Copy the content from a previous blog, say "cars".
Change some stuff in the page content.
Create an RSS-feed.
Change the Normal layout.

I'd like to find a smarter and less redundant way to do this.

/Martin
http://smpl.se





On 8 mar 2007, at 14.52, Sean Cribbs wrote:

> Change the first part of the if_url to look like so:
>
> Posted by on
>
> You can keep chaining on other "categories" with the | character.
>
> Sean
>
> Martin Olsson wrote:
>> So what do I do to make it work with a "multi-blog" site? I need  
>> something that matches /blog//MM/DD, /blog//MM/DD, /car/ 
>> / MM/DD, and I don't really want to have to change it or add  
>> to it every time I add a new "project blog". Regards, Martin  
>> Olsson http://smpl.se On 8 mar 2007, at 11.07, Mislav Marohnić  
>> wrote:
>>> On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote: There is one  
>>> piece of code in the "Normal" layout that I don't quite understand:
>>> Posted by on
>>>
>>> It's simple really - you read it out like English :) If the  
>>> current URL starts with "/articles//MM/DD" (generic blog  
>>> format), print out "Posted by [author] on [date]" in a paragraph.  
>>> However, the URL must not end in "-archives/". This is because  
>>> archives are pages with that URL format, too, but you don't want  
>>> them to look like blog posts.  
>>> ___ Radiant mailing  
>>> list Post: Radiant@lists.radiantcms.org Search: http:// 
>>> radiantcms.org/mailing-list/search/ Site: http:// 
>>> lists.radiantcms.org/mailman/listinfo/radiant
>> ___ Radiant mailing  
>> list Post: Radiant@lists.radiantcms.org Search: http:// 
>> radiantcms.org/mailing-list/search/ Site: http:// 
>> lists.radiantcms.org/mailman/listinfo/radiant
>
> ___
> Radiant mailing list
> Post:   Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Sean Cribbs]

Change the first part of the if_url to look like so:

Posted by  on


You can keep chaining on other "categories" with the | character.

Sean

Martin Olsson wrote:
So what do I do to make it work with a "multi-blog" site? I need  
something that matches /blog//MM/DD, /blog//MM/DD, /car// 
MM/DD, and I don't really want to have to change it or add to it  
every time I add a new "project blog".


Regards,
Martin Olsson
http://smpl.se




On 8 mar 2007, at 11.07, Mislav Marohnić wrote:

  

On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote:
There is one piece of code in the "Normal" layout that I
don't quite understand:

Posted by  on


It's simple really - you read it out like English :)

If the current URL starts with "/articles//MM/DD" (generic blog  
format), print out "Posted by [author] on [date]" in a paragraph.  
However, the URL must not end in "-archives/". This is because  
archives are pages with that URL format, too, but you don't want  
them to look like blog posts.

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Martin Olsson]

So what do I do to make it work with a "multi-blog" site? I need  
something that matches /blog//MM/DD, /blog//MM/DD, /car// 
MM/DD, and I don't really want to have to change it or add to it  
every time I add a new "project blog".

Regards,
Martin Olsson
http://smpl.se




On 8 mar 2007, at 11.07, Mislav Marohnić wrote:

> On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote:
> There is one piece of code in the "Normal" layout that I
> don't quite understand:
>
>  matches="-archives/$">Posted by  on
> 
>
> It's simple really - you read it out like English :)
>
> If the current URL starts with "/articles//MM/DD" (generic blog  
> format), print out "Posted by [author] on [date]" in a paragraph.  
> However, the URL must not end in "-archives/". This is because  
> archives are pages with that URL format, too, but you don't want  
> them to look like blog posts.
> ___
> Radiant mailing list
> Post:   Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] new user questions

[Mislav Marohnić]

On 3/8/07, Raphael Bauduin <[EMAIL PROTECTED]> wrote:



- an applicaiton created with the radiant command doesn't apparently
contain the radiant code. Is there a way to freeze it to the gems used
like for rails applications?



I'm using the SVN checkout. It is self-contained.

- a related question: Will there be attention paid to upgrade

procedures to future versions? I'd like to follow the latest release,
but won't be able to afford long downtimes.



Upgrade procedures should be painless thanks to Rails migrations.

Is there a way to store layouts in files?


No. It would pretty complicated I guess

An "ajax" way

of saving the changes when editing in the browser would be a
workaround.



Yeah, much better solution.

- If I want to let people register on the site, what's the best way to

do it? Add a controller in the radiant installation?



You should go with Radiant extensions

Run an additional rails app to just handle this?


Ugh - no :)
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] new user questions

[Raphael Bauduin]

Hi,

I'm planning to use radiant to power a website, but before taking the
plunge I have some questions. I installed the 0.6 release candidate.
Here are questions I couldn't answer by looking at the docs or the
mailing list archive:

- an applicaiton created with the radiant command doesn't apparently
contain the radiant code. Is there a way to freeze it to the gems used
like for rails applications? (I saw in environment.rb that the gem
used is referenced)  I didn't see it in the rake tasks available.

- a related question: Will there be attention paid to upgrade
procedures to future versions? I'd like to follow the latest release,
but won't be able to afford long downtimes.

- Having all templates and layouts in the database is not the most
user friendly to edit. Only for my tests I have lost time because the
'Save and continue editing' looses the position of my cursor when the
page reload. Is there a way to store layouts in files? An "ajax" way
of saving the changes when editing in the browser would be a
workaround. I would still prefer templates in files (that way, if you
want to change the design, you can do it in development on all layouts
to be changed, and have it all transfered at once, to the production
server. In this case I find it much easier to sync files and
directories than DBs)

- If I want to let people register on the site, what's the best way to
do it? Add a controller in the radiant installation? Run an additional
rails app to just handle this?

Thanks in advance for your help.

Raph

-- 
Web database: http://www.myowndb.com
Free Software Developers Meeting: http://www.fosdem.org
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Simple blog too complex: what does this code do?

[Mislav Marohnić]

On 3/8/07, Martin Olsson <[EMAIL PROTECTED]> wrote:


There is one piece of code in the "Normal" layout that I
don't quite understand:

Posted by  on




It's simple really - you read it out like English :)

If the current URL starts with "/articles//MM/DD" (generic blog format),
print out "Posted by [author] on [date]" in a paragraph. However, the URL
must not end in "-archives/". This is because archives are pages with that
URL format, too, but you don't want them to look like blog posts.
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Installing 0.6.0rc1

[Sharon Clift]

I have tried using Gem install radiant-0.6.0rc1 and Gem install
radiant-0.6.0rc1.gem, but get the same error with both.  I have had a
look at the weblog, which is where I downloaded the gem from, but just
can't persuade it to install, I just get the (Gem::GemNotFoundException)


I have also tried to install it strait from the web by using gem install
--source http://johnwlong.com/downloads radiant-0.6.0rc1.gem  (with and
without the .gem at the end) but get a HTTP 404 and gem remote source
exception

Thanks

Sharon 

--

Message: 1
Date: Wed, 7 Mar 2007 12:52:48 -
From: "Sharon Clift" <[EMAIL PROTECTED]>
Subject: [Radiant] Installing 0.6.0rc1
To: 
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain;   charset="us-ascii"

I am new to Ruby/Rails & RubyGem and  am trying to install a copy of
radiant 0.6.0rc1 for testing.   

I have downloaded the gem from
http://johnwlong.com/downloads/radiant-0.6.0rc1.gem to
c:/ruby/lib/ruby/gems/ however when I use the command

Gem install radiant-0.6.0rc1 

I get the error 

ERROR:  While executing gem ... (Gem::GemNotFoundException) Could not
find radiant-0.6.0rc1 (> 0) in any repository

I also tried downloading to a local directory (C:\Radiant6) and using
the command 

gem install radiant-0.6.0rc1 --install-dir C:\Radiant6 

However I received the same error.  

I know I must be missing something obvious, but can't figure out what.
Can someone please point me in the right direction?  I've tried looking
in the radiant handbook but that part of the site has been down for a
few days.

Many thanks

Sharon 

This e-mail has been scanned for all viruses by MessageLabs.
___
Radiant mailing list
Post:   Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant