• Dear Cerberus X User!

    As we prepare to transition the forum ownership from Mike to Phil (TripleHead GmbH), we need your explicit consent to transfer your user data in accordance with our amended Terms and Rules in order to be compliant with data protection laws.

    Important: If you accept the amended Terms and Rules, you agree to the transfer of your user data to the future forum owner!

    Please read the new Terms and Rules below, check the box to agree, and click "Accept" to continue enjoying your Cerberus X Forum experience. The deadline for consent is April 5, 2024.

    Do not accept the amended Terms and Rules if you do not wish your personal data to be transferred to the future forum owner!

    Accepting ensures:

    - Continued access to your account with a short break for the actual transfer.

    - Retention of your data under the same terms.

    Without consent:

    - You don't have further access to your forum user account.

    - Your account and personal data will be deleted after April 5, 2024.

    - Public posts remain, but usernames indicating real identity will be anonymized. If you disagree with a fictitious name you have the option to contact us so we can find a name that is acceptable to you.

    We hope to keep you in our community and see you on the forum soon!

    All the best

    Your Cerberus X Team

Suggestion Opening window with the built file after build

Rob Hewitt

Active member
Tutorial Author
Joined
Aug 30, 2017
Messages
113
Hi,

(still loving Cerberus-X)

Would it be possible to add the ability for Cerberus to open the folder where the apk/html/exe/etc sits once a build is complete? eg open <projectbuildfolder>\android\app\build\outputs\apk in a window afterwards or the html5 folder etc.

Might get rid of a few "where is my apk" type questions coming up and is helpful this end too! :)
 
Or - counterproposal - copy the APK from <projectfolder>\<projectbuildfolder>\android\app\build\outputs\apk to <projectfolder> automatically
 
I think showing the folder is the most, Cerberus itself should do. I think all other tasks especially messing inside folder structure of gradle is something that should be done by an other tool (Tools for config and distribution?)or change the gradle apk folder itself to something short and easy to grasp like <projectbuildfolder>\android\products containing only the products and nothing confusing next to it like it was with ant ;-)
 
You see, there are different opinions. While you'd prefer a up-popping browser window with each compile, I personally would deactivate that option*, because I almost always have a browser window open pointing to the project root. To have quick access to all the assets. But this is due to how I work: I do cosmetic changes on graphics in the very end, just before compiling the final build, and therefore need quick access to image files.

How about the option to run additional scripts after a successful build? (I guess this is possible already but I don't know how :oops:)

*) Implying two things here: 1. it's a feature that could be activated by users who don't need it. And 2. it's activated by default, just for the noobs =)
 
I totally get this point of avoiding anything that gets in your way. :) Probably I would also turn it off most of the time...
The objective of this request though is completely understandable for me: Cerberus has to become more convenient and easier for noobs and wasting time looking for the folder your apk is in after the build is something that should be abolished.
Maybe a third compile option could be helpful but my english is not good enough to find the best fitting word for it. Something like publish, so you have debug and release as it is and publish, where you can set a target folder for the package or an ftp acount for html5 target.
 
Back
Top Bottom