Asset Manager Mephisto Style

For fun I installed Mephisto yesterday. Wow is it cool for a blogging
app. (http://mephistoblog.com/)

Mephisto’s Asset management systems is as they claim it is, ‘probably
the best you’ll find in any CMS/Bloggin application’. All I can say is
wow, they have Buckets!

Looking at both Radiant and Mephisto I can see two very similar apps
heading in two different directions. Just wondering if for some of the
‘lower level’ stuff like comments, asset management, etc. is it worth
‘sharing’? I would just hate to see a competition to see who’s is
better when working together could potentially make both better.

Mephisto is blog, Radiant is CMS first Blog second. Just wondering if
we should work with along with Mephisto thats all.

Thoughts?

Nicholas Mulder

Mulder Consulting
905 658 5641
[email protected] mailto:[email protected]

Nicholas Mulder [Mulder Consulting] wrote:

For fun I installed Mephisto yesterday. Wow is it cool for a blogging
app. (http://mephistoblog.com/)

Mephisto’s Asset management systems is as they claim it is, ‘probably
the best you’ll find in any CMS/Bloggin application’. All I can say is
wow, they have Buckets!

Once we have a robust plugin system going I would love to see someone
create an asset management solution similar to Mephisto’s. I’m not sure
if buckets trump the idea for attachments, but it is definitely causing
me to rethink my previous ideas about assets.

Looking at both Radiant and Mephisto I can see two very similar apps
heading in two different directions. Just wondering if for some of the
‘lower level’ stuff like comments, asset management, etc. is it worth
‘sharing’? I would just hate to see a competition to see who’s is
better when working together could potentially make both better.

That would probably be up the the plugin authors (and the Mephisto
people). But I do think it would be great if code could be shared.


John L.
http://wiseheartdesign.com

On 9/1/06, John W. Long [email protected] wrote:

if buckets trump the idea for attachments, but it is definitely causing

John,

The Mephisto style for assets sounds good, but plain or direct use of
their code could be difficult.

They store the assets on the file system, on contrary that your desire
to leverage only on DB to distribute everything for Radiant.

Maybe the way they choose to use it could change your mind.


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

I believe that Mephisto uses the acts_as_attachment plugin (which
works great by the way), and you can set this plugin to store
attachments in either the file system or in the database. While
waiting for a real solution for the images issue in Radiant, I hacked
together a rich text version of Radiant using this plugin. My client
has been using it for 2 months now without a single problem.

On 9/1/06, Nathan W. [email protected] wrote:

I believe that Mephisto uses the acts_as_attachment plugin (which
works great by the way), and you can set this plugin to store
attachments in either the file system or in the database. While
waiting for a real solution for the images issue in Radiant, I hacked
together a rich text version of Radiant using this plugin. My client
has been using it for 2 months now without a single problem.

Glad to hear that, haven’t checked the guts of mephisto yet.

What really amazed me about it is that broke webrick! (yeah, you need
mongrel to run it, even for testing).

Anyway, A few things are needed in the Radiant roadmap (as John said,
plugin capability) and then everything will follow, blogging, assets,
you name it!

Once we have a robust plugin system going I would love to see someone
That would probably be up the the plugin authors (and the Mephisto


[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

Luis L. wrote:

The Mephisto style for assets sounds good, but plain or direct use of
their code could be difficult.

They store the assets on the file system, on contrary that your desire
to leverage only on DB to distribute everything for Radiant.

Maybe the way they choose to use it could change your mind.

I’m sure it would be difficult to use their code without modification.
However, I find I can revamp other people’s code almost twice as fast as
it would take me to write it myself. If someone were to choose to write
a plugin based off of the Mephisto code, I’m sure it would be much
simpler than writing it from scratch.


John L.
http://wiseheartdesign.com

John W. Long wrote:

Once we have a robust plugin system going I would love to see someone
create an asset management solution similar to Mephisto’s. I’m not sure
if buckets trump the idea for attachments, but it is definitely causing
me to rethink my previous ideas about assets.

Hi John,

How hard do you think it would be to implement such a system in Radiant?

I’m currently developing a rather hacked together version of Radiant for
a clients portal (of which the first stage has a deadline of two weeks
today) and I will need to implement some way of having multiple images
per page and custom tags to include those images.

I was thinking of just using the acts_as_attachment plugin and modifying
the text filters to parse the custom image tags for the timebeing, or
would having radius tags be a better plan of attack?

I’m very interested to hear that there is a more robust plugin mechanism
in development, are there any further details about this anywhere?

Thanks,
Kev

On Sep 4, 2006, at 8:41 PM, Kevin A. wrote:

Hi John,

How hard do you think it would be to implement such a system in
Radiant?

I’m currently developing a rather hacked together version of
Radiant for
a clients portal (of which the first stage has a deadline of two weeks
today) and I will need to implement some way of having multiple images
per page and custom tags to include those images.

If you need something that ‘works now’ you could try Dror’s page-
parts-type patch (which i cant find on Trac right now?). I used on
our last client project and it worked fine.

Bodhi

Bodhi wrote:

If you need something that ‘works now’ you could try Dror’s page-
parts-type patch (which i cant find on Trac right now?). I used on
our last client project and it worked fine.

Bodhi

I hadn’t seen any mention of that before. I found the related Trac
ticket but it’s just giving an error -
http://dev.radiantcms.org/radiant/ticket/147

Who’s the admin for the trac server? Seems like there is some data in
that ticket that it doesn’t like.

Kev