sorry for douplepost, but i forgot that HTML is neccessery:

mysql meyerweb < meyerweb20050309.sql.dump

Regrads,

Christian

try this:

mysql meyerweb

I am trying out the v11b5 version of S5 and noticed some odd behaviour. You can see two test versions I created to illustrate the oddities, both the same except that one uses the default theme, and another uses the i18n theme:

http://www.carrotpatch.org/s5/test.html
http://www.carrotpatch.org/s5/test1.html

The first problem is perhaps an unexpected case, where the first slide has an incremental list. The entire list is displayed immediately, though the “next” key still pages through each item.

The second problem occurs when an incremental list is the last slide in the presentation. After reaching the last item, pressing the “next” key starts displaying the same page from the beginning again, incrementally displaying each list items.

On a different note, Lachlan Hunt’s most recent blog entry alluded to future changes in progress for S5, restructuring it to make it easy to extend. Can you comment on a roadmap for S5, if any exists? I am interested in enhancing S5 to better separate out themes; if the work is already underway then I would like to know.

I just read about your problems with importing a mysqldump file and if you happen to have access to Paul DuBois’ book “MySQL Cookbook” you will find on page 467 a discussion about NOT using mysqlimport on dump files. You should use a command like
‘mysql [database]

I did have the problem that the return key gets ‘hijacked’ which prevents me from browsing away from the slideshow (i.e. I type a URI, press return and it does not take me there). This only occurs when Adblock is enabled. An object focus conflict maybe?

S5 is really cool though!

I did do a manual clean of the MySQL directories in /usr/local/ which is where the MySQL.com package installs stuff. The problem I kept hitting was that the data directory was unwritable, which meant the initialization routines failed. When I fiddled with the permissions on the data directory, things just got worse. The socket would randomly fire up, but even when it did, I couldn’t get the daemon to come up. Use of the preference pane just seemed to make things worse; it would claim the process was running when I knew damned well it wasn’t, thanks to Activity Monitor.

So I hunted around, found the Complete MySQL 4.0.21 package from Server Logistics, which installed smoothly. It isn’t quite as up to date as the 4.1.10 package I was trying to install from MySQL.com, but I’ll take old and works over new and b0rked any day of the year.

It’s possible that I missed some files scattered around the hard drive, but since these packages don’t seem to come with UNinstall packages, it’s hard to be sure.

At this point, though, I don’t really care: I have an apparently stable MySQL installation, and thanks to comments I successfully imported the database, so I was able to test my update script last night and am ready to kick GK RC2 out the door.

I also ran into a permissions issue….where newest version of mysql used a different authentication type & my password didn’t work…

food for thought?

No jiggling when the window is fullscreen, but a thin blue horizontal lazerline in the control area darkens/brightens

But if I resize the window, I start getting a noticable jiggling of that same line, vibrating up and down as I move the mouse in the control area. When I resize again to fullscreen, the lazerline maintains this up/down jiggling.

Question: why is the lazerline there? It’s the only visual anomaly that I could find…

The problem is due to a rounding error I believe; it disappeared for me in my tests when I defined the size of fonts and linespacing in pixels, e.g. “font: 12px/16px sans-serif” or similar. Also, it occurred with much greater frequency when I combined with alpha opacity fading effects; this was in my FreeStyle Menu script, which has subsequently had its example font sizes defined in pixels and fading animation disabled by default. No more problem.

So perhaps adjust your element sizing code to parseInt() its results and assign as pixels to the document. That should cure the problem!

P.S. How’s the background PNG opacity behavior going? Did you ever get a chance to try that out? I posted a few times to the previous thread and emailed you once or twice to no avail.