Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Thank you for this. There’s two groups of files that were changed: Interfaces and and Classes. In general, I would be more inclined to move interfaces than classes, but there are some things to consider: 1. There are still 17 interfaces in Basic. If the 5 that were moved belong in Core, what

Re: How to setup Jewel Theme in a project(Was Re: 0.9.3 Release)

Hi Pior, I think if you could take care of ANT files as well it would be great. In this way, when I upload the new 70 theme projects, I'll be doing taking into account your work to make all work directly thanks 2018-05-21 15:57 GMT+02:00 Piotr Zarzycki : > I think

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Hi Harbs, 2018-05-21 12:52 GMT+02:00 Harbs : > Thank you for this. > > There’s two groups of files that were changed: Interfaces and and Classes. > > In general, I would be more inclined to move interfaces than classes, but > there are some things to consider: > > 1. There

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Ok, that's good point. But, if users need to refer it in code they will need to import the full package rute plus TextPromptBead right? This could be very confusing right? It's only a suggestion (I think is good)? or do you like more TextPromptBead than TextPrompt? Thanks Carlos 2018-05-21

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

I think we are in agreement. My most recent posts were intended to show that #2 is not easily solvable, if at all, and thus we should not invest time or energy there. My only suggestions regarding #1 is that we do not invent a second naming system, and that whatever we do is PAYG in the sense

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

No. Just referencing the Jewel TextPrompt would bring in the class. As long as the Basic swc is available, it’ll just work. Assuming any piece of Jewel uses Basic, I think Basic should be declared as a dependency by Jewel in Maven. With other build types, the swc should always be available.

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Commenting on this one item (before I respond to the rest). If all you want to do is add , you can do this: Express does this a lot. Harbs > On May 21, 2018, at 5:47 PM, Carlos Rovira wrote: > > In the other hand as I notice before, we can use this to refactor

Re: How to setup Jewel Theme in a project(Was Re: 0.9.3 Release)

Hi Piotr, that's right, right now several people reported problems to try this. Hope as we release they'll have less problems. I want to figure if we can update blog posts with more info, or make a new post and then reference existing post to that one...I'll take a look as I have some time

Re: How to setup Jewel Theme in a project(Was Re: 0.9.3 Release)

I think new one will be more visible, but it doesn't matter to me. I will add Moonshine files to those projects. If any user open project with Moonshine it will just work. I will try to update also VSCode files, unless someone beat me with that. Piotr 2018-05-21 15:51 GMT+02:00 Carlos Rovira

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

I’m getting confused. Let me try and summarize the issues as I understand them: There are two different types of issues: Compile time issues, and runtime issues. Compile time issues are: 1. Compiled css files do not differentiate between different packages. (i.e. ImageButton type selectors

Re: How to setup Jewel Theme in a project(Was Re: 0.9.3 Release)

Alex, I can confirm that this is working. When I added following compiler arguments -theme=${royalelib}/themes/Jewel-Light-NoFlat-Primary-Blue-Theme/src/main/resources/defaults.css My suggestion is that: 1) We should write blog post which describes how to setup all examples in Moonshine and

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

I understand this isn't the latest post on this thread, but it is the easiest one for me to reply to: First, the hopefully easy things we can agree on: -I have no objection to dropping "Bead" off of bead class names -I have no objection to moving all views into a view subfolder as long as

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Hi Harbs 2018-05-21 18:35 GMT+02:00 Harbs : > No. Just referencing the Jewel TextPrompt would bring in the class. As > long as the Basic swc is available, it’ll just work. Assuming any piece of > Jewel uses Basic, I think Basic should be declared as a dependency by Jewel >

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

Hi Alex what do you think about separating the part in Basic that is inherently the same as in Jewel (Button, CheckBox, TextInput, List, ...) along with CSS that wire the beads for Basic UI set, and left the fundamental building blocks as something that is not Core but can be reused by Basic and

[Discussion] Package change names (was Re: 0.9.3 Release)

Hi, as we talked I take the time to make a list of package name changes. Finally 20 classes were changed from package. Here's the list from 16c0dcd643974fe708fd67a3774ea6e35e879811 (in red the changes to better following)

Re: [royale-asjs] 01/02: Allow acceptance of licenses by setting ACCEPT_ALL_ROYALE_LICENSES=true environment variable.

Hi Om, I'd have to check with Adobe people on bypassing acceptance of Adobe agreements. Before I bother them, why is this bypass required? We did already get approval to store that you have accepted once so future installs don't require license acceptance. Is there a way to do something

Re: How to setup Jewel Theme in a project(Was Re: 0.9.3 Release)

I'm too swamped to read this whole thread, but one note: Ant doesn't need to build CSS-only themes. The examples that use them only need to use -theme= HTH, -Alex On 5/20/18, 12:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"