About

Updates to browsers have made it impossible to save changes to this wiki or use its importing or exporting features. As a result of those changes, I’ve decided to stop working on Book on a Stick and remove the files that were available for download. If you are looking for a single file wiki that runs in your browser, you might want to keep an eye on Wiki on a Stick development and get new versions from there if and when they come out, or visit PVHL’s Woas (my wiki-on-a-stick fork) that works in modern browsers.

65 thoughts on “About

    • Done. I hope it helps the WoaS project to grow because it’s an absolutely brilliant piece of software with powerful adaptability that makes it so it can be useful almost anywhere. Using it for writing books is just one of probably billions of possibilities. :)

  1. [...] November 24, 2009 in Uncategorized With all the fuss about bundublog falling over, I didn’t have much time to post something important. Out of the blue, I got an email to say some of my wishes on the Ubuwiki wish list had been granted. Talk about ubuntu,. this is an example of community DIY. I really must get a page up for the project which is currently hosted on sourceforge. Maybe this is how it will happen. BTW littlegirl has her own WoaS project called Book-on-a-Stick. You can see her modifications here [...]

  2. This is such a great resource that you are providing and you give it away for free. I enjoy seeing websites that understand the value of providing a prime resource for free. I truly loved reading your post. Thanks!

  3. Just a question: What are the differences between WoaS and BoaS after all? Wouldn’t it better to provide some plugins for WoaS?

    • Good question! These are the differences between the current version of BoaS and previous versions of WoaS:

      Content
      – A diary utility.
      – A dynamic ToDo list.
      – Different CSS classes.
      – Folding content.
      – Footnotes.
      – Links for writers.
      – More extensive help pages.
      – Page listings without the header.
      – Spoilers.
      – Tooltips.
      – Word count utility.
      – Word frequency utility.
      Core modifications
      – A different theme, including different icons.
      – A function for special treatment of HTML list line-height.
      – A function for unusual HTML list types.
      – A modification of the content in the *About tables* pop-up in the editor.
      – A modification of the function for the Image prompt in the editor.
      – A modification of the setTag function to customize the prompt.
      – An editor help pop-up.
      – Completely different editor buttons.
      – Go to top button in the footer.
      – Many changes in the system pages as far as grammar, spelling, general wording, etc.
      – Menu buttons for default wiki features (hard-coded into the wiki but could be done in a page).
      – Separate options for fixed menu and fixed banner.
      Combination of core modifications and content
      – Footnotes.
      – Folds.

      Some of these differences have been turned into plug-ins for WoaS and are available here. Some cannot be made into plug-ins because not all of WoaS can be altered or edited with a plug-in.

      BoaS will soon be coming out with a new version now that the nowiki bugs in WoaS 0.12.0 are being worked out by a very kind and generous contributor. Once this happens, the list of differences will change. If you’d like, I can create a forum thread that lists the differences. :)

    • You’re welcome! PVHL is working on a BoaS-worthy version of his fixed version of WoaS, and it’s beautiful! It’s not quite done, but as soon as it is, I’ll do my best to quickly BoaSize it and get it released. :)

      • Hope you see this reply,

        Any news on this? I’ve got quite a bit of info in a BoaS instance and have recently started using a linux distro that has a webkit based browser as default, which I’d like to use – Chrome, actually. Firefox on Linux is experiencing many oddities. I had to unistall in fact…

        Cheers,

      • Chrome isn’t officially supported in the current version of BoaS because it’s based on an older version of WoaS. I still don’t know when the next version of BoaS is coming out, but as soon as I have a general idea, I’ll post something here. :)

        In the meantime, Chrome is supported in WoaS 0.12.0, but you must use the TiddlySaver.jar file that comes with the wiki in its zip file. Instructions for using the TiddlySaver.jar can be found on the [[Help::Requirements]] page in Book on a Stick or on the [[WoaS::Help::Requirements]] page in Wiki on a Stick. If you’re unable to open either of those because of the browser you’re using, let me know and I’ll put up an instruction page for them here.

        If you decide to use WoaS 0.12.0, I highly recommend making frequent backups of anything you keep in it since there are a few nasty bugs – at least one of which can wipe out the entire contents of the wiki irretrievably. Please use either the autosave.wsif plug-in or the versionedbackupsave.wsif plug-in (both by FBnil) from my WoaS plug-ins collection to protect your data.

      • Thanks for the help :-)

        To be honest, I’d prefer to stick with BoaS v0.9.3, knowing my data is safe.
        I’ve recently created the option of Firefox 3.6x via a virtualized XP instance on several of my machines – maybe I should just patiently wait for the BoaS update before using Chrome…

        Cheers,

      • As long as you heed the warning on the [[Special::Options]] page, your data should be safe with BoaS, but I still recommend making regular backups of the file for peace of mind. :)

        You might also be interested in what PVHL is doing. Find out about his project by going to the WoaS Files page and grabbing the README.creole file for a description and links. His Legacy file is going to be the base I use for the next version of BoaS. :)

      • mmm, I know that warning, but thanks for the reminder :-)

        In terms of backing up, can I simply import either autosave.wsif or versionedbackupsave.wsif from your plugins collection into your BoaS v0.9.3? I’ve not added any wsif files to date; a search for either produces no results.

        So Paul Levey is currently crawling through the code. That’s good news for us users, knowing both you and he are planning upgrades. Wow, thanks for your efforts! T’would be a sad day indeed for this great application to just fade away…

        Cheers,

      • Neither of those plug-ins will work in BoaS, but I might be able to modify them. I’ll see what I can do (or it will become a non-issue if the new version of BoaS comes out beforehand). Meanwhile I recommend backing the wiki up the old-fashioned way by keeping an updated copy of it somewhere (compressed into a zip file, perhaps), but at least it beats chiseling the backup onto a cave wall. :)

  4. I love BOAS!
    I found errors in the Help pages:

    – Topnote:

    “Utility” in the code [[Include::Utility::Topnote|TEXT]] should be “Template”.

    – Foldaway page:

    “Foldawaycontent” in the code [[Include::Template::Foldawaycontent|PAGE|NAME]] should be “Foldawaypage”.

    I also have a question:
    Is there a way to link on a page to an anchor on another page? Thank you.

    • I’m glad you love it! I love it, too. :)

      Thanks for letting me know about the errors! I’ll make sure they’re fixed in the new version.

      You can’t link to anchors in the current version of BoaS, but the good news is that you’ll be able to link to anchors on the current page and on other pages in the new version. :)

      • Errors again!
        “Add an embedded image” doesn’t work both “From the menu” and “From any page” in the 0.9.1 version, but “From any page” is fine in 0.9 version. I also tested “Add an embedded image” on WoaS, it worked pretty well.

        I like the folding feature, and I use it together with linked buttons to create a Tags menu to access all the tags I created, and it works great! BoaS is really amazing!

        BTW, is it possible to create drawing tools like those in LibreOffice? Except Onenote and Evernote, I can’t find what other note-taking applications can do both writing and drawing. If BoaS can do it, it must be powerful!

      • You’re right! “Add an embedded image” doesn’t work “From the menu”. That’s from a bug in an earlier version of WoaS, since BoaS isn’t yet based on the current version of WoaS (and won’t be until the current version is repaired). “Add an embedded image” works fine “From any page” in BoaS 0.9.1, though. :)

        I’m glad you like the folding! There will be more folding in the next version. :)

        For drawing tools, you might want to check with FBnil in the WoaS forums here. He had been working on something like that in his enhancement branch here.

      • “From any page” in BoaS 0.9.1 still doesn’t work on my pc. When I clicked on the embed button, it didn’t go. I am using Firefox 4 and tested BoaS on both XP and openSuse, also on safe-mode firefox, and they have the same problem. I tried it with IE. Clicking on the embed button did create an embeded page but it showed a red X without image. Do you believe it is because of the setting on my pc or the browsers?

        Here is the message on debug console, with Firefox, maybe you know what the reason is:

        Exception while attempting to load

        [Exception… “Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]” nsresult: “0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)” location: “JS frame :: file:///D:/Download/BookOnAStick/BookOnAStick-v0.9.1.htm :: :: line 5754″ data: no]

        Thanks for the info on drawing tools! I don’t have a background on IT and reading those discussions is a bit tough to me, but I would try.

      • Interesting! “From any page” works for me in BoaS 0.9.1 using Firefox 3.6.16. What I did was type this link to a nonexistent image in the Main Page:

        [[Include::Image::test]]

        I then clicked the link it created and used the embed interface to browse to an image on my computer. I inserted it into the page without a problem.

        I also typed this link to the alert.png image that’s embedded in the wiki by default:

        [[Include::Image::alert.png]]

        The alert.png image gets inserted into the Main Page without any problem.

        Is that the kind of thing you’re doing? If so, maybe it’s the version of Firefox you’re using. That version didn’t exist when BoaS 0.9.1 came out.

        Hopefully you won’t need an IT background to use the drawing feature, if he’s still got a version that will work in the wiki. Good luck, and let me know how it turns out! :)

      • Yes, it is FF4! I ran BoaS on FF3.6.16 portable and the embed “From any page” worked. FF4 even cannot do the ImportWSIF. I tried the ImportWSIF on FF3.6.16 portable and it popped up error alert windows, saying “WoaS unhandled error” but the debug console displayed “149/152 pages imported sucessfully”. Is that OK?

        I created a tree directory on the menu using the fold codes you posted on WoaS forum, and it looked pretty cool! However, if titles of pages are too long, they would be wrapped up and look a little crowded. So, is there a way not to show a full long title but shorten it with dots and tooltips? Or, maybe it is not a good idea to link all the pages onto the menu.

        I haven’t found out a clue about the drawing tool on the forum. Is that the svg stuff? Please forgive my lack of knowledge on that and I don’t know how to apply that to BoaS. The drawing tool on Foxit Reader is also good. I look forward to seeing something like that on BoaS. To visualize concepts, drawing tool is a must on a text editor, am I right?

        The folding feature is really good and it is worth to expand its usabilities. I tried the bluebox and found out that modifying the code in CSS can create all kinds of color box. It’s really exciting! Working together with scrapbook and zetro, I believe, BoaS can give users, at least me, lots of convenience. BoaS should grow bigger but not just a dream!

      • I’m glad to hear that “From any page” works for you in FF3.6.16. :)

        I’m not sure what will happen with the FF4 errors. :(

        If you got the WoaS unhandled error in BoaS when importing a WSIF file, then it could be that there is something about the WSIF file that isn’t compatible with the changes I’ve made to BoaS, especially if it’s a WoaS plug-in. It’s also possible that something was buggy about the WSIF interface in the version of WoaS that was used to make the most recent version of BoaS. Hopefully that will be ironed out in the next version.

        As far as the number of pages imported being different from the total possible number of pages, that can happen if the author of the WSIF file didn’t properly record the number of pages in the file, or when your settings make it impossible for the ImportWSIF interface to import all the pages.

        I created a tree directory on the menu using the fold codes you posted on WoaS forum, and it looked pretty cool! However, if titles of pages are too long, they would be wrapped up and look a little crowded. So, is there a way not to show a full long title but shorten it with dots and tooltips? Or, maybe it is not a good idea to link all the pages onto the menu.

        I’m sure there’s a way to shorten the page titles and replace what got cut off with dots, but I’m not yet good enough at coding to know how to do it. You could try asking in the WoaS forums if anyone knows how to do it. There are some pretty creative people in there. (:

        A quick way to add tooltips to anything is to use HTML acronym tags around any content you’d like to give a tooltip. Then put the tooltip in the title attribute of the tag. For example: <acronym title=”I AM A TOOLTIP”>CONTENT</acronym>

        Yes, the drawing tool I was talking about was FBnil’s svg thing. I’m not sure how to add that to BoaS either, but it could maybe be made into a plug-in, since the next version of BoaS will be able to use those. I’m not familiar with Foxit Reader, and I use Linux, so I won’t be trying it, sorry, but if you know of a JavaScript drawing program, I could take a look at it and see if there’s a way to add it.

        Bluebox is a lot of fun to play with. I’m glad you like it, and FBnil would be happy to hear you like it as well, since he designed it. :)

        I’m not familiar with Zetro. What is it?

        BoaS will definitely grow bigger as time goes by. Hopefully this next version will make it easier for everyone to expand the wiki the way they like it.

  5. I think the error with importing a WSIF file mainly comes from the old version of WoaS you use for BoaS. I tried the import in the latest version of WoaS on both FF4 and FF3.6.16, both importing finished perfect.

    Foldpage error: If a page folds another page containing “Foldpage” feature code, the page will come out with a right arrow at the end. It could be an error from the Foldpage template. Foldtext, Foldaway and “javascript:expanddiv” are all clean.

    For folding feature, it will be wonderful if it could fold part of a page.

    I will learn some html, javascrpt and css from now on. It’s fun! Thanks for your suggestion!

    Foxit Reader is a pdf reader, much lighter than Adobe Reader. I mean Zotero, not zetro, sorry about my English. At first I thought Zotero is good for me, but I tried it today and found I need something simpler.

    Firefox add-ons page used to have a SVG-Edit extension. I don’t use it because I find Inkscape is much better. Even so, I only use Inkscape to draw some straight lines, polygon lines, and squares or circles on a whiteboard. To draw those patterns on images, I use photoscape. So, you can see what I need is just some basic things. The current version of SVG-Edit is 2.5.1. Actually its features are good enough for some basic drawing if I don’t ask more, but it doesn’t draw on web pages. It says it is a javascript-driven svg editor and the code is open, and even can it be used in TiddlyWiki. If this one can be used on BoaS, Wow! Hope it will come true!

    SVG-Edit project is here: http://code.google.com/p/svg-edit/

    Bluebox is a gem! It makes vivid pages! Really thanks for all people who work hard on this wiki project! You people should make it better and make known to more people, just like Firefox.

    • Good to know that the ImportWSIF issue is resolved!

      Thanks for letting me know about the Foldpage error. I’ve made a note of it and will remove or debug it before the next release. As for folding part of a page, I’ll add that to the wish list of possible future features. :)

      I’m happy to hear that you’re going to learn some scripting. I look forward to the things you’re going to create/design. :)

      Thanks for the recommendation of SVG-Edit, but the code is licensed under Apache License 2.0 and the content is licensed under the Creative Commons 3.0 BY-SA license. Once the next version of BoaS is out, it will be able to use plug-ins. Maybe then someone could make a plug-in that uses SVG-Edit, but the licensing issue makes it so that it probably wouldn’t be suitable as a default part of the wiki.

      Thanks for all your praise. :)

      • I tested the Foldpage again, and more accuritely to say, the error occurs when two or more Foldpages are used in a chain of folding, and Foldtext, Foldaway and javascript:exoanddiv are all fine.

        I played BoaS these several days and re-edited the menu and main page to make them more personal and I am very happy with what I have done, so you can see why I praise all you people for BoaS and WoaS. I also have Wikidpad, piggydb and other outliners, but none of them can compare with the folding dynamic features of BoaS.

        I have already used it for my writing, and I believe I would keep using it. BoaS and WoaS are still in an early stage, and in later version, I believe one feature should be added, that is to add a way to get access to the “All pages” when it is in Edit status. Right now, when users need to get a page, they have to close the editor to do that. After they find it, then enter the editor again. That will be inconvenient if they need to look for many pages during their writing.

        Good luck!

      • Since Foldpage wasn’t originally designed to be chained, it’s possible there’s something I could tweak to get it to accept it. I’ll look into it for the next release. Also, folding is done a bit differently in the next release, so maybe this won’t be an issue at all, but I’ll keep in mind that you’d like to chain the folds and do tests on the folding that will be offered to hopefully make sure it can do it. :)

        I’m happy to hear that you’re enjoying customizing and working with your copies of the wikis! The next version of BoaS will offer the features currently available in WoaS 0.12.0, but hopefully without the bugs that the WoaS ones currently have. :)

        I don’t think an “All pages” listing will ever be possible while within the editor. The editor is sort of an isolation chamber that replaces the menu and main text area while you’re in it. I would think that if one were to make it possible to browse through the wiki pages while in the editor, the editor would have to be separated from the wiki in a pop-up. The problem with this would be that if you were to browse through the wiki itself while the editor was open in a separate window, the editor window would go into the background and could be forgotten. Then you could run into conflicts if you tried to open the same page in the editor a second time while the original edit winwow was still open. It’s also possible that you could have a page open in the edit window and forget about it. Then when you try to close down the wiki, it won’t close because it still has a window open.

        I suppose it could be designed to check for things like that and pop up alerts when they happen, but those can be annoying. I’m not yet advanced enough in my programming skills to be able to make the wiki do something like this, but luckily it’s open source, so anybody can change it. Maybe someone else will figure out how to get it to do this. :)

      • Actually I don’t have Foldpage to be chained at the moment and most likely am not going to do that way. I prefer things simple, but pages in a wiki have a chance to fold and to be folded. So, when pages are accumulated, a chain might be built up unconsciously.

        When I put in a Foldpage or Foldaway, I find that the folding will leave a line of empty space. If the Fold is inserted among words and sentenses, then it will make the line space different. However, the javascript:expanddiv feature works perfect.

        I used the javascript:expanddiv feature and Foldaway to customize the menu. I’ve made trees and sub-trees, tag system and sub-menu to open pages. They work pretty good. Also, I use the javascript:expanddiv feature and Foldaway (now I’ve found out they are the same, am I right?) on my main page and link brief notes to the items on the menu. This way I find it works efficiently to me. So I hope next release can keep the same feature of the javascript:expanddiv and Foldaway, otherwsie my menu will have lots of arrows, and all of them will point to Rome. Just a joke! :)

      • Hopefully anyone who creates a page and sees odd behavior will look the page over in the editor and see what might be the culprit, and if there are any inclusions, examine the included page in the editor as well. :)

        I’ll see what I can do about removing the white space above and/or below Foldpage and Foldaway (I don’t like when white space is added without my consent either, so I really should have caught that!), and I’ll also check the other folds to see if they need white space removed as well.

        The expanddiv function is only used in Foldtext and Foldtextinline. I was experimenting with various ways of folding. In looking at the code I can see that I even commented out previous ways of folding and replaced them with something new.

        If I replace the current folds with new ways of folding in the next version I’ll leave the existing folds in the wiki and add a comment to the folding help page that lets you know that those are now considered deprecated and will be done away with in future. That way you’ll have time to switch to the new way of doing folds. :)

      • I found that the expand can do all the folding – Foldtext, Foldpage, Foldaway and a chain of folding. If a template having all these features can be created, editing work will be much easier. Both the expand and expanddiv codes work on BoaS, but only the expand does the folding on WoaS.

      • I will take all of this into consideration when preparing the new version of BoaS (the base of which is still under development) so that it offers the best possible folding tools, but please be aware that BoaS will not be fully compatible with WoaS. If you have content in a WoaS file and wish to bring it into a BoaS file, you will most likely need to make a few changes to it because the links in BoaS are not all the same as they are in WoaS, the system pages are not identical to those in WoaS, and the layout is handled differently.

  6. Hi, thanks for your efforts in improving this software. I’m returning to it after a spree with Tiddlywiki. I have a question and wondered what happened to your Forum.
    Even if my question is better asked on the WOAS site, could I ask it here – yopur site is more current and active by comparison :-)

    I would like to turn of the promting after choosing to Cancell an Edit, thus saving time and effort, but I’m not sure where to find the code. Can you help?

    Cheers and regads,
    Darryl

    • Welcome back from TiddlyWiki! I removed the forum because of limited participation. More commenting was happening here. :)

      From what I hear, the WoaS forums are currently broken, but I can help. You didn’t way whether you’re using WoaS or BoaS, so I’ve included instructions for both.

      • BoaS:
        1. Open the wiki in a text editor (you may have to tell your text editor that it’s encoded with Western ISO-8859-15 – no idea why, but it’s what I had to do.
        2. Find this section:
          	if (!confirm("Are you sure you want to cancel this edit?"))
          		return;
          
        3. Replace it with this section:
          //	if (!confirm("Are you sure you want to cancel this edit?"))
          //		return;
          
        4. Save the file.
      • WoaS:

        1. Open the wiki in a text editor.
        2. Find this section:
          			if (!confirm(woas.i18n.CANCEL_EDITING))
          				return;
          
        3. Replace it with this section:
          //			if (!confirm(woas.i18n.CANCEL_EDITING))
          //				return;
          
        4. Save the file.
      • Many thanks, mostlylinux
        Did the trick!! Sorry, my bad – using BoaS.
        I *really* enjoy this implementation and hope all involved (nl you? :-)) continue to provide us with this outstanding product.

        The standard WoaS can be a bit arcane for a newish user, but you have taken the “how did they do that” away and made it much easier to get started. I’m not a book author, nevertheless find BoaS ideal to collect all my bits and bobs over the years in one place.

        Cheers for now,

      • It’s good to hear the tweak worked! :)

        My involvement has always been offering minor assistance on the WoaS project and then putting finishing touches on it and altering it somewhat to create BoaS. There are always others who contribute in one way or another, but I don’t have an official team.

        I’m so happy that you enjoy the BoaSized wiki. I really enjoy playing around with it, and have no intention of stopping. If anything, development should become easier and more fun the more I learn about JavaScript. :)

  7. Hi,

    I’ve been experimenting with using *oas (woas, ubuwiki and now boas) to provide a wiki I can use as a knowledge base wiki. What I need for this is the ability to launch local pdf and microsoft word documents from links in the wiki. Although I am a C++/C#/F# developer, I’m ashamed to admit that one thing I’m not familiar with is javascript and boas development.

    I did manage to hard-code some javascript to open a pdf when a specific page was entered but I need to do this from a link on the page instead – and this is where I came unstuck :+)

    I’m guessing a javascipt function would be able to add an icon, a description and a link which opens the document in a new window but I don’t know how to produce this and where it should live in boas. Also, I guess the ability to open Office documents would depend on the browser?

    Any help here would be deeply appreciated.

    Thanks

    • You can put a function in the [[Special::Edit Bootscript]] page so that it’s loaded when the wiki is loaded, or you can hard-code it into the wiki by editing the wiki with a text editor (you may have to tell your text editor that it’s encoded with Western ISO-8859-15 – no idea why yet) and putting it somewhere suitable. To find a good spot, do a search for Little Girl in your text editor and you’ll see where I’ve sprinkled a couple of functions without doing any harm that I know of. :)

      Adding an icon can be done by importing an image into the wiki. Ssee the instructions for Add an embedded image in the [[Help::Images]] page. You can then use the image as a link (see the instructions for Image as link in the [[Help::Links]] page) or use an include link ( [[Include::PAGE NAME]] ) to include the image next to a link to your function. If you do a search for javascript on the [[Help::Links]] page, you can see a couple of examples of how functions are used in links.

      I have no experience with opening Microsoft Office documents from a browser since I don’t use Windows, but I suppose Microsoft could tell you what the requirements are for those. It sounds like you’re well on your way, though, since you’ve already got some functioning JavaScript code to do the job.

      I’d be happy to play around with this with you (at least the PDF part) if you like. Feel free to use the Contact tab to send me an email if you want to fling some code back and forth. :)

  8. Been a long time woas user until I found BOAS! Really like the feel of it over woas (but appreciate all the work that went into woas – brilliant little file ;-))

    I’m getting a large amount of white space (10-15 blank lines maybe) whenever I embed an HTML table. Would you happen to know where in the code I could look to remove/prevent that?

    • I’m glad you’re enjoying BoaS – I like the feel of it, too. :)

      You can’t use CSS to take care of the white-space problem on HTML tables – at least I haven’t figured out a way. The cause is something in the base code of the wiki (possibly in the var reReapTables section, but it could be something somewhere else). The good news is that it won’t happen in the next major release of BoaS.

      In the meantime, you can put all the table elements onto one line, which is a visual mess and difficult to edit later, or you can add a backslash to the end of each line so that the wiki parser joins them when it renders the table.

  9. Hi, mostlylinux,
    Long time no speak :-)
    I’ve been using BOAS with Firefox for about a year now, lately as a pinned tab. The file is in Dropbox, so I always have it everwhere. Soooo useful.

    Just wondering if you are able to guess at when your BOAS will be editable in Google Chrome?

    Cheers,
    Darryl

    • I’m glad you like it! It’s an honor to have it pinned in your browser. :)

      The next version will be editable in Chrome, since it will be based on the woas-fix.html file. Have you tried that yet? It’s in the woas-0.12.0.zip file and is far more stable and reliable than WoaS 0.12.0.html. I’m waiting until the woas-fix.html file is finished, or mostly finished, and then will build BoaS 1.0 on that. Note that you’ll need to use the TiddlySaver.jar file with Chrome. See the [[WoaS::Help::Requirements]] page for how to use it.

      In the meanwhile I’m converting the WoaS macros and plug-ins so they’ll work in woas-fix.html, and may just write one big plug-in that BoaSizes it, if possible. :)

  10. Hi, mostlylinux,
    Long time no speak :-)
    I’ve been using BOAS with Firefox for about a year now, lately as a pinned tab. The file is in Dropbox, so I always have it everwhere. Soooo useful.

    I was kinda hoping for a release editable in Google Chrome – any news on that? Of course, I know you are very busy…

    Cheers,
    Darryl

    • I’m so glad that BoaS is useful for you. I store all sorts of information in various copies of it here there and everywhere. No news on the Chrome yet, but I hope to be addressing that at some point. :)

  11. I downloaded the woas-0.12.0.zip file as well as the tarball referred to in the woas-fix.html discussion.
    Both don’t allow edits to a page – I cuurently have Chrome 18.0.1025.151 installed on laptop running Linux.

    I’ll just wait for your “fixed” BOAS as my current v0.9.3, although only 705KB, is and has been rock steady. I make manual backups now and then, just in case.

    Cheers,

    • The development version says that Chrome Java saving should now be properly fixed, so when that one makes it into the zip file it should work for you. :)

      I’m glad you’re making backups, though, since the current version of BoaS isn’t based on woas-fix.html.

  12. I have recently started using Chrome much more. Any update on when we might see BoaS editable on Chrome natively? Currently I’m using a Firefox Tab plug-in to Chrome so I can edit my file.

    • I’m just now getting back to my computer after an unexpected, lengthy hiatus. I have no definite plans yet, but would like to continue working on BoaS, and will see what can be done to get it to work on Chrome at some point. :)

      • @ mostlylinux and parkerjnc

        For what it’s worth, I downloaded a copy of WOAS V0.12.0 which I’ve found id editable in Chrome version 27.0.1453.94 m.

        I’m not able to attach a screen dump here, but Chrome asks the following:
        “Java (TM) needs your permission to run,. ‘Run this time’ or ‘Always run on this site’
        Accepting the latter allows editing and saving of WOAS both on Linux or Windows.

        Cheers,
        Darryl

  13. Whenever I try to download BOAS I get this message:
    “The page you were viewing has expired. Please try your request again.”

    I tried on Chrome, FF, and Opera on two different computers/connections so it seems not to be on my side.

  14. I have been playing with BOAS again too, Love it, it is So handy and fun to create with.
    I just downloaded it to test after reading the comments above, and it downloaded fine for me.
    I’m using Iceweasel (Firefox) and Linux but the website @ app.box.com shouldn’t care which OS or browser is used? I wouldn’t think, but maybe there was a short term glitch at the site before.
    I tried (current version) @ : http://bookonastick.wordpress.com/download/

    • I’m not sure what causes the glitch, but they’re not the first persons to have had it. It’s either a Box issue or the WordPress link not working properly for whatever reason. Gremlins! (:

  15. I am saddened that progress in the name of security ahs broken saving in BOAS and So it seems the latest FF (24 and 25) have broken saves again .
    It is a really useful and fun program.

    • It’s the way of the future. I’m now using CherryTree and Mallard to store all the stuff I like to reference, and I’m leaning toward using Mallard for everything because it works hand in hand with Bazaar versioning and because it accepts typed in markup, which is how I prefer to do things. (:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s