Hi Andrew,

I'm fine with adding more complex output control.  I would caution against 
static things that are shared.  Most places in the compiler have access to the 
ICompilerProject (RoyaleProject/RoyaleJSProject), the ITargetSettings, and/or 
the Configuration.  Feel free to add new members to one or more of these to 
share output options.

The reason to avoid statics is that we want to leave open the option of 
re-creating FCSH or other compiler "servers" that compile more than one 
application or library at a time or compile then in sequence but without 
exiting and re-starting each time.  In the code you'll also see the concept of 
a Workspace.  I don't think it really gets used today, but I think it was 
supposed to map at least roughly to a FlashBuiiler/Eclipse workspace with many 
different projects each with different compile options.

Thanks for offering to help on this,
-Alex

On 6/28/18, 12:52 PM, "Frost, Andrew" <[email protected]> wrote:

    Hi again
    
    Having looked briefly: there is a 'verbose' option already (but it's 
hidden); but it only changes a couple of outputs (of theme information in 
MXMLC.java). I am wondering whether a number of levels would be good rather 
than just "verbose or not", but perhaps that's over-complicating it...
    
    The easiest way to do this would be to use a class with a static function 
to do all the output. Currently there are calls to "System.out.println" dotted 
throughout the code, so we could switch these all to "CompilerOutput.println", 
and have a new "CompilerOutput.verbose()" method too... 
    
    Any objections to a class with a static member function for this? i.e. a 
global function :-)
    
    cheers
    
       Andrew
    
    
    -----Original Message-----
    From: Frost, Andrew [mailto:[email protected]] 
    Sent: 28 June 2018 19:38
    To: [email protected]
    Subject: [EXTERNAL] RE: Migrating Enterprise Flex Application
    
    Sure thing, we'll take a look at this... 
    
    -----Original Message-----
    From: Alex Harui [mailto:[email protected]] 
    Sent: 28 June 2018 17:57
    To: [email protected]
    Subject: [EXTERNAL] Re: Migrating Enterprise Flex Application
    
    Hi Andrew,
    
    Yes, a --verbose flag would be a great idea.  Do you want to volunteer to 
add it?   Could be a good way to get to know the code base.
    
    Thanks,
    -Alex
    
    On 6/28/18, 2:01 AM, "Frost, Andrew" <[email protected]> wrote:
    
        Yes I just tried with your config file, I don't get anything hanging 
although I've got a later Flex SDK so some of the paths/SWC files you're 
including from that are coming up with errors..
        
        Maybe it's worth a slightly more verbose output from the compiler so 
that we can see how far it's getting.. Alex would you think it's worth doing 
something 'official' with a -verbose flag, in case this sort of thing needs to 
be examined in the future? Or it could just be a one-off hack (or using the 
Eclipse debugger to walk through the compilation process to find the issue..).
        
        thanks
        
           Andrew
        
        
        -----Original Message-----
        From: chembali [mailto:[email protected]] 
        Sent: 28 June 2018 09:46
        To: [email protected]
        Subject: [EXTERNAL] Re: Migrating Enterprise Flex Application
        
        I got the nightly build apache-royale-0.9.3-bin-js-swf.zip on June 22. 
It looks like the issue may not be related to the flex-config.xml. I tried to 
compile another component source and it went ahead and compiled the component 
giving a bunch of compile errors. It did not hang though.
        
        
        
        --
        Sent from: 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclicktime.symantec.com%2Fa%2F1%2ForlsiMBzJdC4naKh6jmNWDWIZmfWyRE1hh7_nu4ox48%3D%3Fd%3DTm5ZtgpweIf0znthMCpBeAN9sj7fPueHiDeEtJgEISAuD7VwIEm9M2EoEjhMAVYj-ffkpw39SdD_q98fffbu5K7l5Zd2z7v3LlVQF-7SBkS6gEHHjCsKOgUdEHF9wxG8fm0yMRUHzNjW2UGPNIzdrPWZUesebtTvkD7pPivlBG9ggkc-e7l3veOXJuhOdJymoYw7bXI-kgTbVlOgFkScaW6zEk55ObigVzqNmQgcUIlEBdV3MBQJPaaADxXywFepvZmAncyqtmOmVeo5x3ufl7nnmIly3yDkcK9Y9W66cFZAgPt_nTrdL0_rLfbt0CvMaEV0wQy_hGL_DHSEs_B2jH5u1v00Kv3rC2GBHv0EufuSiUPDh0NC9X40NoGMW470gz5u4ys9y7_eBvAZwKA1mlQ5eoQXcJy3dJJGdVmHRypC0mvP%26u%3Dhttps%253A%252F%252Fna01.safelinks.protection.outlook.com%252F%253Furl%253Dhttps%25253A%25252F%25252Fclicktime.symantec.com%25252Fa%25252F1%25252Fw8-0aepjtghwJrEW5GLyuRkoS-VeQzvX48OL59I1DMk%25253D%25253Fd%25253DOjYvciyyDRLwFT_tUfjYlUA--SsRn5GZapZJdWKYQ6H7T8y5egtT4QsxyO4aNl92BLSp4rGFrBlHLq4Ta6VcLODkcYMaZ7MizXNd0fVujSh3fpenzlFPXntcVkYsWIzK81EpCYgYYMdkM_P4LuDAswrmxQiWPSdBuZOe7tUeI0kiHPX5SAy068B1zgf1H10LmvV8EwdZHLsrXn-GRsOKejIuZ6IVREqX3oz-aAfWWAS_N8JlWMMhtfiv8fpqyp6ci46w4XK4cOLoL3nMdYPPEEIdRbvkJqfDb0tnVNJV2w7I50xWcHCVmVaTDQn-25XAymk5OWyDvZNKi0cyNKrfNmGBUWMa-XqlVtd1aPCkLt0izrYZLRIJkDvsEPH1YVlXPL2mMYgN5DFZzuvASlDHTwIsdZzgb5Yx3w%2525253D%2525253D%252526u%25253Dhttp%2525253A%2525252F%2525252Fapache-royale-development.20373.n8.nabble.com%2525252F%2526data%253D02%25257C01%25257Caharui%252540adobe.com%25257Ce60151af4e8f4a95110908d5dcd5abf0%25257Cfa7b1b5a7b34438794aed2c178decee1%25257C0%25257C1%25257C636657732626882909%2526sdata%253Dw5MQHFUNnBLFfQHJoY2X%25252FsgP2AJrTmRj2TugHEIdqf0%25253D%2526reserved%253D0&data=02%7C01%7Caharui%40adobe.com%7C9ec3e05e0e42421feb9708d5dd30b532%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636658123623215704&sdata=GEjvaMUZb18ufAqBXsU6Gce6ceATftCMkq74BbDRGoA%3D&reserved=0
        
    
    

Reply via email to