[V1] how to build with ios theme? -T ios



  • @s-molinari
    Today, I have to start a new project. I have 3 solutions v0.17 (end of life), v1 (in beta) and vuetify.What is the best solution? I’m very familiar with v0.17 and now I have to learn V1 or Vuetify and I think Vuetify’s API will remain stable.



  • That is a tough choice. @Marc

    If v1’s API changes, it will be only minimal, which means relatively easy upgrading for you. I think with the new docs, if you are an advanced or even intermediate JS and Vue dev, you’ll get rolling along rather quickly. If you knew v0.17 and how to work with it, v1.0 is fairly the same overall from a CLI/ dev experience perspective. We also have an upgrade guide coming out like any day now (I believe with beta 5), which will also help you a lot to see the differences between 0.17 and 1.0 components and other changes.

    The development on v1.0 is also rapidly ongoing. I know. That can be a good thing, but also a bad thing. Depends on how you look at it. I look at it as a great thing. 😁

    Also, what type of app, or even apps, will your project need to be? That might also help you with your decision?

    Scott



  • @Marc i would go with v1-beta, its solid and pretty neat.

    quasar offers the best components i have seen in the the vuejs eco system so far.



  • @rstoenescu

    Where can I find the examples to make components look and feel like iOS?

    Are there any plans of any kind of (offical) ios theme support for standard components in V1 in the near future?



  • @s-molinari Can we follow the work you guys are doing on these extensions? Or at least the list of them… I am thinking about making some of my own after the QMediaPlayer extension release, and I think it would be useless to work on something the Quasar team are already doing

    Also, I really like to follow this project



  • @lucasfernog - I’m not sure the list of extensions we gathered is for the public yet. I’ll check. You could also mention your first few ideas here and I could tell you if they were already mentioned or not. And to be honest, unless it is going to be an official extension, which not too many will be, you can start doing one or two on your own. There are no “dibs” on extensions from the Quasar team. It will be a free and open market for them. That’s one of the beauties of them. 😁

    Scott



  • @lucasfernog - Please DM me to further discuss extension work. Thanks!

    Scott



  • Not wanting to insult people but I have the feeling this thread is diverting from the original topic: what happened to the IOS theme support in V1.

    Fact is that one of the main features(out of the box ios theming) has been been removed from Quasar [V1] and replaced by: do it yourself. While (ios) theming is ‘advertised’ as one of the main features of the quasar framework:

    https://quasar-framework.org/

    • Hybrid Mobile Apps (that look native!)*

    https://www.patreon.com/quasarframework

    • Two Themes (more to come) - Material theme and iOS theme.*
    • native mobile Apps (that really look native!)*

    Could anyone tell me if there are plans of any kind of (offical) ios theme support for in V1 in the near future?


  • Admin

    @dobbel

    We’ve decided not to support two versions of themes to better concentrate on getting just the one right. This however does not mean that your apps will look wrong on iOS or that real themes won’t be available in the future. Quite the contrary.

    Let’s be honest, the iOS theme was not really following the iOS guidelines and there were too few components having different behavior based on the theming. But as few as they were, the development doubled (even tripled in some cases) because basically Quasar was a two frameworks in one – and having in mind the current level of funding, this cannot work long-term due to the continuous exhaustion levels.

    We are also planning on a real theming system in the near future, which is part of the grand scheme of things with v1, where themes can be exported and shared among the community. We strived a lot to make v1 be extremely easy to customize which fits extremely well with these plans. This could never have been possible with two base themes because the CSS would have been a complete mess.

    We also asked our Patrons on this matter and the majority ruled that it would be better to focus on better components and faster releases.

    This was a high overview / satellite view of how and why things changed (to the better!). When getting into details, it will become very obvious why there’s no need for two base themes on Quasar. Take QToolbar for example. It’s way easier for the developer to make it look differently on an Android and iOS (look at v1 docs examples, takes about 15 seconds to differentiate the design if you want). Maybe some don’t even want to be forced into changing the design of Toolbar for iOS specifically. Dealing with the color, inverted-color etc props was very hard to grasp by many. We learned from that and this one base theme allows for a lot more logical props and behavior. It all becomes like a breeze in v1 while developing, which is our main task when creating Quasar. Sometimes you have to take a couple of steps back to take better steps forward.

    This one base theme and the multiple real themes coming in the near future is a big step forward. If it’s not yet clear now, it will be very obvious quite soon as we approach final 1.0 build.



  • @s-molinari
    Thank you for your reply. My decision was made when I read the upgrade documentation.
    New projects will be with Vuetify. I have applications in version 0.14 and others in version 0.17 and it is sometimes difficult to switch from one to another. Three versions would be more complicated than learning a new framework.
    I think the Vuetify API is more stable.
    Why rename ‘plugin’ in ‘boot’? q.i18n to lang ?, tertiary color to accentuate? … and so on.
    To avoid confusion, all components should have been renamed, such as QInput to NInput.


  • Admin

    @Marc

    Switching to another framework just when Quasar’s API becomes stable? 🙂



  • @rstoenescu said in [V1] how to build with ios theme? -T ios:

    @Marc

    Switching to another framework just when Quasar’s API becomes stable? 🙂

    well it’s a valid choice since he need two themes. unless he wants to continue with 0.17 which won’t be updated much now that v1 is out.



  • @dobbel said in [V1] how to build with ios theme? -T ios:

    @rstoenescu

    Where can I find the examples to make components look and feel like iOS?

    Are there any plans of any kind of (offical) ios theme support for standard components in V1 in the near future?

    Still no answer on this. We were creating a SPA with iOS theme, converting to v1 completely broke our design. Can we import old ios stylings manualy somehow?



  • @rstoenescu Honestly I’m also disappointed about this decision. having Components that look native (Like the action sheet) was a really excellent feature

    I know that the theming needed to be improved, but get rid of it is an important downgrade

    also if there is no way to “Switch” between themes please get rid of this on the upgrade guide

    “There are examples in the docs of how to make different components look and feel like iOS”

    is highly misleading.



  • @fega if you’re talking bout this https://quasar.dev/start/upgrade-guide#Build-Themes you can propose an edit if you feel like it’s misleading, click the pencil icon on top of the page to open edit of page and submit a pr.


  • Admin

    @fega

    1. It’s not at all misleading. Due to the way that Quasar is now way way easier to style, we actually don’t need two themes (which slow down development very significantly). Example from docs (and this is just one): https://quasar.dev/layout/header-and-footer#iOS-look-and-feel
      Try to understand Quasar behind the “it’s Material design only?” first impression. Cause it’s not. I won’t go over the technical details because I’ve done it countless times, but you’ll soon see the MANY benefits of having a base design which is years ahead more configurable than pre 1.0 was.

    2. One of those immediate benefits: we are working on more themes than you can imagine (not just 2 as it was before 1.0), and you’ll be able to install them through App Extensions. It’s going to be so easy that you won’t even believe it. This is yet another place where Quasar will really shine.

    3. As always, try to think of the tens of thousands of hours that have been put into the development of Quasar and visit our Why donations are important page (if you haven’t already). It puts things in perspective. The more financial resources that we have the faster the development will go.



    1. Hello @rstoenescu sorry but yes, is misleading, the example that you provided is the only one that I found in the algolia search, and honestly is not very good, it still looks as a Material design theme. also, I tried to upgrade and the started to look for those mentioned “examples” and I needed to roll back because they don’t exist. and as you can see I wasn’t the only one that had that issue.

    2. yes, I understand that the changes made should simplify the code A LOT, and I’m not saying that is a bad decision, but there are some “IOS specific components” that disappeared, like the action sheet and the Date Picker, that could be refactored as an IOS specific themes and let the user switch using the quasar helpers.

    3. Keep in mind that most of us know how hard making open source code is, and I’m is not an opinion against Quasar or the team of people behind of such hard Work. this is an opinion to “Make Quasar better”, and can be added or discarded, yes I’m disappointed about that decision, but don’t take it personally, is just an opinion about a decision, but I still think that the Quasar team is doing a great Job, but software is never perfect.

    @metalsadman I honestly think that the reality is that when a user upgrades the framework, the IOS theme needs to be done manually using quasar helpers, I think that the docs still need to evolve in order to make that affirmation true.



  • @fega you are correct about the manual work, but i don’t think the docs has claimed that you can simply make the v1 components to look exactly ios themed like the legacy versions had. The thing is even with the material design as it’s main theme out of the box, devs still roll their own styling out of the spec (coz of preference / requirements etc.). at first i was skeptical of the changes to v1 tbh (you can even see my skeptism above older post xd), but it made sense along the way. The components are already there, it’s just a matter of how devs use it, highly encourage peeps to extend it according to their needs and add functionalities along with the quasar ones and ofc contribute to our community :). If you still feel the same way of that part of the doc tho, my initial response to you still stands.



  • Could you elaborate on how we might customize components to have an IOS look and feel?



  • Any idea when these themes will be available as extensions?

    Additionally, does anyone know of some sort of theme/library that will make iOS-like components (specifically form components and controls, like toggle/switch) that can integrate with v1? I’ve finally been able to try it out and it’s great, very enjoyable, but lack of iOS will prevent me from bringing v0.17 projects up (which I am excited to do).


Log in to reply