-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dead? #61
Comments
I guess there is no big need for this or they are simply waiting for Angular2. Nobody wants to put a lot of work into this when in some month everything has to be rewritten. |
wondering the same, although there is still some years for angular1 to be called deprecated. |
yeah, angular1 is still far from being deprecated. |
Someone is already working for Angular 2. https://github.com/vladotesanovic/ngSemantic |
DO NOT GO produce nothing angular About 1 ? |
seems dead |
Hey, guys. Thank you for worrying about it I have some points to do:
|
somebody is already did angular2 version, but currently no update since last month. unfortunately i cant help at all, writing is the only help i can do. lol. good luck, cheers. |
@vazh I don't think that angular1 is going to be transformed to angular2. I think that is there 2 totally different versions and doesn't have so much compatibility. In practice, there is a thousand of company and people using ng1 yet and it will take a while to all people move to ng2. A possible way to renew this project is take care about ng1, released and after that open a new discussion about ng2 |
@matheuspoleza not really meant it that way, sorry for the confusion. and yeah it will take a while before people moving to ng2, that's why its best to do it in angular1 first, then you can progress into angular2 bit by bit. just do it natively, without jquery. the thing is, angular1 life cycle is still far from dead. when lots of components released to support angular2 then its time to think about changing to angular2. but right now, i dont see any stable components can be used to build a whole application for people like me who can only use available components, except for PrimeNG ofcourse. |
@vazh totally agree with you. Maybe the problem was take so much care about ng2. A possible way as you mentioned is focus on ng1 and take the first release |
Along that thread here are a couple of repos for Semantic/Ng2 Not posting the ones with jQuery as that's not a full integration. I would love to see some energy towards a formal Ng2 support - a lot of Angular devs are just biting their nails waiting for the final release before pouncing on it. I personally would be super excited to use Semantic for it but am worried that these devs are going to lose steam without more support (already looks like #2 is inactive). |
https://github.com/vladotesanovic/ngSemantic though i did say to start on ng1, but if its going to take a long time to decide, its better to jump ahead into angular2. its much easier anyway. |
@vazh unfortunately that one is a jQuery and not a native Angular one. |
@cyberwombat yeah, but its still the best out there. im curious as to how the heck PrimeNG do it. |
so, there is no further development in this project ? Does anyone know of any other project for angular 1 and semantic-ui? |
@jmls if you actually read the comments you can actually find related projects to your question. |
@vazh Perhaps instead of being distasteful in the comments you could be helpful? I don't see a single link to an active and updated Angular 1 project in this thread. |
So is this repo dead? No activity for a couple of months. Did you hit a roadblock? Need some assistance?
The text was updated successfully, but these errors were encountered: