They should work hard on code rewriting, especially on the performance side (FW 6.1.2 is much slower than 5.5.x).
Also, I notice that currently it runs at 32 bit only. Probably for big websites with tons of images it will help a lot to have a 64 bit addressing space. E.g. A freeway doc of 660 MB requires about 30 seconds to open on a iMac i5 / 4 cores / 3.30 Ghz… very frustrating…
Marco, I noticed the speed issue, too. My Freeway document is only 33mb, but takes 13 seconds to open on the Mac listed in my footer below.
660Mb in 30 seconds…frustrating? It should give me the right sense of feeling that I am importing a huge amount of data. I can hardly brush my teeth in that amount of time ;-).
Nevertheless, I’m looking forward to see FW7 see the light. The ease of use and easily working from scratch has always been my first choice for Freeway. And indeed the great help from people like Walter D, Max Fancourt (WebYep), Noadis (Dutch FW distributor) and more. I’ve used Backdraft but get struggled with a lot of output problems. I hope FW7 will become really responsive/adaptive and if they put also a standard CMS into it, I’ll jump 100 times in the air.
Never really had a problem with the multiple undo thing although it would be nice occasionally. However what I really need to save time is to be able to apply actions to multiple items in one go i.e. selecting more than one item and applying the action. This would save the mind numbing repetitiveness of web design
Never really had a problem with the multiple undo thing although it would be nice occasionally. However what I really need to save time is to be able to apply actions to multiple items in one go i.e. selecting more than one item and applying the action. This would save the mind numbing repetitiveness of web design
I’ve contacted Ulli from Pulse and Max from WebYep and they both mentioned that their CMS options should working with Freeway 7’s responsiveness. Max said he is willing to set up a tut for implementing WY in FW7 as soon it is published. I’ m also using a very nice CMS slider (http://www.jstyler.net/) but that one conflicts with WebYep sadly. A built-in option would sure be more then welcome.
I seem to remember another e-letter, some months ago from Bill, when he first mentioned that the next version of FW would be ‘what I was hoping for’ (which I took to mean responsive) and also that a new CMS action was being built for it… by Walt…
Could be getting senile or suffering wishful thinking of course.
I am still working on my CMS, and aiming to launch it soon. It’s working, but needs some serious interface work before it’s ready for daylight.
Walter
On Jul 3, 2014, at 12:49 PM, Nik Andrew wrote:
I seem to remember another e-letter, some months ago from Bill, when he first mentioned that the next version of FW would be ‘what I was hoping for’ (which I took to mean responsive) and also that a new CMS action was being built for it… by Walt…
Could be getting senile or suffering wishful thinking of course.
I have been using Pulse as my CMS of choice for a while now and it does indeed integrate well into responsive sites (created with backdraft) however they have changed the way it operates with the most recent version and my server has issues with the php paths/permissions so I have to use a workaround which is not ideal.
Walter, do you have an ETA for yours? (or should I just ask the obvious - how long is a piece of string? :))
ha thats curious… I also get that answer that FW would ‘give me were I
was hoping for’. After I wrote that I had plans to switch to another
webdesign program because the lack of a CMS and responsive option. I pray
now for both on my bear knees.
Op 3 jul. 2014 18:53 schreef “Nik Andrew” email@hidden:
I seem to remember another e-letter, some months ago from Bill, when he
first mentioned that the next version of FW would be ‘what I was hoping
for’ (which I took to mean responsive) and also that a new CMS action was
being built for it… by Walt…
Could be getting senile or suffering wishful thinking of course.
I’m working on it, but I don’t have a solid ETA. Fine-tuning the interface and writing the documentation are taking approximately a million times longer than expected.
I should disclaim right away that it is designed to be simple and minimalistic, and it is a hosted product (subscription).
You do need PHP on your server to run the proxy between your server and mine, but you don’t have to add any code to your pages or install anything like a database on your server. The premise is that you make your templates in Freeway, just as you normally would make any other page. Apply an Action to one or more parts of the page, and it becomes a template. No further configuration is needed beyond uploading a tiny PHP script and an .htaccess file to your site root.
Walter
On Jul 3, 2014, at 2:18 PM, MarkSmith wrote:
Walter, do you have an ETA for yours? (or should I just ask the obvious - how long is a piece of string? :))
@Mark. You are using Pulse… if I’m right, with Pulse you place a tiny
codeline in the HTML for the content you want to edit online. . But… if
you offline update your site with FW again, is your pasted code then lost?
Or is that codeline placed in the header or bodytags with markup?
Op 3 jul. 2014 20:18 schreef “MarkSmith” email@hidden:
I have been using Pulse as my CMS of choice for a while now and it does
indeed integrate well into responsive sites (created with backdraft)
however they have changed the way it operates with the most recent version
and my server has issues with the php paths/permissions so I have to use a
workaround which is not ideal.
Walter, do you have an ETA for yours? (or should I just ask the obvious -
how long is a piece of string? :))
@Walter That sounds great Walter. Do you need any help with it?
Op 3 jul. 2014 20:53 schreef “Walter Lee Davis” email@hidden:
I’m working on it, but I don’t have a solid ETA. Fine-tuning the interface
and writing the documentation are taking approximately a million times
longer than expected.
I should disclaim right away that it is designed to be simple and
minimalistic, and it is a hosted product (subscription).
You do need PHP on your server to run the proxy between your server and
mine, but you don’t have to add any code to your pages or install anything
like a database on your server. The premise is that you make your templates
in Freeway, just as you normally would make any other page. Apply an Action
to one or more parts of the page, and it becomes a template. No further
configuration is needed beyond uploading a tiny PHP script and an .htaccess
file to your site root.
Walter
On Jul 3, 2014, at 2:18 PM, MarkSmith wrote:
Walter, do you have an ETA for yours? (or should I just ask the obvious
The code you place in the FW site is a php include via a markup item so as long as this remains intact, you would not lose it.
You can then edit the corresponding ‘blocks’ in Pulse independently and the include will ‘see’ them.
It is really easy to set up but as I mentioned before, the latest version uses different paths and may conflict with some servers security settings.
On 3 Jul 2014, 6:57 pm, Andries Kuipers wrote:
@Mark. You are using Pulse… if I’m right, with Pulse you place a tiny
codeline in the HTML for the content you want to edit online. . But… if
you offline update your site with FW again, is your pasted code then lost?
Or is that codeline placed in the header or bodytags with markup?
Op 3 jul. 2014 20:18 schreef “MarkSmith”
however they have changed the way it operates with the most recent version and my server has issues with the php paths/permissions so I have to use a workaround which is not ideal.
Thats interesting Mark. I had issues with Pulse on a windows server with an earlier version, never resolved, but thats an v old story. I’ve used Pulse on numerous sites and recommend it.
However, their ‘improvements’ with new versions do seem to be questionable. Removing blog search is one that affected a site I was doing, in favour of a google site wide search, other things not implementing smoothly. Still recommend it though for ease of integrating with FW.
Back to thread; looking forward to seeing what FW7 offers.
Please understand me correctly, I love Freeway Pro!!
But Responsive Webdesign is known since 2010 and already is out there for a while. So even though I love to see it implemented, it’s clapping for something that’s not very new.
There are many other things and some of them already mentioned many times that i’d like to see implemented.
But again, I love the software, I love the company behind it and am very interested in what’s coming.
Not to interrupt or disturb the nice conversation here.
You all remember the announcement of “Relative Page Layout” with version 5 (or 5.5)?
It was a biiig hooray cause the absolute necessity of proper (evil) inflow construction had been declared as redundant. People meant with just applying an action they can now have “areas stretching all across the browser window width”. It took a while to understand the magic of the action, but it mainly worked vertical and had been made to prevent overlapping (inflow light).
Unfortunately the need of “positioning relative” was still alive.
Now we got the small note, that you’ll be able to create responsive pages - probably by applying an action and done.
It would be cool - yeah indeed - it would.
But what, if it is just a “helping hand”, something that prevents you from manually add stuff to the head or elsewhere? What if you still need a proper inflow construction? What if still need an imagination what will happen if … ? Even more:
What happens if you need to know what percentage-width, float, clear, padding and margin is? And how to change what for reaching our goals?
And finally - uahhhh - do I need BoxInBox-Model?
Hm - if I have a look into my crystal-ball, I see … wait … unsure … boxes? But gosh - I can’t see how they are positioned.
what if?? ha… Im just so happy I had responsive schooling from you and Caleb, Backdraft. at least whatever transpires with FW7, Ill have some idea, even basic
I couldn’t help myself thinking about this ex-collegue of mine a while ago, still stuck on his Mac OS8 Postscript workflow, who suddenly had to move to an OSX PDF workflow and could not stop complaining about the huge amount of changes that -surprise surprise- made his hair go white overnight. Years of holding on to the past now took him forever to catch up with the current.
Those who don’t keep up with the natural progression have a lot of catching up to do, not easy with the lack of knowledge they’ve ignored for so long.
Responsive web design has been around for years, so has the box model layout. I started using this layout model since FW5 and it’s been a breeze, really. It might appear intimidating, but it’s not. Not at all.
