Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F2CEF200D37 for ; Thu, 9 Nov 2017 20:27:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F14A4160BEF; Thu, 9 Nov 2017 19:27:28 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E81861609C8 for ; Thu, 9 Nov 2017 20:27:27 +0100 (CET) Received: (qmail 72106 invoked by uid 500); 9 Nov 2017 19:27:27 -0000 Mailing-List: contact dev-help@royale.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@royale.apache.org Delivered-To: mailing list dev@royale.apache.org Received: (qmail 72091 invoked by uid 99); 9 Nov 2017 19:27:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2017 19:27:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DFDDA180146 for ; Thu, 9 Nov 2017 19:27:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.65 X-Spam-Level: X-Spam-Status: No, score=-0.65 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, KAM_INFOUSMEBIZ=0.75, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id lG7OWhb6Zbo7 for ; Thu, 9 Nov 2017 19:27:23 +0000 (UTC) Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com [209.85.128.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 2462D5F5B8 for ; Thu, 9 Nov 2017 19:27:23 +0000 (UTC) Received: by mail-wr0-f175.google.com with SMTP id y9so6602697wrb.2 for ; Thu, 09 Nov 2017 11:27:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=AXfvtaoB1FKuNjr92vmY2R2qROx8AiOB95PC4MKhE8k=; b=oS2IvlRcqy9Qht2EdV8+5RRK9Uozfpozwpyn7ZJnYzc241MulKFWkXsbO2+KYAqSvp +TkTEKfpiiZm/Cd5lhS5/mqLqBISNHTq0/UkcI+UGHAtVKK8g+yUBLI89xTCQu+LdUSX L4z/UV5s0KHFAKLeFe3swowyPqf78tTT4RLlhsQqUb56d6ipE7C8FEN2A2JpIeXu98Y+ PEkHZ3JSbDygepYvET4/iQ6F7wL0IMnZHA4A+L0+Ewcpw48zUZGV44OC+qsN/MFf4NXK hdqEyZy++WQVKVQZv9nSycxhsCncvJZnz1JR/Pn7pP3J1tnsKs1R9geYLz/tRS5F9I5a vfMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=AXfvtaoB1FKuNjr92vmY2R2qROx8AiOB95PC4MKhE8k=; b=WmnBOFw6i0J6Y8qaTQM8nWegLw6dkS3m0Gwk3MK2ZgK06aVwxp7yDJ13BJQ1lm2pnt M+PiXyWrzlYYAOo9xErhlleoT5yNylLy+HKKsNoRR4LQeBsjHf7gYtyW4n409UMz+0Kx NCfcMrfKJDSnzUEENBmCNJUiG1oK8J5AUFpzqDoDTFJNr0y6pB3pkYxcoA3jVlEVVb8l RgMSIqJ/+BaOt5t+Slb+w86iE6QJ+fOcHsmUskA+xUQL+f36Bd1ji28xX8fO5BLXJyNr U3sdikLKy6TDXXtqupPF/i5ivE9zo4dtoVa3kYvHU9Mb8FTYjd5Vvl6wLo+FBD0bBrfb qi/g== X-Gm-Message-State: AJaThX4Tmwf5hJKwPVftqqy07OwULX0P1HzqF1dVkk7IgIWSk/fI5JWN 82Vr0rhtar8qpzvDAbFr1pIFVch9 X-Google-Smtp-Source: ABhQp+QMLd9W/n8Xsd/0d3DPw+YZfbL+zTKfCASeQBP06iq/gbhiFDZMzwKq9B08d7BqtjG/h6QoVg== X-Received: by 10.223.160.132 with SMTP id m4mr1322636wrm.45.1510255637197; Thu, 09 Nov 2017 11:27:17 -0800 (PST) Received: from [10.0.0.6] ([185.120.126.135]) by smtp.gmail.com with ESMTPSA id p4sm5075131wrf.36.2017.11.09.11.27.15 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 09 Nov 2017 11:27:16 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Publishing royale to npm From: Harbs In-Reply-To: Date: Thu, 9 Nov 2017 21:27:14 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <23970E98-4762-4C27-A1D6-27E16E8CB5E3@gmail.com> <10F26720-C80A-488F-8752-8D175D4A3423@gmail.com> To: dev@royale.apache.org X-Mailer: Apple Mail (2.2104) archived-at: Thu, 09 Nov 2017 19:27:29 -0000 Did you reserve the name yet? > On Nov 9, 2017, at 9:25 PM, OmPrakash Muppirala = wrote: >=20 > On Thu, Nov 9, 2017 at 10:08 AM, Carlos Rovira = > wrote: >=20 >> Hi Om, >>=20 >> I'm working on the website content and want to know about NPM to = update >> pages with real info. >> could you share your plans about releasing Apache Royale in NPM? >> I suppose you can't still make this due to some final renaming? >>=20 >> Let me know in order to remove this info if you think we'll need more = time >> to get Royale on NPM >>=20 >> Thanks! >>=20 >=20 > I was hoping to release the npm version right after we do the first = release > of royale. Does that work? >=20 > Thanks, > Om >=20 >=20 >>=20 >>=20 >> 2017-10-30 19:57 GMT+01:00 Carlos Rovira = : >>=20 >>> I think apache-royals would be better, since avoids confusing = people. If >> I >>> came to this project for the first time, and try to search in npm, = and >> find >>> "royale", although this was the right and only package, I'll be ask = me if >>> there's the right one. >>>=20 >>> With apache-royale, there's no confusion problems ;) >>>=20 >>> 2017-10-30 19:50 GMT+01:00 OmPrakash Muppirala = : >>>=20 >>>> We always have option of using apache-royale as package name. >>>>=20 >>>> On Mon, Oct 30, 2017 at 11:32 AM, Harbs = wrote: >>>>=20 >>>>> It=E2=80=99s a shame that =E2=80=9Croyale=E2=80=9D seems to = already be taken on npm. >>>>>=20 >>>>> I would vote for two packages: >>>>>=20 >>>>> 1. To install *everything* (i.e. swf, js, node, etc. and future >> targets >>>>> when/if we add them): >>>>> npm install apache-royale -g >>>>>=20 >>>>> 2. To install js-only: >>>>> npm install apache-royale-js -g >>>>>=20 >>>>> If we see a demand for further packages (i.e. compiler only), we = can >> add >>>>> them as additional packages later. >>>>>=20 >>>>> Harbs >>>>>=20 >>>>>> On Oct 30, 2017, at 8:23 PM, OmPrakash Muppirala < >>>> bigosmallm@gmail.com> >>>>> wrote: >>>>>>=20 >>>>>> So, "npm install" downloads a tarball from npmjs.org. The = package >>>>> usually >>>>>> contains the code we want others to use. It also contains a >>>>> "package.json" >>>>>> file which specify all its dependencies. These dependencies (and >>>> their >>>>>> sub-dependencies) are all downloaded from npmjs.org as part of = "npm >>>>>> install". >>>>>>=20 >>>>>> There are options to run custom scripts before and after the npm >>>> install. >>>>>> In the case of FlexJS, we run a script afterwards that simply >>>> downloads >>>>> our >>>>>> non-npmjs.org dependencies (royale sdk, fonts, flash player, air, >>>> etc.) >>>>> and >>>>>> puts them in the correct places. >>>>>>=20 >>>>>> So, our options are: >>>>>>=20 >>>>>> 1. Publish two different packages on npmjs.org: jsonly and = js+swf. >>>> We >>>>>> need to figure out the names of these packages, since they are >> unique >>>>>> identifiers on npmjs's registry. >>>>>>=20 >>>>>> Then the command the users would run would look like: >>>>>> npm install royale-jsonly -g >>>>>> npm install royale-js-and-swf -g >>>>>>=20 >>>>>> 2. Publish only the jsonly package. >>>>>> Then the command the users would run would look like: >>>>>> npm install royale-jsonly -g >>>>>>=20 >>>>>> 3. Possibly, we can figure out a way to optionally download swf >>>> support. >>>>>> This way, by default the jsonly is downoaded and unzipped. Then = we >>>> could >>>>>> (possibly) look at the args or have the user run another command >> that >>>>>> downloads the swf support. >>>>>>=20 >>>>>> Then the command the users would run would (possibly) look like: >>>>>> npm install royale -- -include-swf-support -g >>>>>>=20 >>>>>> (or) >>>>>> npm install royale-jsonly -g >>>>>> and then >>>>>> ./update-royale-include-swf-support >>>>>>=20 >>>>>> In all three cases, we can definitely run a script that alters = xml >>>>> configs, >>>>>> etc. to suit our needs. >>>>>>=20 >>>>>> Hope that helps. >>>>>>=20 >>>>>> Thanks, >>>>>> Om >>>>>>=20 >>>>>> On Mon, Oct 30, 2017 at 9:20 AM, Alex Harui >> >>>>=20 >>>>>> wrote: >>>>>>=20 >>>>>>> Om, >>>>>>>=20 >>>>>>> Can you explain to us what our options are? Essentially, the >> JS-only >>>>>>> package will be a subset of a package that can output both SWF = and >> JS >>>>> and >>>>>>> will probably have slightly different default settings in, for >>>> example, >>>>> a >>>>>>> frameworks/royale-config.xml file. >>>>>>>=20 >>>>>>> It is looking like we can create a zip package for JS-only that >> will >>>>> work >>>>>>> in Moonshine and VSCode, but to fully make it work in Flash = Builder >>>> (and >>>>>>> maybe some other IDEs) you will need to run a script of some = sort >>>> that >>>>>>> fixes up some FB launch configurations that convert Flex = projects >> to >>>>>>> Royale projects. >>>>>>>=20 >>>>>>> The current plan for a "FlexJS" package that has SWF support = (for >>>> users >>>>>>> that want use SWF for testing or as a migration step) will = require >>>> that >>>>>>> users unzip a package and run an Ant script to bring down Adobe >>>>>>> dependencies. I'm thinking we won't use the Flex installer. >>>>>>>=20 >>>>>>> I'm still working through why one of our users isn't getting = code >>>>>>> completion working in FB and the answer there may affect = packaging >> as >>>>> well. >>>>>>>=20 >>>>>>> I don't know NPM well enough to have an opinion on, if we >> distribute >>>> two >>>>>>> packages (flexjs-with-swf-support and js-only), whether NPM = allows >>>> us to >>>>>>> have two different packages or whether it is better to structure >> NPM >>>>>>> releases as js-only package and a swf-support-add-on package. >>>>>>>=20 >>>>>>> I also don't know if the NPM install should run a script that = fixes >>>> up >>>>>>> those launch configs. Maybe it is better to continue to leave = them >>>> as >>>>> "FB >>>>>>> users have to run this additional Ant script" or something like >> that. >>>>> I'm >>>>>>> not sure how important FB still is to our ease-of-migration = story. >>>>>>>=20 >>>>>>> Maybe showing us what folks would have to type on the command = line >>>> might >>>>>>> help us form opinions. >>>>>>>=20 >>>>>>> Thoughts? >>>>>>> -Alex >>>>>>>=20 >>>>>>>=20 >>>>>>> On 10/30/17, 4:36 AM, "carlos.rovira@gmail.com on behalf of = Carlos >>>>> Rovira" >>>>>>> > carlos.rovira@codeoscopic.com> >>>>>>> wrote: >>>>>>>=20 >>>>>>>> Hi Om, >>>>>>>>=20 >>>>>>>> I think that would be great! >>>>>>>>=20 >>>>>>>> If we end having multiple products as Alex suggested, I think = we >>>> should >>>>>>>> have as well multiple NPM installs. >>>>>>>> So for me is ok to sync products we deliver with NPM = installations >>>>> flavors >>>>>>>>=20 >>>>>>>> Thanks >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> 2017-10-30 10:58 GMT+01:00 Yishay Weiss = : >>>>>>>>=20 >>>>>>>>> You=E2=80=99re likely to do most of the maintenance work, so = it=E2=80=99s up to >>>> you=E2=80=A6 >>>>> As >>>>>>>>> far as users go there are some users writing client code in = AIR >> and >>>>>>>>> server >>>>>>>>> code in node (in fact I=E2=80=99m involved in such a project = right now). >>>> So I >>>>>>>>> wouldn=E2=80=99t make sweeping assumptions. >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> ________________________________ >>>>>>>>> From: omuppi1@gmail.com on behalf of >> OmPrakash >>>>>>>>> Muppirala >>>>>>>>> Sent: Monday, October 30, 2017 10:21:37 AM >>>>>>>>> To: dev@royale.apache.org >>>>>>>>> Subject: Re: Publishing royale to npm >>>>>>>>>=20 >>>>>>>>> On Mon, Oct 30, 2017 at 1:19 AM, Harbs >>>> wrote: >>>>>>>>>=20 >>>>>>>>>> Why not publish both versions? >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> It looks like the js only is going to be just a zip file. = That >>>> makes >>>>>>>>> for >>>>>>>>> easy maintenance. >>>>>>>>> The swf version has a bunch of dependencies to be downloaded. >>>>>>>>>=20 >>>>>>>>> Not a big deal, just thinking out loud if we really need to >> publish >>>>> two >>>>>>>>> different packages that might lead to confusion. >>>>>>>>>=20 >>>>>>>>> I'm open to both, though. >>>>>>>>>=20 >>>>>>>>> Thanks, >>>>>>>>> Om >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On Oct 30, 2017, at 10:15 AM, OmPrakash Muppirala < >>>>>>>>> bigosmallm@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>> I was wondering if we should publish the = apache.royale-jsonly >>>> verson >>>>>>>>> via >>>>>>>>>>> npm instead of the full version with swf support. >>>>>>>>>>> After all, users coming in vial npm would most likely not >> expect >>>> swf >>>>>>>>>>> support. >>>>>>>>>>>=20 >>>>>>>>>>> Any thoughts on this proposal? >>>>>>>>>>>=20 >>>>>>>>>>> Thanks, >>>>>>>>>>> Om >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> -- >>>>>>>>=20 >>>>>>>> >>>>>> http%3A%2F%2Fwww.codeo >>>>>>>> scopic.com&data=3D02%7C01%7C%7C5f3b122f189e4e0f119b08d51f8a >>>>>>> 81b0%7Cfa7b1b5a7b >>>>>>>> 34438794aed2c178decee1%7C0%7C0%7C636449602097009881& >>>>>>> sdata=3DwZgQd0X2xX6ed8y0 >>>>>>>> t4O87r66gMlVy%2F8aHqtpwnq8O6w%3D&reserved=3D0> >>>>>>>>=20 >>>>>>>> Carlos Rovira >>>>>>>>=20 >>>>>>>> Director General >>>>>>>>=20 >>>>>>>> M: +34 607 22 60 05 <607%2022%2060%2005> >>>>>>>>=20 >>>>>>>> https://na01.safelinks.protection.outlook.com/?url=3D >>>>>>> http%3A%2F%2Fwww.codeos >>>>>>>> copic.com&data=3D02%7C01%7C%7C5f3b122f189e4e0f119b08d51f8a >>>>>>> 81b0%7Cfa7b1b5a7b3 >>>>>>>> 4438794aed2c178decee1%7C0%7C0%7C636449602097009881& >>>>>>> sdata=3DwZgQd0X2xX6ed8y0t >>>>>>>> 4O87r66gMlVy%2F8aHqtpwnq8O6w%3D&reserved=3D0 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Conocenos Avant2 en 1 minuto! >>>>>>>> >>>>>> https%3A%2F%2Favant2.e >>>>>>>> s%2F%23video&data=3D02%7C01%7C%7C5f3b122f189e4e0f119b08d51f8a >>>>>>> 81b0%7Cfa7b1b5a >>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636449602097009881& >>>>>>> sdata=3DJK22xVqobAGGnZ >>>>>>>> b8laWESXHS3NA5nLdscBYTEHml7Pk%3D&reserved=3D0> >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Este mensaje se dirige exclusivamente a su destinatario y puede >>>>> contener >>>>>>>> informaci=C3=B3n privilegiada o confidencial. Si ha recibido = este >> mensaje >>>>> por >>>>>>>> error, le rogamos que nos lo comunique inmediatamente por esta >> misma >>>>> v=C3=ADa y >>>>>>>> proceda a su destrucci=C3=B3n. >>>>>>>>=20 >>>>>>>> De la vigente Ley Org=C3=A1nica de Protecci=C3=B3n de Datos = (15/1999), le >>>>>>>> comunicamos >>>>>>>> que sus datos forman parte de un fichero cuyo responsable es >>>>> CODEOSCOPIC >>>>>>>> S.A. La finalidad de dicho tratamiento es facilitar la = prestaci=C3=B3n >>>> del >>>>>>>> servicio o informaci=C3=B3n solicitados, teniendo usted derecho = de >>>> acceso, >>>>>>>> rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3=B3n de sus = datos dirigi=C3=A9ndose a >>>>>>>> nuestras >>>>>>>> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la >>>> documentaci=C3=B3n >>>>>>>> necesaria. >>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>>=20 >>> >>>=20 >>> Carlos Rovira >>>=20 >>> Director General >>>=20 >>> M: +34 607 22 60 05 <607%2022%2060%2005> >>>=20 >>> http://www.codeoscopic.com >>>=20 >>>=20 >>> Conocenos Avant2 en 1 minuto! >>>=20 >>>=20 >>> Este mensaje se dirige exclusivamente a su destinatario y puede = contener >>> informaci=C3=B3n privilegiada o confidencial. Si ha recibido este = mensaje por >>> error, le rogamos que nos lo comunique inmediatamente por esta misma = v=C3=ADa >> y >>> proceda a su destrucci=C3=B3n. >>>=20 >>> De la vigente Ley Org=C3=A1nica de Protecci=C3=B3n de Datos = (15/1999), le >>> comunicamos que sus datos forman parte de un fichero cuyo = responsable es >>> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la >>> prestaci=C3=B3n del servicio o informaci=C3=B3n solicitados, = teniendo usted derecho >>> de acceso, rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3=B3n de = sus datos >> dirigi=C3=A9ndose >>> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la >>> documentaci=C3=B3n necesaria. >>>=20 >>>=20 >>=20 >>=20 >> -- >> Carlos Rovira >> http://about.me/carlosrovira >>=20