This commit is contained in:
2020-04-11 20:39:34 +00:00
parent adb386ca12
commit 77448df198
2 changed files with 5 additions and 8 deletions

View File

@@ -51,14 +51,10 @@ CURRENT TODOs
todo: RECORD HISTORY (HAS OUTSTANDING ITEMS)
- finish up current large User log view
- Event type and date are kind of fucked being all grayed out and small, is that the "material" way?
- what is the most important info and where should it go? Room for event type and date in title? Opposite in large view?
- Make object view - Current view works for User view, make a dedicated Object view
- Put object name in title or whatever I do for User View title username
- Make alternate template for small screen for both views, right now it's only suitable for above small (medium?) view
- Will affect title, maybe needs to go into each record redundantly
- could easily feed a report with slight modifications...hmm.
- make a todo entry in the report section below to include the ability of feeding reports from local data in addition to off the server
- Does it benefit from caching? (not really thinking so as this is a different animal than search but something to ponder a bit)

View File

@@ -22,11 +22,11 @@
>{{ i.date }} - {{ getEventName(i.event) }}</v-card-subtitle
>
<v-card-text
><v-icon class="mr-4">{{
><v-icon large class="mr-2">{{
getIconForObjectType(i.objectType)
}}</v-icon
>{{ getNameForType(i.objectType) }}
<div v-if="i.textra">{{ i.textra }}</div>
<div class="mt-4" v-if="i.textra">{{ i.textra }}</div>
</v-card-text>
<v-card-actions>
@@ -222,7 +222,8 @@ export default {
temp[i].index = currentEventCount + i;
//test
temp[i].textra = "This is some extra text. Blah blah blah blah.";
temp[i].textra =
"This is some extra text. Blah blah blah blah blah x.This is some extra text. Blah blah blah blah blah x.This is some extra text. Blah blah blah blah blah x.This is some extra text. Blah blah blah blah blah x.This is some extra text. Blah blah blah blah blah x.12345";
}
vm.obj = [...vm.obj, ...temp];