I was a little late to the game when it came to checking out the Mental
branch, but *wow* I really like what I see. The extensions are very slick,
and I can already see myself spending long hours making new ones.
In fact, I've got a few to offer right now.
The first is a simple text filter ba
Sounds good. I'm looking forward to playing with this. I can see it
being very useful (though I share John's distaste for using WYSIWYG
editors) for my customers.
Are you willing to provide any details on the asset management piece you
are working on? I've read about what the others are doin
On Fri, 23 Feb 2007 19:55:04 -0700, Chris Parrish
<[EMAIL PROTECTED]> wrote:
> Sounds good. I'm looking forward to playing with this. I can see it
> being very useful (though I share John's distaste for using WYSIWYG
> editors) for my customers.
Ditto. How have you persuaded them to use somet
I wrote one of the first extensions for this, but kind of dropped it
as I was in Central America for a month and have yet to pick it up
again.
For me at least, centralized assets are much better. I don't want to
have to hunt through each page to find a photo. The bucket idea seems
like the
Nathan Wright wrote:
> I think that John believes that assets should belong to a page rather
> than
> being more universal in nature, but I honestly think that this may
> complicate things too much for the average user.
>
> In my system all assets are available to all pages. You add those assets
On Feb 24, 2007, at 9:19 AM, Chris Parrish wrote:
>
> Sounds like you're heading in the right direction (IMHO, anyway).
> Feel
> free to contact me directly. Others are welcome too -- I'd like to
> consider all possibilities. I think that this is a much needed aspect
> to radiant (though mayb
Nothing ready for public consumption just yet ... though I am hoping to
have it ready soon (next week or so, if my free time holds up).
On Sat, 24 Feb 2007 03:12:05 -0700, Keith Bingman <[EMAIL PROTECTED]>
wrote:
> I wrote one of the first extensions for this, but kind of dropped it
> as I w
> It also forces the user to use their memory instead of having the system
> keep that knowledge: "I need picture X -- I know I used it before. Let
> me see, where did I put that..." In my opinion, any good system should
> be able to tell you where (or if) assets are being used (in other words
>
Nathan Wright wrote:
> While I agree that they are an "asset" in a sense, they are also an
> asset
> with a behavior, and that certainly complicates things quite a bit.
> Depending on the technical skill (or lack thereof) of a user they could
> even bring down your site (image a bad javascript fil
On 2/26/07, Nathan Wright <[EMAIL PROTECTED]> wrote:
I'm hoping that someone makes an asset manager that's so well thought out
and executed that John looks at it and says "Damn, we've got to have
that!"
The have an interesting look asset management system at
http://www.silverstripe.com/home/.
Just had a little bit of a poke around in their demo site. What ideas are you
thinking we should borrow?
On 2/26/07, Nathan Wright <[EMAIL PROTECTED]> wrote:
I'm hoping that someone makes an asset manager that's so well thought out
and executed that John looks at it and says "Damn, we've got to
On 3/2/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote:
Just had a little bit of a poke around in their demo site. What ideas are
you thinking we should borrow?
I liked the method used for maintaining an image in page. Option to select
another from the asset location or via an upload. Which I
I just finished building a site that used a lot of PDF files scattered
across pages. At over 50 pages, in some cases a single PDF fit well on
more than one page.
Now that I'm done, it looks like I am going to build another page
listing all the PDF documents - an asset tree, if you will. This
13 matches
Mail list logo
