10:32 a.m.
My first and simplest thought for this is just to allow people to clear
markers and not regenerate the file. Markers may subsequently reappear if
Windup is run on the app again. I think that regenerating and re-running
all of windup on each file-save would be too performance prohibitive.
This is really a feature that we need to implement as part of a more
incremental process of analysis, e.g. to support something like a web-app
where you can "explore" the app file-by-file after the initial core
analysis has been completed the first time. The ETA for this is not soon,
unfortunately.
Thoughts?
~Lincoln
On Mon, Apr 27, 2015 at 8:31 AM, Ian Tewksbury <itewk(a)redhat.com> wrote:
All,
With old Windup 1.0 there was a way to regenerate the hints for a single
file. Do to the redesign of Windup 2.0 I understand this is currently not
possible, and doing so is an undertaking no one has attempted yet, so in
the mean time I have a quandary of what to do.
Typically in eclipse when you edit a file you re-generate the validation
markers for that file, so if you fix a validation marker it doesn't still
show as busted. Currently without being able to regenerate the hints for a
specific file I am unsure what the best option is.
Options I can think of are:
1. do nothing, and just allow stale validation markers to sit on the
file even if they have been addressed
2. regenerate the entire windup graph every time a file is edited
1. could do this just on save rather then on every character type
2. how expensive is it to generate the graph? Are there any
statistics?
3. Once a file is changed mark all the windup markers as stale with
a message that the graph needs to be regenerated to update them
4. Simply remove all windup markers from the edited file until such
time as the graph is regenerated
It used to be that my validator would auto run windup on a project as soon
as the validation kicked off. Currently the validator has been changed such
that if windup has not been run it simply does not report any windup hints.
Any thoughts on adding back the bit to at least run windup the first time
when validation first kicks off? Right now the user doesn't have any way of
knowing that the only reason they are not seeing windup validation markers
is they have not manually generated a report. In the old plugin design the
generation of an HTML report and the validaton markers were two different
actions. It is rather an Eclipse anti practice to have to invoke a
secondary menu action, "Windup Generate Report" in this case, to then allow
a validator to run correctly.
Blue Skies,
~Ian
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."