Supports Design View in Linux ?

Hi All,
am new to Flex and am using ubuntu os(Linux) . I have
downloaded and installed Flex Builder alpha version for Linux and i
read that Linux doesn't support Design View and some other views
for Flex Builder from the following
URL:
http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html#features
If so, what is the solution to get Design view or i need to
download any other plug-ins?
Thanks in Advance

Adobe Newsbot hopes that the following resources helps you.
NewsBot is experimental and any feedback (reply to this post) on
its utility will be appreciated:
Adobe Labs - Adobe Flex Builder Linux Public Alpha:
Please download alpha 4. Welcome to the Adobe Flex Builder
Linux alpha on Adobe Labs. Flex Builder Linux is a plugin-only
version of the Flex Builder
Link:
http://labs.adobe.com/technologies/flex/flexbuilder_linux/
Adobe Labs: Flex Builder Linux Alpha 4 Released on Labs:
Aug 13, 2008 ... Flex Builder for Linux is an Eclipse plugin
version of the software that you can use to build Flex applications
on Linux. See the release
Link:
http://weblogs.macromedia.com/labs/archives/2008/08/flex_builder_li_2.html
Adobe Labs - Downloads: Adobe Flex Builder Linux:
For a list of the features currently included in the alpha
release, ... Flex Builder Linux Eclipse Plugin Installer. This
download provides the Flex Builder
Link:
http://labs.adobe.com/downloads/flexbuilder_linux.html
Adobe Labs: Flex Builder Linux Alpha 2 Released on Labs:
The second prerelease of Adobe Flex Builder Linux, an Eclipse
plugin version of ... Flex applications on Linux, is now available
for download on Adobe Labs.
Link:
http://weblogs.macromedia.com/labs/archives/2007/12/flex_builder_li_1.html
Adobe Labs - Adobe Flex Builder Linux Alpha Release Notes:
Flex Builder Linux is a plugin-only version of the Flex
Builder that you can use to .... Your use of the Adobe Labs
including the download of software,
Link:
http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html
Adobe - Flex Builder for Linux:
Aug 13, 2008 ... I'm using Flex Builder 3 for Linux, and my
debugger keeps detaching .... >>Please download the Flash
player latest version of debug plugin
Link:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=657&threadid =1318352&enterthread=y
Disclaimer: This response is generated automatically by the
Adobe NewsBot based on Adobe
Community
Engine.

Similar Messages

  • JSP Design View in Linux?

    Hi,
    I've been going through the weblogic platform evaluation which uses workshop
    heavily. One example which keeps coming up is using the "Design View" of the
    JSP Designer. Unfortunately, I don't have a tab for this, nor do I find it in
    any of the menus.
    I'm running workshop under Gentoo Linux, which I know isn't an
    officially supported Linux distro, but everything else in workshop seems to work.
    Anyone have any ideas? Is this feature supported at all under Linux?
    Thanks,
    -Anthony

    Unfortunately, in 8.1 Design View for JSPs is not supported on Linux.
    This is being addressed in the next release.
    Josh
    Anthony Molinaro wrote:
    Hi,
    I've been going through the weblogic platform evaluation which uses workshop
    heavily. One example which keeps coming up is using the "Design View" of the
    JSP Designer. Unfortunately, I don't have a tab for this, nor do I find it in
    any of the menus.
    I'm running workshop under Gentoo Linux, which I know isn't an
    officially supported Linux distro, but everything else in workshop seems to work.
    Anyone have any ideas? Is this feature supported at all under Linux?
    Thanks,
    -Anthony

  • What is the replacement for design view in in flex builder 4.7 for cs extension builder?

    Because design view is not available in flash builder than what is the use of extension builder in UI designing now we have to do design UI with xml which is very time consuming and boring  if there is any replacemnt for it than please help me .1 more thing i want to know is that when i make new default project in extension builder(flash builder 4.6) than it also not able to load design mode errror is
    C:\Program Files\Adobe\Adobe Flash Builder 4.6\eclipse\plugins\com.adobe.cside.libsinstaller_2.0.0.4-33034\archive\cslibs\2.0\4.5\re lease\apedelta.swc- not respondingSWC file failed to load. Any component dependent on this SWC file will not be displayed in the Design Mode.The SWC may have failed to load because of:
    *  Incompatible definitions caused by usage of a different SDK version
    *  Missing referred class definitions

    I have researched this quite considerably and my understanding is that Adobe have no intention of supporting Design View any more for Extension Builder.  In my opinion a very disappointing decision and one that is hard to comprehend.
    The best workaround I can find is to create the majority of your design in a parallel, non Extension Builder, project and then convert/import your design into your Extension.  This is by no means as satisfactory as having Design View for the Extension you are writing but it is better than simply creating your layout by guess work/trial and error.
    Although this has not been announced by Adobe, I have a suspicion that the reason they have decided not to put any further resources into fixing Design View is that Extension Builder as we know it is going to be abandoned soon, probably replaced with an HTML5/JavaScript method of building extensions.  My concern with this is that, other than wanting reassurances that there will be backward compatibility support for old extensions, There will not be a way of compiling an extension in a way that prevents people from seeing your code.
    This is all speculation and I guess we will have to wait and see what happens.  Hope this has helped.

  • Design View Removed?!

    You've said Design View has been removed in your FAQ, but not said why. I use it to preview certain parts of my application instead of having to launch the app, then drill down to the point where that part of the app is visible.
    It's a bit pointless saying Flash Builder 4.6 supports Design View since it is incompatible with the newer versions of Flex SDK. So if I created an application with Flex 4.8 and wanted to preview it in Design View, Flash Builder 4.6 would complain the SDK is not compatible and would not display the application.
    Why did you remove Design View? Are there any plans to introduce it or something similar at a later date?

    With all respect as former grouper at adobe i believe that you are taking aside here. Nothing wrong with that Don, but as iwas reading i got mixed messages... anyhow
    The point i want to make clear, as i also believe some would agree and diagree is that adobe is simply gibing up with their one of the biggest inventions, JUST because a big *ss company such apple  thinks inother way.
    I would NOT call adobe as leader, a leader would NEVER give up on its team, which is us... developers... users and so on.
    What adobe is now doing.... well they fall pretty much into a dictator mark. Why think this way is that now every company looks up to apple, the biggest company out there and they do so... they dictate users and developers and seems like everyother companie now believes that this is the thing.
    It used to be, company having discussions with users and developer what should the COMPANY do, what do you developers want to see and what do users want to see and experience, but thats not the case anymore.
    So basically, Adobe is no leader, they would NOT have given up on flex nor fb. A leader would have at least done some changes that makes us as the developers to feel comfortable with the transition, but they didnt... or did they ?
    Now that thing with the html5... thats not gonna be the big I in this world. For instance, take C and c# they are used WIIIIIIIIDELY.... consoles, PCs, surely some customized motherboards before compilation, well i dont know that sh*t but what i know, they have been around long time one of e oldest languages BUT STILL there are alternatives which people prefer.
    That leads us to one thing only, yea html5 will probably be some ones new beloved comfortable relationship-like thingy but tghere will be others who still love the kinky stuff, such as3,mxml,haxe,c,c#,xcode,python and so on...
    So DONT narrow down the opportunities..... you dont see that kind of transitions in stores where all these serials suddenly start to dissappear.
    As leader one would strenghten the users behind him nowthrowing them onto a thins ice where there future will be unsecure, cause that happend to me.
    Andone more thing with that dictatorism thing, its not only adobe, sony and ubisoft allready have shown such indicators and also applied some of them on their products where ive seen many and pretty threattening post and also EA seems to follow that pattern.
    A leader would make you comfortable with your choises cause leader belived it himself in the product, but when leader gives up, then you truly see the "leadership".
    Html5 is not for everyones taste, surly not for mine,ill stay with as3 and fb4.6 till they die, then im gonne become an unemployee and will live on the government cause ive payd my taxes for long time and cause of my leader fcks up, im gonna get those taxes back. Pathetic i know, like giving up, yes... thats what adobe does on us!
    Skickat från Samsung TabletDon Kerr <[email protected]> skrev:Re: Design View Removed?!
    created by Don Kerr in Flash Builder 4.7 - View the full discussion
    It is clear from this reaction that most people haven't been following Adobe's abandonment of Flex, over the past two years, and their total investment in other technologies and services.  It is business.
    My point is ... you should not expect any significant investment from Adobe in Flash Builder.   So, complaining about design view, or any other features,  right now is not seeing the forest for the trees.
    I WAS an Adobe User Group manager for years and a huge advocate of Flash Builder.  Now, I've concluded that that 4.6 is the last true version of Flash Builder.
    Handwriting has been on the wall for two years now folks.   Time to wake up and smell the coffee.  Time to invest in other technologies like your leader, Adobe, is doing.
    If you really like design views/drag n drop interface, I recommend you take a look at http://www.sencha.com for designing HTML5 rich apps.  Very nice design view interface. 
    I've chosen not to follow Adobe into their next big thing ... because most likely they will abandon it too like they did ColdFusion and Flex/Flash Builder.
    With that said, Flash Builder 4.6 for Air desktop and mobile apps is a great thing to focus on for the next two years until HTML5 begins to come even remotely close to what Flex was capable of.
    My two cents ... and clearly I have emotional issues that I need therapy for.
    Don Kerr
    Former manager, Space City Adobe User Group at NASA
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4683950#4683950
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4683950#4683950. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Flash Builder 4.7 by email or at Adobe Forums
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Can't find Design View for JSP page on Unix

    I'm using weblogic workshop to develop page flow on Solaris, and I can't find the Design View tab to build
    JSP page. I searched all menus and can't find one to enable this function. Is this function supported on Unix?
    Thanks
    Zhong

    Zhong--
    Unfortunately, no; Workshop 8.x does not support design view on UNIX.
    Eddie

  • Third Party Component Support in Design View

    in this article:"
    http://flexwiki.adobe.com/confluence/display/ADOBE/Flex+Builder+3+Planning"
    the follow is shown:
    Third Party Component Support in Design View
    Planned milestone: M3
    Flex Builder should have better support for third-party
    components in design view. Also, the components view and the
    properties view should be just as good for 3rd party components as
    it is for Adobe Flex components like charting and advanced data
    grid controls.
    * The component author should be able to specify the
    category for the Components panel.
    * The component author should be able to control the
    Standard View property sheet including the Common and Style
    categories
    * A component developer should be able to deliver a single
    component in a SWC that contains all appropriate information
    * The component author should be able to include Design view
    extension code to specify Design View surface behavior
    * The component author should be able to specify the default
    code that gets inserted when a component is dropped on the stage
    I wonder how to specify the category for my components, is
    that some compile options or some configure file?
    thx

    /bump
    Noone any information about that topic? This would be a great
    usability enhancement...
    Regards

  • Design view for jsp custom tags.

    when we drag-and-drop custom tag control in the source of jsp page, when we switch to the design view of jsp we should be able to view controls as desired.
    Observation: 1) Eclipse 3.2 doesn't have design view for jsp pages.
    2) which software uses the design view. we need to extend eclipse core framework and we do not find any technical approach document to proceed further on this.
    3) RAD 6.0 we can see a JSP in design view.
    I'm searching for any technical approach document to create plugin that can intercept the custom tags and provide a design view.
    Will any one suggest the plugin for that.

    Jeff,
    I have checked with engineering and found that JSP Design View support on
    Linux is a planned feature for the next release. I don't think we will have
    this feature as part of a Service Pack for 8.1
    Regards,
    Raj Alagumalai
    WebLogic Workshop Support
    "Jeff Cassanvoa" <[email protected]> wrote in message
    news:3f4df04e$[email protected]..
    >
    Raj,
    Thanks for the information!! Any timeframe when it might be supportedon Linux
    Thanks,
    Jeff
    "Raj Alagumalai" <[email protected]> wrote:
    Jess,
    Unfortunately, the JSP design view is currently not supported on Linux.
    Workshop does allow to do remote development where the IDE is running
    on a
    Windows machine and connects to a server running on Linux/Solaris.
    Regards,
    Raj Alagumalai
    WebLogic Workshop Support
    "Jeff Cassanova" <[email protected]> wrote in message
    news:[email protected]..
    Does anybody else who is running the Linux version of Workshop 8.1have
    troubling
    getting the Design View of JSP files to come up. All I see is thesource,
    with
    no tabs at the bottom to switch to/from the Design View. When I bootover
    to
    Windows and run 8.1 Workshop, I see both tabs and I am able to useboth
    views.
    Is it something I have set in Preferences somewhere that disablesthe
    Design
    View ???
    Thanks,
    Jeff

  • Design view for jpd

    Hello,
    I just installed Weblogic workshop on my Mac running OS X - everything looks OK except the editor doesnt show design/source tabs for jpds ( shows these tabs for others). can anybody please help ?
    thanks
    meera

    Jeff,
    I have checked with engineering and found that JSP Design View support on
    Linux is a planned feature for the next release. I don't think we will have
    this feature as part of a Service Pack for 8.1
    Regards,
    Raj Alagumalai
    WebLogic Workshop Support
    "Jeff Cassanvoa" <[email protected]> wrote in message
    news:3f4df04e$[email protected]..
    >
    Raj,
    Thanks for the information!! Any timeframe when it might be supportedon Linux
    Thanks,
    Jeff
    "Raj Alagumalai" <[email protected]> wrote:
    Jess,
    Unfortunately, the JSP design view is currently not supported on Linux.
    Workshop does allow to do remote development where the IDE is running
    on a
    Windows machine and connects to a server running on Linux/Solaris.
    Regards,
    Raj Alagumalai
    WebLogic Workshop Support
    "Jeff Cassanova" <[email protected]> wrote in message
    news:[email protected]..
    Does anybody else who is running the Linux version of Workshop 8.1have
    troubling
    getting the Design View of JSP files to come up. All I see is thesource,
    with
    no tabs at the bottom to switch to/from the Design View. When I bootover
    to
    Windows and run 8.1 Workshop, I see both tabs and I am able to useboth
    views.
    Is it something I have set in Preferences somewhere that disablesthe
    Design
    View ???
    Thanks,
    Jeff

  • No Design View = Time to move on from Flex?

    I love Flash/Flex.
    I have been using it for a long time.  Nothing comes close to it in many was as a RIA development tool for making great cross platform apps (OSX/Windows/Linux/iOS/Android). (Not just games)
    However, over the last few years as the properganda from entities that would prefer to see Flash go away, has worked well, and only the people who know flash very well are those who have stayed.. As we understand what we get with flash and how alternatives don;t compare.
    Still, we are the only ones left as anyone starting out, considering the properganda, would not even consider flash anymore.
    I was hoping that flash would continue on with those in the know and the advantages would continue on while the rest of the brain washed community would eventually saw, "ah! why are we not using this.." as they realise the advantages of the cross platfom that flash is king in.
    (Cross platform tools will be the most important single issue as time goes on and the market fragments more and more)
    As the developers that have been fathful to the technology, even tho Adobe has forsaken us..  (And paid the price with  probably the bigest reputational damage in its history) One would expect Adobe had learnt from this..
    But unfortunatly not.  The drop of Design View in 4.7 is, unfortunatly, the decision that will break the developers will.  When we consider the reasons why a developer of RIA uses flex, it is the speed of developing the screens and layouts.  Design View is a key to this.  No design View = no future for the product.  Makes you wonder why they even bothered open sourcing the FLEX sdk.
    Consider this.  every, EVERY... IDE,  Windows, OSX, Android Qt, etc development tool has a design view.  Without it, your nothing but a interesting technology with productivity issues that leads you to never using it.
    And that is where we stand now going forward with Flash Builder...
    I understand that 4.7 is likely more for the game developers and design view is less important however... read on..
    We are now at the cross roads where, as some one who has been holding onto Flash as other tool sets do not compare.  Well. now they do, and in some ways even better.
    This decision will likely force the bulk of those holding on of the flash life boat to swim to another.  It will be such a distastful action to actionscript developers that even the flash Gaming plaltform efforts will likely be terribly damaged if not made irrelevant.
    You need a community of active developers utilsiing that technology if you plan to make it a vilable platform.  Especially for games as its so fickel.
    Killing of the quiet but arguably the most lines written protion of the development base..  Custom RIA apps..  You know not what you have done.
    Deisgn View does not need to do everything, but it needs to be there, so layouts are quck and easy to modify.  It needs to be supported again ASAP, or open sourced ASAP.  A decision has to be made, otherwise.
    Adobe Flash team, guess you'll be moving to the HTML5 dev teams in the very near future. (Or look for a new job..)
    James

    I think this has already been discussed, but I agree that dropping design view is a big problem.  There's a lot of propagandists in IT, sadly, who have ulterior motives when they discuss technologies because they want to promote their own horse in the race.  Attacking Flash (or Flex itself) was one type of dishonest behavior, but I guess another that applies to the Flex community itself was propagating the myth that "nobody uses design view", despite not having a shred of objective evidence to say this (that I've seen).  DV was the #1 thing that made FB stand out over other IDE alternatives, without it you might as well end the product line and let the current alternatives move in.
    I don't think DV can be made open source for technical/legal reasons.  And to be honest, it is a bit bloated & buggy anyway, so I don't care because I think it needs a re-do.  But I do hope someone (either Apache or Adobe, although the latter is probably a fantasy) realizes that developers doing serious UI work (something more complex than a mobile phone app with 4 buttons) require some method of rapidly prototyping and visualizing their UI.  Silverlight has Expression Blend and Sketchflow, JavaFX has Scene Builder, GWT has some design tool -- Flex needs to maintain something.  Probably the main thing keeping me in the Flex realm is just a form of "vendor-lock-in" now.
    Design View doesn't need to be a "design without code" solution that lets you specify every possible component attribute, align text, and specify a data source.  We can do that in MXML, and we can read ASdocs or use autocompletion just fine.  What's needed is an intuitive, fast, reasonably reliable way to visually confirm component layouts, with accurate styles, sizing and scrollbars.  The most essential user interaction is probably sizing & positioning of components and containers.  Maybe with some limited label/text setting shortcuts to help non-developer designers.  It doesn't need to be a plugin or built on Eclipse or anything overly bloated like that, a small standalone app that just does the essentials well is fine--even an AIR app.

  • Can not see two fields in Crystal 2008 Developer explorer/designer view

    I am currently developing crystal 2008 reports against the salesforce.com database using version 12.0.0.683 CR Developer Full version. I am using an updated driver that was provided in July or Aug 08 in order to view self referencing fields. The problem is that when I try and report against one of the tables (lead history) I cannot view two of the fields (New Value and Old Value)? I can see these two field (New Value and Old Value) in the database expert as the last two fields in the actual table, but the two fields are missing when I go into the explorer/designer view. In Salesforce, these two fields can not be filtered on, but I can export all the values in this table using Salesforece Apex data loader.

    Please re-post if this is still an issue to the OnDemand Forum or purchase a case and have a dedicated support engineer work with you directly

  • What is it about this markup that breaks DW CS3 Design View Editing?

    Folks:
    I'm attaching very simple --and apparently completely valid-- markup that generates the text shown between the markers below:
    ------------start----------------
    yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda badda.
    ------------end----------------
    As you can see by examining the file, it contains only an span enclosing text and spaces, and some following breaks.  This file passes DW validation: no errors or warnings.
    If I open this file in DW CS3 Design View, select and delete the last word, "badda", the entire text --every "yadda"--  is also deleted.  All that text is really gone -- if I immediately save the file and re-open it, there is no text content at all, just the span pair,  spaces, and the trailing breaks.  This is completely repeatable.
    When you edit this file, do you get the same result?
    The attached file is a cut-down, simplified version of a production file that exhibits this issue. (That file also passes validation.)   When I delete single  words,  entire content paragraphs disappear.   So this is not just a point of curiosity.  I need to figure out how to fix the production code and avoid this problem in the future.
    What is it about the attached markup that causes this issue?  I've fooled around with this code quite a bit and the best I can figure out is that DW is confused when both the start- and end- span tags are followed immediately by a line break.  Inserting a space in either place makes the issue go away.   But the production code doesn't have any occurances of this pattern. And, anyway, line-breaks have no significance to html, just for source-code formatting, right?
    Am I missing something incredibly obvious?
    TIA
    hen3ry

    Nancy O:
    Thank you for your response, which gave me  valuable clues to understanding the issues.   (Specifically, it led me to re-read and understand better the nitty-gritty of the HTML4 specs,  section 7, "The global structure of an HTML Document", especially 7.5.1 The BODY element.)
    I believe you are saying --in sum--  that to be reliably edited in DW, each source file must comprise a syntactically correct and complete HTML Document. 
    I am attaching a second file, "badcode2.html", modified substantially as you suggest.  It passes the DW validator, the validator.w3.org test, and the www.totalvalidator.com test.    No errors or warnings. 
    I do this:   Launch DW, open this file, choose Design View if necessary, select the final word of text, "badda", and activate Edit-->Cut (or Delete).   As before, all the other text is deleted as well. This is repeatable. 
    It seems to me this sample code satisfies your general principle.  Could I be misapplying the three validation tests?  Or that passing these tests does not assure the document  is syntactically correct and complete?   Can you recommend other tests? 
    I'd like to add the following two points as a matter of background and a bit of niggling: 
    --I'm aware  that complete HTML pages must contain <html> , <head>,  and <body> tags, although the HTML4 specification seems to say <body> tags are optional.   All my production pages, as served, contain these tags.   My underlying design is a php template with individual content files incorporated by inclusion.   There may be only one set of <html> , <head>,  and <body> in  a  page. The  "outer" template code provides these tags, and individual content files cannot contain a nested set -- so they must be "bare" markup.   Is DW able to support this design, in which "bare markup" files are seemingly unavoidable?    Is there a mechanism analogous to DW Design-Time Style Sheets to provide virtual existence of these tags so "bare markup" files can be successfully edited?  I've looked for such a mechanism but not found one.    Or some completely different method?   
    --You specify the inclusion of <p> or <h1> tags within the  body.    Is there some special significance of <p> or <h1>  with respect to stable editing in DW?  My reading of the HTML4 spec indicates that a single block element is the minimal requirement for body content. Either of these tags qualify, right?   But so does <div>, and that's what I use in my current example.    Am I misunderstanding something? 
    Bottom line,  I'm looking for a pragmatic solution for my problem:   Once in a while, among hundreds of  structurally similar "bare markup" pages I edit in DW without any problem,  I lose data.   If inserting an additional tag into all my content include files eliminates these occasional problems, I'm  willing to do that, as long as:  (1) There is an arguable technical basis for the addition,  (2) the added tag does not  produce anything visible on the served page, and (3) the validators don't flag the extra tag.     
    Suggestions, please! 
    Thanks, 
    hen3ry

  • Design view is empty

    I'm able to see the html/cf code in the code view, but in the
    design view I don't see anything, to include tables, etc. I'm using
    DWMX2004.
    Any ideas?
    Thanks.
    Force

    Does the page validate? If not, then fix the validation
    errors. That's the
    best way to approach troublesome pages.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "n h c" <[email protected]> wrote in message
    news:er02tr$g93$[email protected]..
    >
    quote:
    Originally posted by:
    Newsgroup User
    > > if that makes any sense.
    >
    > It doesn't really. If the page is valid HTML, you will
    see it in DW.
    > Even
    > when it is a combination of some scripting language and
    HTML, you will see
    > something.
    >
    >
    > well, maybe that's how it should be. but this website
    defies all reason
    > and
    > convention. i think most people would have quit/suffered
    a nervous
    > breakdown/killed my boss by now. the people who worked
    here before me left
    > quite a mess, i must say.
    >
    > i think the code probably isn't valid. but i really
    don't know enough
    > about
    > coding yet to fix it. and it works, it just makes it
    hard to figure out
    > where i
    > need to edit things sometimes.
    >
    > but we're not discussing my ridiculous website here! not
    anymore, at
    > least.
    >
    > -courtney
    >
    >

  • Design View and a CSS Div layout page

    There are a few pages l
    ike this. I am assuming it is because everything is layed out w
    ith div tags, but there mush be a way to correct the desging view. Everything shows up great o
    nline. Here is a screenshot:
    Here is the code:
    <body onload="initHomePage(); addReferToLinks();">
    <!-- ################# TOOLBAR ############## -->
    <script type="text/javascript" src="/shared_assets/toolbar_v2/toolbar.js"></script>
    <!--  end TOOLBAR -->
    <img src="/profile/image/logo_linknet.gif" />
    <!-- Main div for entire page layout -->
    <form name="frmSearch" action="" method="get" title="Resources" class="scopedSearch">
           <input class="textInput" name="qt" value="THIS SECTION ONLY" id="searchField" size="20" />
           <input class="button" type="submit" value="Search" name="submit" />
           <input type=hidden name="col" value="mpr dno dnos1" />
    </form>
        <div id="main">
    <!-- ###################### LEFT NEWS ################################## --> 
      <div id="newsBox" class="box">
       <div class="boxHeader">
        <div class="headerLeft"><h2>MP News</h2></div>
        <div class="headerRight"><a href="/news/news/index.htm" class="more">more &#0187;</a></div>
       </div>
       <div class="boxContent">
        <h3>
         <script type="text/javascript">var x=new Date(); document.write(x.toLocaleDateString());</script>
        </h3>
        <div id="newsContent">
         <div class="loading">
          Loading...
         </div>
        </div>
        <!-- -->
        <h3>My Subscriptions</h3>
         <ul style="list-style-type:none;">
          <li><a href="http://rss/">Setup Subscriptions - Get Help</a></li>
          <li><a href="http://">View Subscriptions</a></li>
         </ul>
        <!-- MEDIA CENTER -->
        <div class="imgFrame"><a href=""><img src="image/mc_logo2.jpg" alt="Media Center" hspace="0" vspace="0" border="0" /></a></div>
        <!-- COLUMNS -->
        <div class="imgFrame"><a href="http/"><img src="image/columns.gif" hspace="0" vspace="0" border="0" alt="The Northwestern Columns" /></a></div>
       </div>
      </div>
    <!-- #### end LEFT NEWS ########### -->
    <!-- ###################### CENTER CONTENT ################################## -->
      <div id="content">
       <!-- MAIN CONTENT WELL -->
       <!-- optional notice (visible only when critical news exists) -->
       <div id="alert" class="box highlightBox">
        <div class="boxHeader">
         <div class="headerLeft"><h2>Important Notice</h2></div>
         <div class="headerRight"> </div>
        </div>
        <div id="alertContent" class="boxContent">
         <div class="article">
          <a href="" class="headline">Avoid lock out - Install LINK 22.2 now</a>
          Users who do not install LINK 22.2 before the version enforcement date of July 31 will be
          unable to access their PCs.
         </div>
        </div>
       </div>
                <div id="home_page_id">) Home Page</div>
       <!-- Activities -->
       <div id="activities" class="box highlightBox">
        <div class="boxHeader">
         <div class="headerLeft">Welcome<span id="username"></span><h2>What would you like to do?</h2></div>
         <div class="headerRight"> </div>
        </div>
        <div class="boxContent">
         <div style="width:100%;">
          <ul>
           <li><a title="Find information and tools for recruiting new representatives" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Recruiting:  <select style="font:message-box; width:19em;" onchange="if(this.value){window.navigate(appendReferer(this.value))};">
             <option name="selectRecruit" selected="selected">*** make selection ***</option>
             <option value="http.htm">Sourcing & Prospecting</option>
             <option value="http://.htm">Selecting & Assessing Candidates</option>
             <option value="http://_process.htm">Post Acceptance Process</option>
             <option value="http">Developing an Internship Program</option>
             <option value="http.htm">Tracking Activity, Results & Accountability</option>
             <option value="http://.htm">Recruiter Development</option>
            </select></a></li>
           <li><a href="/objective/mpr_secure/mp_ldorgdev.htm" title="Find information and tools for developing leaders in your office" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Leadership &amp; Organizational Development </a></li>
           <li><a href="/objective/mpr_secure/mp_supvsn.htm" title="Find information and tools for effective supervision" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Supervision</a></li>
           <li><a href="/objective/mpr_secure/mp_stfop.htm" title="Find information and tools for   managing your office" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Staffing &amp; Operations</a></li>
           <li><a href="/objective/mpr_secure/mp_plnperform.htm" title="Find information and tools for business planning and performance monitoring" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Planning &amp; Performance</a></li>
              <li><a href="/objective/mpr_secure/mp_mngmntcompben.htm" title="Find information regarding income, fees, expenses, allowances and benefits" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Management Compensation &amp; Benefits</a></li>
              <li><a href="/objective/mpr_secure/mp_repdev.htm" title="Find information and tools regarding mentoring and professional growth" onmouseover="showTooltip(this);" onmouseout="hideTooltip(this);">Representative &amp; Specialist Development</a>  </li>
          </ul>
          <div id="slideshow1" class="activitySlideshow" style="height:212px;">
           <img src="image/slideshow_photos/photo06.jpg" />
           <img src="image/slideshow_photos/photo07.jpg" />
           <img src="image/slideshow_photos/photo08.jpg" />
           <img src="image/slideshow_photos/photo09.jpg" />
           <img src="image/slideshow_photos/photo10.jpg" />     
          </div>
         </div>
        </div>
       </div>
       <!-- Lower div under activities (2 columns) -->
       <div class="leftColumn">
       <!-- Events Calendar -->
        <div class="box">
         <div class="boxHeader">
          <div class="headerLeft"><h2>Events Calendar</h2></div>
         </div>
          <div class="boxContent"><ul>                      
          <li>April 25-30<br />
         <a href="http_020110.htm" target="_blank"></a></li>
         <li>May 12-14<br />
         <a href="http://030510.htm" target="_blank"></a></li>               
           <li>June 16<br />
         <a href="http://.htm" target="_blank">Series conversation</a></li>                                  
                          </ul>
          </div>
        </div>
         <!-- Spotlight -->
         <div class="box">
          <div class="boxHeader">
           <div class="headerLeft"><h2>Spotlight</h2></div>
           <div class="headerRight"> </div>
          </div>
          <div class="boxContent">
                  <div class="article">
          <!-- Leave "Market volatility resources available" at the top -->
       <div class="headline"><a href="http.htm?tern Mutual Association dues decline form available</a> </div>
         The $25 association membership fee will be charged to June 30 home
         office supply bills. Representatives who wish to decline membership
         may submit a <a href="http://.htm" target="_blank">decline
         form</a>.
    <div class="headline"><a href="http://.htm">Surplus notes information available</a> </div>
         Find answers to common questions and hear insights from about the company’s recent surplus notes offering.
                              <div class="headline"><a href="http://.htm">Stay up to date on 2010 estate tax repeal </a> </div>
         Consider the new Estate Tax Repeal page on LINKnet “home base” for information on the 2010 repeal and resources to use when talking to clients about this topic.
                  <div class="headline"><a href="http/index.htm">Withstanding Market Challenges</a> </div>
         Access resources to highlight the company’s strength and stability, find sales strategies and share marketing and market-related materials to help address client concerns.
                  <div class="headline"><a href="http:///year.htm">Dividend resources available</a> </div>
         The Current Year Scale page on LINKnet provides the latest information
         and sales support materials based on the 2010 dividend announcement.
    <!-- Leave "Market volatility resources available" at the top -->
                   </div>
          </div>
         </div>
       </div>
       <div class="rightColumn">
       <!-- Approaching Deadlines -->
        <div class="box">
         <div class="boxHeader">
          <div class="headerLeft"><h2>Approaching Deadlines</h2></div>
         </div>
         <div class="boxContent">
           <ul>
    <li>April 30: <a href="http.htm">Submit 2010 Commitment to Excellence Award nbominee</a></li>
           <li>May 25: <a href="http.htm">Submit applications for Intern Community Service Award</a></li>
                          <li>June 30: <a href="http://pdf">Submit 2010 Managers Membership Award Application to NAIFA</a> <img src="/shared_assets/image/doc_icons/pdf.gif" alt="PDF File" /></li>
                          </ul>
          </div>
        </div>
        <!-- Tech Alerts -->
        <div id="techalerts" class="box">
         <div class="boxHeader">
          <div class="headerLeft"><h2>Priority Tech Alerts</h2></div>
          <div class="headerRight"><a href="http://.htm" class="more">more &#0187;</a></div>
         </div>
         <div class="boxContent">
          <div class="loading">
           Loading...
          </div>
         </div>
         <iframe name="techalerts" src="/statusdisplay/001_summary.htm" onreadystatechange="if(this.readyState=='complete'){this.previousSibling.innerHTML = formatTechAlert(frames['techalerts'].document.body.innerHTML);}"></iframe>
        </div>
       </div>
      </div>

    Dreamweaver is pretty good these days at showing the page in Design View how it will be viewed when online. HOWEVER having said that it does largely depend on the way you write the css.
    I guess for Dreamweaver it's impossible for it to show every concievable way you can write css correctly. Unfortuantely if your css is not compatible with what Dreamweaver likes it won't make a great job of rendering the site correctly in Design View, that's always been the case.
    The css is not wrong but I've seen many display issues in Dreameaver Design View caused as a direct result of the css being overly complex to crack simple presentation. I guess it's in the lap of the gods if you are fortunate enough to have found the way to write css that Dreamweaver likes.

  • CSS is not showing in design view

    Hello, I wonder if anyone can help. I would appreciate very
    much if you can... I have read all the css related problems, but
    did not see the problem I am having.
    Anyway, I have done a website template for someone and I gave
    it to him to update the contents. However, on his dreamweaver
    Design view, the css does not support it at all so it looks all
    messy. Though when he preview it on IE, this is all fine. I have
    made templates and css files with dreamweaver and I can view
    everything fine. He seems to have the same version of DW (MX 2004)
    so I am not sure how this happens. We were looking in everything
    (including goofy css as someone says on this forum), but have no
    luck so far. Here is my link and I pasted my css here.
    http://www.norithefish.com/index2.html
    Many thanks for this.
    Noriko
    /* HTML tag styles */
    body
    {background: #cccccc; font-family: Verdana, Arial, Helvetica,
    sans-serif;
    font-size: small; color: #000000; font-weight: normal}
    a { color: #333333; text-decoration: none }
    a:active { color: #666666; text-decoration: none }
    a:hover { color: #CC3300; text-decoration: underline }
    .bodytext { font-size: small; color: #000000; font-weight:
    normal}
    .smalltext { font-size: x-small; color: #000000; font-weight:
    normal}
    .smalltextw { font-size: x-small; color: #ffffff;
    font-weight: normal}
    .title{ font-size: 1.5em; font-weight: bold; color: #CC3300}
    .wbracket{ font-size: small; font-weight: normal; color:
    #ffffff}
    .smalltitle { font-size: 1em; font-weight: normal; color:
    #666666}
    .sub { font-size: small; font-weight: bold; color: #ffffff }
    .foot { font-size: x-small; font-weight: normal; color:
    #000000}
    h1 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1.5em;
    color: #cc3300
    h2 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1.15em;
    color: #cc3300
    h3 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1em;
    color: #666666
    ul{
    list-style-type: square;
    ul ul{
    list-style-type: disc;
    ul ul ul{
    list-style-type: none;
    /* Layout Divs */
    #pageNav{
    float: left;
    width:21.3%;
    top:10px;
    padding-left: 0px;
    border-bottom: 1px solid #cccccc;
    border-right: 1px solid #cccccc;
    #content{
    width:75%;
    float: left;
    padding: 0px 0px 0px 0px;
    margin: 0px 0px 1px 20px;
    /* Component Divs */
    #siteName{
    margin: 0px;
    padding: 16px 0px 8px 0px;
    color: #ffffff;
    font-weight: normal;
    /************** feature styles *****************/
    .feature{
    padding: 0px 0px 0px 0px;
    font-size: 100%;
    /************* #siteInfo styles ***************/
    #siteInfo{
    clear: both;
    font-size: 100%;
    background-color: #999999;
    padding: 0px 0px 0px 0px;
    border-top: 1px solid #666666;
    /************* #smalltitle styles ***************/
    #smalltitle{
    clear: both;
    background-color: #ffffff;
    font-size: 100%;
    padding: 0px 0px 0px 0px;
    border-top: 1px solid #CC3300;
    border-bottom: 1px solid #CC3300;
    /*********** #sectionLinks styles ***********/
    #sectionLinks{
    position: relative;
    width: 150px;
    margin: 0px;
    padding: 0px;
    border-bottom: 1px solid #cccccc;
    font-size: 90%;
    #sectionLinks a:link{
    font-size: 1.15em;
    padding: 2px 0px 5px 10px;
    border-top: 1px solid #cccccc;
    width: 100%;
    width: auto;
    #sectionLinks a:visited{
    font-size: 1.15em;
    border-top: 1px solid #cccccc;
    padding: 2px 0px 5px 10px;
    #sectionLinks a:hover{
    font-size: 1.15em;
    border-top: 1px solid #cc3300;
    background-color: #dddddd;
    padding: 2px 0px 5px 10px;
    /*********** .frame styles ***********/
    .frame {
    width: 700px;
    left: 50%;
    padding-top: 0px;
    margin-left: -350px;
    margin-top: 0px;
    position: absolute;
    visibility: visible;
    border-top: 1px solid #999999;
    border-bottom: 1px solid #999999;
    border-right: 1px solid #999999;
    border-left: 1px solid #999999;
    background-color: #ffffff;
    .bg {
    height: 1px;
    background-color: #cccccc;
    width: 100%;
    /*********** #pageNav link styles ***********/
    #pageNav ul a:link, #pageNav ul a:visited {display: block;}
    #pageNav ul {list-style: none; margin: 0; padding: 0;}
    /* hack to fix IE/Win's broken rendering of block-level
    anchors in lists */
    #pageNav li {border-bottom: 1px solid #EEE;}
    /* fix for browsers that don't need the hack */
    html>body #pageNav li {border-bottom: none;}
    /********************* end **********************/

    > *** you are missing <li> at the beginning of the
    line and </li> at the end
    > or you want to remove the </li> from the previous
    lines.
    Or move the image within the existing pair. You cannot have
    that
    construction, though -
    <li>blah</li>
    <img>
    <li>blah</li>
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "josie1one" <[email protected]> wrote in message
    news:[email protected]...
    > It sounds to me as if it's a path issue.
    > Your path is this:
    > <link rel="stylesheet" href="styles/inside.css"
    type="text/css">
    >
    > Does he have a folder called "styles" within which
    should be the
    > stylesheet?
    >
    > You have a couple of code problems (I'd say unrelated to
    your question).
    > <li><a href="1-about.html">Order your Tshirt
    </a></li>
    > <img src="ferrari_team_polo.jpg" alt="photo of a
    T-shirt" width="120"
    > height="180">***
    > <li><a href="1-about.html">Order your
    cap</a></li>
    > <img src="ferrari_cap.jpg" alt="photo of a cap"
    width="120"
    > height="75"><br>***
    >
    > *** you are missing <li> at the beginning of the
    line and </li> at the end
    > or you want to remove the </li> from the previous
    lines.
    >
    > and according to
    >
    http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.norithefish.com%2Findex2.html
    >
    > you have an extra </div> a couple of lines above
    the </body>
    >
    >
    > --
    > Jo
    >
    >
    >
    >
    >
    > "norithefish" <[email protected]> wrote
    in message
    > news:[email protected]...
    >> Hello, I wonder if anyone can help. I would
    appreciate very much if you
    >> can...
    >> I have read all the css related problems, but did
    not see the problem I
    >> am
    >> having.
    >>
    >> Anyway, I have done a website template for someone
    and I gave it to him
    >> to
    >> update the contents. However, on his dreamweaver
    Design view, the css
    >> does not
    >> support it at all so it looks all messy. Though when
    he preview it on IE,
    >> this
    >> is all fine. I have made templates and css files
    with dreamweaver and I
    >> can
    >> view everything fine. He seems to have the same
    version of DW (MX 2004)
    >> so I am
    >> not sure how this happens. We were looking in
    everything (including goofy
    >> css
    >> as someone says on this forum), but have no luck so
    far. Here is my link
    >> and I
    >> pasted my css here.
    >>
    >>
    http://www.norithefish.com/index2.html
    >>
    >> Many thanks for this.
    >> Noriko
    >>
    >> /***********************************************/
    >> /* HTML tag styles */
    >> /***********************************************/
    >>
    >> body
    >> {background: #cccccc; font-family: Verdana, Arial,
    Helvetica, sans-serif;
    >> font-size: small; color: #000000; font-weight:
    normal}
    >>
    >> a { color: #333333; text-decoration: none }
    >>
    >> a:active { color: #666666; text-decoration: none }
    >>
    >> a:hover { color: #CC3300; text-decoration: underline
    >>
    >> .bodytext { font-size: small; color: #000000;
    font-weight: normal}
    >>
    >> .smalltext { font-size: x-small; color: #000000;
    font-weight: normal}
    >>
    >> .smalltextw { font-size: x-small; color: #ffffff;
    font-weight: normal}
    >>
    >> .title{ font-size: 1.5em; font-weight: bold; color:
    #CC3300}
    >>
    >> .wbracket{ font-size: small; font-weight: normal;
    color: #ffffff}
    >>
    >> .smalltitle { font-size: 1em; font-weight: normal;
    color: #666666}
    >>
    >> .sub { font-size: small; font-weight: bold; color:
    #ffffff }
    >>
    >> .foot { font-size: x-small; font-weight: normal;
    color: #000000}
    >>
    >>
    >> h1 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1.5em;
    >> color: #cc3300
    >> }
    >> h2 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1.15em;
    >> color: #cc3300
    >> }
    >> h3 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1em;
    >> color: #666666
    >> }
    >>
    >> ul{
    >> list-style-type: square;
    >> }
    >>
    >> ul ul{
    >> list-style-type: disc;
    >> }
    >>
    >> ul ul ul{
    >> list-style-type: none;
    >> }
    >>
    >>
    >> /***********************************************/
    >> /* Layout Divs */
    >> /***********************************************/
    >>
    >> #pageNav{
    >>
    >> float: left;
    >> width:21.3%;
    >>
    >> top:10px;
    >> padding-left: 0px;
    >> border-bottom: 1px solid #cccccc;
    >> border-right: 1px solid #cccccc;
    >> }
    >>
    >> #content{
    >> width:75%;
    >> float: left;
    >> padding: 0px 0px 0px 0px;
    >>
    >> margin: 0px 0px 1px 20px;
    >>
    >> }
    >>
    >>
    >> /***********************************************/
    >> /* Component Divs */
    >> /***********************************************/
    >> #siteName{
    >> margin: 0px;
    >> padding: 16px 0px 8px 0px;
    >> color: #ffffff;
    >> font-weight: normal;
    >> }
    >>
    >>
    >> /************** feature styles *****************/
    >>
    >> .feature{
    >> padding: 0px 0px 0px 0px;
    >> font-size: 100%;
    >>
    >>
    >> }
    >>
    >>
    >>
    >> /************* #siteInfo styles ***************/
    >>
    >> #siteInfo{
    >> clear: both;
    >>
    >> font-size: 100%;
    >> background-color: #999999;
    >> padding: 0px 0px 0px 0px;
    >> border-top: 1px solid #666666;
    >> }
    >>
    >> /************* #smalltitle styles ***************/
    >>
    >> #smalltitle{
    >> clear: both;
    >>
    >> background-color: #ffffff;
    >> font-size: 100%;
    >> padding: 0px 0px 0px 0px;
    >> border-top: 1px solid #CC3300;
    >> border-bottom: 1px solid #CC3300;
    >>
    >> }
    >>
    >>
    >>
    >> /*********** #sectionLinks styles ***********/
    >>
    >> #sectionLinks{
    >> position: relative;
    >> width: 150px;
    >> margin: 0px;
    >> padding: 0px;
    >> border-bottom: 1px solid #cccccc;
    >> font-size: 90%;
    >>
    >> }
    >>
    >>
    >>
    >> #sectionLinks a:link{
    >> font-size: 1.15em;
    >> padding: 2px 0px 5px 10px;
    >> border-top: 1px solid #cccccc;
    >> width: 100%;
    >>
    >> width: auto;
    >> }
    >>
    >> #sectionLinks a:visited{
    >> font-size: 1.15em;
    >> border-top: 1px solid #cccccc;
    >> padding: 2px 0px 5px 10px;
    >> }
    >>
    >> #sectionLinks a:hover{
    >> font-size: 1.15em;
    >> border-top: 1px solid #cc3300;
    >> background-color: #dddddd;
    >> padding: 2px 0px 5px 10px;
    >> }
    >>
    >>
    >>
    >>
    >> /*********** .frame styles ***********/
    >> .frame {
    >> width: 700px;
    >> left: 50%;
    >> padding-top: 0px;
    >>
    >> margin-left: -350px;
    >> margin-top: 0px;
    >> position: absolute;
    >> visibility: visible;
    >>
    >> border-top: 1px solid #999999;
    >> border-bottom: 1px solid #999999;
    >> border-right: 1px solid #999999;
    >> border-left: 1px solid #999999;
    >> background-color: #ffffff;
    >> }
    >> .bg {
    >> height: 1px;
    >>
    >> background-color: #cccccc;
    >> width: 100%;
    >> }
    >>
    >> /*********** #pageNav link styles ***********/
    >>
    >> #pageNav ul a:link, #pageNav ul a:visited {display:
    block;}
    >> #pageNav ul {list-style: none; margin: 0; padding:
    0;}
    >>
    >> /* hack to fix IE/Win's broken rendering of
    block-level anchors in lists
    >> */
    >> #pageNav li {border-bottom: 1px solid #EEE;}
    >>
    >> /* fix for browsers that don't need the hack */
    >> html>body #pageNav li {border-bottom: none;}
    >>
    >> /********************* end **********************/
    >>
    >>
    >>
    >>
    >
    >

  • Dreamweaver 8 Design View render issue

    I was wondering if anyone else has noticed a highly
    irritating issue with DW8 that is apparently not an issue in the
    Design View of DW MX 2004.
    In DW 8 for some reason I'm getting an extra 150 pixels of
    white space to the right of my #content container. It only appears
    to happen when the content within the #content container does NOT
    exceed the length of the content in my menu container (#priNav2).
    In other words, if the content is longer then the menu, it renders
    fine.
    See here:
    Dreamweaver
    8
    But, in DW mx2004 the exact same file shows up how it should.
    Dreamweaver
    MX 2004
    Does anyone have any suggestions on how to resolve this issue
    or have a clue as to why this is happening? It's really one of the
    only bugs left preventing me from upgrading to DW 8 anymore.
    Thanks,
    - Paul

    After some tinkering around and a call to Tech. Support I
    eventually resolved this issue by pointing out a bug to Adobe.
    Apparently the problem is the View / Visual Aids / Invisible
    Elements option. If this is turned on, and you have a website set
    up similiarly to
    this one, you will
    experience this sporatic, extranenous white space that shifts your
    content around. It is not an issue in DW MX 2004, only DW 8.
    The solution is to just simply turn OFF the "Invisible
    Elements" option. Then the page will render the way it should.
    A bug report has been submitted.

Maybe you are looking for

  • Can you add a second hard drive

    Just wondering. what is the exact mobo used in the imac 20inch is there an extra sata port. would like to add an extension to the ports on the back and be able to add a second hard drive at the speeds that sata allows

  • Allowing Spanish characters in PDF forms

    I'd like to develop a PDF form primarily for Spanish speaking users. Is it possible to allow Spanish characters in a PDF form? I know setting the "default locale" in LC has nothing to do with this, so is it a matter of system settings (ie. keyboard s

  • Webutil check if folder has write privilidges

    We need to check if a file has write privileges before writing to it using the webutil transfer. I tried WebUtil_File.File_Is_Writable but it shows as TRUE even though it isn't. I know its not writeable as the same location then gives me a WUT-105 Un

  • SAP Third Party PO

    Hi All,           I am getting a third party PO created in our system coming from another enterprise. this happens as following Enterprise sends out ORDERS05 PO to there PI/XI which is transmitted to our PI/XI in which they map the ORDERS05 xml messa

  • How to create production version & Explain with procedure

    how to create production version & Explain with procedure Madan