I think it should be
theme_arg=-theme=<path to theme>
(not tested by be)
2018-05-17 14:02 GMT+02:00 Harbs <harbs.li...@gmail.com>:
> What compiler option is used to specify a theme? (Assuming the command
> line is being used — not Maven, ant or what-have-you.)
>
> > On May 17, 2018, at 2:57 PM, Carlos Rovira <carlosrov...@apache.org>
> wrote:
> >
> > Hi,
> >
> > (renaming to this thread since is not related directly to the old one and
> > is more a "doc" email)
> >
> > To setup a theme in jewel, the best is look at JewelExample's pom.xml. I
> > think Alex already make the ANT's files needed to this.
> > IDE should have some way to achieve this like in Flex. I think this was
> > made using -theme like in flex. Please look in the list for "-theme"
> since
> > I can recall this is how the compiler consume the styles.
> >
> > About how I set up in MAVEN:
> >
> > We have a "master" Theme:
> >
> > <dependency>
> > <groupId>org.apache.royale.framework</groupId>
> > <artifactId>JewelTheme</artifactId>
> > <version>0.9.4-SNAPSHOT</version>
> > <type>swc</type>
> > <scope>theme</scope>
> > <classifier>js</classifier>
> > </dependency>
> >
> > This theme is the one that can create all the combinations of other
> themes,
> > changing variables in *_themes.sass*
> >
> > //Theme variables (Flat/No Flat - Dark/Light -
> Primary/Secondary/Emphasized
> > Color
> > $flat: false
> > $dark: false
> > $primary-color: $blue
> > $secondary-color: $topaz
> > $emphasized-color: $emerald
> >
> > So if you set flat to "true", you'll get the generated css flat, and if
> you
> > change $blue to $amethyst, should get sass calculate the right colors to
> > get the final CSS, finaly $dark will make theme dark or light.
> >
> > To avoid people need to use SASS, I decided to create all possible
> compiled
> > versions. Right now I just committed the half. I still have to create the
> > other half themes.
> >
> > So instead of use the above and generate the final css with SASS, people
> > not using SASS, can change for :
> >
> > <dependency>
> > <groupId>org.apache.royale.framework</groupId>
> > <artifactId>Jewel-Light-NoFlat-Primary-Blue-Theme</artifactId>
> > <version>0.9.4-SNAPSHOT</version>
> > <type>swc</type>
> > <scope>theme</scope>
> > <classifier>js</classifier>
> > </dependency>
> > <dependency>
> > <groupId>org.apache.royale.framework</groupId>
> > <artifactId>Jewel-Light-NoFlat-Secondary-Topaz-Theme</artifactId>
> > <version>0.9.4-SNAPSHOT</version>
> > <type>swc</type>
> > <scope>theme</scope>
> > <classifier>js</classifier>
> > </dependency>
> > <dependency>
> > <groupId>org.apache.royale.framework</groupId>
> > <artifactId>Jewel-Light-NoFlat-Emphasized-Emerald-Theme</artifactId>
> > <version>0.9.4-SNAPSHOT</version>
> > <type>swc</type>
> > <scope>theme</scope>
> > </dependency>
> >
> > and that will make you use the three pieces needed. Normaly people will
> use
> > in this three ones the same configuration of dark-flat, and you can then
> > use the color combination you want between primary, secondary and
> > emphasized.
> >
> > Note that all this themes use JewelTheme code as a master theme to
> generate
> > the corresponding CSS
> >
> > in the final app all this style rules will be merged into one thanks to
> the
> > royale compiler processing.
> >
> > One more thing, we have as in MDL the use of an html template:
> >
> > <htmlTemplate>
> > ${basedir}/target/javascript/bin/js-debug/jewel-example-
> index-template.html
> > </htmlTemplate>
> >
> > but only to get the FONT:
> >
> > <link href="https://fonts.googleapis.com/css?family=Lato:400,700"; rel=
> > "stylesheet">
> >
> > I expect at some time we can remove that need since we implement one of
> the
> > options Alex expose for the incorporation of different fonts, hopefully
> > soon.
> >
> > There's no more needs, hope this clear better how to use Jewel.
> >
> > Thanks
> >
> > Carlos
> >
> >
> > 2018-05-17 13:33 GMT+02:00 Harbs <harbs.li...@gmail.com>:
> >
> >> I see the following in the pom:
> >> <dependency>
> >> <groupId>org.apache.royale.framework</groupId>
> >> <artifactId>Jewel-Light-NoFlat-Primary-Blue-Theme</artifactId>
> >> <version>0.9.4-SNAPSHOT</version>
> >> <type>swc</type>
> >> <scope>theme</scope>
> >> <classifier>js</classifier>
> >> </dependency>
> >>
> >> It looks like there’s no default theme for Jewel. Should that be fixed?
> >>
> >> How are themes specified to the compiler?
> >>
> >>> On May 17, 2018, at 2:26 PM, Harbs <harbs.li...@gmail.com> wrote:
> >>>
> >>> Oh. I guess that’s why the styling did not work.
> >>>
> >>> Carlos, what compiler options are needed for Jewel?
> >>>
> >>> Harbs
> >>>
> >>>> On May 17, 2018, at 2:23 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>>
> >>>> This is another issue. You cannot build those examples using IDE. I
> >> think
> >>>> we should raise on GitHub. I also cannot build those examples in
> >> Moonshine.
> >>>> Something needs to be configured. Probably some additional args for
> >>>> compiler related to theme etc.
> >>>>
> >>>> 2018-05-17 13:18 GMT+02:00 Harbs <harbs.li...@gmail.com>:
> >>>>
> >>>>> VSCode using asconfigc
> >>>>>
> >>>>>> On May 17, 2018, at 12:57 PM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> Harbs,
> >>>>>>
> >>>>>> How did you build the examples? Using VSCode or script ant/maven ?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Piotr
> >>>>>>
> >>>>>> 2018-05-17 11:55 GMT+02:00 Harbs <harbs.li...@gmail.com <mailto:
> >>>>> harbs.li...@gmail.com>>:
> >>>>>>
> >>>>>>> FWIW, it looks to me like the only thing that will not work in the
> >> blog
> >>>>>>> post is <j:View> needs to be <js:View> and <j:TextPrompt> needs to
> be
> >>>>>>> <js:TextPromptBead>
> >>>>>>>
> >>>>>>> Although when I compile styles are definitely missing.
> >>>>>>>
> >>>>>>> Yeah. Jewel is definitely missing important pieces… :-(
> >>>>>>>
> >>>>>>> Harbs
> >>>>>>>
> >>>>>>>> On May 17, 2018, at 12:40 PM, Harbs <harbs.li...@gmail.com>
> wrote:
> >>>>>>>>
> >>>>>>>> You are right. I missed this.
> >>>>>>>>
> >>>>>>>> What is the minimum change necessary to get this to work?
> >>>>>>>>
> >>>>>>>>> On May 17, 2018, at 12:24 PM, Carlos Rovira <
> >> carlosrov...@apache.org
> >>>>>>> <mailto:carlosrov...@apache.org <mailto:carlosrov...@apache.org>>>
> >>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I think you missed one important point I
> >>>>>>>>> posted in other email: All blog post samples posted that are
> using
> >> the
> >>>>>>>>> actual names, packages and namespaces. If you release 0.9.3
> without
> >>>>> all
> >>>>>>>>> that, we can destroy out credibility since in all posts we have:
> >>>>>>>>>
> >>>>>>>>> "The example uses the new Jewel UI set that supports themes.
> Jewel
> >>>>> will
> >>>>>>> be
> >>>>>>>>> available in the forthcoming 0.9.3 release of Royale. In the
> >> meanwhile
> >>>>>>> you
> >>>>>>>>> can find it in the develop branch."
> >>>>>>>>>
> >>>>>>>>> and the code is tailored with the actual api.
> >>>>>>>>>
> >>>>>>>>> For that reason, I think is important to hold 0.9.3 until it can
> >> ship
> >>>>>>> with
> >>>>>>>>> all that we are promising in website and social networks for the
> >>>>> latest
> >>>>>>> 2
> >>>>>>>>> months. I think this is crucial.
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Piotr Zarzycki
> >>>>>>
> >>>>>> Patreon: *https://www.patreon.com/piotrzarzycki <
> >>>>> https://www.patreon.com/piotrzarzycki>
> >>>>>> <https://www.patreon.com/piotrzarzycki <https://www.patreon.com/
> >>>>> piotrzarzycki>>*
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Piotr Zarzycki
> >>>>
> >>>> Patreon: *https://www.patreon.com/piotrzarzycki
> >>>> <https://www.patreon.com/piotrzarzycki>*
> >>>
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
