User defined directory

Need help? Ask here!
7

Hi @Puijterwaal,

Our app is for engineers doing site visits and taking photos, mainly on there phones, of different aspects of a site, be it cracks, defects or point of interest. These photos are then placed into a report (either a word, powerpoint or PDF document), accompanied by a short description and image source. There can 100+ images in these reports.

The intended design for our Viktor app was to;

  1. Enter in a report name and image source (image source is consistent throughout report)
  2. Have the user select a folder directory that contains the images
  3. Select a report format, either DOCX or PPTX.
  4. Click a button that populates a table within the app, that has two columns, Image name and description. The user can then enter in a description for an image or copy and paste in a pre-written table from excel. We also have a dropdown menu containing the image names that the user can select and then update th eimage view (We would like the image view to update after selecting the image here)
  5. After filling in all the descriptions the user clicks a button and create the report.
  6. On the next step, the user can download the report. If they click update, a preview of the report is shown in a pdf format. (We would like this view to be triggered with the previous, ‘Create Report’ button)
  7. The download of the report is a zip file containing the report in a PDF format and the chosen format from step 3.

Here are some images of the current interface:

image
image1898×745 56.6 KB

image
image1905×1001 163 KB

Problems:

  1. Uploading 100+ images to viktor takes time and seems inefficient. We would like to just upload a folder path, and then when actually making the report we can go grab the images and place them in the report. Currently we have to upload them, convert to bytes, pass to a function that places them in a report. Moving this process into an action that only occurs after pressing a button helps with the efficiency of the app as there would only be one long load time as opposed to several.
  2. Views only updating when clicking update rather than triggering on a user interaction with a specific paramater. (We don’t want the view to trigger after every change to a paramater (because its slow), therefore changing the duration guess to below 3 isn’t an option. (This was raised in a seperate post and has been added to your feature requests I believe).

Hope this is clear.

Thanks,
Charlie

Images remaining after closing app