Two minor things remain and I hope to see them fixed or changed for aesthetic reasons.
The Welcome to Freeway dialog still shows a file not found error. Even a simple Welcome message on the SP server would suffice.
The Check for Updates item returns a dialog saying it couldn’t find anything, am I connected to the Internet?
It seems like both of these could be fixed without changing the app itself at all. It would help show that SP is still around/back, especially to those who aren’t on FWTalk.
Joe
freewaytalk mailing list
email@hidden
Update your subscriptions at:
On 5 Feb 2017, at 14:13, Joe Muscara email@hidden wrote:
The Check for Updates item returns a dialog saying it couldn’t find anything, am I connected to the Internet?
I think updates were disabled (maybe remotely) because there was a security issue with the update code (Sparkle) and Freeway was using an old version that didn’t get patched.
The best thing might be to remove the menu option in a future update.
On 8 Feb 2017, at 18:34, MarkSmith email@hidden wrote:
What’s the official word on how this works with Sierra?
As far as I know, Freeway works fine with the current version of Sierra (I’m still using El Capitan). There were minor issues with previous versions of Sierra, which were caused by OS bugs that Apple has now fixed.
I installed Sierra on it then did a Migration [something which seems anathema on both side of the pond!] from the old to new and everything works as in FW7 no need to reinsert the serial.
A warning if you’re still using CS6 because you don’t like the rental model of Adobe, like me. it might not work as expected. I anticipated this and have an install of Yosemite running an a VMWare virtual machine. This is not prefect, but does mean I can carry on using CS6 when I need to.
Peter
On 9 Feb 2017, at 10:02, Robert Mitton email@hidden wrote:
Thanks!
Now I am not afraid to move on with my Mac updates! Thanx for coming back to life!
CS3 seems fine on Sierra. You have to re-install Java SE6, but after that it just works.
I’ve pretty much kicked the Adobe habit - I’m on Affinity Photo and Designer these days. I do have a machine stuck on 10.7.5 that is going to be my go-to machine if /when Photoshop finally fails.
On 9 Feb 2017, 3:30 pm, pandion wrote:
I replaced my old MBP with a TouchBar one …
I installed Sierra on it then did a Migration [something which seems anathema on both side of the pond!] from the old to new and everything works as in FW7 no need to reinsert the serial.
A warning if you’re still using CS6 because you don’t like the rental model of Adobe, like me. it might not work as expected. I anticipated this and have an install of Yosemite running an a VMWare virtual machine. This is not prefect, but does mean I can carry on using CS6 when I need to.
Peter
On 9 Feb 2017, at 10:02, Robert Mitton wrote:
Thanks!
Now I am not afraid to move on with my Mac updates! Thanx for coming back to life!
CS3 seems fine on Sierra. You have to re-install Java SE6, but after that it just works.
You also need to install this to make CS6 work …
I’ve pretty much kicked the Adobe habit - I’m on Affinity Photo and Designer these days. I do have a machine stuck on 10.7.5 that is going to be my go-to machine if /when Photoshop finally fails.
I’m looking forward to seeing the introduction of Affinity Publisher, the ID replacement, I too have Affinity Designer and Photo which are great.
On 9 Feb 2017, 3:30 pm, pandion wrote:
I replaced my old MBP with a TouchBar one …
I installed Sierra on it then did a Migration [something which seems anathema on both side of the pond!] from the old to new and everything works as in FW7 no need to reinsert the serial.
A warning if you’re still using CS6 because you don’t like the rental model of Adobe, like me. it might not work as expected. I anticipated this and have an install of Yosemite running an a VMWare virtual machine. This is not prefect, but does mean I can carry on using CS6 when I need to.
Peter
On 9 Feb 2017, at 10:02, Robert Mitton wrote:
Thanks!
Now I am not afraid to move on with my Mac updates! Thanx for coming back to life!
We’ve replaced the build of 7.1.4 that was on the server with a new build that fixes a problem with template preview icons. Previously, the Templates pane of the New Document dialog was displaying generic icons instead of preview icons that show what the templates look like.
Thanks to Paul Dunning for reporting this problem.
Note: this is built from the same sources as the previous build, so it’s still 7.1.4.
You can download the new build by going to the Softpress web site and clicking on freeway7. Below the text that says “Try it free for 30 days” is a link that says “Already own it? Download Freeway 7 here."
Jeremy
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Edit URLs dirties pages so they are republished correctly
Jeremy,
I’ve been having serious page dirtying issues with the SiteMapper action that recur daily. Tim Plumb suggested that I open the Action and comment-out 4 lines in particular:
In addition to the page dirtying problem associated with the highly useful and important “Site Mapper” action, I would like to mention yet another thorn-in-the-flesh: Unwanted Master Page Item Renaming.
I need to use “getElementById” (JavaScript) fairly often, and document.querySelectorAll() isn’t always the best substitute. The problem is that I want to specify a specific item ID. The problem occurs when I use Master Page content. For reasons unknown to me (and honestly, irrelevant as far as my JS is concerned), Freeway will add a “1” to the end of the Name/ID I assign on the Master Page. For example, if I sketch a Form Field and name it “Field” and hit return (on the Master), the actual name appearing in the Inspector will be “Field1”.
This causes all sorts of problems for me because I want to put my JS code on the Master too and not have to change it page by page. But sometimes an item will get unlinked from the Master and its name won’t have a “1” at the end, and if I try to rename it with the 1, Freeway changes the “1” to a “2”!! It’s a horrid mess, really. The only way I can get around it is to modify my code on a per-page basis when the ID renaming happens, eliminating a lot of the help Master Pages give me.
So to recap the two problems I’ve mentioned to you:
Site Mapper Action Page Dirtying (entire site, every 24 hours)
Master Page Name/ID Remaning (that bothersome “1” at the end)
Thanks,
James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
