Jump to content
Excelsior Forums

hav

Members
  • Content count

    0
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About hav

  • Rank
    Newbie
  • Birthday 01/01/01

Contact Methods

  • Website URL
    zvonok.perm1.ru
  1. JET 3.6, SWT and AWT

    Search for "xawt" in folder "obj" results with no item. Search for "xsql", "xsnd", "xrmi" and etc. gives to me the same result, but this DLLs appears in package. Later... I found in deep of java stack trace classes, wich compiled into "xmia" DLL (this classes used for serialization). This DLL invoked another DLLs ("xawt" and etc.) But I solve this problem: I learn how to JET compiled DLLs, find jet.prj for my jre and make some upgrade: move needed classes to "xkrn" DLL and recompile. As result application memory usage becomes 23Mb (with all DLLs was 48Mb) and reduced package size. Resume: Why super-differed packages like sun.applet and deep-end sun.security.provider packed into one DLL? This is no good! I hope that in JET 4.0 I'll do this operation without hacks. But JET stills great thing (with my upgrade)! Best regards!
  2. JET 3.6, SWT and AWT

    Of course I do it, before post the message.
  3. JET 3.6, SWT and AWT

    Hi! I use JET3.6 Professional for Windows for project under pure SWT, but after JetPackII in distributive I found XAWT36024.dll. Why? Can I drive process DLL adding? Sorry for English, but your forum don't know Russian.
×