Intec Blog | Comments

Creating a Live Text Widget to Launch an Authenticated XPage

Bernd Preusing — Thu, 12 Aug 2010 01:57:43 AM +0100

Hi Paul,

any chance for a demo db for this tutorial please?

thanks

bernd

Embedded View from a Different Database - A Scalable Alternative

Dominosaurus — Fri, 6 Aug 2010 03:07:59 PM +0100

The frameset solution really helped.

Thanks

Jim

Dojox Charting Tutorial - Part Two: Creating Series and Generating the Pie Chart

Patrick Kwinten — Mon, 2 Aug 2010 03:54:58 PM +0100

we have a survey application which now has only 'reporting functiondality' to spreadsheets (excel). I hope these blog posts of yours may contribute to a more dynamic reporting method...

#{lotuscript:

Patrick Kwinten — Mon, 2 Aug 2010 03:40:33 PM +0100

sounds awesome!

Creating a Live Text Widget to Launch an Authenticated XPage

Bernd Preusing — Fri, 30 Jul 2010 01:34:42 AM +0100

Hi Paul,

Just to find out, if you are in a position to upload the demo db for "Creating a Live Text Widget to Launch an Authenticated XPage". I really appreciate you help on this.

Thanks in advance,

Bernd

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Paul Withers — Thu, 29 Jul 2010 09:09:07 AM +0100

@Nathan The idea of custom languaqges sounds very interesting. I won't be at IamLUG, but I look forward to hearing how it works.

@Tim I agree on the use of a script block. The key is realising when the inline EL will be converted to a literal value and handling accordingly

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Nathan T. Freeman — Wed, 28 Jul 2010 09:24:13 PM +0100

@Stephan well that's just crazy talk right there. :-P

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Stephan H. Wissel — Wed, 28 Jul 2010 08:55:06 PM +0100

@Nathan... so will we see #{lotuscript: ... } from you then?

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Tim Tripcony — Wed, 28 Jul 2010 05:26:10 PM +0100

The mixing of EL is extremely convenient. For example, I often see examples where somebody wants dynamic inline client-side script, so they create a computed field, set escape to false (so the renderer won't munge the markup), and set it's value to something like:

""

This works, of course, but there's a more elegant approach: create a scriptBlock tag, and set its value to:

var someGlobal = "#{javascript:@DbLookup(...)}";

As the XPage runtime is rendering the script tag, it detects the inline EL, and automatically translates the value server-side before sending the script tag to the browser.

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Nathan T. Freeman — Wed, 28 Jul 2010 03:21:04 PM +0100

Sorry, thought my website would show up as a link. Here's the session details: { Link }

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

Nathan T. Freeman — Wed, 28 Jul 2010 03:19:06 PM +0100

At our session at IamLUG, Tim Tripcony and I will show the use of entire EL custom *languages*. So instead of #{javascript: or #{id:, we'll have #{lolcode:

The truth is, because of the extensibility of JSF, it really isn't even difficult to do this.

Breaking the Language Barrier: The Rosetta Stone of XPages Languages

sean cull — Wed, 28 Jul 2010 02:21:48 PM +0100

thanks for this Paul

Exporting to CSV and Multi-Value Fields

Paul Withers — Wed, 21 Jul 2010 02:47:12 PM +0100

@David Thanks for posting about NoteReconn, I remember reading that it had come second in the TeamStudio awards, and congratulations for that.

Untitled

Wed, 21 Jul 2010 02:47:12 PM +0100

Another Option when Exporting

David Jeyachandran — Wed, 21 Jul 2010 12:42:03 PM +0100

Thanks for flagging that issue Paul. I've seen that on the Notes7 client too. Glad to see the solution is so simple.

If you're doing a lot of exports hope you don't mind if I mentioned a tool that I've posted on OpenNTF called NotesReconn. It lets you export to CSV/Excel/XML without writing any code. It's very flexible (eg. you can put formulas to deal with multi-value fields). It came second place in a Teamstudio award last year. It may be overkill for this customer but a handy (free) tool to have in your quiver.

{ Link }

Regards

David

Autosave database size revisited: it SEEMED like a great idea but...

Paul Withers — Sat, 10 Jul 2010 10:12:37 AM +0100

@Stephan My autosave only is local. I went to Replication Settings - Space Savers to reduce the size. Removing it each time the PC is closed down with a batch file seems the best way to ensure it doesn't keep growing. But I'm still confused why changing the default period for removing documents triggers a daily prompt.

Autosave database size revisited: it SEEMED like a great idea but...

Stephan H. Wissel — Sat, 10 Jul 2010 01:33:48 AM +0100

Paul,

2 questions:

a) Autosave wasn't meant to be replicated. It is a local security measure against crashes, nothing to be shared elsewhere. Why does it replicate for your?

b) If your autosave database is empty... why not delete it? It gets recreated on client start. Usually during an upgrade I remove *.box and as_*.nsf

Autosave database size

Dan Nelson — Fri, 9 Jul 2010 08:40:11 PM +0100

Are you sure about the deletion stubs being the cause of your problems? Assuming a deletion stub is 16KB (which is extremely unlikely - they're probably less than 256 bytes), you would have to have created and deleted 25000 documents in the last month (over 800 docs per day) to generate 400 MB worth of deletion stubs :)

You can use NotesPeek to find out how many deletion stubs you have in your autosave db.

My recent work on XPages in an existing web app

Bernd Preusing — Fri, 9 Jul 2010 08:24:11 PM +0100

Hello Paul,

Just to see if you could provide a downloadable demo db for my learning purpose. I know, I'm troubling you on this, sorry about that.

Thanks,

Bernd

Autosave database size revisited: it SEEMED like a great idea but...

Peter Presnell — Fri, 9 Jul 2010 06:04:55 PM +0100

I agree Paul.. I hope there is a way to stop the message, but this is the eensy weensy teeny weeny type of behavior that often alienates Notes users from the product. One user gets the prompt and they immediately complain to everyone around them "how (insert favorite adjective) is this...".