-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cleanup Component::save and ::load #383
Conversation
Merging of this PR could be considered only after release, because it concerns core qucs-gui classes concept. As far I can understand you moved |
read my patch. i clearly state, that this is a transitional commit, and that schematic serialization is meant to be implemented as part of a class derived from i do not see your problem, with a concept. there is absolutely no concept for multiple ways of dumping the schematic, exept some stale preprocessor directives related to (please either let me do the cleanup or propose a better way, we had that.) |
842bf40
to
f14e475
Compare
a Component (which is actually a symbol) is not language dependent, hence it must not implement "save". code now stashed in Schematic::saveComponent. will later move to an instance of virtual void SchematicSerializer::saveComponent.
A Component is language independent, hence it is the wrong class to host "load" (which is language dependent). this is a no-op. staging for inclusion into a SchematicParser.
another cleanup done... |
b11de35
to
d41ed81
Compare
ready for go ('develop')... |
"dont use strings to identify components"
please merge (into develop). this is required as a basis for proper symbol attributes, and loadable symbol support. |
Looks good to me. Merging. |
this is a no-op in preparation of