Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
purr-data
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jonathan Wilkes
purr-data
Commits
b21624d1
Commit
b21624d1
authored
9 years ago
by
Jonathan Wilkes
Browse files
Options
Downloads
Patches
Plain Diff
update todo
parent
1df706b3
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
pd/nw/todo.txt
+9
-3
9 additions, 3 deletions
pd/nw/todo.txt
with
9 additions
and
3 deletions
pd/nw/todo.txt
+
9
−
3
View file @
b21624d1
...
@@ -42,9 +42,11 @@ Node-webkit stuff:
...
@@ -42,9 +42,11 @@ Node-webkit stuff:
Everything else: (A [x] means we've fixed it)
Everything else: (A [x] means we've fixed it)
[ ] packaging as app, setting correct appname, etc
[ ] packaging as app, setting correct appname, etc
[
] check if patch windows with screenposition (0,0) get stuck underneath OSX
[
x
] check if patch windows with screenposition (0,0) get stuck underneath OSX
menu.
menu.
[ ] abstract away appendChild
[x] abstract away appendChild
Note: not needed at that time. Maybe further in the future when we've
pulled most of the GUI stuff out of the c code we can revisit this.
[x] font-size should be set as css property for a class of text, rather than
[x] font-size should be set as css property for a class of text, rather than
per each gobj in svg
per each gobj in svg
(Note: not sure that this makes sense right now. We could use a class to
(Note: not sure that this makes sense right now. We could use a class to
...
@@ -53,8 +55,12 @@ Everything else: (A [x] means we've fixed it)
...
@@ -53,8 +55,12 @@ Everything else: (A [x] means we've fixed it)
the font dialog.)
the font dialog.)
[ ] find a better approach to escaping characters for the gui than
[ ] find a better approach to escaping characters for the gui than
escape_double_quotes kludge (and handle any other problematic chars)
escape_double_quotes kludge (and handle any other problematic chars)
[
] once garrays are drawn inside a <g> we won't have to individually erase
[
x
] once garrays are drawn inside a <g> we won't have to individually erase
each child of a scalar
each child of a scalar
Note: Not sure exactly how we would do this. While it makes the most sense
from the GUI-side, a lot the interfaces on the C-side would need to be
changed. Seems like an enormous undertaking, unless there's some clever
hack that I'm not yet seeing.
[ ] make pdgui function names more consistent
[ ] make pdgui function names more consistent
[ ] in draw_vis, move tags to front of function call so they don't have to
[ ] in draw_vis, move tags to front of function call so they don't have to
be in an array
be in an array
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment