PDA

View Full Version : PenguinEdit


Kjurtyl
2003.05.28, 11:03 PM
At first I had thought to merge HooptieEditor by Ededed and PenguinEdit by Josh and John into a super-editor. That idea fell through once I looked at the code and realized they were:

a) Severely incompatible in structure despite both being done in Cocoa.
b) PenguinEdit had more features that I wanted, such as the bundle-browsing mechanism that would need serious work to implement in HooptieEditor.
c) Because PenguinEdit somewhat followed Hooptie's own code structure it was infinitely easier for me to follow than HooptieEditor's structure which appeared to me as quite convoluted, almost C++-like (read: I kept asking myself; Why this? Why that? Why?).

Therefore, I chose to stick with PenguinEdit and merely embrace and expand it, although not in the usual sense of the word (hopefully).

Thus far, I have:

- added a mouseDragged event to ease level construction.
- added a rock tool to add rocks in levels.
- added an eraser tool to remove selectively as an alternative to a full-wipe.
- fixed the level loading code from an existing bundle so that levels actually load and are displayed.
- made it so the bundle browsing window is still active after opening a level so one can edit each level without having to restart the application.
- fixed the button icons so they look smoother.
- added pit-tiles drawing code so that as you draw pits they use the proper image(s) to form strings of pits as seen in Hooptie.
- Remove the grid - it looked ugly and messed the drawing, anyone think we really really need a grid?

Still missing:

- Proper saving code that doesn't save an existing bundle as new but just the individual level.
- Proper menu commands that allow to add a level to a bundle.
- Proper menu-handling to make the above possible.
- Fixing the currently non-functional buttons of the bundle-browsing window.

I feel a lot has been done and that the work is moving along rapidly. It is my hope that before next week it may be completed.

- Kjurtyl.

P.S. Some of you might remember that my father had been diagnosed with cancer almost exactly one year ago today. He passed away early yesterday morning at the tender age of 59 about four days after his birthday.

Carlos Camacho
2003.05.29, 02:47 AM
Sorry to hear that about your father. Please give our love to your family since the people here are also your extended family.

:sorry:

DaFalcon
2003.05.29, 04:16 AM
The editor you're working on sounds wonderful. I don't think we need a grid.

I am very sorry to hear about your father. Carlos is right, our love goes out to you and your family.

Pazolli
2003.05.31, 08:14 AM
I am also very sorry to hear about your father.

My condolences to both you and your family.

The editor sounds great.

Mark.

Kjurtyl
2003.06.01, 01:00 PM
For the editor, a great part of the work has been due to the efforts of John Nikolai and Josh Abernathy, I just touched it up a bit.

One thing that would be really great though is a custom icon.. any takers?

- Kjurtyl.

DaFalcon
2003.06.01, 01:05 PM
I had already created a "Hooptie Edit" icon, is it not floating around someplace? I can dig that up for you when I get home if that'll work.

Kjurtyl
2003.06.02, 09:50 PM
Dig away, I can't find that icon anywhere.

- Kjurtyl.

DaFalcon
2003.06.02, 11:31 PM
I found mention of the icon, but not the icon itself floating :-) I'll find it ;-)

DaFalcon
2003.06.03, 05:14 PM
I've uploaded it here:

http://www.snakequest.com/other/editor%20icon.sit

Let me know if it is what you're looking for or not :-)

Kjurtyl
2003.06.05, 09:02 AM
The icon is fine and will probably be used, although it looks a bit odd on my desktop since the background is varying shades of blue. It'll most likely be on white anyways and looks fine on that.

I'll try to find a way to either include the completed editor with a release-style package of Hooptie and/or add it to the CVS.

Thanks,

- Kjurtyl.

Chris Burkhardt
2003.06.06, 05:18 PM
I would like if you added it to the CVS. That way it will be "officially" part of Hooptie, and we can all improve it without making a gabillion different editors.

I just installed the Apple Developer Tools on my computer (I had reformatted my drive a while ago, and lost them). I grabbed Hooptie from the CVS, and it has come a long way since I last built it. Kjurtyl, I know you've been working on the project lately, so I'm going to hold off making any changes until you submit yours to CVS. So if you could post when you do, I can update my copy and then start doing something. Thanks, and sorry to hear about your father :(

Kjurtyl
2003.06.06, 06:02 PM
If you grabbed Hooptie within the last five days then there's a big chance you've gotten the version that incorporates my changes. You can update through CVS to be sure.

I'll try to add the editor to the CVS, but I need to figure the best way to add it (separate entity or within Hooptie).

- Kjurtyl.

Chris Burkhardt
2003.06.06, 11:40 PM
Okay, I got it from the CVS this morning so I should have the most up to date version -- I was just confused because when I ran it the first time it told me that I should have Quartz Extreme turned on (I'm running Mac OS X 10.1), and I thought that you were going to get rid of that check.

I would just add the editor as a directory in the Hooptie module (along with carbon and obj-c).

Kjurtyl
2003.06.07, 01:43 AM
it told me that I should have Quartz Extreme turned on (I'm running Mac OS X 10.1), and I thought that you were going to get rid of that check.


:?: I suppose I failed to explain myself properly to a larger extent than originally thought. What you got was not a check but a warning. That means I did get rid of the check, otherwise it should have theoretically crashed your machine. It's now meant as a friendly reminder that QE would be really good to have. Maybe I should add "QE should be activated if available"? Feel free to reword the entire warning if you have something in mind that would be more appropriate.

- Kjurtyl.

Chris Burkhardt
2003.06.07, 01:56 AM
No, it makes sense and works. I just thought that you were going to remove any sort of "environment discovery"; which is why I thought I had old code when I got the warning (without a crash).

OneSadCookie
2003.06.07, 01:57 AM
The average user can't disable QE if it is available, and someone savvy enough to turn off QE is asking for it. Just get rid of the warning, it'll only serve to worry people who can't get QE, and provide very little benefit to the two people who'll ever play Hooptie on QE-capable systems with QE disabled.

Chris Burkhardt
2003.06.07, 02:04 AM
In the warnings defense, it is only displayed the first time Hooptie is ran (I hope that is by design), so if it confuses someone they can just click OK and never see it again.

But I agree it probably is not too helpful... and it shouldn't be displayed on OS versions <10.2

OneSadCookie
2003.06.07, 06:20 AM
And it shouldn't be displayed if the user's graphics card is PCI or an ATI Rage (Pro, 128, ...) card, either. So just kill it rather than trying to figure all that out :)

Kjurtyl
2003.06.08, 04:23 PM
In hindsight, the whole QE thing was quite a fiasco for something that is (according to our usage of it) rather irrelevant. I've wasted enough time on it; I won't work on Hooptie just to remove it. Anyone else feels up to it they can, it's not too much but you may need to track down a user default initialization. That means the official word is: "It's been downsized and marked for deletion, but I won't go out of my way to do it." Nobody should get hurt by it right now and that was the main objective.

- Kjurtyl.