<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Framework7 Blog - Medium]]></title>
        <description><![CDATA[Full featured mobile HTML framework for building iOS &amp; Android apps - Medium]]></description>
        <link>https://medium.com/framework7?source=rss----902810cfed8---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Framework7 Blog - Medium</title>
            <link>https://medium.com/framework7?source=rss----902810cfed8---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:45:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/framework7" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Framework7, Next.js & Server-Side Rendering? Yes!]]></title>
            <link>https://medium.com/framework7/framework7-next-js-server-side-rendering-yes-1f6c9334dc03?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f6c9334dc03</guid>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[server-side-rendering]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 16:43:11 GMT</pubDate>
            <atom:updated>2021-07-24T16:15:10.666Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hlPXfloaeH9GftQ8kOP0g.png" /></figure><p>In <a href="https://blog.framework7.io/framework7-v6-d5b843abe8e7">Framework7 v6 release announcement</a> we mentioned the full server-side rendering support. Now it is time for practice.</p><h3>TL;DR</h3><p>You can fork this <a href="https://github.com/framework7io/framework7-nextjs-starter"><strong>framework7-nextjs-starter</strong></a> project right away and start hacking on it.</p><h3>Create Next.js Project</h3><p>First, we need to create a new Next.js project. We will use create-next-app CLI tool. Run in terminal:</p><pre>npx create-next-app f7-next-app</pre><p>This command will create a project in a /f7-next-app directory.</p><h3>Install Framework7</h3><p>Let’s move to our project directory (/f7-next-app) directory and install required Framework7 dependencies. We need to install Framework7 itself, Framework7-React (as we develop a React app), Framework7 and Material icons:</p><pre>npm i framework7 framework7-react framework7-icons material-icons</pre><h3>Setup Environment Variables</h3><p>In project root folder we need to create two env files:</p><ul><li>.env.development — with environment variables for development</li><li>.env.production — with environment variables for production build</li></ul><p>In this files we need to define NEXT_PUBLIC_HOST variable, that will point to our webapp host. During development it will be <a href="http://localhost:3000,">http://localhost:3000</a> (default Next.js dev server), and for production you need to specify the host where the app will be deployed:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2430917fe1dc7fb7280be27ea9f32137/href">https://medium.com/media/2430917fe1dc7fb7280be27ea9f32137/href</a></iframe><h3>Routing</h3><p>Before, we start hacking into our app files, let’s figure out how to handle routing here.</p><p>Next.js has an amazing built-in router, but unfortunately it doesn’t fit for complex page transitions used in Framework7. To solve this issues we need to use both Next.js (to get initial page component on server-side) and Framework7 (on client-side) routers.</p><p>To support server-side routing and have a correct response with initially requested page we must keep our pages in structure required by Next.js (e.g. in ./pages folder). And we need to match our Framework7 router to this pages.</p><p>For example, if we have the following pages in our Next.js app:</p><ul><li>./pages/index.js</li><li>./pages/about.js</li><li>./pages/blog/[postID].js — dynamic route</li></ul><p>We need to match it to Framework7 React router and pass this routes to our Framework7 App. So Framework7 routes for such structure will be the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e5a70b4ff33b5667b6047f374ba86900/href">https://medium.com/media/e5a70b4ff33b5667b6047f374ba86900/href</a></iframe><p>Pay attention that we use asyncComponent because we don’t want (and more likely don’t need) to add all routes/pages content into initial page JavaScript file.</p><h3>_app.js</h3><p>Now, let’s move to our main app component. We need to setup and tweak our main App layout in pages/_app.js file. By default (created by create-next-app) it should look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5bddc8788738b80762ce749cddb8732/href">https://medium.com/media/f5bddc8788738b80762ce749cddb8732/href</a></iframe><p>Let’s modify it to the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/17f423432b4a3ff28c0b462235ae7c40/href">https://medium.com/media/17f423432b4a3ff28c0b462235ae7c40/href</a></iframe><h3>index.js</h3><p>We are almost ready. What is left is to change our main index page (located in index.js ) to be a Framework7-React page:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ead3fa7b33e6e5382e6783b282f19a77/href">https://medium.com/media/ead3fa7b33e6e5382e6783b282f19a77/href</a></iframe><h3>Launch 🚀</h3><p>Now, let’s launch our dev server</p><pre>npm run dev</pre><p>And we should see something similar to this on http://localhost:3000</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GxGMCoJNUntpb0I-73uJeg.png" /></figure><p>But was it rendered on server-side? Let’s check response source code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OiD3Hc9Mrdl8Bl3GvuidLQ.png" /></figure><p>Great, as we see server-side rendering works.</p><h3>Navigation</h3><p>As mentioned above for navigating and router we use ONLY Framework7’s router, its methods and components.</p><p>Let’s create dynamic route page in ./pages/blog/[postID].js file with the following content:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/da240d1d0a711db3e8e3b73c0339d017/href">https://medium.com/media/da240d1d0a711db3e8e3b73c0339d017/href</a></iframe><p>And now we need to add this route to our Framework7 routes in _app.js :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1574292636e5f0e3be802487d9529ec2/href">https://medium.com/media/1574292636e5f0e3be802487d9529ec2/href</a></iframe><p>And link to the page, somewhere on our home page:</p><pre>&lt;a href=&quot;/blog/45&quot;&gt;Blog post&lt;/a&gt;</pre><p>Everything works as intended:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fh1FpBBkF0cw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dh1FpBBkF0cw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fh1FpBBkF0cw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a03bd25e7179414301eff8797efc588a/href">https://medium.com/media/a03bd25e7179414301eff8797efc588a/href</a></iframe><h3>Bonus: Server-Side Theme Detection</h3><p>As you may know Framework7 supports iOS, Material Design and Aurora themes. Theme can be specified on main App component like so:</p><pre>&lt;App theme=&quot;ios&quot;&gt;</pre><p>Or it can be set to auto and Framework7 will decide which theme to use based on user device. And if we use server-side rendering, it is not recommended to use auto theme senselessly.</p><p>For example, we set theme to auto, and user visits our web app with iOS device. Framework7 will be initialized on server-side, and apparently it will not detect server environment as iOS device and will enable material theme. Then on client side, it will detect it as iOS device and set theme to ios , but HTML layout rendered on server-side can be different (the one that required for material theme), which can produce as server-client layouts will not match.</p><p>Simple solution will be to just use single theme. But that is not for us. With Next.js getInitialProps we can actually correctly detect user’s device on server-side based on his user-agent !</p><p>To do so, let’s add getInitialProps function to our _app.js and see how get and use user-agent:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/493e3bdf17b0986bb8f48f5aa6413d11/href">https://medium.com/media/493e3bdf17b0986bb8f48f5aa6413d11/href</a></iframe><p>Now, theme detection will work correctly and we can safely use condition rendering even on server-side, e.g.:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/33fa40527cecc30e0de262c02ffcd278/href">https://medium.com/media/33fa40527cecc30e0de262c02ffcd278/href</a></iframe><h3>P.S.</h3><p>If you love Framework7, please, support project by donating or pledging:</p><ul><li>on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a></li><li>on Open Collective: <a href="http://opencollective.com/framework7">http://opencollective.com/framework7</a></li></ul><p>Your support means a lot for us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f6c9334dc03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-next-js-server-side-rendering-yes-1f6c9334dc03">Framework7, Next.js &amp; Server-Side Rendering? Yes!</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framework7 v6]]></title>
            <link>https://medium.com/framework7/framework7-v6-d5b843abe8e7?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/d5b843abe8e7</guid>
            <category><![CDATA[framework7]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 14:25:18 GMT</pubDate>
            <atom:updated>2021-07-24T16:16:18.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSHBgnBwEpgmKDnatAyycA.png" /></figure><p>It’s been a crazy year and a long road, but, finally, all new Framework7 v6 has been released! 🎉</p><h3>TL;DR</h3><ul><li>New UI Components: Area Chart, Pie Chart, Menu List, Preloader Buttons</li><li>Highly reworked Aurora theme look and feel</li><li>Updated Material Design theme look and feel</li><li>All new core Router Components</li><li>New Store library for application state management</li><li>Capacitor support</li><li>Full Vue.js v3 support</li><li>React functional components</li><li>Server-side rendering support</li><li>Full <a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md#v600---december-31-2020">v6 changelog</a></li></ul><h3>Framework7 Core</h3><p>First, let’s check largest changes in core version and APIs.</p><h4>New UI Components &amp; Improvements</h4><p>There are few new UI components landed in version 6.</p><p>New <strong>Area Chart</strong> &amp; <strong>Pie Chart</strong> components that generate pure SVG charts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsI6Sh_7A5EY40-mzoGTww.png" /><figcaption>Area Chart</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w95XPp-SnEbkAwwndTuZ5A.png" /><figcaption>Pie Chart</figcaption></figure><p>New <strong>Menu List </strong>component (modification for existing list). Menu List unlike usual links list is designed to indicate currently active screen (or section) of your app.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeDRNlubgFMg&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeDRNlubgFMg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/451afddfe062f887ad54f4644fe7f265/href">https://medium.com/media/451afddfe062f887ad54f4644fe7f265/href</a></iframe><p>New <strong>Preloader Buttons</strong> to indicate loading state:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fh0-rXMkYsm8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dh0-rXMkYsm8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fh0-rXMkYsm8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a903b2f836e9db5fa75d70b83271db2/href">https://medium.com/media/1a903b2f836e9db5fa75d70b83271db2/href</a></iframe><p>Support for <strong>nested side panels</strong>. Now, in addition to global app side panels, we can put them right inside of every Page:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3OUFJhtfpRw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3OUFJhtfpRw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3OUFJhtfpRw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8934f5c40d43a1cc2a98df2118a9b893/href">https://medium.com/media/8934f5c40d43a1cc2a98df2118a9b893/href</a></iframe><p>New and reworked <strong>Touch Ripple effect</strong> (used in Material theme) to better match updated official Material theme look and feel:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNdPy9BslTL8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNdPy9BslTL8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNdPy9BslTL8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7844ec23d0e98f4a3f42210f84713feb/href">https://medium.com/media/7844ec23d0e98f4a3f42210f84713feb/href</a></iframe><p><strong>Highly reworked and redesigned Aurora theme</strong> (the desktop theme). All components styles have been tweaked to bring all new look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v7QrEwiLyJ2Ri0jGuryysQ.png" /><figcaption>All new Aurora Theme</figcaption></figure><h4>Request Library</h4><p>Built-in request library now only uses Promises API:</p><p>If in v5 we had something like:</p><pre>request.get(&#39;some-url&#39;, (data) =&gt; {<br>  console.log(res.data);<br>});</pre><p>In v6 we should use new Promise sytax:</p><pre>request.get(&#39;some-url&#39;).then((res) =&gt; {<br>  console.log(res.data);<br>});</pre><h4>Dom7 Library</h4><p>Built-in library for DOM manipulation has been updated to new version 3, which, under the hood, has been rewritten as `Array` class extension instead of custom class.</p><p>And because of that it inherits all native Array.prototype methods, but at the some time introduces some breaking changes in “iteration” methods to match native Array methods:</p><p>If in v5 we used, for example, .each method like this:</p><pre>$(&#39;p&#39;).each((index, el) =&gt; {   <em>// ...</em> })</pre><p>Now, arguments of callback are swapped, and in Framework7 v6 it should be the following:</p><pre>$(&#39;p&#39;).each((el, index) =&gt; {   <em>// ...</em> })</pre><h4>Skeleton Elements</h4><p>Skeleton layouts was released as a standalone <a href="http://skeleton-elements.dev/">Skeleton Elements</a> library with “native” components for React, Vue, Svelete and Angular. It is now integrated into Framework7 v6 as a dependency.</p><h4>Swiper</h4><p>In meanwhile, <a href="http://swiperjs.com/">Swiper</a> also got huge v6 update with a lot of new features, and own “native” components for React, Vue, Svelte and Angular. And now it is also integrated into Framework7 v6 as a dependency.</p><h4>Template7 Library</h4><p>Template7 template engine has been completely removed from Framework7, as it produces more confusion and limitations, especially when comparing to native JS template literals.</p><p>If you still rely on it in your custom logic, you can install it as dependency</p><pre>npm i template7</pre><h4>Router Component</h4><p>One of the largest addition in core version of Framework7 v6 is totally new Router Components.</p><p>With Template7 removal, they use JS tagged template literals as template engine. It provides much more flexibility over previously used Template7 templates, but may require some extra efforts migrating your existing components.</p><p>Also component definition is now a function rather then object with data , methods, and other options.</p><p>For example if we had something like this in v5:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ceb12502ffe42698ff7029b3e2317aba/href">https://medium.com/media/ceb12502ffe42698ff7029b3e2317aba/href</a></iframe><p>In v6 will look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4edae7443d55406b2c47240de433771d/href">https://medium.com/media/4edae7443d55406b2c47240de433771d/href</a></iframe><p>Having component in single function body provides much better readability, structuring and opens a lot of possibilities for reusing code and logic across components.</p><p>And now, it is even possible to write Router Components with JSX:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b702c500ddefc1d29f45bac4ed4ea95/href">https://medium.com/media/2b702c500ddefc1d29f45bac4ed4ea95/href</a></iframe><h4>Store</h4><p>There is also a totally new application state management solution built-in. As you remember in v5 we could have global app data and methods defined on app init, now this is gone in favor of new Store.</p><p>First, we create store (for example in store.js file):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1b31f46082c5a27623e419a1e15b76e1/href">https://medium.com/media/1b31f46082c5a27623e419a1e15b76e1/href</a></iframe><p>Next we pass this store to Framework7 app on init:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/deab3ea72f74a2d416e77cbb7cb8ea59/href">https://medium.com/media/deab3ea72f74a2d416e77cbb7cb8ea59/href</a></iframe><p>And we can use store in our components:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9f7c15ee97a7c4769bf7df16fd31996/href">https://medium.com/media/a9f7c15ee97a7c4769bf7df16fd31996/href</a></iframe><p>Awesome thing with Store is that it will automatically update (re-render) dependant components on state/getters update.</p><h4>Capacitor</h4><p>Framework7 now officially support Capacitor. We added support for core APIs when app is running under Capacitor environment (core Statusbar methods, automatic disabling of service workers and router browser history, etc.)</p><h3>Framework7 React</h3><p>Framework7 React also got a large update.</p><p>First, of course, there are new React components for new UI elements: Area &amp; Pie charts, Menu List, Preloader buttons, etc.</p><p>As you could know, since Framework7 v3 we used Phenome.js library that allows us to write components once, and then auto compile them to Vue and React components. But such approach has some limitations and didn’t allow to use some framework-specific features.</p><p>In v6 we removed Phenome.js components and rewrote all Framework7 React components from scratch as function components (using hooks). Such change should provide a noticeable performance boost and much better support for Fast refresh (hot reload).</p><p>We also changed a bit how Router works in React, and now initial page components (initial routes) should be loaded much faster - on first initial app rendering.</p><p>And finally, full server-side rendering (SSR and SSG) support (with Next.js)! 🎉</p><h3>Framework7 Vue</h3><p>Framework7 Vue got an even bigger update, with full new Vue.js v3 support.</p><ul><li>In v6 we rewrote all Framework7 Vue components from scratch as function components (using new Composition API).</li><li>There are new Vue.js components for new UI elements: Area &amp; Pie charts, Menu List, Preloader buttons, etc.</li><li>Same as in Framework7 React — now initial page components (initial routes) should be loaded much faster — on first initial app rendering.</li><li>Server-side support is coming as well, with upcoming Nuxt.js v3.</li><li>As we migrated to pure Vue.js components, support for v-bind came back and can be used with all kind of form elements components and modals!</li></ul><h3>Framework Svelte</h3><p>New Framework7 Svelte already had own “native” components so not much updates here.</p><ul><li>There are new Svelte components for new UI elements: Area &amp; Pie charts, Menu List, Preloader buttons, etc.</li><li>Same as in Framework7 React — now initial page components (initial routes) should be loaded much faster — on first initial app rendering.</li><li>Added support for bind:$property props for form elements components and modals</li></ul><h3>Framework7 CLI</h3><p>CLI got a large update too:</p><ul><li>Now it generates Framework7 v6 projects (with new Router Components for Core version)</li><li>Webpack projects updated to use latest webpack 5</li><li>Now, in addition to Cordova, it can generate Capacitor project (for native iOS and Android apps)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKiRy8hiO_v8H-P808LItA.png" /></figure><h3>What’s Next?</h3><p>That was just a brief overview of most significant changes.</p><p>There are also a lot of minor improvements and fixes across whole Framework7. For all changes list please refer to <a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md">full v6 changelog</a> which can also be helpful for migration from previous version.</p><p>As next steps it is recommended to check the following new and updated Framework7 v6 docs:</p><p><strong>Framework7 Core</strong></p><ul><li><a href="https://framework7.io/docs/migration-from-v5.html">Migration guide from v5</a></li><li><a href="https://framework7.io/docs/router-component.html">Router Component docs</a> — updated documentation for all new Router Component</li><li><a href="https://framework7.io/docs/store.html">Store docs</a> — documentation for all new Store library</li><li><a href="https://framework7.io/docs/area-chart.html">Area Chart docs</a> — new Area Chart component</li><li><a href="https://framework7.io/docs/pie-chart.html">Pie Chart docs</a> — new Pie Chart component</li><li><a href="https://framework7.io/docs/menu-list.html">Menu List docs</a> — new Pie Chart component</li></ul><p><strong>Framework7 React</strong></p><ul><li><a href="https://framework7.io/react/migration-from-v5.html">Migration guide from Framework7 React v5</a></li><li><a href="https://framework7.io/react/store.html">Store docs</a> — on how to use new Store with Framework7 React</li></ul><p><strong>Framework7 Vue</strong></p><ul><li><a href="https://framework7.io/vue/migration-from-v5.html">Migration guide from Framework7 Vue v5</a></li><li><a href="https://framework7.io/vue/store.html">Store docs</a> — on how to use new Store with Framework7 Vue</li></ul><p><strong>Framework7 Svelte</strong></p><ul><li><a href="https://framework7.io/svelte/migration-from-v5.html">Migration guide from Framework7 Svelte v5</a></li><li><a href="https://framework7.io/svelte/store.html">Store docs</a> — on how to use new Store with Framework7 Svelte</li></ul><p>And docs in general:</p><ul><li><a href="http://framework7.io/docs/">Framework7 Core documentation</a></li><li><a href="http://framework7.io/vue/">Framework7-Vue documentation</a></li><li><a href="http://framework7.io/react/">Framework7-React documentation</a></li><li><a href="http://forum.framework7.io/">Framework7 Forum</a> — the best place to get F7 support.</li></ul><h3>P.S.</h3><p>If you love Framework7, please, support project by donating or pledging:</p><ul><li>on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a></li><li>on Open Collective: <a href="http://opencollective.com/framework7">http://opencollective.com/framework7</a></li></ul><p>Your support means a lot for us!</p><p>Happy New Year! 🎄</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5b843abe8e7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-v6-d5b843abe8e7">Framework7 v6</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framework7 Svelte]]></title>
            <link>https://medium.com/framework7/framework7-svelte-e6634910f2b6?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/e6634910f2b6</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[svelte]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 17:22:52 GMT</pubDate>
            <atom:updated>2021-07-24T16:16:48.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpDcGUyZqLZcM0sXirSNkw.png" /></figure><p>I am excited to announce that <strong>Framework7-Svelte</strong> is finally here and available from Framework7 v5.4.0! 🎉</p><p>Now we can build <strong><em>cybernetically enhanced</em></strong> web, desktop and mobile apps with native look and feel!</p><p>If you are not familiar with Svelte:</p><blockquote>Svelte is a radical new approach to building user interfaces. Whereas traditional frameworks like React and Vue do the bulk of their work in the <em>browser</em>, Svelte shifts that work into a <em>compile step</em> that happens when you build your app.</blockquote><blockquote>Instead of using techniques like virtual DOM diffing, Svelte writes code that surgically updates the DOM when the state of your app changes.</blockquote><p>Svelte will make your apps faster, with less and more clear code to write, and with built-in state management and reactivity.</p><h3>Usage</h3><p>Usage is pretty simple, straightforward and similar to what we have in Framework7-Vue/React. For example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c430cbb85394a538c9c702cb8ad9a29b/href">https://medium.com/media/c430cbb85394a538c9c702cb8ad9a29b/href</a></iframe><p>And we will get the following output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*NWSFljunn4vGxGZhlD5-fw.png" /></figure><h3>Getting Started</h3><p>To start creating apps with Framework7 and Svelte, it is recommend to create project with <a href="https://framework7.io/cli/">Framework7 CLI</a>, it allows to choose the framework, target platform, starter templates and many other useful things.</p><p>Just run the following command where you want to setup new project:</p><pre>npx framework7-cli create --ui</pre><p>And in “Framework” section choose <strong>Framework7 with Svelte:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v7cTkA-Pd-Pddcx9fvUhvA.png" /></figure><h3>What Is Next?</h3><p>Now it is time to try it yourself, and as next steps it is recommended to check the following Framework7 v5 docs:</p><ul><li><a href="https://framework7.io/cli/">Framework7 CLI docs</a> — useful information and instructions on how to install and work with CLI</li><li><a href="https://framework7.io/svelte/">Framework7 Svelte docs</a> — documentation for Framework7 Svelte components</li><li><a href="https://framework7.io/docs/">Framework7 Core docs</a> — documentation for core framework APIs</li></ul><h3>P.S.</h3><p>If you love Framework7, please, support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a></p><p>Your support means a lot for us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6634910f2b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-svelte-e6634910f2b6">Framework7 Svelte</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migration to Framework7 v5]]></title>
            <link>https://medium.com/framework7/migration-to-framework7-v5-1374257bb5a7?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/1374257bb5a7</guid>
            <category><![CDATA[cordova]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 10:29:31 GMT</pubDate>
            <atom:updated>2021-07-24T16:17:08.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MY_zwYuz3Ww_co0LpfGWRg.png" /></figure><p>Framework7 stable 5.0.0 released on October 7, 2019 and it is time to update!</p><p>Let’s walk through all v3 -&gt; v4 breaking changes to see what needs to be changed to upgrade your app to new Framework7 v4.</p><p>In this article we will walk most of v4 -&gt; v5 breaking changes to check what needs to be done to migrate from Framework7 v4 to Framework7 v5.</p><p>But first of all it is recommended to read <a href="https://blog.framework7.io/framework7-v5-679176716faa"><strong>what is new in v5</strong></a> and check <a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md"><strong>full v5 changelog</strong></a> for full list of changes that can be used as a good reference.</p><h3>Framework7 Core</h3><h4>New Responsive Breakpoints</h4><p>Framework7 uses new responsive breakpoints to apply different styles based on app width.</p><p>They are now:</p><ul><li>xsmall — width more than 480px</li><li>small — width more than 568px</li><li>medium — width more than 768px</li><li>large — width more than 1024px</li><li>xlarge — width more than 1200px</li></ul><p>If you use tablet-${n} and desktop-${n} modifiers classes on Layout Grid columns:</p><pre>&lt;div class=&quot;col-50 tablet-33 desktop-25&quot;&gt;...&lt;/div&gt;</pre><p>they must be changed to the following:</p><pre>&lt;div class=&quot;col-50 medium-33 large-25&quot;&gt;...&lt;/div&gt;</pre><p>Same for Lists and Block, if you use tablet-inset class there, it must be changed to medium-inset</p><pre>&lt;div class=&quot;list tablet-inset&quot;&gt;...&lt;/div&gt;<br>&lt;div class=&quot;block tablet-inset&quot;&gt;...&lt;/div&gt;</pre><p>should be changed to:</p><pre>&lt;div class=&quot;list medium-inset&quot;&gt;...&lt;/div&gt;<br>&lt;div class=&quot;block medium-inset&quot;&gt;...&lt;/div&gt;</pre><h4>New Side Panels APIs</h4><p>Panels functionality has been fully reworked and now they behave more like a modals.</p><p>Global app panel parameters (like panel.swipe = &#39;left&#39; ) are not supported anymore and now every panel must be initialized separately and panel parameters must be specified for each panel. And to make transition easier it is possible to auto init the Panel by adding panel-init class and specify panel parameters with data- attributes.</p><p>For example, if we have something like this in v4:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/36fb722be58eb5fdb497151b1b2b18d6/href">https://medium.com/media/36fb722be58eb5fdb497151b1b2b18d6/href</a></iframe><p>It must be changed to the following in v5:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e71925f1255791ac953d5aa867b0f711/href">https://medium.com/media/e71925f1255791ac953d5aa867b0f711/href</a></iframe><p>Check updated <a href="https://framework7.io/docs/panel.html">Panel Docs</a> for all new APIs and examples.</p><h4>New Navbar Layout</h4><p>In v5 Navbar container must have new navbar-bg element that should be placed before navbar-inner, and new layout looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/36564dbbd109c81d99189fdda62f1366/href">https://medium.com/media/36564dbbd109c81d99189fdda62f1366/href</a></iframe><p>Large Navbar (Navbar with large title) now should be enabled by adding navbar-large class to Navbar element:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f492c93e52e1703fbabee4c526c222d1/href">https://medium.com/media/f492c93e52e1703fbabee4c526c222d1/href</a></iframe><h4>New Calendar API</h4><p>Now Calendar uses ECMAScript Internationalization API, specifically <a href="https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat">Intl.DateTimeFormat</a> (for date/time format, month names, day names, etc.).</p><p>It has new Month and Year pickers which are enabled by default. Check updated <a href="https://framework7.io/docs/calendar.html">Calendar Docs</a> for new APIs.</p><h4>Fast Clicks Removed</h4><p>Fast clicks functionality has been completely removed. Following app parameters are not supported anymore: touch.fastClicks, touch.fastClicksDistanceThreshold, touch.fastClicksDelayBetweenClicks and touch.fastClicksExclude</p><h4>Request.Promise</h4><p>Now it resolves and rejects with a different object.</p><ul><li>will be resolved with { data, status, xhr } object (rather than with just data like before)</li><li>Request “promise” methods now will be rejected with { message, status, xhr } object (rather than with just status like before)</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d178e11064c49807832cf48fb1a22cae/href">https://medium.com/media/d178e11064c49807832cf48fb1a22cae/href</a></iframe><h4>Router Component</h4><p>Component DOM updates are now asynchronous. It means that it is not guaranteed that DOM will be updated right after calling $setState. There is a new $tick method that can be safely used to reference DOM and ensure it was updated. Or we can now use new second callback argument in $setState</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/121d9a15eba8c84140bf548c0e7d97d8/href">https://medium.com/media/121d9a15eba8c84140bf548c0e7d97d8/href</a></iframe><h3>Framework7 Vue &amp; React</h3><h4>Framework7 Lite</h4><p>It is new “Lite” version of Framework7 Core that doesn’t contain Core Component functionality. And now it is recommended to use “lite” version with F7-Vue/React packages:</p><pre>import Framework7 from &#39;framework7/framework7-lite.esm.js&#39;;</pre><p>or bundle version:</p><pre>import Framework7 from &#39;framework7/framework7-lite.esm.bundle.js&#39;;</pre><h4><strong>List &amp; Block Components</strong></h4><p>tabletInset prop has been removed, and new props based on new responsive breakpoints should be used instead: xsmallInset, smallInset, mediumInset, largeInset, xlargeInset</p><pre>&lt;List mediumInset&gt;...&lt;/List&gt;<br>&lt;Block mediumInset&gt;...&lt;/Block&gt;</pre><p>and</p><pre>&lt;f7-list mediumInset&gt;...&lt;/f7-list&gt;<br>&lt;f7-block mediumInset&gt;...&lt;/f7-block&gt;</pre><h4><strong>Col Component</strong></h4><p>tabletWidth and desktopWidth props have been removed, and new props based on new responsive breakpoints should be used instead: xsmall, small, medium, large, xlarge :</p><pre>&lt;Col size=&quot;50&quot; medium=&quot;33&quot; large=&quot;25&quot;&gt;...&lt;/Col&gt;</pre><p>and</p><pre>&lt;f7-col size=&quot;50&quot; medium=&quot;33&quot; large=&quot;25&quot;&gt;...&lt;/f7-col&gt;</pre><h4><strong>Panel Component</strong></h4><p>Panels got new API, so main app parameters related to Panel are not actual anymore and all panel parameters should be defined on Panel itself:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a0936c539982438816040bbdc05a965/href">https://medium.com/media/1a0936c539982438816040bbdc05a965/href</a></iframe><h4>Statusbar Component</h4><p>Statusbar component has been removed as its logic was reworked. So make sure you are not referring Statusbar / f7-statusbar components in app.</p><h3>New Framework7 Icons</h3><p>Framework7 Icons icon font was also updated to new version 3 with more than 800 new icons. As it is now based on Apple’s SF Symbols, most of icon names were renamed. Check the <a href="https://framework7.io/icons/">Framework7 Icons Cheatsheet</a> — for new v3 icons. And you can still access old (v2) cheatsheet (for comparison) by downloading latest 2.x icons release from repository releases <a href="https://github.com/framework7io/framework7-icons/releases">https://github.com/framework7io/framework7-icons/releases</a></p><h3>That Is All</h3><p>There is not so much breaking changes in v5, but there are a lot of new features. Check <a href="https://blog.framework7.io/framework7-v5-679176716faa"><strong>what is new in v5</strong></a> blog post if you missed it.</p><p>As next steps it is highly recommended to check all new Framework7 v5 docs and:</p><ul><li><a href="http://framework7.io/docs/">Framework7 Core documentation</a></li><li><a href="http://framework7.io/vue/">Framework7-Vue documentation</a></li><li><a href="http://framework7.io/react/">Framework7-React documentation</a></li><li><a href="http://forum.framework7.io/">Framework7 Forum</a> — the best place to get F7 support.</li></ul><h3>P.S.</h3><p>If you love Framework7, please, support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a></p><p>Your support means a lot for us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1374257bb5a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/migration-to-framework7-v5-1374257bb5a7">Migration to Framework7 v5</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framework7 v5]]></title>
            <link>https://medium.com/framework7/framework7-v5-679176716faa?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/679176716faa</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[cordova]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 10:29:06 GMT</pubDate>
            <atom:updated>2021-07-24T16:17:32.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TXbi6gSknYojZ1z3wTB1tw.png" /></figure><p>Major Framework7 update has been arrived 🎉!</p><p>In this post we will look at what is new in v5.</p><h3>Framework7 Lite</h3><p>Core Framework7 package now contains new so called -lite JavaScript files. “Lite” version is basically the same as usual one, but with one difference - it doesn’t contain Router Component functionality and its related features (Virtual Dom, routes with componentUrl, etc.).</p><p>This “lite” version is designed to be used with Framework7-React and Framework7-Vue libraries, where you, anyway, use React or Vue components instead, so switching to “lite” version will save extra KB in F7-React/Vue apps.</p><pre>import Framework7 from &#39;framework7/framework7-lite.esm.js&#39;;<br>import Framework7Vue from &#39;framework7-vue&#39;;</pre><pre>Framework7.use(Framework7Vue);</pre><p>Check updated <a href="https://framework7.io/docs/package.html">Package Structure docs</a> for full reference of new files.</p><h3>CSS and Theming</h3><p>There are many CSS and theming tweaks and fixes:</p><ul><li>iOS dark theme colors reworked to match iOS 13 dark theme colors</li><li>Most of CSS variables related to colors (especially “gray” colors) reworked to rgba colors to appear better on custom designs. It is related to text colors, background colors, icons colors, borders and hairlines colors.</li><li>Most of iOS theme 15px sizes (list/blocks paddings and margins) are changed to 16px instead</li><li>Dark theme can now be excluded from bundle (custom build)</li><li>And light (default) theme can also be excluded from bundle (custom build)</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX_1oIVlpnuM%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX_1oIVlpnuM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX_1oIVlpnuM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8757ad68c7f618915399561636f9dd2b/href">https://medium.com/media/8757ad68c7f618915399561636f9dd2b/href</a></iframe><h3>New Responsive Breakpoints</h3><p>There are new system CSS responsive breakpoints. <strong>This can be a breaking change.</strong></p><p>If you remember in previous version we had helper classed like tablet-inset to make list block inset on tablet-size screen, or tablet-50 to make grid column 50% width on tablet-size screen.</p><p>Nowadays this became irrelevant, so v5 has new set of such responsive breakpoints:</p><p>They are now:</p><ul><li>xsmall — width more than 480px</li><li>small — width more than 568px</li><li>medium — width more than 768px</li><li>large — width more than 1024px</li><li>xlarge — width more than 1200px</li></ul><p>So, if we want to make List block inset on tablet screens, now we need to add medium-inset class to it.</p><p>Same for Grid. Now we have more control on column sizes:</p><pre>&lt;div class=&quot;row&quot;&gt;<br>  &lt;div class=&quot;col-100 small-66 medium-50 large-25 xlarge-15&quot;&gt;<br>    ...<br>  &lt;/div&gt;<br>  ...<br>&lt;/div&gt;</pre><p>Same for Data Table, we can have more controls on which cells to show on different screen sizes:</p><pre>&lt;tr&gt;<br>  &lt;td&gt;...&lt;/td&gt;<br>  &lt;td&gt;...&lt;/td&gt;<br>  &lt;!-- show cell when screen width &gt;= 768px --&gt;<br>  &lt;td class=&quot;medium-only&quot;&gt;...&lt;/td&gt;<br>  &lt;!-- show cell when screen width &gt;= 1024px --&gt;<br>  &lt;td class=&quot;large-only&quot;&gt;...&lt;/td&gt;<br>&lt;/tr&gt;</pre><h3>iOS Translucent Bars &amp; Modals</h3><p>Framework7 v5 now supports translucent navigation bars (Navbar, Toolbar, Subnavbar, etc.) and modals (Dialog, Actions) for iOS theme and iOS devices from the box. And this is enabled by default.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FS2dBG7gIDwE%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DS2dBG7gIDwE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FS2dBG7gIDwE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0e2ebcf98e1510da35857a44c289fb9/href">https://medium.com/media/a0e2ebcf98e1510da35857a44c289fb9/href</a></iframe><p><strong>This can be a breaking change</strong> if you have custom bars colors, because in “translucent mode” it uses other CSS variables for that. So you can disable translucent bars and modals by disabling iosTranslucentBars and iosTranslucentModals app parameters.</p><pre>var app = new Framework7({<br>  iosTranslucentBars: false,<br>  iosTranslucentModals: false,<br>})</pre><h3>New Navbar Layout</h3><p><strong>This can be a breaking change</strong>, or at least if you don’t update it, it will look broken.</p><p>In v5 Navbar container must have new navbar-bg element that should be placed before navbar-inner, and new layout looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/36564dbbd109c81d99189fdda62f1366/href">https://medium.com/media/36564dbbd109c81d99189fdda62f1366/href</a></iframe><p>Large Navbar (Navbar with large title) now should be enabled by adding navbar-large class to Navbar element:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f492c93e52e1703fbabee4c526c222d1/href">https://medium.com/media/f492c93e52e1703fbabee4c526c222d1/href</a></iframe><p>Also, iOS theme’ dynamic Navbar behavior has been totally reworked. Now it doesn’t take navbar-inner from the page’s Navbar, but takes whole Navbar element. It makes it easier to customize each navbar (background color, text color, hairlines (borders), shadows) and such behavior brings better transitions between them.</p><h3>Large Transparent Navbar</h3><p>There is new “transparent” modification of Large Navbar. It makes Navbar and its behavior similar to what we have in Apple’s native apps in iOS 13.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQp0_IL6KFPk%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQp0_IL6KFPk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQp0_IL6KFPk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a49cfcea645354414e726f4c1d971c9d/href">https://medium.com/media/a49cfcea645354414e726f4c1d971c9d/href</a></iframe><p>To make large title transparent we need to add navbar-large-transparent class to large Navbar:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/182cd1a14ba16e5e04454ed4b3dd3be5/href">https://medium.com/media/182cd1a14ba16e5e04454ed4b3dd3be5/href</a></iframe><h3>Reworked “Statusbar” Layout</h3><p>Statusbar overlay element (&lt;div class=”statusbar”&gt;) and related functionality has been removed in favour of using that space by navigation bars and other elements to provide true full-screen experience and better customization.</p><p>Statusbar Cordova’s API is there as it was before.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJao09Nc5Cc8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJao09Nc5Cc8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJao09Nc5Cc8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6fb3f06ed1aa9fba0e5cf8c7913e46e/href">https://medium.com/media/c6fb3f06ed1aa9fba0e5cf8c7913e46e/href</a></iframe><h3>Improved Calendar</h3><p>Calendar got major improvements. Now it uses ECMAScript Internationalization API, specifically <a href="https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/DateTimeFormat">Intl.DateTimeFormat</a> (for date/time format, month names, day names, etc.).</p><p>Also, it has new features:</p><ul><li>New month picker functionality (clicking month name in toolbar will open month picker)</li><li>New year picker functionality (clicking year in toolbar will open year picker)</li><li>New time picker functionality (to select a time in addition to date)</li></ul><p>Check updated <a href="https://framework7.io/docs/calendar.html">Calendar Docs</a> and demo video below that is using system-related date-time format with month, year and time pickers:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1cj0e47ciS4%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1cj0e47ciS4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1cj0e47ciS4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d201eb397de7a85cb088e78d43717cc8/href">https://medium.com/media/d201eb397de7a85cb088e78d43717cc8/href</a></iframe><h3>New Text Editor Component</h3><p>Framework7 v5 comes with a new touch-friendly Rich Text Editor component. It is based on modern “contenteditable” API so it should work everywhere as is.</p><p>It comes with the basic set of formatting features. But its functionality can be easily extended and customized to fit any requirements.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FdKrujuSTz4Q%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DdKrujuSTz4Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FdKrujuSTz4Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/489c70ac2e7e62aaf95ed0c8de36634c/href">https://medium.com/media/489c70ac2e7e62aaf95ed0c8de36634c/href</a></iframe><h3>Push Popup</h3><p>There is a new “Push” Popup behavior. On open it will push View (or Views) behind. To enable it we just need to pass push:true to Popup parameters or by adding a popup-push class to Popup element.</p><p><em>This feature works only when top safe area is in place (e.g. when </em><em>safe-area-inset-top is more than 0). For example, when it is a full-screen iOS Cordova app or iOS app installed to home screen.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxMlZ_OSCHvI%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxMlZ_OSCHvI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxMlZ_OSCHvI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/58276d9ca80c42f36b626b83e112983e/href">https://medium.com/media/58276d9ca80c42f36b626b83e112983e/href</a></iframe><p>Also, it is possible to enable it on components that use Popup as a content opener. In components like Smart Select, Autocomplete, Color Picker, Photo Browser we can pass openIn: &#39;popup&#39; and popupPush: true to enable such “push” behavior.</p><h3>Push Sheet Modal</h3><p>As with Popup, there is a new “Push” Sheet Modal behavior. On open it will push View (or Views) behind. To enable it we just need to pass push:true to Sheet parameters or by adding a sheet-modal-push class to Sheet element.</p><p><em>This feature works only when top safe area is in place (e.g. when </em><em>safe-area-inset-top is more than 0). For example, when it is a full-screen iOS Cordova app or iOS app installed to home screen.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBrinDLzlxEM%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBrinDLzlxEM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBrinDLzlxEM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/41d4a02765ed340803e73c85faff6a33/href">https://medium.com/media/41d4a02765ed340803e73c85faff6a33/href</a></iframe><p>Also, it is possible to enable it on components that use Popup as a content opener. In components like Smart Select, Calendar, Picker, Color Picker we can pass openIn: &#39;sheet&#39; and sheetPush: true to enable such “push” behavior.</p><h3>Strong Segmented</h3><p>There is a new “strong” style for Segmented (buttons row) which is similar to native iOS 13 Segmented component:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHqlH9NRqKi8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHqlH9NRqKi8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHqlH9NRqKi8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e490ecb7f39eefc5c30afeafcc9e127/href">https://medium.com/media/9e490ecb7f39eefc5c30afeafcc9e127/href</a></iframe><h3>New Connection API</h3><p>There is a new simple Connection API that allows to determine if the app is connected to internet or not.</p><p>There is a new app.online property which is true when app is online and there are new online, offline and connection app events:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/67cdef58744d3e6ca0b4dd7317459ac1/href">https://medium.com/media/67cdef58744d3e6ca0b4dd7317459ac1/href</a></iframe><h3>No More Fast Clicks</h3><p>Fast Clicks library (to eliminate 300ms click delay) was disabled by default in Framework7 v4, and in version 5 this functionality has been completely removed as none of modern devices doesn’t need this fix anymore.</p><h3>Request.Promise</h3><p>There is a change in Request Promise API. Now it resolves and rejects with a different object. <strong>This can be a breaking change.</strong></p><ul><li>Request “promise” methods now will be resolved with { data, status, xhr } object (rather than with just data like before)</li><li>Request “promise” methods now will be rejected with { message, status, xhr } object (rather than with just status like before)</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d178e11064c49807832cf48fb1a22cae/href">https://medium.com/media/d178e11064c49807832cf48fb1a22cae/href</a></iframe><h3>Custom Page Transitions</h3><p>In addition to default theme-specific page transition it is now possible to create custom page transition or use one of the additional transition effects.</p><p>There are following additional custom page transitions built-in: f7-circle, f7-cover, f7-cover-v, f7-dive, f7-fade, f7-flip, f7-parallax, f7-push</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FO8QUUByx1AA%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DO8QUUByx1AA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FO8QUUByx1AA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e5eb991bbc546176682e1a58f0c33e25/href">https://medium.com/media/e5eb991bbc546176682e1a58f0c33e25/href</a></iframe><p>Check the <a href="https://framework7.io/docs/view.html#custom-page-transitions">Custom Page Transitions</a> docs for live examples and how to create custom ones.</p><h3>Reworked Panels</h3><p>Panels functionality has been fully reworked and now they behave more like a modals, which means we now can have as many panels as we want (or need) not limited to only 2 (left and right) panels.</p><p>Global app panel parameters (like panel.swipe = &#39;left&#39; ) are not supported anymore and now every panel must be initialized separately and panel parameters must be specified for each panel. And to make transition easier it is possible to auto init the Panel by adding panel-init class and specify panel parameters with data- attributes.</p><p>For example, if we have something like this in v4:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/36fb722be58eb5fdb497151b1b2b18d6/href">https://medium.com/media/36fb722be58eb5fdb497151b1b2b18d6/href</a></iframe><p>It must be changed to the following in v5:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e71925f1255791ac953d5aa867b0f711/href">https://medium.com/media/e71925f1255791ac953d5aa867b0f711/href</a></iframe><p>Also there is a new feature called collapsedBreakpoint where we can specify app width when Panel becomes partially visible.</p><p>Anyway, check updated <a href="https://framework7.io/docs/panel.html">Panel Docs</a> for new APIs and examples.</p><h3>New Swiper v5</h3><p>The best mobile touch slider became even better and Framework7 v5 comes with recently released Swiper v5. It has a bunch of new features and breaking changes. It is recommended to check <a href="https://github.com/nolimits4web/swiper/blob/master/CHANGELOG.md#swiper-500---released-on-september-17-2019">Swiper Changelog</a>.</p><p>The most interesting new feature is the new additional CSS Scroll Snap mode (can be enabled with cssMode: true). It doesn&#39;t support all of Swiper&#39;s features, but potentially should bring a much better performance in simple configurations. Check this <a href="https://swiperjs.com/demos/145-css-mode.html">CSS Scroll Snap live demo</a>.</p><h3>Router Component</h3><p>Core router components got a lot of improvements and new features.</p><p>First of all, it now supports async data (where it should return a Promise). This can be used if we need to load data before loading the component:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/25c9a1eb86eb93cfccc87d327e753ba3/href">https://medium.com/media/25c9a1eb86eb93cfccc87d327e753ba3/href</a></iframe><p>Component DOM updates are now asynchronous. It means that it is not guaranteed that DOM will be updated right after calling $setState. There is a new $tick method that can be safely used to reference DOM and ensure it was updated. Or we can now use new second callback argument in $setState</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/121d9a15eba8c84140bf548c0e7d97d8/href">https://medium.com/media/121d9a15eba8c84140bf548c0e7d97d8/href</a></iframe><p>Added support for mixins that can be re-used in components. Mixin can extend any component lifecycle hook, methods and data</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b0e6a7e4fe39387fc730c2e37006ffea/href">https://medium.com/media/b0e6a7e4fe39387fc730c2e37006ffea/href</a></iframe><p>Added support for new Class based syntax for better TypeScript support:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd6f8e21f9a5aa5123e8426104adcc04/href">https://medium.com/media/dd6f8e21f9a5aa5123e8426104adcc04/href</a></iframe><p>And support for custom reusable components:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/636c966ba8093cc979d14774feb93863/href">https://medium.com/media/636c966ba8093cc979d14774feb93863/href</a></iframe><h3>New Framework7 Icons v3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_e4s1ApiJhhCfrXH-9LNw.png" /><figcaption>Some of Framework7 Icons v3</figcaption></figure><p>As you could know, Apple recently released SF Symbols — collection of official icons for using in iOS apps.</p><p>Official icons are really great designed and the collection is huge. We took most of them for reference and updated icons collection in new version of Framework7 Icons v3.</p><p>Whole Framework7 Icons collection has grown from ~380 icons to 1200+ icons! Most of icons (that came from SF library) are renamed as they appear in SF Symbols. It can be not very clear now but should be fine when get used to it, for example:</p><ul><li>share &gt;square_arrow_up</li><li>delete &gt; minus</li><li>close &gt; xmark</li><li>add &gt; plus</li></ul><p><strong>This can be a breaking change</strong>, so take a look at new <a href="https://framework7.io/icons/">Framework7 Icons Cheatsheet</a> and update your icons with new ones.</p><h3>New Framework7 CLI v3</h3><p>Framework7 CLI was also update with the following new features:</p><ul><li>Generated app templates updated to Framework7 v5</li><li>Generated app templates updated to use Framework7 Icons v3</li><li>Update cordova backbuttonhandler. Now it will close opened modals (if available) or go back in navigation</li><li>Updated cordova-related scripts names, e.g. build-cordova-dev-&gt; build-dev-cordova</li><li>Added alias f7 for CLI command. Now we can run it like f7 create --ui</li></ul><p>CLI User Interface (--ui) updates:</p><ul><li>Added new Text Editor to custom build settings</li><li>Added options to include/exclude Dark and Light themes in custom build</li><li>Added ability to import project setting from JSON file</li><li>Added ability to export project setting to JSON file</li></ul><h3>Deprecating Templates</h3><p>All official Framework7 templates are deprecated now (will not be supported) in favour of Framework7 CLI which provides a much more flexible and up to date setup.</p><h3>What Is Next?</h3><p>That was just a brief overview of most significant changes.</p><p>There are also a lot of minor improvements and fixes across whole Framework7. For all changes list please refer to <a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md">full v5 changelog</a> which can also be helpful for migration from previous version.</p><p>As next steps it is recommended to check the following new and updated Framework7 v5 docs:</p><ul><li><a href="https://framework7.io/docs/panel.html">Panel docs</a> — for new Panel APIs and usage</li><li><a href="https://framework7.io/docs/grid.html">Layout Grid docs</a> — for new responsive breakpoints reference</li><li><a href="https://framework7.io/docs/calendar.html">Calendar docs</a> — for new Internationalization based APIs</li><li><a href="https://framework7.io/docs/router-component.html">Router Component docs</a> — for all the new things about with mixins and custom components</li><li><a href="https://framework7.io/docs/view.html#custom-page-transitions">Custom Page Transitions docs</a> — to know how to use and create own custom page transitions</li><li><a href="https://framework7.io/docs/navbar.html">Navbar docs</a> — for reference to new Navbar layout and new styles</li><li><a href="https://framework7.io/docs/text-editor.html">Text Editor docs</a> — for new Rich Text Editor</li><li><a href="https://swiperjs.com/api/">Swiper API</a> — for new Swiper v5 API</li><li><a href="https://framework7.io/icons/">Framework7 Icons Cheatsheet</a> — for new v3 icons</li></ul><p>And docs in general:</p><ul><li><a href="http://framework7.io/docs/">Framework7 Core documentation</a></li><li><a href="http://framework7.io/vue/">Framework7-Vue documentation</a></li><li><a href="http://framework7.io/react/">Framework7-React documentation</a></li><li><a href="http://forum.framework7.io/">Framework7 Forum</a> — the best place to get F7 support.</li></ul><h3>P.S.</h3><p>If you love Framework7, please, support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a></p><p>Your support means a lot for us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=679176716faa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-v5-679176716faa">Framework7 v5</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framework7 4.4.0 — Treeview]]></title>
            <link>https://medium.com/framework7/framework7-4-4-0-treeview-1616c2fec4b0?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/1616c2fec4b0</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Mon, 13 May 2019 15:52:33 GMT</pubDate>
            <atom:updated>2021-07-24T16:18:16.257Z</atom:updated>
            <content:encoded><![CDATA[<h3>Framework7 4.4.0 — Treeview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBP8XBzlOhWOG2h9hPtWCw.png" /></figure><p>I am glad to introduce new 4.4.0 Framework7 update with lots of new features and improvements.</p><h3>All New Treeview Component</h3><p>This was asked for a while, and it is finally here. All new Treeview component, which will be a great improvement for desktop apps.</p><h3>Framework7 on Twitter</h3><p>All new Treeview component coming soon in Framework7 v4.4.0🔥 https://t.co/Ppalw7dYKz</p><h3>Checkboxes With Indeterminate State</h3><p>Simple but very useful Checkboxes UI improvement with new indeterminate state, which fits great when used in Treeview or in Data Tables:</p><h3>Framework7 on Twitter</h3><p>Checkboxes with indeterminate state coming soon to Framework7 ✅ https://t.co/9wPlmvYsWR</p><h3>Swipe To Close Popup</h3><p>One more requested feature — is the ability to close Popups with swipes. Now it is here:</p><h3>Framework7 on Twitter</h3><p>And you for sure was asking for Popups with &quot;swipe-to-close&quot; feature! Here it comes, also in 4.4.0 🎉 https://t.co/iZFUkXGCfs</p><h3>Swipeable Sheet Modals</h3><p>This was asked a lot from Framework7 community. Sheet modals now can be also closed with swipe. But more important, there is a new “swipe-to-step” functionality, which is used a lot in native apps. When it is enabled, sheet modal will be opened for some specific size that later can be further expanded with swipe gesture:</p><h3>Framework7 on Twitter</h3><p>And we didn&#39;t forget about swipeable sheets😎 https://t.co/Gwi1tKZktc</p><h3>Autcomplete with Keyboard</h3><p>Autocomplete got few desktop improvements.</p><p>Now, it is possible to select autocomplete dropdown value with keyboard UP and DOWN keys and confirm selection with ENTER — which is pretty straightforward behavior for desktop apps. Also, dropdown will be closed with keyboard ESC key:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsH7rvnX8ncXA5Q0eOoPZw.png" /></figure><h3>Release</h3><p>Framework7 4.4.0 version already released with all the documentation updated. Check the following links for more details:</p><ul><li><a href="https://framework7.io/docs/treeview.html">Treeview Documentation</a></li><li><a href="https://framework7.io/docs/sheet-modal.html">Updated Sheet Modal Documentation</a></li><li><a href="https://framework7.io/docs/popup.html">Updated Popup Documentation</a></li><li><a href="https://framework7.io/docs/checkbox.html">Updated Checkboxes Documentation</a></li><li><a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md">Full 4.4.0 Changelog</a></li></ul><h3>P.S.</h3><p>If you love Framework7, you can support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a> or by purchasing a nice branded t-shirt at <a href="https://teespring.com/stores/framework7">Framework7 Shop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1616c2fec4b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-4-4-0-treeview-1616c2fec4b0">Framework7 4.4.0 — Treeview</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framework7 4.3.0 — The Most Colorful Update]]></title>
            <link>https://medium.com/framework7/framework7-4-3-0-the-most-colorful-update-47175a880c5e?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/47175a880c5e</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[framework7]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 07:13:12 GMT</pubDate>
            <atom:updated>2021-07-24T16:18:44.123Z</atom:updated>
            <content:encoded><![CDATA[<h3>Framework7 4.3.0 — The Most Colorful Update</h3><p>Large Framework7 update, again :) This time, there are new UI components, a lot of tweaks and improvements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nx-78i1maLq1TXgIt3JQww.png" /></figure><h3>Color Picker</h3><p>Yes, finally! One of the most requested components has been arrived. 4.3.0 update introduces all new ultimate modular Color Picker component!</p><p>With its modular structure and custom modules support you can create limitless combinations of color picker controls.</p><p>It comes with the following modules:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nH5aK9wzTEW9o8r0ezbgbg.png" /></figure><p>And you can create color pickers with any combinations of these modules. Here is the demo from Kitchen Sink:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*PmeT2piTSoH7nrAdUjQuWg.gif" /></figure><h3>Resizable Side Panels</h3><p>One more requested feature landed. We continue to improve desktop experience and now side panels can be resizable! And it is super easy to enable it, just add panel-resizable class to panel element (or pass resizable=true prop to React/Vue panel component) and that is it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ZXjC8IStUXOEyFF3lsYkoQ.gif" /></figure><h3>Automatic Dark Theme</h3><p>Now Framework7 can automatically enable/disable dark theme based on user system color scheme preference. This feature is based on prefers-color-scheme media query, which is <a href="https://caniuse.com/#feat=prefers-color-scheme">not widely supported</a> yet, but already implemented in latest versions of Safari and FireFox, and coming to Chrome in upcoming versions.</p><p>To enable this feature we need to pass autoDarkTheme: true parameter on app init:</p><pre>var app = new Framework7({<br>  autoDarkTheme: true,<br>  // ...<br>});</pre><p>This is how it works (when we switch system color scheme it applies same scheme in the app):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Sr7M1fnnWXULXxfDAQoSdQ.gif" /></figure><h3>Navbar Events</h3><p>Now Navbar emits the following events that can be useful to detect its state change:</p><ul><li>navbar:hide / navbarHide — event will be triggered when Navbar becomes hidden</li><li>navbar:show / navbarShow — event will be triggered when Navbar becomes hidden</li><li>navbar:collapse / navbarCollapse — event will be triggered when Navbar with large title collapsed (from large navbar to usual navbar)</li><li>navbar:expand / navbarExpand — event will be triggered when Navbar with large title expanded (from usual navbar to large navbar)</li></ul><h3>Close Modals With “Esc” Key</h3><p>One more desktop experience improvement. Now all modals (Popup, Popover, Sheet Modal, Actions Sheet) can be closed with ESC keyboard key. To enable this feature, we need to pass closeOnEscape: true when we create modal, for example:</p><pre>var popup = app.popup.create({<br>  closeOnEscape: true,<br>  // ...<br>})</pre><h3>Modals Backdrop Improvement</h3><p>There is some minor but pretty useful improvement with modals backdrop (semi-transparent dark overlay behind the modal). Now when app running in cordova environment and there is a cordova keyboard plugin installed:</p><ul><li>Clicking on modal backdrop won’t close modal if virtual keyboard was opened. More likely user expects here to close the keyboard rather than modal.</li><li>Closing/opening virtual keyboard will correctly reposition currently opened Popover</li></ul><h3>Top Sheet Modal</h3><p>By default sheet modal opens from the bottom of the screen. Now it is also possible to open it from the top of the screen. In this case we just need to add sheet-modal-top class to sheet element.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*gBE5c-hQIdzu_9pRyuqowQ.gif" /></figure><h3>Time To Update</h3><p>Framework7 4.3.0 version already released with all the documentation updated. Check the following links for more details:</p><ul><li><a href="https://framework7.io/docs/color-picker.html">Color Picker documentation</a></li><li><a href="https://framework7.io/docs/sheet-modal.html#sheet-top-layout">Top Sheet Modal documentation</a></li><li><a href="https://framework7.io/docs/panel.html#resizable-panel">Resizable Panels documentation</a></li><li><a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md">Full 4.3.0 Changelog</a></li></ul><h3>P.S.</h3><p>If you love Framework7, you can support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a> or by purchasing a nice branded t-shirt at <a href="https://teespring.com/stores/framework7">Framework7 Shop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47175a880c5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/framework7-4-3-0-the-most-colorful-update-47175a880c5e">Framework7 4.3.0 — The Most Colorful Update</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Aurora — New Framework7 Desktop Theme]]></title>
            <link>https://medium.com/framework7/meet-aurora-new-framework7-desktop-theme-b4064c5b6040?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/b4064c5b6040</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 13:31:09 GMT</pubDate>
            <atom:updated>2021-07-24T16:18:55.313Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet Aurora — New Framework7 Desktop Theme</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DWE6w9DyDXK0VM8mj_1_w.png" /></figure><p>With modern web technologies we can build any kind of apps: native mobile apps (with Cordova or WebView), web apps, progressive web apps, native desktop apps (with Electron). And Framework7 with its unreachable set of ready to use components and UI is a great choice for all of them.</p><p>But when it comes to native desktop apps and desktop-related features, it could be hard to choose what fits better — iOS or MD theme, and this is the area where Framework7 could lack a little bit, becoming not so obvious choice for desktop apps.</p><p>And now, there is a solution for desktop apps.</p><h3>Aurora</h3><p>So here comes the <strong>Aurora</strong> — <strong>all new desktop theme which is now a part of the Framework7 and available from Framework7 4.2.0</strong>.</p><p>We have <strong>redesigned and tweaked each and every component in Aurora theme</strong> to look, feel and behave better in desktop apps.</p><p>Main idea of Aurora theme is to provide styles more closer to what we have in desktop apps, so using this theme should require a much less efforts to customize it.</p><p>We decided to go with some none-relevant name rather than call it Desktop to avoid confusing with “desktop” as device/platform in API and styles.</p><p>Here is a sneak peak of what you can quickly build with Aurora:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMoam_HJbGuo8MW4rmQZmg.png" /><figcaption>macOs Mail app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3b00qz9LDZteHiVjfcN4Q.png" /><figcaption>Whatsapp desktop app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8455YMhD0OJZdVoO6Qn-Q.png" /><figcaption>Desktop Slack app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohU9Lqh3vmftbvYycGEQaA.png" /><figcaption>Google Chrome</figcaption></figure><p>All these Aurora demo layouts available in <a href="https://github.com/framework7io/framework7-recipes">Framework7 Recipes</a> repository where you can see them live.</p><h3>Enable Aurora</h3><p>To enable Aurora theme we just need to specify theme: &#39;aurora&#39; in app parameters:</p><pre>new Framework7({<br>  theme: &#39;aurora&#39;,<br>})</pre><p>In case if we have theme: &#39;auto&#39; Aurora will be enabled automatically only if app runs under <a href="https://electronjs.org/">Electron</a> environment.</p><h3>API Changes</h3><p>There is no any breaking changes, but there is a bunch of new aurora-related parameters and properties added to components.</p><p>All app’s and components’ theme-related parameters that were prefixed with theme name, like app.touch.iosTouchRipple, view.iosSwipeBack, navbar.mdCenterTitle, now available with aurora prefix, e.g. auroraTouchRipple, auroraSwipeBack, auroraCenterTitle, etc.</p><p>All buttons and same kind modifier classes and component props are also available with aurora suffix, e.g. button-round-aurora makes button round only in Aurora theme.</p><h3>Theme Conditional Rendering</h3><p>In Framework7 Vue and React, and in Framework7 Router Components we use this.$theme.ios and this.$theme.md to differentiate theme-based output. Now, if you develop with Aurora theme, you also need to consider this.$theme.aurora property that will be true for this theme.</p><p>In Framework7 Core html templates we used if-ios/ios-only and if-md/md-only classes on elements that were automatically removed (or hidden) if other theme in use. With Aurora release this set of classes expands to:</p><ul><li>if-ios — element will be rendered only for iOS theme</li><li>if-not-ios — element will be removed/hidden for theme other than iOS</li><li>if-md — element will be rendered only for MD theme</li><li>if-not-md — element will be removed/hidden for theme other than MD</li><li>if-aurora — element will be rendered only for Aurora theme</li><li>if-not-aurora — element will be removed/hidden for theme other than Aurora</li></ul><p>So, in previous versions when we had only two themes, we used the following code to hide Navbar’s back button text for MD theme:</p><pre>&lt;div class=&quot;navbar&quot;&gt;<br>  &lt;div class=&quot;navbar-inner sliding&quot;&gt;<br>    &lt;div class=&quot;left&quot;&gt;<br>      &lt;a href=&quot;#&quot; class=&quot;link back&quot;&gt;<br>        &lt;i class=&quot;icon icon-back&quot;&gt;&lt;/i&gt;<br>        &lt;span class=&quot;if-ios&quot;&gt;Back&lt;/span&gt;<br>      &lt;/a&gt;<br>    &lt;/div&gt;<br>    ...<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><p>But now this code will also hide back button text in Aurora theme. So if we develop for Aurora theme too, we need to change it to:</p><pre>&lt;div class=&quot;navbar&quot;&gt;<br>  &lt;div class=&quot;navbar-inner sliding&quot;&gt;<br>    &lt;div class=&quot;left&quot;&gt;<br>      &lt;a href=&quot;#&quot; class=&quot;link back&quot;&gt;<br>        &lt;i class=&quot;icon icon-back&quot;&gt;&lt;/i&gt;<br>        &lt;span class=&quot;if-not-md&quot;&gt;Back&lt;/span&gt;<br>      &lt;/a&gt;<br>    &lt;/div&gt;<br>    ...<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><h3>Picker With Mousewheel</h3><p>Just having only a desktop look is not enough. You know Framework7&#39;s attention to details is outstanding. So many components tweaked to also behave better on desktop.</p><p>Picker was basically one of the touch-only and absolutely not mouse-friendly component. Now it is possible to scroll Picker values with mousewheel, which is now enabled by default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*yYl9t-SYJIqGEJt9ae1GwA.gif" /></figure><h3>Pull To Refresh With Mousewheel</h3><p>One more no-go for desktops feature and component can work now with mousewheel. To enable it we just need to add data-ptr-mousewheel=&quot;true&quot; attribute to PTR content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*7VkhaL-h_a-Yx36iV5FYng.gif" /></figure><h3>Hovers</h3><p>And of course hovers. Buttons, List Buttons and List Links have hover effect in Aurora theme:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*9GwAL084jU2yvjG5rniDZg.gif" /></figure><h3>New Appbar Component</h3><p>Aurora comes with new Appbar component which is designed to be used in desktop apps with Aurora theme. It is the main app bar, which looks mostly the same as Navbar/Toolbar, with actions on top of the whole app.</p><p>For example, in macOs Mail demo app layout you can see two Appbars on top of the app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMoam_HJbGuo8MW4rmQZmg.png" /><figcaption>macOs Mail app with two Appbars on top</figcaption></figure><h3>Inline Searchbar</h3><p>This is a new Searchbar modification that comes in 4.2.0 update. It has a bit simplified layout and, as title says, it made to be easier integrated into other components and custom layouts. Like, for example, into the Appbar in macOs Mail app demo layout above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*dYuKkiNEJrtiFoeWI8gjig.png" /><figcaption>Inline Searchbar in Appbar</figcaption></figure><h3>Conclusion</h3><p>Framework7 was originally developed as a mobile-only framework. First version of Framework7 was released exactly 5 years ago 🎉 and during this period of time it became unreachable in terms of UI quality. And Aurora, is our 5 years celebration of Framework7, Aurora — is our huge next step — step towards desktop apps to make Framework7 even more cross-platform friendly! All of this wouldn’t happen without you — app developers!</p><p>You can already try Aurora theme right now by updating your Framework7 version to 4.2.0.</p><p>This release contains a lot more new micro features, fixes and improvements. Check the <a href="https://github.com/framework7io/framework7/blob/master/CHANGELOG.md">full changelog</a> for more details.</p><p>As next steps it is recommended to check:</p><ul><li><a href="http://framework7.io/docs/">Framework7 Aurora-updated docs</a></li><li><a href="http://forum.framework7.io/">Framework7 Forum</a> — the best place to get F7 support</li><li>New <a href="https://github.com/framework7io/framework7-recipes">Framework7 Recipes</a> repository with new Aurora demo layouts</li></ul><h3>P.S.</h3><p>If you love Framework7, you can support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a> or by purchasing a nice branded t-shirt at <a href="https://teespring.com/stores/framework7">Framework7 Shop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4064c5b6040" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/meet-aurora-new-framework7-desktop-theme-b4064c5b6040">Meet Aurora — New Framework7 Desktop Theme</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migration To Framework7 v4]]></title>
            <link>https://medium.com/framework7/migration-to-framework7-v4-89d1ce49f4c0?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/89d1ce49f4c0</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 11:47:42 GMT</pubDate>
            <atom:updated>2021-07-24T16:19:10.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0NDu0gguq4ZqzGg9Cl-fw.png" /></figure><p>Framework7 stable 4.0.0 released on February 7, 2019 and it is time to update!</p><p>Do you need to update? Framework7 v4 targets modern devices with CSS Custom Properties support. So if your app targets old iOS (&lt; 10) and Android (&lt; 5) devices, or other <a href="https://caniuse.com/#feat=css-variables">platforms that don’t support this technology</a>, then you shouldn’t migrate.</p><p>Let’s walk through all v3 -&gt; v4 breaking changes to see what needs to be changed to upgrade your app to new Framework7 v4.</p><h3>Framework7 Core Files Structure</h3><p><strong>If you are using ES-modules then you can skip this section, nothing has changed here.</strong></p><p>Core JS and CSS files have been renamed and restructured a bit, so you need to rename them to new files in your &lt;link href=&quot;...&quot;&gt; and &lt;script src=&quot;...&quot;&gt; tags to the following ones:</p><pre>framework7.css -&gt; framework7.bundle.css<br>framework7.min.css -&gt; framework7.bundle.min.css<br>framework7.lazy.css -&gt; framework7.css<br>framework7.lazy.min.css -&gt; framework7.min.css</pre><pre>framework7.js -&gt; framework7.bundle.js<br>framework7.min.js -&gt; framework7.bundle.min.js<br>framework7-lazy.js -&gt; framework7.js<br>framework7-lazy.min.js -&gt; framework7.min.js</pre><p>And RTL stylesheets:</p><pre>framework7.rtl.css -&gt; framework7.bundle.rtl.css<br>framework7.rtl.min.css -&gt; framework7.bundle.rtl.min.css<br>framework7.lazy.rtl.css -&gt; framework7.rtl.css<br>framework7.lazy.rtl.min.css -&gt; framework7.rtl.min.css</pre><p>Theme-specific stylesheets are gone now, so there is no more these files:</p><pre>framework7.ios.css<br>framework7.md.css<br>framework7.ios.rtl.css<br>framework7.md.rtl.css</pre><h3>CSS Custom Properties (CSS Variables)</h3><p>This is the most significant and most complex part of new update. All CSS styles were reworked to use <a href="https://developer.mozilla.org/docs/Web/CSS/Using_CSS_variables">CSS Variables (Custom Properties)</a>. It shouldn’t break any default styles that were in v3. But if you have a lot of custom styles, then some of them may become invalid. In v4, it is recommended to do custom styling with CSS Custom properties.</p><p>New documentation has reference for each component’s CSS variables, like, for example, on this <a href="http://framework7.io/docs/button.html#css-variables">Button CSS variables docs</a>. There is also <a href="http://framework7.io/docs/css-variables.html">reference of all available CSS variables</a>.</p><h3>Unified Toolbars Position</h3><p>In both iOS and MD themes Toolbar / Tabbar can now be positioned on top or on bottom. And now it is always required to add position-specific class to each Toolbar/Tabbar:</p><ul><li>toolbar-top to place Toolbar on top of view/page</li><li>toolbar-bottom to place Toolbar on bottom of view/page</li></ul><h3>Buttons</h3><p>big button modifier renamed to large in v4:</p><pre>&lt;button class=&quot;button button-big&quot;&gt;...&lt;/button&gt;<br>&lt;f7-button big&gt;...&lt;/f7-button&gt;</pre><pre>&lt;!-- need to be changed to --&gt;</pre><pre>&lt;button class=&quot;button button-large&quot;&gt;<br>&lt;f7-button large&gt;...&lt;/f7-button&gt;</pre><p>All buttons modifiers (raised, outline, fill, small, large) now supported in both iOS and MD themes in same way. For example the “raised” button which worked only in MD theme before will become “raised” in iOS theme as well. So don’t forget to tweak this behavior.</p><h3>Fast Clicks Disabled</h3><p>Fast clicks, the built-in library that removes 300ms delay from links and form elements in mobile browser while you click them, is now disabled by default to avoid unnecessary issues, especially with 3rd party libraries. And it must be enabled if you target older devices, like iOS &lt; 10, with touch.fastClicks: true app’s parameter.</p><h3>Safe Areas</h3><p>To handle device’s safe-areas correctly there were special ios-edges classes. This is not iOS-only feature anymore so these classes are renamed too:</p><pre>ios-edges -&gt; safe-areas<br>ios-left-edge -&gt; safe-area-left<br>ios-right-edge -&gt; safe-area-right<br>no-ios-edges -&gt; no-safe-areas<br>no-ios-left-edge -&gt; no-safe-area-left<br>no-ios-right-edge -&gt; no-safe-area-right</pre><p>You can read more about these classes in <a href="http://framework7.io/docs/safe-areas.html">Safe Areas documentation</a>.</p><h3>Unified Navigation Bars Styling</h3><p>In v4 we unified color scheme for navigation bars (Navbar, Toolbar, Subnavbar) in iOS and MD themes. So you need to check and make required styles tweaks if it breaks your custom styles.</p><h3>New Framework7 Icons</h3><p>Framework7 v4 is intended to be used with Framework7 Icons v2. So if you use this icon font, then you need to update it to latest version too. Check <a href="https://blog.framework7.io/framework7-icons-v2-1bb74ef5055a">this blog post</a> to learn more about new icons font.</p><h3>Framework7 React &amp; Vue Components Changes</h3><p>f7-label / Label component has been removed. It was used together with f7-input / Input component to create inputs in List View. Now instead of that component, we need use new f7-list-input / ListInput that was recently introduced in latest versions of Framework7 v3.</p><p>So if you have something like this (for example in Vue):</p><pre>&lt;f7-list-item&gt;<br>  &lt;f7-label&gt;Name&lt;/f7-label&gt;<br>  &lt;f7-input<br>    type=&quot;text&quot;<br>    :value=&quot;userName&quot;<br>    placeholder=&quot;Your name&quot;<br>    <a href="http://twitter.com/input">@input</a>=&quot;updateUserName&quot;<br>  /&gt;<br>&lt;/f7-list-item&gt;</pre><p>It needs to be changed to new single component:</p><pre>&lt;f7-list-input<br>  label=&quot;Name&quot;<br>  type=&quot;text&quot;<br>  :value=&quot;userName&quot;<br>  placeholder=&quot;Your name&quot;<br>  <a href="http://twitter.com/input">@input</a>=&quot;updateUserName&quot;<br>/&gt;</pre><h3>This Is It</h3><p>Yes, there is not so much breaking changes here, but there are a lot of new features. Check <a href="https://blog.framework7.io/the-best-framework7-yet-what-is-new-in-v4-74b2b467047c">What Is New In v4</a> blog post if you missed it.</p><p>As next steps it is highly recommended to check all new Framework7 v4 docs and:</p><ul><li><a href="http://framework7.io/docs/">Framework7 Core documentation</a></li><li><a href="http://framework7.io/vue/">Framework7-Vue documentation</a></li><li><a href="http://framework7.io/react/">Framework7-React documentation</a></li><li><a href="http://forum.framework7.io/">Framework7 Forum</a> — the best place to get F7 support.</li></ul><h3>P.S.</h3><p>If you love Framework7, you can support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a> or by purchasing a nice branded t-shirt at <a href="https://teespring.com/stores/framework7">Framework7 Shop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89d1ce49f4c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/migration-to-framework7-v4-89d1ce49f4c0">Migration To Framework7 v4</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Framework7 Yet. What Is New In v4]]></title>
            <link>https://medium.com/framework7/the-best-framework7-yet-what-is-new-in-v4-74b2b467047c?source=rss----902810cfed8---4</link>
            <guid isPermaLink="false">https://medium.com/p/74b2b467047c</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[framework7]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Vladimir Kharlampidi]]></dc:creator>
            <pubDate>Wed, 16 Jan 2019 15:13:12 GMT</pubDate>
            <atom:updated>2021-07-24T16:19:25.016Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EG3AIQxDsfdMknFK-EbaBw.png" /></figure><p>Time for big release, the <strong>largest Framework7 update</strong> in terms of new features is coming soon.</p><p>Let’s look at new features and breaking changes coming in version 4 and what to expect with migrating your existing app from v2/v3 to v4.</p><h3>Core Framework7 Files Structure</h3><p>Core framework has new file structure. In previous version (v3) we had the following:</p><pre>| components/<br>  |  /accordion/<br>  |  /actions/<br>  |  /calendar/<br>  |  ...<br>| lazy-components/<br>  |  accordion.css<br>  |  accordion.js<br>  |  actions.css<br>  |  actions.js<br>  |  calendar.css<br>  |  calendar.js<br>  |  ...<br>| js/<br>  |  framework7-lazy.js<br>  |  framework7-lazy.min.js<br>  |  framework7.js<br>  |  framework7.min.js<br>| css/<br>  |  framework7-lazy.css<br>  |  framework7-lazy.min.css<br>  |  framework7-lazy.rtl.css<br>  |  framework7-lazy.rtl.min.css<br>  |  framework7.css<br>  |  framework7.min.css<br>  |  framework7.rtl.css<br>  |  framework7.rtl.min.css<br>  |  framework7.ios.css<br>  |  framework7.md.css<br>  |  ...<br>| framework7.esm.bundle.js<br>| framework7.esm.js<br>| framework7.less<br>| framework7.less</pre><p>In new version file structure is more consistent and a bit different:</p><pre>| components/<br>  |  /accordion/<br>  |  accordion.css<br>  |  accordion.js<br>  |  /actions/<br>  |  actions.css<br>  |  actions.js<br>  |  /calendar/<br>  |  calendar.css<br>  |  calendar.js<br>  |  ...<br>| js/<br>  |  framework7.bundle.js<br>  |  framework7.bundle.min.js<br>  |  framework7.js<br>  |  framework7.min.js<br>| css/<br>  |  framework7.bundle.css<br>  |  framework7.bundle.min.css<br>  |  framework7.bundle.rtl.css<br>  |  framework7.bundle.rtl.min.css<br>  |  framework7.css<br>  |  framework7.min.css<br>  |  framework7.rtl.css<br>  |  framework7.rtl.min.css<br>| framework7.esm.bundle.js<br>| framework7.esm.js<br>| framework7.bundle.less<br>| framework7.less</pre><p>Before: Files with -lazy suffix in name contain minimal (core) Framework7 version with minimal required set of components. Files without -lazy suffix contain full bundle Framework7 version with all components.</p><p>In v4: Minimal core version now comes without any suffix and it is just framework7.js and framework7.css (what was with -lazy before). Full bundle version now has bundle in file name.</p><p>Browser lazy components that were in lazy-components/ folder moved to the root of components folder.</p><p>Theme-specific styles like framework7.ios.css removed and not available anymore because it is not really necessary now (explanation in next section).</p><h3>CSS Variables (Custom Properties)</h3><p>This is the most significant and most complex part of new update. All CSS styles were reworked to use <a href="https://developer.mozilla.org/docs/Web/CSS/Using_CSS_variables">CSS Variables (Custom Properties)</a>. So why it was needed? Here is some awesome advantages of moving to CSS variables:</p><ul><li>It allowed us to reduce size of whole Framework7 bundle by 60%! Unminified CSS bundle reduced from ~1MB (in v3) to 400Kb (in v4)!</li><li>We were able to reduce amount of JS code as well. Some new features like Large Navbars became available due to CSS variables without significant extra amount of JavaScript.</li><li>A lot of theme-specific differences we had before now unified, that will make app branding a way more simpler.</li><li>It is extremely easy to add new and modify existing colors, theme colors and color modifiers.</li><li>For some components it is now possible to mix theme styling. For example, if you use iOS theme and want button to appear in style of MD theme, we can just add md class to this button and it will look like in MD theme.</li></ul><p>Custom styling became much more easier with CSS variables. The stunning part here is that we don’t need to know the exact HTML markup of the component we want to style if CSS variables available for this component. For example, if we need to change font-size of List Item’s title, we can just add to CSS:</p><pre>:root {<br>  --f7-list-item-title-font-size: 20px;<br>}</pre><p>If we need to change Navbar’s height:</p><pre>:root {<br>  --f7-navbar-height: 80px;<br>}</pre><p>And in this case all Navbar-size dependent styles (rules that depend on this CSS variable) will be updated automatically (e.g. page-content paddings, transformations, etc.).</p><p>CSS variables just make developer life easier.</p><p>But there are some drawbacks of moving to CSS variables. And the most noticeable, is their support in browsers. Like we may see from <a href="https://caniuse.com/#feat=css-variables">this table</a> it is supported on:</p><ul><li>Edge 16+</li><li>iOS Safari 10+</li><li>Chrome — means Android 5+</li><li>FireFox</li></ul><p>What it means? It means that Framework7 v4 will not work on browsers older than mentioned above. And here we come to Framework7 v4+ ideology.</p><h3>Supported Browsers &amp; Devices</h3><p>Due to CSS variables and some other legacy features removed in v4, it will be the framework for modern devices. No IE and Android &lt;5 support at all! Supporting such old browsers just holds us back in terms of new features development and framework evolution, so no more old browsers.</p><p>Framework7 v3 will be maintained for a while (bug fixes) for the apps needed old devices support.</p><h3>Color Themes</h3><h3>Framework7 on Twitter</h3><p>How about ... generating custom color themes right in Kitchen Sink. Coming in @framework7io v4 🔥 https://t.co/E8JoKcg8PF</p><p>Working with color themes in v4 is like a breath of fresh air. Now if you need to change default color theme, you just need to specify few CSS variables instead of modifying/overwriting all default color references in whole CSS file. We need 4 CSS variables:</p><ul><li>--f7-theme-color — HEX value of theme color.</li><li>--f7-theme-color-shade — 8% darken theme color. Required, for example, for pressed buttons state.</li><li>--f7-theme-color-tint — 8% lighten theme color. Required, for example, for pressed buttons state.</li><li>--f7-theme-color-rgb — RGB value of theme color. Required for semitransparent elements.</li></ul><p>For example, if our brand color is #f00 (red) we just need to add following variables to our CSS:</p><pre>:root {<br>  --f7-theme-color: #f00;<br>  --f7-theme-color-shade: #d60000;<br>  --f7-theme-color-tint: #ff2929;<br>  --f7-theme-color-rgb: 255, 0, 0;<br>}</pre><p>That is all we need to create custom color theme!💥</p><p>There is also new colorThemeCSSProperties util that can generate required CSS variables:</p><pre>/* Generate CSS variables for red theme color */</pre><pre>app.utils.colorThemeCSSProperties(&#39;#f00&#39;);</pre><p>It will return the following object:</p><pre>{<br>  &quot;--f7-theme-color&quot;: &quot;#f00&quot;,<br>  &quot;--f7-theme-color-rgb&quot;: &quot;255, 0, 0&quot;,<br>  &quot;--f7-theme-color-shade&quot;: &quot;#d60000&quot;,<br>  &quot;--f7-theme-color-tint&quot;: &quot;#ff2929&quot;<br>}</pre><h3>Unified Navigation Bars</h3><p>There is also unification in navigation bars (Navbars, Toolbars, Subnavbar, etc.) appearance. In v3 their color scheme is different for iOS and MD themes. This brings complications and a bunch of extra styles when we need to bring custom branding.</p><p>In v3 they look like on the following picture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-hDTsenwdQGmuYeoNVHgg.png" /><figcaption>Navigation Bars in v3</figcaption></figure><p>In v4 we unified color scheme for navigation bars in iOS and MD themes to the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCLIAVqfriplTRdrvLkcEg.png" /><figcaption>Navigation Bars in v4</figcaption></figure><p>With such scheme it is much easier to bring your custom branding for navigation bars.</p><p>Also Navbar with centered title (and with its dynamically calculated position) is also available in MD theme now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3JJnLGSacaplWRn5OiUAg.png" /><figcaption>Centered Navbar Title in iOS &amp; MD Themes</figcaption></figure><h3>Unified Toolbars Position</h3><p>Before v4 we had the following restrictions for Toolbar position:</p><ul><li>in iOS theme, Toolbar is always on the bottom</li><li>in MD theme, Toolbar by default is on the top, and can be positioned on bottom with extra toolbar-bottom-md class.</li></ul><p>Now such restriction is gone and in both themes Toolbar / Tabbar can be positioned on top or on bottom. But now it is always required to add position-specific class to each Toolbar/Tabbar:</p><ul><li>toolbar-top to place Toolbar on top of view/page</li><li>toolbar-bottom to place Toolbar on bottom of view/page</li></ul><p>Again, it also should help to keep your custom styles/branding in consistence across iOS and MD themes.</p><p>So even on iOS, Toolbar can be easily positioned on top:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*MzHcZcfrGKS2t20cepdBJw.png" /><figcaption>Top Tabbar in v4 iOS theme</figcaption></figure><h3>Unified &amp; Reworked Buttons</h3><p>With the arrival of CSS variables, Buttons now also support all modifiers for both iOS and MD themes. For example, “raised” button now supported by iOS theme and “outline” button supported by MD theme.</p><p>Also “button-big” has been renamed to “button-large”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dt6Z8e8lmh46b7JfEg4O5A.png" /></figure><h3>Unified Messages Colors</h3><p>Messages component now has similar color scheme for both iOS &amp; MD themes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYY394W75z7paHVt8syCqQ.png" /><figcaption>Messages color scheme in v4</figcaption></figure><h3>Navbar Goes Large</h3><p>This is one of the most requested features in Framework7. And now it is available in v4 for both iOS and MD themes.</p><h3>Framework7 on Twitter</h3><p>You have asked for it, you will get it! Meet all new large navbars with proper transitions coming in @framework7io v4 🎊 https://t.co/IUhi46Cw1Q</p><p>HTML markup for large navbar is pretty simple:</p><pre>&lt;div class=&quot;navbar&quot;&gt;<br>  &lt;div class=&quot;navbar-inner&quot;&gt;<br>    &lt;div class=&quot;left&quot;&gt;...&lt;/div&gt;</pre><pre>    &lt;!-- Usual title --&gt;<br>    &lt;div class=&quot;title&quot;&gt;My App&lt;/div&gt;</pre><pre>    &lt;div class=&quot;right&quot;&gt;...&lt;/div&gt;</pre><pre>    &lt;!-- New large title (text can be different) --&gt;<br>    &lt;div class=&quot;title-large&quot;&gt;<br>      &lt;div class=&quot;title-large-text&quot;&gt;My App&lt;/div&gt;<br>    &lt;/div&gt;<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><p>For Framework7 Vue/React components it is even more simpler:</p><pre>&lt;f7-navbar title=&quot;My App&quot; large /&gt;</pre><pre>&lt;Navbar title=&quot;My App&quot; large /&gt;</pre><h3>Expandable Cards</h3><p>This was a real challenge to implement but here we goes. Meet all new expandable cards (aka AppStore cards) coming in v4:</p><h3>Framework7 on Twitter</h3><p>How about this? Meet all new expandable cards (aka AppStore cards) coming in @framework7io v4 🔥🔥🔥 https://t.co/fMRoAKjPkh</p><p>And their API is pretty simple. Just extra card-expandable class on card element. But sometimes, to look correctly and feel native, expandable card content may require additional tweaks. But in general it is just:</p><pre>&lt;!-- expandable card --&gt;<br>&lt;div class=&quot;card card-expandable&quot;&gt;<br>  &lt;div class=&quot;card-content&quot;&gt;<br>    ... any HTML content here ...<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><h3>Large Block Titles</h3><p>Block titles extended to be in medium and large sizes to improve out-of-the-box typography:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ml-BlONPgMnQrAUn1n7RJw.png" /></figure><p>It is just extra block-title-large or block-title-medium class on any block title to make it large or medium size.</p><h3>Pull To Refresh From Bottom</h3><p>In addition to usual pull to refresh, v4 also supports pull to refresh from bottom:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*X9tZc_mGlSRtEYrc_2xSTg.gif" /></figure><h3>Menu — New UI Component</h3><p>The idea and request for this component came from our Patrons 🙌</p><p>Menu component not so often seen in mobile apps. But it is proven to be extremely helpful when you need controls on top of the map, images, some text/code editor, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*aOme48IHHAhjyYdtvV3wsw.gif" /></figure><h3>Skeleton — New UI Component</h3><p>Perhaps you have already heard of such concept: UI Skeletons, Skeleton Screens, Skeleton Elements, or even Ghost Elements?</p><p>Skeleton elements are basically “gray box” representations of UI that will be available soon. They are designed to improve perceived performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*-SEuT4csTk0RYSSFafhVww.gif" /></figure><p>Framework7 comes with two Skeleton patterns:</p><ul><li>skeleton-block. It is just a usual block element with gray background color, that can be in any required size</li><li>skeleton-text. It is more interesting thing. Framework7 comes with special built-in Skeleton font, that renders every character as small gray rectangle. When we apply skeleton-text class to any element, it converts text to gray blocks/lines. Advantage over skeleton-block is that such “skeleton text” can be fully responsive and it is size will reflect actual text size.</li></ul><p>Skeleton elements also support three animation effects: Fade, Blink and Pulse.</p><h3>Range Slider Goes Vertical</h3><p>Range Slider in v4 is also a bit reworked and improved. Now it supports scale, and vertical directions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qi3A6wBRJ64ibLnk6g6QJg.png" /></figure><h3>Core Icons Font</h3><p>Here is one more improvement related to Framework7 core icons, e.g. “back” icon, Searchbar “search” icon, and others. Before v4 they were implemented as inline (data-url) SVG images in main CSS bundle. It is pretty convenient, but brings difficulties when we need to change color of such icons — we need to redefine it with another inline SVG image with required color.</p><p>In v4 all core icons are reworked to built-in core icons font with ligatures. It allowed to save extra KB’s of size and no more difficulties to change their color. Now to change such icon color we can use CSS’s color rule.</p><h3>Service Workers — New Module</h3><p>This new module is a large step towards Progressive Web Apps development with Framework7. Right now it only allows to simplify the process of service workers registration but will have a lot more functionality soon.</p><p>For example to register service worker, we can just specify it in app parameters:</p><pre>var app = new Framework7({<br>  // ...<br>  serviceWorker: {<br>    path: &#39;path/to/service-worker.js&#39;,<br>    scope: &#39;/&#39;,<br>  },<br>});</pre><p>Or with API after app initialization:</p><pre>app.serviceWorker.register(&#39;path/to/service-worker.js&#39;, &#39;/&#39;)<br>  .then((registration) =&gt; {<br>    console.log(&#39;Service worker registered&#39;);<br>  })</pre><p>With this module it will be super easy to work with service workers.</p><h3>Request Promisified</h3><p>Built-in Request library to work with XHR requests can work as Promises now.</p><ul><li>app.request.promise(...) — same as app.request() but returns Promise that will be resolved with response data</li><li>app.request.promise.get(...) — same as app.request.get(...) but returns Promise that will be resolved with response data</li><li>app.request.promise.post(...) — same as app.request.post(...) but returns Promise that will be resolved with response data</li><li>app.request.promise.json(...) — same as app.request.json(...) but returns Promise that will be resolved with response data</li><li>app.request.promise.postJSON(...) — same as app.request.postJSON(...) but returns Promise that will be resolved with response data</li></ul><p>And the usage is:</p><pre>app.request.promise.get(&#39;./something.html&#39;)<br>  .then((data) =&gt; {<br>    // Handle response<br>    console.log(data);<br>  })<br>  .catch((err) =&gt; {<br>    // Error happened<br>    console.log(err);<br>  });</pre><p>Or with async/await:</p><pre>const content = await app.request.promise.get(&#39;./something.html&#39;);</pre><pre>// Handle content<br>console.log(content)</pre><h3>Fastclicks Disabled</h3><p>Fast clicks is a built-in library that removes 300ms delay from links and form elements in mobile browser while you click them. It was implemented and enabled since very first Framework7 release and this is one of the features that makes app developed with Framework7 feel native.</p><p>But much time has passed since then. And modern browsers are smart enough to eliminate that click delay when certain conditions met like correct &lt;meta name=&quot;viewport&quot;&gt; meta tag. So in v4 it is now disabled by default to avoid unnecessary issues, especially with 3rd party libraries. And it must be enabled if you target older devices, like iOS &lt; 10.</p><h3>Touch Ripple in iOS Theme</h3><p>Why not? Touch ripple effect that was MD-theme exclusive now can be enabled for iOS theme too with app.touch.iosTouchRipple = true parameter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*x2je18FD8fOAqcnK0U9s7Q.gif" /><figcaption>Touch Ripple effect in v4 iOS theme</figcaption></figure><h3>Events Bus</h3><p>As you may aware Framework7 has pretty flexible events system/model. Each instance of Framework7&#39;s class (<em>like main </em><em>Framework7() class or any class-based component like </em><em>app.calendar.create()</em>) has methods to emit and handle events (emit, on, once, off).</p><p>Such model is also very useful to create custom events for communication between app components.</p><p>So in v4 there is a new helper class that is designed to be used like event bus only and not to flood main app instance.</p><pre>const myEvents = new Framework7.Events();</pre><pre>// handle event<br>myEvents.on(&#39;some-event&#39;, () =&gt; {<br>  // do something when &#39;some-event&#39; fired<br>})</pre><pre>// emit event<br>myEvents.emit(&#39;some-event&#39;);</pre><pre>// another event bus<br>const notificationEvents = new Framework7.Events();</pre><pre>notificationEvents.on(&#39;notificationReceived&#39;, (notification) =&gt; {<br>  // do something<br>})</pre><pre>// somewhere in the app<br>notificationEvents.emit(&#39;notificationReceived&#39;, {<br>  title: &#39;New message&#39;,<br>  from: &#39;John Doe&#39;,<br>});</pre><h3>Framework7 Icons V2</h3><p>You may aware that we recently released <a href="https://blog.framework7.io/framework7-icons-v2-1bb74ef5055a">Framework7 Icons v2</a> — free, amazing and huge set of hand-crafted iOS icons specially designed for Framework7.</p><p>And in <a href="https://blog.framework7.io/framework7-icons-v2-1bb74ef5055a">this blog post</a> we wrote that they have different design sizes, so their usage in Framework7 v1–v3 may required additional tweaks.</p><p>Framework7 v4 is designed to be used with new F7 icons so they will perfectly fit here.</p><h3>Framework7 React &amp; Vue Changes</h3><p>Of course all new features written above like large navbars, toolbar positions, unified buttons, expandable cards will be available here with new props on related components. And there are new Vue/React components for new UI components like Menu and Skeleton.</p><p>But there is also breaking changes here. f7-label / Label component has been removed. It was used together with f7-input / Input component to create inputs in List View. Now instead of that components, we need use new f7-list-input / ListInput that was recently introduced in latest versions of Framework7 v3.</p><p>So if you have something like this (for example in Vue):</p><pre>&lt;f7-list-item&gt;<br>  &lt;f7-label&gt;Name&lt;/f7-label&gt;<br>  &lt;f7-input<br>    type=&quot;text&quot;<br>    :value=&quot;userName&quot;<br>    placeholder=&quot;Your name&quot;<br>    <a href="http://twitter.com/input">@input</a>=&quot;updateUserName&quot;<br>  /&gt;<br>&lt;/f7-list-item&gt;</pre><p>It needs to be changed to new single component:</p><pre>&lt;f7-list-input<br>  label=&quot;Name&quot;<br>  type=&quot;text&quot;<br>  :value=&quot;userName&quot;<br>  placeholder=&quot;Your name&quot;<br>  <a href="http://twitter.com/input">@input</a>=&quot;updateUserName&quot;<br>/&gt;</pre><h3>Framework7 CLI v2</h3><p>First version of Framework7 CLI was released a while ago and due to lack of its features and usefulness it wasn’t maintained and mentioned anywhere.</p><p>But now everything changes. With Framework7 v4 release we introduce totally new Framework7 CLI which is an extremely powerful tool to start Framework7 app development. And with Framework7 v4 it will be the most recommended way for setting up new Framework7 project.</p><p>Instead of maintaining different variations of official templates (<em>Core/Vue/React * Single View/Tabs/Split View * Web/Cordova/PWA</em>) it is easier to have one tool that combines all variations.</p><p>So new Framework7 CLI allows:</p><ul><li>to select template: Single View, Tabs, Split View</li><li>to choose framework: F7 Core, F7 Vue, F7 React</li><li>to choose target: Web app, PWA, or Cordova, or mix of them</li><li>to specify custom color theme from the start</li><li>to choose bundler: No bundler, Webpack or Rollup (coming later)</li><li>to generate required icons and splash screen</li></ul><p>And the usage is very simple. First, we need to install F7 CLI (in beta now) and Cordova:</p><pre>$ npm i framework7-cli@beta cordova -g</pre><p>And to run the following command in the directory where you want to create app:</p><pre>$ framework7 create</pre><p>Program will prompt for a few questions about framework and template you want to start with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQtTZ99F-Llz3xv5M-0CQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dv0ow2VcaGAy0j8IDkZBOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrw40Ha3J2LOZlmnPolMrQ.png" /></figure><p>And it also comes with UI. We can run the following command instead to launch UI to create the project:</p><pre>$ framework7 create --ui</pre><p>And the following web app will be opened:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E71Zw0ZZ62BcNJiyGUTCFA.png" /></figure><h3>When?</h3><p>Final and stable 4.0.0 release is going to happen in the end of January — beginning of February, 2019 🎉</p><p>But you can already try the beta version which can be considered as production ready.</p><p>For already created v2/v3 app, you can upgrade by downloading beta release at <a href="https://github.com/framework7io/framework7/releases">GitHub releases page</a> or via NPM:</p><ul><li>npm i framework7@beta — for core framework v4</li><li>npm i framework7-react@beta — for Framework7-React v4</li><li>npm i framework7-vue@beta — for Framework7-Vue v4</li></ul><p>For the new app it is highly recommended to start with all new Framework7 CLI:</p><pre>$ npm i framework7-cli@beta cordova -g<br>$ framework7 create --ui</pre><h3>P.S.</h3><p>If you love Framework7, you can support project by donating or pledging on Patreon: <a href="https://www.patreon.com/framework7">https://www.patreon.com/framework7</a> or by purchasing a nice branded t-shirt at <a href="https://teespring.com/stores/framework7">Framework7 Shop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74b2b467047c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framework7/the-best-framework7-yet-what-is-new-in-v4-74b2b467047c">The Best Framework7 Yet. What Is New In v4</a> was originally published in <a href="https://medium.com/framework7">Framework7 Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>