Prototype available

I am pleased to announce that a prototype version is available for Win32 and Linux32.
We are willing to gather feedback from experts in the field of AOP, bytecode instrumentation, APM and similar techniques.
If you are willing to evaluate this technology and were not contacted please drop me an email at avasseur AT bea DOT com to request participation.
Alex

Hi Pablo,
Your question has nothing to do with AOP, but with JRockit, so you can
direct such questions in the future to jrockit.developer.interest.general .
To answer your question, no, there is no version available for Mac OS.
Regards,
Tiberiu Covaci
JRockit Team
<Pablo Quiroga> wrote in message news:[email protected]..
It is possible to found some version of JRockit to Mac OS X version 10.4.8 ?
thanks
Pablo

Similar Messages

  • First beta prototype of e2publish

    e2publish is a sophisticated AIR application that uses the Text Layout Framework.  I've just made the first beta prototype available of my website.
    http://www.e2easy.co.cc/e2publish.html
    An ambitious project such as this relies on the feedback of test users.  Comments, suggestions, recommendations, ideas, and bug reports.  Let me know what you think?
    A video presentation about this project can be found here:-
    http://e2easy.wordpress.com/2009/10/19/announcing-an-adobe-air-publish-application/
    The most novel feature is way the text arranges itself to warp around the pictures, wherever they are placed on the page.

    Thanks for feedback Richard.  Your comments are very useful for me.  And my replies are useful to me too - as they help me to revisit, rethink, and crystallise my ideas and vision for this project.
    >I wanted to draw more boxes and connect them with arrows.
    In layout mode, you can use the Layout drop-down menu.  It allows you to Create (add) new text boxes, Split an existing text box, or Remove a text box.  It's my fault you didn't see these - and I was already thinking that I should put some buttons next to the layout view, where users will notice them.  UI design is an iterative process.
    There are three pre-set layouts.  One, Two, or Three columns.  I'm not sure about the same layout on every page?  Magazines don't tend to do this. On some pages, text boxes are arranged around images that feature more prominently than the text.
    Soon, I'll add a feature to create text boxes that aren't connected to the flow.  With optional big quotation marks for pull quotes.
    I was thinking of allowing the user to save layouts, so that they can then apply a saved layout to any page.
    >Is the undo stack integrated?  The UndoManager is designed with the hope that other clients can use it and stack their own operations.
    I already have my own undo manager class that I've been using and refining for years.  It works well with my own custom components. Unfortunately, Adobe's UndoManager assumes it runs the whole show.  This frustrated me.  It's a pity that it wasn't designed with adequate hooks to play second fiddle.  In the end, I devised workarounds, and implemented a scheme so that Adobe's UndoManager is controlled from my undo manager.
    >It'd be nice if the ctrl-z and ctrl-y keys worked everywhere and not just over the TLF area.
    I'll get around to it after Christmas, when I'll have access to a windows PC for testing.  Everything works as it should on a Mac.  I just need to implement naive PC menus.  They'll handle keyboard shortcuts properly, and channel everything through my undo manager.  (e2spreadsheet and e2vector also require this.)  Currently, the ability to do ctrl-Z or ctrl-Y inside a text box on a PC causes a problem.  Because it bypasses my own undo manager.
    >The scrollbar doesn't indicate there are more pages or provide a way to switch pages - that's annoying.
    I attempted to write this application prior to the Flash 10 player (before flash.text.engine), with my own textflow mechanism and TextFields.  (I actually made a request to Adobe for a "textflow" mechanism about six years ago! - at least we got there in the end).  TextFields just weren't powerful enough.  I battled against performance issues, and this page-by-page scheme was a compromise at the time to reduce computational complexity.  TextFlow seems powerful enough - I should go back to scrolling over the entire document - you're right.
    >Not sure if your goal is to demonstrate knowledge of TLF and Flash, or to make some sort of word processor.
    This is definitely a conversation I want to have.  This is the first prototype, warts-and-all.  My vision is more than just a word processor.  I want to create a publishing application capable of creating stylised and captivating e-magazine pages.   I wrote something on my blog yesterday, where I called it a potential tablet magazine 2.0 solution.  I made comparisons with "Web 2.0" that allowed non-technical users to collaborate write to the internet, not just read from it.  My vision is to allow enthusiasts to collaborate on their own magazines.  Not just read them.
    So I definitely want to know what you think is missing that would make this more like a real word-processor?  I'm hoping that Squiggly will soon be integrated with the TLF, and I'll be able to put spell-checking in quite effortlessly.
    Bear in mind that I'm working on this in my spare time.  This isn't Buzzword.  Nobody is throwing huge amounts of money at me to do this.  In fact, every day that I work on this, I'm losing money because I could have worked that day for one of my commercial Flex project clients.  So while I want to this project to aspire to a professional standard.  It might take a little longer - I still have my day job.

  • Pre-qualification Test Suites for Device Driver Verification

    Pre-qualification test suites for verification of network and storage device drivers on Solaris(TM) 7 (Intel Platform Edition) are now available. These test suites are prototypes of test suites we plan to make available later this year. We are making the prototypes available for download
    because IHVs (Independent Hardware Vendors) and third-party developers have told us these tests are useful in assessing the readiness of their drivers. Please note that these prototype test suites are unsupported. We welcome your comments, which can be submitted by e-mail to
    [email protected]
    The test suites (NETTests for network drivers, SUNWprtst for storage drivers) are on the Developers Tools page (http://soldc.sun.com/developer/support/driver/tools/). If you're a
    registered user of the Solaris Developers Connection, log on and go straight to this page, then choose the network or storage test suite to download. If you haven't registered yet, go to
    http://soldc.sun.com to register (it's quick and it's free). You'll find links to the test suites under "What's New" on this same page.

    Pre-qualification test suites for verification of network and storage device drivers on Solaris(TM) 7 (Intel Platform Edition) are now available. These test suites are prototypes of test suites we plan to make available later this year. We are making the prototypes available for download
    because IHVs (Independent Hardware Vendors) and third-party developers have told us these tests are useful in assessing the readiness of their drivers. Please note that these prototype test suites are unsupported. We welcome your comments, which can be submitted by e-mail to
    [email protected].
    The test suites (NETTests for network drivers, SUNWprtst for storage drivers) are on the Developers Tools page (http://soldc.sun.com/developer/support/driver/tools/). If you're a
    registered user of the Solaris Developers Connection, log on and go straight to this page, then choose the network or storage test suite to download. If you haven't registered yet, go to
    http://soldc.sun.com to register (it's quick and it's free). You'll find links to the test suites under "What's New" on this same page.

  • Universe Based on ABAP QUERY?

    Hi,
    Can we create a universe based on an ABAP Query( As far as i know its not possible directly to create universe based on ABAP Query). Is there any other way i can create a universe based on ABAP query.
    Thanks,
    SK.
    Edited by: Siva Vallabhaneni on May 22, 2009 5:48 PM

    There is a prototype available from the Labs site which allows to create a Universe on top of an ABAP function and a report in WebIntelligence. It is using the Data Federator technology to translate SQL into ABAP.
    Check it out here:
    SAP BusinessObjects Web Intelligence Reporting for SAP ERP [original link is broken]
    Hope that it helps
    PPaolo

  • Do you use 3D visualizat​ion/graphs​?

    ...if so, I'd love to get your feedback.
    Specifically... 
    Is 3D visualization important in your LabVIEW applications?
    Do you use any 3rd-party tools for 3D visuals?
    What can be improved in LabVIEW in order to meet your visualization challenges?
    Message Edited by chris.b on 09-08-2009 05:27 PM
    Chris Bolin
    LabVIEW Partner Program, CLA

    Dear All,
    Upon multiple customer requests, I started studying LabVIEW on behalf of VSG (Visualization Sciences Group, www.vsg3d.com) in early 2009 to see whether VSG's 3D visualization technology, represented by  Open Inventor (OIV hereafter) SDK and Avizo application, can bring value to the LabVIEW community.
    From a historical standpoint, LabVIEW and OIV/Avizo communities are at two ends of the large data volume and real-time spectrum. OIV/Avizo visualization technology has been adopted in imaging, seismic and numerical simulation where the interpretation of large amount of multi-dimensional, multi-variate, transient data dictates the success of the corresponding applications. On the other hand, data streams coming in and out of LabVIEW applications are processing-time critical and relatively small in volume.  
    While I am fascinated by LabVIEW technology and the wonderful community around it in this initiative, I am also pleasantly surprised the great synergy between LabVIEW and OIV/Avizo.
    There are a number technology trends that have lead to this synergy,
    1. Advances in data acquisition hardware continues to drive down the cost and improve the performance, which resulted in an explosion of data size.
    2. There are increased number of applications with requirements on both real-time, hardware in-the-loop and interactive 3D.
    3. A significant growth of the needs on comparing and fusing data from experiments and simulation.
    The findings of this initiative is documented by an invited talk at NIWeek and a LabVIEW-Avizo integration prototype, available through these two links respectively,
    http://www.vsg3d.com/vsg_sol_avizo_labview.php
    http://decibel.ni.com/content/docs/DOC-6054
    The prototype developed in this project is fairly simple. It is serving as a proof-of-concept that Avizo can be a nice complimentary tool to enhance LabVIEW's 3D capability. In the light of better serving LabVIEW user community, it will be extremely valuable to get your feedback regarding the questions that Chris initiated above.
    This initiative has been support at the very beginning by NI, and would not be possible otherwise.
    Regards
    Shawn Zhang ([email protected])
    VSG - Visualization Sciences Group

  • New version of the prototype (1.2) now available!

    A new version of the generics prototype has been
    posted at
    http://developer.java.sun.com/developer/earlyAccess/adding_generics/

    Were covariant return types removed from the compiler? I tried compiling this code:
    import java.lang.reflect.*;
    class Base implements Cloneable {
        public Base clone() { return null; }
    class Derived extends Base {
        public Derived clone() { return null; }
    public class Generic {
        public static void main(String[] args) throws Exception {
            Method m = Derived.class.getDeclaredMethod("clone", new Class[] { });
            System.out.println(m.getReturnType());
    }And got these errors:
    Generic.java:4: clone() in Base cannot override clone() in java.lang.Object; att
    empting to use incompatible return type
    found : Base
    required: java.lang.Object
    public Base clone() { return null; }
    ^
    Generic.java:8: clone() in Derived cannot override clone() in Base; attempting t
    o use incompatible return type
    found : Derived
    required: Base
    public Derived clone() { return null; }
    ^
    2 errors
    I think this same program compiled without error with the first version of the generic compiler.

  • Missing prototype and Undefined Symbol errors

    So, I am using an Opal Keyy XEM3005 board.
    Depending on the documentation I read, this board has a native ANSI C interface with a C++ wrapper.
    In their forums, they say to rename the ".cpp" file to "c", and then go forward with calling the default constructor & keep track of the pointer.  Their functions are all in an externally loadable DLL.
    Well and good.
    Their API documentatin is available here:  http://www.opalkelly.com/library/FrontPanelAPI/
    I have written a REALLY simple app to ease my way in - it does nothing more than allow the user to throw a switch, and when this happens, it goes off to connect to the board:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    #include <cvirte.h>
    #include <userint.h>
    #include "Try1.h"
    #include "XEM.h"
    #define _WIN32_WINNT 0x0501
    //#define _WIN32
    #include <windows.h>
    static int panelHandle;
    static okFrontPanel_HANDLE    XEM_Device;
    int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance,
    LPSTR lpszCmdLine, int nCmdShow)
    if (InitCVIRTE (hInstance, 0, 0) == 0)
    return -1;    /* out of memory */
    if ((panelHandle = LoadPanel (0, "Try1.uir", PANEL)) < 0)
            return -1;
        DisplayPanel (panelHandle);
        RunUserInterface ();
        DiscardPanel (panelHandle);
        return 0;
    int CVICALLBACK Connect (int panel, int control, int event,
            void *callbackData, int eventData1, int eventData2)
        int    Value = 0;
        switch (event)
            case EVENT_COMMIT:
                GetCtrlVal(PANEL, PANEL_CONNECT_SWITCH, &Value);
                SetCtrlVal(PANEL, PANEL_CONNECT_LED, Value);
                if( Value )
                    XEM_Connect(XEM_Device);
                else
                    XEM_Disconnect(XEM_Device);
                break;
        return 0;
    int CVICALLBACK Quit (int panel, int control, int event,
            void *callbackData, int eventData1, int eventData2)
        switch (event)
            case EVENT_COMMIT:
                QuitUserInterface (0);
                break;
        return 0;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    This, of course, works fine by itself (with empty _Connect() and _Disconnect() functions)
    I then started working with the XEM_Connect function.
    The first step is to run their LoadDLL function as such:
    int XEM_Connect ( okFrontPanel_HANDLE    XEM_Device )
        int    NoDevices = 0;    //    Number of devices attached to the PC
        //    Load the DLL (?)
        // Load the FrontPanel DLL
        if (FALSE == okFrontPanelDLL_LoadLib(NULL))
            printf("Could not load FrontPanel DLL\n");
            exit(-1);
        return XEM_SUCCESS;
    And this would compile and run just fine.
    Now, when I added the functions to start trying to get info about the device, I started getting "missing prototype" errors.
    int XEM_Connect ( okFrontPanel_HANDLE    XEM_Device )
        int    NoDevices = 0;    //    Number of devices attached to the PC
        //    Load the DLL (?)
        // Load the FrontPanel DLL
        if (FALSE == okFrontPanelDLL_LoadLib(NULL))
            printf("Could not load FrontPanel DLL\n");
            exit(-1);
        //    Find out how many devices are attached
        XEM_Device = okFrontPanel_Construct(  );
    //    XEM_Device = okCFrontPanel( void );
    //    NoDevices = GetDeviceCount( );
        printf("%d OK devices attached\n", NoDevices);
        //    Call the contructor?    
    //    okCFrontPanel ();
        return XEM_SUCCESS;
    Now, I searched the forums and found the bits about adding #define _WIN32_WINNT 0x0501 prior to inclusion of windows.h.  Did that.  No joy.
    Then I searched some more and found the bit about changing the build options to uncheck the "prototype required" flag.
    Done.
    This seemed to work at first (the above code could be built with no errors, and appeared to run).
    So I thought maybe I had it, and added the next line, so:
    int XEM_Connect ( okFrontPanel_HANDLE    XEM_Device )
        int    NoDevices = 0;    //    Number of devices attached to the PC
        //    Load the DLL (?)
        // Load the FrontPanel DLL
        if (FALSE == okFrontPanelDLL_LoadLib(NULL))
            printf("Could not load FrontPanel DLL\n");
            exit(-1);
        //    Find out how many devices are attached
        XEM_Device = okFrontPanel_Construct(  );
        OpenBySerial( XEM_Device, "UaLgzvVpBJ" );
    //    XEM_Device = okCFrontPanel( void );
    //    NoDevices = GetDeviceCount( );
        printf("%d OK devices attached\n", NoDevices);
        //    Call the contructor?    
    //    okCFrontPanel ();
        return XEM_SUCCESS;
    Now it doesn't complain about no prototypes (duh), but instead I get linker errors:
        Undefined symbol '_OpenBySerial@0' referenced in "XEM.c".
    So, dredging through the .h and .c files, I found a couple of things:
    in the okFrontPanel.c file I found the following:
    okDLLEXPORT ok_ErrorCode DLL_ENTRY
    okFrontPanel_OpenBySerial(okFrontPanel_HANDLE hnd, const char *serial)
        if (_okFrontPanel_OpenBySerial)
    ;  return((*_okFrontPanel_OpenBySerial)(hnd, serial));
        return(ok_UnsupportedFeature);
    In the okFrontPanel.h file I found:
    and also:
    okDLLEXPORT ok_ErrorCode DLL_ENTRY okFrontPanel_OpenBySerial(okFrontPanel_HANDLE hnd, const char *serial);
    So, I see them in the .h & .c files, but the linker is bombing out.
    I smell a problem with actual code to link being in the DLL...  How do I resolve this, any ideas?  Or am I doing something so stupidly (and obviously) wrong that I'm being blinded to it?

    Hi tomii,
    My suspicion is that these issues are due to using a C++ dll in a C environment. There are inherent challenges with performing such an operation as you have to make sure all your parameters and settings are correct.
    I also could not find the documentation that the Opal Kelly dll is ANSI C but it sounds like you can use this in C with some reconfiguration. I would recommend using their forums to get more information on what steps need to take place to get things working in ANSI C.
    From the information you provided, I did find some resources on the missing prototype error and undefined symbol issue with the linker.
    For the missing prototype I found a thread of someone actually using LabWindows and seeing this compiler error you may want to look at
    http://bytes.com/topic/c/answers/695019-missing-prototype
    I found a few cases where using a function definition of int func(void) removes such issue when int func() does not.
    Another link I found that may be worth a look can be found at http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html
    It gives some good pointers to mixing C and C++ code. Some of it may be applicible in your case.
    And, a resource for your undefined symbol linking issue.
    http://www.cprogramming.com/tutorial/compiler_linker_errors.html
    Hopefully these resources will give some context for getting things compiling and working with your dll.
    Good luck!
    James W.
    Applications Engineer
    National Instruments

  • Behaviours not working in PDF prototype [click-through]

    I'm trying to create a click-through PDF using Behaviours to swap out images onClick. My aim is to create a prototype PDF of a website for my Portfolio by mimicking a Spry Widget.  Please see image below.
    FYI:  I do have an issue with the Main-Nav which uses simple slices linked to their named page [via Link in Properties].  These are naturally shared in each page via Web Layer from a Master Page.  This menu doesn't function in Preview mode or once exported or previewed in a browser.[Google].  However, it does click-through in PDF format!  So all good there.
    I'm concerned with the 2nd Nav set; 1.1 to 1.9.  A simple set of rectangular Slices linking to the content area below - a single large rectangular Slice.  These Slices are not in the Master Page but located in the Design page of my document, and in all the States of the Design page, of which there are 12 in total. This Nav bar has simple UP, OVER and DOWN States that swap-out and seem to work fine and click-through OK, if previewed in a browser and in Preview mode within Fireworks. 
    However, click-through does not function in a PDF.  Each nav-tab Slice is using Behaviours: onMouseOver | Set Nav Bar Image and the second Behaviour being: onClick Swap Image, then names the correct slice to show onClick in the Behaviours' Panel.
    I have tried variations such as adding a Hotspot to create a hand on rollover and clicked and unclicked various Behaviour options in the Behaviours Panel to no avail.  I wondered if it was a PDF option that needed fixing much like when exporting a file from InDD but I can't find a suitable PDF option.  I read elsewhere about not using Animated Gif as an Image File Type but that didn't work either.  When I export to PDF, there aren't the Slice Save options available for PDF.  Also Fireworks defaults to export to Acrobat Pro, though if I view in Pro or Reader the click-through still fails.
    I'm fairly new to Fireworks but would really like to get to grips with it and I love this prototype wizardry.  I'd like to know why the click-thru fails in PDF but functions in browser and FW Preview and why Main Nav functions in PDF but not browser?
    So any help will be greatly appreciated.
    Blanche

    The original post did not indicate the method of creating the PDF. The result that was obtained was what happens when you print to the Adobe PDF printer. To get the hyperlinks embedded in the PDF, you have to use the PDF Maker (create PDF in WORD 2007).

  • I have now used Reflow for 2 client prototypes and here is what I have found.

    First, I can see Reflow being an incredible prototyping tool if Adobe steps up and makes it a useful tool for production and not just another creative program to help designers build for the web. That's what Muse is for.
    So here is my wish list.
    Reflow needs to be able to have more control over the DOM elements. By that I mean, we should be able to have a layer based approach (similar to what you can see in Macaw) to move elements around from "box" to "box" (also, can't we just call them "divs"). Nesting is crucial. Also, what's up with all the IDs in the published files? We should be able to name and create classes for these elements before it publishes. Also, support the basic HTML tags for users to control.
    On that note, shared elements should have one style sheet instead of a style sheet for each page.
    Also, elements should be able to be saved to a library for use on multiple pages. It is a nightmare now if you create an element on a page that needs to also be placed on other pages. You have to recreate it on each page as of now.
    Support for common CSS frameworks would be an amazing idea...just sayin.
    As for type...Edge fonts and Typekit are great but we all know that there are many other font libraries out there such as Google fonts. Also, being able to use your own @font-face should be an option.
    I think the overall goal would be able to use the files produced as a starting point for production code. As it stands right now, the code that is produced will require more time to format properly than it would be to build from scratch.
    I know Reflow is not meant to be a Dreamweaver or Brackets, but it could really help set the stage for development in those programs. It can improve the workflow of web development vs. just being a "cool new app". It has real potential and I hope it gets the love that it deserves.

    Control over DOM: Yup we're working on exposing this even more. You may or may not have noticed the elements panel already in Reflow. You can find it here:
    Are you looking for more than that? We're looking at ways to expose the elements panel in a better way, that should be coming soon.
    As for stye sheets all being in one, we're debating this. Since we don't know everything you want to do page-to-page, we're holding off making this leap until we can begin cleaning up what CSS we already give you. (see last answer)
    Common library elements: yup, we want  this too. It's on our backlog.
    Frameworks: yup again, on our backlog. Are there frameworks you would prefer? We don't wanna play favorites unnecessarily. We don't know how it might be prioritized, since we've got lots of features to get to.
    Additional fonts: yup for this one too, we have it on our backlog to tackle. As a note, most google fonts are available in the Adobe Web Fonts.
    Output: We're actively working on improving the CSS output from Reflow. We cannot promise perfect production quality, but the issues you raise are all ones we're eager to minimize.
    Thanks for the thorough feedback, we love these kinds of posts!
    - Seth

  • What's changed in the 1.2 prototype.

    The 1.2 prototype has surprisingly little documentation. I started this thread to try to remedy that, in part. I'm going to start off by listing what's I've noticed changed in 1.2, gotchas to watch out for, etc, and I hope you all will follow up below w/ all the rest of the changed things which I haven't discovered yet.
    1) THE COMMAND-LINE scripts/javac TOOL NEEDS THE '-gj' OPTION.
    The previous release didn't. This is a big user-noticible change if you were using the older 1.0-ea prototype in makefiles and such. Note that the 'javac --help' information lists '-gj' as the default; it is wrong. '-nogj' is the default.  I hope this doesn't reflect on the status of GJ in java 1.5?
    2) THE COLLECTIONS API HAS CHANGED.
    This is made more interesting by the fact that this release doesn't come with any javadoc and (as far as I know) javap still crashes when given GJ .class files. The only way to tell that the interface
    has changed out from under you is the javac error message which you will sometimes get when you try to extend a Collection class
    with a now-incorrectly-typed method. (Other times, javac will just crash.)
    The changes I have seen have altered the signature of addAll, putAll, and similar methods from:
    class Collection<V> {
       boolean addAll(Collection<V> c);
    }to
    class Collection<V> {
       <T extends V> boolean addAll(Collection<T> c);
    }Note that this gives you much more flexibility and restores covariance in some ways; but it also breaks all your Collection subclasses which override methods with the now-obsolete signatures.
    Are there any other similar method changes to watch out for? Post below; if the 'offical' javadoc for this 1.2 prototype release isn't forthcoming 'soon' I'll probably hand-edit the 1.0 prototype javadoc to be correct for the new release and post it on the web for everyone to use pro tem. (But it would be nice if the Sun folk did this themselves, so I wouldn't have to bother, hint, hint!)
    3) NO MORE JAVADOC. Mentioned above; hope you've got a copy of the 1.0 javadoc lying around still.
    4) BUGS FIXED. As pnkfelix noted in another post here, some type-system loopholes have been fixed in this release. Also, the bugs which prevented casts from Set to Collection and from Set to Set<T> appear to have been fixed. The bad-line-numbers-on-non-Unix-platforms bug is reputedly gone. Further, it seems that this release compiles non-GJ code better. I'll probably post more on these issues as I get a little more experience w/ this new release. Does anyone else have 'favorite' 1.0-prototype bugs which were fixed in this release?
    5) ONLY WORKS ON JDK1.4. The last release didn't work on 1.3 either, as far as I can tell. But, regardless, this is the only documented change in this release (according to the CHANGES file in the distribution).
    OK. This feels incomplete. Post below and let's hear what else you've noticed has changed.
    [[[ObObscurePersonalNote: Felix, FLEX now has a GJ port.  'magic-4-0'  These prototype compilers are far too buggy for me to release it on the rest of the group, but I've been playing with it on my own personal branch.]]]

    1) THE COMMAND-LINE scripts/javac TOOL NEEDS THE '-gj'
    OPTION.Thanks for noting this. It may have saved me a lot of time. With only this change, my "Frink" project
    ( http://futureboy.homeip.net/frinkdocs/ , 194 classes with a mix of generic and non-generic code, 25000 lines) recompiled with the new compiler with zero changes. Of course, in the course of building this project, I worked around some bugs in the old compiler.
    * I think that inner classes still don't work as expected. I don't know if this is a bug, but it's a shortcoming. For example, the following code still doesn't compile:
    public class Outer<T>
       private T outerMember;
       public Outer()
          outerMember = null;
       private class Inner<T>
          private T innerMember;
          public Inner()
             innerMember = outerMember;
    }The compilation error is:
    Outer.java:16: incompatible types
    found : T
    required: T
    innerMember = outerMember;
    ^
    1 error
    This isn't a particularly wonderful sample, but often you do want inner classes to be able to access data from the enclosing class (say, the inner class is an enumerator that enumerates over the contents of the outer class.) But you can't. Dang.
    If nothing else, a better error message should be produced. To me, "T" sure looks like "T".
    * The "README" file indicates that the compiled code only works with a 1.3 or later runtime. I've tested with 1.2 and (thankfully) found no cases where it doesn't work (but there may be some.) That would be a showstopper, as many people who use Frink haven't even installed 1.3 yet, and I've worked hard to make it compatible with 1.2, 1.3, and 1.4.
    Does anyone know why the documents say that the compiled code only works with a 1.3 environment? Let's hope it's a mistake. I thought one of the goals of the generic compiler was to create bytecode that could run in any JVM. And compiling with the new compiler shouldn't introduce dependencies on classes that the programmer doesn't reference...
    I do compile with the -target 1.1 flag for maximum backward compatibility.
    3) NO MORE JAVADOC. Mentioned above; hope you've got
    a copy of the 1.0 javadoc lying around still.Gafter's recent comments in this forum indicated that they've not even begun making a version of the javadoc tool that works on generic code. I sorta wished that something magical might have happened since then, but I guess not.
    The bad-line-numbers-on-non-Unix-platforms bug is
    reputedly gone.But Java is write-once-run-anywhere! That's impossible! :) Gafter posted a (one-line) patch for the original compiler to this forum just a week ago. Wish I had it a year ago. That's why I wish that releases would be made more often--it was fixed long ago.
    5) ONLY WORKS ON JDK1.4. The last release didn't work
    on 1.3 either, as far as I can tell. I tried compiling with 1.3 and the new generic compiler, and got this message:
    Exception in thread "main" java.lang.NoClassDefFoundError
    at com.sun.tools.javac.v8.Main.bugMessage(Main.java:490)
    at com.sun.tools.javac.v8.Main.compile(Main.java:477)
    at com.sun.tools.javac.Main.compile(Main.java:36)
    at com.sun.tools.javac.Main.main(Main.java:27)
    The old compiler did usually work with 1.3 (I've used it for about 10 months with 1.3,) except for 4 classes out of 194, which tickled part of the compiler which used the CharSequence class (which wasn't available until 1.4). Luckily, these 4 classes of mine didn't contain generic code and could be compiled with the normal compiler.
    * The new batch file for Windows contains UNIX-style linefeeds. I think that's sorta bad form.

  • Aperture tomorrow's application available today

    On these boards there seems to be a lot of complaints regarding the performance of Aperture. I think a lot of it is due to the fact that people do not realize how ahead of its time the application really is. Aperture is the fist imaging application to leverage the power of a graphics card to perform its RAW conversion and image processing. In fact it is surprising that no one has done this as yet.
    Image processing is one of the few computational tasks that lends itself to highly parallel processing ie; the image can be broken up into small pieces, each piece processed individually and the recombined for the final result. Not surprisingly graphics cards are highly optimized for this type of processing with each card being able to process several of these little pieces simultaneously. The number of pieces that a card can process is defined by the number of “pixel pipelines” the card has. The fastest card to date the ATI X1900 has 48 of these pixels pipelines compared to the hot card last year at this time the 9800 Pro which only has 8 pixel pipelines. If this processing was not done by the graphics card the maximum number of simultaneous processes would be 2 on a dual core or perhaps 4 on a quad.
    As a result of leveraging the power of the graphics card Aperture is able to do RAW conversion and image processing in Real Time. This is a quantum leap in image processing. All the other applications allow you to make approximate adjustments on a low-res version or on a portion of the image. Once you have picked the adjustment the application then goes off and processes the whole image at full resolution while you wait. Aperture does the whole image, at full resolution in Real Time.
    The other major change is that with such fast processing Aperture is able to make all adjustments to the original RAW image. There is never any destructive processing on the image. Eg. Prior to Aperture one of the golden rules was always perform sharpening last. This was due to the fact that sharpening is destructive to the image and if you wanted to make a change after sharpening you would have to hope that you had saved the version prior so that you could go back. With Aperture all these rules are out the window. You can sharpen first, then adjust shadow highlight and then exposure as all adjustments are recalculated from the original RAW each time a change is made…in Real Time. Sharpening is not the only destructive process that is done to an image. In Photoshop you can use ‘Adjustment layers’ for some changes that are non destructive but any change that is not available as an ‘adjustment layer’ you can assume is destructive.
    Prior to Aperture besides the odd game there really were no applications that took advantage of the processing power of the graphics card. As a result, in general, Macs were equipped with relatively low end video cards. The chart below shows the approximate performance of some common video cards. All performance numbers are from PC testing and are only approximates as not all on same motherboard.
    Card...................Memory................Pixel................3DMark 2005
    ......................Bandwidth (GB).........Pipelines ..........1024 x 768 (Approx)
    9600............... 6.4...............................4....................1800
    6600(LE)...........16.............................. 8.....................2000
    6600GT............16...............................8.....................3000
    9800Pro ...........21.............................. 8.....................2600
    X1600..............12...............................12...................5000
    X800XT.............32.............................16....................6000
    X1800XT...........48.............................16....................8000
    7800GT.............38.............................20....................7000
    X1900.................?..............................48..................10000
    As can be seen the standard card that Apple provides even in the PowerMac G5 the 6600 is relatively low end. However it appears things are changing as the new Intel iMacs (consumer grade machines) have the X1600 which is no slouch.
    The other thing to note is that last year this time the hottest cards were the 6600GT and the 9800Pro. As can be seen in only 1 year their performance has been eclipsed. We can assume that ATI and NVIDIA will keep on pushing the envelope which will result in cards getting not only faster but cheaper. Currently the biggest demand for these high end cards is PC gamers, 3D animation and some CAD, however with the release of Vista the demand should greatly increase as the minimum recommended card for the full Aero experience is high end with at least 512MB. The increase in card production for Vista should greatly assist in driving down prices. At least we can be thankful to uncle Bill for one thing
    As we can see Apple is poised with an application that takes advantage of the cutting edge in technology. So while it may seem a lot today to spend $300 to purchase an Aperture optimum card if you hold on that same card will be $200 in six months and probably $100 in a year. Also in a year should you feel you need a boost in Aperture performance you do not need to purchase a whole new computer. Simply an upgrade to the latest video card should result in a significant performance increase.
    While Aperture is the first application to see graphic card based optimization I would not be surprised to see other applications following suit. My guess is if not Lightroom or CS3, CS4 will have at least some filters graphics card optimized. I am also sure this same technology will be used in Final Cut to make more transitions real time.
    Comments welcome.

    <...>
    Let's take a specific example. Open a 12MB Canon 5D
    RAW file in both applications and apply Shadows &
    Highlights, then immediately scroll around the image
    fully zoomed to see the effects (check for noise,
    etc.). This is a fairly typical digital darkroom
    task that works fine in Photoshop after the initial
    few-second hit while it computes the final image.
    Smooth scrolling after that. Aperture? A spinning
    beachball o' death -- for 90+ percent of current
    users. This is NOT the "application of the future",
    but rather the "doorstop of today".
    Not for me, and I have an older computer.
    To more exactly recreate your scenario I downloaded a 5D RAW from here:
    http://www.jirvana.com/rawlarge/canon5d
    And used that. Granted both Shadows/Highlights were a bit jumpier than I normally see (as I work with imported TIFF files) as was scrolling - but not once did I see the beachball at all.
    Lightroom by comparison (same file) felt a little faster adjusting, but it's kind of a pointless comparison since it also decreased the image resolution by a factor of four while doing so making live preview less useful as a feature since I had to wait for the image to clear up before I could really see what happened. Scrolling was smoother but still jerky.
    Look down there at my specs and tell me they are so unreasonable to be working with a really large RAW file. I don't even think I'm in that upper 10% of Mac users right now.
    And exactly which piece of information from Apple was
    supposed to make it possible for people to stand a
    chance at "realizing" this? Oh, that's right, those
    "recommended" hardware specs. How silly of them to
    trust the literature and the box.
    I would say however the recommendations fail mostly for the 6600 - as I said some people are happy with Aperture on a 12" TiBooks. Some people like you are suffering using Aperture on a fairly powerful computer while at the same time some people struggle to find cracks so that the can install and use Aperture on computers that are below even the minimum specs, so it's a hard thing to say what should be on the list and what shouldn't since people buy the software for different needs.
    <...>
    For Quake 4, yes. For what Aperture's doing? No
    freakin' way. I've done what Aperture's (or Core
    Image, depending on how they broke it out) doing with
    SIMD instructions and it works just fine.
    You are underestimating what is going on there, and Aperture is trying to do it through a general purpose API, not hand tuned assembly. I am pretty sure there are some inefficiencies in all the layers there which will get baked off over time, Aperture is really the first app to make heavy use of Core Image.
    Why should Aperture not suffer as greatly at the
    hands
    of a less dedicated processor?
    My point exactly, thanks!
    ?? - I was actually saying that Aperture would downgrade just as much running on the CPU only as a video-card dependent game would, as it is equally dependent on the specialized features of the video card to perform well.
    Have you ever heard about newer video cards
    removing features?
    Yes.
    Not to the extent that API's cannot work around it. I'll admit that was hastily penned.
    <...>
    It'll suffer if Core Image has to start emulating
    things.
    So give us an example of something Core Image is doing that may have to be emulated in the future?
    Although you walk a fine line complaining the CPU can easily do the same work while at the same time complaining that API performance will downgrade if the API has to switch to use the CPU...
    It's not doing that in the case of the 6600 card.
    Perhaps its speed-detection routines need
    recalibration?
    I think you'd see Aperture run an order of magnitude slower by running using only the CPU instead of the GPU.
    Actually I think you could even test it. There may be debugging features in the dev kit (perhaps even the same profiler tools you were using) that let you disable use of the GPU by CoreImage and see how well it works.
    <...>
    Hmm. How big are your RAW files? Shadows &
    Highlights is the worst one on the 6600 -- delays are
    in the TENS of seconds. This is especially
    problematic when trying to scroll around within an
    image.
    As I said I don't even see a beachball on the 5D files, it's just a little jerky. Normally I work with TIFF files directly which I'll grant are faster than working with RAW.
    Any my card is roughly half again as slow as the x800XT card according to the only Core Image tests I've seen on both cards. I think I could say that working with 5D files using a x800XT would in fact be pretty reasonable.
    I'm not sure how to note that some power users may
    be not be
    happy with some cards while other users will
    Given this is a "professional" application, who
    exactly would be a NON-power user? And trust me,
    unless you do ZERO adjustments in Aperture you will
    eventually be "unhappy" (understatement of the year)
    with the performance on a 6600 card.
    Actually I think the people using out-of-spec laptops (or perhaps any laptops) are using it for comparison features more than adjustments, until they get back to a desktop. For that use it would work well even with fairly poor video cards.
    Not everyone uses Aperture for the same things.
    I do think that card might be there just because
    it's shipping
    with the Powermacs
    Oh, well, that makes it okay to mislead customers
    then.
    You seem to have missed how that was a critique on my part. I didn't say it was right, just what I thought might be going on there.
    On the other hand as we noted your card should behave about as well as my card, I really don't understand what is going on there unless the 6600 drivers and/or CoreImage support is really, really poor.
    <...>
    But MY point (and the point of many disappointed
    Aperture customers) is that HIS point is completely
    specious and irrelevant. While Apple's goals are to
    be lauded, and even appreciated in a "think tank"
    type environment, they chose to unlease this product
    upon WORKING PROFESSIONALS. They made promises and
    created high expectations. They failed to fulfill
    some very critical ones. That is ALL that matters
    right now to most people.
    <...>
    I don't see your point as fully valid because it IS working for many people today, yes it's a subset of the Apple community but it's not as if everyone was let down. In your case you obviosuly were, but in other cases people got what they expected. I did. After seeing the previews I got exactly the software I was expecting.
    Those defending Apple are blinded to seeing or even
    acknowledging this point, much less conceding it.
    Problems cannot be fixed until they are acknowledged
    and Apple fan boys (not saying you are one!)
    attacking people on for being unsatisfied with
    Aperture and finding it unusable for one reason or
    another are not helping the situation.
    I sympathise with people in your situation, where you have a computer that really should be capible of running the software at full tilt but cannot.
    However many such people don't just vent and move on. They must come and post EVERY time someone actually says they like the software. After about ten or twenty of the same comlaints for the same user, I have to say - we get the point. It's obvious the software is doing you no good. Get a refund, I think anyone who complains loudly enough to Apple can do so though they don't make it easy.
    I don't know if that is the case for you as I don't really follow posting history. But I would say it's perfectly valid to correct posters that over-generalize problems and make people think that ALL users suffer from them when they do not. I only post corrections when I see that to be the case - if people want to complain about specific setups that's perfectly valid and helpful to potential purchasers. What is not helpful is making an x800XT user stay away from the software thinking the experience is going to be a nightmare when in fact it would be far better for them.
    Similarly, telling these upset customers "See, you
    just need to ignore your pain and appreciate how
    GRAND AND WONDERFUL Apple is for "seeing" the future!
    All hail Apple!" is also pointless. It may be
    informative, but it doesn't take away any of the
    sting and it doesn't get them a refund and (worst of
    all) doesn't suddenly make Aperture usable.
    It's not saying that at all. It's just saying that Apple put a lot of thought into the software and is really leaning heavily on some leading edge technology, so give them some slack and recognize that in just a year or two the performance concerns will not really be there for newer users and possibly for some older ones. It may not help now but it's pointing out these problems are more short-lived than they would appear, and that the approach is sound (which I still think it is). Some people seem to think that Aperture performance problems are simply unsoluable, and the original post addresses that.
    <...>
    Well, hopefully the PCI-X cards come soon. In the
    meantime I'll just continue to disagree with the
    assertion that the 6600 is a "low-end" card. I run
    some REALLY SOPHISTICATED software on that card on my
    Windows PC. There's no excuse why it can't handle
    something like Aperture, which is CHILD'S PLAY by
    comparison.
    <...>
    I'm not saying low-end either, more like mid-range. I consider my Radeon 9800 to be bit dated at this point as well and the 6600 is around the same level of performance.
    I'm not saying they aren't. The wrong track they're
    on is being lazy writing software -- the super-wazoo
    card is NOT NECESSARY for Aperture. Heck, you even
    say yourself that your lowly old ATI video card is
    running it in realtime. I think the developers just
    didn't test the application with the 6600 (and
    probably several other cards).
    I do wonder if that is the case (6600 testing). However I don't think they are being lazy exactly - I think they simply focused more effort in getting the Core Image API the way they wanted it and less on tuning actual cards.
    Given the timeframe of software release I'll bet most of the developers were working with Quad G5's though, not the newer dual-core models... probably rectified by now although perhaps they just all jumped to prototype Intel Powermacs (or whatever they will be).
    This is a shame,
    since that's what they sell as the default in
    Powermacs. On a positive note, this is why I expect
    this problem to be fixed. Now that developers are
    aware of the performance issues on the 6600, plus the
    fact that they've sold a lot of them, leads me to
    believe (hope) my performance issues will melt away
    (like butter, even!) with the next point release.
    Please, please, please...
    I have the same hope. You'd think it would be a focus of Aperture though since as you say that card is default on all new Powermacs and they would seemingly want the software to shine there.
    I wonder how much they are reliant on the nVidia driver performing well though, to that extent their hands may be somewhat tied.
    <...>
    So how about giving the application away for free
    until it's good enough to be sold at retail? Why
    does everybody cut Apple slack on this when it's an
    EXPENSIVE and PROFESSIONAL application? Are those
    same apologists as forgiving when they have to wait 6
    months for updates to their favorite game to make it
    playable? Of course not. So why are they THAT
    demanding on a $40 application and yet so forgiving
    on a $500 too? It makes absolutely no sense to me.
    <...>
    But the application is ready for prime time for some users. Some of the early bugs were glaring to be sure but it's definitely a very solid applciation at this point, especially when you look at Lightroom and use the two apps for any length of time. Aperture really is a finished product with a fair amount of polish to it when you look at all the little things it handles well and the detail that has gone into it.
    That's the only option available to some people --
    anyone with a PCI-X video card, for example. The
    more interesting question is why do others choose to
    attack these customers and defend Apple? Who screwed
    who here, for goodness sake? Some people really need
    to back off on their koolaid intake...
    My goal is simply to clarify on what confgurations people may see problems - and where they may not.

  • ProtoType

    Hi,
    Iam new to JDeveloper 3.0. Started working on a prototype for an application which have like 30 to 40 screens. I have
    played with the tool to create screens
    accessing database and Iam at a point trying
    to understand the big picture. My previous
    experience is in Oracle forms and I have
    deployed applications successfully.
    Questions I have are...
    1). What is the recommended approach for
    the application. Ex: Do I have to
    create one single project and in that
    create several screens (*.java) or is
    it better to create separate projects
    for every screen. The screens will be
    accessing oracle 8 database.
    2). How do I call different screens from
    my main screen.
    3). How do I setup a desktop Icon for an
    user to run this prototype. Iam
    looking for complete setup.
    Thanks in advance,
    Kishore Mandava

    Kishore,
    If this will all be one Java Application, then you probably want to store all of your 'screens' in one project.
    Since you are developing against an Oracle datasource, here is what I would recommend:
    1. Create a project that will contain your Business Components. This is basically your data model. For more information on Business Components for java, see the online walkthroughs available on the JDeveloper page of OTN.
    2. Create a separate project for your Java Application. You can use the InfoSwing containers and controls to build your UI.
    Keep in mind that developing and designing a UI in Java is quite different from Oracle Forms. The layout environment specifically can be tricky.
    You may want to check out some of the resources on the JavaSoft website for more information on Infobus controls. They have some tutorials that might be useful.
    Laura

  • I've designed a magazine prototype for a client and I need it to flip pages like a book on an i-pad. What software will do this?

    I've designed a magazine prototype for a client and I need it to flip pages like a book for her sales team to show on ipads. What software will do this?

    The max OS for all Macs with a PowerPC processor is Leopard OS 10.5.x.
    If you are going to consider getting a newer, but used, Mac, here's the requirements for Lion.
    Lion 10.7 System Requirements
        •    Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor (most models released since late 2006 - early Intel-based Macs with Core Solo or Core Duo processors aren't compatible)
        •    2GB of memory (recommend at least 4GB -- and ideally even more, as you'll see benefits in many computing tasks)
        •    OS X v10.6.6 or later (v10.6.8 recommended) for Lion download from Apple App Store; or Leopard 10.5.x if using Lion on USB drive
        •    7GB of available space (10GB recommended)
     Cheers, Tom

  • E90 Firmware upgrade available?

    Hi
    We've currently got a prototype E90 for testing on a development project. The firmware version on it is:
    V 07.11.1.0
    19-3-2007
    RA-6
    Does anyone if it possible to upgrade this? We've been led to believe by Forum Nokia Pro that there is a firmware update available but as yet cant find it. The Nokia software updater page doesnt list the E90.
    Anyone have any ideas?
    Thanks

    YES your firmare is OLD!
    You should have the latest firmware V 07.24.0.3
    You can update your firmare by installing Nokia Software Uptader NSU...
    Regards,
    Lami
    Lami
    Current Phone: Nokia E90, E61i, E50

  • Regarding third party  Software  which genrates screen (prototype)

    Hi ,
    Is there any third party software available which can be use for  generating SAP  screen prototype like without doing coding we should be able to generates screen , and attached to Functional specification as a proposed screen , please suggest or give a name of the software if anyone knows . for example i want a screen to be enhanced with a new field , of a selection screen with two radio button and check box  so any software which will give a prototype of this kind of requirement .
    Thanks in advance
    Rajeev

    Hi,
    Please take a look at this link: www.synactive.com ->Tutorials -> GuiXT
    Regards,
    ScriptMan

Maybe you are looking for