joereddington / MrsLandingham

An exercise in working out what my workflow actually is.
0 stars 1 forks source link

Sprint: Development for the phone #2

Closed joereddington closed 7 years ago

joereddington commented 7 years ago

I've been playing with pythonista recently and I'm interested to know how much use ML might be on the phone. In particularly I'm interested to see if it might be even more interesting from a graphic perspective.

Let's map this out.

joereddington commented 7 years ago
01/07/17 15:14:

As part of this, we'll also be strengthening MLs project management work.

15:18:

I've done a quick rewrite. I'll reload -but first I want to be able to quickly skip the openning for ML

15:21:

I've added the ability to skip the opening. Now I want to refactor so I can go directly to working on a project.

15:23:

What's next? Oh, look at the workflow? I supose I should push the current code and see how easy it is to pull down.

15:23:

Time.

15:28:

Okay, I push things up via a merge - but running into a problem bringing them down...

15:33:

Turns out that may have been because iternet was off on my phone...

15:33:

Next action is to try again with a change.

15:37:

Redid - working fine.

15:37:

Now let's see if those exmaples work.

15:39:

It appears from http://omz-software.com/pythonista/docs/ios/ui.html that the library is for iOS only...

15:44:

But there is a really really interesting 'design your own' funciton... hmmm.... I'm trying to build a 'do' menu. Let's see how I trigger it...

15:52:

Wow... That worked... hmmm.

15:58:

I used this forum to find out how to change a label. Now to get 'yes' and 'no' working...

16:12:

I've committed, we're at the first stages of working out what happens here.

16:20:

Okay, I've worked out how dialogs work. But we might want to think carefully about restructuring here...

So dialogs are a bit ugly looking, but that is fine. The problem I have is that I need to overload the do function - again... fine. Because there will simply be a do function.

16:23:

Also the dialog has NOT quite enought text to be able to give a good instruction.

01/07/17 16:24:

So what's the design? Is it that we have an instruction on each page for the yes/nos and we find a way to make them work?

In side a class that might be a thing.

There's a problem that the design is fundermentally different - yes and NO in a gui means that the yes and the NO functions do most of the work - but I've been looking at something that is procedural where the yes/no thing is simply an if statement.... hmmm.

16:29:
16:39:

Trying to get a wait thing working...

16:45:

https://stackoverflow.com/questions/42933821/getting-a-function-call-to-wait-until-an-input-via-ui-is-received

16:48:

https://forum.omz-software.com/topic/1050/wait-for-view-to-close This actually looks like the right thing...

01/07/17 17:02:

I've done some more work on it. Solved the dialog thing (for now) and had a very short attempt at intergrating the code with the main thing - but I'm running into a problem with global variables and the like...

joereddington commented 7 years ago
05/07/17 07:02:

Update - this sprint finished nicely - although much of it will need to be rewritten now that the workflow is done in levels.