task

CREATE-task# # -

FEATURE-000n-view-selling - porting to .org

[previously]

  1. [00:00] NEW task IN
    1. [] # 2922 - CREATE-task# # - ADD-FEATURE - view selling - port - ] porting the view / selling functionality into the .org version
    2. [*] reference example = # 2919 - CREATE-task# #  - FEATURE-000n-view-buying - porting to .org
    3. [*] reference example = # 2793 - CREATE-task# #  - FEATURE-4900-view-bio - porting to .org - currently the MyStuff/Bio feature is not functional
    4. [] TLDR - 'view selling' should show 'all'  'items' that have a status value of "For-Sale" ( and a Priority value of "?" )
    5. [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)
  2. [00:00] NEW task IN - prj-022 -
    1. [x] # # - FEATURE view/selling - using view_buying on db
    2. [x] created NEW PAGE 'view selling' AS copy of view / buying page, 
  3. [00:00] NEW task IN
    1. [x] EDIT PAGE - view selling -
    2. [x] changed queries,
    3. [x] changed title
    4. [x] EDIT PAGE -_menuMain - add link to view selling / all / Selling (aka ForSale)
  4. [00:00] NEW task IN - CREATE DOCUMENTATION
    1. [] 'view selling' should show 'all'  'items' that have a status value of "For-Sale" ( and a Priority value of "?" )
    2. [] EXAMPLE select all from view_selling WHERE status='Selling' and priority <= @Priority
    3. [*] FORMAT URL = view / selling / {case} / {status} / {priority} / {warehouse_name}
    4. [*] warehouse_name AKA case paramater, if case is all
    5. [*] if case is warehouse, provide warehouse name
    6. [*] if case is inventory, provide inventory name
    7. [*] if case is itemCategory, provide itemCategory name
    8. [] ?=  if case is all, provide 2nd param in case_parameter place ???
    9. [] ?= do we need a view, to list/link to all view / selling display options - aka - ] all, ] by warehouse, ] by inventory, ...
  5. [] [00:00] NEW task IN -  stats bar - location and style
    1. [] used NEW statsBarBio AS example
    2. [] in NEW LOCATION = relocated it to directly below navHeader, [x] removed current style of "statsbar" (used absolute postioning),
    3. [] created AS _statsBarBuying = itemsCount, itemsTotalCOST,
  6. [] [00:00] NEW task IN - review
    1. [] dont seem to see/find any documentation for view/buying OR view/selling
    2. [] # 4490 - list all projects, data size
  7.  [] [00:00] NEW task IN - git commit & merge
    1. [] commit -m = {"ADD-FEATURE - view selling - porting feature functionality from original sospep.com version, refactored, enhanced"}
    2. [] git local commited branch(ADD-FEATURE-selling)
    3. [] merged branch into master

[currently]

  1.  [00:00] NEW task IN
    1. [] # # -

[next]

  1. [00:00] NEW task IN TODO
    1. [] heading styles -
    2. [i] stats bar - functionality
    3. [i] database - update VIEW on OTHER DATABAseS, - [x] public [x] dons, [] ewa, [] other(s) ,
  2.  [00:00] NEW task IN
    1. [] # # - CREATE-task# # -
    2. [x] view / selling - all
    3. ===
    4. [x] view / selling - by warehouse
    5. [] view / selling - by inventory
    6. [] view / selling - by itemCategory
    7. ===
    8. [] view / selling - by period - ( day, month, week, quarter, )
    9. [] view / selling - by period - custom ( ex date range )
  3. [] >[00:00] NEW task IN - ISSUE-007 - stats bar functionality
    1. []  # # - [] stats bar - functionality -
    2. [x] moved 'statsBar' into '/Shared' as partial page, call RenderPage,
    3. [] ERROR re: - var doesnt exist in this context, RESOLUTION: changed varName to Page.varName
      1. [] even after changing to Page["var"] property
      2. [] 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
      3. [] RESOLUTION =
      4. [1] return prev, render component after display loop, then re position  (update from :using absolute position, to: ] reposition with script ] reposition with css)
      5. [] https://stackoverflow.com/questions/104953/position-an-html-element-relative-to-its-container-using-css
      6. [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
    4. [] ERROR re: type passed into arg, when calling the calculateCompletedPercentage helper method
  4.  

[reference]

  1. [*] sospep public - # 4900 - feature definition

query

SELECT * FROM `view_p1` WHERE priority = -5 and status = 'Completed'

SELECT * FROM view_buying WHERE status = Want || NEED ||

and priority =

 

create query

[] my groups - using order by in query to get dessired grouping, WORKS but very slow 

SELECT * FROM view_p1 WHERE priority=@0 && status=@1 ORDER by name_calendar ASC, name_plan ASC, name_taskgroup ASC
SELECT * FROM view_p1 WHERE priority= -1 && status='Completed' ORDER by name_calendar ASC, name_plan ASC, name_taskgroup ASC;

[] logic blocks removed from view buying

// LOGIC BL 1 - to build qry's IF called from viewCalendar's
    if (planId=="000")
  ...


Details Photos Edit more

Details

ID: 2922

NAME: plan-today-10-13

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 TIME: 2013-10-13 07:00:00

EST DURATION: 00:15:00

END DATE TIME: 2013-10-13 07:15:00

STATUS: Completed

PRIORITY: -5

OWNER ID: 75

Content Photos Edit more

photos

photos for this task

actions

Agenda Email task SMS task Priorities