No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. jesus
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 20
    • Best 4
    • Groups 0

    jesus

    @jesus

    12
    Reputation
    648
    Profile views
    20
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    jesus Follow

    Best posts made by jesus

    • RE: Migration 0.13 to 0.14

      I am sorry for all whom expect a migration via magic button or script able in a couple of hours to do the job or solve it with find and replace, it did not work for me at all.
      I am working in moving a large invoicing web/app from 0.13 to 0.14 and tasks are really tough, 0.14 is great but it changes a lot of ui behaviours … 😲
      I know a migration guide is coming but distance is much longer that one digit.
      There is a lot of work behind and in any point apps has to move forward, updated, bug fixed, etc

      A couple of things I found just beginning:
      0) You will not have src in node-modules so for every Quasar element you have to declare and import, for instance it is how things should be done. In some points I had used quasar 0.14 src to go further than current documentation.

      1. Layout has to be adjusted, one should be learn how new layout can be set and make changes. No Drawer. If target app use slots for layouts you have to change some labels and play. 0.14 layout is much easier by far in this release, so one can take this as housekeeping, and simplify code.
      2. Import Utils does not work, so all elements have to be imported individually, specially dom, format functions, etc.
      3. Buttons, changing <button to <q-btn, I am afraid it will not be enough, events can work but style has to be checked, and dynamic use of icons has to be moved to q-icon and use β€œname” prop for the icon.
      4. Icons and style is another point to consider, it depends on what icon set your app is using (material, fontawesome, etc.)
        In target app main.js Icon set should be imported, load style theme mode (css or styl)
      5. Toolbar, another brick in the wall, in 0.13 is a class div and in 0.14 use <q-toolbar, anycase class and style has to be reviewed.
      6. Some app css styles using classes for toolbar or button will not have effect as html objects classes are renamed with qt, so app stylesheets has to be reviewed. This is a big issue pretty normal by the way with ui updates.
      7. Autocomplete is an example of changes, in 0.13 my app use input inside autocomplete and in 0.14 this is reversed
        Despite I have my own modifications of autocomplete and data-table all elements has to be revised, because usually elements has others elements dependencies, so process will be a long cascade of changes. 🀺

      So make your space, read carefully current 0.14 doc and then be patient and review 0.13 code, the final results will be worth, but it will take patient and time, I am still in the process.πŸ™

      I have to confess that sometimes I thought if it was not better to start the whole UI of the application again. I think it would be helpful to get familiar with 0.14 in a new application and then later try to migrate others. πŸ˜•

      Think that as in life, inevitably to go forward implies to drop some older ways of doing and learn/apply other methods … we are not in a position of judge these changes, only in a point to understand and implemented them for our target application users benefits. πŸ‘Œ

      posted in Framework
      J
      jesus
    • RE: The 0.14 beta release is available!

      @rstoenescu Stop immediately whatever you are doing, turn off everything except your desire of enjoy and be well with your self and take 10 day vacations. We always always will have works and pending tasks, people to help, etc. But we need to re-charge ourselves, have confidence universe will be there after your sacred 10 days dedicated to your self. You deserve it simple because you wanted it. It will be also part of this new release, a minimum price we have to pay to honor you and your hard work.
      We will miss you during this time but we will survive and we know that when you return you will be stronger and everything easier.
      Why I say this because I have much more than 2 years with no vacation I am not proud of this at all. Sorry but sometimes one have to be first !!!

      posted in Announcements
      J
      jesus
    • RE: Migration 0.13 to 0.14

      We are passionated about v0.14 but hold your horses, first learn how new version works in depth, you will probably discover that your are dealing with a new framework to finally conclude that it is worth to rethink most of your ui app before to consider to upgrade from 0.13.
      For me it is a major upgrade rather than a simple update.
      I hope to be wrong but I do not see a clear upgrade path, a deep refractor is need, in some case it will push to rewrite components and app flow.
      If one does not know well v0.14 and vuejs version behind and how to use it appropriately, the it will not be posible to estimate how much it will cost in time and work.
      Any way sooner or later v0.14 will be the path so make space and be ready. πŸ™‚

      posted in Framework
      J
      jesus
    • RE: [v0.14] Removed "src" folder from Quasar package

      I am seeing this way of no src in others too. It is ok but as developers we need to have src for several reasons:
      a) Sometimes we need to read code and to know what it is happening rather than guessing, etc
      b) Sometimes we need to raise an exception and to do strange and stupid things like to use src files directly or why not overload or fork code for whatever arise.
      c) For me to have src is guarantee of being in a open and not blind software, it is how things stand up behind scene. It is not only what we do it is also what support us, so we need to make very smart choices like quasar πŸ™‚
      So in my humble opinion for development src should be there or accesible anywhere, but deployment is a complete different animal who needs to be fed in other way.

      posted in Announcements
      J
      jesus

    Latest posts made by jesus

    • RE: ~~Do not upgrade to Vue 2.4.x (yet)~~ Edit: Safe to upgrade

      In https://github.com/vuejs/vue/releases/tag/v2.5.0
      Provide/Inject
      support providing default values for injections (#6322) 88423fc
      So, is it fixed or not ?

      posted in Announcements
      J
      jesus
    • RE: Router lazy loading with 0.14 does not work for me

      I was looking at https://www.youtube.com/watch?v=rn97hCNQsKI practical part starts at minute 6:30
      Sean Larkin (a maintainer of webpack) recommends to use code splitting ALWAYS on routing.

      posted in Help
      J
      jesus
    • RE: New Weex Release Officially Supports Vue 2.0

      https://github.com/quasarframework/quasar-template-pwa
      Working in progress …

      posted in Hangout
      J
      jesus
    • RE: New Weex Release Officially Supports Vue 2.0

      Digging into forum I found @s.molinari saying β€œQuasar is PWA ready. Only the wrapper is missing.” http://forum.quasar-framework.org/topic/241/excellent-work/4
      Any info about this in 0.14 or in roadmap after full release ?

      posted in Hangout
      J
      jesus
    • RE: Router lazy loading with 0.14 does not work for me

      @JDrechsler this is a complementary info https://webpack.js.org/guides/lazy-loading/
      I am glad that you solve it, I think it is much better to move this to low level layer, as far as I see is webstack.

      posted in Help
      J
      jesus
    • RE: New Weex Release Officially Supports Vue 2.0

      @paul totally agree … I do not see too much freedom and control in native apps development, Cordova, Weex … patching situation … mmm.
      Back to the roots, let stay in web-mode, claim app control out of stores and use full device features.
      To whom may concern, is there anything we can do to make Quasar PWA and SSR possible ? πŸ‘

      posted in Hangout
      J
      jesus
    • RE: Router lazy loading with 0.14 does not work for me

      @JDrechsler Ok I see but … what about webpack 3 ? At least you should do something like this https://alexjoverm.github.io/2017/07/16/Lazy-load-in-Vue-using-Webpack-s-code-splitting/

      posted in Help
      J
      jesus
    • RE: Router lazy loading with 0.14 does not work for me

      I am sorry if it has non sense but have you tried async component support for webpack 3 and vue js 2.4.0 ?
      I know that 0.14 has issues with 2.4.0 and webpack 3 is a different animal
      I think also it could be better to have lazy loading out of router app flow (to avoid constraint app routes and delay responses).
      This is a very interesting challenge before to consider to move to SSR: to serve or consume code by context, needs and demand.

      posted in Help
      J
      jesus
    • RE: New Weex Release Officially Supports Vue 2.0

      Well why not to go to progressive web apps ? Why not to push Quasar into PWA and SSR ?

      posted in Hangout
      J
      jesus
    • RE: Migration 0.13 to 0.14

      We are passionated about v0.14 but hold your horses, first learn how new version works in depth, you will probably discover that your are dealing with a new framework to finally conclude that it is worth to rethink most of your ui app before to consider to upgrade from 0.13.
      For me it is a major upgrade rather than a simple update.
      I hope to be wrong but I do not see a clear upgrade path, a deep refractor is need, in some case it will push to rewrite components and app flow.
      If one does not know well v0.14 and vuejs version behind and how to use it appropriately, the it will not be posible to estimate how much it will cost in time and work.
      Any way sooner or later v0.14 will be the path so make space and be ready. πŸ™‚

      posted in Framework
      J
      jesus