paul.kholer paul.kholer | 9 Jul 23:12 2007

Icon LASIK in Denver - LASIK Dallas

LASIK Dallas

Icon LASIK in Denver has performed more laser eye surgery procedures than any other clinic in Colorado. That trend continues with the introduction of Denver Colorado Intralase LASIK which when combined with Icon's custom wavefront or NIDEK EyeTracker technology often leads to 20/15 vision.

Icon LASIK has completed over 60,000 LASIK procedures in Denver. This experience combined with the best laser eye surgery technology including the VISX Wavefront Star4, the NIDEK EC-5000, and now, introducing the Intralase bladeless LASIK system results in the best possible outcome for your laser vision correction.

Read more about the Advantages of Icon LASIK in Denver including the custom wavefront technology and affordable pricing.

Icon's latest laser eye surgery introduction to the Denver market is IntraLase. The degree of accuracy achieved by the IntraLase laser is unprecedented in flap creation technology. Peer-reviewed ophthalmology studies and nearly 1,000,000 clinical cases demonstrate the elimination of the most serious sight-threatening complications and prove that the IntraLase Method leads to a faster, more precise LASIK outcome.

Leveraging this laser eye surgery technology, Icon LASIK has completed over 60,000 LASIK or PRK procedures in Denver. This unmatched local experience combined with the latest custom wavefront, laser technology, Icon patients often see better than 20/20. With laser eye surgery starting at just $499 and with 0% interest, $0 down financing available until December 15th, more individuals can now take advantage of Icon's great technology, experience, and affordability.

If you are interested in receiving a free lasik consultation and to receive more information on the wavefront, intralase, or other lasik technologies, visit Icon's Denver Colorado laser eye surgery. With sixty thousand laser eye surgery procedures performed you know you are in good hands.

paul.kholer paul.kholer | 9 Jul 22:46 2007

Randy Bancino Completes Certification in High Performance Business Development - International Profit Associates

International Profit Associates
Profitable Growth Partners, LLC., a Grand Rapids-based high performance business and people development firm, announced that Managing Partner, Randy Bancino, completed High Performance Business Development certification training provided by the Center for Organizational Design, Inc. of Littleton, Colorado.

Mr. Bancino's background includes many leadership and executive positions in large, global companies, as well as people development at the corporate and University level. He has various degrees, including an M.B.A from Western Michigan University and extensive executive training from the University of Michigan. This latest training and certification continues to add breadth to his world-class business development expertise.

"The program was rigorous, but continuing to grow and add skills in the areas of high performance development was truly exciting," said Randy Bancino, Managing Partner with Profitable Growth Partners. "Our clients continue to demand world class expertise, backed up by real world experience. This additional certification helps us continue to offer the best to our clients."

The week-long certification training, lead by Dr. Roger Allen of the Center for Organization Design, focused on organizational assessment, strategic business design, and executive business coaching. Participants gained greater knowledge of the principles of high performance and their real-world application through a series of lectures, exercises, and case studies.

About Profitable Growth Partners, LLC.
Profitable Growth Partners, LLC. works directly with the leadership of small and medium sized companies to help them harness their potential to accelerate growth and enhance profitability. Through their exclusive Business Acceleration Process and their Top Gun for Business People TM series, the experienced business growth experts with Profitable Growth Partners deliver improvements to a business's strategy, processes, structure, systems, and culture, resulting in measurable improvements in both the top line and bottom line.

paul.kholer paul.kholer | 6 Jul 19:23 2007

Einstein Medical Unveils New LASIK Information Resource As Part of DocShop Expansion - Dr. William Boothe

Dr. William Boothe
Einstein Medical has launched a comprehensive online resource for people who are interested in LASIK and other vision care treatments. The latest in an ongoing series of additions to its website, these patient education pages feature the most up-to-date information about LASIK eye surgery, including recent developments in "bladeless" LASIK and custom LASIK.

For more than a decade, has been providing consumers with information about laser eye surgery and other vision care services by linking them with reputable eye surgeons across the United States and around the world. This recent expansion of DocShop's vision care patient education section includes newly written pages about all-laser LASIK, the cost of LASIK, and LASIK benefits and risks. In addition, now includes updated information about other leading edge vision treatments, such as cataract surgery, treatments for glaucoma, implantable contact lenses, and intraocular lens (IOL) implant surgery.

With the release of the expanded vision care section, reinforces its position as one of the most thorough and detailed resources for information about LASIK on the Internet. The site also contains information about other popular laser eye surgeries such as LASEK and PRK, as well as the promising treatment for presbyopia, conductive keratoplasty (CK). After learning about the vision treatment in which they're interested, readers are able to use to locate and view the websites of vision care specialists in their area.

Since the Food and Drug Administration approved the excimer laser for use in LASIK in the late-90s, the procedure has emerged as the most popular form of elective surgery in the United States. Einstein Medical has vowed to update regularly in order to keep consumers abreast of the latest developments in LASIK technology.

Earlier this month, Einstein Medical announced the release of the newly designed and expanded version of DocShop. The revised version of DocShop's vision care section is part of Einstein Medical's comprehensive plan to make DocShop an even more valuable consumer resource. For further information about or Einstein Medical, please contact Pamela Lund, director of marketing of Einstein Industries, Inc.


Stephen Tan | 13 Oct 21:09 2006

Just checked out cpsskins

I checked out the cpsskins for paris-sprint-2006 release 3610.  I am currently
looking at the recent macromedia flash demos and trying to implement some of the
features.  It seems to me that a lot of the flash demos showcase a different
cpsskins release version.  

Why does the "Portlet perspectives" version differ from the "Using and reusing
settings" cpsskins version?

The portlets button in the 3610 release cannot be moved and prevents me from
adding portlets to the bottom left part of my page layout.  I like the "Using
and reusing settings" cpsskins version better than the 3610 release version. 
How can I checkout that release version?

Stephen T 

David Pratt | 9 Aug 05:50 2006

Negotiation with Pages

Hi. I have been continuing to play with cpsskins and read the code. One 
thing for me that I have not got right is page negotiation. I have read 
the code and the readme but it appear that you are able to set this up 
for folders in the Site Manager area. I wanted to have a page apply only 
to a particular folder so I set my path, used pull down to select the 
choice to apply only to folder and selected a theme - So here's another 
question, why are the pages not selectable here - just Themes? Also 
hoping to hear back on how to get my page frame to be tableless. I see 
this this should be possible since the code exists. Just trying to get 
this to happen through the interface is still evading me. I haven't seen 
the code touched in a while. JM - you must be taking a well deserved 
holiday. Many thanks


yary | 3 Aug 21:01 2006

Trying out z3ecm

Hello all,

this isn't a development issue per se- I just checked out the z3ecm trunk to "check it out" on a brand new zope 3.3 beta 1 instance. Thing is, I don't know how to get it installed and working. I copied the contents of z3ecm/src to my instance's lib/python, then tried moving the ecm and xpdlcore directories up a level... read about and installed the dependencies, but other than that, I don't really know what I'm doing!

Can someone help get me to a point where I can play with z3ecm?

mike | 15 Jul 06:12 2006

Z3 component readiness?

Hi folks,

I'm very new to CPS-Project, and I really need a shared-calendar 
component (and the remaining components eventually as well).

I'm on a fairly tight schedule, so I'm nervous about biting off more 
that I can chew with an instable system. 

What's the realistic status of the Z3 port of cps-project?  I can't 
really tell (and I apologize if it is obvious and I've missed).


proclus | 2 Jul 01:22 2006

FOSS, Science, and Public activism

(Sorry if you get more than one copy of this message, but I felt
that it was urgent to get this important info out.)

The values of freedom and openness are crucial to understanding 
itself, so that civilization and public welfare now depend on 
them, as I argue below.  These values may find their best 
expression in the free and open source software (FOSS) movement, 
and the foresightful example of FOSS developers should now be
beneficially applied to many other disciplines in the context of a
global and public Internet.

It is crucial that we occasionally take time to discuss the
reasons _why_ we release our source code, and this is one of 
those occasions.  There are good reasons for the freedom and
openness which are characteristics of FOSS development, reasons
which should receive wider attention now that they can be readily
communicated to other arenas.  The consequences of doing otherwise
are often catastrophic.

For example, it incomprehensible that Genentech could consider
withdrawing a cheap cure for blindness (ARMD) from the market.

The mechanism of this drug is public knowledge.

This abhorrent situation is a great example of the kind of thing
that will happen if people don't get behind the values of freedom
and openness that we are espousing.  Please let Genentech know
that you find what they are doing offensive.  Publicize the mechanism
so that new compounds can be obtained as replacements.  For the 
future, continued vociferous public activism is required to prevent
such outrages from occurring in the future.

It becomes clear that the compounds which come from common roots,
fruits, and vegetables are a shared human heritage and the free and
open source of the future.  Tannins are another interesting case in
point, because as molecules, and as anti-oxidents, they are similar to
resveratrol (resV), and that molecular mechanism has been anchored to
the public domain via a prior art declaration.  It is a so-called
CR-memetic, which may increase healthy human longevity by many
decades.  Here are some links about it.

Resveratrol mechanism posts from GNU-Darwin list

CR protocol for human bodies

Here is some important recent news about it.

It is exciting to suppose that people can get off the pharmaceuticals
that they are taking with calorie restriction or CR-memetics.  I
personally am trying to get off the cholesterol drug Pravachol, a
statin compound, starting a few of weeks ago.  Write me, and I'll let
you know how it turns out.  From the article...

"Fontana says ...  evidence of "younger" hearts in people on calorie
restriction, suggest that humans on CR have the same adaptive
responses as did animals whose rates of aging were slowed by CR."

I think that it is time to look at the tannins in tobacco leaves.  
There may be other treasures lurking there too.  As you may be
aware there is ample public research into any possible beneficial
compounds that may be obtained from tobacco leaves.  The mechanisms
are there waiting to be discovered.  If you want to post them, just
reply to me and I'd be delighted to host them.

The public establishment of prior art is a time-honed method of
entering inventions into the public domain.  We now have other
methods at our disposal as well.   If you are planning to establish
prior art against future CR-memetic related patents, you might want
to have a look at  Perhaps it goes without
saying at this point that you should please choose a license that
provides for free and broad public access to your memetic.

In that way you will assure that the public health is served by 
anchoring them to the public common, where they cannot be exploited
by those who would withhold them for their own profit.  The DRM 
situation is precisely analogous to this.  Can you imagine doing
science in a world where your ability to read and write your data is
filtered through secret protocols that are hidden from you? I
recommend the Defective By Design campaign to fight the outrage of
DRM, which is incompatible with the scientific pursuit.

It is clear that scientific tools must be demonstrably and
penetratingly understood, or else our claims will likely be skewed
and called into question.  Free and open source software is
a great example of how to make your science verifiable to the
public.  Establishing prior art against future patents is 
another good one, which is precisely analogous in method, 
making the result explicit to the public, free and open to all.
Thank goodness for the free and open software movement, which
gave us such a great example of how to serve the public in this

I am willing to grant that there are particular exceptions to
these rules of freedom and openness, and such exceptions may be
relatively harmless; however, let us posit the opposite, that
freedom and openness are _not_ crucial to understanding.  Think of
the implications.  When people are compelled to learn, they do not
receive the intended message.  It is not understood correctly
or completely.   When crucial facts are withheld from the people
you are trying to teach they become paranoid, possibly unteachable. 
Freedom and openness are obviously the best approach to understanding.

This is not a metaphor for the pursuit of science, but a fact. 
We are learning from nature, and it is ultimately required that
our tools be demonstrably and penetratingly understood, or else
we will receive incorrect lessons from nature.  Clearly this
requires public access to the source code and more.  This 
is why many of us are pressing for public access to scientific

Moreover FOSS tools are becoming ever more important to the
pursuit of the scientific endeavor itself.  In our biophysics
department we are obsolescing proprietary hardware and software
in favor of open standards and free software, which is a
widespread phenomenon in the science sector, and sure to continue.
We build most of the workstations ourselves with commodity hardware,
but we also have some clusters running Debian and FedoraCore.

Some of you will know that I am the lead developer for the
GNU-Darwin distribution.  GNU-Darwin has a FOSS operating system,
which is getting alot of press these days.  Here is an example

How Apple and Microsoft are advancing desktop Linux

I see the article as counter-productive against building a FOSS
coalition that includes democracy, freedom, and public access 
activists, Apple, GNU-Darwin, GNU, and GNU/Linux all linked
together in spectrum.

It is important to alert the whole FOSS community that Darwin
cannot be classified as a free or open source operation system
as of the Darwin-8 revision, because AppleACPIplatform-39 which
is required to boot the system is proprietary.  It is notable that
only the current version of Darwin from Apple is a non-free OS.
GNU-Darwin has a free version, an earlier revision that includes
the source code.  It is FOSS, and we call upon Apple to maintain
Darwin as such, as it has been in the past.  We hope that the
current situation with the kernel and ACPI driver will soon be
remedied so that Darwin will continue as a FOSS OS.

We are asking for free software developers to please write to the
*nix core of Darwin, which is the core OS for both Mac OS X and
GNU-Darwin OS.  Darwin OS, which underlies both systems, comprises
parts from GNU, the BSD's, mach, plus Apple's substantial
contributions to the free software community.  Be consistent with your
philosophy and avoid linkage to proprietary binaries, such as OpenGL
and CoreAudio, except when it is imperatively required in order to
lead users to the values of software freedom.  Under that principle,
another reason to maintain compatibility with the *nix core, is so
that your code will be readily portable to new platforms and usable
by free-software-only aficionados too.  

GNU-Darwin OS is not an obsolete implementation of Darwin OS, or to be
superseded by Mac OS X.  We are trying to lead users to freedom, not
away from it.  By maintaining Darwin core compatibility your code will
remain valuable as the marketplace and industry continues to evolve
(trust me here), particularly as DRM-related problems continue to come
forward. Of course, that means releasing your source code under a FOSS
license, such as APSL.  Darwin OS is a free and open source operating
system that is not going away, so try to focus your coding towards
supporting that standard instead of proprietary software.

Here is the essence of the current problem with Darwin OS.  Apple
replaced working boot code with the following proprietary drivers, 
which are required for the system to boot.



In addition the kernel (xnu) has been taken proprietary in the
recent revisions.  We are not asking for Apple to give away such
things, but rather to continue maintaining Darwin OS as FOSS, which
it already was. 

After repeated attempts by many FOSS developers to get this
situation remedied, nothing has happened.  It is now time for us to
better use the measures at our disposal in order to assure that
Darwin OS remains free and open.  If you are unhappy that xnu and 
the boot drivers have not been released, I would encourage you to
spread your dissatisfaction to other forums, so that Apple will take
notice and commit to a workable free and open Darwin OS from now on.  

Moving on to coalition strategy now, some of you may not know that
GNU/Linux system administration is one of my day jobs.  I manage a
wide range of systems.  Here is a screen-shot of my work desktop, so
that you can see I use the same tools at work that I use at home at
night on GNU-Darwin.  (weekends too, so please read I am your friend)

The only time that I ever use proprietary software is when I am trying
to help other users learn free and open source free software.  I'm a 
long time Apple and GNU/Linux user, and here is the old proof doc ;-}.

Now, it is embarrassing but, I want you to have a look at my cv.

In all my years I have never used Microsoft Windows.  There are only
two exceptions to this statement, where I was helping Windows users to
access our servers at Hopkins.  Clearly, you can get a few things done
without it ;-}.

One of the primary reasons for founding GNU-Darwin was to help people
to put Microsoft behind them,  and it is definitely possible to do it
now.  You have many resources at your disposal to help you leave
Microsoft behind.  Look at the link below to see what you can do
with free software.  Apple, GNU-Darwin,, and GNU/Linux will
all help, and we are largely all helping together, because we have a
shared foundation of free software.

Microsoft is only one example.  That is why we are so insistent that
Apple keep true to free and open source software principles.  We
should ultimately try to leave all proprietary software behind us, so
that we can participate fully in the freedom and openness of the
internet culture and public domain.  What more do we need, when we
have such a rich store of information and so many capable people at
our sides?

Finally, as a scientist, it is obvious to me that this situation is
relevant current and ongoing discussion in the scientific community,
and as such, it is also clear that many members of the various lists
would be interested in the current state of Darwin with respect to
FOSS and with respect to science.  

Here is the crucial point.

The principles of FOSS and scientific inquiry converge.  In
practical terms, how else can you know is what happening in your
experiments?  Free and open source software, open standards, best
promote the scientific endeavor by mirroring its method, but also
they assure that the work is accessible to the public.

Freedom and openness are crucial to understanding, and foundational
to the scientific endeavor, and they should not be compromised. 
There are a few examples of exceptions, but clearly, this matter
will find further debate in the appropriate forums.  We should not
quell debate because a few people are offended or complaining.  
From a scientific perspective that would be incorrect.

On that last point, I would suggest that Apple get on the right side
of the debate, and they will make tremendous headway.  Now is the

Some people will find this message annoying and divisive, and the
delete button is ready at hand for them, but other people will find 
it interesting and engaging.  All as you like.  Let us not quell
discussion because a few people are annoyed.

Some will call this a troll, but I hope that folks will see through
such name-calling.  Trolls are mythological creatures, so don't
believe in them.  Everyone has a right to have their opinion
heard, even if those opinions are divisive or unpopular.  It is
clear that the idea of trolls is being used to attack freedom of
expression.  In fact, freedom of expression demands that we
listen to the so-called-trolls sometimes, and if you are civil, it
helps, so don't resort to name-calling. 

On cross-posting; when there are matters of urgent importance that
affect a broad range of subscriber lists, courtesy must sometimes
take a back seat, and cross-posting is an example of that. 
Cross-posting is to be encouraged when the subject of the post is on
topic.  Each of the various lists will respond in the way that seems
appropriate to the people in that forum, and the threads on the
various lists will diverge accordingly.  As the threads diverge, the
cross-posting addresses should be removed as needed.  Relevance to
all people is an unattainable goal, but messages of the broadest
applicability should have the broadest reach, and discussion should
not be stymied because some find it irrelevant.  I have given this
method due consideration; it is not trolling, not spam, not off-topic,
and cross-posting is an example of something that is sometimes
required according to the felt importance and relevance of a given
subject matter.  

In summary, Freedom and openness are now the bedrock of our
civilization and public welfare depends on these values, so that we 
should actively engage ourselves in preserving and making them happen.
In keeping with these principles it is crucial to note that there are
exceptions to etiquette, otherwise free expression will be overly
channeled, damped, and ultimately suppressed in our forums.  This
notion of courtesy will certainly receive additional consideration,
but meanwhile, let us together get to work on the activism now.  

Duly, I am amenable to valid criticism and able to respond, but please
reply with kindness.  Obviously, feel free to write back, copy, or
send these comments along to anyone else as you see fit.

Michael L. Love Ph.D
Department of Biophysics and Biophysical Chemistry
School of Medicine
Johns Hopkins University
725 N. Wolfe Street
Room 608B WBSB
Baltimore MD 21205-2185

Interoffice Mail: 608B WBSB, SoM

office: 410-614-2267
lab:    410-614-3179
fax:    410-502-6910
cell:   443-824-3451
Jean-Marc Orliaguet | 10 Jun 01:20 2006

CPSSkins updates (as of 2006-06-10)


here are the latest updates on cpsskins:

- lots of user interface improvements (better responsiveness, fixed the 
contextual menu, more "application-like" graphical appearance, a new 
portlet creation panel)  see the animation:

- the style editor has been ported to the Ajax lib (cpsskins.js)
  the amount of javascript code used by the editor has been reduced 
dramatically  (now consisting of 60 lines) the rest being MVC 
components. see

- implemented "presets" i.e. reusable settings that can be stored in the 
ZODB or on the filesystem. For instance, the user can save the settings 
of a given box style and use them elsewhere in a same theme.

- portlets can be registered and categorized by "provider" (there are 
'standard' portlets that come with the application itself, and 
third-party portlets).

- made it possible for third-party products to register translations in 
the "cpsskins" domain.
  (see the tutorial for an example:

- CPSSkins4Five created during the Paris 2006 sprint runs natively on 
zope-2.10 as expected...  There are still some minor issues to solve 
though (the code is at .
   and also see the animation


Jean-Marc Orliaguet | 12 May 21:44 2006

[TUTORIAL] widget creation (cpsskins)


I've updated the tutorial with some code for creating widgets.

In the example, the widget simply displays news items with data coming 
from an RSS portlet.
the animation demonstrates how to "colorize" the widget using the style 



this is the first iteration of the widget API, so it will be simplified 
but the idea is basically:

- providing a template (ZPT, DTML, python, ...) to output HTML markup 
from on a data structure
- providing an HTML preview to be used the style editor.
- registering the widget in ZCML


Jean-Marc Orliaguet | 6 May 20:32 2006

File-system themes (a.k.a "global" themes)


CPSSkins themes can now be loaded directly from the file-system.
see the demo which shows the entire workflow:

this is performed quite simply by first creating them through-the-web 
and by exporting them as a TAR archive, then they can be loaded from any 
package with:

 <configure xmlns:cpsskins="">
    <cpsskins:setup site="site-2006-05-06-18.01.47.tgz" />

such themes are registered in the global site manager upon server 
startup. Use cases are for applications whose appearance needs not be 
modified through-the-web. Portlets located in slots are supported too 
since they're not stored in local folders but stored in a central 
portlet "repository".

Theoretically global themes can be modified, but there is no point in 
modifying them when the server is in production, since they're volatile 
and ZEO-based setups would get out-of-sync.

However there is a case where modifying them in RAM would make sense, 
i.e. when developing a site collaboratively; indeed it is trivial to 
implement automatic reloads from the file-system on svn updates for