User:Hkmaly

Explain xkcd: It's 'cause you're dumb.
(Difference between revisions)
Jump to: navigation, search
(jBjZHawpoo)
 
(The spambots are getting infuriatingly bold now. Could we block anonymous edits and tell them to make accounts for a week or so?)
Line 1: Line 1:
 +
{{spam}}
 
: Hi, it is a good idea…I am working on a sialimr one…did you plan to make it opensource?Thanks@Tobia,Thanks! I am indeed planning to make it open source. Absolutely. The only reason I don't have the source up right now is that as it is, missing a few key features, it isn't really useful as a library. Once I get some event handling in place, I'll make all the code available and hopefully write some basic instructions. Good luck on your sialimr project unless you just want to wait for this one now.: wow, that looks great and very promising. I would definitly prefer this “aml” to android layout xml. So the yes i definitly would want to get my hands on this!!@Murat,Thanks! I hope to have a useful tool available for you all shortly. I'm glad you like how it's turning out so far.: I just wonder how does it behave with multiple screen sizes and also how would I theme it, make it look presentable.@Jude,So far, there is nothing in the code that requires a specific screen size, while there is a density detection feature that should help standardize the behavior across multiple sizes. Android has a nice unit called a  dip  or simply  dp , meaning Density Independent Pixel (as you may already know). Unfortunately, directly building views with code only allows you to specify absolute pixels; you can only use a  dp  unit in the /res/layout XML files (grr!). However, the API provides a way to detect screen density and simply calculate a scale factor. This is done automatically by the AML main build method, and then it is used automatically whenever pixel values are given. So, if I specify a padding="6" attribute on a table cell, it will automatically multiply it by a scale factor of 1.5 on my Motorola Droid (854 480), and use a literal pixel value of 9. This feature will ultimately be optional, but it does work great for now.The same AML code works in both portrait and landscape mode as well, though it is my goal to allow a unique view definitely on the same Activity screen for portrait and landscape mode, so you can rearrange things based on orientation if it makes sense to do so. That feature isn't there yet though.As for theming: although you can specify foreground and background colors on individual objects, I realize this falls short of what will be necessary. I have read a little bit about , but that's it so far. I'm thinking maybe something analogous to CSS, and/or something to access styles built into the app. That's lower on the priority list than getting the basic functionality to work, but still important.Good thoughts!
 
: Hi, it is a good idea…I am working on a sialimr one…did you plan to make it opensource?Thanks@Tobia,Thanks! I am indeed planning to make it open source. Absolutely. The only reason I don't have the source up right now is that as it is, missing a few key features, it isn't really useful as a library. Once I get some event handling in place, I'll make all the code available and hopefully write some basic instructions. Good luck on your sialimr project unless you just want to wait for this one now.: wow, that looks great and very promising. I would definitly prefer this “aml” to android layout xml. So the yes i definitly would want to get my hands on this!!@Murat,Thanks! I hope to have a useful tool available for you all shortly. I'm glad you like how it's turning out so far.: I just wonder how does it behave with multiple screen sizes and also how would I theme it, make it look presentable.@Jude,So far, there is nothing in the code that requires a specific screen size, while there is a density detection feature that should help standardize the behavior across multiple sizes. Android has a nice unit called a  dip  or simply  dp , meaning Density Independent Pixel (as you may already know). Unfortunately, directly building views with code only allows you to specify absolute pixels; you can only use a  dp  unit in the /res/layout XML files (grr!). However, the API provides a way to detect screen density and simply calculate a scale factor. This is done automatically by the AML main build method, and then it is used automatically whenever pixel values are given. So, if I specify a padding="6" attribute on a table cell, it will automatically multiply it by a scale factor of 1.5 on my Motorola Droid (854 480), and use a literal pixel value of 9. This feature will ultimately be optional, but it does work great for now.The same AML code works in both portrait and landscape mode as well, though it is my goal to allow a unique view definitely on the same Activity screen for portrait and landscape mode, so you can rearrange things based on orientation if it makes sense to do so. That feature isn't there yet though.As for theming: although you can specify foreground and background colors on individual objects, I realize this falls short of what will be necessary. I have read a little bit about , but that's it so far. I'm thinking maybe something analogous to CSS, and/or something to access styles built into the app. That's lower on the priority list than getting the basic functionality to work, but still important.Good thoughts!

Revision as of 04:56, 20 October 2012

Ambox deletion.png This page has been flagged by an editor as spam. Admins, please review and delete the page.
Note: Make sure to check the revision history in case legitimate previous versions exist.
Hi, it is a good idea…I am working on a sialimr one…did you plan to make it opensource?Thanks@Tobia,Thanks! I am indeed planning to make it open source. Absolutely. The only reason I don't have the source up right now is that as it is, missing a few key features, it isn't really useful as a library. Once I get some event handling in place, I'll make all the code available and hopefully write some basic instructions. Good luck on your sialimr project unless you just want to wait for this one now.: wow, that looks great and very promising. I would definitly prefer this “aml” to android layout xml. So the yes i definitly would want to get my hands on this!!@Murat,Thanks! I hope to have a useful tool available for you all shortly. I'm glad you like how it's turning out so far.: I just wonder how does it behave with multiple screen sizes and also how would I theme it, make it look presentable.@Jude,So far, there is nothing in the code that requires a specific screen size, while there is a density detection feature that should help standardize the behavior across multiple sizes. Android has a nice unit called a dip or simply dp , meaning Density Independent Pixel (as you may already know). Unfortunately, directly building views with code only allows you to specify absolute pixels; you can only use a dp unit in the /res/layout XML files (grr!). However, the API provides a way to detect screen density and simply calculate a scale factor. This is done automatically by the AML main build method, and then it is used automatically whenever pixel values are given. So, if I specify a padding="6" attribute on a table cell, it will automatically multiply it by a scale factor of 1.5 on my Motorola Droid (854 480), and use a literal pixel value of 9. This feature will ultimately be optional, but it does work great for now.The same AML code works in both portrait and landscape mode as well, though it is my goal to allow a unique view definitely on the same Activity screen for portrait and landscape mode, so you can rearrange things based on orientation if it makes sense to do so. That feature isn't there yet though.As for theming: although you can specify foreground and background colors on individual objects, I realize this falls short of what will be necessary. I have read a little bit about , but that's it so far. I'm thinking maybe something analogous to CSS, and/or something to access styles built into the app. That's lower on the priority list than getting the basic functionality to work, but still important.Good thoughts!
Personal tools
Namespaces

Variants
Actions
Navigation
Tools

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?