Error: no such theme PatternSkinTheme

Difference: InkToDo (1 vs. 35)

Revision 35
2011-07-26 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

TUESDAY
Deleted:
<
<
  1. Finish wrapping all console procedures.
 
  1. Make sure object-get-center is consistent (0-100 or 0-255)
  2. Test procedures, check info tab; check for errors and omissions
  3. Write a notes/dev file (for ex, documentation for wrapped functions)
Revision 34
2011-07-25 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Changed:
<
<
This Week:
  1. wrap all console functions
  2. fix opacity (1-100)
  3. wrap move to hshift and vshift; update INFO TAB.
  4. Write lots of notes/documentation of work for future projects
    1. notes on why some functions were wrapped
    2. README explaining package, how to install, and how to build documentation.
    3. update wiki procs list/information
  5. make a set of examples for Elizabeth/an "examples" folder
  6. test all functions; make sure everything is working, and present.
  7. write get-center procs.

Next Week:
  1. INFORMATION TAB in console- edit
>
>
TUESDAY
  1. Finish wrapping all console procedures.
  2. Make sure object-get-center is consistent (0-100 or 0-255)
  3. Test procedures, check info tab; check for errors and omissions
  4. Write a notes/dev file (for ex, documentation for wrapped functions)
  5. Rough draft of paper

  1. Package:
    1. Write a README file
    2. clean up examples folder
 
  1. package project
Changed:
<
<
  1. write 12 page paper
>
>
  1. Paper:
 
    1. Audience: CS people interested in education.
    2. Abstract: ~400 words. what you did, and why it's interesting (convincing people it's valuable to program).
    3. Introduction: state the problem. give background on the programs/procs you're using. state previous related work (other examples of scripting Inkscape). State how your project is different from these projects.
Line: 31 to 24
  1 Conclusion/future work. 1 References section: Mark Guzdizl Media Computation. MIT paper. 1 look for Wienmann paper.
Added:
>
>
  1. Future Groups:
    1. Write lots of notes/documentation of work for future projects
    2. update wiki
    3. note: fix command to "only open one doc
 
Deleted:
<
<
Next Group can do/low priority:
  1. fix command to "only open one doc"
 

Revision 33
2011-07-25 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

This Week:
  1. wrap all console functions
Changed:
<
<
  1. wrap move inot hshift and vshift; update INFO TAB.
>
>
  1. fix opacity (1-100)
  2. wrap move to hshift and vshift; update INFO TAB.
 
  1. Write lots of notes/documentation of work for future projects
    1. notes on why some functions were wrapped
    2. README explaining package, how to install, and how to build documentation.
Revision 32
2011-07-25 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

This Week:
Changed:
<
<
  1. write build-documentation procedure.
>
>
  1. wrap all console functions
  2. wrap move inot hshift and vshift; update INFO TAB.
 
  1. Write lots of notes/documentation of work for future projects
Added:
>
>
    1. notes on why some functions were wrapped
    2. README explaining package, how to install, and how to build documentation.
 
    1. update wiki procs list/information
  1. make a set of examples for Elizabeth/an "examples" folder
  2. test all functions; make sure everything is working, and present.
Revision 31
2011-07-23 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

This Week:
  1. write build-documentation procedure.
Deleted:
<
<
  1. test/document wrapped change-level procs
  2. fix new scale/skew functions to take degrees.
  3. test new scale/skew function
  4. write get-center procs.
  5. test all functions; make sure everything is working, and present.
  6. Update procs list on wiki?
 
  1. Write lots of notes/documentation of work for future projects
Added:
>
>
    1. update wiki procs list/information
 
  1. make a set of examples for Elizabeth/an "examples" folder
Added:
>
>
  1. test all functions; make sure everything is working, and present.
  2. write get-center procs.
 

Next Week:
Revision 30
2011-07-22 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

This Week:
Changed:
<
<
  1. find shape functions, and documentation for shape functions.
>
>
  1. write build-documentation procedure.
 
  1. test/document wrapped change-level procs
  2. fix new scale/skew functions to take degrees.
  3. test new scale/skew function
  4. write get-center procs.
Changed:
<
<
  1. check that documentation/lbraries are organized/formatted well, and that everything it working.

  1. Format inkscript-documentation
>
>
  1. test all functions; make sure everything is working, and present.
  2. Update procs list on wiki?
  3. Write lots of notes/documentation of work for future projects
  4. make a set of examples for Elizabeth/an "examples" folder
 

Next Week:
Added:
>
>
  1. INFORMATION TAB in console- edit
 
  1. package project
  2. write 12 page paper
    1. Audience: CS people interested in education.
Line: 32 to 33
 
  1. fix command to "only open one doc"
Deleted:
<
<
  1. Update procs list on wiki?
  2. Write lots of notes/documentation of work for future projects
  3. make a set of examples for Elizabeth/an "examples" folder
  4. INFORMATION TAB in console- edit

Revision 29
2011-07-22 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Changed:
<
<
  1. Format inkscript-documentation
>
>
This Week:
 
  1. find shape functions, and documentation for shape functions.
Changed:
<
<
  1. test/document wrapped change-level procs.
>
>
  1. test/document wrapped change-level procs
 
  1. fix new scale/skew functions to take degrees.
Changed:
<
<
  1. test new functions
  2. delete shape/get-center functions; update documentation; make sure that no procs are missing
>
>
  1. test new scale/skew function
  2. write get-center procs.
  3. check that documentation/lbraries are organized/formatted well, and that everything it working.

  1. Format inkscript-documentation

Next Week:
  1. package project
  2. write 12 page paper
    1. Audience: CS people interested in education.
    2. Abstract: ~400 words. what you did, and why it's interesting (convincing people it's valuable to program).
    3. Introduction: state the problem. give background on the programs/procs you're using. state previous related work (other examples of scripting Inkscape). State how your project is different from these projects. 1 Design: ~1 page summery of what you did 1 Why it's good: (i.e. look: you can easily create this cool image. Must directly relate to arg. of the purpose/value of your project.) Examples. 1 Conclusion/future work. 1 References section: Mark Guzdizl Media Computation. MIT paper. 1 look for Wienmann paper.

Next Group can do/low priority:
 
  1. fix command to "only open one doc"
Added:
>
>
 
  1. Update procs list on wiki?
  2. Write lots of notes/documentation of work for future projects
  3. make a set of examples for Elizabeth/an "examples" folder
Line: 16 to 36
 
  1. Write lots of notes/documentation of work for future projects
  2. make a set of examples for Elizabeth/an "examples" folder
  3. INFORMATION TAB in console- edit
Deleted:
<
<
  1. package project
  2. write 12 page paper
 

Revision 28
2011-07-22 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Changed:
<
<
  1. document new scale/skew functions
>
>
  1. Format inkscript-documentation

  1. find shape functions, and documentation for shape functions.
  2. test/document wrapped change-level procs.
  3. fix new scale/skew functions to take degrees.
 
  1. test new functions
Changed:
<
<
  1. delete shape/get-center functions
>
>
  1. delete shape/get-center functions; update documentation; make sure that no procs are missing
 
  1. fix command to "only open one doc"
  2. Update procs list on wiki?
Deleted:
<
<
  1. Make sure that files are documented/formatted nicely
 
  1. Write lots of notes/documentation of work for future projects
  2. make a set of examples for Elizabeth/an "examples" folder
  3. INFORMATION TAB in console- edit
Revision 27
2011-07-21 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Added:
>
>
  1. document new scale/skew functions
  2. test new functions
  3. delete shape/get-center functions
 
  1. fix command to "only open one doc"
Changed:
<
<
  1. Wrap selection functions
    1. update documentation
  2. Rewrite -orig functions
    1. update documentation
>
>
  1. Update procs list on wiki?
 
  1. Make sure that files are documented/formatted nicely
Deleted:
<
<

  1. organize svn folders
 
  1. Write lots of notes/documentation of work for future projects
  2. make a set of examples for Elizabeth/an "examples" folder
Deleted:
<
<
 
  1. INFORMATION TAB in console- edit
Deleted:
<
<
 
  1. package project
  2. write 12 page paper

Revision 26
2011-07-21 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Changed:
<
<
  1. add libraries to console!
  2. wrap selection functions
  3. rename -orig! functions
  4. INFORMATION TAB in console- edit
  5. console -> only open one new document when initialized?
  6. make a set of examples for Elizabeth/an "examples" folder.
>
>
  1. fix command to "only open one doc"
  2. Wrap selection functions
    1. update documentation
  3. Rewrite -orig functions
    1. update documentation

  1. Make sure that files are documented/formatted nicely
 
  1. organize svn folders
Changed:
<
<
  1. make sure files are documented/formatted nicely
>
>
 
  1. Write lots of notes/documentation of work for future projects
Added:
>
>
  1. make a set of examples for Elizabeth/an "examples" folder

  1. INFORMATION TAB in console- edit
 
  1. package project
  2. write 12 page paper

Revision 25
2011-07-21 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

  1. add libraries to console!
Added:
>
>
  1. wrap selection functions
  2. rename -orig! functions
 
  1. INFORMATION TAB in console- edit
  2. console -> only open one new document when initialized?
  3. make a set of examples for Elizabeth/an "examples" folder.
Line: 12 to 14
 
  1. make sure files are documented/formatted nicely
  2. Write lots of notes/documentation of work for future projects
  3. package project
Added:
>
>
  1. write 12 page paper
 

Revision 24
2011-07-20 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

  1. add libraries to console!
Changed:
<
<
  1. write inkscript.c to use a dynamic array
  2. write inkscript-clear and inkscript-close functions
>
>
  1. INFORMATION TAB in console- edit
  2. console -> only open one new document when initialized?
 
  1. make a set of examples for Elizabeth/an "examples" folder.
  2. organize svn folders
  3. make sure files are documented/formatted nicely
Revision 23
2011-07-20 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

  1. add libraries to console!
Changed:
<
<
  1. write console to use a dynamic array
>
>
  1. write inkscript.c to use a dynamic array
 
  1. write inkscript-clear and inkscript-close functions
  2. make a set of examples for Elizabeth/an "examples" folder.
  3. organize svn folders
Revision 22
2011-07-20 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Deleted:
<
<
  1. document and test. Update InkSchemeProcs and add documentation to the scheme library and to inkscript documentation.
    1. get-center functions
    2. object-scale functions
    3. shape functions
 
  1. add libraries to console!
  2. write console to use a dynamic array
  3. write inkscript-clear and inkscript-close functions
Added:
>
>
  1. make a set of examples for Elizabeth/an "examples" folder.
 
  1. organize svn folders
  2. make sure files are documented/formatted nicely
  3. Write lots of notes/documentation of work for future projects
Revision 21
2011-07-19 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List
Changed:
<
<
For Inkscape
  1. email Soren the list of broken dbus methods => InkDbusBroken
  2. write "inkscript-close" " proc to disconnect from dbus and free memory; "inkscript-clear" to re-set the documents array and such.
  3. Keep editing, improving the InkInventory
>
>
  1. document and test. Update InkSchemeProcs and add documentation to the scheme library and to inkscript documentation.
    1. get-center functions
    2. object-scale functions
    3. shape functions
  2. add libraries to console!
  3. write console to use a dynamic array
  4. write inkscript-clear and inkscript-close functions
  5. organize svn folders
  6. make sure files are documented/formatted nicely
  7. Write lots of notes/documentation of work for future projects
  8. package project
 
Deleted:
<
<
Ongoing
  • Prepare for meeting with large CSC group every other Tuesday
  • Blog assignments due every week
 
Deleted:
<
<
Big Picture

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
  • Work w/ Elizabeth on Wednesday
Revision 20
2011-07-02 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
  1. email Soren the list of broken dbus methods => InkDbusBroken
Deleted:
<
<
  1. make the inkscript doc array a dynamic array.
 
  1. write "inkscript-close" " proc to disconnect from dbus and free memory; "inkscript-clear" to re-set the documents array and such.
Deleted:
<
<
  1. make tests for mplti procs for console.c shorter => add loops.
  2. reorganize "console" into different files
  3. figure out how to add wrapper_library to the console
    1. remember to commit to svn
 
  1. Keep editing, improving the InkInventory

Ongoing
Revision 19
2011-06-28 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 8 to 8
 
  1. email Soren the list of broken dbus methods => InkDbusBroken
  2. make the inkscript doc array a dynamic array.
  3. write "inkscript-close" " proc to disconnect from dbus and free memory; "inkscript-clear" to re-set the documents array and such.
Changed:
<
<
  1. make code in "console.c" less ugly.
  2. reorganize "console" into different files?
  3. finish writing Scheme commands from inkscript, start wrapping procedures.
>
>
  1. make tests for mplti procs for console.c shorter => add loops.
  2. reorganize "console" into different files
  3. figure out how to add wrapper_library to the console
 
    1. remember to commit to svn
  1. Keep editing, improving the InkInventory
Revision 18
2011-06-27 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 8 to 8
 
  1. email Soren the list of broken dbus methods => InkDbusBroken
  2. make the inkscript doc array a dynamic array.
  3. write "inkscript-close" " proc to disconnect from dbus and free memory; "inkscript-clear" to re-set the documents array and such.
Changed:
<
<
  1. read up on Racket, learn how to write Scheme wrappers
  2. Start writing Scheme commands!
    1. remember to commit them to svn
>
>
  1. make code in "console.c" less ugly.
  2. reorganize "console" into different files?
  3. finish writing Scheme commands from inkscript, start wrapping procedures.
    1. remember to commit to svn
 
  1. Keep editing, improving the InkInventory

Ongoing
Revision 17
2011-06-22 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 20 to 20
  Big Picture
  • Write C commands to do things in Inkscape => Write Scheme commands to do things in Inkscape
  • Write additional methods for org.inkscape.applications
Added:
>
>
 

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Revision 16
2011-06-22 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

For Inkscape
Changed:
<
<
  • blog due Friday
  • finish writing/test/document C procs
  • addt'l => a dynamic array? an inkscript_close command?
  • email Soren confusing/broken commands
  • Learn for to write Scheme programs that call C programs.
>
>
  1. email Soren the list of broken dbus methods => InkDbusBroken
  2. make the inkscript doc array a dynamic array.
  3. write "inkscript-close" " proc to disconnect from dbus and free memory; "inkscript-clear" to re-set the documents array and such.
  4. read up on Racket, learn how to write Scheme wrappers
  5. Start writing Scheme commands!
    1. remember to commit them to svn
  6. Keep editing, improving the InkInventory
 
Changed:
<
<

  • ONGOING:
>
>
Ongoing
 
    • Prepare for meeting with large CSC group every other Tuesday
    • Blog assignments due every week
Deleted:
<
<
  • PROBS SHOULD DO AT SOME POINT
    • Learn how to use Subversion
    • Read through Inkscape source code
  Big Picture
  • Write C commands to do things in Inkscape => Write Scheme commands to do things in Inkscape
  • Write additional methods for org.inkscape.applications
Revision 15
2011-06-16 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

For Inkscape
Changed:
<
<
  • Prepare for Tuesday talk!
  • Monday/Tuesday- Learn how to write C programs that use GLib (bindings to proxy objects) and dbus to do operations in Inkscape. => Get help from Soren.
  • Learn for to write Scheme programs that use Glib -> after Sam's talk (on Tuesday?)
>
>
  • blog due Friday
  • finish writing/test/document C procs
  • addt'l => a dynamic array? an inkscript_close command?
  • email Soren confusing/broken commands
  • Learn for to write Scheme programs that call C programs.
 

  • ONGOING:
Revision 14
2011-06-13 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

For Inkscape
Added:
>
>
  • Prepare for Tuesday talk!
  • Monday/Tuesday- Learn how to write C programs that use GLib (bindings to proxy objects) and dbus to do operations in Inkscape. => Get help from Soren.
  • Learn for to write Scheme programs that use Glib -> after Sam's talk (on Tuesday?)
 
Deleted:
<
<
  • Blog assignment- due Monday.
  • Monday/Tuesday- Learn how to write C programs that use GLib (bindings to proxy objects) and dbus to do operations in Inkscape. => Get help from Python team and Sam.
  • Be ready to present
 
Changed:
<
<
  • ONGOING- Prepare for meeting with large CSC group every other Tuesday
>
>
  • ONGOING:
    • Prepare for meeting with large CSC group every other Tuesday
    • Blog assignments due every week
 

  • PROBS SHOULD DO AT SOME POINT
    • Learn how to use Subversion
Revision 13
2011-06-13 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 8 to 8
 

  • Blog assignment- due Monday.
  • Monday/Tuesday- Learn how to write C programs that use GLib (bindings to proxy objects) and dbus to do operations in Inkscape. => Get help from Python team and Sam.
Added:
>
>
  • Be ready to present
 

  • ONGOING- Prepare for meeting with large CSC group every other Tuesday
Revision 12
2011-06-10 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
Changed:
<
<
  • DUE FRIDAY
    1. Write a complete inventory of the commands we want to provide- include 6 P's for some.
    2. Learn dbus, be able to explain how dbus interacts with Inkscape
    3. Read through Inkscape source code (learn C++)
>
>
  • Blog assignment- due Monday.
  • Monday/Tuesday- Learn how to write C programs that use GLib (bindings to proxy objects) and dbus to do operations in Inkscape. => Get help from Python team and Sam.
 

  • ONGOING- Prepare for meeting with large CSC group every other Tuesday
Changed:
<
<
  • PROBS SHOULD DO AT SOME POINT- Learn how to use Subversion
>
>
  • PROBS SHOULD DO AT SOME POINT
    • Learn how to use Subversion
    • Read through Inkscape source code

Big Picture
  • Write C commands to do things in Inkscape => Write Scheme commands to do things in Inkscape
  • Write additional methods for org.inkscape.applications
 

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Revision 11
2011-06-09 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
Changed:
<
<
  • DUE TONIGHT- a complete draft of our project proposal.

  • DUE MONDAY- final Project Proposal

  • DUE NEXT FRIDAY
>
>
  • DUE FRIDAY
 
    1. Write a complete inventory of the commands we want to provide- include 6 P's for some.
Added:
>
>
    1. Learn dbus, be able to explain how dbus interacts with Inkscape
 
    1. Read through Inkscape source code (learn C++)
Deleted:
<
<
      1. Prepare explanation of how Python is used in Inkscape source
    1. Keep in touch with Soren, install Inkscape from source
 

  • ONGOING- Prepare for meeting with large CSC group every other Tuesday
Line: 22 to 17
 

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Added:
>
>
  • Work w/ Elizabeth on Wednesday
Revision 10
2011-06-03 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
Changed:
<
<
  • DUE TODAY- prepare compelling examples
  • DUE TONIGHT- a better draft proposal, all scholarly and such
  • DUE THIS WEEK- Start looking at the Inkscape source code
    • Teach yourself C++
  • DUE NEXT WEEK- final Project Proposal
  • DUE NEXT WEEK- Prepare explanation of how Python is used in Inkscape source
  • DUE w/in the week-lower priority
    • Get resources for our Project:
      • Find useful scholarly works about programming for vector graphics
      • Read through articles from 2007 Inkscape project.
    • Think about what commands we will make possible in our console-> make a list
  • PROBS SHOULD HAVE DONE ALREADY-
    • Learn how to use Subversion
    • Learn SVG
    • Learn Inkscape commands
  • ONGOING-
    • Prepare for meeting with large CSC group every other Tuesday
>
>
  • DUE TONIGHT- a complete draft of our project proposal.

  • DUE MONDAY- final Project Proposal

  • DUE NEXT FRIDAY
    1. Write a complete inventory of the commands we want to provide- include 6 P's for some.
    2. Read through Inkscape source code (learn C++)
      1. Prepare explanation of how Python is used in Inkscape source
    3. Keep in touch with Soren, install Inkscape from source

  • ONGOING- Prepare for meeting with large CSC group every other Tuesday

  • PROBS SHOULD DO AT SOME POINT- Learn how to use Subversion
 

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Deleted:
<
<
  • Think about when you want to meet with Elizabeth to work on Ill. Examples.

For Downloading GIMP from source
  • PUT ON HIATUS
Revision 9
2011-06-02 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
Changed:
<
<
  • DUE TOMORROW- prepare compelling examples
>
>
  • DUE TODAY- prepare compelling examples
  • DUE TONIGHT- a better draft proposal, all scholarly and such
 
  • DUE THIS WEEK- Start looking at the Inkscape source code
    • Teach yourself C++
Changed:
<
<
  • DUE NEXT WEEK- rewritten Project Proposal
>
>
  • DUE NEXT WEEK- final Project Proposal
 
  • DUE NEXT WEEK- Prepare explanation of how Python is used in Inkscape source
  • DUE w/in the week-lower priority
    • Get resources for our Project:
Revision 8
2011-06-01 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 6 to 6
 

For Inkscape
Deleted:
<
<
  • DUE TODAY- Project proposal.
    • Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
 
  • DUE TOMORROW- prepare compelling examples
  • DUE THIS WEEK- Start looking at the Inkscape source code
    • Teach yourself C++
Added:
>
>
  • DUE NEXT WEEK- rewritten Project Proposal
 
  • DUE NEXT WEEK- Prepare explanation of how Python is used in Inkscape source
  • DUE w/in the week-lower priority
    • Get resources for our Project:
Revision 7
2011-06-01 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

For Inkscape
Changed:
<
<
  • Things due soon:
>
>

  • DUE TODAY- Project proposal.
 
    • Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
Changed:
<
<
  • Start reading through Inkscape source code
>
>
  • DUE TOMORROW- prepare compelling examples
  • DUE THIS WEEK- Start looking at the Inkscape source code
    • Teach yourself C++
  • DUE NEXT WEEK- Prepare explanation of how Python is used in Inkscape source
  • DUE w/in the week-lower priority
 
  • Get resources for our Project:
    • Find useful scholarly works about programming for vector graphics
    • Read through articles from 2007 Inkscape project.
Changed:
<
<
    • email Soren
    • Check out Scheme-Draw (MIT) -> Once Sam gets back to us.
  • Learn the tools:
>
>
    • Think about what commands we will make possible in our console-> make a list
  • PROBS SHOULD HAVE DONE ALREADY-
    • Learn how to use Subversion
 
    • Learn SVG
Deleted:
<
<
      • Read through tutoiral/examples on w3school.com
 
    • Learn Inkscape commands
Changed:
<
<
  • Project Itself:
    • Think about what commands we will make possible in our console-> make a list

General Tasks
  • Prepare for meeting with large CSC group on Tuesday- 5 mins per group: what you're doing for the summer and why.
  • Every other Tuesday: 15 min. presentation of project to other CSC groups.
  • Study Subversion
  • Learn about automake, gtk+ objects, Media-Scheme source (Sam will lecture on topics)

For Downloading GIMP from source (Kate)
>
>
  • ONGOING-
    • Prepare for meeting with large CSC group every other Tuesday
 

For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Added:
>
>
  • Think about when you want to meet with Elizabeth to work on Ill. Examples.

For Downloading GIMP from source
  • PUT ON HIATUS
Revision 6
2011-06-01 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 7 to 7
  For Inkscape
  • Things due soon:
    • Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
Added:
>
>
  • Start reading through Inkscape source code
 
  • Get resources for our Project:
    • Find useful scholarly works about programming for vector graphics
    • Read through articles from 2007 Inkscape project.
Revision 5
2011-05-27 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26

To Do List

For Inkscape
Changed:
<
<
  • Find useful scholarly works about programming for vector graphics; Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
  • Check out Scheme-Draw (MIT)
  • DUE FRIDAY: be ready to teach Inkscape, and a little SVG to the group
  • Learn SVG standard
>
>
  • Things due soon:
    • Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
  • Get resources for our Project:
    • Find useful scholarly works about programming for vector graphics
    • Read through articles from 2007 Inkscape project.
    • email Soren
    • Check out Scheme-Draw (MIT) -> Once Sam gets back to us.
  • Learn the tools:
    • Learn SVG
      • Read through tutoiral/examples on w3school.com
    • Learn Inkscape commands
  • Project Itself:
    • Think about what commands we will make possible in our console-> make a list
  General Tasks
  • Prepare for meeting with large CSC group on Tuesday- 5 mins per group: what you're doing for the summer and why.
  • Every other Tuesday: 15 min. presentation of project to other CSC groups.
Line: 14 to 25
 
  • Every other Tuesday: 15 min. presentation of project to other CSC groups.
  • Study Subversion
  • Learn about automake, gtk+ objects, Media-Scheme source (Sam will lecture on topics)
Added:
>
>
  For Downloading GIMP from source (Kate)
Added:
>
>
  • PUT THIS ON HIATUS until I know who else is working on this with me, can tt them and work on it together.
 
Changed:
<
<
  • tt rebelsky about error while installing
>
>
  • tt rebelsky about error while installing
  For Helping Other Groups
  • Think about what you could cut from csc 151 for a week to learn python
Deleted:
<
<
Revision 4
2011-05-27 - Main.KimSpasaro
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Revision 3
2011-05-26 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 5 to 5
  To Do List

For Inkscape
Deleted:
<
<
  * Find useful scholarly works about programming for vector graphics; Write 1/2 page/1 page SS project description. Include a motivating example. Think about how this would be used in the classroom.
Changed:
<
<
>
>
  • Check out Scheme-Draw (MIT)
  • DUE FRIDAY: be ready to teach Inkscape, and a little SVG to the group
  * Learn SVG standard
Deleted:
<
<
  General Tasks
Changed:
<
<

* Every other Thursday: 15 min. presentation of project to other CSC groups.

* Study how to learn Subversion
>
>
  • Prepare for meeting with large CSC group on Tuesday- 5 mins per group: what you're doing for the summer and why.
  • Every other Tuesday: 15 min. presentation of project to other CSC groups.
  • Study Subversion
  * Learn about automake, gtk+ objects, Media-Scheme source (Sam will lecture on topics)
Deleted:
<
<
  For Downloading GIMP from source (Kate)
Deleted:
<
<
  * follow instruction from http://darwingimp.sourceforge.net/buildgimp.html
Changed:
<
<

* tt rebelsky about error while installing
>
>
  • tt rebelsky about error while installing
  For Helping Other Groups
Deleted:
<
<
  * Think about what you could cut from csc 151 for a week to learn python
Changed:
<
<


>
>
Revision 2
2011-05-26 - Main.KateIngersoll
Line: 1 to 1
 
META TOPICPARENT name="DailyNotesInkscape"
-- KateIngersoll - 2011-05-26
Line: 16 to 16
 

* Study how to learn Subversion
Changed:
<
<
* Learn about automake, gtk+ objects, MediaSchem source (Sam will lecture on topics)
>
>
* Learn about automake, gtk+ objects, Media-Scheme source (Sam will lecture on topics)
 

For Downloading GIMP from source (Kate)
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback