edit-task

Task Description: SUM(7)] pln(today 2922) ] doc(yesterday 28##) x] FIX PG view/article ] CD update 1769 closure, del o.137 sII x] MGMT tasks Q prioritized,assigned

Start Date:

Start Time:

Duration:

Priority:

Status: To Do Completed In Process

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;">CREATE-task# # -</h1> <h1 style="text-align: center;">FEATURE-000n-view-selling - porting to .org</h1> <h2>[previously]</h2> <ol> <li><strong>[00:00] NEW task IN </strong></li> <ol> <li>[] # 2922 - <a href="/view/task?id=2922" target="_blank">CREATE-task# # </a>- ADD-FEATURE - view selling - port - ] porting the view / selling functionality into the .org version</li> <li>[*] reference example = # 2919 - <a href="/view/task?id=2919" target="_blank">CREATE-task# #</a>&nbsp; - FEATURE-000n-view-buying - porting to .org</li> <li>[*] reference example = # 2793 - <a href="/view/task?id=2793" target="_blank">CREATE-task# #</a>&nbsp; - FEATURE-4900-view-bio - porting to .org - currently the MyStuff/Bio feature is not functional</li> <li>[] TLDR - 'view selling' should show 'all'&nbsp; 'items' that have a status value of "For-Sale" ( and a Priority value of "?" )</li> <li>[x] these items are then organized by the warehouse, inventory and itemgroup that they appear in, aka bio_by_project, [*] based on DB view_buying (actually uses it)</li> </ol> <li><strong>[00:00] NEW task IN - <a href="/view/plans?id=1" target="_blank">prj-022</a> -<a href="/view/plans?id=1" target="_blank"><br /></a></strong></li> <ol> <li>[x] # # - FEATURE view/selling - using view_buying on db</li> <li>[x] created NEW PAGE 'view selling' AS copy of view / buying page,&nbsp;</li> </ol> <li><strong>[00:00] NEW task IN</strong></li> <ol> <li>[x] EDIT PAGE - view selling -</li> <li>[x] changed queries,</li> <li>[x] changed title</li> <li>[x] EDIT PAGE -_menuMain - add link to view selling / all / Selling (aka ForSale)</li> </ol> <li><strong>[00:00] NEW task IN - CREATE DOCUMENTATION<br /></strong></li> <ol> <li>[] 'view selling' should show 'all'&nbsp; 'items' that have a status value of "For-Sale" ( and a Priority value of "?" )</li> <li>[] EXAMPLE select all from view_selling WHERE status='Selling' and priority &lt;= @Priority</li> <li><strong>[*] FORMAT URL = view / selling / {case} / {status} / {priority} / {warehouse_name}</strong></li> <li>[*] warehouse_name AKA case paramater, if case is all</li> <li>[*] if case is warehouse, provide warehouse name</li> <li>[*] if case is inventory, provide inventory name</li> <li>[*] if case is itemCategory, provide itemCategory name</li> <li>[] ?=&nbsp; if case is all, provide 2nd param in case_parameter place ???</li> <li>[] ?= do we need a view, to list/link to all view / selling display options - aka - ] all, ] by warehouse, ] by inventory, ...</li> </ol> <li><strong>[] [00:00] NEW task IN -&nbsp; stats bar - location and style<br /></strong></li> <ol> <li>[] used NEW statsBarBio AS example</li> <li>[] in NEW LOCATION = relocated it to directly below navHeader, [x] removed current style of "statsbar" (used absolute postioning),</li> <li>[] created AS _statsBarBuying = itemsCount, itemsTotalCOST,</li> </ol> <li><strong>[] [00:00] NEW task IN - review <br /></strong></li> <ol> <li>[] dont seem to see/find any documentation for view/buying OR view/selling</li> <li><span style="background-color: #ffff99;">[] # 4490 - list all projects, data size</span></li> </ol> <li><strong>&nbsp;[] [00:00] NEW task IN - git commit &amp; merge</strong></li> <ol> <li>[] commit -m = {"ADD-FEATURE - view selling - porting feature functionality from original sospep.com version, refactored, enhanced"}</li> <li>[] git local commited branch(ADD-FEATURE-selling)</li> <li>[] merged branch into master</li> </ol></ol> <h2>[currently]</h2> <ol> <li>&nbsp;<strong>[00:00] NEW task IN </strong></li> <ol> <li>[] # # -</li> </ol></ol> <h2>[next]</h2> <ol> <li><strong>[00:00] NEW task IN TODO</strong></li> <ol> <li>[] heading styles -</li> <li>[i] stats bar - functionality</li> <li>[i] database - update VIEW on OTHER DATABAseS, - [x] public [x] dons, [] ewa, [] other(s) ,</li> </ol> <li><strong>&nbsp;[00:00] NEW task IN </strong></li> <ol> <li>[] # # - <a href="/view/task?id=1839" target="_blank">CREATE-task# # </a>-</li> <li>[x] view / selling - all</li> <li>===</li> <li>[x] view / selling - by warehouse</li> <li>[] view / selling - by inventory</li> <li>[] view / selling - by itemCategory</li> <li>===</li> <li>[] view / selling - by period - ( day, month, week, quarter, )</li> <li>[] view / selling - by period - custom ( ex date range )</li> </ol> <li><strong>[] &gt;[00:00] NEW task IN - ISSUE-007 - stats bar functionality<br /></strong></li> <ol> <li>[]&nbsp; # # - [] stats bar - functionality -</li> <li>[x] moved 'statsBar' into '/Shared' as partial page, call RenderPage,</li> <li>[] ERROR re: - var doesnt exist in this context, RESOLUTION: changed varName to Page.varName</li> <ol> <li>[] even after changing to Page["var"] property</li> <li>[] PROBLEM WAS - shared page is rendered BEFORE values are caculated. Values are calculated in the display list items loop. Page is rendered at the top. This is why was previously using</li> <li>[] RESOLUTION =</li> <li>[1] return prev, render component after display loop, then re position&nbsp; (update from :using absolute position, to: ] reposition with script ] reposition with css)</li> <li>[] https://stackoverflow.com/questions/104953/position-an-html-element-relative-to-its-container-using-css</li> <li>[2] call js method - ] write vars to input hidden, ] call js method, updateStatsBar(), ] write js method updateStatsBar, -uses hidden input vars to update statsbar # values</li> </ol> <li>[] ERROR re: type passed into arg, when calling the calculateCompletedPercentage helper method</li> </ol> <li>&nbsp;</li> </ol> <h2>[reference]</h2> <div><ol> <li>[*] sospep public - # 4900 - feature definition</li> </ol></div> <hr /> <h1 style="text-align: center;">query</h1> <p style="text-align: left;">SELECT * FROM `view_p1` WHERE priority = -5 and status = 'Completed'</p> <p style="text-align: left;">SELECT * FROM view_buying WHERE status = Want || NEED ||</p> <p style="text-align: left;">and priority =</p> <p style="text-align: left;">&nbsp;</p> <p>create query</p> <div>[] my groups - using order by in query to get dessired grouping, WORKS but very slow&nbsp; <br /><br />SELECT * FROM view_p1 WHERE priority=@0 &amp;&amp; status=@1 ORDER by name_calendar ASC, name_plan ASC, name_taskgroup ASC <br />SELECT * FROM view_p1 WHERE priority= -1 &amp;&amp; status='Completed' ORDER by name_calendar ASC, name_plan ASC, name_taskgroup ASC;</div> <div><hr /></div> <div><hr /></div> <h1 style="text-align: center;">[] logic blocks removed from view buying</h1> <div>// LOGIC BL 1 - to build qry's IF called from viewCalendar's<br />&nbsp;&nbsp;&nbsp; if (planId=="000")</div> <div>&nbsp; ...</div> <div><br /><br /></div>