New tool : DSMBuilder

[anmendes]

Hi,

I'm developed a tool named DSMBuilder.

It's a GUI tool for make dsm files.

Package = DSM File

You can :

- Create a new package (DSM file),
- Load a existing package and modify it,
- Load new certificate for package,
- Save the certifcate of package for use in another package,
- Load new dependency packages
- Remove certificate
- Rebuild the file and module list,
- Change the friendly name of package and other attributes.
- View list of Dependency packages and Shadow GUI List
- DSM Information updated with new structure.
- Remove one dependency package
- Clear list of dependencys package and shadow GUI list

- Beta version. Tested and generate a valid DSM file with all parts.

Changelog:

2008-08-08 :
- bug fix. DSM file not saved where attributes Hidden, System or ReadOnly is setting in file.

2008-07-28:
- Initial release.



Excuse me for my bad english.

[Ather]

what is the difference between this and the one in BuildOS

[anmendes]

what is the difference between this and the one in BuildOS

With this tool, is possible load/save certificates and change friendly name of dsm files, buildOS generate a basic dsm file missing certificate.

[MickyMax]

Thanks anmendes ! :)

[anmendes]

Updated version, see post#1 for details

[!Aman!]

Updated version, see post#1 for details
looks like a good tool. will test it out mate ;)
thanks.

[!Aman!]

Updated version, see post#1 for details
great tool bro :)
my observations/suggestions:
1. tool doesn't work on hidden files.
2. some menu's are not in english.
3. may be u can add an option to delete the certificate from dsm
4. is it possible to edit the dependent packages list?

[anmendes]

great tool bro :)
my observations/suggestions:
1. tool doesn't work on hidden files.
2. some menu's are not in english.
3. may be u can add an option to delete the certificate from dsm
4. is it possible to edit the dependent packages list?

-----------------------

1 - I will correct this bug.
2 - Me say what are the options that are not in English? (So I can fix them)
3 - I will add this option
4 - I'm planning functions for add and delete dependent packages list and shadown GUI list

I'm too plannig another tool based in this (mixed of pkgtool and BuildOS)
and DSM files will be saves in a xml file (also as xxxxx.dsm.xml, incorporate the actual option.xml) for future edit and manipulations.

What do you think about this?

[!Aman!]

I'm too plannig another tool based in this (mixed of pkgtool and BuildOS)
and DSM files will be saves in a xml file (also as xxxxx.dsm.xml, incorporate the actual option.xml) for future edit and manipulations.

good idea ;)

2 - Me say what are the options that are not in English? (So I can fix them)

check the screenshot for my observtion.

[anmendes]

good idea ;)

check the screenshot for my observtion.

A non english text is generate for my compiler with lib in portuguese language. I fix this:D

[anmendes]

Updated version. See post #1 for details

[Ameet]

Updated version. See post #1 for details

Hey anmendes, a changelog would be helpful ;)

[!Aman!]

Updated version. See post #1 for details
many improvements mate :). but i still have some observations:
1. tool doesn't modify the DSM if it is having 'read only', 'system' & 'hidden' attributes. i've to remove those attributes first if i want to modify a dsm. it would be better if the tool can modify the dsm without having to remove these attributes (at least we shouldn't need to remove 'system' and 'hidden' atrributes).
2. pls add the option to minimize the tool :D

and i've a question, what's the use of 'dependency package list' and 'shadow gui list'? what will happen if i remove all of these dependencies from a dsm like the dsm in Shell?

[Ameet]

many improvements mate :). but i still have some observations:
1. tool doesn't modify the DSM if it is having 'system' & 'hidden' attributes. i've to remove those attributes first if i want to modify a dsm. it would be better if the tool can modify them without having to remove these attributes
I tried to use this new build. I dont face this problem :) I can see all the files (hidden & system) when I refresh the file listing

[!Aman!]

I tried to use this new build. I dont face this problem :) I can see all the files (hidden & system) when I refresh the file listing
u didnt get my point :D
refresh the list, make some changes and try to save that DSM which is 'hidden' and 'system'.

[Football]

Great tool, works like a charm,thanks a lot bro ;)

[Ameet]

u didnt get my point :D
refresh the list, make some changes and try to save that DSM which is 'hidden' and 'system'.
Well, actually I removed a few modules from the folders and opened the dsm in this proggy. Refreshed the list, it still shows me all the files :)

[anmendes]

Hey anmendes, a changelog would be helpful ;)


I am a novice in this matter, a changelog would be something like me post a new version, increasing their number and say what was modified? Because I'm already doing something like this, but without specifying the version number.

[anmendes]

many improvements mate :). but i still have some observations:
1. tool doesn't modify the DSM if it is having 'read only', 'system' & 'hidden' attributes. i've to remove those attributes first if i want to modify a dsm. it would be better if the tool can modify the dsm without having to remove these attributes (at least we shouldn't need to remove 'system' and 'hidden' atrributes).
2. pls add the option to minimize the tool :D

and i've a question, what's the use of 'dependency package list' and 'shadow gui list'? what will happen if i remove all of these dependencies from a dsm like the dsm in Shell?

1- 2 : I will check this and put a fix. Thank you!


Good question! The dependencies are used to indicate that packages must be present so that it functions properly. The "Shadow GUI List" is a mystery to be solved. The correct that we would be tools of manipulation of ROMS to examine it and say what is missing. You are in my plans to create a new tool to manipulate ROMS with these characteristics.

[!Aman!]

@anmendes, could you pls explain this:
what's the use of 'dependency package list' and 'shadow gui list'? what will happen if i remove all of these dependencies from a dsm like the dsm in Shell or any other dsm in SYS?

[anmendes]

what's the use of 'dependency package list' and 'shadow gui list'? what will happen if i remove all of these dependencies from a dsm like the dsm in Shell or any other dsm in SYS?

@anmendes, could you pls explain this:

- 'dependency package list' : show the packages that the package needs to work properly. The PkgTool uses this list for identify missing packages. Clear this list involves losing control of this dependence. If you plan to use the other person in his PkgTool ROM, not clear it.

- 'shadow gui list' - Is a mystery, but several GUIDs listed here appear with GUID in DSM files.

[anmendes]

minor update. See post #1 for details

[deepred]

Thanks a lot for the tool. Already fixed a couple of errors using it. :) Could you please shed some light on DSM file format?

[anmendes]

Thanks a lot for the tool. Already fixed a couple of errors using it. :) Could you please shed some light on DSM file format?

see in http://forum.xda-developers.com/showthread.php?t=412439

[g77]

Congratilations it's absolutely great! As I can see you didn't use pkgcommon.dll so you must had to write all code to access dsm structure. Believe me it would be much easier if you use pkgcommon.

Btw, I wonder if there is someone who have tutorials on pkgcommon like those in msdn for using this library...

Keep your good workin!

[anmendes]

Congratilations it's absolutely great! As I can see you didn't use pkgcommon.dll so you must had to write all code to access dsm structure. Believe me it would be much easier if you use pkgcommon.

Btw, I wonder if there is someone who have tutorials on pkgcommon like those in msdn for using this library...

Keep your good workin!

I decided to write this program and work in the structure of the DSM by not just find information available on the pkgcommon and also have something that can also be used in Linux

[qtotter]

what a great tool, anmendes!

if i had knew this tool much earlier, i would not have had to waste SO MUCH time!!!

thank you!!

qt

[mbarvian]

great tool!

just two suggestions for future versions:

could you add button "Generate" next to GUID?

could you add command-line %1 parameter?

thanks a bunch man :)

[BlackBox77]

Thanks! Great tool!
Can you integrate this in Windows shell? (Open with...)
Thanks again! :)

[dj13241]

Anyone understand the Dependencies well? Please take a look at my post on DSM Dependencies ...

http://forum.xda-developers.com/showthread.php?t=527965

I can't seem to find a SINGLE ROM (cooked or stock) that has the DSM dependencies intact.

Update (7/13/09) - I was mistaken (I guess it does happen from time to time). There are two GUIDs in a DSM ... The Package GUID (which is the one we used in the DSM file name) and Interface GUID. All of the "missing" dependencies I came across matched up with an Interface GUID.

[c_shekhar]

great work @anmendes
The dsm created/modified using your has one issue which I would request you to explain to me.
When the package having the created/edited dsm using your tool is cooked into a ROM and when I dump that ROM the package having the dsm created/edited using your tool goes into "SYS" folder instead of going into "OEM" folder. What is that inside the dsm file which stamps the package as part of "SYS" or "OEM"?