Agreed, except for the asset manager, sort of.
I can think that an asset manager is going to be something that will
be ideosyncratic for many people. I would REALLY like to see not only
a standard asset manager but also an architecture that allows me to
write my own asset manager without loosing the existing hooks into the
UI. This way if I make an extension that needs access to the asset
manager, I don't have to know what all the existing asset managers
are. I just have to use the "AssetManagerBucketHelper" or something.
On 27-Jan-09, at 1:21 PM, Joe Van Dyk wrote:
On Tue, Jan 27, 2009 at 10:56 AM, Mohit Sindhwani <[email protected]>
wrote:
Adam van den Hoven wrote:
I think this highlights why some sort of versioning really
shouldn't be an
optional part of radiant. Distribute it as an extension, but make
it one of
those extensions that comes by default. This way everyone has some
protection but I can substitute my own advanced version control or
remove it
if I like.
+1
+2 over here.
Other things that we think most people would want by default:
- some sort of rich text editor
- asset manager better integrated
It would be great to have these as extensions, but installed by
default. Having an officially "blessed" extension is important for
quality, in our opinion.
Joe
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
