![]() ![]() The attached screenshots tell the tale - one shows what a typical responsive script will do, as it desperately tries to keep everything within the viewport, and the other shows what my skin mod will do. I've done the coding for an option in Jupiter (the logical Gromit successor) that gives responsive priority to the image, and lets a vertical scrollbar show up if there's a boatload of text. ![]() I've been having a tinker, and am about 95% of the way there. Yes, it's a persuasive "use case" - something that it's not unreasonable for someone to be doing, but that most skins don't handle gracefully. It still works well for me and Jeff's Celestial Albums appear not to do as much as what GROMIT does now!Ī school panoramic photo split into 6 or 8 slides to make it fairly readable on small screens. I never really found the Chained Directories feature in GROMIT to be much of a problem, but that may be because my albums don't have many folders within folders! Anyway, some good may have come about with David now suggesting limiting to siblings only. I can think that it's advantage is that it can index for searching web pages that are not part of JAlbum. (It does not exactly mirror the image width!) However, I really like the inbuilt search feature.Īndre, thank you for your suggestion about FREEFIND. (I've got loads of existing text) I tested Tiger with one of my text heavy school panoramas and it hasn't lost its formatting and it produces a scrollable comments box.The size of which is a bit weird sometimes when the web page is resized. Thanks Jeff for pointing me towards the PREFORMAT feature on Tiger, without which, would have made Tiger a no-go skin. I've been playing around with Tiger Skin today and am fairly pleased with the result on a trial album. Thanks you everyone for all your advice and suggestions. I might even be persuaded to allow directory chaining in Jupiter - it really is just a matter of removing a few lines of code. Personally, I don't like having an image that I can't see in its entirety. On a typical laptop and with a landscape image, they end up being almost the same, but with a portrait mode image, they're quite different. Gromit could do either "width responsiveness," which would sometimes result in the need to scroll to see all of the image, or "image responsiveness," which would make sure the entire image fit in the viewport, but not the text. The question is which of the two modes to provide - they're very different "under the hood," so I'd provide only one. In other words, the page would still be responsive as far as the image itself is concerned, but they would let the caption text trigger a scrollbar when necessary. In Jupiter, I can fairly easily provide an album-wide option, along with a "just this image" option, to do the slide page responsiveness differently, so that images like these are given priority. None of my skins relies on a JSON file - hence, no searching. The only reasonable way to do it is in a JSON-driven skin, and Laza's skins that have that feature are all such beasts. In my Mercury and Jupiter skins, I let the slide page show a vertical scrollbar when the text pushes things too far, rather than shrink the image to the vanishing point. And things inevitably get ugly on a phone. You can keep making the image smaller, but you can't make the text smaller (it would become unreadable), so you eventually run out of room. Laza's skins seem to have no big problems dealing with long comments, but that's always tough in a responsive skin. He might have to check to see if there are already HTML break characters in the comment, and not add any if there are. Tricky as an after-the-fact change, however, since his skin users have probably already put in the breaks where they want them, so having the skin suddenly start adding its own could be problematic. Laza's skins do not convert text file newline characters into HTML break characters, alas. Putting in 4 to 7 into SEARCH SKIN comes up with:īut I'm unable to determine if criteria 1 to 3 are satisfied.Īny advice appreciated. ![]() (instead of Google Search on my own site home page) Otherwise - from the selectable features in Skin Browser:Ĩ. Allows a large or little amount of left-justified text in slide comments. Requirements (not able to select in the SEARCH FOR SKIN browser):ģ. Jupiter has been mentioned somewhere, but I don't think it allows CHAIN DIRECTORIES? (BTW - I dislike the new HTML Editor on existing text, because it gets completely messed up!) This was a fantastic advantage, so that would be an essential requirement. jGromit skin put in line breaks where needed without entering code. I have a huge amount of text rich Albums, so it is important for me that any new skin does not cause me a lot of re-editing text. It is no longer supported, so sadly, it may soon be time for a change. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |