JSON objects in the ODB, Markdown text instead of WP-Text
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
研究方向
No files, tests, or entry points are named. Start by breaking the proposal into the JSON-in-ODB and Markdown-backed wp-text editor work, then identify the existing ODB, scripting-language, and wp-text implementations. Done requires an agreed scope and tests for JSON storage/navigation and editing wp-text as Markdown.
由索引模型根據 Issue 內容生成。
描述
A bit of thinking out loud. Last time I worked on Frontier, JSON didn't exist and neither did Markdown.
If we were doing it today, we would have used both formats, and integrated them into the language of Frontier, both the scripting language and the odb, we could manipulate and store them.
JSON
I never liked dealing with XML objects in Frontier. We mapped it onto the odb structure, but XML allows multiple objects to have multiple instances with the same name, where as the odb insists every name is unique. We did a hack, and got it to work, but JSON would be better.
Example of how this might work -- the reallySimple package and daveRss, the first for reading feeds, and the latter for writing them. The input and output go in and out in JSON.
JSON details
A JSON type.
JSON constants, when you assign one to a value, it's stored as a JSON type.
Navigation is done the same way JavaScript does it.
Here's an example of a constant assignment to a local.
local (historyArray = [
{
"text": "The <b>Associated</b> <i>Press</i> is adding user-generated social content into its wire services.",
"title": "",
"link": "http://www.niemanlab.org/2017/05/the-associated-press-is-adding-user-generated-social-content-verified-of-course-into-its-wire-services/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+NiemanJournalismLab+(Nieman+Journalism+Lab)",
"linkShort": "http://bit.ly/2qoz8i6",
"when": "2017-05-16T16:47:07.045Z",
"guid": {
"flPermalink": true,
"value": "http://www.niemanlab.org/2017/05/the-associated-press-is-adding-user-generated-social-content-verified-of-course-into-its-wire-services/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+NiemanJournalismLab+(Nieman+Journalism+Lab)"
},
"idTweet": "864522615880380419",
"twitterScreenName": "davewiner",
},
{
"text": "If Donald Trump Were a C.E.O., He'd Probably Be Fired Today.",
"title": "",
"link": "http://www.newyorker.com/news/john-cassidy/if-donald-trump-were-a-c-e-o-hed-probably-be-fired-today?mbid=rss",
"linkShort": "http://bit.ly/2qoxxce",
"when": "2017-05-16T16:44:25.731Z",
"guid": {
"flPermalink": true,
"value": "http://www.newyorker.com/news/john-cassidy/if-donald-trump-were-a-c-e-o-hed-probably-be-fired-today?mbid=rss"
},
"idTweet": "864521938814857216",
"twitterScreenName": "davewiner"
},
])
Referencing part of the JSON object.
local (guid = historyArray [ix].guid)
if (guid.flPermalink)
scratchpad.guid = guid
Markdown
This is the perennial problem for Frontier implementors, we licensed a WP engine for the original Frontier, back in the early 90s, and the product wasn't maintained, something like that -- but there were often problems in moving it forward with us. wp-text type is a pain in the ass. I left this for a to-do item until now, but I want to solve it because some of the apps legitimately use wp-text type.
What I want to do is implement it as Markdown.
So when you see a wp-text object you can open it in a window, the user can edit it, and when they save it back to the odb we store Markdown text.
I haven't thought it through any more than that, but wanted to let people know I'm going in this direction.
Haven't done anything with JSON yet.
- 主要語言
- 沒有語言資料
- 星號
- 0
- 分支
- 0
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
我們還沒有檢查這個專案的環境設定檔。先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
scripting/helloFrontier 的其他 Issue
-
難度 5/5 一週以上 新手友好度 25/100
scripting/helloFrontier#15 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 35/100
scripting/helloFrontier#13 · 5 則留言 · 1 個 reaction ·
-
難度 3/5 1-2 天 新手友好度 35/100
scripting/helloFrontier#12 ·
-
難度 5/5 一週以上 新手友好度 10/100
scripting/helloFrontier#11 ·
-
難度 5/5 一週以上 新手友好度 25/100
scripting/helloFrontier#10 ·
查看 scripting/helloFrontier 的全部 Issue
相似的 Issue
-
check:failed feeds:add
難度 2/5 1-3 小時 新手友好度 70/100
iptv-org/database#36179 · 1 則留言 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 1/5 1-3 小時 新手友好度 88/100
ClickHouse/pg_clickhouse#383 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆