Anyone know how to remove or supress the enoying dialog boxes when developing xPages
If you are just making small xpages application you might not see these very often, but the more complex your xPages get you see these all the time. specially when you navigate your xpage using the outline view or during build
I click the x several times every day to get rid of it, Not sure if the operation quits when I click the x or if it continues in the background.
I would like a setting to get rid of it once and for all
Well, in your designer, you should disable Build automatically in the Project menu. This will remove the constant build, but also means that you have to build manually, when needed.
You could also take a look at Nathan T. Freeman's post on the matter # Making Domino Designer work like you want
Are you using any java libraries added to the webinf/lib dir in your nsf? I noticed that when adding any jar files to the lib dir rebuilding your application can take ages..
I had 2 external jar files used in my project (contained within the database). It used to take around 5-10 minutes to compile the project. Any changes to the XPages/Custom Control/Java files needs a recompile. And you can imagine the frustration I had with the compilation time. Later I detached the jar files and put under the jvm\lib\ext folder. The compilation time drastically reduced to 1 minute. Still not happy.
As a next step, took a local replica of the database and started making the changes and recompilation on the local replica. Once done, replicated the databases and always previewed the changes on the server version. The compilation time is hardly 10 seconds. So 10 minutes to 10 seconds :)
Switch off build automatically, it will solve most of these.
There is also a known issue SPR SODY8Q9KNA where Java Design elements (new feature in 8.5.3) keep getting rebuilt on designer start up. That brings up the same pop-up.
There should be a fix for that in 8.5.3FP1 but I am not in an official position to say it will be in FP1 until it actually ships. You can check in the release notes as they are updated.
http://www-10.lotus.com/ldd/r5fixlist.nsf/(Progress)/853%20FP1
Related
Every time I am inside a Java or XPages/Custom Control file and save the file it takes an unusual amount of time to complete the save operation (about 5 seconds).
While saving, the cursor rapidly switches between the standard cursor and the loading wheel - looks like it does so by the millisecond.
When inside a small project I have no issues - but after working a while and the project gets bigger the issue starts to show and worsens the bigger the project gets. It almost seems like the Domino Designer is trying to save every file in the project (which it does not do).
The only file I don't have this issue with is the faces-config.xml.
As mentioned above, I'm working with the IBM Domino Designer (9.0.1FP6). Also, the Domino Designer is running inside a Windows 10 Virtual Machine using VirtualBox.
The problem started to appear a couple of weeks ago.
No problems before that.
"Build Automatically" is not enabled and I made no significant changes to preferences - at least not that I'm aware of.
As Sven Hasselbach and Per Henrik Lausten pointed out the issue might be the server I am working on - Working on a local replica resolves the issue.
I've been working on a Rascal project in Eclipse 2018. The project is roughly 500 LOC. My problem is that saving a file within the project takes about 20 to 40 seconds. This is due to rascal_builder running after every save.
Since I am accustomed to saving many times during editing, this is starting to reduce my productivity. Is there a way to stop rascal_builder from being invoked every save and have it run only when actual execution of the program is requested? I am not interested in conserving the syntactic annotations for e.g. wrong declarations, missing quotes etc.
Yes, in the configuration part of eclipse, CMD+, on Mac, go to the Rascal section and disable the experimental compiler flag.
I am trying to run my projects in Eclipse, whenever I used to run any program a window appear and it shows that project is launching and building.
This never happened before. In fact, it was working very okay an hour before but now, even for old created project it showing this and not moving ahead.
Is this a general thing happened in eclipse as I haven't seen this before.
I want to get out of this to move ahead and to run the project.
The Launcher looks like this :
The progress Bar is also not moving ahead if it's building the project.
It's definitely normal to see; there's times I'll see it two or three times in a day. It shows up if the launching process is waiting on anything or is expected to take more than a couple seconds.
In your case, it seems to be stuck on "Building workspace," which happens when you open Eclipse. The more projects you have in Eclipse and the more sections of workspace you have (groups of tabs), the longer it takes to build your workspace. So I'm going to wager a guess that you tried to launch a project within the first minute or two of Eclipse being open. Am I right?
If that's the case, just wait a bit, and watch the lower right corner (where it says "Launching Clock" in your screenshot). When it shows it's stopped trying to do start-up tasks, you should be good to go.
If Eclsipse had been open for a while, then perhaps Eclipse is busy with other junk and calling it "Building workspace." Maybe it's having a hard time understanding what to do with one of your projects, so check for compiler errors. You can also try to "clean" your projects (Project -> Clean).
If that also fails...hmmm...I'm sure there's other options before you get to this point, but you might need to re-install Eclipse. I suppose there's a chance that in the deep dark corners of Eclipse, a file was corrupted, causing Eclipse to hang on a task that requires a missing/bad file. But before you go this far, make you get second or third opinions, because I might be missing some simpler cause of your Eclipse hanging than what I've listed already.
I found the solution.
I don't know what was the error and why it was displaying the Launcher window and stuck there. But, I forcefully stopped eclipse using Task Manager and then restarted it.
When restarted it took few minutes (more than usual time) and I was done with it. now it's working okay.
Re-installation of Eclipse also worked but i tried this before re-installing or upgrading.
I use Eclipse IDE for my java projects and there are times in which I need to change some constants and test the effect of it.
But on change of the code I have to rebuild it which generally takes me 40 min and 5 more mins to start the server in debug mode.
So I am looking for some tools which make my task easy like cutting the rebuild time at least by 50 %.
You can put your constants out of the code. Put them in a properties file for instance. Then change your code to read the constants right from the properties file.
You will be able to build your code once and change the constants whenever you want.
If you're not already using it, you probably should look into setting up a continuous integration solution like Jenkins. You could automate builds to poll your code repository and monitor for changes, then run a suite of builds and tests with different flavors of constants to see the effect on your system.
Recently I tried to build a flash application in Flash Builder, and I wanted to export it to my iPhone. I have gone through all the required steps in order to certify my application.
Now, with all that done, all that was left to be done is building the ".ipa" file in Flash Builder. Now, this gives the following error:
'Launching TestGame' has encountered a problem.
Error occurred while packaging the application:
NotBefore: Wed Apr 11 18:52:40 CEST 2012
Google didn't give me a decent answer, nor does Adobe's information regarding mobile application development. All I can think off, is that I can't build the application before that date. That's ridiculous, I can't imagine a certain check like that.
I'm pretty sure my ".p12" key file is generated correctly.
Is anyone else familiar with this error? Please, be so kind to guide me in the right direction.
Kind regards,
Matthias.
The error occurs because the compiler didn't find the files under the corresponding directory such as debug-bin or release-bin folder. (explains from: http://forums.adobe.com/thread/893772)
For example, if you are doing a debug-build, and you didn't select the project option: copy non-embeded files to the output folder. And debug-build needs some files such as icons files under the debug-bin folder, and it couldn't find it.
Solution: select project compiling option: the copy non-embeded file to the output folder.
Try again, if still not you will need to try the ADT build to get more details http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac35eb7b4e12cddc5fbbb-8000.html
I suggest compiling from command line. I'd ported an AIR app to iOS and compiled using adt dirrectly (without FB or whatever), and there were more meanful messages then yours. Take a look at the manual on how to build ipa wit adt. The other advise is to check your iPhone node in app.xml (take a look here) and icons.
The "error" was thrown because the certificate wasn't valid yet. It became valid on the date shown above.
You could also fix the manifest file in the iOS developers center.
This problem does come up more often than needed. The error reporting is lacking distinctions but is also difficult to asses since there can be many factors causing this error. If it was one factor or even just a few then it would most likely let you know.
A great way to ensure that the error reporting can do its job and tell you where the problem is is to check your error log. It will tell you at least a few of the places that threw the block.
If you are unable to read those strange glyphs then just ensure that all your resources are being packaged. This does mean a little time of list checking but it is well worth it, for the errors and to get rid of development junk.
The first step in the asset list check is to go through each part of your Assets class (flash builder reference). If you do not have a direct Assets class then you may want to make one and move all of your asset calls to that one class - since it will save you time if this happens again.
Your Assets class is not the same as your Assets folder. Your folder is where the files are stored - i.e. images, bitmaps, sounds, etc. Your Assets class is what categorizes and assigns references to each individual file.
Go through your Assets class to ensure that each of those files exist in the folder as well. Then go to the Project menu (top near Navigate and Search) and select Clean. Either clean all your projects or check the current one. Once this is done you need to click on your Assets Folder (right click or highlight and hit edit or whatever), and select Refresh. This will check that all the files are still there and get rid of/update them.
If none of this throws an error -red X- or other errors then you need to check your project .xml file. This may take you some time to ensure that all of your add on packages and details are correct. Make sure you have the correct:
at the top and it matches your current air release.
Make sure all the filenames, names, ids, version numbers, aspect ratios, fullscreen, visible, icons, extensionIDs, and everything else are not only correct but actually there. Most of these statements should have something written and not be blank. If they are blank find out what to put in.
Ensure that you have the proper icon file extension. If it says assets/icon48.png and the icon48.png is actually in assets/pictures/images/icons/toomanyfilesextensions/whatever/icon48.png
you need to fix that link.
The last thing that you will need to check is when you want to either Release Build or Debug. You need to make sure that all assets are checked and selected.
Go to Project - Properties.
then select ActionScript Build Path.
Click the Native Extensions tab and see if there are any red X's. If there are tap the little arrow beside them and see what the matter it. Add the correct ANE or get rid of it or whatever you need to do.
Then in the same menu go to the left and select ActionScript Build Packaging. A little arrow should be beside that one too. Tap the arrow and it will open to Apple iOS, BlackBerry, Gooogle and whatever else you have (probably nothing more). Select the OS your want to use, lets say Apple, and you will have 4 tabs pop up. Make sure you have the correct certificates selected. If you have none or are confused about this you need to spend some time on Google.
The biggest one for this error is under the Package Contents tab. Most people miss this!
Open the tab and see if anything is not checked. There will 99.99% be something or many of them not checked if you are getting this error. Just check them all and you can figure out what you need and don't need later. Some of them will be listed because you just threw in a bunch of ANEs and .SWFs to have some awesome app. Those add on packages will throw in unnecessary contents into this package. That is fine and don't worry until you want to be picky. Just make sure they are all selected and hit Apply and Ok.
That's it. You should have a working Release Build if you did everything else correct and this error should be easy from now on (but time wasting).
You may get a 'slip' error now, but that is another story. But that is a great sign because you are getting closer to that stupid mistake that we all make: the elusive spelling mistake.