CSS Preprocessors?

These questions are for people that want to copy CSS from Parfait.
Do you use CSS Preprocessors in your workflows?
If so, which one do you use most often?
Do you ever use others, and if so, which one(s)?
Would you like Project Parfait to provide you with CSS in the syntax needed for your preprocessor?
Tell us about it!
Thanks,
Bruce

Hi Bruce,
I use LESS a lot in my day to day work flow, but as most people I know using less have semi-build-there-own mixin libraries not sure how easy that would be to integrate in without having to do a lot of restructuring your workflow, one that would be nice would be vendor prefixes as mixins, I think they are one of the few things most people have in their mixin libraries and since the syntax is fairly close to see anyway I would think it might be easier to implement efficiently!
Glad you're thinking of these kinds of things though, ideal situation would be you have a base mixin library and let people add their own on a per-account level? Again not sure how practical this would be to generate, CSSHat have a mixin library that works with their Photoshop extension but I've not actually used it so don't know if it's any good. http://lesshat.madebysource.com/
Danny

Similar Messages

  • Will Dreamweaver be incorporating the LESS CSS preprocessor?

    Will Dreamweaver be incorporating the LESS CSS preprocessor? A lot of us developers prefer LESSCSS as the preprocessor of choice. It would be great if there was an add on or integration of this in Dreamweaver.
    Any answer and suggestions are greatly ppreciated.
    Thanks.
    Peter Marino
    HTML5 Web Designer
    Sheffield Media Group, Inc.

    Hi,
    The first thing that we need to do is to tell Dreamweaver that it’s okay to open a .scss or .less file – something that Dreamweaver by default doesn’t understand. You’ll first need to take a peak in your personal Dreamweaver configuration folder – on a Mac, that’s located in ~username/Library/Application
    html5 mobile development

  • CSS preprocessors support

    Hi,
    I recently started using SASS in my websites. Working on a mac, i had to install a good deal of software via Terminal such as Ruby, NodeJS and Compass to check and handle the preprocessing for me. This process was pretty intimidating for a front-end designer like me. I can imagine incorporating such technology would greatly improve the appeal of Edge Code.
    Any chance Edge would support this in the future?

    I wanted to give an update on this feature concept, as we know that CSS preprocessor support is a hot topic these days. The team analyzed it and divided the feature into two significant pieces: 1) preprocessor support for code hinting and syntax support 2) direct preprocessor compiling/support from within the tool. We are looking into resolving #1 mid this year, but I don’t have an ETA for #2. We are in current investigation of both task and hope to provide the best solution as soon as possible! On the Brackets side, we have the below tasks that lead into this feature. When these features are completed for Brackets, they get shortly rolled into Edge Code.
    Early preprocessor hinting/syntax support: https://trello.com/c/C2vXQ7qU
    Full preprocessor hinting/syntax support: https://trello.com/c/EAQrlZv5
    Full LESS compiling/tooling in the editor, which would lead quickly into SASS: https://trello.com/c/fwdSCJSK/912-epic-sass-support
    Thanks again for using Edge Code!

  • 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

  • Syntax Highlighting for LESS CSS in Dreamweaver CS5.5

    This article describes how to add the .less extension to Dreamweaver so that it views it as CSS and thus performs proper syntax highlighting.
    I'm using Dreamweaver CS5.5 and following those steps still doesn't work for me. It works perfectly fine in CS5 and earlier versions but not CS5.5.
    Do you have any ideas? I'm modifying the following file as the above link suggests:
    C:\Program Files (x86)\Adobe\Adobe Dreamweaver CS5.5\configuration\DocumentTypes\MMDocumentTypes.xml

    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

  • [SOLVED] Compass does not work after update.

    For those of you not familiar, Compass is a Ruby gem that works with SASS , another Ruby gem. SASS is a CSS preprocessor. Anyway, I had Compass working fine, now I've completely broken it. I didn't see anything on the announcements that I thought would affect me, nor did I see anything on the forums.
    When I try to run the command 'compass watch' which makes compass poll for changes, I get this:
    /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- sass/script/node (LoadError)
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches/browser_support.rb:1:in `<top (required)>'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:2:in `block in <top (required)>'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `each'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `<top (required)>'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass/sass_extensions.rb:9:in `<top (required)>'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass.rb:5:in `block in <top (required)>'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass.rb:4:in `each'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/lib/compass.rb:4:in `<top (required)>'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/bin/compass:20:in `block in <top (required)>'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/bin/compass:8:in `fallback_load_path'
    from /home/joe/.gem/ruby/2.1.0/gems/compass-0.12.2/bin/compass:19:in `<top (required)>'
    from /home/joe/.gem/ruby/2.1.0/bin/compass:23:in `load'
    from /home/joe/.gem/ruby/2.1.0/bin/compass:23:in `<main>'
    From what I can tell, I have some sort of file path wrong. I added this to my ~/.bashrc file just like the wiki said:
    PATH="$(ruby -e 'puts Gem.user_dir')/bin:$PATH"
    Again, everything was fine but now it's not.
    Last edited by joetemp (2014-02-05 22:33:07)

    Oh no I know Compass isn't an official package. But Ruby is and I was using RubyGems as the 'package manager' to install Compass.
    I'm not at all trying to be a smartass but the reason I feel it belongs in the Pacman section is because everything I did... I did according to the wiki. Not a single AUR package is involved in this problem.
    See here:
    https://wiki.archlinux.org/index.php/ruby#RubyGems
    Last edited by joetemp (2014-02-05 23:29:49)

  • 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

  • Dreamweaver CS5.5 CodeIgniter Syntax Highlighting

    Hi Everyone,
    I am new to CodeIgniter but have been using Dreamweaver for over a year now, and one of the best features that speeds up my coding is the syntax highlightin and code completion that Dreamweaver offers,,is there a plugin or some way in which Dreamweaver can do the same for CodeIgniter 2.x? that would really be a good addition if its doesnt already exist. Thanks in advance for your answers! hehe

    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

  • Recent improvements to Parfait

    The team has busy fixing bugs, adding new features, and generally improving Project Parfait. Here are some recent changes, that we would love to get your feedback on:
    + Support for Layer Comps. If your PSD has Layer Comps, you can toggle them in the menu that is just left of the Zoom controls.
    + New Eyedropper tool. Sample colors from bitmaps in your PSD. Takes transparency into account, and is not affected by your display's color profile.
    + Support for CSS Preprocessors. So far, we've added SCSS + Bourbon, and LESS + Hat. Let us know if there are others we should add.
    + Units for fonts can be displayed in pixels, ems or rems. A Base Font setting allows you to override the default - ems and rems will be calculated using the Base Font.
    + CSS for Gradients is more accurate, and has improvements for some of the less common gradient types.
    + Click to Copy Position and Size in the blue HUD when you have something selected.
    + Cursor changes to provide hints and feedback as you work in Parfait.
    + In-product feedback. Simple yes/no questions presented to you in the context of the operation you just performed. We hope these are unobtrusive and easy for you to help provide feedback to us.
    + Parfait is now smarter about when your Creative Cloud login token expires, and prompts you to login.
    + Improved cross-browser support.
    We welcome your feedback and comments, either here in the Forums, or in the Chat pod in Parfait.
    Bruce

    Hello everyone,
    The team has kept busy improving Parfait, and we pushed a new build today with some new features for you to try. As always, please do provide feedback. We're eager to hear how these features work for you, and whether we can improve them. Even just a quick note to say one of them works well for you would be helpful and appreciated. We would love building Parfait to be an even more collaborative effort with our users.
    + Percentage-based measurements. You can now toggle between pixels and percentages in the blue info overlay when selecting one or two objects in Parfait. We definitely need feedback on this feature!
    + Typekit integration. Parfait now checks the Typekit library to see if the fonts used in the Photoshop file, and provides links to the webfont equivalents.
    + Asset Scaling. Parfait now allows you to enter relative scaling as 2x, 3x, 4x, 5x, even .5x now when you are exporting assets. We don't yet support entering an exact dimension, but will soon.
    + Improved Selection model. Now, we use alpha based hit testing rather than bounding box selection. This makes it easier to select what you want when items are close together.
    + Improved cross-browser compatibility.
    + Bugs and tweaks to improve performance and user experience.
    The Parfait team is going to be on vacation beginning June 28, returning July 7, but we're eager to have your feedback. Please use the chat pod in Parfait, or comment here in the forums, and we'll replay as soon as possible.
    Thanks!
    Bruce

  • Extension for HTML5  tags in Dreamweaver CS5.5??

    Hi, I'm currently using Dreamweaver CS5.5 and i 'd like to ask whether there's any extension or update available that updates the Insert Panel in order to support HTML5  tags?

    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

  • CSS Live development stopped working?

    Hello all, I just updated to the lated release of Edge code and while I love that live development for HTML is a nice added feature, it seems that the live development for my CSS is now not working properly.
    What happens is the changes I make to the css dont automatically update of the preview browser unless I refresh the browser now. The way I set up my files currently is I create a separate css file and link to it from my html file. Any help would be appreciated as this is kind of slowing down my whole process.
    Thanks

    Is the file extension for your external css file ".css"? Live Preview does not yet support preprocessors like LESS or SASS.
    Be sure to use File > Open Folder... to select a folder that contains all of you project files.
    Hope this helps,
    Randy

  • Css code completion everywhere?

    Would it be possible to make css code completion work in these two situations?:
    inside style="" attributes
    inside things like background-image:

    Taking an example like 'box-shadow', what sort of code hints would you want to see?
    Most of the individual bits of the property value are lengths in pixels, so it probably wouldn't make sense to show any hints for them individually.  But we could, for example, show hints for the entire value by just listing other 'box-shadow' values you've used elsewhere in your code (making reuse easy in cases where you're not using a preprocessor).  Is that the sort of thing you'd want?
    - Peter

  • Problem with CSS in ADF 11g application

    Hi,
    I have added a CSS code for my login page(login.html), The issue i am facing is When ever i am opening the page the complete CSS is not coming for each time one CSS component is coming that's means if there are 4 CSS components as shown below i need to login and logout the page 4times. 5th time i am getting the complete page.
    .ESPS_login_body{
    background-color:#eef1f8;
    margin:0px;
    padding:0px;
    }.ESPS_login_body *{
    margin:0px;
    padding:0px;
    font-family: Tahoma, Verdana, sans-serif;
    .ESPS_login_top_bar{
    background-image: url(../skin_images/login_top_bar.png);
    background-repeat: repeat-x;
    background-position: left top;
    height:30px;
    I am running the application on firefox3.5.3 version.
    Please suggest me
    Thanks,

    Hi,
    Thanks for your quick reply.
    MY CSS File:
    .ESPS_login_body{
    background-color:#eef1f8;
    margin:0px;
    padding:0px;
    }.ESPS_login_body *{
    margin:0px;
    padding:0px;
    font-family: Tahoma, Verdana, sans-serif;
    .ESPS_login_top_bar{
    background-image: url(../skin_images/login_top_bar.png);
    background-repeat: repeat-x;
    background-position: left top;
    height:30px;
    .ESPS_login_bottom_bar{
    background-image: url(../skin_images/login_bottom_bar.png);
    background-repeat: repeat-x;
    background-position: left top;
    height:46px;
    color:#eeeeee;
    text-align:center;
    padding-top:9px;
    font-size:small;
    .ESPS_login_bg{
    background-image: url(../skin_images/login_bg_gradient.png);
    background-repeat: repeat-x;
    background-position: left top;
    background-color:#6882cc;
    height:594px;
    overflow:hidden;
    .ESPS_login_content{
    -moz-background-clip:border;
    -moz-background-inline-policy:continuous;
    -moz-background-origin:padding;
    background:transparent url(../skin_images/login_bg_main.png) no-repeat scroll center top;
    color:#4269b6;
    height:594px;
    overflow:hidden;
    .ESPS_login_content_left{
    height:594px;
    .ESPS_login_content_main{
    height:594px;
    width:650px;
    margin:0px auto;
    padding:20px;
    .ESPS_login_content_main h1{
    margin-top:230px;
    margin-left:125px;
    color:#4269b6;
    .ESPS_login_content_main > h1{
    margin-top:210px;
    div.ESPS_login_from{
    margin-top:20px;
    margin-left:245px;
    .ESPS_login_input{
    background:transparent url( '../skin_images/login_input.png' ) no-repeat scroll center top;
    border:none;
    margin:0px;
    padding-top:4px;
    padding-left:7px;
    width: 193px;
    height: 25px;
    .ESPS_login_submit{
    display:-moz-inline-box;
    display:inline-block;
    cursor:pointer;
    border:none;
    font-size:0;
    line-height:0;
    text-decoration:none;
    font-style:normal;
    vertical-align:middle;
    background: transparent url("../skin_images/login_go_button_i.png") no-repeat top left;
    border: none;
    width: 48px;
    height: 25px;
    margin:0px;
    margin-bottom:17px;
    div > a.ESPS_login_submit{
    margin-bottom:0px;
    .ESPS_login_submit:hover{
    background: transparent url("../skin_images/login_go_button_highlighted_i.png") no-repeat top left;
    .ESPS_login_submit:active{
    background: transparent url("../skin_images/login_go_button_pressed_i.png") no-repeat top left;
    label.ESPS_label{
    display:-moz-inline-box;
    display:inline-block;
    font-weight:bold;
    padding-bottom:8px;
    width:110px;
    margin-bottom:2px;
    div > label.ESPS_label{
    padding-bottom:3px;
    margin-bottom:2px;
    Login Page:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
    <html>
    <head>
    <title>ESPS Login</title>
    <link href="/skins/css/mySkin.css" rel="stylesheet" type="text/css"></link>
    </head>
    <body class="ESPS_login_body">
    <div class="ESPS_login_top_bar">
    </div>
    <div class="ESPS_login_bg">
    <div class="ESPS_login_content">
    <div class="ESPS_login_content_main">
    <h1>External </h1>
    <form name="ESPS_login_form" method="POST" action="j_security_check">
    <div class="ESPS_login_from">
    <label class="ESPS_label">User Name:</label><input type="text" name="j_username" class="ESPS_login_input" onclick="this.value='';"/>
    <label class="ESPS_label">Password: </label><input type="password" name="j_password" class="ESPS_login_input" onclick="this.value='';"/>
    <a id="submit" href="#" class="ESPS_login_submit" onclick="document.ESPS_login_form.submit(); return false;">
    <span> </span></a>
    </div>
    </form>
    </div>
    </div>
    </div>
    <div class="ESPS_login_bottom_bar">&copy;Copyright 2009, DISH Network L.L.C., all rights reserved.
    </div>
    </body>
    </html>
    Please help me

  • Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only. However opening a CSS file does not prompt that it is alr

    Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only.
    However opening a CSS file does not prompt that it is already open on or from any machine which is causing code edits to be lost.
    What we found from out testing:
    - The file can be saved from one user to the server and WILL NOT PROMPT on other machines until the saving machine has the Dreamweaver program closed completely
    - The file can be closed and  Dreamweaver minimised to the launch bar but it still will not register on other machines that it has been changed.
    - Also, until the  Dreamweaver program is closed on the machines, it will continue to open it's saved version of the file. 
    Example Scenario:
    - User 1 opens test.css (which is 2000 lines) and adds some code to the end of the file to bring it up to 2500 lines
    - Meanwhile User 2 opens test.css as well (opens as 2000 lines as User 1’s edits have not yet been saved) and adds in code to bring it to 2300 lines
    - User 1 saves his file and closes it - but  Dreamweaver is still open.
    - User 2 also saves his file and leaves  Dreamweaver  open.
    - The server will report the size and last edit of the file the same as User 2 as he was the last person to save it (and if you open from the Win7 Machine it will show as User 2’s 2300 line version)
    - If User 1 then open's the file again (from either the 'recent' in Dreamweaver OR clicking on the file directly in Finder...which version opens.... The version that User 1 saved! Not the true version on the server, but the version that User 1 edited and saved with 2500 lines in it.
    - Same for User 2, he will open 'his' version with 2300 lines in.
    Other information:
    - Files are opened directly from the server
    - Sometimes the users will save incrementally and re-open
    - Most of the time users will save incrementally and keep the files open
    - The users will never not save incrementally and just save when closing the file once finished
    - The users are usually working on the files all day
    - It is always the bottom lines of code that are lost. It could be a case of the two versions being mixed up and cutting off the newly added lines based on the line count (possibly).
    It is as if Dreamweaver is holding a cache of the version locally and then only properly looking back to the server when it has been completely closed. It is very difficult to see how the server is causing such an impact on these files, there are very few logs which are giving any indication to the root cause of the problems.
    Anyone know if this is a known issue?
    Is there a way that there can be a featured implemented on the server that doesn't allow another user to open a file if it is already open on another machine?
    Thanks

    Your server file handling has nothing, and really nothing to do with Adobe software. If files don't get locked for (over-)writing and/or lose connection to the program opening them, then your server is misconfigured. It's as plain and simple and that. Anything from "known file types"/ file associations not being set correctly, MIME types being botched, crooked user privileges and file permissions, missing Mac server extensions, delayed file writing on the server, generic network timeout issues and what have you. Either way, you have written a longwinded post with no real value since you haven't bothered to provide any proper technical info, most notably about the alleged server. Either way, the only way you can "fix" it is by straightening out your server and network configuration, not some magic switch in Adobe's software.
    Mylenium

  • How Do You Add Multiple CSS Rules to Text?

    Hi everyone, I have these css rules in my css styles window they are all assigned to some text in a cell on my page.
    .Def14grey4 <body>
    .def14grey4 a:link <a>
    .def14grey4 a:visited <a>
    .def14grey4 a:hover <a>
    .def14grey4 a:active <a>
    .def14grey4 a:focus <a>
    How do you add (all of) these styles to the text in the first place, I know how to add the first one (.Def14grey4), you select the text in the cell and choose the rule from the drop-down menu in the css panel, but how do you add the other ones to some text as well, so that it can have the same link properties.
    Basically I have some more text elsewhere on the page and want to assign these rules to that as well.
    thanks Gareth

    You would want to change your order as shown here -
    .Def14grey4 <body>
    .def14grey4 a:link <a>
    .def14grey4 a:visited <a>
    .def14grey4 a:hover, .def14grey4 a:focus <a>
    .def14grey4 a:active <a>
    That way, the hover and the focus states are equivalent.
    How do you add (all of) these styles to the text in the first place, I know how to add the first one
    You don't really.  The 4 bottom selectors say -
    "find an element with a class of 'def14grey4', and style any link inside that element this way"
    So, <span class="def14grey4"><a href="whatever.html">Whatever</a></span> would get the pseudo-class styles, as would any of the following -
    <span class="def14grey4"><a href="whatever.html">Whatever</a></span>
    <td class="def14grey4"><a href="whatever.html">Whatever</a></td>
    <p class="def14grey4"><a href="whatever.html">Whatever</a></p>
    <body class="def14grey4"><a href="whatever.html">Whatever</a></body>
    <div class="def14grey4"><a href="whatever.html">Whatever</a></div>
    <strong class="def14grey4"><a href="whatever.html">Whatever</a></strong>
    and so on.  These examples assume that there isn't some other more specific rule that would apply to the same links.  You need to study up on the CSS cascade and specificity....

Maybe you are looking for