jsonedit 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- jsonedit-0.1.0/LICENSE +121 -0
- jsonedit-0.1.0/PKG-INFO +216 -0
- jsonedit-0.1.0/README.md +195 -0
- jsonedit-0.1.0/pyproject.toml +39 -0
- jsonedit-0.1.0/setup.cfg +4 -0
- jsonedit-0.1.0/src/jsonedit/__init__.py +0 -0
- jsonedit-0.1.0/src/jsonedit/__main__.py +3 -0
- jsonedit-0.1.0/src/jsonedit/jsonedit.py +1497 -0
- jsonedit-0.1.0/src/jsonedit.egg-info/PKG-INFO +216 -0
- jsonedit-0.1.0/src/jsonedit.egg-info/SOURCES.txt +11 -0
- jsonedit-0.1.0/src/jsonedit.egg-info/dependency_links.txt +1 -0
- jsonedit-0.1.0/src/jsonedit.egg-info/entry_points.txt +2 -0
- jsonedit-0.1.0/src/jsonedit.egg-info/top_level.txt +1 -0
jsonedit-0.1.0/LICENSE
ADDED
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
Creative Commons Legal Code
|
|
2
|
+
|
|
3
|
+
CC0 1.0 Universal
|
|
4
|
+
|
|
5
|
+
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
|
|
6
|
+
LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
|
|
7
|
+
ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
|
|
8
|
+
INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
|
|
9
|
+
REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
|
|
10
|
+
PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
|
|
11
|
+
THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
|
|
12
|
+
HEREUNDER.
|
|
13
|
+
|
|
14
|
+
Statement of Purpose
|
|
15
|
+
|
|
16
|
+
The laws of most jurisdictions throughout the world automatically confer
|
|
17
|
+
exclusive Copyright and Related Rights (defined below) upon the creator
|
|
18
|
+
and subsequent owner(s) (each and all, an "owner") of an original work of
|
|
19
|
+
authorship and/or a database (each, a "Work").
|
|
20
|
+
|
|
21
|
+
Certain owners wish to permanently relinquish those rights to a Work for
|
|
22
|
+
the purpose of contributing to a commons of creative, cultural and
|
|
23
|
+
scientific works ("Commons") that the public can reliably and without fear
|
|
24
|
+
of later claims of infringement build upon, modify, incorporate in other
|
|
25
|
+
works, reuse and redistribute as freely as possible in any form whatsoever
|
|
26
|
+
and for any purposes, including without limitation commercial purposes.
|
|
27
|
+
These owners may contribute to the Commons to promote the ideal of a free
|
|
28
|
+
culture and the further production of creative, cultural and scientific
|
|
29
|
+
works, or to gain reputation or greater distribution for their Work in
|
|
30
|
+
part through the use and efforts of others.
|
|
31
|
+
|
|
32
|
+
For these and/or other purposes and motivations, and without any
|
|
33
|
+
expectation of additional consideration or compensation, the person
|
|
34
|
+
associating CC0 with a Work (the "Affirmer"), to the extent that he or she
|
|
35
|
+
is an owner of Copyright and Related Rights in the Work, voluntarily
|
|
36
|
+
elects to apply CC0 to the Work and publicly distribute the Work under its
|
|
37
|
+
terms, with knowledge of his or her Copyright and Related Rights in the
|
|
38
|
+
Work and the meaning and intended legal effect of CC0 on those rights.
|
|
39
|
+
|
|
40
|
+
1. Copyright and Related Rights. A Work made available under CC0 may be
|
|
41
|
+
protected by copyright and related or neighboring rights ("Copyright and
|
|
42
|
+
Related Rights"). Copyright and Related Rights include, but are not
|
|
43
|
+
limited to, the following:
|
|
44
|
+
|
|
45
|
+
i. the right to reproduce, adapt, distribute, perform, display,
|
|
46
|
+
communicate, and translate a Work;
|
|
47
|
+
ii. moral rights retained by the original author(s) and/or performer(s);
|
|
48
|
+
iii. publicity and privacy rights pertaining to a person's image or
|
|
49
|
+
likeness depicted in a Work;
|
|
50
|
+
iv. rights protecting against unfair competition in regards to a Work,
|
|
51
|
+
subject to the limitations in paragraph 4(a), below;
|
|
52
|
+
v. rights protecting the extraction, dissemination, use and reuse of data
|
|
53
|
+
in a Work;
|
|
54
|
+
vi. database rights (such as those arising under Directive 96/9/EC of the
|
|
55
|
+
European Parliament and of the Council of 11 March 1996 on the legal
|
|
56
|
+
protection of databases, and under any national implementation
|
|
57
|
+
thereof, including any amended or successor version of such
|
|
58
|
+
directive); and
|
|
59
|
+
vii. other similar, equivalent or corresponding rights throughout the
|
|
60
|
+
world based on applicable law or treaty, and any national
|
|
61
|
+
implementations thereof.
|
|
62
|
+
|
|
63
|
+
2. Waiver. To the greatest extent permitted by, but not in contravention
|
|
64
|
+
of, applicable law, Affirmer hereby overtly, fully, permanently,
|
|
65
|
+
irrevocably and unconditionally waives, abandons, and surrenders all of
|
|
66
|
+
Affirmer's Copyright and Related Rights and associated claims and causes
|
|
67
|
+
of action, whether now known or unknown (including existing as well as
|
|
68
|
+
future claims and causes of action), in the Work (i) in all territories
|
|
69
|
+
worldwide, (ii) for the maximum duration provided by applicable law or
|
|
70
|
+
treaty (including future time extensions), (iii) in any current or future
|
|
71
|
+
medium and for any number of copies, and (iv) for any purpose whatsoever,
|
|
72
|
+
including without limitation commercial, advertising or promotional
|
|
73
|
+
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
|
|
74
|
+
member of the public at large and to the detriment of Affirmer's heirs and
|
|
75
|
+
successors, fully intending that such Waiver shall not be subject to
|
|
76
|
+
revocation, rescission, cancellation, termination, or any other legal or
|
|
77
|
+
equitable action to disrupt the quiet enjoyment of the Work by the public
|
|
78
|
+
as contemplated by Affirmer's express Statement of Purpose.
|
|
79
|
+
|
|
80
|
+
3. Public License Fallback. Should any part of the Waiver for any reason
|
|
81
|
+
be judged legally invalid or ineffective under applicable law, then the
|
|
82
|
+
Waiver shall be preserved to the maximum extent permitted taking into
|
|
83
|
+
account Affirmer's express Statement of Purpose. In addition, to the
|
|
84
|
+
extent the Waiver is so judged Affirmer hereby grants to each affected
|
|
85
|
+
person a royalty-free, non transferable, non sublicensable, non exclusive,
|
|
86
|
+
irrevocable and unconditional license to exercise Affirmer's Copyright and
|
|
87
|
+
Related Rights in the Work (i) in all territories worldwide, (ii) for the
|
|
88
|
+
maximum duration provided by applicable law or treaty (including future
|
|
89
|
+
time extensions), (iii) in any current or future medium and for any number
|
|
90
|
+
of copies, and (iv) for any purpose whatsoever, including without
|
|
91
|
+
limitation commercial, advertising or promotional purposes (the
|
|
92
|
+
"License"). The License shall be deemed effective as of the date CC0 was
|
|
93
|
+
applied by Affirmer to the Work. Should any part of the License for any
|
|
94
|
+
reason be judged legally invalid or ineffective under applicable law, such
|
|
95
|
+
partial invalidity or ineffectiveness shall not invalidate the remainder
|
|
96
|
+
of the License, and in such case Affirmer hereby affirms that he or she
|
|
97
|
+
will not (i) exercise any of his or her remaining Copyright and Related
|
|
98
|
+
Rights in the Work or (ii) assert any associated claims and causes of
|
|
99
|
+
action with respect to the Work, in either case contrary to Affirmer's
|
|
100
|
+
express Statement of Purpose.
|
|
101
|
+
|
|
102
|
+
4. Limitations and Disclaimers.
|
|
103
|
+
|
|
104
|
+
a. No trademark or patent rights held by Affirmer are waived, abandoned,
|
|
105
|
+
surrendered, licensed or otherwise affected by this document.
|
|
106
|
+
b. Affirmer offers the Work as-is and makes no representations or
|
|
107
|
+
warranties of any kind concerning the Work, express, implied,
|
|
108
|
+
statutory or otherwise, including without limitation warranties of
|
|
109
|
+
title, merchantability, fitness for a particular purpose, non
|
|
110
|
+
infringement, or the absence of latent or other defects, accuracy, or
|
|
111
|
+
the present or absence of errors, whether or not discoverable, all to
|
|
112
|
+
the greatest extent permissible under applicable law.
|
|
113
|
+
c. Affirmer disclaims responsibility for clearing rights of other persons
|
|
114
|
+
that may apply to the Work or any use thereof, including without
|
|
115
|
+
limitation any person's Copyright and Related Rights in the Work.
|
|
116
|
+
Further, Affirmer disclaims responsibility for obtaining any necessary
|
|
117
|
+
consents, permissions or other rights required for any use of the
|
|
118
|
+
Work.
|
|
119
|
+
d. Affirmer understands and acknowledges that Creative Commons is not a
|
|
120
|
+
party to this document and has no duty or obligation with respect to
|
|
121
|
+
this CC0 or use of the Work.
|
jsonedit-0.1.0/PKG-INFO
ADDED
|
@@ -0,0 +1,216 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: jsonedit
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: JSON Tree Editor
|
|
5
|
+
Author-email: Lion Kimbro <lionkimbro@gmail.com>
|
|
6
|
+
License-Expression: CC0-1.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/LionKimbro/jsonedit
|
|
8
|
+
Project-URL: Repository, https://github.com/LionKimbro/jsonedit
|
|
9
|
+
Project-URL: Issues, https://github.com/LionKimbro/jsonedit/issues
|
|
10
|
+
Keywords: json,editor,edit,agent,llm
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.9
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
17
|
+
Requires-Python: >=3.9
|
|
18
|
+
Description-Content-Type: text/markdown
|
|
19
|
+
License-File: LICENSE
|
|
20
|
+
Dynamic: license-file
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
# jsonedit
|
|
24
|
+
|
|
25
|
+
**A structured document editor for composing meaning in JSON.**
|
|
26
|
+
|
|
27
|
+
jsonedit is a tree-based editor designed for working with **hierarchical ideas**, not just JSON text.
|
|
28
|
+
It treats JSON as a *living document* — something you assemble, reshape, and extract from — rather than a file you manually type.
|
|
29
|
+
|
|
30
|
+
It is especially well suited for **LLM prompt construction, context curation, and structured knowledge editing**.
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
## Screenshot
|
|
35
|
+
|
|
36
|
+

|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## What jsonedit is (and is not)
|
|
41
|
+
|
|
42
|
+
jsonedit is **not** a traditional programmer’s JSON editor.
|
|
43
|
+
|
|
44
|
+
It is a **document compositor** built around one core idea:
|
|
45
|
+
|
|
46
|
+
> Edit meaning locally. Commit structure deliberately.
|
|
47
|
+
|
|
48
|
+
Instead of editing lines of text, you work directly with the document’s tree structure — selecting nodes, reshaping hierarchies, and exporting semantic fragments when needed.
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
## Why it exists
|
|
53
|
+
|
|
54
|
+
Modern workflows — especially those involving LLMs — often look like this:
|
|
55
|
+
|
|
56
|
+
* assemble structured prompts
|
|
57
|
+
* rearrange examples or schemas
|
|
58
|
+
* experiment safely
|
|
59
|
+
* extract only the relevant subtree
|
|
60
|
+
* paste into an AI context window
|
|
61
|
+
* iterate
|
|
62
|
+
|
|
63
|
+
Traditional editors treat JSON as text.
|
|
64
|
+
|
|
65
|
+
jsonedit treats JSON as **thought structure**.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## Core Concepts
|
|
70
|
+
|
|
71
|
+
### 🌲 Structure First
|
|
72
|
+
|
|
73
|
+
The primary editing unit is a **node**, not a line.
|
|
74
|
+
|
|
75
|
+
Common operations include:
|
|
76
|
+
|
|
77
|
+
* raise / lower items in hierarchy
|
|
78
|
+
* duplicate subtrees
|
|
79
|
+
* insert siblings
|
|
80
|
+
* rename keys
|
|
81
|
+
* delete with intelligent reselection
|
|
82
|
+
|
|
83
|
+
Navigation uses structural paths instead of line numbers.
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
### ✍️ Split-Brain Editing
|
|
88
|
+
|
|
89
|
+
Two coordinated views:
|
|
90
|
+
|
|
91
|
+
* **Tree view** → orientation and structure
|
|
92
|
+
* **Text pane** → focused semantic rewriting
|
|
93
|
+
|
|
94
|
+
You always know *where* you are structurally while editing *what* something means.
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
### 🧪 Safe Editing via Explicit Commit
|
|
99
|
+
|
|
100
|
+
Text edits remain sandboxed until you explicitly commit them.
|
|
101
|
+
|
|
102
|
+
This allows:
|
|
103
|
+
|
|
104
|
+
* experimentation without breaking structure
|
|
105
|
+
* temporary invalid JSON while thinking
|
|
106
|
+
* deliberate structural mutation
|
|
107
|
+
|
|
108
|
+
No accidental global edits.
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
### 📦 Export is a First-Class Action
|
|
113
|
+
|
|
114
|
+
jsonedit assumes you frequently want pieces of documents.
|
|
115
|
+
|
|
116
|
+
You can quickly copy:
|
|
117
|
+
|
|
118
|
+
* entire documents
|
|
119
|
+
* selected subtrees
|
|
120
|
+
* pretty or compact JSON
|
|
121
|
+
|
|
122
|
+
Ideal for moving structured context into LLM prompts.
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
### 🧠 JSON as a Living Document
|
|
127
|
+
|
|
128
|
+
Documents may include metadata and workspace information, encouraging long-lived structured artifacts rather than disposable config files.
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Ideal Use Cases
|
|
133
|
+
|
|
134
|
+
jsonedit works best when JSON represents **ideas**, not just data.
|
|
135
|
+
|
|
136
|
+
### ✅ Excellent for
|
|
137
|
+
|
|
138
|
+
* LLM prompt composition
|
|
139
|
+
* Context packaging for AI systems
|
|
140
|
+
* Agent or tool configuration
|
|
141
|
+
* Structured writing and outlining
|
|
142
|
+
* Dataset annotation
|
|
143
|
+
* Knowledge assembly in hierarchical form
|
|
144
|
+
|
|
145
|
+
Typical workflow:
|
|
146
|
+
|
|
147
|
+
1. Select subtree
|
|
148
|
+
2. Rewrite locally
|
|
149
|
+
3. Commit structure
|
|
150
|
+
4. Copy compressed node
|
|
151
|
+
5. Paste into LLM context
|
|
152
|
+
|
|
153
|
+
---
|
|
154
|
+
|
|
155
|
+
### ❌ Not Designed For
|
|
156
|
+
|
|
157
|
+
* General programming JSON editing
|
|
158
|
+
* Schema validation or linting
|
|
159
|
+
* Large machine-generated JSON files
|
|
160
|
+
* Collaborative merge workflows
|
|
161
|
+
* High-speed code typing environments
|
|
162
|
+
|
|
163
|
+
If you want VS Code for JSON — use VS Code.
|
|
164
|
+
|
|
165
|
+
jsonedit optimizes for **clarity of structure**, not typing speed.
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
## Install
|
|
170
|
+
|
|
171
|
+
```bash
|
|
172
|
+
pip install jsonedit
|
|
173
|
+
```
|
|
174
|
+
|
|
175
|
+
---
|
|
176
|
+
|
|
177
|
+
## Run
|
|
178
|
+
|
|
179
|
+
```bash
|
|
180
|
+
jsonedit
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
Open a file directly:
|
|
184
|
+
|
|
185
|
+
```bash
|
|
186
|
+
jsonedit <filepath>
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
## Requirements
|
|
192
|
+
|
|
193
|
+
* Python
|
|
194
|
+
* Tkinter available in your Python installation
|
|
195
|
+
|
|
196
|
+
(jsonedit is a desktop GUI application.)
|
|
197
|
+
|
|
198
|
+
---
|
|
199
|
+
|
|
200
|
+
## Philosophy
|
|
201
|
+
|
|
202
|
+
jsonedit is built on a few assumptions:
|
|
203
|
+
|
|
204
|
+
* JSON encodes ideas, not just data.
|
|
205
|
+
* Structure matters more than formatting.
|
|
206
|
+
* Users think in subtrees rather than lines.
|
|
207
|
+
* Editing should be deliberate and reversible.
|
|
208
|
+
* Exporting fragments is a primary activity.
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
## License
|
|
213
|
+
|
|
214
|
+
CC0 1.0 Universal — public domain.
|
|
215
|
+
See `LICENSE`.
|
|
216
|
+
|
jsonedit-0.1.0/README.md
ADDED
|
@@ -0,0 +1,195 @@
|
|
|
1
|
+
|
|
2
|
+
# jsonedit
|
|
3
|
+
|
|
4
|
+
**A structured document editor for composing meaning in JSON.**
|
|
5
|
+
|
|
6
|
+
jsonedit is a tree-based editor designed for working with **hierarchical ideas**, not just JSON text.
|
|
7
|
+
It treats JSON as a *living document* — something you assemble, reshape, and extract from — rather than a file you manually type.
|
|
8
|
+
|
|
9
|
+
It is especially well suited for **LLM prompt construction, context curation, and structured knowledge editing**.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Screenshot
|
|
14
|
+
|
|
15
|
+

|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## What jsonedit is (and is not)
|
|
20
|
+
|
|
21
|
+
jsonedit is **not** a traditional programmer’s JSON editor.
|
|
22
|
+
|
|
23
|
+
It is a **document compositor** built around one core idea:
|
|
24
|
+
|
|
25
|
+
> Edit meaning locally. Commit structure deliberately.
|
|
26
|
+
|
|
27
|
+
Instead of editing lines of text, you work directly with the document’s tree structure — selecting nodes, reshaping hierarchies, and exporting semantic fragments when needed.
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## Why it exists
|
|
32
|
+
|
|
33
|
+
Modern workflows — especially those involving LLMs — often look like this:
|
|
34
|
+
|
|
35
|
+
* assemble structured prompts
|
|
36
|
+
* rearrange examples or schemas
|
|
37
|
+
* experiment safely
|
|
38
|
+
* extract only the relevant subtree
|
|
39
|
+
* paste into an AI context window
|
|
40
|
+
* iterate
|
|
41
|
+
|
|
42
|
+
Traditional editors treat JSON as text.
|
|
43
|
+
|
|
44
|
+
jsonedit treats JSON as **thought structure**.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## Core Concepts
|
|
49
|
+
|
|
50
|
+
### 🌲 Structure First
|
|
51
|
+
|
|
52
|
+
The primary editing unit is a **node**, not a line.
|
|
53
|
+
|
|
54
|
+
Common operations include:
|
|
55
|
+
|
|
56
|
+
* raise / lower items in hierarchy
|
|
57
|
+
* duplicate subtrees
|
|
58
|
+
* insert siblings
|
|
59
|
+
* rename keys
|
|
60
|
+
* delete with intelligent reselection
|
|
61
|
+
|
|
62
|
+
Navigation uses structural paths instead of line numbers.
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
### ✍️ Split-Brain Editing
|
|
67
|
+
|
|
68
|
+
Two coordinated views:
|
|
69
|
+
|
|
70
|
+
* **Tree view** → orientation and structure
|
|
71
|
+
* **Text pane** → focused semantic rewriting
|
|
72
|
+
|
|
73
|
+
You always know *where* you are structurally while editing *what* something means.
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
### 🧪 Safe Editing via Explicit Commit
|
|
78
|
+
|
|
79
|
+
Text edits remain sandboxed until you explicitly commit them.
|
|
80
|
+
|
|
81
|
+
This allows:
|
|
82
|
+
|
|
83
|
+
* experimentation without breaking structure
|
|
84
|
+
* temporary invalid JSON while thinking
|
|
85
|
+
* deliberate structural mutation
|
|
86
|
+
|
|
87
|
+
No accidental global edits.
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
### 📦 Export is a First-Class Action
|
|
92
|
+
|
|
93
|
+
jsonedit assumes you frequently want pieces of documents.
|
|
94
|
+
|
|
95
|
+
You can quickly copy:
|
|
96
|
+
|
|
97
|
+
* entire documents
|
|
98
|
+
* selected subtrees
|
|
99
|
+
* pretty or compact JSON
|
|
100
|
+
|
|
101
|
+
Ideal for moving structured context into LLM prompts.
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
### 🧠 JSON as a Living Document
|
|
106
|
+
|
|
107
|
+
Documents may include metadata and workspace information, encouraging long-lived structured artifacts rather than disposable config files.
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## Ideal Use Cases
|
|
112
|
+
|
|
113
|
+
jsonedit works best when JSON represents **ideas**, not just data.
|
|
114
|
+
|
|
115
|
+
### ✅ Excellent for
|
|
116
|
+
|
|
117
|
+
* LLM prompt composition
|
|
118
|
+
* Context packaging for AI systems
|
|
119
|
+
* Agent or tool configuration
|
|
120
|
+
* Structured writing and outlining
|
|
121
|
+
* Dataset annotation
|
|
122
|
+
* Knowledge assembly in hierarchical form
|
|
123
|
+
|
|
124
|
+
Typical workflow:
|
|
125
|
+
|
|
126
|
+
1. Select subtree
|
|
127
|
+
2. Rewrite locally
|
|
128
|
+
3. Commit structure
|
|
129
|
+
4. Copy compressed node
|
|
130
|
+
5. Paste into LLM context
|
|
131
|
+
|
|
132
|
+
---
|
|
133
|
+
|
|
134
|
+
### ❌ Not Designed For
|
|
135
|
+
|
|
136
|
+
* General programming JSON editing
|
|
137
|
+
* Schema validation or linting
|
|
138
|
+
* Large machine-generated JSON files
|
|
139
|
+
* Collaborative merge workflows
|
|
140
|
+
* High-speed code typing environments
|
|
141
|
+
|
|
142
|
+
If you want VS Code for JSON — use VS Code.
|
|
143
|
+
|
|
144
|
+
jsonedit optimizes for **clarity of structure**, not typing speed.
|
|
145
|
+
|
|
146
|
+
---
|
|
147
|
+
|
|
148
|
+
## Install
|
|
149
|
+
|
|
150
|
+
```bash
|
|
151
|
+
pip install jsonedit
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Run
|
|
157
|
+
|
|
158
|
+
```bash
|
|
159
|
+
jsonedit
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
Open a file directly:
|
|
163
|
+
|
|
164
|
+
```bash
|
|
165
|
+
jsonedit <filepath>
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
170
|
+
## Requirements
|
|
171
|
+
|
|
172
|
+
* Python
|
|
173
|
+
* Tkinter available in your Python installation
|
|
174
|
+
|
|
175
|
+
(jsonedit is a desktop GUI application.)
|
|
176
|
+
|
|
177
|
+
---
|
|
178
|
+
|
|
179
|
+
## Philosophy
|
|
180
|
+
|
|
181
|
+
jsonedit is built on a few assumptions:
|
|
182
|
+
|
|
183
|
+
* JSON encodes ideas, not just data.
|
|
184
|
+
* Structure matters more than formatting.
|
|
185
|
+
* Users think in subtrees rather than lines.
|
|
186
|
+
* Editing should be deliberate and reversible.
|
|
187
|
+
* Exporting fragments is a primary activity.
|
|
188
|
+
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
## License
|
|
192
|
+
|
|
193
|
+
CC0 1.0 Universal — public domain.
|
|
194
|
+
See `LICENSE`.
|
|
195
|
+
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["setuptools>=61.0"]
|
|
3
|
+
build-backend = "setuptools.build_meta"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "jsonedit"
|
|
7
|
+
version = "0.1.0"
|
|
8
|
+
description = "JSON Tree Editor"
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
license = "CC0-1.0"
|
|
11
|
+
license-files = ["LICENSE"]
|
|
12
|
+
requires-python = ">=3.9"
|
|
13
|
+
dependencies = []
|
|
14
|
+
authors = [
|
|
15
|
+
{ name = "Lion Kimbro", email = "lionkimbro@gmail.com" }
|
|
16
|
+
]
|
|
17
|
+
keywords = ["json", "editor", "edit", "agent", "llm"]
|
|
18
|
+
classifiers = [
|
|
19
|
+
"Programming Language :: Python :: 3",
|
|
20
|
+
"Programming Language :: Python :: 3 :: Only",
|
|
21
|
+
"Programming Language :: Python :: 3.9",
|
|
22
|
+
"Programming Language :: Python :: 3.10",
|
|
23
|
+
"Programming Language :: Python :: 3.11",
|
|
24
|
+
"Programming Language :: Python :: 3.12"
|
|
25
|
+
]
|
|
26
|
+
|
|
27
|
+
[project.urls]
|
|
28
|
+
Homepage = "https://github.com/LionKimbro/jsonedit"
|
|
29
|
+
Repository = "https://github.com/LionKimbro/jsonedit"
|
|
30
|
+
Issues = "https://github.com/LionKimbro/jsonedit/issues"
|
|
31
|
+
|
|
32
|
+
[project.gui-scripts]
|
|
33
|
+
jsonedit = "jsonedit.jsonedit:main"
|
|
34
|
+
|
|
35
|
+
[tool.setuptools]
|
|
36
|
+
package-dir = {"" = "src"}
|
|
37
|
+
|
|
38
|
+
[tool.setuptools.packages.find]
|
|
39
|
+
where = ["src"]
|
jsonedit-0.1.0/setup.cfg
ADDED
|
File without changes
|