akc42 / football-mobile Goto Github PK

I want the path to have a parameter in it of the cid

In order to get a clearer view in my mind, develop the navigation help page (which is essentially just writing the text) to explain how navigation in the app works.

lets think a little about what the classes are as a starting point

• - the main app itself, menu - header and footer
• - session manager
• - session pages
• - route-manager
• - page managers (derived from route-manager)
• - sub-pages (home and others)
• - list manager
• - elements referred by list manager
• - form manager
• - form controls
• - common ui components - specifically <fm-page> to <user-page> , <app-page> to <fm-page>, <app-overlay> to <dialog-box> and <app-waiting> to <waiting-indicator>

This is going to require some framework first

• Define style for Admin Page
• Develop Global Admin home page
• Global Admin - Manage Competitions Page.

See #21

• list fields in the database that could contain this sort of text
• define a case statement that uses instr(string,substr) to find each of the valid current emoticons
• make a query to list them all - might initially just look for :

Css problem

I want to switch more to using the native form handling with native elements embedded but with unique styling. I think I can do this with existing <app-form> element appropriately modified. Slotted content will be the child elements, but I am hoping I can still these using the ::slotted selector

• review existing date elements to see how, when editable it should be integrated within the form
• review area needs for date element
• review documentation on validation and make a plan (as comments to this issue) as how to use it
• define styling I want to use for this
• review ::slotted selector and the sort of styling that can be done with that to see if that is an appropriate way to style form content
• change <app-form> to achieve the above

see #24

I was viewing a url of the form "/rounds/15/user/200" from an old competition. When I tried to refresh the page, I take a path through session manager which set the competition to the latest. Because the url doesn't contain the competition it proceeded to try and read a url for a user who wasn't in the latest competition and fell over.

So I think we need (apart from at the very beginning) to include the url in the in the requests.

My suggestion for this is for page manager to screen out the url before passing it on the the top level route manager

https://football.melindasbackups.com/13/rounds/15

something is not 100% not sure what yet

Implement a more meaningful navref

Its a mess at the moment and needs to be tidied up

This is a performance issue, we don't want the dom littered with dialog boxes when only one is needed, we send it a message and it responds by opening a dialog.

We should have enabled the same teams as last year, and can possibly allow changes to that. When all done we will set team lock in the competition

The code will try and get version and copyright info from the git repository if there is one. However in a live environment it is expected that the code will be copied in place and there will not be an underlying repository. A mechanism is built in to check a "release.info" file.

This needs to be checked as we move into the beta phase and this issue is a reminder to do that

see #21

I need to set up an instance of the old system and get some screen shots of that and use that to redesign the layout for running on a mobile phone

Set up a live system and started to use it. Noticed that the first page opening was the scores page and not the round data page

this should enable a user list which is scrollable (with momentum) with default slot for user data, and two heading slots, one for the user side element and one for the data part part

see #21 and #22

As I see it, the old emoticon system in previous versions of mobile is completely out of date. It was hardly every used and its going to be a pain to implement it as is. Instead we know have emoji, and particularly mobile phones and ipads have emojis available on them as standard. So we should switch over. which I think involves a number of steps

• #22 go through existing database and get a list of the actual emoticons that have been used
• #23 define a replacement emoji for all existing used emoticons
• create an emoticonremoval branch for work below
• remove emoticon references from server start up
• #29 make a conversion script (ideally in just sql, but alternatively as a special one off javascript program)
• integrate conversion with server start
• #32 tidy up code to remove old emoticon elements.

Having read lit-element discussion on styling I came across an idea I had not though of before. Namely that static get styles() function can have inline css template strings. However, there is an important and often overlooked point. these styles are per class and therefore can only be overridden in dev tools by adding per-element styles. Its a mild inconvenience, but will add to our approach.

• All elements should start development with the styles defined in a <style> tag in the render function.
• When an element reaches stability we can move styling into a css tagged template string in the get styles() static function. The very fact that our element has been styled that way is our indication that we regard styling as stable. Note that returning some or all of the styling back to the render function is acceptable if there is an issue.
• We will only use external style sheets when multiple element classes want them (e.g tooltip)

These rules are different from now - so we will tick off the tasks below as we get to them.

• re-encorporate all element specific styles inside their own element
• evaluate all remaining styles and remove those not needed
• change vscode snippets in creating new elements to match this policy (including starting with a <style> element in render)
• remove vscode snippet to add just style.

I think it is better (especially for caching) to store the team icons as static images.

• #25 go through existing images and turn them into png files stored in client/appimages/teams with just tid as their basename
• #26 fix code in client to use image files rather than database data
• #31 fix api calls on server to remove returning logos
• #30 fix database conversions to remove logos entirely (we will solely reference via tid)

I will be called with :cid/admin/round and from there I should either go to :cid/admin/round/:rid of a rid exists, else go to the create round page at :cid/admin/round/rounds page

See this https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html

came after looking at the issues in #27

see #21

An optimisation thing. We don't need multiple waiting indicators around the dom when one will do.

Note - I am not sure whether to latch the event onto the window or bubble up the dom. I am inclined to the latter as in future it gives flexibility to have more than one in the dom with different visual appearences.

See #24

Implement google re-captcha

• - make a client element
• - client element needs to resize to fit reservered space (and position over it)
• - server side validation works
• - supports re-get capture if fails (just wait to minutes so token not valid anymore)
• - prove it works in the e-mail logon section.

see #24

it seems to not have a position target, so assumes its parent and drops to bottom left

Currently it leaves you in what ever competition you happen to be in. I don't think that is the expectation

In particular I want to see what I can do with a page transition from the summary page and this new page. I would like all the other users to shrink, and this user to grow into a full page.

see #24

For the new version of football mobile we need a component library of some sort. In my last project I rolled my own, but that was because the components available were not mature. I feel this has changed.

However before a decision has to be made, I need to have sketched out the UI look