This effect is certainly achievable with Prototype/Scriptaculous, too, so you could have a completely “Action-safe” version of this effect without any issue. If this is the look you want, I can probably code this up in P/S very easily.
Walter
On Sep 2, 2012, at 8:10 PM, DeltaDave wrote:
I would make sure that the client is happy with the navigation before committing to the jQuery solution. Another thing to consider is how to link your nav to other possible effects that you might want to use - like rollover triggers - as this will have to be a hand coded route too.
Once the nav is agreed then you will need to discuss with the client what sort of gallery they want - at that point we can probably point you in the direction of a suitable jQuery option.
But you are getting to the stage where a lot of FW’s actions are going to be out of your reach on this project if this navigation is going to appear on every page.
A better (than me) coder/js guru would/should be able to translate that jQuery code into Script/Protaculous based stuff but there is really only 1 man here that has that experience - and he is a busy man!
Just make sure that you are not digging yourself too deep a hole.
I would want a way to do this with the least possible conflicts with other actions and if this is what would be needed that would be best. There will be a gallery needed, but as a carousel rather than show/hide target layer. I’m very keen to learn new ways and actions but as mentioned by Dave I don’t want to dig any holes! Walter would there be a cost for you to do this and if so what would it be?
The actions pledge is front of mind now!
Elizabeth
On 03/09/2012, at 10:03 AM, Walter Lee Davis wrote:
This effect is certainly achievable with Prototype/Scriptaculous, too, so you could have a completely “Action-safe” version of this effect without any issue. If this is the look you want, I can probably code this up in P/S very easily.
Walter
On Sep 2, 2012, at 8:10 PM, DeltaDave wrote:
I would make sure that the client is happy with the navigation before committing to the jQuery solution. Another thing to consider is how to link your nav to other possible effects that you might want to use - like rollover triggers - as this will have to be a hand coded route too.
Once the nav is agreed then you will need to discuss with the client what sort of gallery they want - at that point we can probably point you in the direction of a suitable jQuery option.
But you are getting to the stage where a lot of FW’s actions are going to be out of your reach on this project if this navigation is going to appear on every page.
A better (than me) coder/js guru would/should be able to translate that jQuery code into Script/Protaculous based stuff but there is really only 1 man here that has that experience - and he is a busy man!
Just make sure that you are not digging yourself too deep a hole.
Part of the genesis for building a new ActionsForge came out of something related to this.
I was very frustrated one day with how painful the current ActionsForge is for developers. Upload a single file containing a bunch of Actions (as in a bundle Action or a single-file Action that contains several logical Actions) and you have to click-click-click-type-type-type-choose-choose-choose through a form for each version of each Action. You also have to remember what version number you assigned to each Action in the bundle. So I wrote a little Ruby script that could read an Action and parse out all of the versions within it. The current site is coded in PHP, so I can’t use this script there directly, and my lightbulb went off that I should rewrite the entire site in Ruby on Rails, just so I could fix this one little pain-point and make the site more usable for the developers.
This same technique could read the JavaScript inside the individual Actions, and check at which point they run their code. Each Action writer can choose when in the publish cycle they want their Action to fire. These points in time coincide with the part of the page code that Freeway is written, so they have very similar names to the “slots” in the Page / HTML Markup dialog:
fwBeforeStartHTML
fwAfterStartHTML
fwBeforeStartHead
fwAfterStartHead
fwBeforeEndHead
fwAfterEndHead
etc.
If two Actions fire at the same “slot” in the publishing process, one may be changing something that the other relies on. I say may because the order in which they will run is (I am guessing) defined by the order in which they were added to the page or element. In practice, the order seems random. If they fire at different slots, then these conflicts are easier to deduce. Simply changing the slot won’t magically fix every conflict, but having that information available in the Forge might make it easier to parse out what’s happening. Having a more robust comment and tag system would certainly allow the community to collaborate on documenting these Actions and their interdependencies.
Walter
PS: If you want to try this out, here’s the script.
On Sep 3, 2012, at 9:33 AM, okn wrote:
Hi,
My suggestion for the new Actions site (Walter) would be exactly this, an (incl. visual) description of Actions which conflict with each other.
Right now I seem to be a victim of such Action conflicts on my site.
/ Omar
::: Communication to improve civilisation :::
s_ip
On 3 sep 2012, at 02:51, Elizabeth email@hidden wrote:
with the least possible conflicts with other Actions
If you look at the extra styles I put in my example document, you’ll see that I removed the bullets a different way. Freeway makes the list into a slightly broken definition list when you remove bullets – that tag is a dl instead of a ul.
My style #item1 li removes the bullets. The attribute is in the Extended dialog:
list-style-type: none
Rename this style to match the name of your HTML box as reported in the Title field of the Inspector.
Walter
On Sep 3, 2012, at 9:03 PM, Elizabeth wrote:
When I try to remove the bullets and set it up as a unbulleted in the inspector palette it removes the functionality. Is there another way to do this?
Elizabeth
On 04/09/2012, at 1:24 AM, Walter Lee Davis wrote:
Thanks Walter I’ve got it working without the bullet points, black on white (client request) and looks very smart. How about changing the colours of the visited links? I need to keep things simple to do as when I’ve tried making some changes it through the whole system out and I had to start again.
Elizabeth
On 04/09/2012, at 10:45 AM, Walter Lee Davis wrote:
If you look at the extra styles I put in my example document, you’ll see that I removed the bullets a different way. Freeway makes the list into a slightly broken definition list when you remove bullets – that tag is a dl instead of a ul.
My style #item1 li removes the bullets. The attribute is in the Extended dialog:
list-style-type: none
Rename this style to match the name of your HTML box as reported in the Title field of the Inspector.
Walter
On Sep 3, 2012, at 9:03 PM, Elizabeth wrote:
When I try to remove the bullets and set it up as a unbulleted in the inspector palette it removes the functionality. Is there another way to do this?
Elizabeth
On 04/09/2012, at 1:24 AM, Walter Lee Davis wrote:
You can change the visited color in the normal Freeway manner. Click on the box containing the links, open the Style tab of the Inspector, open the Links segment, and style away. I usually do not style the visited any different than the link in a navigation element – I think of these as utility links that a visitor will press over and over as they interact with the site/application. Content links I do style so that a visitor can see what they’ve already read, but top-level navigation rarely contains links to the final leaf of the content tree.
Walter
On Sep 3, 2012, at 10:54 PM, Elizabeth wrote:
Thanks Walter I’ve got it working without the bullet points, black on white (client request) and looks very smart. How about changing the colours of the visited links? I need to keep things simple to do as when I’ve tried making some changes it through the whole system out and I had to start again.
Elizabeth
On 04/09/2012, at 10:45 AM, Walter Lee Davis wrote:
If you look at the extra styles I put in my example document, you’ll see that I removed the bullets a different way. Freeway makes the list into a slightly broken definition list when you remove bullets – that tag is a dl instead of a ul.
My style #item1 li removes the bullets. The attribute is in the Extended dialog:
list-style-type: none
Rename this style to match the name of your HTML box as reported in the Title field of the Inspector.
Walter
On Sep 3, 2012, at 9:03 PM, Elizabeth wrote:
When I try to remove the bullets and set it up as a unbulleted in the inspector palette it removes the functionality. Is there another way to do this?
Elizabeth
On 04/09/2012, at 1:24 AM, Walter Lee Davis wrote:
Is it possible to have this sliding navigation work with as a rollover than having to click the menu name, i.e. About, Home, etc?
Elizabeth
On 04/09/2012, at 9:47 PM, Walter Lee Davis wrote:
You can change the visited color in the normal Freeway manner. Click on the box containing the links, open the Style tab of the Inspector, open the Links segment, and style away. I usually do not style the visited any different than the link in a navigation element – I think of these as utility links that a visitor will press over and over as they interact with the site/application. Content links I do style so that a visitor can see what they’ve already read, but top-level navigation rarely contains links to the final leaf of the content tree.
Walter
On Sep 3, 2012, at 10:54 PM, Elizabeth wrote:
Thanks Walter I’ve got it working without the bullet points, black on white (client request) and looks very smart. How about changing the colours of the visited links? I need to keep things simple to do as when I’ve tried making some changes it through the whole system out and I had to start again.
Elizabeth
On 04/09/2012, at 10:45 AM, Walter Lee Davis wrote:
If you look at the extra styles I put in my example document, you’ll see that I removed the bullets a different way. Freeway makes the list into a slightly broken definition list when you remove bullets – that tag is a dl instead of a ul.
My style #item1 li removes the bullets. The attribute is in the Extended dialog:
list-style-type: none
Rename this style to match the name of your HTML box as reported in the Title field of the Inspector.
Walter
On Sep 3, 2012, at 9:03 PM, Elizabeth wrote:
When I try to remove the bullets and set it up as a unbulleted in the inspector palette it removes the functionality. Is there another way to do this?
Elizabeth
On 04/09/2012, at 1:24 AM, Walter Lee Davis wrote:
Brilliant! Both solutions brilliant! Walter’s is straightforward and clean. I like Todd’s bouncy motion, but the bounce should be from right to left: the bounce makes the linktext move left, not indent.
And I like your name. I’m not sure why but the Bucky’s I’ve known were
always the most good-humored and affable people in the room.
Todd
Bucky Edgett wrote:
Brilliant! Both solutions brilliant! Walter’s is straightforward and clean. I like Todd’s bouncy motion, but the bounce should be from right to left: the bounce makes the linktext move left, not indent.
I just tried it here, and it did work – to a point – but it became difficult to interact with, because the slightest move out of the current section and into the next would cause the current section to animate closed. There needs to be some timers on this or something, so the effect only fires if you hover long enough in a certain area. I’m not sure I like this design in terms of interaction and content discovery. Did you try the accordion effect?
Walter
On Sep 12, 2012, at 7:06 AM, Elizabeth wrote:
Walter,
When I made that change the menu expanded and is not clickable.
cheers
Elizabeth
On 11/09/2012, at 10:59 AM, Walter Lee Davis wrote:
Sure. Change the word ‘click’ on line 4 of the top Function Body dialog to ‘mouseenter’.
Walter
On Sep 10, 2012, at 8:31 PM, Elizabeth wrote:
Is it possible to have this sliding navigation work with as a rollover than having to click the menu name, i.e. About, Home, etc?
Personally I don’t mind the effect, but I’ll try Accordion too. The client who wants this wants a minimalistic look and has very specific ideas.
Elizabeth
On 12/09/2012, at 8:53 PM, Walter Lee Davis wrote:
I just tried it here, and it did work – to a point – but it became difficult to interact with, because the slightest move out of the current section and into the next would cause the current section to animate closed. There needs to be some timers on this or something, so the effect only fires if you hover long enough in a certain area. I’m not sure I like this design in terms of interaction and content discovery. Did you try the accordion effect?
Walter
On Sep 12, 2012, at 7:06 AM, Elizabeth wrote:
Walter,
When I made that change the menu expanded and is not clickable.
cheers
Elizabeth
On 11/09/2012, at 10:59 AM, Walter Lee Davis wrote:
Sure. Change the word ‘click’ on line 4 of the top Function Body dialog to ‘mouseenter’.
Walter
On Sep 10, 2012, at 8:31 PM, Elizabeth wrote:
Is it possible to have this sliding navigation work with as a rollover than having to click the menu name, i.e. About, Home, etc?