redzic / dynamic-fake-bank Goto Github PK

As of now, the generated banks all look very similar.

To achieve completely different looking banks each time, some changed need to be made (in order of priority):

• Instead of having a fixed template for elements that should go in, which thus causes very similar-looking banks with slightly different colors, an entire layout should be generated for each page that is extensive. This would entail that not all types of elements would need to actually be used (like they are now).
• Have multiple groups of selection pools that align with some theme so that the bank look & feel does not look the same. If we were to try to avoid this issue without this, the bank would look very inconsistent. If we don't fix the issue, the generated banks would all look very similar

Here are some random ideas for the future:

• Have a more flexible config file. For example, instead of specifying a specific element manually, just specify "random" in the config file and the program will choose one for you based on that

It will let you make a transfer from one account to another, but many features are broken

• No AJAX support so it is not easy to display a message if something goes wrong
• There is no limit on how much you can transfer
• You can effectively "generate" (fake) money by transferring money from an account to that same account
• The generic default option ("Account") displays a developer error message instead of a user error message
• They are not formatted with the correct date at all

Many files like the database are tracked and shouldn't be, as they are dynamically generated anyway

Especially on some templates with the mobile app badge. One way to fix this might be to include the paragraph below the mobile app badge in the "hero" template or whatever it's called. Then, move the mobile app badge to be in a flexbox with the paragraph, and add a negative top margin to move it up.

There needs to be a way to generate realistic account information.

• Delete all existing account and transactions
• Randomly create new accounts with different account numbers
• Fill each account with random transactions (for now, they can be the same ones)
• Edit build.py to actually have a function that does something with the -a argument is passed

add some screenshots to show what it looks like

Now that tracking is removed, it seems like you must first manually create certain nonexistent directories, migrate changes, and regenerate the bank. Regenerating the bank is actually an acceptable step to get it working, but not all of this other stuff.

I think adding tracking to certain files that while still constantly change, at least have some kind of initial value or something. Or have it so that build.py has an initial set procedure flag which can automate this step (which is mostly undesirable). At the very least, document that this is an issue and how to fix it in the README.