Roy-DOU commited on
Commit
abd8f04
·
verified ·
1 Parent(s): 52a4d7d

Disambiguate the size formula's unit in c21

Browse files
Files changed (1) hide show
  1. tasks/c21/task.json +1 -1
tasks/c21/task.json CHANGED
@@ -18,7 +18,7 @@
18
  "milestones": [
19
  {
20
  "operator": "generate",
21
- "request": "We need an internal asset batch-processing workbench called PixelForge; let's put the shell and the data out first. Top to bottom: a toolbar at the very top with the product name \"PixelForge Batch Workbench\" on the left and room for action buttons on the right; the middle main area splits left and right — on the left the asset queue list (filename, format, size, and resolution all visible), on the right a detail panel that shows guidance copy when nothing is selected (like \"Pick an asset on the left to see its details\"), and when an item is clicked shows its filename, format, size, and resolution; at the very bottom pin a persistent status bar where you can see at a glance how many assets are in the queue, the total in MB, how many are selected, and the combined MB of the selected ones — MB always to one decimal place — with nothing selected initially.\n\nDon't make up the data; the rules from ops are: 48 assets in the queue, filenames asset_001 through asset_048 (zero-padded to three digits). Formats cycle in PNG, JPG, WEBP, GIF order — the 1st PNG, the 2nd JPG, the 3rd WEBP, the 4th GIF, then back to PNG, all the way through 48. Size is the sequence number times 0.7 plus 1.2 MB, to one decimal place, so the first is 1.9 MB. Resolution has three tiers: numbers divisible by 3 are 3840×2160, remainder 1 is 1920×1080, remainder 2 is 1280×720. Also, ops flagged urgent ones — the ones whose number is a multiple of 7; the entry must show at a glance that it's urgent, and other entries must not carry this marker."
22
  },
23
  {
24
  "operator": "add state",
 
18
  "milestones": [
19
  {
20
  "operator": "generate",
21
+ "request": "We need an internal asset batch-processing workbench called PixelForge; let's put the shell and the data out first. Top to bottom: a toolbar at the very top with the product name \"PixelForge Batch Workbench\" on the left and room for action buttons on the right; the middle main area splits left and right — on the left the asset queue list (filename, format, size, and resolution all visible), on the right a detail panel that shows guidance copy when nothing is selected (like \"Pick an asset on the left to see its details\"), and when an item is clicked shows its filename, format, size, and resolution; at the very bottom pin a persistent status bar where you can see at a glance how many assets are in the queue, the total in MB, how many are selected, and the combined MB of the selected ones — MB always to one decimal place — with nothing selected initially.\n\nDon't make up the data; the rules from ops are: 48 assets in the queue, filenames asset_001 through asset_048 (zero-padded to three digits). Formats cycle in PNG, JPG, WEBP, GIF order — the 1st PNG, the 2nd JPG, the 3rd WEBP, the 4th GIF, then back to PNG, all the way through 48. Size is (sequence number × 0.7 + 1.2) MB, rounded to one decimal place, so the first is 1.9 MB. Resolution has three tiers: numbers divisible by 3 are 3840×2160, remainder 1 is 1920×1080, remainder 2 is 1280×720. Also, ops flagged urgent ones — the ones whose number is a multiple of 7; the entry must show at a glance that it's urgent, and other entries must not carry this marker."
22
  },
23
  {
24
  "operator": "add state",