is it possible to change the css of an existing widget so it will support rtl?
I was thinking of creating a custom widget from the existing widget and just change the css but couldn’t find the widget code.
All official Widget code is located here.
https://github.com/netlify/netlify-cms/tree/master/packages
Widgets are usually divided into "Editor" and "Preview" implementations, and you can customize the React Components that each generates. I'm not familiar with RTL, so I could be wrong, but if that can be done with just a CSS change, then you can probably do what you want to do.
https://www.netlifycms.org/docs/custom-widgets/
Related
I have been reading some of the Flutter documentation, wondering what the best way is to make completely custom designs. I have come across the following image in flutter's README file:
Does anyone know what the recommended way is of creating custom layouts like this one? Do I restyle the different parts of the Material Theme?
Some widgets are customized Material Design, often you would create your own if you are looking for custom style.
In the screenshot seems like they are using the material PageView, BottomNavigationBar but have created a custom slider, switch ext.
It really depends have custom you want your app, Material Design gives you flexibility but it has its limits.
I´m rookie in Joomla. I'd like to do a fine-adjustment in the presentation of a bunch of icons in a toolbar that I've created using logo/image components in the layout editor for a certain theme. These icons are being presented with a too wide spacement between one another, and it seems that the cause is the property flex in the css file nucleus.css (.size-5 element, according to inspections in Firefox).
I'd like to know how to resolve this spacement issue, perhaps changing paramenter's values in this css file, if there is no other way. Thanks for any help.
I just have learned about vaadin and I'm watching tutorial about a CRUD TODO list in youtube. Vaadin uses Valo theme for css rendering that I found great but I'm wondering is it possible to use w3.css framework within vaadin vue code ?
I try googling but no answers.
It depends™
If you are asking: can is just replace Valo with W3.css the answer is most likely no, at least out of the box. The reason for this is, that Vaadin client side code emits the HTML-code you see in the browser and all style and class tags there are defined on their end. So what any theme for Vaadin must do, is to provide styling rules for that exact schema; so you would have to find a way to adapt. Or you have to put addStyleName all over your code (if it's btn in your CSS framework, it's v-button in Vaadin and also nested elements might be different etc).
Yet, if you just want to use the styles for some parts of your application (let's say, you want a fancy start page or add cards etc), then you can add the other CSS and use them together. Vaadin/Valo does a good job in isolating their styles from the rest of the page and also within their hierarchy (the theme name is a prefix to all Valo rules). Yet if the two themes then look great together is another story, but Valo itself allows for quite some tweaking just with variables put in SASS.
Is it possible to add an accordion to a Joomla 3.x component's options screen, similar to what is presented in Joomla's menu or template parameters screens?
If so, how does would one structure the config.xml file?
Example illustration of what I am trying to achieve:
Com_config manages that view and it pretty much expects a standard structure. You might be able to do a layout override for it as long as you don't break the other extensions. You could for example make it conditional on the option being your extension.
A client web site uses a Joomla template with lots of modules in the left column, but for the custom component I'm designing, those modules must be replaced by a vertical menu. The hack solution I came up with is to hide those modules with CSS:
div#leftpad > div {
display:none;
}
and then insert a <div id='compmenu'> in <div id='leftpad'> with javascript and set display:block. With jQuery, I could do
jQuery('#compmenu').appendTo('#leftpad').show();
The component displays a google map, so javascript is required anyway. Any Joomla experts here know of a more elegant or straightforward method to achieve the same result?
Why don't you use the build in Menu-Bind for Modules to hide them when your Module or Component is displayed, this would be a clean way. I think your Module/Comp is bound to a Menu item.
Edit:
For sure your client have to implement your Module/Comp the right way. Is is very bad to do something like this with a hack.
Create Menu-Item for your component (programtic)
Create a hidden menu
Add your component to that menu
Do unbound all modules from this menue
The Joomla API hold a good series of Tutorials about building components. I gone through them in the past but as I see they have improved them. As I understand your component is relatively straight forward so the default menu should be what you want. It is described in the install XML
<administration>
<!-- Administration Menu Section -->
<menu>MyMenuLink</menu>
<!-- some other stuff -->
</administration>
And will be available at the Joomla! menumanager after your client has installed your component. So I think it will be not that hard for you.
In Joomla, menu types are determined by the various Views specified by the installed components. If your component is properly coded to Joomla MVC standards, you should have at least one View, which will give you at least one menu type to choose from. As sra mentioned, even if you do not need a menu link, you should create a hidden menu so you can create a link so you have an itemID to work with and assign modules to.
There are a few extensions and websites that can help create the necessary files for a component so all you have to do is add a little code. Once you understand the Joomla MVC it's really not too difficult.
http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1
Doing it this way will save you a lot of headache later when the end user has to figure out how to use your component.