Giter Club home page Giter Club logo

Comments (4)

web-padawan avatar web-padawan commented on May 30, 2024

Thanks for the issue. I don't have any plans to integrate Lumo at this point due to the reasons:

  1. Aybolit is my personal pet-project, not associated with Vaadin. I'm working on it in my free time only, and I'm not getting paid for it. And I would prefer to keep MIT license here.

  2. Lumo, in its current shape, introduces some complexity which I would like to avoid - especially, it relies on extra wrappers in certain components, selectors like :host::before for alignment etc.

  3. Lumo still has to support IE11, and in Aybolit I would like to feel a breath of fresh air and drop the support for this compatibility solution in order to gain more power and flexibility.

So the only integration strategy I can recommend would be extending "white label" components and tweaking the CSS manually to make them look visually similar to Lumo, using same colors etc.

from aybolit.

lkraav avatar lkraav commented on May 30, 2024

If we look to use Vaadin components, I think we will be having Lumo in active play regardless. For now.

It seems like an unfeasible amount of work to recreate an optimized "Aybolumo" in Aybolit (kill :host::before wrappers, etc), then also somehow get Vaadin components re-styled for "Aybolumo".

I'm thinking if starting with Vaadin and Lumo today, while writing our own components in Aybolit structure, we simply migrate and evolve towards "better" with the upstream over time.

Are there any significant flaws in this thinking model?

from aybolit.

web-padawan avatar web-padawan commented on May 30, 2024

Yes, I think that's a good idea. Vaadin components are a complete set, while Aybolit is personal project and experiment, so it's unlikely that I will be able to cover all the components any time soon.

from aybolit.

lkraav avatar lkraav commented on May 30, 2024

So it's unlikely that I will be able to cover all the components any time soon.

We'd be motivated to consistently help along. I just can't imagine off the top of my head what the process of merging upstream changes would be, is there any merge automation available at all, or all changes need to be cherry-picked (aka unsustainable).

from aybolit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.