Rework layout using relative elements, image buttons and scalable images about tecla-framework HOT 21 CLOSED

I guess i'll try to dig deep into this issue.I believe i can work it out somehow.

from tecla-framework.

@lakhan091 I am working on it now. I can push an early version of the layout so you can take a look. You could work on fixing up the associated class, which would be broken

from tecla-framework.

@lakhan091 see my work here: https://github.com/jorgesilva/tecla-framework/tree/issue-73

from tecla-framework.

@jorgeSilva I have updated the repo in my laptop. I will work on the broken the class.

from tecla-framework.

@jorgeSilva The only error it shows is that it cannot find the imageviews which i guess is not created yet.So i wanted to clear one thing is that do you want me to make those images and fix the imageview problems or is there any functionality needs to be implemented and if yes then which one?
The error is "Description Resource Path Location Type imageView_border_up cannot be resolved or is not a field TeclaHUDController.java /java/src/ca/idrc/tecla/hud line 43 Java Problem" and another 39 erros just like this.

from tecla-framework.

@lakhan091 I don't think you have the right branch. Make sure you are working off of the issue-73 branch

from tecla-framework.

I will be moving towards creating custom ImageButton classes and overriding their onDraw() method in order to paint the HUD 'by hand'. This is because using pre-made resources is introducing too many problems that may be easily solved by simply drawing the HUD ourselves.

from tecla-framework.

@jorgeSilva Are the problems related to just scaling of images?
I went through your code and noticed that all the pngs in different drawable-mdpi,xdpi,ldpi,mdpi are of same size. That might be creating blurry/oversharped images on a smaller device. I noticed that on my phone too.

from tecla-framework.

I went through the developers guide and got to know the pixel ratios between different sized pngs, will resize the pngs if necessary.

from tecla-framework.

@sagarchandarana123 scaling is a problem yes, but not just because of the drawables with same resolution, but becuase we cannot really scale angular lines nicely. It'll be best to draw them.

from tecla-framework.

Not necessary to resize the pngs since, as I already mentioned, we are abandoning that approach. Would you like to try helping me create the custom ImageButtons?

from tecla-framework.

@jorgeSilva i checked it again.And i went to the link you provided me.I just want to know what shall i do about it?And i also observed that declaration in Androidmanifest was not matching the original file.Changing that criteria might also help.

from tecla-framework.

I am lost, not sure what you are talking about @lakhan091

from tecla-framework.

@jorgeSilva I am talking about this issue-73. I observed there was no error except of those imageview could not be resolved in the file ca.idrc.tecla.hud.TeclaHUDController.java .

from tecla-framework.

@lakhan091 we are beyond this now... are you interested in drawing the ImageButtons?

from tecla-framework.

@jorgeSilva Yeah sure. Just tell me what shall i do. Which tools to use and needed ImageButtons.

from tecla-framework.

Do I have to use Draw 9-Patch tool?

from tecla-framework.

@jorgeSilva @lakhan091 I think what is meant here by drawing custom ImageButtons, that no pre-drawn resource png will be used. Instead, we manually write the code which draws the buttons on the screen at run time, so that we can overcome all the issues we are facing.

from tecla-framework.

@lakhan091, @sagarchandarana123 is partially correct. But I would prefer not to draw at runtime, though alterations (e.g., changing the alpha value) are acceptable. Instead, we should extend the ImageButton class for each section of the HUD an draw the proper traces by overriding the onDraw() method. We may need to override other related methods too.

from tecla-framework.

@jorgeSilva Thank you for the detailed description. I get the whole scenario now. And you are right overriding onDraw() method would be the best as we can pass our canvas object in it so that the problem can be solved.And also I think we can use setImageAlpha(int alpha) method to change the alpha value and write a method in it which will decide when to change the alpha value of the ImageButton.

from tecla-framework.

@lakhan091 excellent. Please feel free to go ahead and attempt an implementation that is able to recreate the HUD here:

You would still have to rework the XML layout so it is not as convoluted. For a quick start see my experimental code here: https://github.com/jorgesilva/tecla-framework/tree/issue-73

from tecla-framework.