Wombat Beta - Feedback

[stlads]

Re: Wombat Beta - Feedback

Just Upgraded to PR7 Beta release and noticed that for the Product Import from flat file, the attribute template assignment is missing from the select box. Is this intentional or a bug or am I missing something?

[Rick Wilson]

Re: Wombat Beta - Feedback

Did you upgrade all the way to RC 2?

[stlads]

Re: Wombat Beta - Feedback

Yes, PR7 RC2

[sammy33]

Re: Wombat Beta - Feedback

In the Wombat demo admin under frameworks I see four different versions of the CSSUI.

Login: http://store.yellowtee.com/mm5/admin.mvc
User: demo
Pass: demo

Were these never released in the beta stream? I only have the one available for download from last September.

[Rick Wilson]

Re: Wombat Beta - Feedback

Those Frameworks are only there for testing and Beta purposes. True CSSUI is not a Framework and can not be applied on top of the legacy MMUI. When Wombat ships it will not include any predefined Frameworks in CSSUI, unless you save one.

[koala]

Re: Wombat Beta - Feedback

For those of us who do not want to move to CSSUI, are we going to be "missing out?"

As much as I'd like to clean up all of the code on my site and stop using tables, we're talking about a lot of work for an existing store.

Is there something fundamentally different about a CSSUI based store or are the changes purely within the page templates?

As it stands right now our current code reads like a disaster. It's a mix of <div> and <table> tags. lol...

[Rick Wilson]

Re: Wombat Beta - Feedback

No you won't be missing out on anything. It's purely just a better base for the template code.

[koala]

Re: Wombat Beta - Feedback

No you won't be missing out on anything. It's purely just a better base for the template code.

Thank you Rick. You must have this forum open 24 hours a day! Your answers are bound to start coming before our questions pretty soon here.

[Rick Wilson]

Re: Wombat Beta - Feedback

That's the beauty of an iPhone :)

[wcw]

Re: Wombat Beta - Feedback

Is there something fundamentally different about a CSSUI based store or are the changes purely within the page templates?

While it is probably technically possible, you would not want to switch an existing MMUI store to CSSUI. There is a whole new set of component modules that are used in the CSSUI. Additionally there are variables which are different so if your page template is coded to so something with a particular variable, that variable may not be there. Also, you have to be using 3rd party modules that use the CSSUI components and recognize the new variables. Hence, many of your 3rd party modules would need to be updated. I'm rewriting a bunch of modules that check the UI, then branch to specific code based on the finding. I finished one last night and I'll be working on another today. This is what was done in 4x with MMUI vs OpenUI. Stay with your css framework in the MMUI store. Only new stores should use the CSSUI. Period!

[RayYates]

Re: Wombat Beta - Feedback

Only new stores should use the CSSUI. Period!

We will probably not be converting current customers to Wombat and CSSUI any time soon for many of the reasons already listed.

If you really want to get the most out of the new CSSUI, have your host setup a dev.yoursite.com on a server that has been upgraded to the latest version of Empressa, Merchant and the CSSUI and do a site conversion. Have them migrate data so you have something to work with.

You can maintain your design and re-code it tableless. Keep in mind that tables are NOT evil and are completely appropriate for things like the shopping cart or line item search results. Tables inside tables inside tables... are evil.

[Rick Wilson]

Re: Wombat Beta - Feedback

I would like to jump in and clear up a couple misconceptions I see in the last few posts:

1. It's NOT TECHNICALLY POSSIBLE to switch between MMUI and CSSUI. So Bill's advice is more than advice, you can only use CSSUI on a new build.

2. Upgrading to Wombat will not "put you" on CSSUI. CSSUI is a brand new feature for new installs after someone has upgraded to Wombat. However upgrading to Wombat will in no way alter your existing template code.

Everyone's business is unique and they need to decide when it's appropriate for them to run their upgrades, however we've gone to great lengths to ensure that upgrading to PR 7 (Wombat) when it ships will NOT break your store and not alter your page code.

[benjamintr]

Re: Wombat Beta - Feedback

Hi Rick,

It seems as if there's a lot of confusion about what CSSUI is/isn't and the specific benefits/features that come with it.

May I suggest that you put out some sort of documentation with details and a FAQ when Wombat is released?

-B

[RayYates]

Re: Wombat Beta - Feedback

We will probably not be converting current customers to Wombat and CSSUI any time soon for many of the reasons already listed.

Just to clarify, I should have said Wombat Plus CSSUI. We would only convert a client to PR7 (aka Wombat) after confirming that 3rd party modules were all in place and working. Even then, we would likely do it on a dev site first. I tend to work on sites with lots of custom apps. and would be more concerned with those breaking as opposed to Merchant breaking.

The CSSUI is another issue. As has been stated, it is designed for new site builds. It is not an upgrade for your stores look and feel, but it has new features and templates. To take advantage of them, will require a site conversion.

[wcw]

Re: Wombat Beta - Feedback

The demo at http://www.mivamerchant.com/products.../merchant.mvc? is using mmui. Is there a similar demo of the CSSUI? I need to look at some things and I do not have a CSSUI store to work with. I had hoped to convert Emporium Plus but there was an order date issue with the 4x export module that needed to be fixed, plus it was not able to provision a CSSUI store from the export. The provide.xml would need extensive manual editing. Since many are asking questions about the CSSUI, perhaps everybody would benefit if there was a demo they could look at.