@layer styleTab {\n${this.props.style}\n} ` }} />;
+ return
-
+
+ {baseThemePath &&
+
+ }
+
{/* Apply CSS from Style tab and render pages from Markdown tab */}
{this.state.isMounted
&&
diff --git a/client/homebrew/brewRenderer/brewRenderer.less b/client/homebrew/brewRenderer/brewRenderer.less
index abb80fc5f..bde91c92e 100644
--- a/client/homebrew/brewRenderer/brewRenderer.less
+++ b/client/homebrew/brewRenderer/brewRenderer.less
@@ -21,11 +21,17 @@
right : 17px;
bottom : 0;
z-index : 1000;
- padding : 8px 10px;
background-color : #333;
font-size : 10px;
font-weight : 800;
color : white;
+ div {
+ display: inline-block;
+ padding : 8px 10px;
+ &:not(:last-child){
+ border-right: 1px solid #666;
+ }
+ }
}
.ppr_msg{
position : absolute;
diff --git a/client/homebrew/brewRenderer/notificationPopup/notificationPopup.jsx b/client/homebrew/brewRenderer/notificationPopup/notificationPopup.jsx
index 92193d22c..f0a0f5f1f 100644
--- a/client/homebrew/brewRenderer/notificationPopup/notificationPopup.jsx
+++ b/client/homebrew/brewRenderer/notificationPopup/notificationPopup.jsx
@@ -4,7 +4,7 @@ const createClass = require('create-react-class');
const _ = require('lodash');
const cx = require('classnames'); //Unused variable
-const DISMISS_KEY = 'dismiss_notification09-9-21';
+const DISMISS_KEY = 'dismiss_notification08-27-22';
const NotificationPopup = createClass({
displayName : 'NotificationPopup',
@@ -22,45 +22,45 @@ const NotificationPopup = createClass({
},
notifications : {
psa : function(){
- return \n${this.props.style}\n` }} />;
},
renderPage : function(pageText, index){
@@ -177,6 +187,9 @@ const BrewRenderer = createClass({
render : function(){
//render in iFrame so broken code doesn't crash the site.
//Also render dummy page while iframe is mounting.
+ const rendererPath = this.props.renderer == 'V3' ? 'V3' : 'Legacy';
+ const themePath = this.props.theme ?? '5ePHB';
+ const baseThemePath = Themes[rendererPath][themePath].baseTheme;
return (
@@ -188,7 +201,7 @@ const BrewRenderer = createClass({
: null}
-
- After a long and bumpy road, we decided it was high time we finally release version 3 of the homebrewery into the wild. You can check out a - brief overview and see how to opt-in to the new features here: - V3 Welcome Page and - the Changelog. -
- BE WARNED: As we continue to develop V3, expect small tweaks in the styling, fonts, and snippets; your brews may look slightly - different from day-to-day. All of your old documents will continue to work as normal; we are not touching them. If you don't want to deal - with the possibility of slight formatting changes, you may choose to stick with the Legacy renderer on any of your brews for as long as you like. -
- With this in mind, if you still wish to try out V3, you can opt-in any of your brews to the the V3 renderer. - This will likely break much of your formatting as a lot of the Markdown code has been updated, and starting from scratch may be cleaner. - (Don't worry, you can always change the renderer back to Legacy for any brew at any time). -
- Currently a lot of people are striking issues with their Google credentials expiring, which happens one year after the last sign in via - Google. This can cause errors when trying to save your brews. If this happens, simply visit the - - logout page - - , sign out, and then sign back in "with Google" to refresh your credentials. See - - this discussion on Github - for more details. -
- If you opt not to use your Google Drive, keep in mind that we do not save a history of your projects. Please make frequent backups of your brews! - - See the FAQ - to learn how to avoid losing your work! -
+ We are happy to announce that after nearly a year of use by our many users, + we are making the V3 render mode the default setting for all new brews. + This mode has become quite popular, and has proven to be stable and powerful. + Of course, we will always keep the option to use the Legacy renderer for any + brew, which can still be accessed from the Properties menu. +
+ We have made a change to the process of tranferring brews between Google + Drive and the Homebrewery storage. Starting now, any time a brew is + transferred, it will keep the same links instead of generating new ones! + We hope this change will help reduce issues where people "lost" their work + by trying to visit old links. +
+ We have had several reports of users losing their brews, not realizing + that they had deleted the files on their Google Drive. If you have a Homebrewery folder + on your Google Drive with *.txt files inside, do not delete it! + We cannot help you recover files that you have deleted from your own + Google Drive. +
+ If you opt not to use your Google Drive, keep in mind that we do not save a history of your projects. Please make frequent backups of your brews! + + See the FAQ + to learn how to avoid losing your work! +
+ 
+