<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tiago Alves on Medium]]></title>
        <description><![CDATA[Stories by Tiago Alves on Medium]]></description>
        <link>https://medium.com/@tiagoreisalves?source=rss-7728756e245a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sPtkR0HyH93414HG2xJiIg.jpeg</url>
            <title>Stories by Tiago Alves on Medium</title>
            <link>https://medium.com/@tiagoreisalves?source=rss-7728756e245a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:27:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tiagoreisalves/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Native apps with Vue.js: Weex or NativeScript? — chapter II]]></title>
            <link>https://medium.com/hackernoon/native-apps-with-vue-js-weex-or-nativescript-chapter-ii-6d1776da090d?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d1776da090d</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[native]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[nativescript]]></category>
            <category><![CDATA[weex]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 01:14:08 GMT</pubDate>
            <atom:updated>2019-05-17T07:11:43.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5WwrrfdfsfLpzcUOAK1QfA.png" /></figure><p>Six months is a lot of time in <a href="https://hackernoon.com/tagged/javascript">Javascript</a> framework land, so <a href="https://hackernoon.com/native-apps-with-vue-js-weex-or-nativescript-8d8f0bac041d">my previous article</a> needs an update. I advise you to check it out before this one, as we go deeper in the philosophies behind Weex and NativeScript-Vue.</p><h3>So… what&#39;s new?</h3><p>Both frameworks are being furiously developed, particularly by improving the limitations <a href="https://hackernoon.com/native-apps-with-vue-js-weex-or-nativescript-8d8f0bac041d">pointed out six months ago</a>.</p><p><strong>Weex</strong> has a <a href="https://weex.apache.org/">new website</a> with better documentation. The CLI tools (weex-toolkit) were refined and should provide a smoother <a href="https://hackernoon.com/tagged/development">development</a> experience. The Weex core team is very invested in showing the framework to the world. Also, now we have the UI lib <a href="https://alibaba.github.io/weex-ui">weex-ui</a> and a solid set of plugins named &#39;<a href="http://natjs.com/">natjs</a>&#39; to access native capabilities.</p><p><strong>NativeScript-Vue </strong>reached <a href="https://nativescript-vue.org/blog/nativescript-vue-1.0-and-a-new-site/">version 1.0</a>! <a href="https://twitter.com/igor_randj">Igor Randjelovic</a> did a great job with the new project website at <a href="https://nativescript-vue.org/blog/nativescript-vue-1.0-and-a-new-site/">nativescript-vue.org</a>. The community grew exponentially after v1.0 was released, with several contributions including a new <a href="https://github.com/nativescript-vue/vue-cli-template">Vue-CLI template</a> by<a href="https://github.com/lewebsimple"> Pascal Martineau</a>. The NativeScript team provides great support for NativeScript-Vue by giving several incentives to community members and adjusting their tooling to specific needs of NativeScript-Vue. For example, you can now use Vue.js directly from the <a href="https://play.nativescript.org/?template=play-vue">NativeScript Playground</a>, and the <a href="https://www.nativescript.org/nativescript-sidekick">Sidekick</a> team is also working on a Vue.js template.</p><h3>Different approaches</h3><p>Weex and NativeScript-Vue are <strong>not</strong> the same thing. The right framework will vary depending on your app and target platforms.</p><h4>Weex</h4><p>With <strong>Weex</strong>, we write html(<em>-ish</em>) and css flexbox that will render into native and web components. This is actually quite hard to do because native UI APIs are very different from flexbox, which makes the UI development somewhat fragile and error prone. You may end up with lots of difficult edge cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5bSblfsoTiNA0oGwuQaEdQ.png" /><figcaption>Weex buttons on iOS/Android/Web</figcaption></figure><p>Also, Weex does very little to respect the native UI. For instance, buttons look <em>exactly</em> the same in iOS, Android and Web (see image above). This can be a good thing if your app is heavily styled, but generally it is a good idea to use native UI components to show a familiar look-and-feel to the user. Sure, Weex builds for the web, but in practice the web build is a second class citizen. Depending on your app size and complexity, you should expect to write at least some amount of platform-specific code.</p><h4>NativeScript-Vue</h4><p>On the other hand, <strong>NativeScript</strong> embraces the native platform. You build the UI with layout elements similar to those you find on native APIs, so the result is more predictable. Consequently, it is easier to build apps that look and feel more native on Android and iOS. As a downside, it cannot build for the web. It is possible, however, to set up your project in a way that allows you to <a href="https://www.nativescript.org/blog/code-sharing-between-web-and-mobile-with-angular-and-nativescript">share as much code as possible</a> between Web and native platforms. Using this technique you only have to duplicate the view layer of the app (templates, css and some UI code).</p><h3>So… which one should I choose?</h3><p>As with most things in development… It Depends™. If you want an app with distinct looks and absolutely need a web build too, then maybe Weex is for you. Just beware of possible edge cases... something may come back to bite you in the future and it is difficult to get support from the community. If you want better native support and look-and-feel, then Nativecript is a solid bet. If you run into trouble, there are lots of people willing to help in <a href="http://nativescriptcommunity.slack.com/">NativeScript Slack</a>&#39;s #vue channel (invites <a href="http://developer.telerik.com/wp-login.php?action=slack-invitation">here</a>).</p><p>As for me, I am still betting on NativeScript-Vue! It feels more predictable and community supported.</p><blockquote><strong>PREVIOUS:</strong><br>&lt;&lt;&lt;&lt; Go to <a href="https://hackernoon.com/native-apps-with-vue-js-weex-or-nativescript-8d8f0bac041d">chapter I</a>.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d1776da090d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/native-apps-with-vue-js-weex-or-nativescript-chapter-ii-6d1776da090d">Native apps with Vue.js: Weex or NativeScript? — chapter II</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native apps with Vue.js: Weex or NativeScript? — chapter I]]></title>
            <link>https://medium.com/hackernoon/native-apps-with-vue-js-weex-or-nativescript-8d8f0bac041d?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d8f0bac041d</guid>
            <category><![CDATA[native]]></category>
            <category><![CDATA[weex]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nativescript]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Sat, 12 Aug 2017 18:44:47 GMT</pubDate>
            <atom:updated>2019-05-17T07:11:45.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7DPKcdQm1mCM4TQtgKGjrg.png" /></figure><blockquote><strong>UPDATE 07-03-2018</strong>: Now there is a <a href="https://medium.com/@tiagoreisalves/native-apps-with-vue-js-weex-or-nativescript-chapter-ii-6d1776da090d">chapter II</a> of this article! Make sure you check it out after reading this one.</blockquote><p><a href="https://hackernoon.com/tagged/vue-js">Vue.js</a> is a great framework! It has a friendly learning curve and combines the best of React’s component approach and Angular’s templates. Despite all this, Vue.js still has a limitation that could be a deal breaker: unlike with React’s <a href="https://hackernoon.com/tagged/react-native">React Native</a>, Vue.js currently has no stable, widely adopted way to develop native apps.</p><p>This is bound to change, though! There are currently two frameworks under development that could open the door to creating native apps with Vue.js, the framework we all love and cherish: <strong>Weex</strong> and <strong>NativeScript</strong>. In this article we will compare both frameworks and give you enough of a taste to at least try one of them!</p><h3>Weex</h3><p><a href="https://weex.incubator.apache.org/">Weex</a> is a project created by the chinese e-commerce giant Alibaba. Its slogan is &quot;Write once, run Everywhere&quot;, meaning that you can produce builds for web (html5), Android and iOS from the exact same codebase. There are several Weex projects currently in production, in the hands of probably millions of users in China. The core of Weex is in active development with PRs coming every week. Weex has several components, plugins to interact with the native platform, and a set of tools that are still somewhat crude.</p><p>Unfortunately, Weex developers don’t see making the platform available for the open source community as a big priority. Sure you have <a href="https://weex.incubator.apache.org/references/">documentation</a>, github repos, etc., and some things are getting better now that Weex is under the Apache Incubator (ASF). But… there is still no clear way to build a Weex project from scratch without a considerable amount of hacking on the native code. Also, forget talking in English in the <a href="https://gitter.im/weexteam/cn">official gitter channel</a>…</p><h3>NativeScript</h3><p>In April, <a href="https://twitter.com/igor_randj">Igor Randjelovic</a> <a href="https://twitter.com/igor_randj/status/854501034697383936?ref_src=twsrc%5Etfw&amp;ref_url=https%3A%2F%2Fwww.nativescript.org%2Fblog%2Fa-new-vue-for-nativescript">opened up</a> the possibility to use Vue with NativeScript. <a href="https://github.com/rigor789/nativescript-vue">nativescript-vue</a> is a NativeScript plugin that bridges the gap between Vue.js virtual DOM and NativeScript components, allowing you to build cross-platform apps with Vue.js. Although the project is still in early stages and not suitable for production apps, it has lots of potential because it leverages the NativeScript framework with all of its tools and huge inventory of components and <a href="http://plugins.nativescript.org/">plugins</a>. With webpack, you can even use .vue single file components (see <a href="https://github.com/tralves/nativescript-vue-webpack-template">this template</a>).</p><p>The community is great and <a href="https://www.nativescript.org/blog/2017-sweetness-and-light-summer-app-contest">very</a> <a href="https://www.nativescript.org/blog/announcing-the-winners-of-the-vue.js-nativescript-contest">well</a> <a href="https://twitter.com/igor_randj/status/874941696307593216">tendered</a>! If you join the <a href="http://developer.telerik.com/wp-login.php?action=slack-invitation">official slack</a> you will find lots of friendly people willing to help, including NativeScript core team developers, nativescript-vue creator, and other folks involved on the project. There are lots of people wanting nativescript-vue to work!</p><h3>Summary of Pros and Cons</h3><p>Summing up the pros and cons of each framework, we have:</p><h4>Weex :</h4><p>👍 In production (although, only in China);<br>👍 Builds for Web, Android and iOS;<br>👎 Bad community;<br>👎 Crude tools;<br>👎 No clear path to start a project;</p><h4>nativescript-vue:</h4><p>👍 Awesome community!<br>👍 Leverages all of NativeScript platform;<br>👎 Not ready for production;<br>👎 Builds only for Android and iOS (although there are people working on code sharing with a web build);</p><h3>Final verdict</h3><p>In open source projects, community trumps technology. Weex had a several months head start and is backed by a huge company, but we haven’t seen much progress in the community side of things. On the other hand, <strong>NativeScript + Vue</strong> has been getting an increasing amount of traction. Sure, there are some rough edges, but once they are cleared out we will have a solid framework to develop native apps with Vue.js.</p><p>I am betting on <strong>NativeScript</strong>!</p><blockquote><strong>NEXT:</strong><br>&gt;&gt;&gt;&gt; Go to <a href="https://medium.com/@tiagoreisalves/native-apps-with-vue-js-weex-or-nativescript-chapter-ii-6d1776da090d">chapter II</a>.</blockquote><h3>Links</h3><h4><strong>Weex:</strong></h4><ul><li>Official website: <a href="http://weex.incubator.apache.org/">http://weex.incubator.apache.org/</a></li><li>Weex How-to: <a href="https://hackernoon.com/how-to-create-a-weex-vue2-project-6b94981bee4e">https://hackernoon.com/how-to-create-a-weex-vue2-project-6b94981bee4e</a></li><li>Demo To-Do app made with Weex: <a href="https://github.com/tralves/weex-todo-list">https://github.com/tralves/weex-todo-list</a></li></ul><h4>NativeScript + Vue.js:</h4><ul><li>nativescript-vue: <a href="https://github.com/rigor789/nativescript-vue">https://github.com/rigor789/nativescript-vue</a></li><li>Article about nativescript-vue: <a href="https://www.nativescript.org/blog/a-new-vue-for-nativescript">https://www.nativescript.org/blog/a-new-vue-for-nativescript</a></li><li>NativeScript slack channel: <a href="http://developer.telerik.com/wp-login.php?action=slack-invitation">http://developer.telerik.com/wp-login.php?action=slack-invitation</a></li><li>NS + Vue template: <a href="https://github.com/tralves/nativescript-vue-template">https://github.com/tralves/nativescript-vue-template</a></li><li>NS + Vue template with webpack (ready for .vue single file components): <a href="https://github.com/tralves/nativescript-vue-webpack-template">https://github.com/tralves/nativescript-vue-webpack-template</a></li></ul><h4>Hmm… how do you know all this stuff?</h4><p>I have been playing with Weex for a while. I <a href="https://twitter.com/tiagoreisalves/status/816466567496089601">made</a> <a href="https://twitter.com/tiagoreisalves/status/841504371015860224">tests</a>, built a <a href="https://github.com/tralves/weex-todo-list">demo app</a>, a <a href="https://www.youtube.com/watch?v=ZM3tJMSNC1E&amp;feature=youtu.be">walkthrough video</a>, <a href="https://medium.com/@tiagoreisalves/the-state-of-weex-an-inaccurate-and-outdated-report-fae2c6e5fc2e">wrote</a> <a href="https://hackernoon.com/how-to-create-a-weex-vue2-project-6b94981bee4e">articles</a>, and <a href="https://docs.google.com/presentation/d/18NKqd3_AHmAXQCx_37rVf_v16-HHSkCxJ85qYu6SF7Y/edit?usp=sharing">presented about Weex</a> in <a href="https://twitter.com/tiagoreisalves/status/854840414611931136">local events</a>. Then, I boarded the nativescript-vue train! I wrote a <a href="https://github.com/tralves/not-hotdog-ns-vue">silly app</a>, <a href="https://www.nativescript.org/blog/announcing-the-winners-of-the-vue.js-nativescript-contest">won a contest</a> and built a <a href="https://github.com/tralves/nativescript-vue-template">couple</a> of <a href="https://github.com/tralves/nativescript-vue-webpack-template">templates</a> to smooth the getting started process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d8f0bac041d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/native-apps-with-vue-js-weex-or-nativescript-8d8f0bac041d">Native apps with Vue.js: Weex or NativeScript? — chapter I</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native Mobile Apps with Weex and VueJS 2.0]]></title>
            <link>https://medium.com/hackernoon/how-to-create-a-weex-vue2-project-6b94981bee4e?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b94981bee4e</guid>
            <category><![CDATA[weex]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Mon, 10 Apr 2017 14:33:51 GMT</pubDate>
            <atom:updated>2019-05-17T07:11:45.532Z</atom:updated>
            <content:encoded><![CDATA[<p>How to build a Weex app for the Web, Android and iOS!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOj6fHhJUWowFGgp9dsQXg.jpeg" /></figure><p>If you read <a href="https://medium.com/@tiagoreisalves/the-state-of-weex-an-inaccurate-and-outdated-report-fae2c6e5fc2e">The State of Weex: an inaccurate and outdated report</a>, you learned that there was no clear path to make a Weex VueJS app that would build for the web, <a href="https://hackernoon.com/tagged/android">Android</a> and iOS.</p><p>Well… now there is! Let’s do it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*LWNONuXCJ0ONKdh0MOAQWQ.gif" /></figure><p>OK… maybe we should set the proper expectations here. Weex still has a <strong>lot</strong> of rough edges. This tutorial will not end a deployable production app. You will, however, see a simple Weex Vue2.0 app working on the browser and on your phone. And that’s a pretty good milestone.</p><h3>Install the tools</h3><p>We will need <a href="https://github.com/vuejs/vue-cli">vue-cli</a> to install the template and <a href="https://github.com/weexteam/weex-toolkit">weex-toolkit</a> which has the tools to build the native app.</p><pre>&gt; npm install -g vue-cli<br>&gt; npm install -g weex-toolkit</pre><h3>Create app</h3><p>Create the app from this <a href="https://github.com/tralves/weex-vue">weex-vue template</a>.</p><pre>&gt; vue init tralves/weex-vue &lt;project_name&gt;<br>&gt; cd &lt;project_name&gt;<br>&gt; npm install</pre><p>The template creates a project with the folder structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/186/1*xAyBQVu5TWiV_aqjyN8scQ.jpeg" /><figcaption>Folder structure</figcaption></figure><p>The important folders are:</p><ul><li>dist — where the compiled js will go.</li><li>platforms — Android/iOS native projects.</li><li>src — the app code.</li></ul><p>Other important files:</p><ul><li>config.xml — a cordova config file used to generate the native projects. This is not working properly yet.</li><li>weex.html — the entry file of the web version.</li><li>app.js — the <a href="https://hackernoon.com/tagged/vuejs">VueJS</a> bootstrap file used inweex.html .</li><li>index.html —renders the app in a mobile-like frame. Displays a QR-Code you can use to load your app into the <a href="https://weex.apache.org/playground.html">Weex playground app</a>.</li></ul><p>Your app will be in src. If you open the App.vue file, you will find a simple layout with only two Weex components: &lt;image&gt; and &lt;text&gt;. You can find more about all the Weex components <a href="https://weex.apache.org/references/components/index.html">in the official docs</a>. Weex compiles these components into html for the web version (e.g. an &lt;image&gt; becomes an &lt;img&gt;) and into native components for the iOS/Android apps.</p><p>This example is very simple, but you can build more complex apps. Check out the <a href="https://github.com/weexteam/weex-hackernews">weex-hackernews</a> and <a href="https://github.com/tralves/weex-todo-list">weex-todo-list</a>. These apps show how to use vue-router, vuex, locally persistent data, etc.</p><h3>Web build</h3><pre>&gt; npm run build<br>&gt; npm run serve</pre><p>The command npm run build compiles the web and native versions of the app into build/. The npm run serve starts a local webserver.</p><p>Now you can point your browser to <a href="http://localhost:8080to">http://localhost:8080</a> to preview the mobile app in the browser, and http://localhost:8080/weex.html to access the web version.</p><h3>Android build</h3><p>Firstly, we need to:</p><ul><li>Download and install <a href="https://www.google.com.br/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwiO97vWqZjTAhWGEJAKHWL4AwEQFggiMAA&amp;url=https%3A%2F%2Fdeveloper.android.com%2Fstudio%2Findex.html&amp;usg=AFQjCNFxiiJ5jw3OprFf7ya-IJj9GFv2Eg&amp;sig2=69T1Hl64JW95-mSaCQIF7w">Android Studio</a>.</li><li>Add the $ANDROID_HOME environment variable and add the SDK tools to the $PATH. In my case I added to .bash_profile:</li></ul><pre>export ANDROID_HOME=~/Library/Android/sdk<br>export PATH=${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools:$ANDROID_HOME/build-tools</pre><p>Then we add the android platform:</p><pre>&gt; weex platform add android</pre><p>Then, connect an Android device (<a href="https://www.howtogeek.com/129728/how-to-access-the-developer-options-menu-and-enable-usb-debugging-on-android-4.2/">with USB debug activated</a>) and run:</p><pre>&gt; weex run android</pre><blockquote>Note: If you don’t have an Android device, it will use an emulator which is <em>very</em> slow.</blockquote><p>And that’s it! The app should be running in the device!</p><h3>iOS build</h3><p>Pre-requirements:</p><ul><li>Xcode</li><li><a href="https://cocoapods.org/">CocoaPods</a></li></ul><p>Then:</p><pre>&gt; weex platform add ios</pre><p>Install cocoapods dependencies:</p><pre>&gt; cd platforms/ios<br>&gt; pod install</pre><p>Open the Xcode workspace WeexDemo.xcworkspace under platforms/ios.</p><p>Add the dependencies from the pods:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*4JpbJpw3j7s9V66nwFxM9w.jpeg" /></figure><ul><li>Open General settings.</li><li>(1) press ‘+’ under <strong>Linked Framework and Libraries</strong></li><li>(2) Select the libs libSDWebImage.a, libSocketRocket.a and libWeexplugin.a.</li><li>(3) Press ‘Add’</li></ul><p>Run the project!</p><blockquote>I had some problems with outdated cocoapods. If you run into compilation issues, try pod update.</blockquote><h3>Next steps for weex-vue?</h3><p>The TODO list is big:</p><ul><li>Fix config.xml settings.</li><li>Have config.xml generate a properly configured Android/iOS projects. Currently, this template generates projects with the wrong names, icons, app ids, etc.</li><li>Fix the debugging tools. Weex has pretty amazing debugging tools that use the Chrome Dev Tools. I couldn’t make it work properly so far.</li><li>Improve build tools: icon/splash screen generators, distributable Web builds, etc.</li><li>Tools and tutorials about Weex plugins, components that interact with the native capabilities.</li><li>More demo apps, with more complex scenarios, that will show more Weex components and plugins.</li></ul><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b94981bee4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-create-a-weex-vue2-project-6b94981bee4e">Native Mobile Apps with Weex and VueJS 2.0</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The State of Weex: an inaccurate and outdated report]]></title>
            <link>https://medium.com/@tiagoreisalves/the-state-of-weex-an-inaccurate-and-outdated-report-fae2c6e5fc2e?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fae2c6e5fc2e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[weex]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Tue, 28 Feb 2017 14:46:27 GMT</pubDate>
            <atom:updated>2017-02-28T14:46:27.243Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*JGQP6WjsRwiiLTNPiCAH5A.png" /></figure><blockquote>Disclaimer: This is what we know as of 28th February 2017 and will soon (hopefully) be even more inaccurate and outdated!</blockquote><p>A few weeks ago I decided I wanted to fiddle with <a href="https://weex-project.io/">Weex, A framework for building Mobile cross-platform UI</a> with <a href="http://vuejs.org/">Vue.js</a>. The project promises a lot:</p><blockquote>Write Once Run Everywhere: Weex provides the ability to cross platform, such as the web, Android and IOS can use the same API development function.</blockquote><p>Weex is currently being actively developed mostly by <a href="https://www.alibaba.com/">Alibaba</a>’s dev team, which is great because they are huge! Unfortunately, this also means that most of the documentation and discussions in Git or Gitter are written in chinese… Also, most of the docs are behind the actual development stage of the project.</p><p>That’s why I am pretty sure this report is both inaccurate and outdated. So… why would you want to read this? <strong>Because, unless you read Chinese, this is the best report you’ll get!</strong></p><h3>How to create a Weex app?</h3><p>Some weeks ago, <a href="https://github.com/weexteam">weexteam</a> released a <a href="https://github.com/weexteam/weex-hackernews">weex-hackernews</a> with everything you would expect from Weex: a project with the same code running on web, Android and iOS. And it worked! I was able to make a build for all the platforms and even collected some evidence that it used real native components for both Android and iOS:</p><h3>Tiago Alves on Twitter</h3><p>Native @vuejs #weex HN example app! Both Xcode and Android Monitor show the native layout components. How cool is THAT?! #vuejsnativenow!</p><p>So how could I create one app like that? Should be an easy question, right? Just look at the <em>“Getting Started”</em> section of the docs, yes? <strong>Nop…</strong></p><p>The <a href="https://weex-project.io/guide/index.html">official documentation</a> tells us to use <a href="https://github.com/weexteam/weex-toolkit">weex-toolkit</a>, except that when you use it, it does not create the Android/iOS boilerplate.</p><p>There is also <a href="https://github.com/weexteam/weex-pack">weex-pack</a>, the <em>“next generation of engineering development kits”</em> that “<em>helps to setup weex application from scratch quickly”</em>. This tool offers CLI commands similar to Cordova (i.e. add/remove platform). Unfortunately, it creates a project for a previous version of Weex, one that doesn’t really use Vue 2.0.</p><p>It seems like there is no way to build an app like weex-hackernews from scratch. Evan You <a href="https://youtu.be/E84m5KrzOZk?t=7m43s">mentioned</a> a new Weex vue-cli template which means that soon we will be able to start a Weex project with vue-init weex my-project.</p><p>Since I couldn’t wait, I created a Weex Todo app by grabbing the hackernews app and hacking the hell out of it.</p><h3>Tiago Alves on Twitter</h3><p>Today I built a To-do app with Weex + Vue2.0! Vid: https://t.co/2l5xGk3AlD GitHub: https://t.co/Gz0XoGiE9u #VueJS #Weex @vuejs</p><p>This is what I learned about development with Weex.</p><h3>Development with Weex</h3><p>For the most part, everything works as you would expect. The Vue code runs well in the native environment, once you get around the following caveats:</p><h4>There is no DOM in native</h4><ul><li>Events don’t bubble up like in HTML5. (Good! No preventDefault().)</li><li>You can’t simply query the DOM to get an element. (It forces you to have stronger references to the UI elements, which is a good practice anyway!)</li><li>CSS classes don’t cascade to child elements. Also toggling classes doesn’t work. Changing the :style directive dynamically does work.</li><li>Weex implements a subset of box model and flexbox layout. Not all flexbox properties will work exactly the same way in native as in the browser.</li><li>You don’t have all HTML5 APIs. For instance, instead of localStorage I had to use the <a href="https://weex-project.io/references/modules/storage.html">weex storage module</a>.</li><li>There are some inconsistencies between all platforms. If you compare the <a href="https://www.youtube.com/watch?v=4L4ABYDhpsA">iOS demo</a> with the <a href="https://www.youtube.com/watch?v=AMU0gXuEl_Y">Android demo</a>, you’ll see some misalignments inside the buttons.</li></ul><p>For more information about these differences, <a href="https://weex-project.io/cn/references/vue/difference-with-web.html">check out this page</a> (Google Chrome’s translation will be your friend).</p><p>Other than that, it was straight Vue.js development. I used vue-router ,vuex and other external javascript libs with no problem.</p><h4>Lack of dev/debug tools for native platforms</h4><p>While developing in the browser I could use the regular Vue tools, but once the app was running in the native environment I couldn’t find a way to debug the javascript nor the UI.</p><h3>Give it some time!</h3><p>Weex is still a bit far from its initial goal of “<em>Write Once Run Everywhere”</em>, but I <strong>know</strong> it will get there. Why?</p><ul><li>Vue.js is growing fast and getting close to React. In the same way, Weex will get closer to React Native in community and support.</li><li>Weex’s goal of “<em>Write Once Run Everywhere”</em> is more compelling for the web developer than React Native’s <em>“Learn Once, Write Anywhere”</em>. Some hindrances aside, I built an app that runs on web, android and iOS with the<strong> same code</strong>!</li><li>Evan You is actively involved with Weex and I have no doubt he will make Weex more “open” to the open source community outside China.</li></ul><p>Is Weex something to keep an eye on? Absolutely! Would I start a real-world project with Weex right now? Absolutely not! Not yet…</p><p>Nevertheless, I will be <strong>very happy </strong>to see this report be even more inaccurate and outdated in a couple of weeks…</p><p>I would also be <strong>very happy</strong> if someone would tell how inaccurate and outdated this is! If you can, please leave a comment. I would love to learn more!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fae2c6e5fc2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Bíblia em “Carga de Ombro” de Samuel Úria]]></title>
            <link>https://medium.com/@tiagoreisalves/a-b%C3%ADblia-em-carga-de-ombro-de-samuel-%C3%BAria-4940558bd85c?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4940558bd85c</guid>
            <category><![CDATA[bíblia]]></category>
            <category><![CDATA[carga-de-ombro]]></category>
            <category><![CDATA[samuel-úria]]></category>
            <category><![CDATA[jesus]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Sun, 08 Jan 2017 20:53:03 GMT</pubDate>
            <atom:updated>2017-04-12T02:40:06.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*rQ9bKIheGNUnYILmXzO3eg.jpeg" /></figure><h4>Uma lista das referências bíblicas e teológicas das letras do último álbum de Samuel Úria</h4><p>Provavelmente Samuel Úria é hoje a voz protestante evangélica mais ouvida em Portugal. As suas letras espelham a integridade de um homem de fé que vive a fé. É só querer ouvir...</p><p>Propus-me a fazer uma lista das interseções entre o disco “Carga de Ombro” e a Bíblia. Não pretendo fazer uma exegese das letras (isso seria pretensioso da minha parte), mas limito-me a listar as vezes em que Samuel claramente referencia a Bíblia ou algum conceito teológico.</p><blockquote>Nota: Nem sempre a referência é aplicada no sentido direto. Por vezes a referência é usada como contraste ou num sentido irónico.</blockquote><p>Espero que seja de utilidade para quem queira entender um pouco melhor a sua poesia. Já que o Samuel Úria segue o Deus que se revelou, acho que ele não se vai importar de ser revelado... Vamos lá!</p><h3><strong>01- Dou-me Corda</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZr2G6Zoem5U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZr2G6Zoem5U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZr2G6Zoem5U%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/60c9542e418a433e5760d2e93399717b/href">https://medium.com/media/60c9542e418a433e5760d2e93399717b/href</a></iframe><h4><strong>(4) “Mas com fascínio travestido de mulher de Ló”</strong></h4><blockquote><strong><em>Livro de Génesis 19:26</em>:</strong> Mas a mulher de Ló olhou para trás e ficou convertida em uma estátua de sal.</blockquote><h4><strong>(7)</strong> “O livre arbítrio fez voz grossa mas saiu falsete”</h4><p><em>Livre arbítrio</em> é a capacidade de cada um fazer escolhas. Como conceito teológico, deve ser visto justapondo com a Soberania de Deus.</p><h4><strong>(8) “Mantive a Fé e o bom combate na carreira das 7”</strong></h4><blockquote><strong><em>2ª Carta de Paulo a Timóteo 4:7:</em></strong> Combati o bom combate, acabei a carreira, guardei a fé.</blockquote><h3>02- É preciso que eu diminua</h3><blockquote><strong><em>João Batista diz acerca de Jesus em João 3:30:</em></strong> é necessário que ele cresça e que eu diminua.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fij6u67SoFpA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dij6u67SoFpA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fij6u67SoFpA%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2ad082a008ff6d96dd11ce093961df0/href">https://medium.com/media/c2ad082a008ff6d96dd11ce093961df0/href</a></iframe><h4>(3) “Não são obras que me salvam”</h4><blockquote><strong><em>Carta aos Efésios 2:8–9:</em></strong> Porque pela graça sois salvos, por meio da fé; e isto não vem de vós, é dom de Deus; não vem das obras, para que ninguém se glorie.</blockquote><h4>(22) “Mas bato no peito”</h4><blockquote><strong><em>Sinal de arrependimento, por ex., Lucas 18:13:</em></strong> Mas o publicano, estando em pé de longe, nem ainda queria levantar os olhos ao céu, mas batia no peito, dizendo: ó Deus, sê propício a mim, o pecador!</blockquote><h4>(41) “Fermento em massa de autismo”</h4><blockquote><strong><em>Na Bíblia, o fermento simboliza a corrupção e pecado, por ex. em Mateus 16:6: </em></strong>E Jesus lhes disse: Olhai, e acautelai-vos do fermento<strong> </strong>dos fariseus e dos saduceus.</blockquote><h3>03- Carga de Ombro</h3><blockquote><strong><em>Gálatas 6:2:</em></strong> Levai as cargas uns dos outros, e assim cumprireis a lei de Cristo.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYJDx-X2-6BI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYJDx-X2-6BI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYJDx-X2-6BI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b242dce52deddcd08cfdef8a4604050a/href">https://medium.com/media/b242dce52deddcd08cfdef8a4604050a/href</a></iframe><h4>(14) “A justiça tem de vir”</h4><blockquote><strong><em>A “vinda” da justiça de Deus aparece por toda a Bíblia como uma forma em que o Seu domínio é mais visível. Por ex., Mateus 6:33:</em></strong><em> </em>Mas buscai primeiro o seu reino e a sua justiça, e todas estas coisas vos serão acrescentadas.<br><strong><em>Também em Isaías 51:5: </em></strong>De repente minha justiça chegará, minha salvação vai aparecer, as ilhas em mim terão esperança e contarão com meu braço.</blockquote><h3>04- Graça Comum</h3><p>“Graça Comum”, em teologia, é o favor imerecido que Deus vai concedendo à humanidade em geral, mesmo aos que O rejeitam.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fs-4EU3tYga8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ds-4EU3tYga8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fs-4EU3tYga8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6e1d0f167500b6ba506945439506ae11/href">https://medium.com/media/6e1d0f167500b6ba506945439506ae11/href</a></iframe><h4>(3) “Quero sobrolho interdito a citar a Lei”</h4><blockquote><strong><em>Referência à Lei dada por Deus através de Moisés. Por ex. João 1:17: </em></strong>Porque a lei<strong> </strong>foi dada por meio de Moisés; a graça e a verdade vieram por Jesus Cristo.</blockquote><h4>(9) “Quero ter queixo caído a ganhar o Céu”</h4><blockquote><strong><em>O Céu é o Paraíso. Vejamos esta resposta de Jesus ao jovem rico, em Marcos 10:21:</em></strong> E Jesus, olhando para ele, o amou e lhe disse: Uma coisa te falta; vai vende tudo quanto tens e dá-o aos pobres, e terás um tesouro no céu; e vem, segue-me.</blockquote><h3>06- Aeromoço</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqEHGyAjsZoY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqEHGyAjsZoY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqEHGyAjsZoY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba2a5797ed6a0357919f3618e60cac38/href">https://medium.com/media/ba2a5797ed6a0357919f3618e60cac38/href</a></iframe><h4>(3, 6, 9, 14, 17, 20) “chão”</h4><blockquote><strong><em>O “chão” ou “terra” refere-se ao que é mundano, não espiritual. P. ex. Colossenses 3:2: </em></strong>Pensai nas coisas que são de cima, e não nas que são da terra;</blockquote><h4>(7, 8, 9, 18, 20) “mundo”</h4><blockquote><strong><em>“Mundo” enquanto sistema em rebelião com Deus. P. ex. João 15:19:</em></strong> Se fôsseis do mundo, o mundo amaria o que era seu; mas, porque não sois do mundo, antes eu vos escolhi do mundo, por isso é que o mundo vos odeia.</blockquote><h4>(10, 20, 26) “Volta lá ao teu primeiro amor”</h4><blockquote><strong><em>No livro de Apocalipse (2:4), Jesus condena a igreja em Éfeso:</em></strong> Tenho, porém, contra ti que deixaste o teu primeiro amor.</blockquote><h3>07- Ei-Lo</h3><blockquote><strong><em>João Batista disse (João 1:29 e 26):</em></strong> Eis o cordeiro de Deus…</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvVRdRYAq5hA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvVRdRYAq5hA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvVRdRYAq5hA%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6bc1b17970ca1d83ec08ecea01f9e955/href">https://medium.com/media/6bc1b17970ca1d83ec08ecea01f9e955/href</a></iframe><h4>(1) “Tinhas palavras para calar o mar”</h4><blockquote><strong><em>Marcos 9:39:</em></strong> E ele, levantando-se, repreendeu o vento, e disse ao mar: Cala-te, aquieta-te.</blockquote><h4>(2–3) “E até citavas quem basicamente / Esteve a citar as coisas que vinhas fazer”</h4><blockquote><strong><em>Em Lucas 4:16–21, Jesus leu no livro de Isaías, escrito cerca de 600 anos antes, uma profecia acerca dEle próprio:</em></strong> Chegando a Nazaré, onde fora criado; entrou na sinagoga no dia de sábado, segundo o seu costume, e levantou-se para ler. Foi-lhe entregue o livro do profeta Isaías; e abrindo-o, achou o lugar em que estava escrito: O Espírito do Senhor está sobre mim, porquanto me ungiu para anunciar boas novas aos pobres; enviou-me para proclamar libertação aos cativos, e restauração da vista aos cegos, para pôr em liberdade os oprimidos, e para proclamar o ano aceitável do Senhor. E fechando o livro, devolveu-o ao assistente e sentou-se; e os olhos de todos na sinagoga estavam fitos nele. Então começou a dizer-lhes: Hoje se cumpriu esta escritura aos vossos ouvidos.</blockquote><h4>(6) “E que lição nos dás por não responderes?”</h4><blockquote><strong><em>Esta ideia aparece muitas vezes nesta letra (4–5, 6, 8–9, 11, 12–13, 14, 15, 21). Refere-se ao fato de Jesus não se ter defendido no seu julgamento. Marcos 14:60–61:</em></strong> Levantou-se então o sumo sacerdote no meio e perguntou a Jesus: Não respondes<strong> </strong>coisa alguma? Que é que estes depõem conta ti? Ele, porém, permaneceu calado, e nada respondeu. Tornou o sumo sacerdote a interrogá-lo, perguntando-lhe: és tu o Cristo, o Filho do Deus bendito?<br><strong><em>Isto estava profetizado também em Isaías 53:7:</em></strong> Ele foi oprimido e afligido, mas não abriu a boca; como um cordeiro que é levado ao matadouro, e como a ovelha que é muda perante os seus tosquiadores, assim ele não abriu a boca.</blockquote><h4>(7) “Eu já lá estava pra te negar”</h4><blockquote><strong><em>Pedro negou a Cristo três vezes enquanto Ele estava a ser julgado (Marcos 14:66–72): </em></strong>Ora, estando Pedro em baixo, no átrio, chegou uma das criadas do sumo sacerdote e, vendo a Pedro, que se estava aquentando, encarou-o e disse: Tu também estavas com o nazareno, esse Jesus. Mas ele o negou, dizendo: Não sei nem compreendo o que dizes. E saiu para o alpendre. E a criada, vendo-o, começou de novo a dizer aos que ali estavam: Esse é um deles. Mas ele o negou outra vez. E pouco depois os que ali estavam disseram novamente a Pedro: Certamente tu és um deles; pois és também galileu. Ele, porém, começou a praguejar e a jurar: Não conheço esse homem de quem falais. Nesse instante o galo cantou pela segunda vez. E Pedro lembrou-se da palavra que lhe dissera Jesus: Antes que o galo cante duas vezes, três vezes me negarás. E caindo em si, começou a chorar.</blockquote><h4>(14) “Ei-lo, verbo antigo, a suster a voz”</h4><blockquote><strong><em>João 1:1, acerca de Jesus:</em></strong> No princípio era o Verbo, e o Verbo estava com Deus, e o Verbo era Deus.</blockquote><h4>(15) “Pra que o copo não passasse por nós”</h4><blockquote><strong><em>O cálice (copo) é o sofrimento de Jesus na cruz no nosso lugar. Mateus 26:39:</em></strong> E adiantando-se um pouco, prostrou-se com o rosto em terra e orou, dizendo: Meu Pai, se é possível, passa de mim este cálice; todavia, não seja como eu quero, mas como tu queres.</blockquote><h4>(16) “Eis o rei dos réus, o agitador”</h4><blockquote><strong><em>“Rei dos reis” é um título atribuído a Jesus. 1 Timóteo 6:15:</em></strong> Ele é o bendito e único Soberano, o Rei dos reis e Senhor dos senhores.</blockquote><blockquote><strong><em>Jesus foi acusado de “agitador” em Lucas 23:14:</em></strong> Apresentastes-me este homem como agitador do povo, mas, interrogando-o eu diante de vós, não o achei culpado de nenhum dos crimes de que o acusais.</blockquote><h4>(18) “Eras convite também à expulsão”</h4><blockquote><strong><em>Jesus convidou em João 11:28:</em></strong> Vinde a mim, todos os que estai cansados e oprimidos, e eu vos aliviarei.</blockquote><blockquote><strong><em>Jesus também expulsou (Mateus 21:12):</em></strong> Então Jesus entrou no templo, expulsou todos os que ali vendiam e compravam, e derribou as mesas dos cambistas e as cadeiras dos que vendiam pombas;</blockquote><h4>(19–21) “Tinhas o dedo para pôr na ferida / Nalguns pra sarar e noutros para fazer doer”</h4><blockquote><strong><em>Jesus curava impondo as mãos. Por ex. Marcos 8:23:</em></strong> Jesus, pois, tomou o cego pela mão, e o levou para fora da aldeia; e cuspindo-lhe nos olhos, e impondo-lhe as mãos, perguntou-lhe: Vês alguma coisa?</blockquote><p>Existem outras referências menos óbvias, mas sobre essas não vou arriscar uma interpretação. Por exemplo, a faixa 11 “Vem por mim” não falará da segunda vinda de Cristo?</p><p>Que acham? Escapou-me alguma coisa? Coloquei alguma a mais?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4940558bd85c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why not to use Swagger-PHP]]></title>
            <link>https://medium.com/@tiagoreisalves/why-not-to-use-swagger-php-ec509590fefb?source=rss-7728756e245a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec509590fefb</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[swagger]]></category>
            <dc:creator><![CDATA[Tiago Alves]]></dc:creator>
            <pubDate>Thu, 04 Feb 2016 12:59:02 GMT</pubDate>
            <atom:updated>2016-05-11T16:55:58.748Z</atom:updated>
            <content:encoded><![CDATA[<p>In a project I decided to use the package <a href="https://github.com/slampenny/Swaggervel">Swaggervel</a>, which combines generating <a href="http://swagger.io/">Swagger</a> documentation with <a href="https://github.com/zircote/swagger-php">Swagger-PHP</a> and serving swagger-ui all in a nice Laravel package.</p><p>Swagger-PHP generated swagger documentation from annotations, which is a great idea because having the docs and the code in the same place makes it easier to keep both in sync. I had each endpoint documentation above the corresponding action in the controller and documented the model definitions in the (thephpleague/fractal) Transformer classes.</p><p>So great! I actually managed to document my Api with these annotations, but:</p><ul><li>It was very, very hard;</li><li>Poor documentation. The <a href="http://zircote.com/swagger-php/">official documentation</a> is outdated. Had to do everything based <a href="https://github.com/zircote/swagger-php/tree/master/Examples">on the examples</a>, and even search the source code of the package in order to figure some things out. Basically a trial and error process;</li><li>The syntax is awful. It is very wordy and hard to read. It would be nice if I could use those annotations as documentation for the code, but they are very hard to read even for me, who created them in the first place! Ended up with huge blocks of comments in my code that I hated to have to scroll through;</li><li>Hard to test. Change the annotations, generate the json, paste it into swagger editor and then see the error. Then repeat…</li></ul><p>The main advantage of having the documentation along with the code so that you could keep code and docs in sync simply disappeared in the middle of all these problems.</p><p>So in my case, when the time came when the Api had some changes and another developer coming along, we just quit using swagger-php annotations and just use swagger editor to generate the .json.</p><p>I still use the <a href="https://github.com/slampenny/Swaggervel">Swaggervel</a> package to serve the swagger-ui though.</p><p>That’s it. I hope this helps someone…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec509590fefb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>