Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreJoin Store Development team?Join Store Development team?
Previous
 
Next
New Post
9/15/2006 5:50 PM
 

pls fwd to: Robert Colins

Hi, I'm Ron Robinson, GM of www.800cart.com

Never done this before, but I'm interested (and my 4 programmers are possibly interested) in joining the store development team.   A couple of us old hands around here have been developing cart technology for about 12 years - yes since before the internet was generally available to the mainstream public.

As I mention above, we've never joined an open source project before, but I think at least a couple of us are ready for it... at least from the standpoint that we are willing to listen and not barge in and try to get our own way on a project.

Some 'almost ready' code we have right now in c#.net (we could re-write in VB pretty easily, I think) is a module that goes out to the UPS and USPS servers and gets a real-time, accurate shipping quote, based on the destination zip/country and the product weight.  We'd be willing to adapt what we have and contribute it if you think that would be useful to you.  Of course, we'd also be willing to look at undertaking some coding of items that you have already identified that you need.

Enough for now, I think I've already conveyed enough to be able to ask - what is the next step for us if we were to join you?

Ron Robinson
GM, 800cart.com
rsr@cartsupport.com
626-375-5472

 

 

 

 
New Post
9/23/2006 7:14 PM
 

Get invole to move forward!

copy from http://www.dotnetnuke.com/tabid/824/default.aspx

 

 
New Post
9/25/2006 4:07 PM
 
s.ali wrote

Get invole to move forward!

copy from http://www.dotnetnuke.com/tabid/824/default.aspx

 



That's great in theory, except that the project issue tracker is not up-to-date and it's hard to contribute code when you can't run a diff against the current source tree since it is not public.

I know Robert and Dwayne accept code contributions from the rest of us, but the best we can do is work with the release versions and then they have to shoe-horn the new code into what's in their tree. It would be nice if the rest of us had read-only access to the current tree and could submit patches and updates. It would still be up to the core team to decide if the code goes in or not, so they would not be losing any control of the project. In a recent posting Dwayne asked for some pseudo-code to solve a problem (importing and exporting items from store). It would be a better use of his time if someone code send him actual, working C# code.

Just my $CAD 0.02.

Marius


email: MY USER ID at gmail dot com
 
New Post
9/25/2006 7:37 PM
 

I will be posting a similar message in my blog to explain some of what has happened in the past few weeks. I am feeling terribly guilty for the delay with this release and while it appears that nothing is happening, there has been a huge influx of work on the Store Module lately. As soon as I get access to Gemini, you will see how many issues have been resolved.

While we are on the subject of DotNetNuke module development, it is a little more involved than just fixing a line of code here and there. Since it is an open source project, the code has to come from you and you have to own the rights to the code in order to contribute it to the project. It is not acceptable to port code from a book, nor it is easy to prove ownership when your client paid you to write the code in the first place. In fact, you have to sign a disclosure to contribute source to DotNetNuke. Does this mean I can simply post code from the forum to the project? 

Beyond the legal stuff, then you have to deal with the reality factor.

For example, lets say we want to add a simple field to one of the tables. You have to...

  • modify the abstract class to handle the new property (BLL)
  • modify the controller class with overrides to the (BLL)
  • add a control to view/edit (UI)
  • add resource entries for localization (UI)
  • modify the SqlDataProvider overrides as required (DAL)
  • write script to alter the table including databaseOwner and objectQualifiers tokens (DAL-SQL)
  • write script to alter the stored procedures including parameters (input) and return values (output) (DAL-SQL)
  • package the module and upload it for testing (PA)

After that, does your code still work? Does it play nice with the existing system? Ok, let's update the change log.

Now let's say that the next version of the Store works right out of the box. Will the next version work quietly with existing data? Do you need some update scripts to manipulate the database? What about all of the data already stored in the database?

Forgive me, but I think you get the drift of my post. 

Did I mention multiple code bases without compiler directives in .NET 2.0? <chuckle>


Dwayne J. Baldwin
 
New Post
9/26/2006 3:49 PM
 

Indeed, a distributed project, with upgrades to existing production data, and in differing languages--it's a lot of work!  MANY THANKS!

But would anyone care to comment on the module's roadmap, especially in light of this press release about the Core team choosing an alternate e-commerce solution?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreJoin Store Development team?Join Store Development team?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out