I use X.Y.Z also, except bug fixes always get rolled into a Z release and Y releases usually only happen when Z rolls over. X releases are complete rewrites (i.e. probably not able to migrate easily without starting over). See my item’s changelog in its demo for an example.
Wait for retina displays. You’ll kick yourself in 6 months when they start pouring onto the market. The Apple displays marry perfectly with MBP. As soon as they release one I’ll be getting it.
Buy all the devices you can afford, and get used to the fact that there is no standard DPI anymore. If you want to keep working as a designer you have to be aware of how the medium is changing.
Also: nobody regrets getting a Retina MBP. It’s an amazing machine and I wouldn’t trade it for any other.
Once again…and that’s why updates should be paid for. Both sides need an incentive.
You spend $30 for a haircut every few months ($60 if you’re a woman). Is it really so hard to swallow that highly technical products being maintained and improved have a lifetime value beyond the initial purchase?
I accidentally posted a comment reply in the wrong input, and then flagged my comment so the duplicate could be removed. Which looks like this:
Now, it looks like I wrote an inappropriate comment on my own item. I think “innocent until proven guilty” should be the standard. It would be more neutral for the marketplace if the flagged comment message read:
This comment has been flagged and will be reviewed by our staff.
My point was the market for Enterprise themes is a tiny fraction of Community themes. Since Enterprise is so different at the code-level you cannot take a Community theme and implement it on Enterprise without massive rewrites. At that point you’d be much better off starting a custom implementation on Enterprise.
Realistically, if you don’t have the budget to do a custom frontend with Enterprise then you should probably be using Community and applying the money you would save to extend it with the functionality you need.
But don’t put the movie in your package. Upload it to YouTube and embed it.
About 65% of the frontend files in Magento Community are different in Magento Enterprise. It’s not possible to develop a theme that works in both without essentially developing two independent products that look indiscernible.
Magento Enterprise projects tend to require unique design, so there really isn’t a large market for “visual” themes. A frontend framework like http://magefrontend.com/ is probably more useful since it doesn’t prescribe the graphical properties of the project.
Authors are not required to provide any updates or support (Envato’s rules), but many do. You should research the author to see what their policy of providing updates/support is. Take it at face value only though, their history of providing support/updates is the best indication of future behavior. If they have no history it’s a gamble.
Using the mobile dashboard, comments are posted twice. Can’t use it until that’s fixed.