GithubHelp home page GithubHelp logo

Comments (6)

jangalinski avatar jangalinski commented on August 16, 2024

When I use "extends UI" and "@ui" on my class, I cannot import both (so I would have to use FQN), so your last option would confuse me.
And since UI already is the Vaadin core component, annotating it with "VaadinUI" seems redundant. So although five capital letters in a row look strange ... as a user, I liked @CDIUI ... it annotates my vaadin UI with a cdi specific extension.

from cdi.

AdamBien avatar AdamBien commented on August 16, 2024

You are right. This was the reason, why we started with VaadinUI. Five capital letters do look strange :-). IMHO the annotation just marks a class as being a Vaadin UI. If the majority of CDI-extesion users prefers @CDIUI over @VaadinUI I'm perfectly fine with that.

from cdi.

jojule avatar jojule commented on August 16, 2024

Those were the exact reasons for the change.

On Mon, Apr 29, 2013 at 10:54 AM, Jan Galinski [email protected]:

When I use "extends UI" and "@ui https://github.com/UI" on my class, I
cannot import both (so I would have to use FQN), so your last option would
confuse me.
And since UI already is the Vaadin core component, annotating it with
"VaadinUI" seems redundant. So although five capital letters in a row look
strange ... as a user, I liked @CDIUI ... it annotates my vaadin UI with a
cdi specific extension.


Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-17153865
.

Dr. Joonas Lehtinen, CEO
Vaadin - http://vaadin.com/

FI: +358-40-5035001, US: (415) 513-0739, Skype: joonaslehtinen
Office: Vaadin Oy, Ruukinkatu 2-4, 20540, Turku, Finland
Twitter: https://twitter.com/joonaslehtinen
LinkedIn: http://fi.linkedin.com/in/joonaslehtinen

from cdi.

AdamBien avatar AdamBien commented on August 16, 2024

IMHO CDIUI is misleading, because we get integration with the whole JavaEE and not only CDI. It is more than likely, that you will inject an EJB into the UI and CDI managed beans into the EJB. JavaEEUI would be more consistent, but I don't like the name either and Java is trademarked.

@VaadinUI is redundant, but logical--you recognize immediately, that the annotation belongs to Vaadin. CDIUI looks like an annotation coming from CDI. It might be confusing for JavaEE + Vaadin beginners. I would just prefix everything consistently with Vaadin.

Alternative: we could also rename CDIUI after the responsibilities like: DiscoverableUI. It means: a view that does not have to be registered somewhere. Like @startup in EJB. Or ScopedUI -- UI participated in a scope or just: @tab (browser tab)

from cdi.

jojule avatar jojule commented on August 16, 2024

Neither CDIUI or any of the proposed names are good. Unfortunately I do not have a better alternative. A word describing what happens for UI might be the best. Something like @attached or @Served

Dr. Joonas Lehtinen, CEO
Vaadin - http://vaadin.com/

FI: +358-40-5035001, US: (415) 513-0739, Skype: joonaslehtinen
Office: Vaadin Oy, Ruukinkatu 2-4, 20540, Turku, Finland
Twitter: https://twitter.com/joonaslehtinen
LinkedIn: http://fi.linkedin.com/in/joonaslehtinen

On Mon, Apr 29, 2013 at 11:12 PM, Adam Bien [email protected]
wrote:

IMHO CDIUI is misleading, because we get integration with the whole JavaEE and not only CDI. It is more than likely, that you will inject an EJB into the UI and CDI managed beans into the EJB. JavaEEUI would be more consistent, but I don't like the name either and Java is trademarked.
@VaadinUI is redundant, but logical--you recognize immediately, that the annotation belongs to Vaadin. CDIUI looks like an annotation coming from CDI. It might be confusing for JavaEE + Vaadin beginners. I would just prefix everything consistently with Vaadin.

Alternative: we could also rename CDIUI after the responsibilities like: DiscoverableUI. It means: a view that does not have to be registered somewhere. Like @startup in EJB. Or ScopedUI -- UI participated in a scope or just: @tab (browser tab)

Reply to this email directly or view it on GitHub:
#16 (comment)

from cdi.

Artur- avatar Artur- commented on August 16, 2024

All CDI issues in GitHub have been moved to http://dev.vaadin.com

from cdi.

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.