Commit by etdsoft :: r2585 /server/branches/experimental/2008-06_rails2.0-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2584 /server/branches/experimental/2009-06_refactorNodesTree-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2583 /server/branches/experimental/2009-06_refactorWordExport-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2582 /server/branches/experimental/2009-06_refactorWordExport_customfields-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2581 /server/branches/experimental/2009-10_ExtJS30-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2580 /server/branches/experimental/2009-12_rails2.3.5-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2579 /server/branches/experimental/2010-01_RedCloth_Editor-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2578 /server/branches/experimental/2010-10_rails3-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2577 /server/branches/experimental/2010-12_wintercode/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2576 /server/branches/experimental/2011-02_metasploit/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2575 /server/branches/experimental/2011-03_new-plugins/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2574 /server/branches/experimental/2011-04_extjs4-etd/: (link)

There is no need for this (or any) experimental branch to remain live after the concepts/tests that were tried have been merged or discarded

Commit by etdsoft :: r2573 /meta/trunk/ (reset.sh start.sh): (link)

It makes more sense to let Bundler run these commands as the PATH will be set automagically

Commit by etdsoft :: r2572 /meta/ (3 files in 3 dirs): (link)

Starting in Dradis 2.7 we are using Thor instead of Rake for the setup/reset tasks. This was spotted while building the packages (after the branch and tag were created)

Commit by etdsoft :: r2571 /server/trunk/ (2 files in 2 dirs): (link)

Add a few styles to the note header and footer

Commit by etdsoft :: r2570 /server/trunk/ (3 files in 2 dirs): (link)

Create a new @notes/summary@ partial to display each notes in the list of all the notes associated with a node.

Add some raw styles at least to see each note in a separate block.

Commit by etdsoft :: r2569 /server/trunk/ (3 files in 3 dirs): (link)

• Every time a node is clicked, load the /nodes/<id>/notes view (notes#index) from the server.
• In @NotesController@ allow requests in HTML format
• Create a simple view that at least shows the list of available notes

Commit by etdsoft :: r2568 /server/trunk/public/javascripts/interface.js: (link)

Instead of killing the old insterface and start from scratch or creating a brand
new layout we can start by creating a new tab that will display the notes in a
more pure HTML + CSS way as opposed to the current 'grid + preview' view.o

I have also updated the @nodeclick@ event handler to update the contents of the
new tab. Ideally this will invoke the REST /nodes/<id>/notes route to pull a
standard Rails view from the server.

Commit by etdsoft :: r2567 /server/trunk/public/javascripts/nodestree.js: (link)

When changing the node type, make a local change so the icon is updated before sending the Ajax request to persist the change in the DB

Commit by etdsoft :: r2566 /server/trunk/public/javascripts/nodestree.js: (link)

When loading the tree, use different icon classess (@iconCls@) for different node types