Open epsi1on opened 4 years ago
EDIT: removed task list.
You can either remove Milestone 3 or add some specific tasks (one addition - with rather low priority - could be to inspect the TODO
s scattered across the projects).
I think you should put the heading Plan towards BriefFiniteElementNet
version 2 and a nuget release back in place (or change the title of the issue). All the tasks should be addressed before publishing a final nuget package. Of course you can publish prerelease packages - as you might have noticed, I added <Version>2.0.0-pre</Version>
when converting the project files. The pre
means nuget will handle it as a prerelease.
Maybe need to make a new project with title Plan towards BriefFiniteElementNet version 2 and a nuget release? First we should address stuff that need to be done before release nuget package...
I rather to move obsolete classes into another namespace, and remove them in next version, what you think about it? For integration tests, you mean it should be automatically tested by visual studio? currently it is a console application...
I rather to move obsolete classes into another namespace, and remove them in next version, what you think about it?
If you think that the obsolete code is still widely used, that would be a fair compromise. Alternatively, you could add another project BriefFiniteElementNet.Compatibility
, which could even be distributed via nuget, if anybody feels the need.
For integration tests, you mean it should be automatically tested by visual studio? currently it is a console application...
If I'm correct, at the moment it's a loose collection of tests, which must be run manually. Just add a class TestRunner
(or the like) which calls all those tests and gives a hint if anything doesn't work as expected. I will start working on the Matrix
class, once we have this.
Hi,
I'm going through the todo-list and I noticed item "complete TriangleElement codes that support all 3 types of loads.": https://github.com/BriefFiniteElementNet/BriefFiniteElement.Net/projects/4#card-44141482. What do you mean with all 3 types of loads?
There are 3 type of elemental loads, Uniform, Concentrated and PartialNonUniform. I think currently only uniform load is supported by triangle element.
At least IElementHelper.GetLocalEquivalentNodalLoads()
method should be implemented for both DkqHelper
and CstHelper
and the code should support ConcentratedLoad
and PartialNonUniformLoad
.
EDIT:
Milestone 1
BriefFiniteElementNet
/BriefFiniteElementNet.Common
Obsolete
attribute.Milestone 2
BriefFiniteElementNet
/BriefFiniteElementNet.Common
BriefFiniteElementNet.Validation
BriefFiniteElementNet.Controls
dependencyMilestone 3
BriefFiniteElementNet
/BriefFiniteElementNet.Common
BriefFiniteElementNet.Validation
[ ] fix TODO items
discussion continued from comment number 673732028 of #36 (link)
I've used
[Obsolete()]
attribute for both deprecated codes and new codes which are under development and not tested yet. As you stated, I'm also waiting to get an stable version then publish that version in nuget.org.You mean XML documentation for methods and fields and property ?
Thanks