Like I said, I am trying to achieve something “different.” And sometimes that turns out to be very difficult or impossible. But as you read in that thread Page Shadow Woes thread, I did achieve most of what I set out to achieve via the RPL action. I see you did achieve that too, in part. Your test page works fine in modern browsers, and I am well aware that a straight inline layout can achieve that:
But if you read through that entire thread on my Page Shadow Woes, you will see that the heart of what I am trying to achieve is OLD BROWSER COMPATIBILITY too:
As such, if you open your inline layout test page in IE8 (which is the newest version of IE you can run on the still-widely-used WindowsXP OS), you will see there is no shadow at all. To remedy that, I use PIE.htc. But PIE.htc cannot be used on a server that is not my own, such as Atomz Search. In such a case, PIE.js would need to be used, but I’ve not found out how to get that to work reliably.
Nevertheless, for the sake of comparing your inline layout with the failed inline layout I made previously, would you might updating your “inline-layout-uber-alles” page by adding a link to the original Freeway document for that page?
Also, I see your use of “html5shiv.js”. Does this mean you must use HTML5 elements to get your layout to work properly? (Again, I am pondering older browser compatibility.)
Thomas, If you upload your Search Results page code to Atomz and find it works perfectly in IE6/7/8, I would be interested in seeing how you implemented PIE.js.
I can get PIE.htc to work fine from my own server, but I’ve never been able to get PIE.js to work on my Atomz Search Results page, even though I hacked into Walter’s CSS3 Corners action and tried to mimic his PIE.js implementation.
it seems that I’m way too dumb (or even drunken) to make this all working.
If I add a search feature to the above example, it shoots me to all but not to the search-template I created. I have to review this maybe tomorrow morning.
However I’m pretty sure that it’ll work. But before confirming anything I’d like to double-check.
You cannot just generate the HTML from Freeway and then copy and paste it into your Atomz template space. If you do that, there will be a lot of broken links, due to the fact that Freeway creates lots of relative links. So I have to do a lot of manual labor in TextWrangler to fondle my Freeway generated code into submission.
You can have a look at my Atomz search results page right now, if you like. Just go to my site, at a search term in the bottom left of the page, and then view the source of the search results page that appears:
The “show” checkbox is a red herring. It is the thing that tripped me up.
Frankly, I am not a fan of condescension. There are a number of people on this forum who make huge contributions and who are willing to help with even small things. They do this in a professional fashion and it is greatly appreciated by the rest of us.
Regarding the “big deal”: When you have a page that is displaying at a width of 2,000+ pixels, you can wind up with a lot of empty space. Dealing with this is a legitimate concern.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
I have to dig further.