Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- mesteele101 created topic »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 01:39 AM
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 01:29 AM
- mdee created topic »How to implement returnpage ?« 01:00 AM
- nestormateo responded to »Fillters in Clip« 24. May
- damon responded to »Can the Updated Version Check be Turned Off (Z 1.3)« 24. May
- frw responded to »Bug in the SMTP mail transfer protocol - Port 25 - Zikula 1.2.9« 22. May
- mdee responded to »Short URL questions« 22. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Trade Module
-
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 56
I was wondering if something like this exists or is in the making. Its something like ebay, lists of items, users, feedback ability .. etc. Like ebay but an exchange system not money. Is there a module of this or maybe a stand alone? does something like this exist for download ? -
**unknown user**
- Rank: Softmore
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 367
I am glad that I came across your posting this evening.
I am actually working on something like what you have asked about. If you would like to read the information that I have available at this time, these articles should serve as an introduction. You may also want to review the forum postings others have made in the dedicated forums I have set up for this module. If you have any input you would like to contribute regarding features or functions, please feel free to make a posting. While most things on my site are available without having to register, you do have to register to make postings. It only makes sense to do it that way since with your email address on file you can elect to recieve notice when someone has posted to your message. But registration on my site is free, so you can't beat the price
I have registered this project with the Post Nuke Network Operations site, found at this location so that it would be recognized as an official module for Post Nuke.
Hope this helps you out. -
**unknown user**
- Rank: Registered User
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 4
Ira.. I love how you say that youre going to do something like this.. but.. you.. never.. do. Ive got one that works.. but it doesnt work the way *I* want it to.. maybe I should find someone to hack it? -
**unknown user**
- Rank: Softmore
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 367
thatgirltx
Ira.. I love how you say that youre going to do something like this.. but.. you.. never.. do. Ive got one that works.. but it doesnt work the way *I* want it to.. maybe I should find someone to hack it?
Before I dive into the detail of my reply, just let me say that I am not offended by the posting made and am not making this reply in any kind of an upset mode. So please read this reply with the knowledge it is meant to inform, and nothing more.
Actually, there have been things going on around the project that I said I would do. True, there is not a finished product to download and install, but that does not mean things have not been happening.
When I first registered the project at the NOC center of PostNuke and began initially laying out things to design the database, information on .750 PostNuke was not yet out. The latest release of PostNuke at that time was .726. Part way through my initial database design work on the project, PostNuke .750 came out. The importance of this is .750 brought a new way of designing modules through the incorporation of Smarty in the form of pnRender. Because .750 came out just as .760 is, in the form of release candidates until things have been smoothed out enough to make an official release, I stopped the work I was doing at the .726 level and began looking at how modules are built under the new modle that would begin with .750 and follow forward with later releases of PostNuke.
Something I have had to devote some time to as well is looking into what development environment to use to perform the development work in. My day job as a programmer has me dealing in the Microsfot environment and using tools built by them. Being new to PHP programming, I hadn't a clue where to begin looking for a development environment. In looking at this aspect of things I was trying to find something reasonably priced that I could justify spending the money on because my PostNuke work is a hobby at this time given how my day job is oriented to a different arena of technologies. Luckily for me, one of the individuals that I gave some assistance to opted to make a donation for the help received and that donation will go toward the expense of the development environment that I will be using to perform my PHP programming in.
Also during this same time span, I began to realize that the initial design I had in mind may not be the best way to do things. There are some postings in the forums if you care to have a look and spend time doing some searching where those more experienced in module development made some suggestions to me about taking the one module I was planning and breaking it down into smaller pieces, some of which could be used by other modules.
I began to look at taking this approach and planning out how to accomplish it. The suggestion made some sense to me at the time and makes even more sense to me now that I have worked quite a bit on planning how to break things down. Prior to this I had been feeling a bit uneasy about the potential size of the project because this one has a more complex nature than some due to the things that are involved with it.
At this point in the planning phase the original registered pnAuctionSystem will still be a module but it will be much smaller than the original way I was going about things. The size reduction is because there will be two other modules, pnBidSystem and pnProductList that will be written to accompany it. PnAcutionSystem will be a module that ties pnBidSystem and pnProductList together to allow you to perform auctions in the style of ebay or other auction houses.
The beauty of this new design method will allow pnProductList to be 're-used' if someone wants to write a trade style module where you swap goods rather than auction them off. The author, whoever that might be, would have to focus only on the logic and UI that would be involved in trading and using the PostNuke concept of hooks, tie into the pnProductList module to be the storehouse of good willing to be traded and goods being sought.
The pnBidSystem can be, or will be, so designed that it contains the logic to allow auctions of goods like ebay or other auction houses and at the same time use logic to allow for 'bids' to be taken. This would be for cases where instead of auctioning off goods to the highest bidder the idea would be to post contract jobs, take bids on them, and then take the lower of the bids placed. In a case like this, job bids, the pnProductList module could be used to house the informatio for the job bid.
This has taken me quite a bit of time to get oriented to and to think it through and then lay the initial database design out to split things up into the separate modules that they will belong in. True, I would most likely have had the auction module completed by this time if I had stayed focused on developing it at the .726 level and not looked at .750 and the upcoming .760, however, I do not believe that would have been in the best interest of anyone involved. I would have had a major re-work on my hands later when legacy coded modules are phased out and at that time if I would attempt a split out like that described above into the three separate modules rather than the one massive one it would have been a massive database conversion as well. I fully believe that the change in module development is worth the added wait because of the enhanced features it brings and the flexibility it permits users when it comes to templating the UI without having to worry about messing in the logic of the program itself. I also believe the splitting of the former single module into three separate components is in the best interest of everyone involved because of the ability to build more stable and solid modules as well as the ability to have 're-use' of module technology for other systems that in part need what these modules provide.
I do plan to continue my work and to eventually see the modules through to their completion. It is going to take time though because I am new at PostNuke development and it is something I do in my spare time along with maintaining my web site and writing article for it which help other users in the use of creating PostNuke sites. At this point in time I pretty much have the database layouts completed for the three separate modules and am starting the next step which is to create the initialization files which contain the format information for each of the columns in each of the database tables.
- Moderated by:
- Support
