Re: [J2me-device-db-general] Plugin Problems
Brought to you by:
s_szczygiel,
space2
From: James B. <jm...@ho...> - 2006-09-20 15:11:20
|
Cheers for this, I've just posted something before this came though. Ok, no problem I'm sure I can do something else instead to get the same effect. Cheers, James Brook ----- Original Message ----- From: "Sebastian Szczygiel" <seb...@op...> To: <j2m...@li...> Sent: Wednesday, September 20, 2006 4:04 PM Subject: Re: [J2me-device-db-general] Plugin Problems > Yes, it's a bug (or let's call it a "missing feature") in the microcode > framework. > >> -----Original Message----- >> From: James Brook [mailto:jm...@bl...] >> Sent: Mittwoch, 20. September 2006 16:57 >> To: Sebastian Szczygiel >> Subject: Re: [J2me-device-db-general] Plugin Problems >> >> Thanks for the replies, >> >> I thought that this was how it was supposed to work. However if I take >> the >> example and add >> >> #pngsize on >> +mariobros_176x208.png >> >> I don't see any additional fields within the device.profile. Is this a >> bug? >> >> I'll get the latest version and rebuild to see if that will work. >> >> Cheers, >> >> James >> >> ----- Original Message ----- >> From: "Sebastian Szczygiel" <seb...@op...> >> To: <j2m...@li...> >> Sent: Wednesday, September 20, 2006 3:48 PM >> Subject: Re: [J2me-device-db-general] Plugin Problems >> >> >> > Hi, >> > >> > microcode framework creates a "device.profile" which can be found in >> > /dist/src after deployment. >> > >> > Like written in the documentation you have to include this file in your >> > java-sources with >> > >> > //#include "device.profile" >> > >> > After that you can access all device-properties and also the properties >> > generated by pngsize plugin. >> > >> > BR, Sebastian >> > >> >> -----Original Message----- >> >> From: j2m...@li... >> [mailto:j2me- >> >> dev...@li...] On Behalf Of Szasz >> >> Pal >> >> Sent: Mittwoch, 20. September 2006 16:43 >> >> To: James Brook >> >> Cc: j2m...@li... >> >> Subject: Re: [J2me-device-db-general] Plugin Problems >> >> >> >> Hi! >> >> >> >> I'm not very familiar with the microcode framework (I use the other, >> >> linux/shell/gcc based one), but here is how the pngsize works: >> >> >> >> When the exporter runs in resource collector mode (ie creates the JAR >> >> file), it can also save the profile as text file. The profile contains >> >> all the properties from the phone database (for the given phone) as >> well >> >> as all the properties defined in the "resource recepie" file, hence >> also >> >> the image sizes. >> >> >> >> For example let's take a test image, call it test.png. Write the >> >> following res.txt: >> >> >> >> //--------8<---------- >> >> #pngsize on >> >> +test.png >> >> //--------8<---------- >> >> >> >> I executed the exporter this way: >> >> >> >> $ ~/work/j2me-device-db/tools/exporter/exporter --root >> >> /work/j2me-device-db/db --res res.txt --jar out.jar --format cpp >> >> --output profile.h sonyericsson/k750 >> >> >> >> (I have the j2medd project at ~/work/j2me-device-db) >> >> In short what each options does: >> >> --root - specifies where the phone database is >> >> --res - means work in resource collector mode, read the resource list >> >> from res.txt >> >> --jar - create the jar file with the resource >> >> --format - use the C header file format for output (for the profile >> file) >> >> --output - save the profile file >> >> >> >> Now in profile.h I will have all the properties and image sizes: >> >> >> >> ... >> >> //+TEST_PNG >> >> #define TEST_PNG_WIDTH 256 >> >> #define TEST_PNG_WIDTH_ "256" >> >> #define TEST_PNG_HEIGHT 256 >> >> #define TEST_PNG_HEIGHT_ "256" >> >> >> >> I think the microcode framework creates the profile file as well, but >> >> I >> >> don't know where. Also it uses a different naming convention (ie. the >> >> properties are not converted to uppercase, etc). >> >> Actually now I just took a look in microcode, it seems it does not >> >> save >> >> the profile file when collecting resources. It executes the exporter >> >> twice: first to get the profile file, then to create the jar. This has >> >> the disadvantage that the properties set in the resource file cannot >> >> be >> >> accessed from the code... but I might be mistaken here... >> >> >> >> >> >> James Brook wrote: >> >> > Hello All, >> >> > >> >> > I don't seem to be able to get the plugins to work properly with my >> >> > basic test project. >> >> > >> >> > I have added the command "#pngsize on" to my res.bld and it doesn't >> >> > appear to have any effect. >> >> > >> >> > The documentation says "When this plugin is enabled for each PNG >> >> > file >> >> > added to the jar it find out it size and adds the properties >> >> > '<filename>.width' and '<filename>.height' " >> >> > >> >> > Where does it add this property to? >> >> > >> >> > Also when I try and include the pngcheck that causes a "[exec] [E] >> >> > Unknown command `pngcheck' at >> >> > c:/development/microcode/mariobros/build/res.bld:10!" >> >> > >> >> > Any pointers would be great. >> >> > >> >> > Cheers, >> >> > >> >> > James Brook >> >> > >> >> > >> >> > --------------------------------------------------------------------- >> --- >> >> > >> >> > --------------------------------------------------------------------- >> --- >> >> - >> >> > Take Surveys. Earn Cash. Influence the Future of IT >> >> > Join SourceForge.net's Techsay panel and you'll get the chance to >> share >> >> your >> >> > opinions on IT & business topics through brief surveys -- and earn >> cash >> >> > >> >> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> >> > >> >> > >> >> > --------------------------------------------------------------------- >> --- >> >> > >> >> > _______________________________________________ >> >> > J2me-device-db-general mailing list >> >> > J2m...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general >> >> >> >> >> >> -- >> >> Best regards, >> >> Szasz Pal >> >> ---------------- >> >> Space Software Studio >> >> http://www.spacesoftwarestudio.com >> >> >> >> ----------------------------------------------------------------------- >> -- >> >> Take Surveys. Earn Cash. Influence the Future of IT >> >> Join SourceForge.net's Techsay panel and you'll get the chance to >> >> share >> >> your >> >> opinions on IT & business topics through brief surveys -- and earn >> >> cash >> >> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> >> _______________________________________________ >> >> J2me-device-db-general mailing list >> >> J2m...@li... >> >> https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general >> > >> > >> > ------------------------------------------------------------------------ >> - >> > Take Surveys. Earn Cash. Influence the Future of IT >> > Join SourceForge.net's Techsay panel and you'll get the chance to share >> > your >> > opinions on IT & business topics through brief surveys -- and earn cash >> > >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> > _______________________________________________ >> > J2me-device-db-general mailing list >> > J2m...@li... >> > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general >> > >> > >> >> > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > J2me-device-db-general mailing list > J2m...@li... > https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general > > |