I’m not sure if the topic is still open for new wishes, but since we have aurora and the desktop in the house, drag’n’drop for card component (and probably for other components also) would come handy.
The idea comes from the desktop scene where it is quite common to have “customizable” dashboards, where customization often means that cards with different contents can be dragged and pinned around the dashboard.
I would better not reinvent the wheel and recommend this library https://sortablejs.github.io/Sortable/ It has zero dependencies, modern, has a lot of options. I use it in my recent projects and fully happy with it
Good advice, perhaps we can create a list of useful libraries? I don’t mean another “awesome” list but complementair to F7 and based on positive experience and recommendations. Like sortable.js and localforage.js
In order to improve the performance of all animations, have you thought about using the Web Animations API? Maybe something simple, similar to this ones:
(I mean in the Core v5 edition)
BTW @nolimits4web, as always, congrats for such a great tool and framework.
Would be great if upgrade tabbar to something like this for material theme: https://onsen.io/demo/
Notice moving white indicator under the tabs while swiping, something like native of android.
Agree with @luigi37 (not on the star-system component, though), but what really would be shiny, would be some pages with ‘best-practices’ or ‘tips and tricks’ (I would help with that):
I found there’s not much info/guidance on the F7 documentation pages and lot’s of things require a look at the kitchen-sink sources (or the F7-sources itself).
I recently stumbled upon Quasar's info-pages, which do a great job in that regard:
It would be tremendously helpful, if we could create something like that for F7 - this is also where ionic shines (ok. they are much more people , but again: I also would contribute…
I agree that best-practices and tips & tricks are very useful. They might require a different platform then this forum or a blog to enable participation of experienced F7 users. I don’t see immediately how Quaser achieve this but like tiptronic I am also available to help. At this moment I scan daily this forum to learn from experience of others but that is not very efficient and less effective for newcomers than best-practices pages.
What I mean is that I would like to be able to execute ALL cordova related commands (including and referring specifically to “simulate” which is the thing I use the most while developing)
As per today it looks to me that
either you avoid those commands
or you must work in the cordova directory
but that’s explicitly mentioned as a bad practice in F7 projects…
So it makes me assume that some automatisms will not work if I have an F7 project but I’m working in the cordova dir (specifically it seems that “routing” could not be automated properly).
NOTE: I’m not expert in F7 v5, just learning now, so I understand my points might be trivial but at the same time, my learning experience could be useful to improve documentation/processes for all newcomers…
@Erik_Cornelisse@tiptronic i am totally agree that something like Best practise/Most common errors/Etc. is missing. But help me to figure out what is exactly missing I raised the old topic that was forgot for some reason: Let’s make FAQ section Would be cool if you can add there your thoughts, anything that comes to your mind
Also, guys, if you see something is missing in docs, don’t hesitate to raise an issue at Framework7 Website repo at https://github.com/framework7io/framework7-website/ or if you can, you can edit docs directly and send the PR. I will really appreciate it
is there any chance adding custom components like vue ?
import mycompoenet from './mycomponent'
…
{
components: [‘mycomponent’]
}
…
i know there is registerComponent but it’s before init,
it would be great if we could use it afterwards and on demand like using import(’’) inside components;