We are about to start a spartacus-storefront project (1.3.1) and in the docs it is mentioned that for Q1 2020 the removal of ng Bootstrap is planned.
https://sap.github.io/cloud-commerce-spartacus-storefront-docs/spartacus-roadmap/#move-to-angular-9--ivy
What will this mean for projects we start now and base on bootstrap? If we want to upgrade in the near future and we based our components on bootstrap will we need to refactor a lot? It is kind of a black box for me what the implications will be.
ngBootstrap functionality will be removed from Spartacus in 2.0 but bootstrap styles will not be removed as a dependency in the styles library as of then. You can always import bootstrap into your projects even if it is removed from Spartacus.
~ Caine from Spartacus Core Team
ng-bootstrap is an angular component library for bootstrap components. We've decided to move away from this implementation. Initially we tried to complete this before the 1.0 release, to get ride of the dependency, but we haven't been able to drop the modal before 1.0 release. We will drop the last pieces of ng-bootstrap (modal) for the 2.0 release.
This doesn't mean that we're dropping bootstrap itself (yet). We have a plan to become agnostic to various UI systems, but that's a bigger change.
Related
So issue is that one of the app i working on as react-native developer is using
Material Top Tabs Navigator
Which is officially recommended by react-native but since it is depended on
react-native-tab-view
react-native-pager-view
and apparently react-native-tab-view have issue with RTL it not work properly.
Also in there limitation they also mention that rtl support is limited
https://reactnavigation.org/docs/limitations/
For me my app is causing weird behaviour in rtl and i want to ask about probable solutions for this
I am able to fix this issue by forking the "react-native-pager-view" but issue remain that mean i also have to fork "Material Top Tabs Navigator" as i want to use my own pager view.
One more solution i come up with is to write my own library by using native scrollview.
So what you suggest what is better option. In case one i have to wait for their solution until then i just have to keep my fork repository up-to-date but complete dependency on update for rtl.
In case 2 i have to maintain my code by myself but i good side full control over code.
which is the better option according to you and why ?
Building an enterprise level application with Vue 3 and unfortunately I haven't found any suitable plugin to make the application responsive. While there are older plugins that work with Vue 2, nothing I have found works with Vue-3.
What would be a suitable approach to make the application responsive?
Assuming CSS media queries aren't enough I would honestly just use the matchMedia API.
You could react to window resizes with a MediaQueryList onchange handler.
I recently joined a team working on a nuxt js frontend application. Since the beginning, I could not make the project run properly in terms of styling.
Styles, classes, are correctly loaded in the html, I can clearly see them in the code inspector.
Though, it does not behave like it normally should (See picture 1). I compared nearly everything with the other developers and impossible to find a fix.
Did any of you already have such an issue ? And any idea of how to fix it ?
Thank you
Small example of the styling issue I have between 2 menus
Now that Rally has changed the default UI for their ALM product, I have noticed that the UI components in my apps don't fit the same styling characteristics as the default UI elements. I think it would look a lot cleaner if I could use Ext's "Neptune" theme: http://docs.sencha.com/extjs/4.2.2/extjs-build/examples/build/KitchenSink/ext-theme-neptune/#basic-panels
Is there a way I can use this theme by default? If it is hosted anywhere within Rally, I think it would be as easy as including the CSS file in the App.html, but I could be wrong.
2.0rc1 is built on Ext 4.1.1a, so I'm not sure if the neptune theme is included or not. You'll be happy to know that 2.0rc2 is hot off the presses though, and should incorporate most of the new look and feel.
https://rally1.rallydev.com/apps/2.0rc2/sdk.js
https://help.rallydev.com/apps/2.0rc2/doc/
I think I'm missing something very, very obvious and easy, but - how do I migrate my 2.1-app to 2.2? What do I have to copy or which script do I have to run?
Just be aware that the theming has changed between version 2.1 and 2.2. In particular the Picto icons, used for buttons, have now been replaced by fonts. Unfortunately it appears that the new Picto font doesn't contain entries for all the icons that were in the previous set and I haven't yet found a way to continue to use the old icons. As a result, your new version 2.2 app may therefore look different to your version 2.1 app.