Recent changes to development-plan

#5 Add point groups to the GUI

2013-07-29T17:59:02.094000Z

status: open --> closed-fixed
Group: --> Box_0.3.3,_Boxer_0.3.7

#10 Extend Undo/Redo to reference points

2013-05-11T17:57:28.572000Z

status: open --> closed-fixed
Group: --> Box_0.3.3,_Boxer_0.3.7

#3 Rewrite Box type system and merge it with runtime

2012-12-19T21:58:49.652000Z

status: open --> closed-fixed
milestone: --> Box_0.3.3,_Boxer_0.3.7

Ideas for the documentation system and browser

2012-06-24T15:12:43Z

\- The documentation system should allow specifying some code-snippets, which can be pasted - using the documentation browser - into the current document. During paste the documentation browser should expand macros like \(\*\*dox-new-point: \(1.23, 4.56\), "description"\*\) in a convenient way. In this particular case, the point should be added and its name should be used to expand the macro. As a further extension, Boxer may decide to interact with the user, tell him/here that the selected object requires one point to be created and ask him/her to create it. This could provide a very powerful way to extend the Boxer GUI. This would be nicer if Boxer could analyse the code, see where the cursor is, understand whether we are inside a box construct which allows the given object to be used. If this is the case then the object can be simply pasted \(e.g. "Object\[...\]"\), otherwise a variable should be created \(e.g. "object1 = Object\[...\]"\) or the object should be ignored \(e.g. "\ Object\[...\]"\). \- The documentation system should allow to specify, for the object which is being documented, some code snippets which provide an example of usage. These examples should be shown in the documentation browser. \- The documentation browser should be able to show information about errors in parsing the documentation. \- The documentation browser should allow inspecting the source code which defines the selected object.

Add preview to the documentation browser

2012-06-24T15:00:56Z

The documentation system should allow to specify some code to generate a preview which will be shown by the documentation browser when selecting corresponding entries. This is the first step to allow users to have a quick visual representation of what object do. We should reuse the box view area which is used in the main Boxer window. We should also allow zooming in/out/off.

Extend Undo/Redo to reference points

2012-04-09T20:18:28Z

Actions such as creating/moving/removing a reference point should enter the undo/redo list. Investigate whether it is possible to include reference points in the source as objects \(and not text\) which are atomic.

Extend Undo/Redo to reference points

2012-04-09T20:18:28Z

Ticket 10 has been modified: Extend Undo/Redo to reference points
Edited By: Matteo Franchin (fnch)
Status updated: u'open' => u'closed-fixed'
_milestone updated: '' => u'Box_0.3.3,_Boxer_0.3.7'

Bug: Figure.Save cannot be used

2012-04-09T18:47:51Z

See title. This is a more generic language concern. If Z is defined as Z = X then, even if X.Y exists, Z.Y cannot be used.

Allow recursive sections in Dox documentation

2012-04-08T18:20:06Z

We should change Dox so that recursive sections are possible in the documentation \(at the moment Sections are flat, can only contain Types\). This way we will be able to create a nice tree of code snippets and examples. The documentation browser should be updated accordingly. It should display the tree of sections and should allow searching the tree.

Box state machine to handle If, etc.

2012-04-08T11:39:28Z

Add machine state to handle different types of Box constructs. For example \[If\[...\], ..., Elif\[...\], ..., Else, ...\] or \[While\[...\], ...\]. Make sure variable handling is consistent.