Re: [Radiant] Re: [Radiant-Dev] Re: Radiant 0.7.0 release candidate 1 available
There's already a VIM plugin, but with the ARes API it should be easier to build stuff into local text editors. I could even envision including this in the Radius TextMate bundle. Sean Anton J Aylward wrote: Sean Cribbs said the following on 12/10/2008 01:22 PM: Anton, Radiant 0.7.x will be ActiveResource compatible, i.e. having a simple XML/JSON REST API. Any other APIs will need to be supported by extensions. While the roadmap says 0.7 is the blogging release, we are incrementing the version number without necessarily moving forward the feature set toward those goals. We feel the internal refactoring represents enough of a significant departure from previous versions to warrant the new number. This is what I mean when I say we've been slavish to the roadmap in the past - that we need the version numbers to more adequately reflect the amount of progress, not some externally-determined feature set. That's OK, just asking. I'm glad that the internals are getting a work-over. Things can only grow so much on a certain size of 'skeleton'. In many ways software is more like a crustacean than a mammal in having an exoskeleton that can limit its growth. The reason I asked was some users are unhappy with the idea of logging in and editing. I can't imagine what they expect - telepathy? ___ 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: [Radiant-Dev] Re: Radiant 0.7.0 release candidate 1 available
Sean Cribbs said the following on 12/10/2008 01:22 PM: > Anton, > > Radiant 0.7.x will be ActiveResource compatible, i.e. having a simple > XML/JSON REST API. Any other APIs will need to be supported by > extensions. While the roadmap says 0.7 is the blogging release, we are > incrementing the version number without necessarily moving forward the > feature set toward those goals. We feel the internal refactoring > represents enough of a significant departure from previous versions to > warrant the new number. This is what I mean when I say we've been > slavish to the roadmap in the past - that we need the version numbers to > more adequately reflect the amount of progress, not some > externally-determined feature set. That's OK, just asking. I'm glad that the internals are getting a work-over. Things can only grow so much on a certain size of 'skeleton'. In many ways software is more like a crustacean than a mammal in having an exoskeleton that can limit its growth. The reason I asked was some users are unhappy with the idea of logging in and editing. I can't imagine what they expect - telepathy? -- He who stops being better stops being good. - Oliver Cromwell ___ 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: [Radiant-Dev] Re: Radiant 0.7.0 release candidate 1 available
Anton, Radiant 0.7.x will be ActiveResource compatible, i.e. having a simple XML/JSON REST API. Any other APIs will need to be supported by extensions. While the roadmap says 0.7 is the blogging release, we are incrementing the version number without necessarily moving forward the feature set toward those goals. We feel the internal refactoring represents enough of a significant departure from previous versions to warrant the new number. This is what I mean when I say we've been slavish to the roadmap in the past - that we need the version numbers to more adequately reflect the amount of progress, not some externally-determined feature set. Sean Anton J Aylward wrote: There was discussion of Radiant 7 having APIs for suff like WebDav. Did that happen? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
