Sigasi HDT 1.0 feature missing in Sigasi 2.0
Sigasi 2.0 is a complete rewrite of Sigasi HDT 1.0. We put a lot of effort in the new core which enabled instantaneous interactivity. Your code is now analyzed while you type. This results in type time problem reporting, navigation in and context sensitive auto-complete.
Some features of Sigasi HDT 1.0 have not been ported to Sigasi 2.0 yet however. Some features are not ported yet because we simply did not have the time yet (Eg. documentation,…) . Others however are still 1.0 only, because we are still brainstorming on better ways to implement them. We are experimenting with new user interfaces to enhance your VHDL design experience. We also consider dropping some little-used features.
This page keeps track of the status of each of these features. Feel free to comment to add extra priority to porting your favorite to 2.0. You can discuss completely new features (not from Sigasi HDT 1.0) on the user forum.
External tools Integration
- ISim
- ModelSim
- CSV file builder
- Makefiles
Linting
- Sensitivity list problems
- Unused Signals/Constants/Variables
- Association Style
- Instantiation style
QuickFixes
- Declare signal
- Fix Sensitivity list
- Remove unused declaration
Refactoring
- Add Generic / Port
- Encapsulate concurrent statements
Elaboration
- Hierarchy view
- Open Matching entity (navigation)
- Rename: coupling component and entity declarations
Other
- Add extra plugins to standalone version (Mousefeed, Subversion)
- Fix Case (fontify)
Comments
Is this list still
Is this list still up-to-date? It seems like some of the features should be available for proper exploitation of Sigasi anyway. For instance the external tools integration.
Hi Rob, Thanks for the
Hi ARob,
Thanks for the poke. I have updated the list.
Integration with external tools is not scheduled yet.
In the mean time, you can use the generic Eclipse External tools mechanism to run external tools from within Sigasi.
Kind regards,
Hendrik
It would be nice to see the
It would be nice to see the add generic/port feature implemented in Sigasi 2.0. It would be great if in addition to adding ports/generics it would be possible to delete them.
Martin
planning for re-introducing these features
Hi
Could you give us a (preliminary) timeline / plan when these features are re-introduced in sigasi 2.0
People are now disappointed when they first use sigasi 2.0 and see all the nice features from 1.x stripped in 2.x
Now 2.x is more like notepad++ with only a code checking as you type feature and a more difficult library mapping system,
all interesting things are gone (hierarchy / refactoring)
ModelSim integration
Hi sigasi team,
ModelSim integration is essential for me to switch over so 2.0.
Without ModelSim integration design speedup drops significantly!
Josef
Signal Path Analyzer
In addition to a hierarchy viewer, it would be nice to have a signal viewer -- where does a signal go throughout a design and is it renamed via port maps or assignment statements along the way.
Generic/Constant analyzer
Many constants and generics are inherited trough a lot of levels or calculated by functions. In larger designs one loses track of the actual value of these. If one could get to see the actual value with the current (high level)defined generics while typing code it would help a lot!