j2me-device-db-general — Everything about j2me-device-db

[J2me-device-db-general] problem with the resource-collector

[<kro...@gm...>]

 Hi everybody,

I'm using netbeans with j2me-device-db.
I compiled the exporter and configure the microcode and works fine, but in
the resource-collector task I get this error:

...
Preverification ...
Preverifying
/home/kronenthaler/work/3dealers/test/dist/jadjar/sonyericsson/w810/test.jar
Updating JAD file
/home/kronenthaler/work/3dealers/test/dist/jadjar/sonyericsson/w810/test.jad
resource-collector:
Adding resources to JAR ...
[E] Cannot locate file
`/home/kronenthaler/work/3dealers/test/build/res.bld'!
Result: 1
obfuscate:
Obfuscating ...
...

 The res.bld file exists in the right path.
Also, I try the same command in the console and I get the same error... :S

Anybody can help me? Any tips or tricks?

PD: sorry my english
--
ignacio calderon
senior programmer
www.3dealers.net

Re: [J2me-device-db-general] J2me-device-db-general Digest, Vol 4, Issue 1

[Sebastian S. <seb...@op...>]

Hi Juan,

 

I personally I'm not active anymore in development of j2me-device-db.

 

If you're interested we could add you as developer to the project, just let
us know before what you would like to do.

 

Regards,

Sebastian

 

 

  _____  

From: j2m...@li...
[mailto:j2m...@li...] On Behalf Of
Juan Carlos Ramirez
Sent: Montag, 16. April 2007 21:51
To: j2m...@li...
Subject: Re: [J2me-device-db-general] J2me-device-db-general Digest, Vol
4,Issue 1

 

Hi,

I would like to know if this project is under development? Is there a list
of tasks in order to help?
This has been very helpful for me...

Thanks,

Juan Carlos

Re: [J2me-device-db-general] J2me-device-db-general Digest, Vol 4, Issue 1

[Juan C. R. <3d...@gm...>]

Hi,

I would like to know if this project is under development? Is there a list
of tasks in order to help?
This has been very helpful for me...

Thanks,

Juan Carlos

Re: [J2me-device-db-general] Project status

[James B. <jm...@bl...>]

Hello,

We are currently using it quite a lot (http://www.teazel.com) and adding a 
few more devices - we haven't updated it for a bit.

Has anyone considered trying to merge the date with wurfl?

Cheers,

James Brook


----- Original Message ----- 
From: "Pal Szasz" <sp...@sp...>
To: "Omry Yadan" <om...@ya...>
Cc: <j2m...@li...>
Sent: Monday, March 05, 2007 6:53 PM
Subject: Re: [J2me-device-db-general] Project status


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> Currently I think only Sebastian is working on the project (I don't know
> if he's active or not). I haven't updated the database for some time
> now, and probably won't in the following month. However I might continue
> updated the Sony-Ericsson phones.
>
> However, if you find a bug in the exporter, or in the database, please
> let us know, I might try to make some time to fix it.
>
> Omry Yadan wrote:
>> Hi guys,
>>
>> I am considering to use the device database as a part of antenna new
>> preprocessor,
>>
>> is the database being actively maintained?
>>
>>
>>     Thank.
>>
>>        Omry.
>>
>>
>> -------------------------------------------------------------------------
>> 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
>>
>
> - --
> Szasz Pal
> - ----------------
> Space Software Studio
> http://www.spacesoftwarestudio.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFF7GcVCclUI0EjozQRApisAJ45tOPkXZSnJQMvStd5ZhFbZrRONQCdHONY
> b6sCVbR4orkgnTEoeKqEkLs=
> =9Dza
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> 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
>
> 

Re: [J2me-device-db-general] Project status

[Pal S. <sp...@sp...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Currently I think only Sebastian is working on the project (I don't know
if he's active or not). I haven't updated the database for some time
now, and probably won't in the following month. However I might continue
updated the Sony-Ericsson phones.

However, if you find a bug in the exporter, or in the database, please
let us know, I might try to make some time to fix it.

Omry Yadan wrote:
> Hi guys,
> 
> I am considering to use the device database as a part of antenna new 
> preprocessor,
> 
> is the database being actively maintained?
> 
> 
>     Thank.
> 
>        Omry.
> 
> 
> -------------------------------------------------------------------------
> 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
> 

- --
Szasz Pal
- ----------------
Space Software Studio
http://www.spacesoftwarestudio.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF7GcVCclUI0EjozQRApisAJ45tOPkXZSnJQMvStd5ZhFbZrRONQCdHONY
b6sCVbR4orkgnTEoeKqEkLs=
=9Dza
-----END PGP SIGNATURE-----

[J2me-device-db-general] Project status

[Omry Y. <om...@ya...>]

Hi guys,

I am considering to use the device database as a part of antenna new 
preprocessor,

is the database being actively maintained?


    Thank.

       Omry.

[J2me-device-db-general] Test

[Omry Y. <om...@ya...>]

Testing

Re: [J2me-device-db-general] Full XML Export

[Pal S. <sp...@sp...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

There is a script in tools/scripts/list_all_in_xml.sh which does this...
but it's working for linux only (however you might be able to get it
working in windows with msys or cygwin environment... or you can write a
similar script, eg. in perl).

Omry Yadan wrote:
> Hi all,
> 
> I am wrote a new preprocessor for Antenna that has integration with the 
> Polish XML.
> 
> You can find more info about it in the antenna mailing list on sf.net.
> 
> a quick glance shows that the information in your database is of higher 
> quality and is generally more useful to be used as variables for a 
> preprocessor.
> 
> your exporter also supports the h2me-polish XML format (per a request I 
> made a long time ago, if I am not mistaken) - but from what I 
> understand, it can only export a single phone at a time.
> 
> I would rather integrate the preprocessor with your database, but I 
> would need a way to export all the devices into a single XML.
> 
> is something like that supported at the moment?
> 
> 
> Thanks,
> 
>     Omry.
> 
> 
> -------------------------------------------------------------------------
> 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
> 

- --
Szasz Pal
- ----------------
Space Software Studio
http://www.spacesoftwarestudio.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF6y7DCclUI0EjozQRAlEGAJ9Z1XMosMKQfyT68RIBSLhdjEMFKgCgrlIa
Um8XkzGCO21Nwx/8vlIiM7c=
=+xVv
-----END PGP SIGNATURE-----

[J2me-device-db-general] Full XML Export

[Omry Y. <om...@ya...>]

Hi all,

I am wrote a new preprocessor for Antenna that has integration with the 
Polish XML.

You can find more info about it in the antenna mailing list on sf.net.

a quick glance shows that the information in your database is of higher 
quality and is generally more useful to be used as variables for a 
preprocessor.

your exporter also supports the h2me-polish XML format (per a request I 
made a long time ago, if I am not mistaken) - but from what I 
understand, it can only export a single phone at a time.

I would rather integrate the preprocessor with your database, but I 
would need a way to export all the devices into a single XML.

is something like that supported at the moment?


Thanks,

    Omry.

Re: [J2me-device-db-general] Resource Collector

[Jim W. <ech...@gm...>]

Hi,

make sure you've included "device.profile"

put:

//#include "device.profile"

at the top of the source file, where you use SOUND_MIME variable

regards,
Jim


2006/12/14, Juan Carlos Ramirez <3d...@gm...>:
> Hi,
>
> I'm trying to create something similar to the sound example in the bottom of
> the following link:
>
> http://j2me-device-db.sourceforge.net/pmwiki/index.php?n=Main.ResourceCollector
>
> and even the example is not working for me... I'm having compile errors
> because the SOUND_MIME variable that they use in the j2me code (Player p =
> Manager.createPlayer(stream, SOUND_MIME);) is not defined.
>
> Can anybody help me? Do you have any sample code?
>
> Thanks,
>
>
> --
> Juan Carlos Ramirez
> www.3dealers.net
> -------------------------------------------------------------------------
> 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
>
>
>

[J2me-device-db-general] Resource Collector

[Juan C. R. <3d...@gm...>]

Hi,

I'm trying to create something similar to the sound example in the bottom of
the following link:

http://j2me-device-db.sourceforge.net/pmwiki/index.php?n=Main.ResourceCollector

and even the example is not working for me... I'm having compile errors
because the SOUND_MIME variable that they use in the j2me code (Player p =
Manager.createPlayer(stream, SOUND_MIME);) is not defined.

Can anybody help me? Do you have any sample code?

Thanks,


-- 
Juan Carlos Ramirez
www.3dealers.net

[J2me-device-db-general] Problem again :s

[Damian S. <dam...@ad...>]

I have problem again :-[ , when I use the KeyPress and KeyRelease I have 
a problem.
This is the mesage in the console,

Buildfile: C:\projects\workspace\Microcode1945\build\build.xml
deploy:
deploy:
deploy-device:
clean-sources:
   [delete] Deleting directory C:\projects\workspace\Microcode1945\dist\src
   [delete] Deleting directory 
C:\projects\workspace\Microcode1945\dist\classes
db-exporter:
     [echo] Exporting device properties ...
    [mkdir] Created dir: C:\projects\workspace\Microcode1945\dist\src
preprocess:
     [echo] Preprocessing Java source files ... 
c:/projects/workspace/Microcode1945/dist
     [copy] Copying 7 files to C:\projects\workspace\Microcode1945\dist\src
filepp:
filepp:
filepp:
filepp:
filepp:
filepp:
filepp:
create-jar:
     [echo] Creating JAD ...
     [echo] Using CLDC 1.0 MIDP 1.0
   [delete] Deleting: 
C:\projects\workspace\Microcode1945\dist\src\device.properties
   [wtkjad] **************************************************************
   [wtkjad] * Antenna 0.9.13 initialized for project "microcode build 
file" *
   [wtkjad] * Using Sun Wireless Toolkit 2.2 (CLDC-1.0; MIDP-1.0)        *
   [wtkjad] **************************************************************
   [wtkjad] Creating JAD file 
C:\projects\workspace\Microcode1945\dist\jadjar\nokia\s40\EjemploMicrocode_v1-0-0_en.jad
     [echo] Compiling ...
    [mkdir] Created dir: C:\projects\workspace\Microcode1945\dist\classes
 [wtkbuild] Compiling 7 source files to 
C:\projects\workspace\Microcode1945\dist\classes
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:407: 
duplicate case label
 [wtkbuild] case KEY_NUM4:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:410: 
duplicate case label
 [wtkbuild] case KEY_NUM6:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:413: 
duplicate case label
 [wtkbuild] case KEY_NUM2:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:416: 
duplicate case label
 [wtkbuild] case KEY_NUM8:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:432: 
duplicate case label
 [wtkbuild] case KEY_NUM4:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:435: 
duplicate case label
 [wtkbuild] case KEY_NUM6:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:438: 
duplicate case label
 [wtkbuild] case KEY_NUM2:
 [wtkbuild] ^
 [wtkbuild] 
C:\projects\workspace\Microcode1945\dist\src\SSCanvas.java:441: 
duplicate case label
 [wtkbuild] case KEY_NUM8:
 [wtkbuild] ^
 [wtkbuild] 8 errors

BUILD FAILED
C:\projects\workspace\Microcode1945\build\build.xml:8: The following 
error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:50: The 
following error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:59: The 
following error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:92: Compile 
failed; see the compiler error output for details.

Thanks,

Re: [J2me-device-db-general] Problem whit example

[Sebastian S. <seb...@op...>]

Extend your windows environment PATH variable with JDK\bin
Example c:\Java\j2sdk1.4.2_09\bin;

Let me know if this works.

Sebastian


> -----Original Message-----
> From: j2m...@li... =
[mailto:j2me-
> dev...@li...] On Behalf Of Damian
> Sansberro
> Sent: Dienstag, 12. Dezember 2006 16:59
> To: j2m...@li...
> Subject: [J2me-device-db-general] Problem whit example
>=20
> Hi,
> I need start to use the framework, when I deploy the example in =
eclipse,
> the build falid.
> I paste the message of the console,
>=20
> Buildfile: C:\projects\workspace\EjemploMicrocode\build\build.xml
> deploy:
> deploy:
> deploy-device:
> clean-sources:
>    [delete] Deleting directory
> C:\projects\workspace\EjemploMicrocode\dist\src
>    [delete] Deleting directory
> C:\projects\workspace\EjemploMicrocode\dist\classes
> db-exporter:
>      [echo] Exporting device properties ...
>     [mkdir] Created dir: =
C:\projects\workspace\EjemploMicrocode\dist\src
> preprocess:
>      [echo] Preprocessing Java source files ...
> c:/projects/workspace/EjemploMicrocode/dist
>      [copy] Copying 2 files to
> C:\projects\workspace\EjemploMicrocode\dist\src
> filepp:
> filepp:
> create-jar:
>      [echo] Creating JAD ...
>      [echo] Using CLDC 1.0 MIDP 1.0
>    [delete] Deleting:
> C:\projects\workspace\EjemploMicrocode\dist\src\device.properties
>    [wtkjad] =
**************************************************************
>    [wtkjad] * Antenna 0.9.13 initialized for project "microcode build
> file" *
>    [wtkjad] * Using Sun Wireless Toolkit 2.2 (CLDC-1.0; MIDP-1.0)      =
  *
>    [wtkjad] =
**************************************************************
>    [wtkjad] Creating JAD file
> =
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
c
> ode_v1-0-0_en.jad
>      [echo] Compiling ...
>     [mkdir] Created dir:
> C:\projects\workspace\EjemploMicrocode\dist\classes
>  [wtkbuild] Compiling 2 source files to
> C:\projects\workspace\EjemploMicrocode\dist\classes
>      [echo] Creating JAR ...
> [wtkpackage] Building jar:
> =
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
c
> ode_v1-0-0_en.jar
> [wtkpackage] Updating JAD file
> =
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
c
> ode_v1-0-0_en.jad
>      [echo] Preverification ...
> [wtkpreverify] Preverifying
> =
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
c
> ode_v1-0-0_en.jar
> [wtkpreverify] JAR file creation failed with error -1
> [wtkpreverify] The preverified classes if any are in tmp16554. See jar
> log of errors in
> C:\projects\workspace\EjemploMicrocode\build\a13c0464.tmp\jarlog.txt
>=20
> BUILD FAILED
> C:\projects\workspace\EjemploMicrocode\build\build.xml:8: The =
following
> error occurred while executing this line:
> C:\projects\j2me-device-db-win\tools\microcode\build.xml:50: The
> following error occurred while executing this line:
> C:\projects\j2me-device-db-win\tools\microcode\build.xml:59: The
> following error occurred while executing this line:
> C:\projects\j2me-device-db-win\tools\microcode\build.xml:108:
> Preverification failed (result=3D1)
>=20
> Total time: 8 seconds
>=20
>=20
> Thanks,
> Dami=E1n
>=20
> =
-------------------------------------------------------------------------=

> 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=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> J2me-device-db-general mailing list
> J2m...@li...
> https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general

[J2me-device-db-general] Problem whit example

[Damian S. <dam...@ad...>]

Hi,
I need start to use the framework, when I deploy the example in eclipse,=20
the build falid.
I paste the message of the console,

Buildfile: C:\projects\workspace\EjemploMicrocode\build\build.xml
deploy:
deploy:
deploy-device:
clean-sources:
   [delete] Deleting directory=20
C:\projects\workspace\EjemploMicrocode\dist\src
   [delete] Deleting directory=20
C:\projects\workspace\EjemploMicrocode\dist\classes
db-exporter:
     [echo] Exporting device properties ...
    [mkdir] Created dir: C:\projects\workspace\EjemploMicrocode\dist\src
preprocess:
     [echo] Preprocessing Java source files ...=20
c:/projects/workspace/EjemploMicrocode/dist
     [copy] Copying 2 files to=20
C:\projects\workspace\EjemploMicrocode\dist\src
filepp:
filepp:
create-jar:
     [echo] Creating JAD ...
     [echo] Using CLDC 1.0 MIDP 1.0
   [delete] Deleting:=20
C:\projects\workspace\EjemploMicrocode\dist\src\device.properties
   [wtkjad] *************************************************************=
*
   [wtkjad] * Antenna 0.9.13 initialized for project "microcode build=20
file" *
   [wtkjad] * Using Sun Wireless Toolkit 2.2 (CLDC-1.0; MIDP-1.0)        =
*
   [wtkjad] *************************************************************=
*
   [wtkjad] Creating JAD file=20
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
code_v1-0-0_en.jad
     [echo] Compiling ...
    [mkdir] Created dir: C:\projects\workspace\EjemploMicrocode\dist\clas=
ses
 [wtkbuild] Compiling 2 source files to=20
C:\projects\workspace\EjemploMicrocode\dist\classes
     [echo] Creating JAR ...
[wtkpackage] Building jar:=20
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
code_v1-0-0_en.jar
[wtkpackage] Updating JAD file=20
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
code_v1-0-0_en.jad
     [echo] Preverification ...
[wtkpreverify] Preverifying=20
C:\projects\workspace\EjemploMicrocode\dist\jadjar\nokia\s40\EjemploMicro=
code_v1-0-0_en.jar
[wtkpreverify] JAR file creation failed with error -1
[wtkpreverify] The preverified classes if any are in tmp16554. See jar=20
log of errors in=20
C:\projects\workspace\EjemploMicrocode\build\a13c0464.tmp\jarlog.txt

BUILD FAILED
C:\projects\workspace\EjemploMicrocode\build\build.xml:8: The following=20
error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:50: The=20
following error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:59: The=20
following error occurred while executing this line:
C:\projects\j2me-device-db-win\tools\microcode\build.xml:108:=20
Preverification failed (result=3D1)

Total time: 8 seconds


Thanks,
Dami=E1n

Re: [J2me-device-db-general] Define custom properties

[Sebastian S. <seb...@op...>]

Or you can include in your source-code (where you use own properties) with

//#include "common.inc"

Just before you include the device profile.
Where common.inc is a file in /build folder (where res.bld is). There you
you can define

//#define $debug

Or whatever you need.


> -----Original Message-----
> From: j2m...@li... [mailto:j2me-
> dev...@li...] On Behalf Of Jim Walt
> Sent: Donnerstag, 9. November 2006 14:07
> To: Szasz Pal
> Cc: j2m...@li...
> Subject: Re: [J2me-device-db-general] Define custom properties
> 
> Thanks! it works.
> 
> I've made some custom --set parameters to exporter in microcode's
> build.xml such as
> "--set ${prop1}" parameter
> 
> and then in my build.properties project file do
> "prop1=DEBUG"
> 
> regards,
> Jim
> 
> 2006/11/9, Szasz Pal <sp...@sp...>:
> > I think you can edit the build.xml file and add some extra options for
> > the exporter. For example if you add the option '--set DEBUG=1' then it
> > will be defined in every source file (actually it will be like a
> > property, ie. I think you need to use it as $DEBUG)
> >
> > Jim Walt wrote:
> > > Hi!
> > >
> > > How can I use my own-defined properties?
> > > I want to define "DEBUG" property and use it with preprocessor, but i
> > > cant get where to put it.
> > >
> > > e.g.
> > > Canvas.java
> > >
> > > //#ifdef DEBUG
> > > render_debug();
> > > //#endif
> > > I want to define it global. Putting "//#define DEBUG" in every source
> > > header  is inconvenient.
> > >
> > >
> > > best regards,
> > > Jim
> > >
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> J2me-device-db-general mailing list
> J2m...@li...
> https://lists.sourceforge.net/lists/listinfo/j2me-device-db-general

Re: [J2me-device-db-general] Define custom properties

[Jim W. <ech...@gm...>]

Thanks! it works.

I've made some custom --set parameters to exporter in microcode's
build.xml such as
"--set ${prop1}" parameter

and then in my build.properties project file do
"prop1=DEBUG"

regards,
Jim

2006/11/9, Szasz Pal <sp...@sp...>:
> I think you can edit the build.xml file and add some extra options for
> the exporter. For example if you add the option '--set DEBUG=1' then it
> will be defined in every source file (actually it will be like a
> property, ie. I think you need to use it as $DEBUG)
>
> Jim Walt wrote:
> > Hi!
> >
> > How can I use my own-defined properties?
> > I want to define "DEBUG" property and use it with preprocessor, but i
> > cant get where to put it.
> >
> > e.g.
> > Canvas.java
> >
> > //#ifdef DEBUG
> > render_debug();
> > //#endif
> > I want to define it global. Putting "//#define DEBUG" in every source
> > header  is inconvenient.
> >
> >
> > best regards,
> > Jim
> >

Re: [J2me-device-db-general] Define custom properties

[Szasz P. <sp...@sp...>]

I think you can edit the build.xml file and add some extra options for 
the exporter. For example if you add the option '--set DEBUG=1' then it 
will be defined in every source file (actually it will be like a 
property, ie. I think you need to use it as $DEBUG)

Jim Walt wrote:
> Hi!
> 
> How can I use my own-defined properties?
> I want to define "DEBUG" property and use it with preprocessor, but i
> cant get where to put it.
> 
> e.g.
> Canvas.java
> 
> //#ifdef DEBUG
> render_debug();
> //#endif
> I want to define it global. Putting "//#define DEBUG" in every source
> header  is inconvenient.
> 
> 
> best regards,
> Jim
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> 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

[J2me-device-db-general] Define custom properties

[Jim W. <ech...@gm...>]

Hi!

How can I use my own-defined properties?
I want to define "DEBUG" property and use it with preprocessor, but i
cant get where to put it.

e.g.
Canvas.java

//#ifdef DEBUG
render_debug();
//#endif
I want to define it global. Putting "//#define DEBUG" in every source
header  is inconvenient.


best regards,
Jim

Re: [J2me-device-db-general] Device Data Source

[Szasz P. <sp...@sp...>]

James Brook wrote:
> Hello All,
>  
> I was wondering where you had got all the data from for the device 
> database as I have noticed the odd mistake:

It's collected from several sources, own tests, etc.
If you find any mistake, just send an email to this list, or issue a bug 
report. (I think the later one would be the better choice).

> For example the Motorola V3 has a full screen canvas size of 176 x 220 
> but the output of the exporter is 176 x 204. What is the process of 
> correcting the data (i.e. committing back to CVS etc).

You mean you can actually access the full screen size? I have a V525 
which is almost the same, and there I can access only 204 rows in 
fullcanvas mode (and I think 182 in normal mode). And although I don't 
have the phone, I made several games for it, and the testers doesn't 
mentioned anything that not the full screen is used.

> Also I was unable to solve my problems with getting the framework to 
> including the image sizes in the device output so instead I'm using a 
> combination of the exporter and my own antenna scripts. Also I couldn't 
> see a way of putting in the device specific Jad properties and make use 
> of the framework build files.

I suppose you are speaking of the "Microcode" framework. It had a small 
bug, which has been corrected now, I'm not sure if the patch is commited 
yet in the CVS though.
>  
> 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

[J2me-device-db-general] Device Data Source

[James B. <jm...@ho...>]

Hello All,

I was wondering where you had got all the data from for the device =
database as I have noticed the odd mistake:

For example the Motorola V3 has a full screen canvas size of 176 x 220 =
but the output of the exporter is 176 x 204. What is the process of =
correcting the data (i.e. committing back to CVS etc).

Also I was unable to solve my problems with getting the framework to =
including the image sizes in the device output so instead I'm using a =
combination of the exporter and my own antenna scripts. Also I couldn't =
see a way of putting in the device specific Jad properties and make use =
of the framework build files.

Cheers,

James Brook

Re: [J2me-device-db-general] Plugin Problems

[James B. <jm...@ho...>]

I think it does have the device at the end, I have:

<target name="db-exporter">
    <echo message="Exporting device properties ..."/>
    <mkdir dir="${dist.dir}/src"/>
    <exec executable="${microcode.home}/contrib/exporter/exporter.exe" 
output="${dist.dir}/src/device.profile">
      <arg
          line="--root ${j2me.device.db} --set ${exporter.props} --res 
${res.bld} --format cpp:prefix=//#,nameprefix=$,noupper,nostrings 
${device}"/>
    </exec>
    <exec executable="${microcode.home}/contrib/exporter/exporter.exe" 
output="${dist.dir}/src/device.properties">
      <arg
          line="--root ${j2me.device.db} --set ${exporter.props} --format 
txt ${device}"/>
    </exec>
  </target>

Cheers,

James

----- Original Message ----- 
From: "Szasz Pal" <sp...@sp...>
To: "James Brook" <jm...@ho...>
Cc: <j2m...@li...>
Sent: Wednesday, September 20, 2006 6:18 PM
Subject: Re: [J2me-device-db-general] Plugin Problems


> James Brook wrote:
>> Hum,
>>
>> It changed the device.profile so that it now contains the mapping between
>> the image names and the images eg:
>>
>> splash.png = splash240x320.png
>> bg.png = bg240x320.png
>>
>> but it doesn't have the image size information in there.
>
> Please make sure the ${device} is also present at the end of the command
> line, ie:
>
>>>          line="--root ${j2me.device.db} --set ${exporter.props} --res
>>> ${res.bld} --format cpp:prefix=//#,nameprefix=$,noupper,nostrings
>>> ${device}"/>
>
>
> -- 
> 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
>
> 

Re: [J2me-device-db-general] Plugin Problems

[Szasz P. <sp...@sp...>]

James Brook wrote:
> Hum,
> 
> It changed the device.profile so that it now contains the mapping between 
> the image names and the images eg:
> 
> splash.png = splash240x320.png
> bg.png = bg240x320.png
> 
> but it doesn't have the image size information in there.

Please make sure the ${device} is also present at the end of the command 
line, ie:

>>          line="--root ${j2me.device.db} --set ${exporter.props} --res
>> ${res.bld} --format cpp:prefix=//#,nameprefix=$,noupper,nostrings
>> ${device}"/>


-- 
Best regards,
Szasz Pal
----------------
Space Software Studio
http://www.spacesoftwarestudio.com

Re: [J2me-device-db-general] Plugin Problems

[James B. <jm...@ho...>]

Hum,

It changed the device.profile so that it now contains the mapping between 
the image names and the images eg:

splash.png = splash240x320.png
bg.png = bg240x320.png

but it doesn't have the image size information in there.

Interestingly it no longer includes all the other device information, would 
that be a problem or does the rest of the framework use the 
device.properties that is produced instead?

Cheers,

James

----- Original Message ----- 
From: "Sebastian Szczygiel" <seb...@op...>
To: <j2m...@li...>
Sent: Wednesday, September 20, 2006 4:12 PM
Subject: Re: [J2me-device-db-general] Plugin Problems


> Try this:
>
> In microcode build.xml in target "db-exporter"
>
> Change the following line
>
>          line="--root ${j2me.device.db} --set ${exporter.props} --format
> cpp:prefix=//#,nameprefix=$,noupper,nostrings ${device}"/>
>
> to
>
>          line="--root ${j2me.device.db} --set ${exporter.props} --res
> ${res.bld} --format cpp:prefix=//#,nameprefix=$,noupper,nostrings
> ${device}"/>
>
> the option "--res ${res.bld}" was missing.
>
> BR, Sebastian
>
>> -----Original Message-----
>> From: j2m...@li... [mailto:j2me-
>> dev...@li...] On Behalf Of James Brook
>> Sent: Mittwoch, 20. September 2006 17:10
>> To: j2m...@li...
>> Subject: Re: [J2me-device-db-general] Plugin Problems
>>
>> Thanks for the reply,
>>
>> I've just taken the latest version from CVS (at about 3.30 today) and
>> rebuilt. I've then taken the framework project example
>> mariobros-example.zip. Unpacked it, altered the properties etc.
>>
>> Then I've added a new resource called donkey.png and added the following
>> to
>> the res.bld
>>
>> #pngsize on
>> +donkey.png
>>
>> In the generated device.profile I get the following:
>>
>> //#define $full_canvas 1
>> //#define $vendor nokia
>> //#define $model s60
>> //#define $profile nokia/s60
>> //#define $nokia 1
>> //#define $nokia/s60 1
>> //#define $uses.nokia/s60
>> //#define $uses.nokia/base
>> //#define $uses.generic/midp1
>> //#define $midp.version 1
>> //#define $cldc.version 1.0
>> //#define $mmapi 0
>> //#define $btapi 0
>> //#define $nokiaapi 1
>> //#define $siemensapi 0
>> //#define $samsungapi 0
>> //#define $vscl 0
>> //#define $wmapi 0
>> //#define $mascotapi 0
>> //#define $m3gapi 0
>> //#define $pdaapi 0
>> //#define $locationapi 0
>> //#define $webservicesapi 0
>> import javax.microedition.lcdui.*;
>> import javax.microedition.midlet.*;
>> import javax.microedition.rms.*;
>> //#define $uses.includes/nokiaapi
>> import com.nokia.mid.ui.*;
>> import com.nokia.mid.sound.*;
>> //#define $nokiaapi.ott 1
>> //#define $nokiaapi.wav 1
>> //#define $key.up -1
>> //#define $key.down -2
>> //#define $key.left -3
>> //#define $key.right -4
>> //#define $key.softleft -6
>> //#define $key.softright -7
>> //#define $key.clear -8
>> //#define $canvas_class FullCanvas
>> //#define $uses.nokia/canvas_176x208
>> //#define $canvas.width 176
>> //#define $canvas.height 208
>> //#define $icon.width 42
>> //#define $icon.height 29
>>
>> Which is missing the donkey properties.
>>
>> Is there a step I'm missing, or is this a bug?
>>
>> Cheers,
>>
>> James Brook
>>
>> ----- 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
>
>
> -------------------------------------------------------------------------
> 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
>
> 

Re: [J2me-device-db-general] Plugin Problems

[Sebastian S. <seb...@op...>]

Try this:

In microcode build.xml in target "db-exporter"

Change the following line

          line="--root ${j2me.device.db} --set ${exporter.props} --format
cpp:prefix=//#,nameprefix=$,noupper,nostrings ${device}"/>

to

          line="--root ${j2me.device.db} --set ${exporter.props} --res
${res.bld} --format cpp:prefix=//#,nameprefix=$,noupper,nostrings
${device}"/>

the option "--res ${res.bld}" was missing.

BR, Sebastian

> -----Original Message-----
> From: j2m...@li... [mailto:j2me-
> dev...@li...] On Behalf Of James Brook
> Sent: Mittwoch, 20. September 2006 17:10
> To: j2m...@li...
> Subject: Re: [J2me-device-db-general] Plugin Problems
> 
> Thanks for the reply,
> 
> I've just taken the latest version from CVS (at about 3.30 today) and
> rebuilt. I've then taken the framework project example
> mariobros-example.zip. Unpacked it, altered the properties etc.
> 
> Then I've added a new resource called donkey.png and added the following
> to
> the res.bld
> 
> #pngsize on
> +donkey.png
> 
> In the generated device.profile I get the following:
> 
> //#define $full_canvas 1
> //#define $vendor nokia
> //#define $model s60
> //#define $profile nokia/s60
> //#define $nokia 1
> //#define $nokia/s60 1
> //#define $uses.nokia/s60
> //#define $uses.nokia/base
> //#define $uses.generic/midp1
> //#define $midp.version 1
> //#define $cldc.version 1.0
> //#define $mmapi 0
> //#define $btapi 0
> //#define $nokiaapi 1
> //#define $siemensapi 0
> //#define $samsungapi 0
> //#define $vscl 0
> //#define $wmapi 0
> //#define $mascotapi 0
> //#define $m3gapi 0
> //#define $pdaapi 0
> //#define $locationapi 0
> //#define $webservicesapi 0
> import javax.microedition.lcdui.*;
> import javax.microedition.midlet.*;
> import javax.microedition.rms.*;
> //#define $uses.includes/nokiaapi
> import com.nokia.mid.ui.*;
> import com.nokia.mid.sound.*;
> //#define $nokiaapi.ott 1
> //#define $nokiaapi.wav 1
> //#define $key.up -1
> //#define $key.down -2
> //#define $key.left -3
> //#define $key.right -4
> //#define $key.softleft -6
> //#define $key.softright -7
> //#define $key.clear -8
> //#define $canvas_class FullCanvas
> //#define $uses.nokia/canvas_176x208
> //#define $canvas.width 176
> //#define $canvas.height 208
> //#define $icon.width 42
> //#define $icon.height 29
> 
> Which is missing the donkey properties.
> 
> Is there a step I'm missing, or is this a bug?
> 
> Cheers,
> 
> James Brook
> 
> ----- 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

Re: [J2me-device-db-general] Plugin Problems

[James B. <jm...@ho...>]

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
>
>