In Designer today, you can change your mind about what language you are writing an agent, web service, or script library in. (On button events, etc., too, but we're not going there yet!)
Would it be a huge hardship to lose that? Do you really change your mind about what language you're writing something in? If you do, would it be horrible to have to go create a new agent or whatever in that case? (Bonus - you wouldn't have to live through the "Are you sure/all existing code will be lost" message, and actually you would no longer necessarily be losing anything unless you chose to delete the item you were in!
It is a simpler design (that's what's in it for us!)
We made a similar change to script libraries in Release 6, and I didn't hear any issues, but taking it this much farther bears a question...
Thursday, November 29, 2007
Saturday, November 17, 2007
and then there were five.....
Our stairway has six picture frames, as does my office shelf. Each year in the fall, there's a ritual - open up the back of each picture and put in the new school picture for the year. It is a nostalgic moment as each picture frame holds all the previous years' photos. As time goes on, it can be quite a struggle to close the back of the frame again.
It started with one frame, when my oldest had his first school pictures taken. It built up to six picture changes for the years when they were all in school. Then there's senior year in high school... Time freezes for four years until the college yearbook picture (or longer if said son doesn't believe in such things).
The frame for my oldest son contains the picture from his college graduation day, walking down the steps with his diploma in hand. The next three have been frozen in time as high school seniors as they are still in college or working.
Today my fifth son's senior picture went up on the wall. We went through each of the pictures in the back - a frame by frame documentary of his metamorphisis from day care to almost eighteen year old man.
I likely won't see Tom's grade school pictures again for at least four years. Next fall, we'll only go through Rory's pictures. And the year after that, this moment repeats with Rory.
The fall after that... I have to believe I'll just open up all those pictures and remember anyway.
It started with one frame, when my oldest had his first school pictures taken. It built up to six picture changes for the years when they were all in school. Then there's senior year in high school... Time freezes for four years until the college yearbook picture (or longer if said son doesn't believe in such things).
The frame for my oldest son contains the picture from his college graduation day, walking down the steps with his diploma in hand. The next three have been frozen in time as high school seniors as they are still in college or working.
Today my fifth son's senior picture went up on the wall. We went through each of the pictures in the back - a frame by frame documentary of his metamorphisis from day care to almost eighteen year old man.
I likely won't see Tom's grade school pictures again for at least four years. Next fall, we'll only go through Rory's pictures. And the year after that, this moment repeats with Rory.
The fall after that... I have to believe I'll just open up all those pictures and remember anyway.
Saturday, November 03, 2007
does anyone use the Tools menu?
In Release 6, we added a feature to allow people to add their own menu items to the Domino Designer tools menu. It would allow you to set the contexts in which these tools should run, and you could specify a formula or a simple executable to be available on the menu in these contexts.
This is different from how one would normally extend Eclipse so I'm not convinced it's a good fit with the new Designer. It's "just code" so we could bring it over, but is it worth the effort? Is it helpful to allow users who may not yet be Eclipse savvy enough to extend it with another mechanism, or is it just confusing to have more than one way?
Inquiring minds want to know first if anyone ever used this function, and second, what to do with it now?? thanks :-)
This is different from how one would normally extend Eclipse so I'm not convinced it's a good fit with the new Designer. It's "just code" so we could bring it over, but is it worth the effort? Is it helpful to allow users who may not yet be Eclipse savvy enough to extend it with another mechanism, or is it just confusing to have more than one way?
Inquiring minds want to know first if anyone ever used this function, and second, what to do with it now?? thanks :-)
Subscribe to:
Posts (Atom)