Thanks.
I will definitely upgrade as soon as it will be released. hope to become Beta Tester.
The good is that I can use parallel Installation of 6&7 and keep my important projects in RW6.
Thanks
Peter
Yes count me in 
I’m in, waiting with anticipation!
@dan I will definitely be updating - but I hope it will not take as long as Version 6 to stabilise.
The path to a resource is entirely dependent on the location of the page you’re pasting it into. Would an easier option to copy the resource macro be useful in its place?
No. We’ve not hit this at 7.0 as we’ve focused on portable documents. We have a ticket in the tracker for this though 
Yup. They’re now tabs instead of a list of fields, and we’ve added a new “body” area.
Yes. Totally new view and completion engine, with option to turn it off if you’d prefer not to have it.
Nothing this time around.
If you’ve listened to the podcast, you’ll already know about the ability to configure multiple publishing destinations, and “Export” is now “Publish to a local folder” so you get smart publishing by default for changes. We found that most people never simply “Exported Changes”, so in addition to our parallel publishing (which applies locally, too) it’s far quicker when working locally.
Obviously it all depends on your projects. We’ve seen preview be at least twice as quick to render previews. As RW7 uses more modern OS X developer APIs, we’re able to take advantage of the performance enhancements (subtle though they may be on their own) in the latest OS X SDKs.
—N
The path to a resource is entirely dependent on the location of the page you’re pasting it into. Would an easier option to copy the resource macro be useful in its place?
Apologies, perhaps I’m being dense (as usual), but I’m not sure I completely understand. Do you mean that if we take lets say a file called header.jpg in a folder called images in project resources. What do you propose we get when we control click it? I would like to be able to copy to the clipboard a resource macro which includes the path to that resource synthesised using the currently selected page as the context for the path. Would that be possible?
Will I be able to drag a folder full of resources in to the project?
No. We’ve not hit this at 7.0 as we’ve focused on portable documents. We have a ticket in the tracker for this though
Well, that is a pity.
Yup. They’re now tabs instead of a list of fields, and we’ve added a new “body” area.
Sounds promising. Can we control where code placed in the body area will be injected into the DOM?
Has code completion / code suggester been improved?
Yes. Totally new view and completion engine, with option to turn it off if you’d prefer not to have it.
Again, sounds good. I’m all for it, when it works and helps.
Blog page? Anything?
Contact page? Anything?
Nothing this time around.
Doesn’t bother me as there are now loads of quality solutions out there, but I’m surprised that at V7 the blog and contact form will be the way they are. You obviously have your reasons for not developing those pages any further.
If you’ve listened to the podcast, you’ll already know about the ability to configure multiple publishing destinations, and “Export” is now “Publish to a local folder” so you get smart publishing by default for changes. We found that most people never simply “Exported Changes”, so in addition to our parallel publishing (which applies locally, too) it’s far quicker when working locally.
I don’t listen to the podcast, I’m afraid. I was more wondering about visibility of which file was being processed, more reliable/faster transfers, visibility of the directories and files on the host (and dare I say it a file manager to interact with the host/a chmod tool etc ).
Obviously it all depends on your projects. We’ve seen preview be at least twice as quick to render previews. As RW7 uses more modern OS X developer APIs, we’re able to take advantage of the performance enhancements (subtle though they may be on their own) in the latest OS X SDKs.
Previews twice as fast? Nice. Is that just base RW pages or Stacks pages too?
I’m not sure. I’m just getting back to publishing a site after 5 years and the upgrade process from 5 to 6 seems like a pain. Definitely not set and forget. I get errors saying it can’t find my content. The interface on 6 looks so different from 5 (was it really a problem?) and I can’t even find the plugins to upgrade them, that I feel like I have to learn RW all over again. I’m actually considering giving my site to someone else to design because I don’t want the hassle of relearning RW all over again. In all fairness I haven’t used 6 at all so another upgrade seems too soon and the $59 seems just a tad high. I’m actually feeling kinda discouraged at using RW - I used to love it.
Philip,
5 to 6 was indeed a big leap. It looks as though 6 to 7 will be a very very small one.
According to the PodCasts and the gleaming of info from the forums, it looks like a pretty substantial update actually.
I think we will all be surprised when it is launched.
5-6 was a pretty big change but mostly UI stuff and bugs, some people don’t like change and that’s ok, but improvements are necessary to fix bugs sometimes imho.
Brad
Will it be possible to password protect the Backup ZIP?
Brad,
You’re right, of course, that 7 will have many new features, and that the interface appears to have been rationalized. Good news!
What I mean in reply to @Philipnb is that the substantial inconvenience and many hours of hard work caused by a complete rewrite of the app such that the locations of add-ons, the way to install them, the project file format, incompatibility between 5 and 6 for many third party tools etc looks as though it’s been avoided this time.
I actually gave up trying to ‘convert’ my sites built in 5 and rebuilt all of them in 6 - chiefly because of the large number of add-ons which just would not work in 6. The thought that this has been avoided this time fills me with delight 
Ahhh… you are absolutely right Mark!
Fortunately, I only see that from a forum advocate point of view. I have the software installed, can make projects in it, can do troubleshooting with it but I haven’t had the need to depend on it on a day to day basis. RW 6.x on the other hand, I have had to depend on and have had few lagging issues.
I’m sure that RMS have taken into account the headaches associated with the previous upgrade process and hopefully made it better for us to do the upgrade to 7.
As an outsider, I can see them looking and going… ok, where did we have serious issues that we must avoid in the next upgrade, what have users been complaining about in the forums the most, what have crash logs been reporting consistently, what feature requests have been asked for, what do developers want for improvements to the API…
So yeah, I’m sure @dan and team do not want a repeat performance 
Time will tell and I can’t wait to use it and see what’s what in the forums when 7 comes out… should be an interesting go. Probably need a couple weeks with it to figure things out to offer expeditious support but I’m not too worried at all and have faith.
Brad
Absolutely: this is also why we also made some changes to the upgrade process from RW 5 to 6 earlier in the RW6 lifecycle (i.e. we made some changes allowed RW6 to open RW 5.4.1 projects. This was made possible by our decision to not be in the Mac App Store w/RW6).
I always use Export Changes, so somewhat surprised by this comment and for anyone using a fast FTP program this is exactly how you would use RW. Are you saying that there is a new RW7 Export function that is quicker that the current RW6 Export Changes?
Also very keen to understand what RW7 is all about, but as I never listen to Podcasts, and never will, as it is just too inconvenient, it’s impossible to know what has been announced.
Yes, I’ll be upgrading. Rapidweaver is my favorite plaything!
Definitely but as with all major updates, I’ll run concurrently with 6 and give it a good trial run before jumping in the deep end. Very pleased to hear Dan’s emphasis on stability and just working. Hard to achieve but good to know these aims are top of the agenda rather than just new features. Hope the styles UI is improved…just saying.
I am only using Foundation these days, so I would first like to see what direction that goes with RW. What I have at the moment currently works fine but I haven’t forgotten the difficulties when RW6 was introduced so I’ll be a little more careful this time.
The changes mentioned above like portable documents etc are of little interest. I am wondering how an SEO health check can make your site load faster unless it’s just a suggestion to make images smaller.
Preview affects all pages, not just our built-in ones.
The code is inserted before the closing </body> tag, and that’s not changeable.
