meomeoim

Profiling is a frequently misunderstood concept in web experience factory. This blog entry describes profiling by comparing it to java code, something that more developers are familiar with. Comparing Profiles to Java Code Many people struggle with the concept of profiling and profile sets, but it can be closely compared to a conditional statement in java. Suppose that we have a button that needs to be displayed if the application is accessed from an android device. Coding this using java would look something like this (depending on the framework): if (request.getHeader("User-Agent") == "android"){    button.visible = true; } The same can be accomplished with WEF profiling except we don't have any code to work with, only a button builder with inputs. Ideally, we would want to apply the results of profiling to the builder enable input, setting it to true or false which would effectively replicate what the java code above does. Think of a profile set as a collecti...

Today I finally had the time to resolve a problem I had experienced regarding branches on CVS with web experience factory. Sometimes I want to work with a branch that, for some unknown reason, doesn't show up in eclipse drop down lists. I know it exists, but I have no means to select it. Eclipse and CVS Branches The solution to the problem is documented in this eclipse CVS FAQ list , but it's worth mentioning in a WEF blog because we typically don't check in the .project file. As the FAQ explains, eclipse looks at this file to determine which branches are available for a project, so we have to change the CVS configuration to look at another file instead. Checking in the .project file causes problems when later attempting to check out using the new WEF project wizard . Following the instructions in the FAQ above provides an easy work around. Hope someone finds some use in this tidbit of information.