[Radiant] basic newbie questions: Updating radiant and installing
behaviors
Michael Moscow
mike at mikemoscow.com
Fri Oct 20 11:09:13 CDT 2006
Hi Everyone, I'm a designer (not developer/programmer) trying to wrap
my head around radiant because I'm going to use it with 2 different
clients this month. I currently have an account at textdrive and I
used jake's tutorial to get it up and running: http://
www.fourhats.com/blog/archive/2006/08/27/radiant-on-textdrive/
here are where my questions finally begin, I ran the following code
using shell access:
<code> svn co http://dev.radiantcms.org/svn/radiant/tags/rel_0-5-2/ ~/
radiant
~/radiant/radiant/bin/radiant ~/web/ <code />
Now I understand the first part of this... I took release 0.5.2 from
the subversion archive and copied it to a folder named radiant on my
TD account. The second line in the command I'm not really sure...
did It save the actual radiant app in the radiant folder ( ~/radiant/
radiant/bin/radiant ) and then create an instance in the web
directory? ( ~/web/ ) so that my website is running in instance
mode? Or did I just download the full source of radiant and then made
another copy for the web directory?
I'm going to have to install oliver's gallery and search behaviors
and I'm confused as to where I have to do this or if its even
possible on Textdrive. Do I install the plugin into my ( ~/web/ )
directory or the ( ~/radiant/radiant/bin/radiant ) directory?
In the future when I want to upgrade radiant to 1.0, etc. Do I svn
another copy to my ( ~/radiant/radiant/bin/radiant ) directory and
then do an --upgrade from my ( ~/web/ ) directory? Or will have i
have to copy all the files over to ( ~/web/ ) again and import the
DB?
Thanks,
A.Calzadilla
On Oct 20, 2006, at 8:00 AM, radiant-request at lists.radiantcms.org wrote:
> Send Radiant mailing list submissions to
> radiant at lists.radiantcms.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.radiantcms.org/mailman/listinfo/radiant
> or, via email, send a message with subject or body 'help' to
> radiant-request at lists.radiantcms.org
>
> You can reach the person managing the list at
> radiant-owner at lists.radiantcms.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Radiant digest..."
>
>
> Today's Topics:
>
> 1. Where to contribute my ambitious change. (Jacob Burkhart)
> 2. What I actually meant to say was... (Jacob Burkhart)
> 3. Re: What I actually meant to say was... (Alexander Horn)
> 4. Re: What I actually meant to say was... (John W. Long)
> 5. WYSIWIG Plugin (Todd Baur)
> 6. Re: WYSIWIG Plugin (Alexander Horn)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Oct 2006 23:39:33 +0200
> From: Jacob Burkhart <igotimac at gmail.com>
> Subject: [Radiant] Where to contribute my ambitious change.
> To: radiant at lists.radiantcms.org
> Message-ID: <6e91a0f11299849d83529849e6619ede at ruby-forum.com>
> Content-Type: text/plain; charset=utf-8
>
> Hey Everybody,
>
> I have a
>
> --
> Posted via http://www.ruby-forum.com/.
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 20 Oct 2006 00:23:33 +0200
> From: Jacob Burkhart <igotimac at gmail.com>
> Subject: [Radiant] What I actually meant to say was...
> To: radiant at lists.radiantcms.org
> Message-ID: <f7e1da4a8651cbe043d4b26e90f555a3 at ruby-forum.com>
> Content-Type: text/plain; charset=utf-8
>
> Oops, I accidentally hit return while editing the subject.
>
> Anyway this post has 2 purposes:
>
> 1. To explain what I want to do with Radiant, and to see if anybody
> else
> has ever tried. And to validate that my approach is correct.
>
> 2. To ask where/how it might most be useful to contribute what I
> plan on
> doing back into the core
>
>
> The details:
>
> I want to implement Page types. From an interface perspective, I'm
> imagining you'll see a little pop-up when you click "add child" in the
> pages admin asking you what type of page you want to make.
>
> I propose to implement each page type as a database table with a
> one to
> one relationship back to the pages table. We will assume that somehow
> we know about all tables that have this property and thus know that
> they
> are page types. I want to implement it so that anybody can create any
> arbitrary page type with very little work. (basically just create the
> database table) In my examples I will use the following example type:
>
> students
> name - short string
> grade - number
> birthday - date
> description - text
> page_id - (one to one relation back to pages)
>
> So for the purposes of this example you click "add child" in the pages
> admin you would be prompted to chose "standard page" or "student"
>
> Next, what do you see:
>
> If you chose "student" you would see an addional tab after your page
> parts called "Attributes" If you clicked this tab you would see a
> scaffolding-esque form for filling out all of the columns in the
> students table (you would then proceed to fill these out). In the body
> of your page (or in my case in the layout I select for my page) there
> will be additional r:tags for displaying the content-type specific
> attributes. <r:content attribute="birthday" /> for example.
>
> Once I have this working, I'd like "text" attributes to appear in
> seperate tabs with a WYSIWYG (remember they will not actually be page
> parts, they are still stored as attributes of the content type) I am
> also thinking about supporting file uploads in a similar manner.
>
> Once I have that working, I'd like to add a new user type (called
> content admin) who can only create and edit pages that are of a
> non-standard type. (all other actions in the admin would be greyed
> out)
>
> Finally, I'd like to support linking to other special page types via
> content types. So for instance:
>
> students
> name - short string
> grade - number
> birthday - date
> description - text
> page_id - (one to one relation back to pages)
> school_id - (foreign key to schools table)
>
> schools
> page_id - (one to one relation back to pages)
> etc...
>
> This way, when you create a student you can select which school
> they are
> in from a drop down showing all other school-typed pages.
>
>
> Remember, the idea here is not to add students and schools, but the
> ability for me to simply create those tables (and maybe their
> models) in
> a particular instance of radiant and have the core of the application
> recognize them as page types and allow me to manipulate then in the
> admin
>
> I want to be able to customize radiant with content types for a
> particular purpose and then hand it off to a more non-technical users.
> I eliminate the need for that user to know any radiant tags by
> creating
> a layout for each content item type (which would pull all of the
> relevant stuff from the attributes they populate)
>
> Any comments?
>
> Should I work from corex or mental? Does it sound like what I am
> trying
> to do might be broken by the currently planned roadmap for the next
> release of radiant?
>
> Can you explain to me how (If possible) I might develop the
> entirety of
> the functionality I just described as a "plug-in"?
>
> thanks,
> Jacob
>
> --
> Posted via http://www.ruby-forum.com/.
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 19 Oct 2006 17:34:21 -0500
> From: "Alexander Horn" <alex.horn at gmail.com>
> Subject: Re: [Radiant] What I actually meant to say was...
> To: radiant at lists.radiantcms.org, radiant-core at lists.radiantcms.org
> Message-ID:
> <dd6cf9840610191534x624250b3y5cb7142d6d7b36cf at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> You should check out Hieraki. It does exactly what your describing.
> Unfortunately Tobias and I can no longer support the project but it is
> in a very usable state.
>
> On 10/19/06, Jacob Burkhart <igotimac at gmail.com> wrote:
>> Oops, I accidentally hit return while editing the subject.
>>
>> Anyway this post has 2 purposes:
>>
>> 1. To explain what I want to do with Radiant, and to see if
>> anybody else
>> has ever tried. And to validate that my approach is correct.
>>
>> 2. To ask where/how it might most be useful to contribute what I
>> plan on
>> doing back into the core
>>
>>
>> The details:
>>
>> I want to implement Page types. From an interface perspective, I'm
>> imagining you'll see a little pop-up when you click "add child" in
>> the
>> pages admin asking you what type of page you want to make.
>>
>> I propose to implement each page type as a database table with a
>> one to
>> one relationship back to the pages table. We will assume that
>> somehow
>> we know about all tables that have this property and thus know
>> that they
>> are page types. I want to implement it so that anybody can create
>> any
>> arbitrary page type with very little work. (basically just create the
>> database table) In my examples I will use the following example type:
>>
>> students
>> name - short string
>> grade - number
>> birthday - date
>> description - text
>> page_id - (one to one relation back to pages)
>>
>> So for the purposes of this example you click "add child" in the
>> pages
>> admin you would be prompted to chose "standard page" or "student"
>>
>> Next, what do you see:
>>
>> If you chose "student" you would see an addional tab after your page
>> parts called "Attributes" If you clicked this tab you would see a
>> scaffolding-esque form for filling out all of the columns in the
>> students table (you would then proceed to fill these out). In the
>> body
>> of your page (or in my case in the layout I select for my page) there
>> will be additional r:tags for displaying the content-type specific
>> attributes. <r:content attribute="birthday" /> for example.
>>
>> Once I have this working, I'd like "text" attributes to appear in
>> seperate tabs with a WYSIWYG (remember they will not actually be page
>> parts, they are still stored as attributes of the content type) I am
>> also thinking about supporting file uploads in a similar manner.
>>
>> Once I have that working, I'd like to add a new user type (called
>> content admin) who can only create and edit pages that are of a
>> non-standard type. (all other actions in the admin would be
>> greyed out)
>>
>> Finally, I'd like to support linking to other special page types via
>> content types. So for instance:
>>
>> students
>> name - short string
>> grade - number
>> birthday - date
>> description - text
>> page_id - (one to one relation back to pages)
>> school_id - (foreign key to schools table)
>>
>> schools
>> page_id - (one to one relation back to pages)
>> etc...
>>
>> This way, when you create a student you can select which school
>> they are
>> in from a drop down showing all other school-typed pages.
>>
>>
>> Remember, the idea here is not to add students and schools, but the
>> ability for me to simply create those tables (and maybe their
>> models) in
>> a particular instance of radiant and have the core of the application
>> recognize them as page types and allow me to manipulate then in the
>> admin
>>
>> I want to be able to customize radiant with content types for a
>> particular purpose and then hand it off to a more non-technical
>> users.
>> I eliminate the need for that user to know any radiant tags by
>> creating
>> a layout for each content item type (which would pull all of the
>> relevant stuff from the attributes they populate)
>>
>> Any comments?
>>
>> Should I work from corex or mental? Does it sound like what I am
>> trying
>> to do might be broken by the currently planned roadmap for the next
>> release of radiant?
>>
>> Can you explain to me how (If possible) I might develop the
>> entirety of
>> the functionality I just described as a "plug-in"?
>>
>> thanks,
>> Jacob
>>
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> Radiant mailing list
>> Post: Radiant at lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>
>
> --
> Alexander Horn
> http://www2.truman.edu/~ah428
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 19 Oct 2006 17:23:08 -0600
> From: "John W. Long" <ng at johnwlong.com>
> Subject: Re: [Radiant] What I actually meant to say was...
> To: radiant at lists.radiantcms.org
> Message-ID: <453808DC.6000409 at johnwlong.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jacob Burkhart wrote:
>> I propose to implement each page type as a database table with a
>> one to
>> one relationship back to the pages table. We will assume that
>> somehow
>> we know about all tables that have this property and thus know
>> that they
>> are page types. I want to implement it so that anybody can create
>> any
>> arbitrary page type with very little work. (basically just create the
>> database table) In my examples I will use the following example type:
>
> This is probably outside the scope of what I have planned for 1.0. You
> are welcome to fork. :-)
>
> --
> John
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 19 Oct 2006 20:48:02 -0700
> From: Todd Baur <todd at tackletechnology.org>
> Subject: [Radiant] WYSIWIG Plugin
> To: radiant at lists.radiantcms.org
> Message-ID:
> <3826B97F-B824-468E-BA1F-10F4FCDA972C at tackletechnology.org>
> Content-Type: text/plain; charset="us-ascii"
>
> We've got Dojo working with it
>
> http://dojotoolkit.org/docs/rich_text.html
>
>
> ~*~*~~*~*~*~*~*~*~*~*~*~
> Todd Baur
> todd at tackletechnology.org
> 858-752-1459
> 11814 Westview Parkway
> Unit #176
> San Diego, CA 92126
>
>
>
> On Oct 19, 2006, at 5:00 AM, radiant-request at lists.radiantcms.org
> wrote:
>
>> On a side note, I wonder if a simplistic WYSIWYG editor could be
>> made as
>> an interface to Textile or Markdown?
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.radiantcms.org/pipermail/radiant/attachments/
> 20061020/dd895cd4/attachment-0001.htm
>
> ------------------------------
>
> Message: 6
> Date: Thu, 19 Oct 2006 22:53:23 -0500
> From: "Alexander Horn" <alex.horn at gmail.com>
> Subject: Re: [Radiant] WYSIWIG Plugin
> To: radiant at lists.radiantcms.org
> Message-ID:
> <dd6cf9840610192053u12e2d7f1qdfca01d868d2e0da at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>> We've got Dojo working with it
>
> Very nice.
>
> On 10/19/06, Todd Baur <todd at tackletechnology.org> wrote:
>> We've got Dojo working with it
>>
>> http://dojotoolkit.org/docs/rich_text.html
>>
>>
>>
>> ~*~*~~*~*~*~*~*~*~*~*~*~
>> Todd Baur
>> todd at tackletechnology.org
>> 858-752-1459
>> 11814 Westview Parkway
>> Unit #176
>> San Diego, CA 92126
>>
>>
>>
>>
>> On Oct 19, 2006, at 5:00 AM,
>> radiant-request at lists.radiantcms.org wrote:
>>
>>
>> On a side note, I wonder if a simplistic WYSIWYG editor could be
>> made as
>>
>> an interface to Textile or Markdown?
>>
>> _______________________________________________
>> Radiant mailing list
>> Post: Radiant at lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:
>> http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>
>
>
> --
> Alexander Horn
> http://www2.truman.edu/~ah428
>
>
> ------------------------------
>
> _______________________________________________
> Radiant mailing list
> Post: Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
> End of Radiant Digest, Vol 7, Issue 34
> **************************************
>
More information about the Radiant
mailing list