Re: Promo on Facebook, results after 1 month

2018-07-06 Thread Harbs
Cool. I have no idea what this actually means, but it sounds good. ;-) (I personally hate Facebook, so I don’t use it. I do recognize the value of reaching people through it though…) Harbs > On Jul 5, 2018, at 11:58 PM, Carlos Rovira wrote: > > one more I forgot: > > 2.308 reproductions of

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Olaf Krueger
Hi Carlos, you are right, the title "Jewel Refactoring" is misleading, sorry. It should mean the SDK refactoring in favour of the Jewel development. Anyway, I was absent the last few weeks and probably not up-to-date. But it seems to me that you all are still searching for a solution? So, even

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Carlos Rovira
Hi Olaf, 2018-07-06 10:19 GMT+02:00 Olaf Krueger : > > I am interested in two points: > - If we decide to decouple Jewel from Basic and introduce a Core and/or > Foundation package: Is there any volunteer out there who will do this work? > Yes, I said I'll work on that. Harbs said as well that

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Harbs
Here’s what I’d like to do so we could just get out a release: * Postpone any final decision on package and project refactoring until after the release. * Make sure (for the current release only) that the package names match the previous release (even if they could use changing). * Leave the

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Harbs
> but don't you think we can save time and > resources and left this for 0.9.4 with more refactors we already planned? My motivation is to not release undocumented breaking changes — especially since they might be changed further or reverted in the next release. I’d like to keep the breaking

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Carlos Rovira
ok, I can revert this changes in the next few days, so you don't have to deal with this. 2018-07-06 11:39 GMT+02:00 Harbs : > > but don't you think we can save time and > > resources and left this for 0.9.4 with more refactors we already planned? > > My motivation is to not release undocumented

Re: Coming back to discussion over separating libs (Was Re: No Touch support?)

2018-07-06 Thread Carlos Rovira
Hi Harbs 2018-07-06 10:27 GMT+02:00 Harbs : > Here’s what I’d like to do so we could just get out a release: > > * Postpone any final decision on package and project refactoring until > after the release. > Ok for me, although I think this was one of the things we all agree. But I think you

Re: No Touch support?

2018-07-06 Thread Alex Harui
Hi Carlos, The "CSS" that handles which beads to load is not conforming CSS and is handled by custom code, similar to Apache Flex. So we could extend media query similar to how Flex Mobile did it, or people will figure out queries that pretty much tell the same. Some combination of screen