Topic: AutoCAD Extension Framework

[Jeff H]

Hey guys,
 
Before I spend the time which would not be too much, I wanted to check if you guys would be interested first.
 
Was checking if guys would want to advise, contribute, or test with some libraries that would make common task easier and save some lines of code.
 
I could start off with posting the complete libraries I have built and I do not mind sharing, but I think it would be too much and not implemented the way it should for community use.
 
I was thinking it would be better to start off with a simple small solution just to act as placeholder for getting everything setup.
The solution is definitely not meant to be a starting point because I think it needs to discussed how to structure the solution, naming conventions, defined rules, etc......
 
I know this is vague, but I think we can come up with something useful that would help with common task.
If you want a example I will just use the last thing I added which was functionality for basically getting, setting, exporting, importing all the searchpaths on the files tab in options, to treat them like profiles without all the other crap. It uses DLR so other than requiring 4.0 it is not dependent on AcadApplication version, and for settings with multiple paths you treat them as a collection instead of string separated with ";", and had functionality for "temporary or project" paths which would add and remove "extra paths". That seems like something that would be useful but maybe not.
 
If you guys are interested then I will place project on GitHub and will be private, but will add anyone who wants to join, and of course will out updates here.
 
So you guys down?

[Keith Brown]

Was checking if guys would want to advise, contribute, or test with some libraries that would make common task easier and save some lines of code.

I could definitely test and possibly contribute.  I am not sure how much a beginner can contribute but I would give it my best shot.  I left the advise portion out for obvious reasons.

[WILL HATCH]

I'm down!

[mohnston]

I'll do what I can. I have some block attribute and dynamic block setting code that might be of interest.

This isn't going to be written in F# is it?

Just kidding. I'll take what I can get.

[BlackBox]

Jeff,

This is incredibly kind of you to offer/suggest. I'd very much appreciate an opportunity to test what is shared, contribute where I can, and learn a great deal while I'm at it, frankly.

Cheers :beer:

[MexicanCustard]

Im in!

[Jeff H]

Great!
 
Been busy as hell, and drunk all memorial day weekend but got GitHub, etc... setup and will get startup post posted soon.

[bargool]

I'm in again!

[Jeff H]

Finally got a little something together that is to just get discussion started.
Do you think I should load it here or do you guys want to get through GitHub?
 

[WILL HATCH]

Probably get more attention here.

[bargool]

Do you think I should load it here or do you guys want to get through GitHub?

Probably get more attention here.

I think that GitHub is much-much better for developing with all this commits, pull requests, issue/bug trackers, branches e.t.c., than forum. And this forum is good for discussion, ideas and information about framework.

[sybold]

github works great for bug tracking, and tracking changes.

[dgorsman]

Providing separate forks for C# and VB?

[MP]

Forkin' eh.

[Jeff H]

Providing separate forks for C# and VB?

Most use C#, but if anyones want to do whole assembly in VB fine by me.
 
Marking the assemblies  CLSCompliant.
 
 

[Jeff H]

I hope everyone understands I do not have the final decision on anything and is up to you guys,
and if more 50% vote to kick me out then I gone.
 

[Keith Brown]

I am new to GitHub so before I get started I do have a couple of questions.  Are we going to use this board for discussion? or is there a built in bulletin board in gitHub that can be used?  Additionally I think it would be great to agree on a format before getting to deep.  For instance, a command name structure would be good.  As an example, in the sample code shown so far there are commands such as PrintBlock, PrintGroup, etc.  My thoughts on that would be to change the name to BlockPrint, GroupPrint, etc.  That way we could define a command called Block <prefixed with a universal project prefix> that would give options such as <Print Insert Option3 Option4 Option5> etc.  That is just one idea and I am certainly open for any others.  I think it would be best if we came to an agreement before going any further.
Also I think someone should invite Gile to the party so we can use his excellent geometry extensions!

[Jeff H]

Hi Keith,
 
There is a built-in wiki, issues, etc.... in github. I agree that a format needs to be setup starting of with the structure of the solution, etc...
 
I am not too worried about the commands names slapped together in the samples because I can not see any reason for it to contain any commands.
 
A consistent naming convention for parameters, methods, etc... is important and hopefully if it starts to gain more traction then the more input and ideas to toss around.
 
Right now I was thinking of people just slapping together ideas and what the best plan of attack would be.
Should we wrap certain objects or use extension methods, the GroupDictionary in PrintGroups will fall flat on its face if IncludingErased property is called. It can be fixed.
What I posted was one of fifty different ways I thought about doing it.
 
It would be much easier verbally and visually to express ideas I know it is for me.
 
There so many things could do and so many different ways of doing them.
We could start off with a coming up with small set of decisions and actions that need to be made to get project started.
 
 
I had same thought if it gained a little steam to ask gile if he wanted to incorporate his geometry extensions.
 
 

[BlackBox]

Regarding the idea of gile's extension methods... Doesn't TheSwamp have a plethora of threads dedicated to various extension methods, etc? Why not strt the by organizing those into a single/layered structure of library code accessible in at least 2010 and 2013 database format projects (as applicable)? This would help to organize some conten already here at TheSwamp, and remove a lot of the initial creative thought, and allow us to focus on those more important aspects, such as naming conventions, etc, which could then support all the creative thought thrown at it.