Support for css

I'm used to building html pages with sections of <DIV class="..."> and using styles to control all visual layout etc.
Does HTMLDB allow us to use css to break away from the standard layout of logos , colours , layout etc ?

I have read the white paper that you have referred to in your response and have included the following in the Header section of my Reports Region -- I am using a custom CSS to format the Table Headers <th> and the table data <td>:
<head>
<title>Air Road Dispatch Board</title>
#HEAD#
<link rel="stylesheet"
href="#WORKSPACE_IMAGES#test.css"
type="text/css" />
</head>
The table data is working based on the CSS but the table headings are still not working correctly and the substitution string #HEAD# is sending the #HEAD# as output on my report at the top. I understood that by placing the reference to the .CSS after the #HEAD# that it would bypass the classes from the core.css file. But obviously this is not working. I also tried the same code above in the page html header to see if it worked but received the same results.
Any ideas?
Regards,
Jeffrey

Similar Messages

What about support for CSS preprocessors?

I love that Adobe is making all of these advancements in areas of HTML / CSS / JS / etc. but CSS preprocessors are becoming the way to "do things" and this is where I cringe when I have to use Dreamweaver and now recently Edge Code. If Adobe is all about the future, why not start including support for CSS preprocessors (most noteably SASS and LESS)?

I think you would want to support both less and sass mainly because there are so many differnt opinions on what works best, I started out using less and then learned about sass and did a little research and decided sass had more to offer, but I Know there are sever folks who think less is easier to use,
I think your biggest problem is getting people to open up something new such as Edge Code and decide what will this offer me that I can't get elsewhere, for example before I got creative cloud, I started with dreamweaver way back in the early days, latter on when jquery started getting popular I couldn’t seam to get code hinting to work, and there where a few random folks offering a half-assed plugin that didn't always work and between that and not being able to pay for the updates for dreamweaver and other products I looked around and found Aptana which I still use today because so far It has never been unable to do what I need and its free, now that I have just recently started using CC which is freaking awsome Im thinking about giving dreamweaver another shot, in-fact I was downloading it when I noticed edge code and decided to try it, the first thinks that I thought was how am I going to use sass with this.
So that said I think to me the most annoying part of using sass is the setup which consists of the following steps, copy a folder I made and update on my local machine, which has all the basic structure such as css folder, js folder, an index that has the basic linking to folders and files then rename the folder change some of the basic things such as title and well the obvious things, then open terminal and do a sass —watch then carefully make sure I only point to the css folder I'm working in so I don't have the annoying delay you get if you point to a folder that has several projects in it, and then once its set up if I still have any ambitions to even work anymore I do my thing, so things I think would work great would be thus, and this is keeping in mind Im new to the edge products so some of this may already exist, I haven't spent allot of time in any of the apps,
What if not only could I just drag my preset work folder(s) into Edge Code and get going but maybe have it auto start a sass watch if it detects a .sass file.
I think code hinting and color are obvious needs.
Maybe a button that would create a project folder and include some pre determined files in the folder and link to them.
Maybe a option to work in sass mode.
Link files between the edge apps, really I could go on forever I am more of a visual person so I made a sample of what it might look like if I could create a picture with my words and I'm sure I'm leaving things out, I don't have allot of time to really explore this like I would like, over all I think the edge apps are looking really positive and I can't wait to see where they go, I hope this helps and let me know if I over looked things.
cid:0A2D995B-A35B-45BC-82F6-3E7D1C582E35

Design view in DreamWeaver CS3 disabled for CSS & Java

I currently use Adobe Dreamweaver CS3, and only some files have the option to view them in code AND in design view. This works for most files (HTML, PHP, etc). However, anytime I create a new CSS or Java file, the design view is disabled:
I have already tried the two other solutions I've found in this forum.
First I tried Preferences > File Types / Editors, and I deleted all of the file types in the "Open in Code View" menu (pictured below).
I restarted DW, and it didn't work.
Then I tried several steps to re-create the Configuration folder (which it did, but the problem remained) listed here: http://kb2.adobe.com/cps/401/kb401118.html.
Still nothing. HTML, PHP, ASP and all other files have the Design View and Split View available, but CSS and Java do not. I would really like to use DW to start editing CSS, but do not know it well enough to write in code and therefore could really use that handy Design View so I can learn as I tweak it.
Any help much appreciated - thanks!

HTML, PHP, ASP and all other files have the Design View and Split View available, but CSS and Java do not.
That's correct. That's as it should be.
A CSS file contains a bunch of text only CSS rules. Javascript is text-only script. There's no layout to see for CSS and JS files in Design and Split View so they're disabled.
Files with layout e.g. .htm, .php have Design View because they're web pages with a layout which can be viewed.
I would really like to use DW to start editing CSS, but do not know it well enough to write in code and therefore could really use that handy Design View so I can learn as I tweak it.
Open any .htm or .php (or other) web page and its associated CSS file.
Then tweak the CSS either via Code View in the CSS file, or using the DW CSS Editor when viewing the .htm/.php file, and see the formatting changes applied in Design View in the .htm (or .php) file.
Do not rely on DW's Design View as an absolute reference for pixel perfect accuracy. It will always be an approximation only to assist visually oriented web designers while editing.
Always test all CSS rules and edits in a range of browsers. Browser support for CSS rules and effects varies. Not all browsers support everything on offer in CSS1, CSS2 and CSS3.

Support for HTML and CSS properties

My biggest frustration with Acrobat Pro 9 is that it dropped support for certain HTML and/or CSS properties that were available in Acrobat Pro 8. In particular, the page-break-before attribute no longer works, nor does colspan. When I convert an HTML table with some colspans into a PDF, the table looks okay to the naked eye, but the structure behind the table (PDF tags) is incorrect.
I can live without the page breaks, but I need colspan. I need to do this for hundreds of tables, so opening the Acrobat Table Editor and fixing the colspan by hand is not an option. A scripting/programming solution is required. Has anyone found a workaround? Does Acrobat X fix this problem?

hello
not trying to hijack the thread but needed some clarification
your very short tutorial
http://alt-web.blogspot.com/2012/11/primer-for-using-jquery-plug-ins.h tml
was really informative. Just have a couple quick questions:
you state:
"the core code library which you ref in your <head> tags,"
the below code just has to be declared ONCE at the beging in your head section, correct?

<script type="text/javascript" src="http://code.jquery.com/jquery-latest.min.js">
</script>
then any number of jquery plugin scripts can be placed in ANY order in your head section following the above code, correct?
"the function code inside <script> tags to invoke the plug-in."
so then in the body, does the functions code have to come RIGHT AFTER the place it is being used?
example
<body>
<div class="slideshow1"
</div>

<script type="text/javascript">
</script>
<div class="slideshow2"
</div>

<script type="text/javascript">
</script>
</body>
or can you take all the function codes and paste them in the end outside of the respective divs that are using the code?
ie does the position of the code matter?\
thanks guys
Nancy O. wrote:
Try jQuery Fancybox
http://fancybox.net/
If you're new to using jQuery plugins, see this primer:
http://alt-web.blogspot.com/2012/11/primer-for-using-jquery-plug-ins.h tml
Nancy O.

CSS Level 2 Support for RGB Hex Abbreviation

when creating a style sheet during the tutorial in
Flash 8: Training from the Source, i abbreviated my hex
colors as usual when i have repeating pairs (in this particular
case #999 instead of #999999) and the publised Flash page would not
display the correct color. it displayed black text instead of gray.
after changing the #999 to the full #999999, the republished
Flash page displayed the page correctly. I understand from the book
Flash 8 does not support level 2 CSS, which includes more than my
simple abbreviation issue.
when do you (Adobe Flash Team) expect to incorporate CSS
level 2 support into the product? is it supported by Flex 2, as I
am not too familiar with that platform yet?
thank you,

Hi Mike,
OHJ uses the ICE Browser, which we license from a company named ICESoft. It generally compares favorably with other Java-based browsers, although it is not as complete as a native browser such as IE or Firefox.
There is a list of what is and is not supported in CSS:
http://www.icesoft.com/developer_guides/icebrowser/htmlguide/featuresappendix3.html#86328
We recently finally resolved the licensing issues that were holding us back from releasing a version of OHJ with JavaScript support. The current versions don't support JavaScript, but our next major release will.
Depending on your needs, we also have OHW, which is a server based help system, that uses the client's native browser.
Regards,
Jeffrey Stephenson
Oracle

Support for Arabic text and Direction:rtl

I am using HTML/CSS/Javascript to develop my application.
I have been trying to get direction:rtl (right to left) to
work to display Arabic text in the right form with no luck.
Does Adobe AIR lack the support for this feature ? If so,
what are the alternatives to Adobe AIR ??
I hope one of the Adobe employees reply to this....

> Any update on the Arabic support in Air ??
http://labs.adobe.com/technologies/textlayout/
"Bidirectional text, vertical text and over 30 writing
systems including Arabic, Hebrew, Chinese, Japanese, Korean, Thai,
Lao, the major writing systems of India, and others.
Selection, editing and flowing text across multiple columns
and linked containers, and around inline images"

Adobe recommends: Enhanced support for CSS3 in Dreamweaver CS5.5

Over the past week, we publicized some high-value content from adobe.com and other community sites. Hopefully you enjoyed these posts and found the resources useful. Today is our last day of the "Adobe Recommends" series.
Continuing our trip along the CSS highway, we now move to CSS3 with our next recommendation, by Preran Kurnool:
Enhanced support for CSS3 in Dreamweaver CS5.5
This blog post takes you through using box shadow, text shadow, border radius, and border image properties in Dreamweaver CS5.5.
Give it a spin and let us know what you think!
Previous recommendation threads:
Use Dreamweaver CS 5.5 to package your web application for iOS and Android devices
Customizing a Spry Menu Bar widget
Spry Menu Bar resources
Layout 101
CSS page layout basics
New CSS features in Dreamweaver CS5
Automatically attaching style sheets to new documents

Aegis Kleais wrote:
Sorry, Al, but I couldn't disagree more. Where I respect the fact that, as coders, we're rather ingrained with our workflow processes and, at times, hesitant to change, I've found LESS' benefits to be very worthwhile.
No need to apologize. Preprocessing is a topic on which there are differing opinions. You have one. I have one. There are advocates:
http://blog.urbaninsight.com/2012/04/12/ten-reasons-you-should-be-using-css-preprocessor
There are those who are not sold:
http://blog.millermedeiros.com/the-problem-with-css-pre-processors/
http://www.skybondsor.com/blog/css-preprocessors
There are those mostly sold:
http://css-tricks.com/musings-on-preprocessing/
There are even those who have been converted (but who might reverse at some later point):
http://cognition.happycog.com/article/preprocess-this
Heck, even I might be converted someday - or not
Bottom line for me, right now? I know I can write CSS that is better than most, more efficient than most, and easier to follow than most, and a preprocessor would add unwanted complexity. But that's for me. For someone not able to be organized intutively, or for a large - but carefully coordinated - team, a preprocessor could be a positive.
But not for me.
There are evolving trends - popular aspects of the technology that may and should find themselves being adapted into CSS. But I've been around this business as long as CSS has. I've seen buzzwords and trends and I've historically been spot-on in predicting the one that will stick. I think preprocessing will stick - but only insofar as it will be a catalyst for features in future versions of CSS. As a separate technology it makes no sense - to me

WLS support for SC_NOT_MOFIDIED (304) status code

Hi all,
We are using WLS 7.0 and noticed that it does not support the conditional retrieval
of URL for static content (ie html pages and gif files etc). This is true at least
for web application deployed with either a war file or "exploded" directory structure.
For those of you who not familiar with this status code, it basically enables
browser to send IF-MODIFIED-SINCE header with a http request. The server is supposed
to check if a new version exisits and if not, returns status code 304. This would
speed up things for an application with large number of static images, css or
html files. We are quite surprised that a leading product like WLS would omit
somthing so basic. So we are not sure if there is a place to turn it on or off?
If there is simply no support for this feature, can someone provide some explaination
as to the rationale behind it? We have some idea, but would rather hear it directly
from BEA. Thanks.

No, we have consolidated on the Apache XML/XSL stuff. You are free to use
whatever other parser you would like however. The Sun XML pkg should work
fine.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Boris Tabenkin" <[email protected]> wrote in message
news:[email protected]..
Are you still including the sun XML package, and if so which version?
"Toby Allsopp" <[email protected]> wrote in message
news:[email protected]..
Hi, Craig.
Craig Macha wrote:
Our company typically does NOT use Open Source products. We can't
risk
not having support.
I think you're a little confused about what "Open Source" means. Itdoesn't mean "unsupported." If you want support then you need to pay forit,
just like any software. One of the advantages of open source software is
that you aren't tied to a single vendor for your support - anyone with the
appropriate skills can take the source code and
provide support, as BEA have chosen to do in this case.
Regards,
Toby Allsopp.

What is the appropriate product name for CSS 11500 on Bug Toolkit

Today I tried to search DDTs of CSS 11500 on Bug Toolkit (http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl), however I can not find out appropriate product name corresponding to CSS 11500.
Before I had searched DDTs of CSS 11500 on Bug Toolkit many times, at that time, if my memory correct..
I selected "Cisco CSS 11500 Series Content Services Switches" in the list of "Search for bugs in other Cisco software and hardware products" on Bug Toolkit.
But I can not find this product name today.
Do you know what product name appropriate for CSS 11500 on Bug Toolkit ?
Your information would be appreciated.
Best regards,

Hi Gilles,
Thank you for your cooperation.
Today, I can find the CSS at "new Bug Toolkit".
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Select Product Category: Application Networking Services
Select Product: Cisco CSS 11000 Series Content Services
So I understand I should go "new Bug Toolkit" instead of old "Bug Toolkit" to
search any DDTs for CSS 11500.
Many thanks.
Best regards,

[svn:fx-trunk] 12944: Added support for state specific sccessible names in ToggleButtonAccImpl

Revision: 12944
Revision: 12944
Author: [email protected]
Date: 2009-12-14 21:36:44 -0800 (Mon, 14 Dec 2009)
Log Message:
Added support for state specific sccessible names in ToggleButtonAccImpl
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
 flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ToggleButtonAccImpl.as

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>

[svn] 1307: modules: added support for automatically adding " use namespace X", depending on the -target-player value

Revision: 1307
Author: [email protected]
Date: 2008-04-18 16:28:33 -0700 (Fri, 18 Apr 2008)
Log Message:
modules: added support for automatically adding "use namespace X", depending on the -target-player value
* similar to how we add "use namespace AS3"
* symmetric with ASC's -use feature, however we don't have equivalent commandline support yet
Bugs: n/a
QA: Nothing in particular, except for testing the new functionality of -target-player (email me about this)
Doc: Maybe: If we doc about "use namespace AS3" being added to all Flex compiles, we may want to talk about this.
Reviewers: Pete and Erik
Modified Paths:
flex/sdk/trunk/frameworks/flex-config.xml
flex/sdk/trunk/lib/asc.jar
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/BatchCompiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/Compiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/ScriptCompiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Parser.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/Context.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/ContextStatics.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/SymbolTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/MetaDataParser.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/Configuration.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/DefaultsConfigurator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleModule.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/TypeTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/AtEmbed.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tools/SwfxPrinter.java

Thanks for your attention.
In the above logs, higher resolutions seems to be detected on both screens, hence my surprise :
[ 391.631] (II) intel(0): Printing probed modes for output LVDS1
[ 391.631] (II) intel(0): Modeline "1600x900"x60.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 391.897] (II) intel(0): Printing probed modes for output HDMI1
[ 391.897] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
If it can help here is also my current xrandr output (after having called it manually to use the preferred resolution of each screen)
itanguy ~ $ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1600x900 60.0*+ 40.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
1680x1050 59.9*+
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
If needed, I may reboot and provide xrandr output after boot (it will be 1024x768), or could other logs help you ? Please ask...

[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

CSS3 support for older browsers

It's pretty clear now that CSS3 is a Rubicon for web browsers and that either the browser is capable of interpreting the rules or it is not. Having said that, is there a "patch" of some sort that can be painlessly added to the CSS to allow support for, say, IE8?

I'm with Mark. Build to the level of your main target audience -- not the fewer than 5% who insist on using outdated browsers.
I have experimented with PIE and other so called "workaround" scripts for IE with less than stellar results. Also , IE Filters have some nasty side effects -- like disabling clearType which makes text look really terrible. I view these "workarounds" as mainly counterproductive.
Going forward, I'm adding an IE8 End Of Life message inside a conditional comment in all my projects now. That way people know up front that their browser sucks. The ball is then in their court whether or not to do anything about it.
We still have an XP computer at home that hubby doesn't want to part with. So the only IE browsers he can use are 7 & 8. That said, his favorite browsers are the latest versions of FF and Chrome which he uses regularly on XP. Just because some people have an older operating system doesn't necessarily mean they have to use inferior browsers.
Unless it's adversely effecting your content or usability, I don't think you should do cartwheels to support the few remaining IE7 and IE8 users. It's better for everyone if we ween them off the bad browsers as soon we can.
Nancy O.

IBooks support for auxiliary content and linking?

I have a couple of questions for the iPad/iBooks owners out there that I hope can answer them for me. I'm in Canada, so I won't be getting an iPad for at least another month or more (also waiting for the 3G), and I don't have any readily available access to one to try for myself.
1) This is a bit technical, but I'll just come right out and ask it. How is iBooks support for auxiliary content (non-linear content documents, in ePub parlance)? Does it do anything special with it (pop-ups, tooltips, side bars, slide-out panels, etc...), or does it just ignore it and lump it in with the rest of the "real" content?
From a cursory glance, it looks like Microsoft has done something similar with their proprietary .LIT ebooks (which are apparently based roughly on the same specs as ePub, i.e. XHTML and CSS). But I get the feeling this functionality has gone the way of multi-angle DVDs, which is to say no one bothers with it.
2) And my next question comes from having tried various ePub readers on the iPhone. None, but Stanza seem to even get this remotely correct (some completely ignore them, some render them but don't do anything with them, and one attempts to do something with them but spits out errors). I have an ePub that uses footnotes heavily (in the dead-tree version they're footnotes, in the ePub they're essentially endnotes). The ePub in question doesn't have chapters, but it has been broken up into multiple chunks (multiple XHTML content documents behind the scenes). The footnotes are accomplished by linking (and back-linking) a la standard HTML hrefs between said chunks. I assume iBooks is Webkit-based and this isn't a problem at all (i.e. it's just like using a web browser in that regard)? Also, am I correct that there's no "back" button/function except in the TOC?
3) Based on all the PR and guided-tours, etc..., I presume iBooks strictly conforms to a paginated view? There's no scrolling layout/view, and by extension a way to do auto-scrolling?
4) How does text-to-speech work? Will it read the whole book, or does it only read, for instance, your current selection?
Thanks!

Jon Walker wrote:
How is iBooks support for auxiliary content (non-linear content documents, in ePub parlance)? Does it do anything special with it (pop-ups, tooltips, side bars, slide-out panels, etc...), or does it just ignore it and lump it in with the rest of the "real" content?
It isn't handled by the reader at all. It is handled by the ePUB generating application. Non-linear content, if included, is usually ordered as found, i.e., it uses a left-most, top-to-bottom ordering algorithm. This usually means it ends up at the end unless aligned to the left edge of the source document above the inline content or interspersed between other non-linear and linear segments if also included. To ensure content displays with associated text, it is normally anchored, inline, just before or just after the desired text. Some generating apps indicate an ability to perform left/right alignments with text wrapping around inline images but I have yet to personally try this.
You'll have to excuse my ignorance, Jon, but I barely understand anything you wrote just then. I've only been playing with ePubs for the last several days, so I still have a very limited understanding of the specs, and have only a small collection of samples (which are very simply constructed), so I don't know the full breadth of what's possible in ePub. For instance, in my example ePub, one content document ends at the end of a paragraph, and the next document begins at the start of the next paragraph.
Please correct me if I'm wrong, but my current understanding of "content documents" are that they're essentially XHTML pages, and the only reason they're broken up inside the container is either for semantic reasons, to reduce initial load times, or to support older readers. And basically a reader will load them sequentially when it comes time to display them (i.e. next chapter, via a link, etc...), assuming in the 'spine' section they're listed as being linear (either explicitly or by default).
The only examples I've seen where a particular 'itemref' has had its 'linear' attribute set to 'no' are things like covers and footnote sections (I believe the IDPF also uses the example of an answerkey in a textbook). I guess it's a two-fold question. I'm having a hard time envisioning what other elements in a book one would want to mark as non-linear. I guess things like a glossary, a table of illustrations, an index, etc... (i.e. stuff that's important to the book, but you wouldn't want to read linearly with the actual content of the book). I should point out I write Windows apps for a living, and have no understanding of how the publishing industry works, or what goes into the making, designing, or laying out a book.
And second, it seems the specs leave it completely up to the reading device to determine what it wants to do with these non-linear documents. Hence, why I asked how iBooks handles them.
You lost me when you started talking about edges, anchoring, and wrapping. To me, that sounds more like formatting decisions one would have to make inside an XHTML document. But I'm always open to being schooled on a subject.
I have an ePub that uses footnotes heavily (in the dead-tree version they're footnotes, in the ePub they're essentially endnotes).
I believe this is essentially correct. Since ePUB files have no defined pages, the footnotes become endnotes the the specific generating application determining if they display at the end of the book or at the end of the chapter. E.g., Since Adobe InDesign requires segments (cover page, title page, chapters, etc.) be generated as independent documents with are later assembled as a "book," I believe its "endnotes" automatically display at the end of the individual documents which make up the book while other applications use inline tags to break up a single "book" document into independent XHTML documents but place all "endnotes" at the end of the "book" rather than within each XHTML document created from the tagged segment where found in the main source document.
From what I've seen in the specs, it makes sense that, with the way the specs are at this time, the onus is on the generator to figure out how to use and where to put the footnotes. Without a standard way of defining them, there's no way for a reader device to know what it's looking at is a footnote or not.
I was just hoping in my heart of hearts that Apple had somehow solved the problem. After all, they were the ones throwing the word "magical" around when describing the iPad.
As a side note, would you know if iBooks properly supports the page-break-before and page-break-after CSS styles?
Based on all the PR and guided-tours, etc..., I presume iBooks strictly conforms to a paginated view? There's no scrolling layout/view, and by extension a way to do auto-scrolling?
I've not found a way to scroll but then I prefer paging through the document with a tap than continuously "swiping" and so have not looked all that hard.
Yeah, not a dealbreaker by any means. Just something I've started playing with on my iPhone reader, and have kinda started to enjoy. But I'll make sure not to get too comfortable with it now.
As for the text-to-speech (which I wouldn't use anyway), I guess it's using the VoiceOver APIs that Apple includes in the SDK(?), and, no, it won't automatically read a whole book for you, but it will read at most a page at a time. Apparently, this is their work-around for the same grief that Amazon got with the Kindle's speech feature.

UA support for cursor properties

I would like a unique style for links to the articles section
of a site and
I was wondering if I could try a small image and if FF and IE
would support
that and if not, just default to the pointer image.
I can't get them to accept an image (may have styled it
incorrectly) - is
there a list somewhere of browser support for cursor
properties?
I suppose I could use a bg image or colour, etc on the hover,
but kinda
liked using a small icon for the cursor instead.
Cheers,
Lossed
__when the only tool you have is a hammer, everything looks
like a nail __

tks Gary,
Well, here goes:
FF seems to accept many file types, including .png, .cur, and
regular image
filetypes, but NOT .ani.
IE seems to accept only .cur or .ani.
If I make a 16 x 16 cursor, FF displays it as such.
IE blows it up to 32 x 32 (so I need to make it 32 x 32 and
have more
transparent area).
FF resolves the path as per normal - relative to the position
of the css
file in the file heiracy.
IE doesn't! It seems to resolve the relative path to the
cursor image as it
it's relative to the document the css is imported into, not
relative to the
css file itself.
That is why my cursor files weren't showing in IE - when I
change the path
to root relative or absolute, IE shows the cursor. Just why
it does this for
cursor images and (thank goodness) no other images called
from within the
css file, I have no idea.
And all this for just IE and FF on PC.
How other UA's and platforms treat cursor images is unclear.
"Gary White" <[email protected]> wrote in message
news:[email protected]..
> On Thu, 24 Aug 2006 13:53:00 +1200, "Lossed"
<[email protected]>
> wrote:
>
>>I can't get IE to show any image regardless of format
>>Must be doing something wrong somewhere I suppose.
>>I used Axialis AX-Cursor to create the images as .cur
and .ani, but
>>neither
>>show in IE, while the .cur shows in FF OK.
>
>
> No time to test right now, but try using one of the .cur
files from your
> Windows\Cursors directory, so you know the problem isn't
with the file.
> Just copy one of the .cur files to your site.
>
> Gary

Support for css

Similar Messages

Maybe you are looking for