Versions

Script-Linker-2.1.zip (2017-06-14) (Downloaded 31 times)

Contains:

Compatible: Pro 5.5, Pro 6, and Pro 7

Script-Linker-1.8.zip (2013-03-19) (Downloaded 107 times)

Contains:

Compatible: Pro 4, Pro 5, Pro 5.5, and Pro 6

Script_Actions.zip (2009-10-09) (Downloaded 18 times)

Contains:

Compatible: Pro 4 and Pro 5

Script_Maker.zip (2009-09-25) (Downloaded 12 times)

Contains:

Compatible: Pro 4 and Pro 5

Author: max fancourt

javascript css php softpress image free gallery targets slave reflection xml javascript library

This action set contains everything I could think of to allow you to construct intergrate and adjust an: xml, css, html, php, javacript, asp, txt… in fact just about any script type within Feeway that Freeway cant handle directly.

Release Notes Changes in 2.1

  • New: ScriptLinker can now link up-to 10 script pages
  • Bug Fix: Random bug fixes e.g. comments inclusion now works correctly

Release Notes Changes in 1.3

  • New: ScriptLinker can now link up-to 8 script pages
  • Bug Fix: ScriptLinker activation of interface is now working correctly
  • Bug Fix: ScriptCreator Can now be applied to a Master page   

Release Notes Changes in 1.2

  • New: ScriptMaker & Linker can now be used to edit and link to the lightweight and fast JavaScript toolkit; MoreCSS.
  • New: Freeway examples containing “JQuery & MoreCSS are now included.   

7 Comments

Hi I am trying to explore this action but all I can find is the install files for the Doc.Linker-can't find the Doc.Creator action anywhere. Am I missing something? I have searched the ActionForge site but no joy. Thanks. Martin

Having gone over things again I can see that there are two actions bundled in the package available for download here… but only one appears in my menus… what am I doing wrong? I have installed several timers but no go.

That's several times-not timers!

Hi Martin The Scriptcreator only appears in your action list if the specific page you are applying it too is set to document 3.2 within the inspector palette. There are some good reasons for this, but its mainly to do with getting around some problems I had with the other doc types. (This has no bearing on the final output as the document is completely changed to what ever you want). The main thing is set up your project as per normal… for example Document type XHTML, common resources, Site folder location, set up the master pages, ect and then when thats done, then you create a new master which you are going to use as your basis for all bespoke, scripts, css style sheets, xm docs, and set that master (within the inspector palette as doc type 3.2. Then from then on every time you need to add a new script or bespoke style sheet, then you won have to remember to set the doc type.

I have actually just updated this action set. and it now accepts a new type of document which is used by MoreCSS. this is a an easy to use, lightweight and fast JavaScript toolkit / library which uses CSS syntax.

I have also constructed some freeway examples that incorporate JQuery and MoreCSS which you can have a look at… so if you give me your email address i can send over the latest actions, plus the freeway examples and output.

speak soon max

Hi Max That's really helpful-thank you very much. My address is [email protected]

I'm fairly new to web design and I'm on a steep learning curve! As an artist (painter) by profession for some years I am probably the sort of guy fW is aimed at. All technical advice gratefully received!

Ah um er where is this in FWP 6, "(within the inspector palette as doc type 3.2."

Hi George in the latest version of this action you no longer need to set the document to 3.2 (FW6 has dropped it) all the best max

Sign In or Sign Up to comment.