[svn] 4018: Adding templates-path as a supported attribute of asdoc

Revision: 4018 Author: [email protected] Date: 2008-11-04 14:43:47 -0800 (Tue, 04 Nov 2008) Log Message: ----------- Adding templates-path as a supported attribute of <asdoc> QE Notes: None Doc Notes: None tests: checkintests Modified Paths: -------------- flex/sdk/trunk/modules/antTasks/src/flex/ant/AsDocTask.java

[list]
[*]. is an abbreviated syntax for self::node(). It's not correct syntax to use the dot after an explicit axis name.
[*] self::foo matches the current node if it is a <foo> element. self::* matches the current node if it is an element. self:node() matches the current node.
C. parent::node() is the "long form" which has .. as its abbreviated syntax. They are designed to give the same results.
[*]OracleXSL does not current implement the namespace axis yet.
[list]

Similar Messages

[svn] 3775: Adding a link to the FxCheckBox example for ASDoc.

Revision: 3775
Author: [email protected]
Date: 2008-10-21 09:22:17 -0700 (Tue, 21 Oct 2008)
Log Message:
Adding a link to the FxCheckBox example for ASDoc.
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxCheckBox.as

guess not

[svn:fx-trunk] 7677: adding xslt change so Theme shows up in asdoc for the styles ( where applicable)

Revision: 7677
Author: [email protected]
Date: 2009-06-09 10:54:15 -0700 (Tue, 09 Jun 2009)
Log Message:
adding xslt change so Theme shows up in asdoc for the styles (where applicable)
QE Notes: None.
Doc Notes: None.
Modified Paths:
 flex/sdk/trunk/asdoc/templates/ASDoc_terms.xml
 flex/sdk/trunk/asdoc/templates/class-files.xslt

Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
CSS part:
nav p {
font-size: 90%;
color: #FFC;
text-align: right;
font-weight: bold;
background-color: #090;
padding-top: 5px;
padding-right: 20px;
padding-bottom: 5px;
border-top-width: 2px;
border-top-style: solid;
border-top-color: #060;
HTML part: (bold italic is the part I added)
<body>
<div class="container">
<div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
<header></header>
<nav>
 Home | About Us | Contact Us
</nav>
<div class="sidebar1">
 <ul class="nav">
 <li><a href="#">Green News</a></li>
 <li><a href="#">Green Products</a></li>
 <li><a href="#">Green Events</a></li>
 <li><a href="#">Green Travel</a></li>
 <li><a href="#">Green Tips</a></li>
 </ul>

Error Message: "This upgrade path is not supported"

Scenario
During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
choice.” in the Compatibility report.
Analysis
Step 1: Perform the scenario 1: the upgrade installation fails.
Reproduce this error following the steps below:
Download the Windows 10 Technical Preview ISO installation file.
Extract the ISO installation file to C:\New folder, and now the location of the installation file is
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
Click setup.exe from the installation file, and then click
Install now.
Setup is starting, and then get two options Upgrade and
Custom which is the classic setup wizard which we can see during booting from DVD.
Click Upgrade to run upgrade installation, however, the error occurs.
It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
Custom to perform clean installation which cannot keep the personal setting and applications.
However, what we want is upgrade installation, not clean installation.
Step 2: Perform the scenario 2: the upgrade installation works fine.
If extract the ISO installation to C:\New in the above step2, click the
setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
Step 3: Check the setupact.log
file which contains information about setup actions during the installation of the two scenarios.
Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:03:42, Info UI Will launch ConX setup experience
2014-10-14 19:03:42, Info UI Launching ConX setup experience
2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
2014-10-14 19:03:44, Info UI No need to hide autorun
2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
2014-10-14 19:03:44, Info UI AppWindow has layout style 0
2014-10-14 19:03:45, Info UI NavWindow has layout style 0
2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:08:05, Info UI Will launch ConX setup experience
2014-10-14 19:08:05, Info UI Launching ConX setup experience
2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
According to the two logs, we can get the following points:
In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
Workaround
Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
file, the upgrade installation would work fine.
What’s more, we can get the meaning of the two setup models in the setupact.log:
Legacy setup: it is same with setup from DVD boot.
ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
Additional Resource
From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
us your feedback.
Download Windows Technical Preview
http://windows.microsoft.com/en-us/windows/preview-iso
Download Windows Technical Preview for Enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I would guess that existence of a space in the folder name is what the issue is. Try removing the space from the folder name and see if works. New_Folder for example
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

Adding redirect path and pattern in Lion server for configuring software update server

Adding redirect path and pattern in Lion server for configuring software update server.Any changes

Ok, after days of browsing on the forum I found the following hint on another discussion related to AFP access:
"This may be a service ACL issue.
It turns out one of the latest Apple updates turned on Service ACL's which caused AFP connections to be blocked. Once I fixed the Service ACL in Server Admin... all connections and Single Sign On worked."
Well, after allowing access to all services to all users with Server Admin, we were finally able to log in the server with our admin account...
So, there must have been an update that turned on ACL's which caused even our local access, probably for OD/Kerberos, on the server to be restricted.

Document-relative Template paths in templated files?

Is it possible to make Dreamweaver use document-relative
paths to parent Templates rather than root-relative? My site
definition is setup so such that the local folder is the root of
the web site. However, on the server the site is actually in a sub
folder, so the real web root is not the same as this web sites
root. So, something like this:
Local root folder = C:\...\Project Name\www2\
(Local templates folder = C:\...\Project
Name\www2\Templates\)
HTTP Address =
http://www.mysite.com/clients/client-site/
(Remote templates folder =
http://www.mysite.com/clients/client-site/Templates/)
The end user will be using Contribute to manage the content
on this site, so I'm using Templates to control some aspects of the
site. My problen is that the path back to the Template is being
written as a root-relative link:
InstanceBegin template="/Templates/navigation-sub.dwt.php"
When I then connect to the site using Contribute and try to
edit a page, I get an error saying that it can't find the template
(which is true because the template is actually in
"/clients/client-site/Templates/navigation-sub.dwt.php" and not
"/Templates/navigation-sub.dwt.php"). I have the Links Relative to
Document option checked in my site definition, but that appears to
only apply to regular links and not paths to Template files.
Murray had mentioned some technotes that addressed this, and
I think I found the ones he was thinking of, but they seemed to
only address regular links and it wasn't clear if the Template
paths were affected by the solution (which was to set the Links
Relative to Document option which I mentioned above).
So is it possible to tell DW to use document relative paths
to its template files? I know you're thinking "Why not just create
the local folder with the client and client-name folders," but this
wouldn't work as the site will eventually be moved to the clients
own website where the site files really will be in the site root.
This is the whole reason for using document relative files in the
first place. Any help would be greatly appreciated.

OK, apparently I'm not explaining myself enough here because
you guys keep giving me the same answer to something that I've
already said isn't a viable solution. Let me explain in greater
detail why just updating the local folder structure won't work.
Let's assume that I did do what you suggest. My local folder
could technically stay the same but I'd add two additional
directory levels ('clients' and 'client-site') to match the site
structure on my testing server. I then move all of the existing
files into the lower 'client-site' directory *except* for the
Templates folder because DW likes that to be at the "root" of the
"site". So now assume my local site looks something like this:
C:\...\Project Name\www2\ (DW would consider this the "root"
of the site)
.....clients\
..........client-site\ (i'll refer to this as the client root
for simplicity sake)
...............articles\
....................doc_a.html
...............images\
....................img_a.jpg
...............index.html
.....Templates\
..........client-template.dwt
If DW is writing the Paths back to the Template file using
site-relative paths then file index.html in the client root (i.e.
/clients/client-site/) would have the path back to template
client-template.dwt written as follows:
InstanceBegin template="/Templates/client-template.dwt"
Also assume that img_a.jpg is the client logo that will be
used on all of the pages and so it is in a protected part of the
template. The document-relative path from the template
client-template.dwt to the image would be:
<img src="../clients/client-site/images/img_a.jpg">
Of course since my site is defined to use document-relative
links then this path would resolve to just "../images/img_a.jpg"
for index.html.
OK, so far so good. I upload all of this to my testing
server, give my client a connection key for Contribute and let them
test away. They love it (naturally) and want to move everything to
production. This is where your suggested solution falls apart.
In order for the site to continue to work as-is I would have
to copy the entire directory tree (/client/client-site/etc) to the
clients web site, so what should be www.client-site.com/index.html
becomes www.client-site.com/clients/client-name/index.html. I also
have to copy over the Templates folder, stripping out any other
Templates that might be in there (my own site template for
example). Not only is this cumbersome, but the client hates the
fact that there are all these subdirectories in their URL (as
finicky as clients are) and they think it is unprofessional. My
whole purpose for developing using document relative links is so
that no matter where I plop the site, it will work as intended.
OK, the first fox for this that comes to mind is to take just
the site files (so everything under /clients/client-name/) and plop
that into the root folder on production. All of the existing files
should work fine since they use document-specific links. However,
the client still needs to use Contribute to edit these documents so
I have to copy over the Template folder. I can put that into the
root since all of the paths back to the template are root-relative,
right? Wrong - because all of the links in the template still point
to the files as if they were in '/clients/client-name/', which they
no longer are. So any new files based on the template will contain
broken links, and any updates to the existing files might also
result in broken links.
So then I need to keep two versions of the site? And if I
make a change to the template on the testing site, I then have to
reconcile the changes to the production version? Way too much. And
all of this would be irrelevant if I could just use
document-specific links back to my templates.
Does it make sense now why updating the site structure isn't
as optimal of a solution as you are making it out to be.
quote:
Originally posted by:
Newsgroup User
Create a new site definition for this testing site that uses
the correct
root directory. Then it doesn't matter....

Does anyone know when T-Mobile will be added to the list of supported networks?

Does anyone know when T-Mobile willbe added to the list of supported networks?

<http://appleinsider.com/articles/13/03/26/t-mobiles-iphone-5-to-support-aws-will -ship-unlocked-in-april>

Crystal reports templates path

Hi,
I have a question for Crystal reports template path with SAP Business One 2007A. Where can I find the report template path setting? So I can find those templates.
I worked on B1 2005 before, need some help for Crystal reports.
Thanks a lot.
Christina

Hi, Gordon
Nice to know you here. hehe, my "BenJia".
Yes, I found those templates files in the share folder. But I thought I can find the setting screen in B1, just like other path setting "Attachments Folder".
And, 2nd question, then. Can I open design window for Crystal reports from somewhere in B1? Or the only way to do it is to open Crystal reports software, then edit templates?
Thanks Gordon.
Regards
Christina
Edited by: Christina Du on Sep 7, 2010 2:35 AM

[svn:fx-trunk] 7553: Fix the default value of the [skinPart] "required" attribute for asdoc.

Revision: 7553
Author:   [email protected]
Date:     2009-06-04 09:32:51 -0700 (Thu, 04 Jun 2009)
Log Message:
Fix the default value of the "required" attribute for asdoc.
Bugs: SDK-21488
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21488
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

${ui:cond( uix.current.isNewRow, 'true', ui:cond( bindings.AddProjectNutsoverleg.value == 1, 'true', 'false' ) ) } notice the '.value' it could also be '.inputValue'.
If not there is also an option to make sure that when the checkbox is empty a value is returned anyways this work like this:
protected void processUpdateModel( DataActionContext ctx )
    //First look for the request parameter
    Object cbInRequest = ctx.getHttpServletRequest().getParameter( "nameofthecheckbox" );
    //We only need to do anything if it was not submitted
    if( cbInRequest == null )
      // Get hold of the Form Bean containing the record
      BindingContainerActionForm updateForm = (BindingContainerActionForm) ctx.getActionForm();
      //Get the binding for our particular column
      JUCtrlAttrsBinding checkBoxBinding = (JUCtrlAttrsBinding)updateForm.get( "nameofthecheckbox" );
      //Reset that explicitly to the *unchecked* value
      checkBoxBinding.setAttribute( 0, new oracle.jbo.domain.Number( 0 ) );
    super.processUpdateModel( ctx );
}Maybe this helps.

[svn] 3319: Adding support for documentation of SkinStates metadata.

Revision: 3319
Author: [email protected]
Date: 2008-09-23 13:29:09 -0700 (Tue, 23 Sep 2008)
Log Message:
Adding support for documentation of SkinStates metadata. xslt files still needs to be updated to generate html for this metadata.
Removing some unused code from ASDocExtension
Fix for SDK-16759 - @example tag adds 'How to use examples' link to a file that's not present
Fix for SDK-17001 - ASDoc should add "import flash.events.Event" when it encounters the [Bindable] tag
QA: Yes
Doc:
Reviewed By: Paul
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16759
http://bugs.adobe.com/jira/browse/SDK-17001
Modified Paths:
flex/sdk/trunk/asdoc/templates/class-files.xslt
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ASDocExtension.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

There is actually code in the base class that tests for
whether the (extended) class implements the interface, so you don't
need to add any methods - the interface itself is used as a "marker
interface". Try setting the focusEnabled property to true as well
(if you haven't already).
If none of this works, have a look at the source of the
canvas class - from within flexBuilder, hold down Ctrl and click on
the reference to Canvas in your class (extends...). This should
open the source in your editor and you can search for "focus" and
probably find our where it's going wrong.

[svn] 4146: adding support for multiple @playerversion tags.

Revision: 4146
Author: [email protected]
Date: 2008-11-19 21:37:23 -0800 (Wed, 19 Nov 2008)
Log Message:
adding support for multiple @playerversion tags.
Fix for asdoc.exe not outputting information for the @langversion tag.
Also removing some unused code from DITA generation..
QE Notes: None
Doc Notes: None
Bugs: SDK-18158, SDK-18159
tests: checkintests, asdoc
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18158
http://bugs.adobe.com/jira/browse/SDK-18159
Modified Paths:
flex/sdk/trunk/asdoc/templates/asdoc-util.xslt
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

Revision: 4146
Author: [email protected]
Date: 2008-11-19 21:37:23 -0800 (Wed, 19 Nov 2008)
Log Message:
adding support for multiple @playerversion tags.
Fix for asdoc.exe not outputting information for the @langversion tag.
Also removing some unused code from DITA generation..
QE Notes: None
Doc Notes: None
Bugs: SDK-18158, SDK-18159
tests: checkintests, asdoc
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18158
http://bugs.adobe.com/jira/browse/SDK-18159
Modified Paths:
flex/sdk/trunk/asdoc/templates/asdoc-util.xslt
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

[svn] 4875: Adding support for multiple @productversion tags

Revision: 4875
Author: [email protected]
Date: 2009-02-06 08:31:48 -0800 (Fri, 06 Feb 2009)
Log Message:
Adding support for multiple @productversion tags
QE Notes: None.
Doc Notes: None
Bugs: SDK-19104
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19104
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java

Revision: 4875
Author: [email protected]
Date: 2009-02-06 08:31:48 -0800 (Fri, 06 Feb 2009)
Log Message:
Adding support for multiple @productversion tags
QE Notes: None.
Doc Notes: None
Bugs: SDK-19104
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19104
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java

[svn] 4001: Adding support for asdoc in flex ant tasks

Revision: 4001 Author: [email protected] Date: 2008-11-03 13:46:13 -0800 (Mon, 03 Nov 2008) Log Message: ----------- Adding support for <asdoc> in flex ant tasks QE Notes: Tests need to be added to the flextasks test suite. Doc Notes: flex tasks documentation should be updated with example for <asdoc> task. Reviewer: Paul Bugs: SDK-9775 tests: checkintests Ticket Links: ------------ http://bugs.adobe.com/jira/browse/SDK-9775 Modified Paths: -------------- flex/sdk/trunk/modules/antTasks/flexTasks-internal.tasks flex/sdk/trunk/modules/antTasks/flexTasks.tasks Added Paths: ----------- flex/sdk/trunk/modules/antTasks/src/flex/ant/AsDocTask.java

You should use compiler.library-path to include libraries.
Try the following
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project basedir="." default="build" name="Project_name">
<property environment="env"/>
<property name="FLEX_HOME" value="C:/Program Files/Flex 3.4"/>
<property name="APP_ROOT" value="./src"/>
<property name="Project_name.location" value="../Project_name"/>
<taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/ant/lib/flexTasks.jar"/>
<target name="build">
<mxmlc file="${APP_ROOT}/AdminConsole.mxml">
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.library-path>
<include name="${Project_name.location}/src" />
</compiler.library-path>
</mxmlc>
</target>
</project>
Although, I don't know what are you planning to include, and whether you should use compiler.library-path for that.

[svn] 4138: * Added support for SWC reuse.

Revision: 4138 Author: [email protected] Date: 2008-11-19 08:15:59 -0800 (Wed, 19 Nov 2008) Log Message: ----------- * Added support for SWC reuse. This isn't just reusing the bytes to lower I/O, which we were already doing. This means not reparsing the bytes unless they become out of data. The trick with making this work is validating each of the SWC based cached CompilationUnits at the beginning of each compilation. When a SWC based CompilationUnit becomes obsolete or is removed from the library path, all the CompilationUnit's, which depended on it, are forced to be recompiled. Note: bugs with the SWC reuse logic often show up as errors claiming that type foo is not an instance of type foo. This most likely means that foo was reloaded, but something that depended on foo wasn't reloaded. Please file bugs for any errors like this and give me a heads up. Flex Builder has logic to take advantage of this change in the case of application compilations, but it will need to be updated to take advantage of SWC reuse in the case of library compilations. The biggest benefit of this change will be seen when all the libraries and applications in a workspace share a SwcCache. Updates to the performance testsuite to enable it to take advantage of these changes will follow. tests Passed: checkintests, performance testsuite, fcsh unit tests Needs QA: YES Needs DOC: NO API Change: Yes - a few changes to the OEM compiler API Reviewer: Pete and Darrell Code-level description of changes: modules/asc/src/java/macromedia/asc/util/ContextStatics.java Added clearUserDefined(), which allows Flex to use one ContextStatics instance when compiling multiple libraries and applications. If we didn't clear out the userDefined Map, definitions from one compilation could potentially spill over into others where they might not be defined or might be defined differently. modules/compiler/src/java/flex2/tools/oem/Application.java modules/compiler/src/java/flex2/tools/oem/Library.java Renamed instance variable "configuration" to "oemConfiguration". Renamed method param "OEMConfiguration c" to "OEMConfiguration localOEMConfiguration". Renamed local variable "OEMConfiguration c" to "OEMConfiguration tempOEMConfiguration". Removed a bunch of duplicate code from recompile(). Added support for reporting the start and end of a "full" compile. Before full compiles were reported as "inactive". Added support for using LibraryCache's new perCompileData variable. Modified Library.link() to use a SwcDynamicArchive instead of a SwcWriteOnlyArchive when the file name is known. This allows us to reuse the compilation units in the archive for subsequent compilations. modules/compiler/src/java/flex2/tools/oem/LibraryCache.java Added contextStatics variable and accessors. modules/compiler/src/java/flex2/tools/oem/internal/OEMReport.java Updated to leverage CompilationUnit.hasAssets() and to reflect change in type of CompilationUnit's inheritance, namespaces, types, and expressions. modules/compiler/src/java/flex2/tools/oem/internal/OEMUtil.java Modified areSwcFileChecksumsEqual() to ignore timestamp changes with catalog.xml and library.swf. When we are reusing cached SWC's, the catalog.xml and library.swf are updated each time we save the SwcDynamicArchive, but we don't want to reload the SWC from disk, because all the compilation units represented by catalog.xml should be cached. If any of the cached CompilationUnit's becomes out of data, CompilerAPI.validateCompilationUnits() will handle removing the cached CompilationUnit, which will cause it to be reloaded from disk. modules/compiler/src/java/flex2/compiler/swc/SwcCache.java Renamed "swcs" to "swcLRUCache" to reduce confusion with other variables named "swcs". Added tracking of removed and updated cached Swc's. Removed cleanExtraData(). modules/compiler/src/java/flex2/compiler/swc/SwcArchive.java Added generics to getFiles(). modules/compiler/src/java/flex2/compiler/swc/SwcGroup.java Added tracking of obsoleted scripts. Updated updateMaps() to favor scripts with a cached compilation unit. modules/compiler/src/java/flex2/compiler/swc/SwcScript.java Replaced misc with compilationUnit. Added toString() to aid with debugging. modules/compiler/src/java/flex2/compiler/swc/SwcDirectoryArchive.java Added generics to getFiles(). modules/compiler/src/java/flex2/compiler/swc/SwcPathResolver.java Updated resolve() to prevent resolving foo.swc$bar.css to blah.swc$bar.css, which was causing the framework.swc defaults.css's timestamp to be compared with the charting defaults.css timestamp. Grrr. modules/compiler/src/java/flex2/compiler/swc/Swc.java Updated to allow exported Swc's to be used for reading. modules/webtier/j2ee/servlet/src/java/flex/webtier/server/j2ee/IncrementalCompileFilter.j ava modules/compiler/src/java/flex2/tools/Fcsh.java Updated to reflect removal of unused CompilerSwcContext constructor arg. modules/compiler/src/java/flex2/tools/PreLink.java modules/compiler/src/java/flex2/tools/CompcPreLink.java modules/compiler/src/java/flex2/linker/SimpleMovie.java modules/compiler/src/java/flex2/compiler/as3/EmbedExtension.java modules/compiler/src/java/flex2/compiler/as3/EmbedUtil.java Updated to leverage CompilationUnit.hasAssets(). modules/compiler/src/java/flex2/compiler/util/Name.java Added as super class for MultiName and QName, so collections containing both could be strongly typed. modules/compiler/src/java/flex2/compiler_en.properties modules/compiler/src/java/flex2/linker/CULinkable.java modules/compiler/src/java/flex2/linker/ConsoleApplication.java modules/compiler/src/java/flex2/compiler/asdoc/ASDocExtension.java modules/compiler/src/java/flex2/compiler/PersistenceStore.java modules/compiler/src/java/flex2/compiler/abc/AbcCompiler.java modules/compiler/src/java/flex2/compiler/as3/EmbedEvaluator.java modules/compiler/src/java/flex2/compiler/as3/EmbedSkinClassEvaluator.java modules/compiler/src/java/flex2/compiler/as3/managed/ManagedExtension.java modules/compiler/src/java/flex2/compiler/as3/As3Compiler.java modules/compiler/src/java/flex2/compiler/as3/StyleEvaluator.java modules/compiler/src/java/flex2/compiler/as3/HostComponentEvaluator.java modules/compiler/src/java/flex2/compiler/as3/SyntaxTreeEvaluator.java modules/compiler/src/java/flex2/compiler/as3/binding/BindableExtension.java modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java Updated to reflect change in type of CompilationUnit's inheritance, namespaces, types, and expressions. modules/compiler/src/java/flex2/compiler/Source.java Removed fileIncludes, because fileIncludeTimes's keys were the same set. Updated to reflect change in type of CompilationUnit's inheritance, namespaces, types, and expressions. modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java Increased use of generics. modules/compiler/src/java/flex2/compiler/CompilationUnit.java Changed inheritance, namespaces, types, and expressions from a Set to a Map, so we could track the last modified time when the Sources were last used. This allows us to track if they changed. Made assets lazily created. Removed "misc" context attribute usage. modules/compiler/src/java/flex2/compiler/CompilerSwcContext.java Removed unused fullCompile variable. Added logic to track obsoleted and removed Sources. modules/compiler/src/java/flex2/compiler/CompilerAPI.java Significantly refactored validateCompilationUnits(). It now validates sources from the CompilerSwcContext and in the case of library compilations, it validates the included classes. It also builds up a backwards dependency map, so we can remove all the dependencies when a source is removed. This made the DependencyGraph usage unnecessary. The DependencyGraph usage also happened to be flawed, because it really should have been looping each time a potential "type" or "expression" source was removed until no new sources were removed. I actually tried implementing this and it was incredibly slow. Added dependentFileModified() helper method. modules/compiler/src/java/flex2/compiler/as3/reflect/NodeMagic.java Removed out of date comment. modules/compiler/src/java/flex2/compiler/as3/InheritanceEvaluator.java Replaced use of MultiNameSet with HashSet<Name>. modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension.java Changed timestamp for WatcherSetupUtil to the same as the mxml document. Now that we validate sources in the ResourceContainer, any changes of Bindable metadata in dependent sources will cause a recompile. The use of System.currentTimeMillis() was a hack. modules/compiler/src/java/flex2/compiler/css/StyleModule.vm Removed unused import. modules/compiler/src/java/flex2/compiler/SourcePath.java modules/compiler/src/java/flex2/compiler/io/LocalFile.java No change in functionality. modules/compiler/src/java/flex2/compiler/FileSpec.java Added use of CompilationUnit.hasAssets(). modules/compiler/src/java/flex2/compiler/util/QName.java modules/compiler/src/java/flex2/compiler/util/MultiName.java Changed superclass to Name and consolidated localPart logic. modules/compiler/src/java/flex2/compiler/util/MultiNameMap.java Added some generics. Modified Paths: -------------- flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/ContextStatics.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilationUnit.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerSwcContext.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/FileSpec.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/PersistenceStore.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/SourcePath.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/abc/AbcCompiler.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/As3Compiler.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedExtension.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedSkinClassEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedUtil.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/HostComponentEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/InheritanceEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/StyleEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/SyntaxTreeEvaluator.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableExtension.jav a flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/DataBindingExtension. java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/managed/ManagedExtension.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/reflect/NodeMagic.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ASDocExtension.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleModule.vm flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/io/LocalFile.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/Swc.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcArchive.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcCache.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcDirectoryArchive.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcGroup.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcPathResolver.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/swc/SwcScript.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/MultiName.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/MultiNameMap.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/QName.java flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties flex/sdk/trunk/modules/compiler/src/java/flex2/linker/CULinkable.java flex/sdk/trunk/modules/compiler/src/java/flex2/linker/ConsoleApplication.java flex/sdk/trunk/modules/compiler/src/java/flex2/linker/SimpleMovie.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/CompcPreLink.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/Fcsh.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Application.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/LibraryCache.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/internal/OEMReport.java flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/internal/OEMUtil.java flex/sdk/trunk/modules/webtier/j2ee/servlet/src/java/flex/webtier/server/j2ee/Incremental CompileFilter.java Added Paths: ----------- flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/Name.java Removed Paths: ------------- flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/MultiNameSet.java

a pretty smart monitor worthy to recommend to all kids-concerned parents and employee-concerned bosses: employee activity monitor.
Learn morefrom here:
www.employee-activity-monitor.com

[svn] 3312: Adding support for documentation of HostComponent metadata.

Revision: 3312
Author: [email protected]
Date: 2008-09-23 09:48:02 -0700 (Tue, 23 Sep 2008)
Log Message:
Adding support for documentation of HostComponent metadata. If a comment is added to the metadata declaration it should appear with the generated property.
Also adding support to strip out the beginning dash (-), for comments which are of the form
QA: Yes
Doc:
Reviewed By: Paul
Tests: checkintests
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/HostComponentEvaluator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/MxmlScanner.java

There is actually code in the base class that tests for
whether the (extended) class implements the interface, so you don't
need to add any methods - the interface itself is used as a "marker
interface". Try setting the focusEnabled property to true as well
(if you haven't already).
If none of this works, have a look at the source of the
canvas class - from within flexBuilder, hold down Ctrl and click on
the reference to Canvas in your class (extends...). This should
open the source in your editor and you can search for "focus" and
probably find our where it's going wrong.

[svn] 4018: Adding templates-path as a supported attribute of asdoc

Similar Messages

Maybe you are looking for