Comments for eknori.de

Comment on Joda to the rescue by Mikkel Flindt Heisterberg

Mikkel Flindt Heisterberg — Sat, 12 May 2012 07:27:35 +0000

The date represented by java.util.Date is always the UTC date and hence daylight savings doesn’t apply. Daylight savings and time zones is what the java.util.Calendar is for why this is a perfectly fine approach. Of course the date objects would come from a daylight savings/time zone aware piece of code in a real piece of code where Locale etc. apply.

Comment on Joda to the rescue by Stephen Colebourne

Stephen Colebourne — Fri, 11 May 2012 11:30:18 +0000

As a general rule, LocalDate should be preferred to DateMidnight for cases like this. Thats because in some time-zones, midnight does not occur on the date of daylight savings change – ie. time jumps from 00:00 to 01:00 with midnight never occurring. DateMidnight clearly has issues with this. LocalDate does not have a time-zone and so handles it fine.

Mikkel, your code ignores daylight savings time days that last 23 or 25 hours. More generally, its only really reliable if your default time-zone is UTC. If thats fine in your case, great, but please don’t pretend that the code is equivalent.

Comment on Joda to the rescue by Ulrich Krause

Ulrich Krause — Fri, 11 May 2012 05:49:04 +0000

Thx for sharing, Mikkel. Much easier, indeed …

Comment on Joda to the rescue by Mikkel Flindt Heisterberg

Mikkel Flindt Heisterberg — Thu, 10 May 2012 17:58:55 +0000

While Joda Time is a great library there is an easier way to accomplish what you are trying to do. Simpy remove the time component by doing a simple modulus calculation. I am not trying to be smart about it but we do this quite a lot at OnTime Code could look like so:

Date d = new Date();
long lngTime = d.getTime();
lngTime -= lngTime % TimeUnit.DAYS.toMillis(1);
Date dNoTime = new Date(lngTime);

The latter date object creation isn’t actually necessary for the comparison. An utility function could be like so:

private boolean isSameDay(Date d1, Date d2) {
long lngTime1 = d1.getTime();
lngTime1 -= lngTime1 % TimeUnit.DAYS.toMillis(1);

long lngTime2 = d2.getTime();
lngTime2 -= lngTime2 % TimeUnit.DAYS.toMillis(1);

return lngTime1 == lngTime2;
}

Hope it helps and it helps remove the dependency on Joda Time if that’s all you’re using it for.

Comment on SSJS – @CancelPartialRefresh by Stephan H. Wissel

Stephan H. Wissel — Wed, 09 May 2012 05:03:04 +0000

Sweet. Keep the @ rolling

Comment on Access UserBean from Java by Mark Leusink

Mark Leusink — Tue, 08 May 2012 17:45:44 +0000

Did you also check the source code for the UserBean? It is in the ExtLib download. The get() function is actually pretty handy and you might want to add that to every bean you create to be able to access it in Java:

public static final String BEAN_NAME = “userBean”; //name of the bean

public static UserBean get(FacesContext context) {
UserBean bean = (UserBean)context.getApplication().getVariableResolver().resolveVariable(context, BEAN_NAME);
return bean;
}

Comment on FollowUp: Paul Withers: Extending Themes – Custom Pager Labels by Real estate consultants gurgaon

Real estate consultants gurgaon — Mon, 02 Apr 2012 08:00:22 +0000

Your blog is perfect, and I like this article. I find the information I need.

Comment on Using a RamDisk with Notes Client by Leo

Leo — Sun, 25 Mar 2012 21:18:49 +0000

I make even more on every logon:

del “%homedrive%%homepath%\lotus\notes\data\cache.ndk”
del /Q /S “%homedrive%%homepath%\Lotus\Notes\Data\workspace\Local\*.*”
rd /Q /S “%homedrive%%homepath%\Lotus\Notes\Data\workspace\.metadata\.plugins\org.eclipse.core.resources\”

Comment on TabContainer and RichText Control interaction by Philippe Riand

Philippe Riand — Sat, 10 Mar 2012 23:18:37 +0000

For now, add this dojo module at the page level: ibm.xsp.widget.layout.xspCKEditor. A future build of the extlib will solve it.

Comment on Using a RamDisk with Notes Client by Lauri Laanti

Lauri Laanti — Tue, 06 Mar 2012 14:50:41 +0000

I think that the workspace size setting applies to desktop.ndk, not cache.ndk. That would explain Ulrich’s findings. The cache.ndk size is controlled via notes.ini property “UserCacheQuotaSize” (30 MB is the default).

The RAMDisk idea sounds quite interesting, please post your findings!