If you've been watching the change logs lately, you might have noticed a
new branch in the repository--the "mental" branch:
http://dev.radiantcms.org/radiant/browser/branches/mental/radiant
It's basically a place for the core team to play around with a few
architectural changes. The most signif
> If you've been watching the change logs lately, you might
> have noticed a
> new branch in the repository--the "mental" branch:
>
> http://dev.radiantcms.org/radiant/browser/branches/mental/radiant
>
> It's basically a place for the core team to play around with a few
> architectural changes
Daniel Sheppard wrote:
> The big reason that I was trying to push for this change was to be able
> to introduce activerecord associations to the subclassed behaviors and
> then modify the admin display for those behaviors.
Yup, this is a huge benefit the new model.
> To do this you'd need the fol
On 9/28/06, John W. Long <[EMAIL PROTECTED]> wrote:
> Yup, this is a huge benefit the new model.
So, is this going to become the new trunk at some point? I've been
tracking it through svn/hg and it works fine... I've not modified any
behaviour^Wpage types so for me there is no difference yet.
[
Ollivier,I intend to make Commentable into a page type with model(s) soon, but I'm kinda bogged down right now with other projects.Sean Cribbsseancribbs.com
On 10/10/06, Ollivier Robert <[EMAIL PROTECTED]> wrote:
On 9/28/06, John W. Long <[EMAIL PROTECTED]> wrote:> Yup, this is a huge benefit the n
> > [to all]
> > Are there any plan to update/rewrite the current Third Parties
> > behaviours into page types?
I would think that is the responsibility of the maintainers of Third
Party page extensions.
> > So, is this going to become the new trunk at some point? I've been
> > tracking it throu
On 10/10/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
> I would think that is the responsibility of the maintainers of Third
> Party page extensions.
Agreed and that's why it was addressed to all :-)
Now, for people to do that, the branch must gain some kind of status
like "this is where we want
> Now, for people to do that, the branch must gain some kind of status
> like "this is where we want to go in the future" even though it is
> still experimental.
Point granted. As soon as John has come back and has settled in again
we should see what our roadmap should look like to incorporate som
On 10/10/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
> I am happy to answer any questions you guys might have regarding the
> "corex" branch. Please feel free to comment on any issues or quirks
> you encounter. An overall list of changes in the "corex" branch can be
> found here: http://alxh.blog
On 10/12/06, Ollivier Robert <[EMAIL PROTECTED]> wrote:
> On 10/10/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
> > I am happy to answer any questions you guys might have regarding the
> > "corex" branch. Please feel free to comment on any issues or quirks
> > you encounter. An overall list of cha
On Oct 12, 2006, at 10:40 AM, Ollivier Robert wrote:
> On 10/10/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
>> I am happy to answer any questions you guys might have regarding the
>> "corex" branch. Please feel free to comment on any issues or quirks
>> you encounter. An overall list of changes
On 10/10/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
> Have you had time to track the Corex branch? It has some improvements
> to page extensions.
Any migration path from the "normal" radiant? I've tried to import my
postgresql
data and corex fails with several errors like "content" tag unknown
> Any migration path from the "normal" radiant? I've tried to import my
> postgresql
> data and corex fails with several errors like "content" tag unknown and
> others.
With the creation of the branch I removed the old migration scripts
because I could not get Postgresql to work with these legac
On 10/12/06, Alexander Horn <[EMAIL PROTECTED]> wrote:
> migrations. This change is only temporary but it means that you
> currently cannot migrate your 0.5x data to the "corex" branch. Most
OK.
> likely though, you current pages probably rely on Archive and other
> behaviors anyway. Since those
> Except for Archive which I just started using, I don't rely on any
> behaviour and no third-party one anyway so I expected to be easy. But
> the first error I got is "content: tag unknown"... The real home page
> of the site has several parts and I use this code:
>
> -
>
>
>
>
>
Hi Guys,
I'm going to be starting a new site in Radiant (have two others on
0.5.2 already) and wanted to work with mental. Should I just take the
current revision or is there a specific one I should target? Also,
does mental require 1.2/edge?
Cheers,
Marty
__
I've been playing with the Mental branch this weekend to test-out the
work being done on the new Radiant Extensions concept. I thought I
just put down a quick narrative of my experience with it to give
those who've not had a chance to check it out recently a preview of
what's to come. Ther
The commits tend to be well tested if they affect normal operations, so it's
pretty safe to use the current revision. Mental automatically uses Edge
Rails as an svn:external when you checkout.
Sean
p.s. www.kckcc.edu is running the latest revision of mental
On 1/17/07, Marty Haught <[EMAIL PROT
Sean Cribbs wrote:
> The commits tend to be well tested if they affect normal operations, so
> it's
> pretty safe to use the current revision. Mental automatically uses Edge
> Rails as an svn:external when you checkout.
Well not quite. It's using the 1.2 prerelease branch:
http://dev.rubyonrail
Great, so just to confirm before I attempt this. The steps for
upgrading from a 0.5.2 radiant site (installed via gems, no unpack) to
mental is this:
1) do an svn:co into my site directory (which will put all the
radiant/rails 1.2 pre release over the old generated radiant rails
app).
cd my_sit
0) backup the entire site dir + database incase it breaks anything
> 1) do an svn:co into my site directory (which will put all the
> radiant/rails 1.2 pre release over the old generated radiant rails
> app).
...
> Right?
___
Radiant mailing list
Post:
Daniel,
Could not agree the more. It's a step many people either skip or give
for granted. Before you do any kind of migration you MUST back up all
the DB, and all the radiant 0.5.x files your site is currently using.
In fact, unless you are tinkering with a testing/dev intall, you need
to make ba
I just want to second this, the extensions are very well thought out and pretty easy to use even in their very raw state. I have a very simple assets management system (based on acts_as_attachment) that took maybe a few hours to set up. Most of that was making sure that the views integrated nicely
Loren Johnson wrote:
> I know I for one see the maturation of these extensions as an
> important turning-point for Radiant as a project.
>
> IMHO this robust and Rails friendly way of extending Radiant is key
> to allowing it to remain spartan. Though I might still prefer the CMS
> to be the
Keith Bingman wrote:
> I just want to second this, the extensions are very well thought out and
> pretty easy to use even in their very raw state. I have a very simple
> assets management system (based on acts_as_attachment) that took maybe a
> few hours to set up. Most of that was making sure t
Keith,I just want to second this, the extensions are very well thought out and pretty easy to use even in their very raw state. I have a very simple assets management system (based on acts_as_attachment) that took maybe a few hours to set up. Most of that was making sure that the views integrated n
No, not yet. I hope to use it for something soon. I got the database moved over today from 0.5.2, without too many problems (that I have found). I haven't gotten my custom tags going yet, but as soon as those get going I am going to deploy it to a test server. Should it survive that, then I will u
> Keith Bingman wrote:
>> I just want to second this, the extensions are very well thought
>> out and
>> pretty easy to use even in their very raw state. I have a very simple
>> assets management system (based on acts_as_attachment) that took
>> maybe a
>> few hours to set up. Most of that was
I just installed the mental branch on textdrive. It seems to run pretty well. The Assets Manager I wrote has a few problems, because it is based on acts_as_attachment, which uses RMagick. I had to shut that off, as it would kill Radiant due to memory usage. There are a few fixes for that, I have to
Hey Loren-
Thanks for this info, I was wondering if you could give more
blow-by-blow on how you did it? Or even put up a wiki page?
This is all I found:
http://dev.radiantcms.org/radiant/wiki/RPS2
and would love to have more to go on.
Thanks-
Michael
On 11/13/06, Loren Johnson <[EMAIL PROTEC
> Also, the more people that can jump on board and start using the code in
> the mental branch the better. This is a major upgrade and your comments
> and feedback are vital.
I want to jump on this but I'm unable to get my extensions to work.
I'm a radiant noob but have been doing rails for a whil
We are using Radiant for our January 1 website launch and I intend to
write a "How To" very soon for the weblog that will demonstrate
converting a behavior over to the extensions system.
Sean Cribbs
seancribbs.com
Michael Jones wrote:
Also, the more people that can jump on board and start us
Michael Jones wrote:
> 7. See the Album tab, when I click it I get: uninitialized constant
Is your controller called AssetController?
--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://ra
> Is your controller called AssetController?
No that was just the default route that was generated:
map.connect 'admin/album/:action', :controller => 'admin/asset'
Sorry, I was assuming it generated that route for a reason.
I changed it to:
map.connect 'admin/album/:action', :controller => 'albu
> And I get a page rendered however no content is showing on it.
Sweet, I have content. Oh man this new extension stuff is going to ROCK!
Thanks-
Michael
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing
Hi,
I'm just starting out with Radiant and plan to launch a Radiant based site in
January. I'm starting to gather that I should be using extensions and the
mental branch rather than writing behaviors for functionality the site will
need. Any thoughts?
Todd
Quoting Sean Cribbs <[EMAIL PROTECT
Todd,
Tentatively, yes. The extensions API is in great flux right now, as John
and the core team hammer it out. However, it is mostly functional and you
can start using it today. However, I don't see that it will be too much
trouble if you create your behaviors now, and then migrate them over
37 matches
Mail list logo
