sabaoth87 / pha Goto Github PK

Is it worth looking into at this point, separating the SQL handlers into Asynchronous tasks to better manage resources?
Or wait until it is required...?

Design and add an 'Add Tool' UI to the Workbench.
Small/simple I believe is all that is required

• Popup style
• ETs / Spinners

Look into it.

onNothingSelected is an Auto-generated in the
PHA_Converter
PHA_Db
that may have to be looked at.
Possibly just remove the TODO

Need to finish populating the appropriate fields in the Issue

• owner / assignee should be account/user names
• ticket should be a random, unique number
• milestone / project should be linked to trackable objects
• progress should be a value that is based on:
  • owner input
  • open tasks / total tasks, if applied

Use the methods learn from the dB adventure in the Workbench and incorporate them into the reminders, dB, etc., of the existing PHA:LANX platform.

PHA_PuzzleView :: 67

I was required to add this to overcome an Android Lint: Accessibility warning
Look into it WHYT

Call it for a String and find out!

As with the Add Tool UI, need simple, and lightweight UI for Searching within the tools dB.

• simple Popup style with a spinner with criteria, ET with keyword(s)/tag(s)
• ' Searching ... ' toast/overlay prompt
• LV with results, selecting one with bring up a Tool View UI --> that will now have to be CREATED!

I am still not sure how to properly query all entires of the db properly

Hoping something like this:

//Find all entries that have an _ID
        String selection = Contract_Reminder.ReminderEntry.COLUMN_TITLE + " ?";
        String[] selectionArgs = {};

Lint captures that can be removed if no interference IDT (in due time)

activity_pha_reminders_list.xml
activity_workbench.xml

I would say, if the 'app' is running tickety by the first Milestone - remove all commented references found.

Lookup the method to see what the latest acceptable work around is.

This could be resolved when the dB handlers are updated for the rest of the app

PHA_Reminder_Entry :: 394

This is probably not required here - should probably move it to constants/DbHandlers

PHA_Reminder_Entry :: 313

The outState should have the _ID thrown with it, so we can grab on return.
I believe that is how it goes...

For the long press menu
Make sure that the proper _id is fetched and db entries will be removed properly
- get the 'edit' option working first

In order to work with the dB entries, the _ROWID may be the fastest way - passing in an intent may be useful.

Possibly try sending the variable to the StringMath.jar to ensure it is a viable variable

PHA_Util_DatePicker :: 33

Is there something that has to be done when a date is set?
Or do i just read the values of the Object when the user is done?
Look into it!

Need to build a small, simple UI that can display the pertinent information of a tool

• search result display
• multiple menu-related endpoints
• needed for #4

PHA_SudokuGame :: 173

See if I can find a way to save last state or 'game' and continue it the next time.

For some reason, when the fields are populated, the
EditText for Reminder Title reverts to its hint
Possibly because of focus?

I think I should either condense the 'finds' to one method
Have two, or more, variables passed to it, one being an
intent - a CASE SELECT of the intent will then determine
the query and return Cursor contents.

Look into what to do with this location object!
Use the method to do tasks with the location object - such as?

ReminderService :: 15

Original Note:

These reminders and alarms will have to be stripped once we get this up and running
I have no use for them, and it seems this method of implementation is antiquated

I believe i originally intended these Reminders and Alarms to just be learning opportunities, and had thought to remove their existence once i had the PHA:LANX modules up and running.
I think i may be able to use these R&As if i can get them updated to current best-practices and working in a way which suits the app suite.

Pertains to a list of Db entries, selecting or long-pressing should/will bring up a context-sensitive menu to complete tasks on the entry. The _ID of the entry will have to be passed in order to perform operations on the proper entries.

I think i will have to populate a db with some dummy information in order to properly troubleshoot out what is happening, and where i will need to concentrate my efforts!

TiltScrolling no longer works for the PHA_MM activity.

PHA_SensorTest :: 119

Note says that the Location is no longer working for the SensorTest activity.
Look into it - verify and fix.

I believe I just have to distribute the XML to each layout:

<android.support.v7.widget.Toolbar
        android:layout_width="match_parent"
        android:layout_height="?attr/actionBarSize"
        android:id="@+id/tb_Workbench"
        android:background="@color/colorAccent"
        android:elevation="4dp"
        android:theme="@style/ThemeOverlay.AppCompat.ActionBar"
        />

and the call to each onCreate:

Toolbar toolbar = findViewById(R.id.tb_Workbench);
setSupportActionBar(toolbar);

Add, or find and link, the List Tools method to the Main TV / LV of the Workbench