There is a rendering bug in the Google Chrome browser that makes Ryuzine nearly unusable causing pages to display in blocks with some parts missing, some parts of the pages are transparent, and pieces of the User Interface are missing.
Whatever is causing it appears to only be affecting a very, very small number of websites and webapps, Ryuzine being one of them. The bug has been present in Chrome for at least the last 10 versions. It’s probably safe to say Google is never going to fix it. The problem *only* exists in Chrome and the “blink” based Opera browser. IE, Edge, Firefox, and Safari all render Ryuzine without issues. However, Chrome users represent a not insignificant number of people on the Internet, so at this time we are recommending turning some Ryuzine features OFF in order to better accommodate them.
Our best guess at this point is that layering too many CSS effects on top of each other triggers the problem, as disabling certain effects seems to minimize the problem or make it go away entirely.
RECOMMENDED FEATURES TO DISABLE
iScroll – there is an issue with iScroll being “sticky” and for left/right mouse clicks to have become reversed after a recent Chrome update.
A number of other issues with iScroll have also arisen in recent browsers. Until these are addressed you should disable it in your publications.
In your static Ryuzine publication “Config File” remove those two Add-Ons from the ones being loaded. In Ryuzine Press you can do this from the Ryuzine Press –> Options –> Add-Ons section, simply uncheck iScroll in the list and Save the settings.
Note: iScroll is a third-party script created by Matteo Spinelli and maintained by cubiq.org. Ryuzine simply supports iScroll integration. Ryu Maru is not involved in the development of iScroll, and the iScroll developers are not involved in Ryuzine development.
If you still notice problems with Ryuzine rendering, also consider disabling:
3D Page Turns
Depth Effects – the added layer of CSS shadows makes the Chrome rendering problem worse.
Ryuzine Version 1.1 is in the works and will completely change how the pages are handled, reducing the number of layered CSS effects, which will hopefully address this problem once and for all. Until then, please use the work-around above or inform your visitors they should turn off those features themselves after loading your Ryuzine publications.
“When will the next version of Ryuzine be released?”
This is a question that has come up a couple of times recently, especially from those who’ve noted that none of the files on GitHub have been updated since August or September of 2015.
Well, the simple answer is, “when it’s necessary.”
We don’t follow the software development idea of “release early, release often.” Ryuzine updates have historically been driven by updates to the web browsers in which it runs, either to fix something the browser update broke or to take advantage of a new browser feature. Since the release of Ryuzine 1.0 we haven’t become aware of any browser updates breaking the webapps, nor have any “killer” features been introduced that we think Ryuzine should take advantage of.
Furthermore, Ryuzine 1.0 heavily modularized the webapps, with more formerly integrated features now made optional in add-ons. The flexibility of the Add-Ons API would allow the webapps to utilize new browser features without requiring the core code to be updated.
There is an issue being experienced by some users of Chrome on Mac OS X when viewing a Ryuzine publication. What happens is the publication displays with glitchy graphics and any attempt to interact with it will cause the entire screen to glitch and the system to freeze, requiring a hard reset.
This is a known, recurring bug in Google Chrome involving hardware acceleration on some versions of Mac OS X, beginning with Mavericks. Note that this is not a problem with Ryuzine or exclusive to viewing Ryuzine publications. Other hardware accelerated web content can also trigger this problem.
Here is the work-around to prevent it from happening in the future:
Type “chrome://settings/” in your browser’s address bar.
Scroll to the bottom and click “Advanced Settings” to expand it.
Find the “System” section and UNCHECK the “Use hardware acceleration when available” if it was already checked or CHECK it if it wasn’t (in other words try it both ways).
Restart Google Chrome
Return to the Ryuzine that crashed your system, it should no longer cause screen freezing.
However, the display of the Ryuzine publication may still be very blocky/glitchy! This has also been observed in Google Chrome for Android. Here’s how to fix that:
Open the “Options” panel and look for “Depth FX” in the Add-Ons section.
Make sure the switch is set to “OFF”
If it’s still glitchy turn “Page Shadows” off as well.
If it’s still glitchy turn “3D Page Turns” off too.
The absolute last ditch effort is to turn off “Page Animations” as well.
You may need to change these settings for multiple publications if they are on different domain servers.
Music legend Prince sadly passed away yesterday. At the time of this writing an autopsy has been performed but a cause of death has not been made public, all we know for sure is he was found unresponsive in an elevator and couldn’t be resuscitated. Around the world landmarks like the Eiffel Tower, Niagara Falls, the Empire State Building, as well as many peoples’ social media profiles, are being redressed in Prince’s signature color: PURPLE. Ryu Maru is temporarily going purple as well.
Ryu Maru is headquartered in the Minneapolis-St. Paul area of Minnesota. Prince Rogers Nelson (June 7, 1958 – April 21, 2016) was from Minnesota, and though such a huge star who literally could’ve lived and worked anywhere, he chose to live here and he chose to build his studio here. This is where he helped create the “Minneapolis Sound” in the 1980’s and solidified Minnesota’s place on the musical map. He then spent the decades after not only on his own art but nurturing other artists, writing songs for them, producing them, and giving many of them exposure at parties he’d occasionally hold at his studio estate named “Paisley Park.”
Unless you were living under a rock in the 1980s you likely remember when his landmark “Purple Rain” hit, but it’s all too easy to forget just how HUGE a hit it was. At one point he had the top album, top single, and top movie in America all at the same time! He was the first artist to ever achieve such success. “First Avenue,” the club in Minneapolis, is in many ways a historic venue because of Prince, having gained world-wide notoriety in the film “Purple Rain,” but it wasn’t just a movie shooting location – Prince actually performed there many, many times (however, despite popular misconceptions, he didn’t actually own the place).
Comic book fans will remember his amazing soundtrack to Tim Burton’s 1989 “Batman” film, fittingly titled simply “Batman.” The scene with Jack Nicholson as “The Joker” defacing famous artworks wouldn’t be the same without Prince’s music blasting from the very 80’s “boom box” of a henchman character, incidentally, named “Prince.”
However, Prince’s music video for the song “Partyman,” in which he appears as “The Joker” himself, in many ways outdoes Nicholson’s performance in the movie. (You may want to enjoy that video above before it gets pulled, Prince was notoriously protective of his work online and there’s no reason to believe his Estate will be any less so after his death).
He later performed what many consider one of the best Super Bowl half-time shows ever, in the middle of a Miami downpour. Where other artists may have cancelled the show or waited for the rain to stop, Prince reportedly said “can you make it rain harder?” When he performed he was always “all in” and many music fans agree he was arguably the best live musician of their lifetime.
He never forgot his roots, never thought he was so important he had to travel everywhere with security or an entourage (in fact the day before his death he was seen by himself riding his bike near his home on a trip to the drug store), and he never acted like he was too big to encourage the talent of others.
But Prince WAS a “big deal” to many people, especially here in Minnesota – not just because he was a rockstar, but because he was one of us, he chose to remain one of us. You couldn’t grow up here or live here without knowing who Prince was, or without hearing at least some of his music. When the Minnesota Twins baseball team’s new stadium opened they played Prince’s “Let’s Go Crazy” after every home run. It’s a tradition for veteran players on the team to make sure rookies know all the lyrics to “Little Red Corvette.” In 2010 the Minnesota Vikings football team streamed “Purple and Gold” on their website, it was a “fight-song” Prince wrote to support his local team in the NFL playoffs. That same year he let 89.3 “The Current” premiere his new single “Cause and Effect” as a gesture of support for independent radio, as the station is part of Minnesota Public Radio. According to disc jockey Mary Lucia the station would occasionally get calls from Prince asking what artists he should try to book for his next Paisley Park party? Prince performed multiple times at the radio station’s annual “Birthday Party” held, of course, at First Avenue. But Prince was also enigmatic, somewhat reclusive, very private, and had this “magical” air about him, possibly best summed up when he dubbed himself “The Purple Yoda” in the lyrics to “Laydown.”
It’s fitting that his actual given name was “Prince” because he was regarded as “Rock Royalty” in Minnesota, and obviously not just in his home state – as the tributes to him from around the globe attest. He will be missed, though perhaps nowhere more deeply than here in the place he called “home.”
When Ryuzine Writer 1.0 was released the “Maximize/Minimize Editor” button was removed from the toolbar. This was like the “Fullscreen” or “Distraction Free” modes in various word processors. It was removed because there were some reflow errors when you’d pop out of that mode that require you to resize the browser window or hide/unhide the sidebars. Rather than requires people to do this (and know this) the problematic button was removed.
We didn’t actually remove it from the program entirely, just disabled it. So if you liked it and want it back it’s fairly easy to re-enable it. It’s actually a Xinha module and you can re-enable it by finding the file in:
That “popupeditor” will add back the Fullscreen button. It will be available in both WYSIWYG and HTML Editor modes. To return from Fullscreen mode press the Restore button. However, the Editor workspace may be squished into a narrow band across the center of the window. If that happens Toggle Sidebars off/on or resize the browser window.
Note that the Sidebars no longer automatically toggle off/on when you (respectively) enter/exit Fullscreen mode as they did in earlier versions of Ryuzine Writer.
It has been a long time in the making, but Ryuzine 1.0 is finally HERE! Not only is is practically a complete rewrite of all the Ryuzine apps, they are now completely OPEN SOURCE and FREE for personal and commercial use.
This massive update has been in the works since February 2014 and fixed or changed so many things we decided to just skip over a bunch of “beta” versions and jump right to version 1.0 – in total there were nearly 100 changes to the three Ryuzine webapps and the Ryuzine Press plugin. For more details make sure to check out the individual product pages:
The biggest changes came to our Ryuzine Writer authoring webapp bringing it more in line with the features you’d expect from a page layout program. Not only is there better handling of styles and stylesheets, the new “Page Manager” makes it easy to add, delete, and rearrange the pages of your publications. The “RackBuilder” can also now preview newsstand catalogs in the Simulator, the Simulator has been updated with profiles for newer, popular devices, and when everything looks the way you want the “Package Builder” has more and smarter options than every before.
The Ryuzine Press plugin has also seen some improvements that make it easier than ever to turn curated blog posts into engaging Ryuzine Press Edition publications. The plugin has also been updated and tested with WordPress 4.3. The Ryuzine Reader and Ryuzine Rack webapps are now bundled with the Ryuzine Press plugin download from our website – you are no longer required to do a separate installation of the webapps.
Publishers can learn all about how to use either the stand-alone Ryuzine Writer or the Ryuzine Press plugin by reading the manuals – which were written WITH their respective programs and presented in Ryuzine format:
All of the Ryuzine apps now have a much simpler user-interface that no longer requires users to “slide” through multiple toolbars to get to the button they want. Those buttons all now use an “icon font” instead of images for crisp display regardless of the device resolution. Ryuzine Reader has better swipe detection and the “Page Slider” has also been improved.
Updated Phone UI Nav Bar
Ryuzine Rack with custom theme and branding.
All the changes to the User Interface required rewriting the existing themes and creating new ones. The “Urban” Windowsand “Mobile Fruit” iOS themes got much-needed updates, and Android gets the new “Paperbot” theme. Some of the older “Platform Themes” have been dropped since they not only looked outdated but few people even use those devices anymore.
Ryuzine Writer also now gets its own themes and theme creators can choose whether or not they want to support Writer with their themes or not. Moving the Writer styles into their own stylesheet allows the Reader/Rack themes to be simpler and the smaller files load and render more quickly than the old themes did.
The theme system now also supports creating “child themes” that build upon another theme, so you don’t have to write styles for everything in your custom themes.
New Add-On API
In the beta versions only Ryuzine Writer had optional add-ons. In version 1.0 the Add-Ons API has been completely rewritten and is now part of both Ryuzine Reader and Ryuzine Rack too! Features that were previously “baked in” have been broken out into optional add-ons and it’s never been easier to extend and customize Ryuzine.
Free & Open Source
One of the biggest changes to Ryuzine is that now everything is completely open source. Ryuzine Reader, Writer, and Rack are released under the MPL 2.0 license, Ryuzine Press is under a GPL 3.0 license. All the code is available for developers in our GitHub Repository. Non-Developers can continue downloading preconfigured, bundled versions from our website.
Our first “Sample Magazine” was released with Ryuzine back in 2011, so with the launch of version 1.0 it was overdue for an update! This NEW “Sample Magazine” is not only designed to inspire ideas and show off what is possible with Ryuzine, it also has real articles for you to read. The old one was mostly just a demonstration of layout techniques with no actual articles.
If you’re interested in publishing your own digital magazines in Ryuzine format you can download the Ryuzine Publisher Distribution Kit, which contains all of the source files used to create this sample publication. You can open it up in Ryuzine Writer, play with it, and really see how it went together. Not sure you’re ready to download? Try out the ONLINE DEMO instead 😉
This post is to reassure you that we haven’t forgotten about the promised major update to the Ryuzine webapps – in fact they are well on their way for a release sometime later in 2015! Instead of releasing the incremental changes this upcoming release will jump right to version 1.0!
Above you can see the app icons have also undergone a visual overhaul, but the webapps themselves are all undergoing massive rewrites – with so many changes and new features the change-log already goes on for pages. What sort of changes? Well, for starters the User Interfaces have all undergone a lot of simplification.
User Interface Updated
You’ll no longer need to hit the “More” and “Less” buttons to slide controls left and right – all the buttons are now presented on one Navigation Bar:
Updated Phone UI Nav Bar
Behind that “Share” button is also a completely rewritten social media sharing widget, and in addition to still being able to drop in your own widget the third-party “Add-Ons” API from Ryuzine Writer has been completely rewritten and will also available in both Ryuzine Reader and Ryuzine Rack. That means adding your own custom dialogs and panels, but previously built-in features like the “Lightbox” are also going to be broken out into optional add-ons, making it easier for third-party developers to expand or replace them.
Page Manager & More
One of the biggest changes coming to Ryuzine Writer is the new “Page Manager!” Here’s a look at it in action:
“Page Manager” panel in Ryuzine Writer’s Editor
Professional page layout programs used in the print media industry allow the designer to easily see how their pages lay out in relation to one another, and easily add/delete and drag-to-reorder the pages. All of those features will be available in the new Page Manager panel, as well as the ability to change the size of the page thumbnails, show individual or facing pages (either left or right bound), and a “continuous” view in the editor that is a much better representation of the same view within Ryuzine Reader.
The editor will also support “Master Styles” which can be changed without having to refresh the browser and reload Ryuzine Writer. Issue-specific styles can also be loaded, previewed, and unloaded within the editor. If you are using PHP File Operations in the editor the Image Insert no longer creates a pop-up window that may be blocked by browsers.
The “Package Builder” has also undergone a major rewrite and will also offer the option of packaging into a plain folder instead of a ZIP archive. This is useful if you want to make manual additions or changes to the package or plan to immediately FTP it up to a website for viewing rather than offering it as a downloadable publication.
We could literally go on and on listing everything in the change-log but we’ll hold off until the actual release.
Ryuzine is Going Open Source!
We’re still looking through the various open source licenses to find the one that fits us best, but you read that correctly – version 1.0 of all the Ryuzine webapps will be released under an open source license. This will completely replace the current Commercial and Non-Commercial Use licenses. That means with version 1.0 there will no longer be a requirement to purchase a license for commercial use! ALL of the source code will eventually be available on GitHub, with each webapp and add-on in its own repository. Once that has happened anyone and everyone can contribute to making Ryuzine even better! Since it will be a little confusing for non-developers to grab and assemble all the files from multiple repositories, www.ryumaru.comwill remain the place to download the pre-packaged webapps.
So When Can You Get It?
One of the factors in deciding to take Ryuzine open source is that, since the beginning, there has only been ONE developer working on it as a side-project, even as the “family” of webapps has grown. The first step was a “code audit” to make sure all the code that will be released CAN be released under an open source license. Then there were all the UI changes, updating themes broken by the UI changes, bug fixes, adding new features, breaking built-in functions out into add-ons, rewriting the Add-On API, and lots and lots more that still needs to happen. Our best guess is that it will be ready sometime in the Spring or Summer of 2015. Until then you can still download version 0.9.6.7 of Reader/Rack and Writer and 0.9.6.8 of the Ryuzine Press plugin for WordPress.