At last, Herbal V, the all natural alternative!
Herbal V: An Incredible All-Natural Healthy Alternative To Va Herbal V is the All Natural Approach to Male Virility, Vitality and Pleasure. Available N o w ! Welcome to the New Sexual Revolution. It's the all natural male potency and pleasure pill that men everywhere are buzzing about. Herbal V is safe, natural and specifically formulated to help support male sexual function and pleasure. You just take two easy-to-swallow tablets one hour before sex. And there's more great news - you can get Herbal V for less than $1 a pill. Amazing word of mouth praise on Herbal V has been spreading like wildfire-already over 1,500,000 men have chosen Herbal V. Since it is 100% natural you will never have to worry about safety. Try doctor-recommended Herbal V today and have the greatest night of your life! Herbal V... Bringing Back the Magic! 1,585,000 men can't be wrong. To date over 1 million men have tried the super supplement Herbal V. Here is why: No Doctor Visit Required Available Over the Counter Not a Drug 100% Natural Safe, No Worries Highest Quality Pharmaceutical-Grade Pure Nutriceuticals Guaranteed Potency & Purity Be a Real Man Again! Questions and Answers What is Herbal V? Herbal V is a proprietary blend that was specifically developed as a safe alternative for men who prefer an all-natural approach to address impotence and boost sexual performance. This amazing formula first became popular with Hollywood insiders and the wealthy elite. They were maximizing their sex lives, long before it was available to the general public. How does Herbal V work? Developed by a team whose goal was to create the perfect all-natural aphrodisiac. Herbal V is the result of that remarkable effort. The Herbal V formula contains a precise blend of cutting edge pro-sexual nutrients from around the world that provide nutritional support, making it possible for a man to have a pleasurable sexual experience. What can Herbal V do for me? Herbal V helps support male sexual function and pleasure in a safe and natural manner. Simply put, it can make your sex life incredible. Is Herbal V Safe? One of the great things about Herbal V is that it is not a drug. It is an incredible herbal dietary supplement that provides nutritional support for male sexual function and pleasure. One of the most comforting features of Herbal V is that you never have to worry about safety. Herbal V: Safe - Natural - Exciting Many have speculated that because Herbal V is so popular with men, it must contain prescription drugs or chemical components. Herbal V does not contain any elements or traces of any prescription drug. Herbal V is made using the world's most technologically advanced state-of-the-art cold processing equipment to ensure maximum purity. Herbal V has been independently analyzed by the nation's premier testing facility to ensure purity, quality and to end the rumors that, because it is so popular, it must somehow be chemical. It is not. Herbal V is natural - just as it says on the label. Herbal V is simply fantastic! Herbal V: Ingredients Yohimbe, saw palmetto, avena sativa, androstenedione, guarana, taurine, siberian ginseng, tribulus terrestris. Tribulus Terrestis is certified to enhanced testosterone levels by increasing Luteinzing hormone (LH) levels. Androstenedione which is a precursor to testosterone unlocks bound testosterone and makes it biologically active again quickly. This means a dramatic surge in desire. Avena Sativa Stimulates the neurotransmitter pleasure centers to maximum capacity. This greatly intensifies pleasure. Just listen to what Herbal V has done for the sex lives of people like you! On a scale of 1 to 10, it's a 15. Electrifying. It's like a wonder pill! Justin Q B., New Haven, Texas I haven't had sexual relations in 11 years. Then with Herbal V it was... wow! It works again! Sid R., Lakeland, Florida I had sex four times in one night. It made me feel like a 19-year-old again. Chip S, Beech Mountain, North Carolina Herbal V has turned my husband into a Sexual Superman! I like the fact that it's all natural and has no side effects. It's bringing back the good old days. Jennifer B, Beverly Hills, California The above testimonials are from product literature, and we have not independently verified them. However, the following testimonial is from a "senior" gentleman who has purchased his second bottle of Herbal V. When we heard his words with our own ears, we asked his permission to print them here. Man! I'm wild as I can be! I feel like I'm 25 years old again! I'm not believing this! Mr. Murphy, age 64, Lampart, IL. Risk Free: Double Your Money Back Guarantee If Herbal V does not give the desired results as stated above, simply return the unused portion for a double-your money back refund. No questions asked ! Order Now: Safe, Fast, Secure, Private Herbal V with its DOUBLE YOUR MONEY BA
Re: questions
On Fri, Nov 03, 2000 at 06:49:53PM -0800, thus said Caroline Dahllof: > > Yeah, I thought about adding it the fg image as a layer to the bg image > but I thought that there would be a nicer way of doing it. WHat I am > trying to do is onion skinning. Users want to see two images displayed in > the same display. They want to be able to offset these images. They use > this for cloning. > > Thanks, You know, this would be awesome for the GAP animation plugins, show a bit of the previous or next frame in the display while drawing the current one.. That would really help with cartoon-like animation. Cc:ing gimp-devel because I dont think the GAP author is on gimpcon list. Tuomas > > > caro > > > On 4 Nov 2000, Michael Natterer wrote: > > |Hi Caro, > | > |Caroline Dahllof <[EMAIL PROTECTED]> writes: > | > |> Hi, > |> > |> I have some questions about the gimp and how to do some stuff in it. > |> > |> * I need to display two independent images in a single display. One will > |> be opaque and one will have some transparency. I dont want to add the > |> layers of one image to the other image. They should stay independent. Any > |> recommendations? > | > |Hm, sounds like a hack :) > | > |I'd put the composite preview of the transparent image on top of the > |other image's layer stack. It would be the first element in the image's > |layer list and could be treated specially in layers_dialog.c > | > |gimppreviewcache.[ch] may be the source for creating the layer but > |i'm not sure about that :) > | > |Hope this quick idea is helpful. > | > |> * In the layer and channel dialog there is a pull down menu that contains > |> all the images. It seems to be the case that when ever an image is created > |> or destroyed a new pull down menu is created to reflect the changes but it > |> never seem to get destroyed. ??? > | > |When the new option menu is set with > | > | gtk_option_menu_set_menu (GTK_OPTION_MENU (lc_dialog->image_option_menu), > |lc_dialog->image_menu); > | > |the old one is removed and thus unreferenced automatically. > | > | > |bye, > |--Mitch > | -- .---> [EMAIL PROTECTED] .|\,/| [EMAIL PROTECTED] <-. +> www.helixcode.com - ()-@@ , tigert.gimp.org <+ `-> art director , `--')/ a gimp artist <---'
Re: Gimp tool icons
> I won;t say it's more valid to do it as GIMP does, > but I contend it is at least as valid. I would contend that it is more valid ;) If you hold a paint brush up, and it is loaded with paint it is going to drip on your clothes. Or in this case... keyboard ;) and if you select the paint bucket (watch out) > And I *really* don't understand this one. It's always > been intuitive to me ditto > (and I had nothing to do with that > part of the GIMP.) ditto > If you look in the brushes/ directory under the gimp > library, you'll find the brushes. UI feedback...(for those who care) I used to be a photoshop user back in the 3.* days I switched to the Gimp in 98 timeframe, I figured that hey I know how to use an image editor inside and out I should not have to read about how this thing works. the brushes menu did take me longer to find than most other UI features. However once i found it I did think it was rather intuitive. (p.s. adventually i did rtfm) Jeff On Fri, Nov 03, 2000 at 10:23:03PM -0600, Miles O'Neal wrote: > Zolan Davis said... > | > |Please tell me the rationale behind having the drawing icons point downwards. > > Um, it's *natural*? > > Had you asked why they point from the left, I would > understand your question. But the metaphor of using > a pencil, or a paintbrush, or the others, is generally > pointing down. Yes, your monitor is up compared to > your hand, but most people are used to how you hold a > pencil, or a watercolor brush when painting on a table. > > I won;t say it's more valid to do it as GIMP does, > but I contend it is at least as valid. > > |On my desk, the monitor is above the mouse, and my other applications reflect this. > |Far from becoming one with the brush, the Gimp arrangement seems to exaggerate >indirectness; > |We have to work out where the hot spot is going to be from operation to operation. > > And I *really* don't understand this one. It's always > been intutive to me (and I had nothing to do with that > part of the GIMP.) > > If you look in the brushes/ directory under the gimp > library, you'll find the brushes. > > -Miles Thanks, Jeff --- | (Forrest on his being shot in the buttocks) | | They said it was a million dollar wound. But, the army | | must keep that money, cause I still ain't seen a| | nickel of that million dollars" | | -- Forrest Gump | --- | Jeff Sheffield | | [EMAIL PROTECTED] | ---
Re: Gimp tool icons
Zolan Davis said... | |Please tell me the rationale behind having the drawing icons point downwards. Um, it's *natural*? Had you asked why they point from the left, I would understand your question. But the metaphor of using a pencil, or a paintbrush, or the others, is generally pointing down. Yes, your monitor is up compared to your hand, but most people are used to how you hold a pencil, or a watercolor brush when painting on a table. I won;t say it's more valid to do it as GIMP does, but I contend it is at least as valid. |On my desk, the monitor is above the mouse, and my other applications reflect this. |Far from becoming one with the brush, the Gimp arrangement seems to exaggerate |indirectness; |We have to work out where the hot spot is going to be from operation to operation. And I *really* don't understand this one. It's always been intutive to me (and I had nothing to do with that part of the GIMP.) If you look in the brushes/ directory under the gimp library, you'll find the brushes. -Miles
Re: build problems from cvs
On Fri, Nov 03, 2000 at 08:12:07AM +0100, Marc Lehmann <[EMAIL PROTECTED]> wrote: > Since quite some time I get spurious errors while building gimp: sorry, found it (I am not sure that is, I just checked out the build module in gnome and moved it into the gimp tree. Is that correct??) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Gimp tool icons
It isn't urgent but this seemed the best place to ask. If not, please provide alternative. Please tell me the rationale behind having the drawing icons point downwards. On my desk, the monitor is above the mouse, and my other applications reflect this. Far from becoming one with the brush, the Gimp arrangement seems to exaggerate indirectness; We have to work out where the hot spot is going to be from operation to operation. Widows has given me plenty of experience with risible implementation, but I expect better from GNU. And I expect the designers of a visuo-centric application to understand interface essentials. Otherwise, I wouldn't bother asking. But just in case, let me know how I can change the icons. I'm using v 1.1.19 on W'98 (yes, a bit dodgy, but I'm getting there).
Re: [gimpwin-users] gtkrc
Hi, Tor Lillqvist <[EMAIL PROTECTED]> writes: > It used to be posssible to have a user-specific gtkrc file for GIMP, > in the user's .gimp1.1 directory (_gimp1.1 on Windows), but apparently > this has changed at some time. (I had not noticed.) The user-specific > gtkrc file that user_install (.bat) copies from the gtkrc (_user) file > is not used at all. The GIMP's gtkrc file is now supposed to be a > common one for all users of a GIMP installation. This is a bug and I have just added the missing lines to parse the users gtkrc (as found in ~/.gimp-1.1) after the systemwide gtkrc is parsed. Tor, please check out gimp from CVS and check if it works for the windows version too. Salut, Sven
Re: BMP import
The problem is solved now and the bug report can be closed. Martin Martin Weber schrieb: > The import filter for gray indexed bmp files works correctly when using > gcc / Linux > It does not work correctly when using Visual C++. If I use this compiler > I have to comment out line 394/395. > if (grey) > *temp = cmap[*temp][0]; > With this lines commented out it again doesn't work again with gcc / > Linux. > Can anyone debug this. I couldn't find out where the problem is. > An example could be found find here: > http://homepages.go.com/homepages/m/a/r/martweb/ti.bmp > > Martin
New translations
Hi guys, I've just finished translation of GIMP to Croatian language. Almost 100 files are translated except tips which will be finished in next 3-4 days. Problem is cause I never used cvs, so if you can send me any help... Changes are: New hr.po files in po,po-plugins,po-script-fu,po-libgimp and po-perl Added 'hr' in config files. So what should I do? Please answer me by mail. Tnx
CVS Gimp (1.1.29) on Solaris
Two problems: * When compiling the main app, -lintl needs to be added to the link line. I do not want to touch the autoconf stuff. * When running with LANG=fr: During file_ops_post_init, there is a weird file_proc->menu_path for 'GtkIFCBData' (string pointer = 2). I am tracking this one down. Adding a test for weird pointers allows Gimp to start, and looks like everything works including translated messages. David Monniauxhttp://www.di.ens.fr/~monniaux Laboratoire d'informatique de l'École Normale Supérieure, Paris, France
AVI plugin
Looks like the AVI plugin is causing some trouble on Solaris: warnings when i18n is turned off: Gtk-CRITICAL **: file gtkitemfactory.c: line 609 (gtk_item_factory_from_path): a ssertion `path[0] == '<'' failed. Gimp-WARNING **: entry refers to unknown item factory: "" and a segfault if i18n is on. I'll try to nail this one better. David Monniauxhttp://www.di.ens.fr/~monniaux Laboratoire d'informatique de l'École Normale Supérieure, Paris, France
BMP import
The import filter for gray indexed bmp files works correctly when using gcc / Linux It does not work correctly when using Visual C++. If I use this compiler I have to comment out line 394/395. if (grey) *temp = cmap[*temp][0]; With this lines commented out it again doesn't work again with gcc / Linux. Can anyone debug this. I couldn't find out where the problem is. An example could be found find here: http://homepages.go.com/homepages/m/a/r/martweb/ti.bmp Martin
strange configure errors with perl in 1.1.29
I found some strange errors while configuring Gimp-Perl in 1.1.29. The previous versions worked fine (1.1.25 and 1.1.26 from tarball, 1.1.27 and 1.1.28 patched from previous version) so this looks like a new error. What happened was that perl could not find the required modules (PDL, Perl-Gtk, Parse::RecDescent) although they were installed correctly and were working with all recent versions of the Gimp. After a bit of investigation, I discovered that the perl configuration script was not using the right version of Perl! Instead of taking /Local/bin/perl which is listed first in my path and has all the required modules installed, it was taking /opt/local/perl5/bin/perl which comes later in my path. This older perl executable is also symlinked from /bin/perl and /usr/bin/perl, but all these directories come after /Local/bin. Here is the output from the top-level configure script, which also shows another problem with a missing Makefile in devel-docs/pdb/: [...] creating devel-docs/libgimp/Makefile creating devel-docs/pdb/Makefile Can't open ./devel-docs/pdb/Makefile.in creating data/Makefile creating data/brushes/Makefile [...] creating help/images/Makefile creating config.h invoking perl for configuration... WARNING: unable to use PDL (the perl data language). This means that normal pixel access is non-functional. Unless you plan to use Tile/PixelRgn functions together with PDL, this is harmless. The plug-ins using PDL, however, will NOT WORK and you can NO LONGER install PDL later. You can get PDL from any CPAN mirror. checking for PDL support... no NOTICE: You are using a version of perl older than 5.005. This will slightly reduce the features available to the Gimp-Perl extension. NOTICE: unable to use the Perl-Gtk interface. Many features (like Gimp::Fu) rely on this extension. You can build without it (and many scripts will be disabled or run with reduced functionality only), but it's better to install it (version 0.6123 or higher is required, you can get it from ftp://ftp.gimp.org/pub/gtk/perl/ or any CPAN mirror. NOTICE: Parse::RecDescent not found, scm2perl, the Scheme->Perl translator, will not work. This is normally not a problem, since it is quite unimportant for most people. building embedded perl module... no writing Gimp/Config.pm... ok Checking if your kit is complete... Warning: the following files are missing in your kit: po/Makefile.PL po/update.sh Please inform the author. Warning: prerequisite Gtk 0.5 not found at (eval 4) line 221. Warning: prerequisite PDL 1.99 not found at (eval 4) line 221. Warning: prerequisite Parse::RecDescent 1.6 not found at (eval 4) line 221. Writing Makefile for Gimp::Lib Writing Makefile for Gimp::Net Note (probably harmless): No library found for -lgimp Writing Makefile for Gimp::UI Writing Makefile for Gimp [...] I do not understand why this happened. Going to the perl plug-in directory and typing "make distclean; perl Makefile.PL; make" seemed to solve the problem, but configuring from a freshly extracted tar file did not work. -Raphael P.S.: Thanks to Simon for the splash screen. I will still try to finish and upload mine in case we ever need a 1.1.30.
build problems from cvs
Since quite some time I get spurious errors while building gimp: Making all in build make[2]: Entering directory `/localvol2/cvs/gnome/gimp/build' make[2]: *** No rule to make target `all'. Stop. However, since some time now a re-run of autogen.sh does not fix this. Now, what is this build directory (it is empty here, the ChangeLog mentions it a few times but it is not in CVS). -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
