Stacks2 Review

photon

Given the significance of Stacks2 release and substantial new options available with the recent stacks for RW users, it would be very helpful if someone in the know and independent, could provide a review of Stacks2.

Some questions and thoughts for the review:
1. How come all this added functionality is now available for both developers and users?
2. What functionality should Stacks2 users be looking for to avoid duplication of stacks versions?
3. What is theoretically possible for Stacks2 development?
4. Should users drop Stacks1 for future website design and concentrate on Stacks2?
5. Comparison between Stacks 1 and 2 versions.
6. What major changes has Stacks2 brought to RW - eg versus existing plugins/stacks etc.
7. Any other input that would assist users moving to Stacks2.

Believe the review would be helpful to users, outside the info provided by YourHead and third-party providers.
If there is a review already available covering above, then link would be appreciated.

Photon

t-bone

I'm not going to answer all you questions, but I say this. I wish I would not have upgraded to stacks 2 because there are some issues with how stacks 2 publishes. I just got an email from the stacks 2 developer and they agree there are issues, and that they can't narrow the issues....

My recommendation is to wait.

Tony

Jive Dig

No time to get into it all. . . but I think anyone using Stacks1 right now is foolish for not upgrading. I'm not aware of any publishing issues, so if there are any (as above post says there are) they are not affecting everyone. My guess is the issues are for very specific usage types, and will be addressed very shortly.

The time I've saved and the greatness i've created in the few weeks i've had S2 are already worth the cost 10X over.

t-bone

on 1324939731:

No time to get into it all. . . but I think anyone using Stacks1 right now is foolish for not upgrading. I'm not aware of any publishing issues, so if there are any (as above post says there are) they are not affecting everyone. My guess is the issues are for very specific usage types, and will be addressed very shortly.

The time I've saved and the greatness i've created in the few weeks i've had S2 are already worth the cost 10X over.

That's a pretty broad brush you're painting with... Foolish?

I love stacks 2 and the GUI, but to say in general people who haven't upgraded is foolish, is, well, foolish to say.

We all have our own projects and different stacks, and I'm glad you haven't had issues. But I've spent many hours / days trying to find a way around this publishing issue, and I know of a few stacks dev's who are feeling the same pain as I am.

I got an email from yourhead this morning and they agree that there is indeed an issue and they don't know what the problem is.

Tony

Jive Dig

Maybe a bit broad, true.

Is the publishing issue regarding the resizing of photos in Stacks? That's the only thing i've heard thus far. And that one doesn't affect me as I do all my photo sizing/optimizing before I even bring them into RW.

t-bone

on 1324941281:

Maybe a bit broad, true.

Is the publishing issue regarding the resizing of photos in Stacks? That's the only thing i've heard thus far. And that one doesn't affect me as I do all my photo sizing/optimizing before I even bring them into RW.

The image thing is but a small issue compared to the issue at hand. The issue I and others are dealing with is the publishing glitch. Preview and exporting is fine, but when it's PUBLISHED is when things go wrong.

Tony

t-bone

Ok, here's an example.

This page is using zip bar and worked fine about 5 minutes ago, then I marked page as changed, published and this is the result.

http://032eabc.netsolhost.com/pig/page61/liquidfeeding/callmatic2.html

Ed Brenner

Some questions and thoughts for the review:
1. How come all this added functionality is now available for both developers and users?
2. What functionality should Stacks2 users be looking for to avoid duplication of stacks versions?
3. What is theoretically possible for Stacks2 development?
4. Should users drop Stacks1 for future website design and concentrate on Stacks2?
5. Comparison between Stacks 1 and 2 versions.
6. What major changes has Stacks2 brought to RW - eg versus existing plugins/stacks etc.
7. Any other input that would assist users moving to Stacks2.

#1.
I believe you would have to ask Isaiah that question as he is the developer of the plugin.

Here's my 2¢ though, RW user's are always asking for more. More they can do on their own without the "need" for someone else to "sell" it to them. Say hello to the more.

#2.
What "duplication" of versions are you speaking of?
Individual 3rd party developers are responsible for either updating their stacks or not to take advantage of the new additions to the API.
I'll use myself as an example. I updated my stacks to include some of the new API features: Grouping, Subtitles and Image/Icon format. Those changes don't affect which version of Stacks you are using.

#3.
Again, this is probably only a question that a "developer" type could answer. Or, Isaiah himself.

#4.
I believe that that is a personal choice.

#5.
Here's a brief and simple comparison of the changes that I appreciate...

Stacks 1 - The "library" is one long list of stacks = endless scrolling to find what you need. Each stack uses an independent "pop-up" HUD. Auto Updates were a nightmare ( just my opinion ).

Stacks 2 - Organized "library" - if the independent stack dev wants to use it. Everything "contained" within the RW "framework", hence no more HUDs. Auto Updating is shown via a dropdown and allows the end user to choose whether to update all or control the process by selecting the individual stack and applying the update.

#6.
Stacks, in general, has provided us with a "flexible" layout process for our design abilities within the RW framework.

Stacks 2 has added some new "features" such as Templates and Media. I don't know the "full extent" of these as I haven't dug into them to see how they work.

#7.
Communicate. With the 3rd Party Stacks Devs whom you have purchased from. Ensure that what you use works with Stacks 2.
Adam from seyDesign posted a response to "compatibility issues" here.
Some folks have encountered issues while others have not.

Don't limit your communication with just the "independent" stack dev. If you're seeing an issue communicate it to the PlugIn developer as well.

Colorwave

I think that many of the changes in Stacks 2 affect the RW user, but are not necessarily things that make the experience any better for the site visitor. The way that images are handled, though, seems to be the biggest improvement to me. If you use JPEGs, you can now not have to worry about them being converted to PNGs by Stacks, then left that way or converted back to JPEGs by RW. You can mix image types on the same page, and know that if you started with high quality, optimized images, that they will be delivered that way to the end user. As an image guy, this tops the list for me.

Jive Dig

on 1324942347:

Ok, here's an example.

This page is using zip bar and worked fine about 5 minutes ago, then I marked page as changed, published and this is the result.

http://032eabc.netsolhost.com/pig/page61/liquidfeeding/callmatic2.html

Wow. Now that IS an issue. Hopefully all that gets sorted asap. I've not had any of those issue yet. Nice site btw