Hi all-

Having such fun.

I read your funny story on the AI about how to get themes.
It is outlined below.

I am reading about compile-js-config.xml config. It is also one of my favorite 
stories.

I am also reading about ant builds too. I like the way everything stems out 
from bin in the structure on the relative paths.

You all are the bomb.com for giving us this cool project!

I am going to figure out how to put Ant on full power. The xml doesnt trick me 
in your files so I can do it (not that it was meant to).

Now I get the themes and make off like a bandit.

please see below...

thanks,
j.

Yes, you still need to compile your Apache Royale project even after you adjust 
the <source-path> to point to the new theme in the js-config-build.xml file.

Here's why:
Why Compilation is Necessary

    Source Code Compilation: The js-config-build.xml file (or any other build 
configuration files, like build.xml) in Apache Royale is responsible for 
compiling the source code into a final executable format, whether that be 
JavaScript, HTML, or assets like CSS. The <source-path> tells Royale where to 
find your source files (including themes), but it doesn’t automatically apply 
them to your project until the build process is run.

    Theme Integration: If you’re using a custom theme or switching themes, the 
source code in the royale directory (typically written in SASS or MXML) needs 
to be compiled into the corresponding JavaScript and CSS files that will be 
included in the final build. This means that even though you updated the 
source-path, the new theme’s resources still need to be compiled (especially if 
they include things like SASS files) and integrated into your application.

The Compilation Process

When you compile an Apache Royale project, these steps generally occur:

    Compile MXML (if any): Apache Royale compiles MXML files into JavaScript 
code.

    Compile SASS to CSS: If your theme uses SASS, those SASS files are compiled 
into CSS.

    Package Assets: All necessary assets like images, stylesheets, and compiled 
JavaScript files are packaged together into a build output (like a 
bin/js-release/ or bin/js-debug/ directory).

    Link to HTML: The final output files (JavaScript, CSS, etc.) are linked 
into the main HTML file, making sure your app uses the theme and compiled 
resources.

Steps You Need to Take After Adjusting <source-path>:

    Update <source-path> in js-config-build.xml: As you've done, update the 
<source-path> to point to the new theme's directory.

    Rebuild the Project:

        After updating the source path, you’ll need to rebuild your project to 
ensure the new theme is properly compiled and included in the output.

        If you're using Apache Ant, you can do this by running the following 
command:

        ant main

        This will trigger the build process, which will:

            Compile the source files.

            Compile the SASS files (if any) into CSS.

            Package everything into the bin/js-debug or bin/js-release 
directories.

        If you have a different build system, you can use the respective 
command to trigger the build (like grunt, maven, etc.).

    Check the Output: Once the build is complete, check the output directory 
(e.g., bin/js-debug/assets or bin/js-release/assets) to ensure that:

        The theme-related files (like CSS or any JS components related to the 
theme) are properly compiled.

        The theme is applied as expected in the browser when you launch the app.

Summary of Steps:

    Update the <source-path> to point to your desired theme.

    Compile the project using your build system (like ant main).

    Verify the output to ensure the new theme is applied.

In Conclusion:

Simply changing the <source-path> isn't enough; you must compile the project 
afterward to ensure that the newly pointed theme is processed, compiled, and 
integrated into your project.



Sent with Proton Mail secure email.

------- Forwarded Message -------
From: Jim McNamara <jmcnamara10...@proton.me>
Date: On Friday, April 4th, 2025 at 6:20 PM
Subject: themes while i am waiting for a style revelation -- please help
To: users@royale.apache.org <users@royale.apache.org>


> Hi,
> 
> do you know where the themes went to?
> 
> I use mxmlc.
> 
> thanks for any help.
> 
> They used to be here.
> 
> https://cdn.apache.org/royale/0.9.12/themes/Jewel.css
> 
> I thought if i could use a theme it would be cool while i was waiting to 
> figure out how to get some styling.
> 
> thanks,
> j.
> 
> 
> 
> Sent with Proton Mail secure email.

Reply via email to