I have created a personal website to put those demos [1]. It doesn't finish yet and could be linked form Weex's official website when it's done.
It's a static website at present, developers can add examples through PR. I think we could let developers modify or add examples online if it has a backend. [1] https://hanks10100.github.io/weex-vue-examples/ 2017-12-06 10:33 GMT+08:00 方曦(千之) <fangxi...@alibaba-inc.com>: > Also very agree with Hanks. > +1 > > > 在 2017年12月6日，10:31，Jonathan Dong <jondong.commun...@outlook.com> 写道： > > > > I love the idea about the online playground demos, things are kept > online should be easy to publish, modify and revoke. And for the demo > application itself, should be kept as simple as it can be, with minimum > features like navigation, debug, QR scan, and maybe a easy access point to > the online playground demo. > > > > I think I can follow this implementation on app side. > > > >> On 6 Dec 2017, at 10:21 AM, 谷宝剑(剑白) <jianbai....@alibaba-inc.com> > wrote: > >> > >> > >> have an online playground demo like hao123 website, collect as > many example as possible. so that developer can get lastest feature and > example > >> > >> ------------------------------------------------------------------From:Hanks > Zhang <zhanghan...@gmail.com>Time:2017 Dec 5 (Tue) 21:41To:dev < > dev@weex.incubator.apache.org>Subject:Re: Moving Playground & Examples > out of Weex repo > >> Moreover, I think our playground app should be redesigned. > >> > >> Most examples are based on the ".we" framework, which will be removed > soon. > >> Even those examples written in Vue are not the best practice and have no > >> reference value. The UI of it is also rough and has not been updated > for a > >> long time. We should provide more practical examples and make it easy to > >> use. > >> > >> Besides the examples, I think this app is also a link between Weex team > and > >> developers. It can be used to expose information and thoughts to > >> developers, and can also be used to collect the feedback. We should make > >> good use of it. > >> > >> Best Regards, Hanks > >> > >> > >> 2017-10-31 17:49 GMT+08:00 Adam Feng <cxfe...@gmail.com>: > >> > >>> +1 > >>> > >>> The playground in Weex repo should be a simple “Weex browser”, a Weex > >>> examples viewer that lets you navigate to Weex experiences just like > >>> websites. > >>> > >>> Thanks. > >>> Adam Feng > >>> > >>> On 30 Oct 2017, 10:13 PM +0800, xing zhang <zhangxing610...@gmail.com > >, > >>> wrote: > >>>> We should update the Playground App in App Store both on Android and > iOS > >>>> frequently, so the developers can use it to preview their page using > the > >>>> new feature, and we can fix the emergency bug at the same time. > >>>> > >>>> 2017-10-30 21:59 GMT+08:00 Jonathan Dong < > jondong.commun...@outlook.com > >>>> : > >>>> > >>>>> Hi Weex folks, > >>>>> > >>>>> I’m thinking of moving Playground and Examples out of Weex repo to > >>>>> simplify our code base, I hope we can fully discuss if it is > necessary > >>> to > >>>>> make this move. > >>>>> > >>>>> Playground is a good entry to fiddle with the features of basic > >>> components > >>>>> and debug your pages, but it is kind of heavy if we take it as a demo > >>> in > >>>>> the Weex repo. As many of the Weex developers tend to create their > own > >>>>> applications based on the Playground project, I suppose it is > >>> necessary to > >>>>> create a simpler one, say AppShell, which only contains QR Scan and > >>> page > >>>>> load functions, it would be sufficient for users to test their Weex > >>> pages, > >>>>> and much easier for them to take it as an application template to > >>> create > >>>>> their own project. Playground should be maintained in a separate repo > >>> in > >>>>> WeexTeam, which can be maintained and distributed separately. > >>>>> > >>>>> Same things should also happens to examples directory, I suppose what > >>> we > >>>>> really need is one or few simplified example to demonstrate the usage > >>> of > >>>>> the main components and the way of implementing app using Weex in the > >>>>> simplest way, not to keep those detailed example for each components > in > >>>>> Weex repo. Instead I think it is a good practice to move them into > >>> WeexTeam > >>>>> and maintains as a separate repo, and replace the .we implementation > >>> with > >>>>> .vue as well. > >>>>> > >>>>> Any thought? I hope we can fully discuss it and bring out a proposal > to > >>>>> make it happen asap. > >>>>> > >>>>> Cheers, > >>>>> Jonathan Dong > >>>>> > >>>>> > >>> > >> > > > >
