On Fri, Oct 16, 2009 at 3:21 AM, The Editor <[email protected]> wrote: > > On Fri, Oct 16, 2009 at 6:11 AM, Kevin <[email protected]> wrote: > > It would be nice if you could have a link to an image that does not > display > > the image, but allows you to click on it to view it. > > Sure, just use regular links. Try something like this: > > [[{fieldurl}/files/data-sword.jpg]] > > If you have a suggested syntax to shorten this, I'm open. For example: > > [[img:data-sword.jpg]] >
will have to play with it. I think the issue with first example is that it is rather verbose and the end user doesn't know where the images are actually stored. > Would be nice to be able to integrate Lytebox as well.... Unlike lightbox2 > > which is basically limited to images, lytebox can be used for any > content, > > not just images. > > What would you need to integrate it? Probably easy if you can specify > the requirements. > In the head section of the page you are going to use it on you need to include: <script type="text/javascript" language="javascript" src="lytebox.js"></script> <link rel="stylesheet" href="lytebox.css" type="text/css" media="screen" /> The style sheet provides the look and feel of lytebox when you use it. For any link you want to use it with, you add basically 3 elements: The indicator that the javascript looks for: rel="lyteframe" or they now have rel="lyteshow" Configuration info on how to configure what you are displaying... rev="width: 650px; height: 260px; scrolling: no;" Finally, a title that gets displayed on the title section of the screen when it is clicked like: title="station001.png" What I normally do is have a directory in the virtual host that will be using it called lytebox which contains the js and the style (including images it uses). Then when I use the javascript, it defaults to using that directory for all that it needs by referring to it as /lytebox Will make a separate topic on this when I start to play. > Looks like you just add two lines to your skin and use the rel tag. > Should be easy enough... > > > Still working on embeding a flash image slideshow package though I have > not > > done much since the initial try. > > Make sure you are using a code.embed. It makes it very easy to work > with code scripts like javascript or whatever. Takes snippets which is > very nice for making configurable settings. Holler if you need help. > Most likely will bundle up a zip file with a real example of it in action. I think my issue is with the code.embed file... Will be trying that again most likely tonight. Will also make a separate topic on it. I'm finding out a lot of things with having end users use the stuff... My "how to use" document is getting larger and larger on a daily basis when I actually have time to work on it (it is way behind). I also have to have 2 versions of the document. One for work which is a very specific wiki configuration with special action pages to make using the system easier. And a second which is more generic about how the Wiki is used, and how to do those things. Both are output into PDF format so they can print it. Found many users can't deal with multiple tabs in their browser with one on the page they are working on, and the other on a help screen. Plan on making a markup example sheet too which would be laminated for reference purposes, would use it myself for some of the BW syntax stuff. I'm always scrambling to find common code examples of things common things that I want to use when I go to use them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
