[t5c] Category Tree
On 5/11/05, [email protected] <[email protected]> wrote:
> Bill,
Ok, I'm not the Bill you replied to, but he gets half of my email
anyway, so... :)
=20
> I think you missed my point. I am not upgrading to Merchant 5. I do
> have a copy of Merchant 5 so that I may learn the new Miva tokens and
> layout templates, but I will not upgrade anytime in the near future,
> I can't.
Understandable, and probably a wise choice to wait (even if you could
upgrade now).
=20
> Here is my beef.... My gut tells me that Merchant does not want to
> open the entire UI to customization in order to sell modules. (my
> opinion for all you listeners) I do not want 3rd party modules for
> layout and design. (no offense module developers) I need access to
> the templates for not just the category tree, but the attributes, the
> buttons, the breadcrumbs etc. etc.
I'm confused by some of this (but it's not that important).
Personally, I'm pretty sure that M5 will be wide open for development,
or the people in the beta group would be screaming by now. They're
not. They're converting modules.
You don't want 3rd party modules for layout and design, but you use
OUI? Call it what you will, but that's a contradiction.
Breadcrumbs and attribute templates were never a stock feature. If
you have either, you have 3rd party modules. If they're stock in M5,
that's a step forward on Miva's part (in my opinion).
=20
> I also wish Miva was a little more open... Merchant 5 was so hush
> hush... for what reason? If they were to say hey, this is what we
> are working on for future releases, this is the direction we are
> heading... that would be great! But I have to tell you, it is really
> tough to determine what direction to head when there are no signs.
They did announce the direction they were heading in. I believe, they
first talked about 'templated' Merchant 3 years ago. My only
disappointment is with how long it took for that to happen.
M5 is hardly 'hush hush', they had a beta group. For Miva, that's a
first. M1-M4 were simply released, and you found out what they did
when you installed them. M5 is practically 'glasnost' at this point,
I waited years for this to happen, and I wish I'd been a part of the
beta.
> I have three new sites on the back burner right now. Do I code these
> sites in Merchant 4 using OpenUI/OpenDesigner and then have to recode
> them in Merchant 5 in six months? ...or do I bite the bullet and
> code them in Merchant 5 and end up having to buy a bunch of modules
> to get store functionality in the future? ...or do you go with an
> entirely different Ecommerce solution?
Go with M4 using custom MMUI, or OUI as you choose. Few (if any) will
want to convert a store they just built within 6 months, and modules
will be supported for at least another year. If it works for you
today, why change until you have something else that's solid? The
point is, there's still quite a few older Merchant stores running...
because they just work.
Switching to another system may seem appealing, but that would only be
true if you ignore both, the learning curve, and the fact that no
solution is perfect. Any other solution will have problems, they'll
just be different problems (or perhaps the same problems). And you'll
have to learn the ways around them, just as you do with Merchant.
> Miva has put us in a bad spot and they are not communicating with the
> end users.... that sucks!
Again, I think they're communicating with us more than they have in
the past. They did peak about 3 or 4 yrs ago, but even then, it
didn't come close to what they're doing now.
In the end, I'm _very_ optimistic about Merchant 5.
--=20
Bill Guindon (aka aGorilla)
On 5/11/05, [email protected] <[email protected]> wrote:
> Bill,
Ok, I'm not the Bill you replied to, but he gets half of my email
anyway, so... :)
=20
> I think you missed my point. I am not upgrading to Merchant 5. I do
> have a copy of Merchant 5 so that I may learn the new Miva tokens and
> layout templates, but I will not upgrade anytime in the near future,
> I can't.
Understandable, and probably a wise choice to wait (even if you could
upgrade now).
=20
> Here is my beef.... My gut tells me that Merchant does not want to
> open the entire UI to customization in order to sell modules. (my
> opinion for all you listeners) I do not want 3rd party modules for
> layout and design. (no offense module developers) I need access to
> the templates for not just the category tree, but the attributes, the
> buttons, the breadcrumbs etc. etc.
I'm confused by some of this (but it's not that important).
Personally, I'm pretty sure that M5 will be wide open for development,
or the people in the beta group would be screaming by now. They're
not. They're converting modules.
You don't want 3rd party modules for layout and design, but you use
OUI? Call it what you will, but that's a contradiction.
Breadcrumbs and attribute templates were never a stock feature. If
you have either, you have 3rd party modules. If they're stock in M5,
that's a step forward on Miva's part (in my opinion).
=20
> I also wish Miva was a little more open... Merchant 5 was so hush
> hush... for what reason? If they were to say hey, this is what we
> are working on for future releases, this is the direction we are
> heading... that would be great! But I have to tell you, it is really
> tough to determine what direction to head when there are no signs.
They did announce the direction they were heading in. I believe, they
first talked about 'templated' Merchant 3 years ago. My only
disappointment is with how long it took for that to happen.
M5 is hardly 'hush hush', they had a beta group. For Miva, that's a
first. M1-M4 were simply released, and you found out what they did
when you installed them. M5 is practically 'glasnost' at this point,
I waited years for this to happen, and I wish I'd been a part of the
beta.
> I have three new sites on the back burner right now. Do I code these
> sites in Merchant 4 using OpenUI/OpenDesigner and then have to recode
> them in Merchant 5 in six months? ...or do I bite the bullet and
> code them in Merchant 5 and end up having to buy a bunch of modules
> to get store functionality in the future? ...or do you go with an
> entirely different Ecommerce solution?
Go with M4 using custom MMUI, or OUI as you choose. Few (if any) will
want to convert a store they just built within 6 months, and modules
will be supported for at least another year. If it works for you
today, why change until you have something else that's solid? The
point is, there's still quite a few older Merchant stores running...
because they just work.
Switching to another system may seem appealing, but that would only be
true if you ignore both, the learning curve, and the fact that no
solution is perfect. Any other solution will have problems, they'll
just be different problems (or perhaps the same problems). And you'll
have to learn the ways around them, just as you do with Merchant.
> Miva has put us in a bad spot and they are not communicating with the
> end users.... that sucks!
Again, I think they're communicating with us more than they have in
the past. They did peak about 3 or 4 yrs ago, but even then, it
didn't come close to what they're doing now.
In the end, I'm _very_ optimistic about Merchant 5.
--=20
Bill Guindon (aka aGorilla)
Comment