Beta test finished
Download link: http://hotfile.com/dl/161830734/4e4eed7 ... 0.zip.html(edit by EmaStergam 01-07-2012)
Thanks to mirecek for beta test.
Tool will be posted to file center as soon as technical problem resolve, till then i'll reupload if needed.
Varsion 1.6
03-12-2010
[+] Few bugfix
[+] User's manual update
12-09-2010
[+] Added Border editor
[+] Few bugfix
[o] User's manual update
01-08-2010
[+] Added undo, redo
[+] Added recent list
[+] Added automatic error monitoring
[+] Added warnings count
[+] Added Grid markering
[+] Menu redesign
[+] User's manual update
[+] Few bugfix
Varsion 1.5
01-07-2010
Initial relise
_____________________________________________________________________________
Hi all
Two month ago I decide to write program and pass thru all steps of software creation. Plan was to simulate creating commercial program. It is first time I try to do “full developing” of some software. Idea behind is to learn other less interesting but equal important parts of software developing. Because I’m fan of D2 and long-time moder I decide to write some tool that is not complicated from programmers point of view and not required lot knowledge of hard coded stuffs. Final idea was to create gui for inventory manipulation. I pass all developing steps. Last step is to present software to beta testers and make last corrections and implement suggestions before relies. Keep in mind that software is not only part of this project. Planning , coding, testing and public testing are equal important to me. D2Inventory will be free software for anyone.
Few word about D2Inventory
D2Inventory is graphic user interface that make editing of inventory grid much easier. Main goal of this program is to rise speed and accuracy of inventory grid editing. Also program is made to prevent some of common errors. D2Inventory come with Users manual with tutorials and all necessary files.
General note about beta test
- Test will be opened till 07-24-2010 for sing up,
- Test will take 7 days,
- It is expected that tester will spend at least 1h per day testing software,
- Test will start with 5th beta testers signed,
- They will receive program and instructions that explain what need to be tested,
- I'll feedback at least at 21h each day during test period,
- After that ill immediately relies software to PK (if not major bugs discovered),
- Communication between testers is recommended.
- It is expected that testers won't share software with other peoples outside group and will delete beta version after test is complete.
- Beta testers will receive personalized version of software after test is complete.
- 1 - Manual spelling and grammar corrector
3 - General software user
1 - Tutorial writer
1 - Technical tester
- Should correct spelling errors in program and manual and propose better explanations
- Should use software, find bugs and propose features.
- Should write tutorial that isnt included in manual
- Should test program on different systems and configurations
- Have solid D2 moding knowledge,
Senior moders from forum has adventage,
Tester must spend at least 1h per day testing,
Tester should not quit in middle of test.
Sing in
To sing in fill next fields (with example)
- Name or nick*: GameMaster
Age*: 25
Country:
Computer configuration - CPU: 4gh
Computer configuration - Ram: 4gb
OS System*: WinXP
Use MSN or compatible messenger Y/N*: Y
Had experience with inventory edit Y/N: Y
Moding D2 least 3 years Y/N: Y
Test: (Manual spelling and grammar corrector, General software user, Tutorial writer, Technical tester)
Expecting test time: I'm free from 18-20h and can test.
Any other notes: will be unavailable on Monday and Sunday
* required
All communications should be over MSN or compatible instant messenger. I prefers this because I’m online most time. If MSN is problem, e-mile is ok but it may take day to replay. Best time for communication is 10-14h and 18- 21h GMT+1.
Note
I use Office 2003. If you use greater version you should export as older versions. You can use WordPad or Notepad if you wish. Of course you can chose any other format to report errors/corrections but that must be easy and effective and should not make confusion
Any other questions? Ask.
Link updated 03-12-2010us/i/tt00001