@Stealth22  @LtFlash hey! Are you working on something? 

At this moment I'm on a serious backlog in real life, I'll try to look at the code later this week.

At this moment I'm on a serious backlog in real life, I'll try to look at the code later this week.

Sort of a similar situation. Not working on anything with this at the moment, not since my last commit.

I need to finish the upcoming update of Code 3 Callouts.

@Stealth22 @LtFlash Ok, guys I have a working version of RAGENativeUI.

 

I leave you the source code before I update it in Github. The only that isn't working(I think) is the custom banner because I don't find the source code of DrawTexture(). 

Let me know if you think my code is right to upload it to Github.

 

RAGENativeUI & example.rar

Edited September 9, 201510 yr by alexguirre

Just tried the example on RPH 0.22 and it looks like this:

Amazing work guys!!

Thanks. Always good to know that it works with other versions, I compiled and tested it with RPH 0.24. And you should wait until an official release before using it in any plugin

Absolutely, was just testing it out for you :)

Something that caught my attention immediately was that the mouse was visible, I don't know if you can disable that already but it would be nice to be able to in the release version 

Great work, I really appreciate it!

Yes, you can disable the mouse, just use:

menuName.MouseControlsEnabled = false;

 

Edited September 9, 201510 yr by alexguirre

Nice work!

Are all these changes committed to the GitHub repo?

And FYI, you can commit your changes without any problems. If something doesn't work, we can reverse any changesets that are committed to the server.

Nice work!

Are all these changes committed to the GitHub repo?

And FYI, you can commit your changes without any problems. If something doesn't work, we can reverse any changesets that are committed to the server.

I will commit them later today, when I get back to my computer

Nice work!

Are all these changes committed to the GitHub repo?

And FYI, you can commit your changes without any problems. If something doesn't work, we can reverse any changesets that are committed to the server.

I committed the changes to the LSPDFR API repo. Also I made a new repo to have there the releases, report issues there, have a wiki explaining how to use it and not flood the API repo: https://github.com/alexguirre/RAGENativeUI .

I committed the changes to the LSPDFR API repo. Also I made a new repo to have there the releases, report issues there, have a wiki explaining how to use it and not flood the API repo: https://github.com/alexguirre/RAGENativeUI .

If thats the case, we should pick one place to keep it, and have it only live in that repo. We certainly do not want multiple copies of the code living in different places.

Don't delete anything yet, though. I think we should have a collective discussion/decision about it.

@LMS, what do you think? My thoughts on the matter, personally, are maybe it should be in it's own dedicated repository. Simply because of potential issues that would be reported, and so on. Alex can take ownership of it, since he took the lead on getting the original author's permission and such. Whoever contributed to the code (myself, LtFlash, etc) can be added as collaborators on that Git repo, and be credited in the releases.

I don't mind having it in the LSPDFR repo, but it's starting to spin into it's own project, rather than being under the LSPDFR umbrella. It doesn't reference any LSPDFR classes, and I don't see why it ever would. We can keep a RAGENativeUI example in the LSPDFR repo, but my main concern (if you can even call it a concern) with keeping the entire project in the LSPDFR repo is that the repo may get flooded with issues/documentation for RAGENativeUI.

Thoughts?

And just a side note @alexguirre, is the native UI library working now, or are there still issues with it? What needs to be fixed, if anything?

EDIT: If there is anything outstanding, start creating issues for them in your repo. Otherwise we'll start forgetting what needs to be done.

Edited September 9, 201510 yr by Stealth22

 

And just a side note @alexguirre, is the native UI library working now, or are there still issues with it? What needs to be fixed, if anything?

EDIT: If there is anything outstanding, start creating issues for them in your repo. Otherwise we'll start forgetting what needs to be done.

Yes, it is working. The only thing that isn't working(that I have knowledge of) is the custom banner because I can't find the source code to draw textures from a path. It is in the Sprite class.

Edited September 9, 201510 yr by alexguirre

Yes, it is working. The only thing that isn't working(that I have knowledge of) is the custom banner because I can't find the source code to draw textures from a path. It is in the Sprite class.

Just to be clear, by "custom banner", you mean being able to replace that "RageNative UI" header at the top of the menu?

Just to be clear, by "custom banner", you mean being able to replace that "RageNative UI" header at the top of the menu?

I mean be able to replace the title with an external image(i.e. a png). For now you can replace it with a texture from the game files or with other text.

Edited September 9, 201510 yr by alexguirre

Oh ok. That's probably not a huge issue for now, haha. Let's make sure its 100% working first. 

Can you give me contributor access on the second repo? (And where are we making changes for now, until we decide where to keep it?)

Oh ok. That's probably not a huge issue for now, haha. Let's make sure its 100% working first. 

Can you give me contributor access on the second repo? (And where are we making changes for now, until we decide where to keep it?)

Ok, I added you as contributor. I think we should make the changes in the repository I made, it's quite big project and for people who doesn't use the API will be better to have it separeted.

Also we should create I topic announcing this so developers who doesn't read the API forum will know that this exists(maybe in the RAGE forums and in the Script showroom forum).

Ok, I added you as contributor. I think we should make the changes in the repository I made, it's quite big project and for people who doesn't use the API will be better to have it separeted.

 

I guess this is how this should be done. Its project for rage hook plugin not for lspdfr api, it can be used completly outside LSPDFR if someone wishes to do so, so to keep things in order, this should be separated, in my opinion.

Looking pretty incredible guys, great work!

@alexguirre, magnificent work! This will be used by many modders.

I think you have the right to decide where the code should have it's place.

I created a topic announcing it: http://www.lcpdfr.com/forums/topic/54970-dev-tool-rel-ragenativeui/ 

You guys can start using it with your mods :)