Gumbo effects comming soon
Gumbo: the next release of Adobe Flex SDK interface will has some interesting and useful features. The idea of developing custom controls [like buttons or menues] which slide in and out based on mouse interaction can be problematic to build. The logic of incomplete slide ins and slide outs along with the gittery screen can cause the application to look unpolished.
All of this is about to change as you can see in this video describing the new sequence functionality that will be available in the next release. Have a look at the more complex sequences.
PS: seems that the new release will be hitting the shelf sometime in the second half of 2009.
The sales order … is currently being processed by user …
An inbound IDOC was failing due to the error [described in the title]. Some research resulted in the following results:
TR: SM12 displayed a list of locked elements in the system.
TR: SM04 displayed a list of logged in users in the local system.
TR: SM08 displayed a list of logged in users in all the app-servers [not just the current system].
Unfortunately in my case non of the mentioned transactions above helped me narrow down where the user was locking the system – in the end I’ve requested for the user to log back in and kill his session with a TR: /nex.
Finally no spam
This blog has been plagued by constant spam comment postings, the other day I’ve checked the moderation log to see 1400 unmoderated posts. As you can imagine its very annoying and frustrating to see these things and practically impossible to go through and find proper comments.
So, I finally decided to do something about it and implemented Simple CAPTCHA plug in from WordPress library.
Today I have 0 spammed comments and I am very happy about it. So if you are in the same shoes don’t be lazy like I was and set it up asap.
Adobe Flex Builder 3 short dump [JVM terminated. Exit code=1...]
I’ve tried reinstalling the application and even removed the old versions of JRE references. Nothing helped and just as before I had to rely to googling and looking at configuration files.
The problem lied in the small FlexBuilder.ini file located in the root installation directory. The contents of the file included the following settings:
-vmargs -Xms128m -Xmx512m -XX:MaxPermSize=256m -XX:PermSize=64m -Djava.net.preferIPv4Stack=true
I’ve modified the contents to exclude the last lines and vuala, the application went back to it’s usual state [sure I lost all my projects but its nice to have a working EDI once again].
Workaround for: “Click to activate and use this control” IE problem.
Those of you who have been found of putting up interesting controls on your web pages might have come across the ‘Click to activate and use this control’ bug that occurs in Internet explorer. If you do some searching you will find a lot of posts that require upgrade and an installation of a patch. Having explored the problem my self I offer you an alternative solution:
- Create a javascript function that is initiated when the page is loaded ‘onload’ event.
- Create a tag with a particular id somewhere on your page [lets say "fuzzy_object" for a sake of an argument].
- In your javascript function create a single string containing the specifications of your object [in my case it was an swf file].
- Perform the following: document.getElementById(‘fuzzy_object’).innerHTML = concatinated_string.
This is a tad generic but it should work. If not just let me know and I’ll post a more detailed solution.
Hacking CSS
There’s quite a few links out there that talk about the different methods of hacking IE and Firefox along with many other browsers.
Having been developing in Adobe Flex for the past while I’ve been ignoring the CSS issue but in my latest project I had to face the beast. My goal was to find a way in which I can block particular tags in both IE and in Firefox. so here’s what I found after doing some research.
For a page where you have an internal <div id=”pathway_text_inner”> the following will be ignored in Firefox:
#pathway_text_inner{
_width: 900px;
_padding-left: 10px;
_padding-top: 7px;
}
Pretty much anything that is preceded by an underscore is ignored in Firefox.
Similarly the following is ignored in IE7.
*:lang(en) #pathway_text_inner{
padding-left: 10px;
padding-top: 10px;
height: 20px;
overflow: hidden;
width: 890px;
}
where <body lang=”en”> .
I know there’s been quite a bit written about the subject but I couldn’t find the exact answer from the first Google search that I performed. Hence this post.
Cheers.