Re: "Vivid" to become "Jewel"

Carlos, Thanks for clarification :) That's sounds good! :) 2018-03-06 12:31 GMT+01:00 Carlos Rovira : > Hi Piotr, > > for compiler I expect to solve (if I can, since is not my conformt zone and > I need to see what can I do) bugs in CSS. > Don't see anything that not

Re: "Vivid" to become "Jewel"

Hi Piotr, for compiler I expect to solve (if I can, since is not my conformt zone and I need to see what can I do) bugs in CSS. Don't see anything that not should go directly to develop since should be commits solving concrete issues (like #25, and #26) In the other hand, my work will be in 3

Re: "Vivid" to become "Jewel"

Hi, just let you know that I made this refactor and remove old branches. I merged compiler changes in develop, since I think are not specific of Jewel. So, for the moment I'll use only one branch in asjs until I need more branches. If for example, I fix a compiler problem in CSS I'll commit to

Re: "Vivid" to become "Jewel"

Hi Piotr, thanks! :), don't worry I can wait for you to come, I can still be preparing the "scenario" so when you come is all more easy to collaborate :). Regarding names and namespace, I'm a great advocate that these things matters, I know people can use different prefixes if they want, but in

Re: "Vivid" to become "Jewel"

Hi Carlos, First of all - Great job! :) You are again creating something awesome and I can't wait to join you with help. Still many things holds me off. :) Some thought about the namespace, I would not bother about that. User can have different namespace if they want. In the other words I can

Re: "Vivid" to become "Jewel"

Hi Alex, don't want to disturb the new release, and as I'm working on a branch, I think all this work will no affect that. My plan is to make some real work first, and maybe this weekend make the renaming, but all in the branch. Maybe, if I get a component or two that looks final in this days, we

Re: "Vivid" to become "Jewel"

Sounds ok to me. Are you going to try to do that for 0.9.2 or the next release? -Alex On 3/2/18, 11:25 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi, > >now that we solved part of the technical problems to