I am using gatsby and material UI according to the official example and I am wondering if I have to add the withRoot wrapper to EVERY component that uses MUI or if I can just wrap the highest level component that I want to use MUI?
I am having trouble with the render and IDK how to track down the cause. In dev everything works great, but in prod, <Grid> alignments are off and on the initial render, there are no styles applied. They are applied a second or two after the first paint.
I have followed the example exactly and wrapped only my global layout component.
I experienced the sames issues when starting to work with gatsby 2 (latest beta) and MaterialUI.
After some research I stumbled upon very helpful comments on GitHub. I summarized my learnings (with the links to the mentioned comments and solutions) in one of the issues on GitHub. You can find them here.
I hope this helps you and others.
Related
Does anyone have a list of all XAML tags (and the list of properties each has) used in MAUI?
Thanks
I'm not sure if there is a list that is only focussing what is available in XAML. Then again, a lot of the things you can do in code can be done in XAML.
I think a great way to start is to look at the official Docs. Namely the controls, pages and layouts will be something to look at because that is most of the time what you will be putting into XAML files. From there you will automatically branch out into styles, themes and other resources that you can have in XAML as well as you find yourself needing them.
If you really need ALL the public APIs (read: all the classed, methods and objects) then you want to look at the API docs. This is also the documentation that you will find inside of Visual Studio in the IntelliSense. We have published those here.
While this has a description of all the APIs that are there in .NET MAUI, a lot of them are currently lacking a useful description right now. We are working hard on improving that. For most, hopefully, the code should be self-descriptive enough and at least you can make a connection to what to search for our try out yourself in code.
A day ago my prestashop website, in the comment box of the blog started to display the following message:
And entering the post that explains how to migrate the version of TinyMCE , I do not understand very well how to perform these steps in my prestashop.
How can I update this?a
if you are using a third-party module to make your blog it might be is including its own version of TinyMCE. You should try to dig in its code to understand that.
If this is not the case, the blog uses TinyMCE which is normally included in Prestashop core.
On said that, this second case is likely to be the one. Update the e-commerce unlikely will solve your problem. I honestly don't remember in which version they are with TinyMCE but doing an upgrade like that might break back-office editor forms so I don't think they are keen on that at the moment. They are doing a major rollover to Symfony, I am pretty sure this is their priority right now. As said in one comment, Prestashop's dev team has to solve the issue on their side.
I come from the world of JavaDocs and love the DX of working on a thoroughly-annotated application after a certain level of complexity.
Being able to hover over and peek all the props (and implied types) of a component with some brief documentation would save me so much time instead of having to open up and read through the whole component. Better yet, running a command to generate a documentation site just like you can with JavaDocs would be dope!
Are there any standards or tools built around creating SvelteDocs? I looked through the VS Code marketplace and didn't see any documentation tooling related to Svelte.
I stumbled upon this question in search of more in-depth documentation for the hover/peek documentation method I've been using. It seems that it is not very well documented (ironically) but it is a part of Svelte language-tools and I've been using it for some time with Svelte for VS Code so I'm sure there was more documentation at some point. The way it's used is as follows in your component. I remember reading somewhere that it needs to be the first thing in your component, but I can't find that source anymore.
<!--
#component
some markdown here
-->
For some reasons the only documentation I can find of it is here. But it provides very nice markdown support so you can craft some very informative hover/peek documentation for your components.
EDIT:
Still can't locate official documentation for the #component commenting feature but realized it is indeed described in the FAQ: https://svelte.dev/faq#how-do-i-document-my-components Does this information belong in the actual docs? Maybe.
After more digging, I found just a couple projects for documenting Svelte.
SvelteDoc Parser -- takes a VueDoc approach, based on JSDoc standards, generates JSON documentation for Svelte components
Svelte-Docs -- documentation in Markdown mixed with Svelte's features, can embed components in the generated doc pages
Both look interesting while taking completely separate approaches to solving the issue of application documentation. Perhaps there's still room to build a CLI-based site generator for the SvelteDoc Parser which could be turned into a VS Code plugin!
It is difficult to find a good one. I recommend
https://github.com/carbon-design-system/sveld
It looks very promising. It offers export in Typescript definitions, JSON and Markdown. In my opinion there is only one critical bug left (Markdown generation) so hopefully it can be used very soon.
My gist markdown is not rendering when I embed it. Is this a GitHub issue, or am I doing it wrong?
The gist:
https://gist.github.com/3094145
The non-rendering embedded gist:
http://jsfiddle.net/dJnBg/
Thanks!
*2012-12-11 Update: Today github pushed out a complete rewrite of gist.github.com, and this is no longer a problem. For proof, see screenshot. *
It looks deliberate. It's worth noting that syntax highlighting still works in embeds, but not (alas) markdown rendering.
A potential workaround might be to add additional JS code (after the gist embed JS) that renders the markdown client-side, perhaps via http://www.showdown.im/
I made an issue for myself to do this for the redmine gist embed plugin I wrote.
https://github.com/dergachev/redmine_gist/issues/3
Perhaps by the time you're reading this I got around to tackling this ;)
I looked on CKEditor's website and I noticed that there's no plugins documentation yet.
But I'm wondering if there is any anywhere else?
I'd like to make a little plugin to add youtube video from CKEditor. Pretty simple plugin but still I'd like to know how to make it.
Documentation is sparse at the moment, but not completely non-existent.
Check out my CKEDitor link survival pack from a previous question.
As a starting point, you may want to copy and use one of the existing plugins (the unpacked ones from the _source directory, of course).
The symbols plugin is extremely simple but shows the basic points of inserting HTML into the editor
The links plugin may be a good starting point for how to add input fields, tabs, and make them interact (If you want to go the road of understanding CKEditor's highly sophisticated dialog layout system, that is. My cup of tea, it wasn't. You may want to just set up an Iframe dialog, and do everything by yourself).
Since this question was first posted, CK has added documentation for creating plugins - http://docs.cksource.com/CKEditor_3.x/Tutorials/Abbr_Plugin_Part_1