Review of the Awesome Vue list #6
Comments
|
How should updates be communicated? |
|
I like the cleanup. I'll also make a note of what version express-vue uses. But it's always latest as I use greenkeeper.io to keep all dependencies latest and tested. |
|
@dealloc if you are confident about your update -> PR, otherwise let's discuss your update here |
|
Good, question: I see that there's no Modals in the list and just today i've added a modal component. I've sent a PR today, but dont if modal windows arent allowed anymore or something. I've search in brillout/awesome-vue/README.md but couldnt find any related info. (btw, the title says "Aweome" not "Awesome" :) ) |
|
@brillout I have explained advantage of an IoC container in the introduction section, I'm not quite sure what more information you'd like to see. I'd be more than willing to add whatever you feel is missing |
|
If I work on a vuejs version number badge would that be of interest? |
|
@brillout I've addressed your concern about stating which version of Vue my project uses. |
Can't find it, where is it? I remember vuec. I liked the introduction explaining DI. But it doesn't develop in what use cases DI is actually helpful. In short; What was your motivation to write vuex other than implementing DI? E.g. testing? I'll be happy to add it to the new list. Can you create an issue for that? We could discuss it there. |
|
@brillout it's on the original repo: But I suppose I have to make it to this new clean version, I'll make the PR tonight |
Ah, I only checked the merged ones.
Yea that would be awesome. I'll review it then. |
|
So is there something you need me to do for my keyboard component to be included in the cleaned list or is this just an FYI that it doesn't belong there altogether? |
|
vue-form got updated to work with 2.0 a couple of days ago. |
|
@martywallace The ticket is precisely about discussing this type of situations where lib authors disagree with a decision I took. I didn't add your lib because I didn't find a live demo, otherwise I would have added it. If you add a live demo, I'll happily add it to the new list. @fergaldoyle neat, I'll add it to the new list |
|
@brillout Ahh I see, no problem at all. I can sort that out within a couple hours. |
|
@filipemeneses I've seen the doc but I still hesitated on that back then. I just didn't find many use cases why someone would want to add a chalkboard to their app. What I liked about @martywallace 's virtual keyboard doc was @martywallace Awesome @dealloc Love it, perfect, I'll add to the new list |
|
@fergaldoyle @dealloc Actually, it would be great if guys can PR your libs into README_CLEANED.md. Thanks! (The format is |
|
@brillout no problem, under what category should I place vuec? I don't see any category it fits in currently |
|
@aweber1 the question you point out is also what I want to ask 😄 Thanks for your effort at advanced. |
|
Thank you. |
|
Thanks a lot, I don't have anything need to be updated though. |
Yeah, maybe (in contrast, developers have many alternatives here too). So vue-vpaginator requires jQuery but doesn't need the Bootstrap script, it uses the Bootstrap pagination markup only (plain HTML). Anyway, I will go to specify it and add the jQuery dependency. |
|
My vuejs-carousel has full support for Vue 2, it does not have heavy dependencies, aside from moment.js and it's different from the other carousels in the new list because it includes a theater mode plus comment sections inspired by Facebook |
|
I have added a Vue2 topic, does that suffice? |
|
@brillout vue-highcharts supports both v1 and v2. |
|
@brillout vue-ckeditor2 supports both v1 and v2 too. |
|
@brillout what "is not a library" means? Does it mean the code should be move to "UI Components" section? |
|
@brillout I have included the statement: "Tested to work with Vue2." near the top of README.md for vuex-basement. |
|
@brillout I already have that Vue2.0 is on it's way. |
|
hi @brillout I really appreciate your effort. Just a note - vuex-redux-saga does not a simple replacement of "actions" provided in vuex - it is used for handling complex scenarios when order of mutations could be arbitrary, also when you need things running in parallel, etc. A good explanation by my colleague on real life project (with React though) - https://goshakkk.name/lazy-auth-redux-saga-flow/ Let me know If I'm missing the point how i can build easily such "complex" functionalities with pure vuex |
@brillout - could you add a note near this line that tells authors/maintainers what to do once the original issue has been resolved? |
|
Hello @brillout . So much thanks for your work. |
|
@martywallace Great! Make a PR and I'll merge it. @treri Feel free to create a new category; How about @crossjs 👍 for the translation. But the demo http://plato.crossjs.com/#/ doesn't seem to work? I can't make any action on Chrome for desktop. @matt-sanders true, I've improved the categorization, better now? @njleonzhang yes ok. Also would be nice if everything in https://njleonzhang.github.io/vue-data-tables/#/en and in the readme is in English. |
brillout
changed the title
|
@brillout now vuejs-uib-pagination specifies the support for Vue.js 2.0 only. |
|
@brillout vue-super has been updated with tests and explicit Vue 2.x compatibility. |
|
I have created a npm package for my plugin
and i will update the readme for my other plugin in the future :) |
|
@pluto1114 Good. Could you update also the screenshots of the application? |
|
@gluons sure, my perspective; What is the complexity implemented by your library? Implementing a wrapper around highlight.js is easy. If I would need one then I would just implement it myself without even searching for a library. Since it's only couples of LOC. @MarkPieszak @aweber1 @caiyiliang @TIGERB I've added the examples to the new list. @cngu I was mentioning the problem it solves. I still included it in the new list though. @noru yes, please make a PR afterwards. @leonardovilarinho please check the README.md in this repo. @kevinongko would be great to have a live demo for vue-numeric, seems good otherwise. As for vue-instagram, I'd say that it's too specific and the added value too small. @italomaia where on the awesome list is it? Can't find any @varHarrie make a PR:) @pinguinjkeke @lsycxyj thanks:) @joseluisq Actually, I'm confused as to why you need jQuery for it? I'd personally rather use https://github.com/lokyoung/vuejs-paginate since it doesn't depend on jQuery @ludo237 I'd decouple the carousel part from the comment part @happyDemon I personally keep overlooking these GitHub tags @weizhenye Great, please make a PR @dangvanthanh is it on the Awesome Vue list? Can't find it @superwf I meant that your library's use case seems too specific @RashadSaleh great @mrgodhani cool @rpkilby done @lokyoung it's merged @sant123 nice @rpkilby 👍 make a PR and I'll merge it @reinerBa make a PR that I will merge |
|
@MarkPieszak @aweber1 @caiyiliang @TIGERB Examples are now part of the new list. |
|
@brillout perfect, thanks! |
|
@xanf how about adding a short use case that is easy to implement with vuex-redux-saga but difficult with vuex actions & mutations to the readme? |
|
@brillout I really understand that your work is so important to Vue's community, but you should have chosen the other way. How many emails did I receive from this issue?????? Those who not interested in the new list, not interested in updating their library or readme also receives them. Are you going to continue all discussions at here? Please, please, lock this issue and ask them to make issue and PR per user. |
|
Sorry and you are right, a new issue per discussion is better. (Note that you can click on the "Unsubscribe" button on the right to stop receiving emails.) |
|
To everyone: please create a new issue per discussion here at |
and others
You are being pinged because you have at least one resource listed under the Awesome Vue list.
As per vuejs/awesome-vue#836 we have reviewed the list and created a new one; brillout/awesome-vue/README_CLEANED.md.
We removed many resources. Removal reasons can be found at brillout/awesome-vue/README.md. If you have addressed the removal reason of your resource then please create a new issue at
brillout/awesome-vue.Projects using Vue.js have been reviewed by @Ffloriel and I reviewed all components & libraries.
I tried my best but I am sure that I did many mistakes. Let us know if you catch such mistake or if you disagree with a decision. (By creating a new issue at
brillout/awesome-vue.)Also, many libraries are missing a note to state what Vue version is supported. Be sure that your library includes such note. Ideally right a the beginning of the readme text. (A badge or a GitHub tag can be easily overseen.)
I've not included libraries that have no English documentation as stated in https://github.com/brillout/awesome-vue/issues/5.
ping
@10quality @AStaroverov @Akryum @Alex-Fun @alextoudic @AlexandreBonaventure @Angarsk8 @Astray-git @atinux @BirdEggegg @BosNaufal @bubblings @CYBAI @caiyiliang @ChangJoo-Park @codefalling @Coffcer @CroudSupport @DanielZhu @David-Desmaisons @ElemeFE @F-loat @FE-Driver @FranckFreiburger @FranzSkuffka @GeoffZhu @Ginhing @Gomah @Grottolabs @GuillaumeLeclerc @Haixing-Hu @HerringtonDarkholme @JALBAA @jack85 @JackGit @JosephusPaye @Justineo @Kashio @KoRiGaN @kocisov @KyleRoss @LancerComet @MMF-FE @Ma63d @MacArthurJustin @MarkPieszak @martywallace @Mati365 @MatteoGabriele @MattyRad @Memkits @MetinSeylan @Metnew @MiCottOn @MillerRen @Monine @MopTym @MovingToHTTPS @N3-components @NeutroniumCore @NewDadaFE @NightCatSama @OYsun @OnsenUI @PeachScript @PeakTai @PetervMeijgaard @Plortinus @Polyconseil @QingWei-Li @Radyushin @RashadSaleh @RobinCK @Roeefl @SSENSE @ScreamZ @SevenOutman @SidKwok @SimulatedGREG @SkewedAspect @Socketize @Sopamo @SortableJS @TIGERB @TahaSh @Teddy-Zhu @Treri @Twiknight @Vanthink-UED @VueCluster @Vuedeux @Vuedo @Wanderxx @XeonPowder @XingzheFE @ZeroDark1991 @Zhangdroid @aarondfrancis @abdullah @airbnb @airyland @akifo @alidcastano @andylei18 @antongorodezkiy @apertureless @appcomponents @approach0 @arexio @arvidkahl @asika32764 @astralapp @atwxp @aweber1 @ayamflow @bbonnin @bkzl @blue0728 @bootstrap-vue @bpierre @bradstewart @brandonjpierce @brianvoe @bstavroulakis @budiadiono @buhrmi @c01nd01r @calebroseland @caolinjian @ceolter @cezardasilva @charliekassel @cheapsteak @chenz24 @cklmercer @cngu @codecasts @coderdiaz @compmeist @crossjs @cs1707 @cucygh @dalphyx @dangvanthanh @danielschmitz @danmademe @dargue3 @darrynten @davidmoshal @dealloc @declandewet @delay @devfake @dgerber @didierfranc @dkfbasel @doodlewind @drewjbartlett @dwightjack @ealves-pt @ecerroni @echoVic @eddyerburgh @eduardostuart @egoist @eliep @eljefedelrodeodeljefe @erguotou520 @ericmcdaniel @fancellu @fenivana @fergaldoyle @filipemeneses @firework @fishenal @forehalo @formly-js @foxbenjaminfox @freearhey @fritx @fundon @galenyuan @gismall @gluons @gocanto @greyby @groupwrite-io @gurghet @gustaYo @hal0gen @happilymarrieddad @happyDemon @haydenbbickerton @hchstera @heatherbooker @hedefalk @helpbase @hilongjw @hjeti @holic @huanleguang @iFgR @iatsiuk @icebob @ihanyang @ilyashubin @imcvampire @inca @irwansyahwii @italomaia @itsFrank @iview @jade-press @javisperez @jbaysolutions @jcc @jfelsinger @jiakeqi @jiangjiu @jinzhe @joearcher @joseluisq @jrainlau @julesbou @kaorun343 @karol-f @kartsims @katik @kazupon @kevinongko @kewah @kfei @kikyous @klummy @knpwrs @ktquez @ktsn @kylestlb @lajosbencz @lakb248 @laoshu133 @leaves4j @legeneek @leonardovilarinho @lian-yue @lithiumjake @liujians @lmk123 @locoslab @logaretm @lokyoung @loujiayu @lsycxyj @ludo237 @luojilab @madskristensen @mahmoudmy @marcosmoura @mark-hahn @matfish2 @matiastucci @matt-sanders @mbouclas @metricloop @mgyongyosi @mhayes @miaolz123 @mint- @mint-ui @misterGF @mlyknown @moip @monterail @moonou @mrgodhani @mtorromeo @mul14 @museui @mustardamus @myronliu347 @mysticatea @nblackburn @neposoft @nguyenvanduocit @nicolasbeauvais @niksmr @njleonzhang @nolimits4web @noru @nuxt @octref @okoala @oldj @pagekit @palerdot @pandao @partyka95 @paulpflug @pepf @petervmeijgaard @phanan @phoenixwong @phphe @pinguinjkeke @pluto1114 @pmsaue0 @postalservice14 @posva @pramjeet @processing @qazbnm456 @quasarframework @qxl1231 @rafaelpimpa @rahulgaba16 @rajabishek @rascada @ratiw @rawcreative @rayfranco @reinerBa @revue @rhyzx @ridermansb @rigor789 @robinvdvleuten @rodzzlessa24 @rokups @ropbla9 @rpkilby @rstoenescu @sabrinaluo @sagalbot @saivarunk @saman @samcrosoft @samiheikki @samturrell @sandeepk01 @sant123 @santiblanko @sapjax @scaccogatto @scottbedard @scriptPilot @se-panfilov @sebastian-software @sejr @semisleep @shakee93 @shershen08 @shhdgit @shinygang @shiye515 @simplesmiler @sinchang @sjerrys @skyrpex @staskjs @steven5538 @storyblok @suguangwen @sunabozu @super-dev @superlloyd @superman66 @superwf @surfbirdapp @surmon-china @surveyjs @syropian @taoeffect @termosa @text-mask @the6thm0nth @thelinuxlich @theomessin @thetutlage @tyllo @typicode @uniquezhuo @vace @varHarrie @viko16 @villeristi @vmaimone @vue-bulma @vue-comps @vue-play @vue-typed @vuedev-com @vuejs-br @vuetifyjs @vuets @vuikit @wangdahoo @waynecz @weavingbird @websemantics @weibangtuo @weifeiyue @weilao @weinot @weizhenye @wlada @wovue @wyzant-dev @xanf @xiaokaike @xiaoluoboding @xlsdg @xpepermint @xrado @yang-wei @ycwalker @ye-will @yetaai @yjj5855 @yodfz @yujiahaol68 @zerostatic @zhangxin840 @zhouzhuojie @zllovesuki @znck @zurb @zxdong262
The text was updated successfully, but these errors were encountered: