Now basically I like the idea in order to keep a site more basic and cleaned up - just as a tool into another way of design-aspects. The implementing was even for me achievable but of course it was more “mechanical” than really “technical” cause styling is actually based on the delivered external .css.
From the freeway-architectal point, the content of the extruders are single pages that will be adopt by link to that page. So the basic freeway-page is kept simple and clean.
I wonder, what way could be gone to make it much more freeway-based? What has to be done to implement the css-styles in freeway (not the ESS-Actions, cause it doesn’t matter if you work internal or external).
And another point in here has to be remarked:
It’s JQuery and I got the strange feeling, that all funny and modern scripts like this not really harmonize with nearly all in-built or added actions, will mean, to experiment with this script could sometimes cause some strange collision with the other things you wan’t to achieve.
Hi Thomas,
Thanks for sharing.
I can think of three methods of Freeway integration that all offer
their own benefits;
Share the Freeway file you have and let users pick it apart to see
how it ticks,
Create a integration guide as a PDF or video that guides the user
through the process,
Create an action (or actions) that wrap the process up and offer it
in a Freeway-like fashion
Ultimately if you think that you (or anyone else) will need to add
these again to your Freeway sites then it is worth spending some time
streamlining the production process.
Do you have a Freeway file that we can look at and see just how you
managed to integrate the effect into your site?
You are correct in that jQuery can conflict with some of the other
JavaScript libraries (or actions that use these) but the code can be
modified to make sure that this doesn’t happen. The only downside to
mixing libraries like this is one of page size. If you add jQuery as
well as Scriptaculous and Prototype to a page you’ll start to see the
page size bloat.
Overall I like the effect and can think of several good uses for it
already.
Regards,
Tim.
Now basically I like the idea in order to keep a site more basic and
cleaned up - just as a tool into another way of design-aspects. The
implementing was even for me achievable but of course it was more
“mechanical” than really “technical” cause styling is actually based
on the delivered external .css.
From the freeway-architectal point, the content of the extruders are
single pages that will be adopt by link to that page. So the basic
freeway-page is kept simple and clean.
I wonder, what way could be gone to make it much more freeway-based?
What has to be done to implement the css-styles in freeway (not the
ESS-Actions, cause it doesn’t matter if you work internal or
external).
And another point in here has to be remarked:
It’s JQuery and I got the strange feeling, that all funny and modern
scripts like this not really harmonize with nearly all in-built or
added actions, will mean, to experiment with this script could
sometimes cause some strange collision with the other things you
wan’t to achieve.
Yes there are a few projects that I need to implement this, so I’d appreciate if you experts could have an eye on. And I think it could be interesting for a few people, too.
So - I’ll slip this version a bit down (images and stuff seems not to be necessary at this point) and create a link to download.
The problem of the integration is, that I sometimes do things like this more under the intuitive aspect, will mean the left hand does not know what the right one wants. So a description is hard enough at this point to achieve.
But if we figured out, what way it could go, and if I can plan each step, a screencast could be made.
I think the most important part now is to have a primary eye on the script itself and its problems with other actions in freeway - and in fact - I’m not able to do this.
In the next step it should be figured out on how to handle the external stylings into freeway itself.
The rest is to put predefined script snippets and paths to the scripts and upload them somewhere on the host.
So if you and all the others could have an eye on would be much more than valuable.
So I post the link here later after redesigned the freeway-file.
I’ve been seeing this used a lot lately for Twitter response fields. It is useful for the fact it pokes you in the eye and invites you to click on it no matter where you are on the page. I don’t think I would use it more than once on a page though. Kind of related to accordions in effect.
It’s including the original script and it would be nice, if you or someone else could have a look on it.
The way I did, is just stupid following the instructions and copied some code snippets into the page HTML-Markup, uploaded them via Upload Stuff onto the server. I also added some DIV’s (right flap was more than tricky to achieve) and gave them extended attributes.
Finally it worked, but it’s breaking a lot of Freeway-Actions (for example background-action) and I haven’t found out a way how to style the extruder flaps entirely in Freeway (what would be a charm, too).
I personally do have no idea on how to write actions and open spoken no idea on how to proper add extra styles that will be picked up by the script.
So I hope you’ll find the time to have a look on. If their could be a way to actionize or keep it closer to freeway-use, I finally promise a screencast (or a PDF guide), something that actually would not make much sense.
I’ve picked up on your extruder thread and really like what you’ve done on your site and would like to emulate similar on to a new site I’m developing.
The problem is I can’t quite get my head around how it works or where to start even.
My coding skills are very limited and use actions mainly as I’m more graphics based than coder?
thanks - well I agree that I have to declare a bit nearer how I did this, but haven’t had the time yet.
Now one thing first: Extruder was a found and I just tried to embed this in a freeway-doc. It should be declared once more, that I do not know what other actions will be influnced by this script or vice versa. If you plan a site including extruder, you should not plan to have web-yep (for example) on these pages this script will be involved.
So will mean: It’s just a try - but I would be happy if we could step through, and I would be happy if Tim (and the other cracks) could have an eye on it cause:
“I know nothing about coding as well :-)” I just try to reproduce by investigating code and try to rebuild this. Sometimes it works but most of time it fails.
These are the “basic requirements” to walk through and maybe by the help of all, it finally will work.
Sorry - but I have to stop here and have to review what I did and how I shall describe. One good thing to start is the freeway-file I shared on my site. Have a look on these things that are in (actions for example) and try to have a look on the items on the left side. Have a look on page ->extended, choose items and look if they have extended attributes and if yes what kind of.
Have a good night (and me I will have another “Rothaus Tannenzäpfle” my favoured german beer).