January 19, 2019 at 5:59 pm #13659
Hey guys! We just released Bootstrap Studio 4.4.0. Here is what’s new:
- You can now define favicons, create sitemaps, Twitter and Facebook cards, Progressive Web App manifests and more, from the new Settings > SEO panel.
- A new Comment component was added. Drag and drop it into your design, and double click it to edit.
- Commenting support was added to the CSS editor.
- The Bootstrap framework was updated to 4.2.1 and 3.4.0 respectively. We don’t yet have the toast and spinner components built in, we will add them in our upcoming releases.
- The Google Fonts integration was updated with the latest font families.
In the upcoming 4.4.* releases we will focus on adding new components and some of the power features which we’ve discussed in the forum. We will update our roadmap soon.
Be sure to report any bugs that you see. Looking forward to your feedback!January 19, 2019 at 7:43 pm #13660
Haven’t gone through much yet, just playing with the comments, and one thing I need to bring up is that a comment should not even come close to having to be contained within a column or any other container. When we add a comment, it should be straight up, not needing to be contained in anything. This is a lot of extra code to have to wade through that we normally do not ever add when adding a comment.
I appreciate the addition of them though, but they really need to be able to be added straight to wherever we want them without adding anything else with them.
Of other note:
It would totally make sense to have the ability to expand all / collapse all in the Overview and HTML panels to go with this so we can see all the comments added at once.January 19, 2019 at 7:56 pm #13661LarseneMember
Comments are greats, and useful as they are for me 🙂 I love the way you add CSS comments.
But i haven’t found new bootstrap components (Spinner, toast) or new style for checkbox (switch)….
Version after version, BSS becomes better and better 😉January 20, 2019 at 7:06 am #13662MiSTMember
I usually just throw my exported design into sublime text and add all my comments in there.January 20, 2019 at 1:46 pm #13669
Mist, your comment was actually not even slightly useful. We’ve asked for comment capabilities for 2 years, so if you don’t use them, that’s fine, but we don’t really need to know that if it doesn’t help anything.January 20, 2019 at 2:56 pm #13670MiSTMember
I’m not sure why this was such a requested feature. BS Studio is great for concept work and quick drafting of designs but it’s not a full blown development environment and if you’re using the program for that, then you’re doing it wrong! LOL
Oh, and it’s “MiST” not “Mist”
Cheers ;DJanuary 20, 2019 at 3:47 pm #13671
Actually I’m doing it very right and have been every since starting to use this app. I can do most anything any of my clients need all within the app and have not had to branch outside of it as of yet. I’m a Designer mind you, not a Developer, but I’ve included scripts for pretty much anything most businesses will want and need and so far my clients have not asked for anything I couldn’t do within the app. So …..
Having said that, Comments are a very very welcome item for many of us that are using the app itself. Mind you I do code, so it’s not about not knowing how, it’s about ease of management for me 🙂January 20, 2019 at 5:12 pm #13672
I need to also tack on to my comments (no pun intended haha) about the inclusion of the Column as part of the comments in that it adds it visually to the page as well, like any other Column shows up in the visual window, and it totally skews your design in many places. Tried to add one to the Header area for an item I have in there to remind me why it’s there (no comments please! lol) and it totally messed up the Header structure and I had to remove it.. Really a bad way to have this set up, pretty much unusable. I’m not prepared to have to create a set of CSS attributes to style a comment so it’s doesn’t screw up the pages.
Either way, even if I did style them to not screw up the pages, all the columns would be in the code, and so far that’s already messing with the ease of readability of the code. 🙁January 21, 2019 at 9:17 am #13673
Thanks for all the feedback!
@jo I think I know what’s happening. The Row component mistakenly wraps Comments with Columns (like it does with all other components). This is an oversight on our part. Comments don’t come with Columns themselves and it should be possible to place them anywhere with no side effects. We will fix this in the next release.January 21, 2019 at 2:39 pm #13677marrcoMemberValued
I’ve seen it’s not even in the roadmap, so I ask here.
(non breaking space) support be available?
(and that’s not the only html entity missing)January 21, 2019 at 3:08 pm #13678
Thanks Martin! Glad to hear it! Looking forward to that fix for comments as well as the items on your new Roadmap post! Keep em coming!January 21, 2019 at 5:13 pm #13680January 21, 2019 at 5:59 pm #13681
Thanks for the fixes and the NBSP function!January 21, 2019 at 7:42 pm #13685TonyBenedettiMember
Thanks a million for the comment component. Not only does it allow us to develop well documented HTML but opens the door to other JS libraries and potentially other HTML postprocessing. “Exciting” possibilities to this developer.
For example, KnockoutJS has a facility called “virtual elements”. A virtual element is marked up in HTML as a comment and can be bound to a JS function. See Creating custom bindings that support virtual elementsJanuary 21, 2019 at 9:03 pm #13688TonyBenedettiMember
Referencing the new Road Map — Thanks for the new components on the way … spinner, toast, etc.
But while your’e working on those, could you take a look at adding the Bootstrap Form Row component? It’s nothing more than: div class=”form-row” and behaves just like div class=”row” but with “tighter and more compact layouts”. I have a custom component that does the job for me but the Overview shows “Div Form Row” instead of “Form Row elementID”.
I know I could label my Form Rows to match the elementID, but then the Overview would not distinguish between the Form Rows and the hundreds of Divs in my design.
I don’t think it would take much more than duplicating your code for Row; renaming the duplicate to Form Row; and changing the generated class from row to form-row.
You must be logged in to reply to this topic.