Naming conventions for Android

I am going to collect my naming conventions for Android here. This may sound like reinventing the wheel, but a cursory glance around will show that there is not much agreement on what should be done. It will be short to start with and hopefully it will improve as I go along. I would of course be much happier to use the official version, but I can't find this. If it shows up I will switch and leave a link here.

Widgets like buttons: Prefix them with a short version of their class - example btn for button. Follow that by camel case for what they are. So btnCancel would be your cancel button. This has the advantage of allowing you to easily filter out all non buttons when you are wiring your xml layout files up to your java.
btn - button
txt - editable text field (EditText)
lbl - non editable text fields (TextView)
tgl - toggle button


String identifiers in strings.xml: use all lower case, separated by underscores. For button labels use btn_ as a prefix.  For example btn_pause is the label for a pause button.

IDs from layout xml files: Same as string identifiers from strings.xml. Example a page title on the user list page would be title_user_list.


Comments

Post a Comment

Popular posts from this blog

Building a choropleth map for Irish agricultural data

I wanted to create a choropleth map  using Irish data. The Irish Government has made a large quantity of data available at data.gov.ie. The set I chose was for Bovine TB across Ireland over a number of years. You can get geojson for a variety of countries and Ireland's county boundaries are available. All I had to do was get the data labels to match. In the data some counties are split into 2 parts. I merged and summed these data points to get the choropleth to work with normal county boundaries. You can see the results here . A link to the github is included at the top of the notebook.
Read more

Early Stopping with Keras

Steps to train a model There are a number of things you have to do when working on a Machine Learning problem. Import your data and transform it as appropriate Define  your model using something like Keras - this includes your chosen hyperparameter values Run the training phase Evaluate the model If at the end of this process the evaluation shows that your model is not sufficient for your needs you will need to make some changes and rerun the training.  Ideally you should have a way to spot that training is not going as you want and stop it. This is one of the uses of early stopping. The other is if your model has reached a sufficient quality standard for you to use and further improvements have slowed, stopped altogether or an unnecessary.  Early Stopping Keras provides a way of doing this using the EarlyStopping callback . There are a range of callbacks in Keras and you can define your own. Details are here . The EarlyStopping callback works by choosing a metric
Read more

AutoCompleteTextView backed with data from SQLite in Android

Image
This is a handy piece of code. As your database gets bigger you can allow the user to pick the correct value by typing. If the db gets very big, you can always increase the threshold, so that the query does not run until there will be a suitably sized resultset returned. Running it at a threshold of 1 is fine for very small resultsets.  Here is the code you need to back your AutoCompleteTextView with a cursor adapter. @Override protected void onResume() { super.onResume(); text = (AutoCompleteTextView) findViewById(R.id.autoCompleteTextView1); final AdapterHelper h = new AdapterHelper(this); Cursor c = h.getAllResults(); startManagingCursor(c); String[] from = new String[] { "val" }; int[] to = new int[] { android.R.id.text1 }; CursorAdapter adapter = new MyCursorAdapter(this, android.R.layout.simple_dropdown_item_1line, c, from, to); adapter.setFilterQueryProvider(new FilterQueryProvider() { public Cursor runQuery(Cha
Read more