Re: Typo is getting poor!

This suggestion will probably not be popular: use a VPS or dedicated
server. If you’re stuck on a shared server, write your own simple
blog or use one of the newer, lightweight ones.

I had continuous problems with Typo on my shared host. I switched to
a VPS with 192 MB RAM and have had 0 problems and continuous uptime
for the last three months. (granted, I’m using a trunk version from a
few months ago).

Geoff

Ruby on Rails Blog | http://nubyonrails.com

After complaining about my RSS sidebar not working, I rolled up my
sleeves
and fixed it. This, after giving a try at Mephisto and finding it
harder to
set up than Typo was. So Typo is back in my good graces, and honestly
there
isn’t any feature that I can think of that I’m eager to have added.
Maybe
I’m too easy to please but it works great for me right now. I’m stable
on
r1004 if anyone wants a recommended trunk version to use.

That said, what reason would one want to go to r1055, or something more
stable between the two?

Ernie

On 16 Jun 2006, at 19:55, Ernie O. wrote:

That said, what reason would one want to go to r1055, or something
more stable between the two?

In all honesty if you have a stable trunk version then stick with
it. I only jumped up trunk to test the thing. But seriously … if
it’s stable then stay where you are.

Gary

What do I do when I fix a bug or defect?

Levi

Ok it’s the simplist problem. But in the admin panel, the menu tabs need
to
be set at 0.8em not 12px becuase some people have bigger font schemes
than
some…

Add it to trac, either as a new ticket or as a patch to an older
ticket. Then, since Trac isn’t all that hot at telling people when
older tickets change, send mail to this list, and we’ll see what we
can do.

Scott

Ah, great. File a ticket, please? I don’t have access to SVN at the
moment, but this is a pretty obvious fix :-).

Scott

How do I develop a patch? Sorry to ask so noobish questions, I am very
new
here.

Ahh, okay.

I’m going to assume that you’re using the trunk with svn not 2.6.x.

Go ahead and edit the CSS file that’s broken. Change 12px to 0.8em.
Feel free to fix whatever else looks broken.

Then run ‘svn diff’. It should give you a patch. If it includes too
many files (like config files, etc), then try ‘svn diff FILENAMES’.
Save the patch to a file, like /tmp/admin-fix.patch

Then create a new ticket in trac (http://typospehere.org/trac) that
describes the problem. Save the ticket, then click on ‘attach’ and
upload your patch.

If the change is really small (as this one probably is), then you can
just cut-and-paste the patch into the ticket, but that usually makes
it harder for us to apply it. I it’s a 1-line change, it’s probably
not a bit deal.

Scott

Wouldn’t I just be easyer for you guys to do it with out my patch?
Becuase
it’s not even 1 line of css, just 4 characters.

Levi

On Sat, 17 Jun 2006, levi mccallum wrote:

What do I do when I fix a bug or defect?

Levi

Submit a patch and a unit or functional test to trac.

Wait for one of the people with submit access apply it to trunk

Matt R. [email protected] Visit my blog!


He’s a deeply religious moralistic cyborg from a doomed world. She’s a
strong-willed blonde doctor with only herself to blame. They fight
crime!

I filed one…

On Jun 16, 2006, at 2:19 PM, levi mccallum wrote:

How do I develop a patch? Sorry to ask so noobish questions, I am
very new here.

You can check out the slides from my Laying Tracks presentation for
some basic information. The presentation was directed toward Rails
development, but much of it will apply to making a Typo patch,
especially the mechanics of generating the patch file. It’s only 16
slides so it’s a quick read.

http://hasmanythrough.com/layingtracks/


Josh S.
http://blog.hasmanythrough.com

Thanks josh

In this case, it’s pretty easy. I’ll try to get to it this weekend,
but I won’t be able to do anything with it until tonight at the
earliest, and probably not until sometime tomorrow. A ticket would
make it a lot harder to forget :-).

Scott