feedback on changes in tradelink

[josh franta]

Here are two things being considered, please let us know your opinions on them :

1. Consolidate of dlls and namespaces in tradelink

We're considering dumping at least some of the multiple libraries in
tradelink. This would eliminate some typing and dll inclusion.

Eg, instead of

TradeLink.API
TradeLink.AppKit
TradeLink.Research
TradeLink.Common

we might throw Common and Research into TradeLink.Framework.

We're also trying to figure out if there are any advantages to keeping
API seperate, or keeping AppKit seperate.

Please let us know your thoughts.

2. Getting rid of tradelink-contribute group, and just allowing
everything to be discussed on tradelink-users.

-josh

[Greg Jessup]

In favor of both.

--
You received this message because you are subscribed to the Google Groups "tradelink-contribute" group.
To post to this group, send email to tradelink-...@googlegroups.com.
To unsubscribe from this group, send email to tradelink-contri...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tradelink-contribute?hl=en.

[josh franta]

for Framework, you think everything-in-one approach is deseriable?

this will increase the size of an application from say 250KB using
API/Common, to around 1MB when you include research and AppKit

[Greg Jessup]

I prefer all in one at least combining common and api. I really don't thing the size of the app makes too big a difference these days. I can't see portability being that big of a deal, and can't imagine it would slow anything down.

Sorry for being so MIA the past few weeks. Had some other stuff to deal with at my real job :)

[josh franta]

I think we'll combine api/common/research into one. We'll probably
create one or more of those folders you like and put the api stuff in
there. Folders have no affect on namespace, correct? Research
we'll probably just get rid of.

Appkit we could merge in but put it in it's own folder, just to keep
all the GUI stuff from cluttering up average persons experience.

here is a ticket for the work :
http://code.google.com/p/tradelink/issues/detail?id=515

greg.... looking forward to that TD connector and some of the other
stuff brewing in your branch.

-josh

[Greg Jessup]

Folders don't affect namespace. However....when you are in visual studio and go into folder and "Add Class" It will default the namespace to "Namespace.Folder", and so you would have to make the change to Namespace. That is a minor technicality in my opinion as additions are less common than just code changes...just an FYI.

Could go either way with appKit. I haven't dabbled to much with it yet, so can't comment, whether it would affect developers much.

[josh franta]

ok, probably just create in the root project and then drop to new
folder, should solve that.