Application resize best practice

Hello, I have one question when making a chromeless application. In my application I have several different states where each state is different in dimension. For now I have been resizing the application window whenever a state change occurrs but since I have several different states this is starting to get confusing to change the width and height whenever a side tab opens or whenever a login panel slides down. Am I doing this the right way or can I start with a dimension that is the size when the application is at it's maximum and forget about changing the dimension every time? Since it is chromeless, you don't actually see the application background anyway..... I thought that if the application is set to a certain dimension then it will take up that amount of space on the desktop regardless of whether it might only have one button inside.....

I assume you've already found an answer for this old question.

Similar Messages

Upscale / Upsize / Resize - best practice in Lightroom

Hi, I'm using LR 2 and CS4.
Before I had Lightroom I would open a file in Bridge and in ACR I would choose the biggest size that it would interpolate to before doing an image re-size in CS2 using Bicubic interpolation to the size that I wanted.
Today I've gone to do an image size increase but since I did the last one I have purchased OnOne Perfect Resize 7.0.
As I have been doing re-sizing before I got the Perfect Resize I didn't think about it too much.
Whilst the re-size ran it struck me that I may not be doing this the best way.
Follow this logic if you will.
Before:
ACR > select biggest size > image re-size bicubic interpolation.
Then with LR2
Ctrl+E to open in PS (not using ACR to make it the biggest it can be) > image re-size bicubic interpolation.
Now with LR2 and OnOne Perfect Resize
Ctrl+E to open in PS > Perfect Resize.
I feel like I might be "missing" the step of using the RAW engine to make the file as big as possible before I use OnOne.
When I Ctrl+E I get the native image size (for the 5D MkII is 4368x2912 px or 14.56x9.707 inches).
I am making a canvas 24x20"
If instead I open in LR as Smart Object in PS and then double click the smart icon I can click the link at the bottom and choose size 6144 by 4096 but when I go back to the main document it is the same size... but maybe if I saved that and then opened the saved TIFF and ran OnOne I would end up with a "better" resized resulting document.
I hope that makes sense!?!?!?!
Anyway I was wondering with the combo of software I am using what "best practice" for large scale re-sizing is. I remember that stepwise re-sizing fell out of favour a while ago but I'm wondering what is now the considered best way to do it if you have access to the software that was derived from Genuine Fractals.

I am indeed. LR3 is a nice to have. What I use does the job I need but I can see the benefits of LR3 - just no cash for it right now.

JEE5 Application Architecture Best Practice.

Hi Everybody
I am going to redesign a moderate size application (not v big but larger then normal).
Now I have few Question in my mind.
I am using JSF as front-end, EJB3 Session Bean for Business Logic and last but not the least JPA as domain model.
1 - With JPA we have a domain classes. Now its better to use entity as manage-bean for JSF or manage bean should be saperate.
2 - Using DTO (Data Transfer Object) is good practice or not in JEE5.
3 - Simplicity or Complexity but with EntityManager I feel no need of DAO but I am used to with DAO pattern. So again as best practice I have to make 1 session bean as DAO and call it from all the session bean where I write business logic or forget about DAO session bean and call EntityManager from all session bean everywhere.
4 - For initializing EJB JNDI is 1 way other way is
@EJB EJBCLASSNAME ejbclassobject; //this auto initialize and create object.
Initializing like above is standard or it is an extended support from some app server.

Hi,
Follow my opinion:
1 - With JPA we have a domain classes. Now its better to use entity as manage-bean for JSF or manage bean should be saparated.
>> I think that Managed-Bean must be separated, because you can need to bind you Visual Components to it too.
2 - Using DTO (Data Transfer Object) is good practice or not in JEE5.
>> You can put your Entity as a member of you Managed Bean.
3 - Simplicity or Complexity but with EntityManager I feel no need of DAO but I am used to with DAO pattern. So again as best practice I have to make 1 session bean as DAO and call it from all the session bean where I write business logic or forget about DAO session bean and call EntityManager from all session bean everywhere.
>> For CRUD operation I don't create a additional class, but for complex business logic, you can use a separated class (Business Manager)
Best regards

Internet Sales application 2007 - Best Practice

Hi Gurus
Has anyone completed a successful CRM 2007 Internet Sales (ISA not ICSS) configuration exercise.
If anyone has completed the set-up please could you inform me of the documents you referenced in order to achieve this.
Many Thanks
Babu.

SAP has confirmed to me that there is NOT a CRM6/7 ISA Best Practices guide.
We used the C14_BB_ConfigGuide from our CRM4 Best Practices install and made some assumptions on what had changed. I do not think this is still available here and am not sure if I am able to send it to anyone. Someone from SAP or an Admin can tell us.
I also found here the following docs that have bits and pieces of the puzzle.
ECO_Authorizations.CRM5.0 - I think I found this on Sateesh's site, but probably a link around here for it. - CRM E-Commerce Authorizations
Release 5.0
SAP_ISA60_DevAndExt - SAP E-Commerce
6.0 u2013 Landscape, Basics and Concepts.
Web AS - Web Application Development
Title: Working with Java Server Pages and Servlets
Benny Schaich

Web application security best practice?

Hi guys,
I am developing web app using JSF + Spring + Hibernate. I got a user backing bean which handling user login and logout session. Hence if user sign-in successfully, I will just set userLogIn=true in the userBean.java. I really don;t know if this is the best practice for handling user login session. Any security probelm here? Please advice, Thanks !
regards,
kmthien

hi
you can also find a lot of info about security handling and JSF if you search the forum.
thanks.

Application communication - Best practice

Hello
I am eager in understanding the best ways to create communication between applications (Server to client) in Java.
In the past, I have attempted to make applications using the Socket and ServerSocket class. The concept works of course, but I was wondering if this technique is also being used on enterprise level.
I would be most interested in:
- A system that does not rely on request & response, so that the client can receive information without requesting any.
- The ability for users to send and recieve String messages. (e.g. server announcements).
- The ability for users to send and receive objects. (e.g. sending or receiving user information).
- (optional) Security (e.g. encrypted information).
- (optional) Possible communication with clients using different technologies (e.g. .NET client) while using a server in Java.
Any information about this is greatly appreciated.
Vincent

A system that does not rely on request & response, so that the client can receive information without requesting any.Datagram
The ability for users to send and recieve String messages. (e.g. server announcements).Ditto. Investigate Multicast also.
The ability for users to send and receive objects. (e.g. sending or receiving user information).RMI.
(optional) Security (e.g. encrypted information).SSL.
Possible communication with clients using different technologies (e.g. .NET client) while using a server in Java.SOAP.
I think you should spend a bit more time with Google, or better yet buy a book or three on Java networking. This one is good: [http://www.amazon.com/Fundamental-Networking-Java-Esmond-Pitt/dp/1846280303|http://www.amazon.com/Fundamental-Networking-Java-Esmond-Pitt/dp/1846280303]

Application Server Best Practice Config.?

Hi All
We currentely have an R3 System with 7 application servers which I want to check are running optimally. I have been looking around for some documentation on the best config settings and windows settings, but I have not been very successful.
Does anyone have any documentation, notes or links that will help?
Thanks in advance
Phil

A system that does not rely on request & response, so that the client can receive information without requesting any.Datagram
The ability for users to send and recieve String messages. (e.g. server announcements).Ditto. Investigate Multicast also.
The ability for users to send and receive objects. (e.g. sending or receiving user information).RMI.
(optional) Security (e.g. encrypted information).SSL.
Possible communication with clients using different technologies (e.g. .NET client) while using a server in Java.SOAP.
I think you should spend a bit more time with Google, or better yet buy a book or three on Java networking. This one is good: [http://www.amazon.com/Fundamental-Networking-Java-Esmond-Pitt/dp/1846280303|http://www.amazon.com/Fundamental-Networking-Java-Esmond-Pitt/dp/1846280303]

WS application configuration - best practice advice

Hi there,
I'm a newbie on web services.
I'm currently developing a Web Service using JAX-WS 2.1 and deploying on Tomcat 6.
I'm wondering where to put my application's configuration. If I was developing a standalone java application I would put it in a Java Properties file or perhaps use the Java Preferences API.
But this is not a standalone java application, it is something that runs in a container, in this case Tomcat.
I have a fealing that web.xml is the intended place to put this information but I've also read posts discouraging this. I'm also in the dark as to how to access the information in web.xml (Context parameters section) from within my web service.
Basically I would like to use a solution which is a much standard as possible, i.e. not tied to any specific container.
Thanks.
Changed typo: "have" changed to "how"

What is the model number of the switch?
Normally a switch that cannot be changed does not have an IP address. So if your switch has an address (you said it was 192.168.2.12) I would assume that it can be changed and that it must support either a gui or have some way to set or reset the switch.
Since Router1 is using the 192.168.1.x subnet , then the switch would need to have a 192.168.1.x address (assuming that it even has an IP address), otherwise Router1 will not be able to access the switch.
I would suggest that initially, you setup your two routers without the switch, and make sure they are working properly, then add the switch. Normally you should not need to change any settings in your routers when you add the switch.
To setup your two routers, see my post at this URL:
http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&message.id=108928
Message Edited by toomanydonuts on 04-07-2009 02:39 AM

BI Best Practice for Chemical Industry

Hello,
I would like to know if anyone is aware of SAP BI Best Practice for Chemicals.And if so can anyone please post a link aswell.
Thanks

Hi Naser,
Below information will helps you in detail explanation regarding Chemical industry....
SAP Best Practices packages support best business practices that quickly turn your SAP ERP application into a valuable tool used by the entire business. You can evaluate and implement specific business processes quickly u2013 without extensive Customization of your SAP software. As a result, you realize the benefits with less Effort and at a lower cost than ever before. This helps you improve operational efficiency while providing the flexibility you need to be successful in highly demanding markets. SAP Best Practices packages can benefit companies of all sizes, including global enterprises creating a corporate template for their subsidiaries.
Extending beyond the boundaries of conventional corporate divisions and functions, the SAP Best Practices for Chemicals package is based on SAP ERP; the SAP Environment, Health & Safety (SAP EH&S) application; and the SAP Recipe Management application. The business processes supported by SAP Best Practices for Chemicals encompass a wide range of activities typically found in a chemical industry
Practice:
u2022 Sales and marketing
u2013 Sales order processing
u2013 Presales and contracts
u2013 Sales and distribution (including returns, returnables, and rebates, with quality management)
u2013 Inter- and intracompany processes
u2013 Cross-company sales
u2013 Third-party processing
u2013 Samples processing
u2013 Foreign trade
u2013 Active-ingredient processing
u2013 Totes handling
u2013 Tank-trailer processing
u2013 Vendor-managed inventory
u2013 Consignment processing
u2013 Outbound logistics
u2022 Supply chain planning and execution Supply and demand planning
u2022 Manufacturing planning and execution
u2013 Manufacturing execution (including quality management)
u2013 Subcontracting
u2013 Blending
u2013 Repackaging
u2013 Relabeling
u2013 Samples processing
u2022 Quality management and compliance
u2013 EH&S dangerous goods management
u2013 EH&S product safety
u2013 EH&S business compliance services
u2013 EH&S industrial hygiene and safety
u2013 EH&S waste management
u2022 Research and development Transformation of general recipes
u2022 Supplier collaboration
u2013 Procurement of materials and services (Including quality management)
u2013 Storage tank management
u2013 E-commerce (Chemical Industry Data Exchange)
u2022 Enterprise management and support
u2013 Plant maintenance
u2013 Investment management
u2013 Integration of the SAP NetWeaver Portal component
u2022 Profitability analysis
More Details
This section details the most common business scenarios u2013 those that benefit most from the application of best practices.
Sales and Marketing
SAP Best Practices for Chemicals supports the following sales and marketingu2013related business processes:
Sales order processing u2013 In this scenario, SAP Best Practices for Chemicals supports order entry, delivery, and billing. Chemical industry functions include the following:
u2022 Triggering an available-to-promise (ATP) inventory check on bulk orders after sales order entry and automatically creating a filling order (Note: an ATP check is triggered for packaged material.)
u2022 Selecting batches according to customer requirements:
u2022 Processing internal sales activities that involve different organizational units
Third-party and additional internal processing u2013 In this area, the SAP Best Practices for Chemicals package provides an additional batch production step that can be applied to products previously produced by either continuous or batch processing. The following example is based on further internal processing of plastic granules:
u2022 Purchase order creation, staging, execution, and completion
u2022 In-process and post process control
u2022 Batch assignment from bulk to finished materials
u2022 Repackaging of bulk material
SAP Best Practices for Chemicals features several tools that help you take advantage of chemical industry best practices. For example, it provides a fully documented and reusable prototype that you can turn into a productive solution quickly. It also provides a variety of tools, descriptions of business scenarios, and proven configuration of SAP software based on more than 35 years of working with the
Chemical industry.
SAP Functions in Detail u2013 SAP Best Practices for Chemicals
The package can also be used to support external toll processing such as that required for additional treatment or repackaging.
Tank-trailer processing u2013 In this scenario, SAP Best Practices for Chemicals helps handle the selling of bulk material, liquid or granular. It covers the process that automatically adjusts the differences between the original order quantities and the actual quantities filled in the truck. To determine the quantity actually filled, the tank trailer is weighed before and after loading. The delta weight u2013 or quantity filled u2013 is transmitted to the SAP software via an order confirmation. When the delivery for the sales order is created, the software automatically adjusts the order quantity with the confirmed filling quantity.The customer is invoiced for the precise quantity filled and delivered.
Supply Chain Planning and Execution
SAP Best Practices for Chemicals supports supply chain planning as well as supply chain execution processes:
Supply and demand planning u2013 Via the SAP Best Practices for Chemicals package, SAP enables complete support for commercial and supply-chain processes in the chemical industry, including support for integrated sales and operations planning, planning strategies for bulk material, and a variety of filling processes with corresponding packaging units. The package maps the entire supply chain u2013 from sales planning to material requirements planning to transportation procurement.
Supplier Collaboration
In the procurement arena, best practices are most important in the following
Scenario:
Procurement of materials and services:
In this scenario, SAP Best Practices for Chemicals describes a range of purchasing processes, including the following:
u2022 Selection of delivery schedules by vendor
u2022 Interplant stock transfer orders
u2022 Quality inspections for raw materials, including sampling requests triggered
by goods receipt
Manufacturing Scenarios
SAP Best Practices for Chemicals supports the following sales and
Manufacturingu2013related business processes:
Continuous production u2013 In a continuous production scenario, SAP Best Practices for Chemicals typifies the practice used by basic or commodity chemical producers. For example, in the continuous production of plastic granules, production order processing is based on run-schedule headers. This best-practice package also describes batch and quality management in continuous production. Other processes it supports include handling of byproducts,co-products, and the blending process.
Batch production u2013 For batch production,
SAP Best Practices for Chemicals typifies the best practice used by specialty
chemical producers. The following example demonstrates batch production
of paint, which includes the following business processes:
u2022 Process order creation, execution, and completion
u2022 In-process and post process control
u2022 Paperless manufacturing using XMLbased Process integration sheets
u2022 Alerts and events
u2022 Batch derivation from bulk to finished materials
Enterprise Management and Support
SAP Best Practices for Chemicals also supports a range of scenarios in this
area:
Plant maintenance u2013 SAP Best Practices for Chemicals allows for management
of your technical systems. Once the assets are set up in the system, it focuses on preventive and emergency maintenance. Tools and information support the setup of a production plant with assets and buildings.Revenue and cost controlling u2013 The package supports the functions that help you meet product-costing requirements in the industry. It describes how cost centers can be defined, attached
to activity types, and then linked to logistics. It also supports costing and settlement of production orders for batch and continuous production. And it includes information and tools that help you analyze sales and actual costs in a margin contribution report.
The SAP Best Practices for Chemicals package supports numerous integrated
business processes typical of the chemical industry, including the following:
u2022 Quality management u2013 Supports integration of quality management concepts across the entire supplychain (procurement, production, and sales), including batch recall and complaint handling
u2022 Batch management u2013 Helps generate batches based on deliveries from vendors or because of company production or filling, with information and tools for total management of batch production and associated processes including batch derivation, batch information cockpit, and a batchwhere- used list
u2022 Warehouse management u2013 Enables you to identify locations where materials
or batch lots are stored, recording details such as bin location and other storage information on dangerous goods to help capture all information needed to show compliance with legal requirements
Regards
Sudheer

ADF Deployment Granularity - Best Practices

Hi People,
If anyone can spare some time to discuss this, I would like some pointers about ADF applications deployment best practices. For example, we have some customers that complain about having to re-deploy the entire application EAR just to add a field "rendered" condition on a single page, and also having to re-deploy the ADF BC model JARs even though the application has only been changed on the view layer.
What level of deployment granularity can we JDeveloper + ADF developers provide to our customers, without the risk of having inconsistency or dependency problems? So far, our strategy is to deploy the BC Model layer to separate JARs and the View Layer in a WAR file, packaging everything in an EAR. Is it feasible to allow the developers to change one single page and generate a deployment archive for just that single page? If not, which arguments can i provide in a discussion to support the single-deployment point of view?
Thanks for your time, and regards!
Thiago

Hi Thiago
Interesting question and one that comes up from time to time with JEE applications. I've been doing some research on this issue, and recently blogged about how OC4J and BEA Weblogic handles this scenario. Hopefully the post and reference to the OTN post gives you more information, though I'd be interested if you're research reveals a different approach.
I'm also hoping this issue comes up at the OOW ADF Methodology chat among the JDev experts, it would be good for the experts to share their different approaches to this common issue.
I know this doesn't give you a direct answer but hopefully will be useful.
Cheers,
CM.

Best-practice on versioning a soa suite-application

Hi everyone,
I recently organised a seminar for customers concerning the Soa Suite Stack and one of the interesting questions asked that day was a versioning-question.
Let's say we've build a bpel/esb application interacting with different external and internal webservices and we've deployed this application to our production environment and we need to change an internal web service.
How can we add versioning to this heterogenous system in a consistent way? I know you can tell esb which version of the bpel process it needs to use, but what about the custom and external webservices that we've integrated with?
My 2 cents: You need to add a versioning-tag to you custom web services that you need to manage yourself, and use this versioning tag in the services your integrating with.
Could somebody point me out what best practice is, or what Oracle's development team is working out regarding versioning systems for SOA-applications?

Marc,
Are you saying versioning isn't supported in ESB now? I thought that ESB already uses the versioning tag from bpel when you're integrating bpel and esb?
During the development of my demo I've seen that the version-tag was used when invoking the bpel process through a soa service.

Best Practice to Setup an application to work with both oracle and db2 db

Hi,
We have an application that currently supports both oracle and db2 databases . It is currently using JPA with eclipselink as backend mechanism and we want to move to ADFBc as our backend . So what is best practice to do this?
I came across an old post in https://groups.google.com/forum/#!topic/adf-methodology/UlJZSTu14Io that states to create two different model projects to support oracle and db2 .
Is this still the standard ? Is there a way that we could work around rather than creating multiple projects?
How do i get the view controller to work with multiple model projects if this is the case?
Thank you.

Thanks for the response .
The problem is i would have the same schema on both the databases (both in oracle and db2) .
I don't see a scenario where i want both the application model projects at the same time . What i meant is , Application will either be deployed with Oracle DB or DB2 but not with both on a production environment .
So is there a way where i just change the connection parameters alone rather having two different models ?
If i have to use two model projects , would it be possible say i built the view controller for Oracle , and use it for DB2 if i make sure the BC objects names are similar between model projects and switch just the model jar based on the deployment environment ?
-Sam

Best Practice - Bounded Task Flows, Regions and Nested Application Modules

Using JDev 11.1.1.3; understand that it's generally considered good practice to just have 1 root application module servicing model content / services for each page. In our application, we've used a number of bounded task flows and page fragments deployed as af:region's into pages as either a) views targeted in page-flow navigation, b) tab panel content inside a regular jspx, or c) af:popup / af:dialog content. As it stands, we've not engaged nesting of the application modules for this embedded region content, so these regions are no doubt instantiating new AM's if/when invoked. Should the AM's servicing these embedded regions be deployed nested within the root AM's, and then if so, does this change the way that the jsff / fragment content is actually developed (currently as per any other jspx using the DataControl pallete). Or are the best-practice directives talking about a page as being the design-time / declarative composition of content rather than the run-time aggregation of page + fragments ... in which case the fact that our embedded fragments are not using nested AM's is unlikely to concern.
Thanks,

Probably a better question for the ADF EMG: http://groups.google.com/group/adf-methodology?hl=en
CM.

Best Practice to use a single root Application Module?

I was reading in another thread that it may be a good idea to have all application modules nested within a single root application module (AM) so that there is only 1 session maintained for the root AM, versus an individual session for each AM. Is this a best practice? If yes, should the root AM be a skeleton AM (minimal customer service methods), or, should you select the most heavily used AM and nest the other AM's underneath of it?
In my case, I currenlty have 2 AM's (and will have 3 AM's in the future) each representing a different set of use cases withn the application (i.e., one supports users searches / shopping cart-like functionality, and the second supports an enrollment process.) It could be the case that a user only accesses pages on the web site to do searches (first AM), or only to do enrollment (2nd AM), or, they may access pages of the site that access both AM's. Right now I have 2 separate AM's that are not nested. Should I nest the AM's and define a root AM?
thanks

Hi javaX
The main physical effect of having 2 separate AMs is that they have their own transactions with the database, and presumably sit in the application module pool as their own instances consuming connections from the connection pool. Alternatively a single root AM with 2 nested AMs share a single transaction through the root AM; only the root AM controls the transaction in this scenario.
As such it's a question of do you need separate transactions or will one suffice?
How you group your EOs/VOs etc within the AMs is up to you, but usually falls into logical groups such as you have done. If a single transaction is fine, instead of creating multiple AMs, you could instead just create logical package structures instead. Neither method is right or wrong, they're just different ways of structuring your application.
When you create a nested AM structure, within your ViewController project in the Data Control Palette you'll actually see 3 data controls mapped to each AM. In addition expanding the root AM data control, you'll see the nested AMs again. Create a dummy project with a nested AM structure and you'll see what I mean.
If you base your page definitions on anything from the root AM and it's children in the Data Control Palette, this will work on the root AM's transaction.
If you base your page definitions on something from one of the other AM data controls that isn't inside the main root AM in the Data Control Palette, instead of using the root AM's transaction, the separate child AM will be treated as root AM and will have its own transaction.
The thing to care of when developing web pages is to consistently use the AM and it's nested AMs, or the child AMs directly with their separate transactions, otherwise it might cause a bit of a nightmare debugging situation later on when the same application is locking and blocking on the same records from 2 separate AM transactions.
Hope this helps.
CM.

BC4J ApplicationModule - best practice in Stateful web application?

When writing a stateful web application that uses BC4J framework as the model, what is considered best practice in using the Application Module. Is it okay to store an AM instance in a HttpSession, or should we opt for the features explained in the BC4J Pooling samples, which uses the SessionCookie interface?
Tips/Tricks/Pitfalls information welcome
Thx,

When writing a stateful web application that uses BC4J framework as the model, what is considered best practice in
using the Application Module. Is it okay to store an AM instance in a HttpSession, or should we opt for the features
explained in the BC4J Pooling samples, which uses the SessionCookie interface? Best practice is to store the SessionCookie (an ApplicationModule handle) as demonstrated in the pooling sample.
This will allow many advantages including scalable state management support, timeout support, and
failover / clustering support.
Caching the ApplicationModule directly can be dangerous because:
1. The AM is not serializable which could result in serialization exceptions if the servlet container were distributable.
2. The AM does not responsd to timeout which could result in memory leaks if the AM is not explicitly returned to the
pool at the end of each request.
3. For stateful applications the memory consumed by each AM could be significant. Even if the AM were correctly
released to the pool upon session timeout it would still have consumed that memory up to that point. Using the
SessionCookie along with state managed release allows for scalable state management.
Tips/Tricks/Pitfalls information welcome
Thx,

Application resize best practice

Similar Messages

Maybe you are looking for