Summary: | multi-file datawizard for datafile comparison | ||
---|---|---|---|
Product: | [Applications] kst | Reporter: | Nicolas Brisset <nicolas.brisset> |
Component: | general | Assignee: | kst |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | netterfield, syntheticpp |
Priority: | NOR | ||
Version: | 1.10.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Nicolas Brisset
2006-04-05 00:37:05 UTC
I'm wondering if you might end up being happier writing and using a small javascript for this.... once it is written, you would type 'addCurve("19")' to add plots of field 19. I wrote a brief tutorial which is in graphics/doc/kst/scripttutorial which should get you on your way. My worry, as a general one, is that we run the risk of making the UI infinitely complicated, as we add the capability for each new work case, so in the end, it isn't useful for any work case. Some might argue that the current wizard is already heading in that direction. Exactly. This is what scripting and extensions are for. I am not againts scripting or extensions, all the more as integrating this cleanly in the wizard is not very simple (even though my report is long because I tried to list all issues, I am not sure it is a good measure of code complexity, and the UI would not be affected tremendously). But in any case I'm looking for a solution to the above use case (adding a new vector from a number of sources simultaneously very easily) and I definitely don't think we can ask end users to write scripts. They should be offered a point-and-click GUI for such a fairly simple and frequent task. Another option may be to not add this to the wizard, but rather to a new tool with just the minimum amount of information (no PSDs, just datasources to read from in a checklist, field name(s), from/to values, and destination (new plot, new window, etc...) I'm tempted to close that bug as a duplicate of bug #136780. What do you think ? At some point it was said that this would be a good testcase for scripting extensions, but it seems nobody got around to doing it and I believe the proposal made in #136780 is better implemented in C++ (but I may be wrong)... and covers this need completely. Could be still open in Kst 1. Does the duplicate option in the change file dialog solve this problem? If so, is it ok to close this? The duplicate option in the change file dialog does not completely solve this, but almost. The thing is, you'd need to call the change data file tool over and again and select the last vectors added only, instead of having all curves added at once. I think the idea from this report is still nice, but we can live a while without it. It's not high priority, but I would not close it. As already mentioned, we could start by implementing bug #136780, which is also nice and probably easier. And when we have enough hands to work on kst (someday hopefully), integrating those ideas into the wizard could be a nice addition. It does not make it so much more complicated, and makes the feature easier to use and more visible to new users. |