I have created a SoapBox Core add-in that I think would be generally useful to the SoapBox Core community and I would like to share it. Is what's the best way for me to put my add-in out there so that other people will find it and use it?

asked 19 Oct '10, 22:33

KarlB's gravatar image

accept rate: 0%

edited 31 Oct '10, 20:11

Mark%20Phipps's gravatar image

Mark Phipps ♦♦

I've removed the feature-request tag, as I think this needs to be merged in with the Add-in manager feature.

(21 Oct '10, 20:39) Scott Whitlock ♦♦

To my knowledge, there is no established repository for add-ins. Though you could always create a codeprojects article on whatever add-in you’ve created and share your work with the broader community that way. You might even drum up some good PR for the project while you’re at it.

What I think would be really cool is if there were a proverbial ‘SoapBox Add-in App Store’ type of things where people could write add-ins and share them with the SoapBox Core community. Of course all add-ins posted there would be under the same general license as SoapBox Core itself and so they would all be free, unlike the app stores.

This type of communal resource is important because there are a lot of ideas out there, like undo/redo functionality, user configuration setup and management, that may not truly belong in SoapBox CORE, but are still generally useful and could benefit other developers. By not adding these types of things to the core, we would be depriving each other of mutual benefits. However, by adding too much stuff to the core we will increase the complexity of the core and hence the overhead associated with learning and using it.

What do you guys think of this idea? I really like it, but I have no idea how to create, manage or host such a beast. If you like the idea and think you know how to actually create such a thing, please leave a comment. I would love you talk to you and try to implement your good idea with you.


answered 19 Oct '10, 22:36

KarlB's gravatar image

accept rate: 0%

This could possibly be merged with the add-in manager feature-request.

(21 Oct '10, 13:03) Scott Whitlock ♦♦

My original question was supposed to be more about sharing the source code for add-ins not just the binaries. Though I really like Scott's ideas for sharing binaries. I'm sorry if I was unclear about that.

Take for example Lee's implementation for dynamically changing skins/themes. There is no easy way for him to share that add-in with the community if he wanted to. As I mentioned previously, he could write a codeproject article, but that could start to de-centralize the information on what is available in SBC.

Can we create a way for sharing add-in source code to the SBC website?

(28 Oct '10, 17:47) KarlB

What if I created a partitioned area on the svn.soapboxcore.com/svn for each user that wanted to do this? Then you could maintain your own add-in source code in that area?

(29 Oct '10, 05:41) Scott Whitlock ♦♦

That sounds great great to me, as long as it doesn't cause too much work for you and it doesn't take up too much space. What does everyone eles think? Is this something that other people would really contribute to? Thanks alot.

(29 Oct '10, 11:19) KarlB

Alternatively, we could always create a repository just for add-ins. Big picture, how are the add-ins going to be marketed/promoted to those who might be interested in them? Knowing this would help us find the "proper" place for the add-ins.

(29 Oct '10, 12:24) Mark Phipps ♦♦

@Mark Phipps: I think each add-in has to stand on its own (note that add-ins can themselves have add-ins though...). Personally I really like the idea of an "add-in marketplace" where users could create a "home page" for their add-in, it offered source control, bug tracking, support pages, etc. Of course there are already lots of sites that do similar things in general (sourceforge, etc.). You're the web guy. :) Can we do something like that?

(29 Oct '10, 18:45) Scott Whitlock ♦♦

Yes, it could be done but other sites do this as well. What's the value added that we could offer over sites like souceforge? I believe we should have a site where contributors can show off their creations and elicit feedback from the community. Perhaps with some sort or "voting" system (similar to this site). What does the community desire?

(30 Oct '10, 00:27) Mark Phipps ♦♦

@Scott, KarlB: Let's try moving forward with Scott's approach as a first step ; we can evaluate and adjust later as necessary.

(30 Oct '10, 21:57) Mark Phipps ♦♦

Did anyone ever come up with a repository for plugins? More specifically I would like to see a broader breadth of plugin examples. Specifically, a simple datagrid that binds to a data source (XML Data). A typical simple form plugin that captures user data and persists it to the XML data and triggers a rebind in the datagrid plugin.

These are simple app needs.

If possible a plugin that loads a RDLC report and binds it to a data source and presents the report in a RDLC view component inside the plugin.

What do you folks think about those ideas?

(03 Dec '10, 10:27) KenCrismon

@KenCrismon - thanks for reminding me. I'll get this done shortly.

(03 Dec '10, 12:31) Scott Whitlock ♦♦
showing 5 of 10 show 5 more comments

Hi everyone.
I was emailing back and forth with KarlB a couple months ago about MEF ideas and I mentioned to him that I had come up with a way to distribute MEF parts via NuGet packages without creating references in the target project. The detailed write up explaining how to do this is on my blog: http://wp.me/p1HYUa-1N.

Karl directed me to this question because he thought the NuGet idea might fit in well with the "marketplace" idea. Once you accept that NuGet is an acceptable package format, then you can leverage all of the infrastructure around NuGet. At the base of nuget.org they use Orchard CMS, and as you can see on nuget.org, each package has its own little home page. If you dont want to stand up your own service, I think myget.org provides third party hosting for nuget feeds. As for source code, nuget.exe supports a "-Symbols" parameter that includes much more than just the debugging symbols, it also includes a complete copy of the source. By default this code is sent to symbolsource.org, but the maintainers of that site recently introduced a method for you to host your own symbol server if you like.

I think this is a nicer fit than maintaining your own svn repository for add-ins. Contributors can make their own decision about where/how to host their source control system. You wont have to. If they want to contribute the code to the plug-in store they can do so by using the Symbols option. If they only want to contribute the binaries, they can do that too.

Anyway, I'm not really part of the Soapbox community, so you'll have to evaluate this idea against your own goals and needs. But I promised Karl I'd let you guys know about that blog entry and how it might be useful to your community, and I wanted to make good on that promise (better late than never).

If you like the idea, I'd be happy to help get it off the ground. Karl knows where to find me :)


answered 10 May '12, 22:50

Jim%20Counts's gravatar image

Jim Counts
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 19 Oct '10, 22:33

Seen: 3,420 times

Last updated: 10 May '12, 22:50

powered by OSQA