{"action":"created","issue":{"url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/310","repository_url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib","labels_url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/310/labels{/name}","comments_url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/310/comments","events_url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/310/events","html_url":"https://github.com/MN-Script-Team/BZS-FuncLib/issues/310","id":186581803,"number":310,"title":"Idea: just merge all \"write_variable\" functions into one","user":{"login":"theVKC","id":5701751,"avatar_url":"https://avatars.githubusercontent.com/u/5701751?v=3","gravatar_id":"","url":"https://api.github.com/users/theVKC","html_url":"https://github.com/theVKC","followers_url":"https://api.github.com/users/theVKC/followers","following_url":"https://api.github.com/users/theVKC/following{/other_user}","gists_url":"https://api.github.com/users/theVKC/gists{/gist_id}","starred_url":"https://api.github.com/users/theVKC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theVKC/subscriptions","organizations_url":"https://api.github.com/users/theVKC/orgs","repos_url":"https://api.github.com/users/theVKC/repos","events_url":"https://api.github.com/users/theVKC/events{/privacy}","received_events_url":"https://api.github.com/users/theVKC/received_events","type":"User","site_admin":false},"labels":[{"id":345202254,"url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/labels/new%20function","name":"new function","color":"5319e7","default":false},{"id":155944777,"url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-01T16:38:01Z","updated_at":"2016-11-01T16:40:09Z","closed_at":null,"body":"Hear me out:\r\n\r\nIt should be possible to tell what screen you're on based on what position you're in, in PRISM or MAXIS, right? But that might be irrelevant, because...\r\n\r\n...perhaps the function can just look for the amount of underscores present. Or even the position on the screen. Or any other number of combinations of factors?\r\n\r\nBasically, here's what I'm inspired by:\r\n\r\n1. Folks (especially newer scriptwriters) often get confused about the difference between \"write_variable\" and \"write_bullet_and_variable\". It'd be nice to provide the option for a bullet as an optional parameter (just pass \"false\" or \"null\" if you don't need it). That'd make things easier for newbies.\r\n2. The function names are really long. It'd be nice to shorten it up to something like \"write_text\".\r\n3. If they all used the exact same parameters, in theory, PRISM and MAXIS could use the same functionality with variables on screen size dynamically determined. This would make bug fixing easier.\r\n4. Less functions to document.\r\n5. Easier expansion into new and unheard of areas (DORD? CORD? WF1? MMIS?).\r\n\r\nSo, thoughts gang? @MN-Script-Team/funclib-scriptwriters\r\n\r\nIf this is the direction we should explore, I can try it out instead of #277. "},"comment":{"url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/comments/257618051","html_url":"https://github.com/MN-Script-Team/BZS-FuncLib/issues/310#issuecomment-257618051","issue_url":"https://api.github.com/repos/MN-Script-Team/BZS-FuncLib/issues/310","id":257618051,"user":{"login":"lpshanley","id":8583547,"avatar_url":"https://avatars.githubusercontent.com/u/8583547?v=3","gravatar_id":"","url":"https://api.github.com/users/lpshanley","html_url":"https://github.com/lpshanley","followers_url":"https://api.github.com/users/lpshanley/followers","following_url":"https://api.github.com/users/lpshanley/following{/other_user}","gists_url":"https://api.github.com/users/lpshanley/gists{/gist_id}","starred_url":"https://api.github.com/users/lpshanley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lpshanley/subscriptions","organizations_url":"https://api.github.com/users/lpshanley/orgs","repos_url":"https://api.github.com/users/lpshanley/repos","events_url":"https://api.github.com/users/lpshanley/events{/privacy}","received_events_url":"https://api.github.com/users/lpshanley/received_events","type":"User","site_admin":false},"created_at":"2016-11-01T16:40:08Z","updated_at":"2016-11-01T16:40:08Z","body":"I love it. Rather that even requiring false or null you could add a handle for undefined so that if a person specifies nothing then its treated like false and if it has a value that value is used. That would be pretty easy to accomplish and it would make things quite nice ☺\r\n\r\n-Lucas\r\n“Valar dohaeris”\r\n#DecimateTheErrorRate\r\nP Please consider the environment before printing this email. P\r\n\r\nFrom: Veronica Cary [mailto:notifications@github.com]\r\nSent: Tuesday, November 01, 2016 11:38 AM\r\nTo: MN-Script-Team/BZS-FuncLib\r\nCc: Lucas Shanley; Team mention\r\nSubject: [MN-Script-Team/BZS-FuncLib] Idea: just merge all \"write_variable\" functions into one (#310)\r\n\r\n\r\nHear me out:\r\n\r\nIt should be possible to tell what screen you're on based on what position you're in, in PRISM or MAXIS, right? But that might be irrelevant, because...\r\n\r\n...perhaps the function can just look for the amount of underscores present. Or even the position on the screen. Or any other number of combinations of factors?\r\n\r\nBasically, here's what I'm inspired by:\r\n\r\n  1.  Folks (especially newer scriptwriters) often get confused about the difference between \"write_variable\" and \"write_bullet_and_variable\". It'd be nice to provide the option for a bullet as an optional parameter (just pass \"false\" or \"null\" if you don't need it). That'd make things easier for newbies.\r\n  2.  The function names are really long. It'd be nice to shorten it up to something like \"write_text\".\r\n  3.  If they all used the exact same parameters, in theory, PRISM and MAXIS could use the same functionality with variables on screen size dynamically determined. This would make bug fixing easier.\r\n  4.  Less functions to document.\r\n  5.  Easier expansion into new and unheard of areas (DORD? CORD? WF1? MMIS?).\r\n\r\nSo, thoughts gang? @MN-Script-Team/funclib-scriptwriters<https://github.com/orgs/MN-Script-Team/teams/funclib-scriptwriters>\r\n\r\nIf this is the direction we should explore, I can try it out instead of #277<https://github.com/MN-Script-Team/BZS-FuncLib/issues/277>.\r\n\r\n—\r\nYou are receiving this because you are on a team that was mentioned.\r\nReply to this email directly, view it on GitHub<https://github.com/MN-Script-Team/BZS-FuncLib/issues/310>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIL5e2CX072by5ZrT3Pv2BvLcpYenaPBks5q52rqgaJpZM4KmS_Y>.\r\n"}}
{"actor":{"display_login":"lpshanley"}}