CycloEdit Professional

Proxy Support ...

2009-02-17T16:01:00.004-07:00

I'm currently adding proxy server support to CycloEdit Professional as well as making a couple of quick little under the hood fixes.

You can read more about this build and get a copy of it (it's not an official build yet) here.

Working the piecemeal ...

2009-02-16T22:46:00.002-07:00

Right now I'm working on future CycloEdit Professional features as stand alone applications and testing the waters with them - getting the kinks out - and making sure they should even BE in CEP. CycloSkinTastic is currently out - which allows browsing, downloading, unpacking, validating and deploying of skins for your CycloDS Evolution quickly and easily Check out the VenerableSoft site for more information.

1.01 Released

2008-11-22T10:09:00.003-07:00

Use your updater to get 1.101 before getting the latest 1.5 firmware from Team Cyclops.

V1.101 will successfully download and deply the new firmware. Be sure to UNCHECK the INCLUDE BETA VERSIONS option before checking for updates!

What's the latest?

2008-11-17T22:24:00.002-07:00

Now that I've had a decent vacation away from the CycloEdit Pro code, I've started looking at enhancements to the program.

Many user suggested features are up next - things like updating the software without a microSD card in place, deployment of the actual program to your SD card (see the forums for one user's solution - pretty cool), etc.

Two large features on their way - one is still a secret, and the other is a revamp of the deployment system. I've been working behind the scenes with certain users, trying to figure out the "light" way to handle things (i.e. not relying on DAT updates, etc) to handle the needs of a proper "deployment" system.

I think everyone will like it. It will be EXTREMELY simple to use, but VERY robust under the hood (the way the best software should be).

Stay tuned for more info!

Renaming during deployment fixes ..

2008-10-17T06:16:00.001-07:00

V1.09 -> V1.1
* Fixed some games not renaming properly during a deployment (many more to fix)
* Added notation in the status window when a game fails to rename during a deployment.
* Added exception codes displayed when a skin's top/bottom fails to load/render. This should help us chase down some bugs.

New feature for deployment

2008-10-16T06:09:00.000-07:00

V1.08 -> V1.09
* Experimental support for .SAV renaming during a deployment. This is a move toward being able to "redeploy" your existing content back to your card.

So, if you have:
- xps-fhts.nds and xps-fhts.sav
... if you rename ROMs during the deployment, you end up with something like:
- Final Fantasy A2.nds and xps-fhts.save
... which of course, will make your save 'disappear" since the filenames no longer match.

With this build, it will attempt to rename that save file to the new game title during the deployment.

NOTE: This does NOT support alternate save folders! So if you .sav files aren't with your .nds files, then this will not work. I'll add alt save folder support next build.

"Skins skins skins! ... the tigers are playin ... TONIGHT! I never miss a game"

2008-10-14T21:44:00.001-07:00

V1.07 -> V1.08
* Another skin chaser. The icons used to build the bitmap for the bottom screen were (like the top and bottom screen before) being held open as resources. I've converted the resource routine to match the top and bottom screen allocations - and I think that will do the trick.

Skin deleters -- unite!

Updates and more ...

2008-10-14T11:34:00.001-07:00

V1.05 -> V1.07
* The program form is now bigger to accomdate the overwhelming requested feature of full skin preview. Some areas will continue to look 'padded', while other areas that were "crunched" before now have some breathing room.
* Once again, I believe I have the skin deleting problem licked, but - time will tell. It's all about resource management man ...

Another shot at skins ....

2008-10-13T21:04:00.001-07:00

V1.04 -> V1.05
* I have removed all references to .NET 3.x. This should now be a full 2.0 compliant application.
* I think I nailed down the skin deleting (again). Let's hope this works.

Skin woes walloped

2008-10-09T22:20:00.001-07:00

V1.03

* I believe I finally got the deleting of skins down now. No more problems deleting skins (I hope).
* Invalid XML in skins should no longer send the program into an infinite loop.
* Many beta testers do not have the empty.bmp file that is required during the deletion of skins. This is now automatically downloaded if the user is missing it.

For your dialup folks ...

2008-10-09T17:52:00.001-07:00

V1.01 -> V1.02
* I figured out how to check the cheat file date without downloading it! No more "skip cheat file" option.
* Added an option to view the WHAT'S NEW about the cheats file and CycloDS firmware. The what's new with CycloEdit will come later - that takes a little more effort to make happen.

1.01 ...

2008-10-09T14:50:00.001-07:00

I threw a quick 1.01 up .. this fixes problems when deploying skins that have incorrectly been zipped up into subfolders.

Not much of an upgrade, but will help a lot of people.

So ... whats next?

2008-10-08T12:19:00.002-07:00

There are several small features yet to be included with CycloEdit Professional. The top ones are:

- Getting the RERESH CARD and DUPE CHECKER working
- A feature I want to do called CLEAN UP CARD will walk the card and rename all the ROM files to their "proper" Game Title name and rename the save files too.
- Add a deploy mode for SELECTIVE BACKUP that includes the card structure

Some or all of these will hit 1.01. I don't plan on using my full resources to add these updates, however. I want to get a site update done on DualScreenRadio.com - and I need to divide my time up a bit better to make that happen :)

If you're a CycloDS Evolution user, you really owe it to yourself to come over the DualScreenRadio.com and check out all the goodies we have to offer.

Found the problem with skins ...

2008-10-07T22:32:00.002-07:00

I forgot to included the empty.bmp file with the zip distro. Just redownload 1.0.

Early bug reports on 1.0 have been light and the launch appears to be a success!

V1.0 released

2008-10-06T14:07:00.000-07:00

Well, I've decided to release V1.0 of CycloEdit Professional.

Big thanks to everyone with suggestions and comments and bug hunting!

Still plenty of debugging to do ... 1.0 is almomst SYNONYMOUS with finding bugs, so keep them coming.

Please, start leaving you opinions for what you would like to see next. Already on the slate are the dupe checker, the card refresher and both screen skin preview.

What else would you like to see most?

Beta firmware users - update now!

2008-10-03T22:30:00.001-07:00

V0.97b -> V0.98b
* Forgot to add 1.5b4 to some internal tables to toggle certain options ... this is fixed. Recommended EVERYONE update.

Threaded web calls!

2008-10-03T20:13:00.000-07:00

V0.96b -> V0.97b
* All web accesses are now threaded. The app shouldn't feel like it's locked up during those LONG downloads and you get an activity bar.

This is damn near RC1 folks!

Update as usual inside CycloEdit.

Skin updates ...

2008-10-03T13:45:00.002-07:00

.95b is available ... this adds some enhanced, requested functionality to the Skins section. It now displays the default skin name and allows SINGLE click access to the preview.

Update inside CycloEdit Pro.

Link to the original beta ..

2008-10-03T08:15:00.001-07:00

There is now a perm link to the original beta - get it and update immediately to ensure you have the latest build.

Regressions ...

2008-10-02T11:49:00.000-07:00

Regression bug snuck in. Renamer was failing. New build. Just update - problem solved :)

2008-10-02T10:08:00.000-07:00

Forgot some changelog info (and another new minor build)...

V0.92b -> V0.93b
* Deployment folder setting now sticky. Should make testing easier :)

V0.9b -> V0.92b
* Formatting of text files now works! Remember to check mark it before doing your deploy. The code is identical to my WrapIt command line tool. See that for more information on protecting areas, etc.

New build ...

2008-10-02T09:57:00.002-07:00

What can I tell you? Wrapit easily integrated into my code.

So, now, the deploy center is basically done. I still need to handle the collisions and cleanup efforts, but CORE functionality is done.

Yes, I am aware that your deployment folder isn't "sticky" and resets each run. That's on my list of things to do.

Anyway, if you've used my Wrapit tool, this works the same way. Look here. Is it perfect? No. Is it better than nothing? Yes!

We are fastly closing in on 1.0!

Let's put out the beta!

2008-10-01T21:51:00.001-07:00

I'm not done, but happy enough for a beta!

V0.87b -> V0.9b
* Deployment Tool is partially operational! Here are the known issues:
- Formatting of TXT files isn't implemented yet. You won't get an error, but it won't do anything either.
- Filename collisions aren't handled and will error out the program
- Clean up of NFO, DIZ, etc files doesn't occur yet. They will be copied over.
+ Secret revealed! Renaming by Game Title during deployment implemented! No database, dat files etc needed! Title is pulled from the game!
* Various small fixes.

Get V.9b via the update center!

Understanding the Deployment Tool

2008-10-01T20:39:00.002-07:00

For those not familiar with my deployment tool, here is how it works.

Basically, you set a folder on your hard drive to be the "deploy" folder.

Inside this folder, you put folders, NDS files, ZIPPED NDS files, TXT files, untrimmed files - whatever you want deployed to your microSD.

The nice thing is - you do this with your favorite file manager - you don't even have to have CycloEdit running. You make the deployment structure and contents the way you like it.

Then you pop your microSD in, run CycloEdit pro, go to the deployment tool, select your options, hit DEPLOY.

- All ZIPPED NDS files are extracted.
- All UNTRIMMED NDS files are trimmed.
- ... something secret here ...
- All text files are reformatted for the in-game text reader.
- Clean up occurs (non-DS files like .DIZ, .NFO are removed)
- The entire folder is deployed; all folders are preserved. You don't have to do squat.

Who is this for? This is for the people that do a LOT of maintenance on their card. Moving stuff on daily, for example.

How is this a better system than say, Rominator?

This is a DEPLOYMENT TOOL. YOU control where the files are deployed to. Many people have folders for ACTION, PLATFORMER, PUZZLER etc. genres on your card. If you want to "mass deploy" a dozen files that fall into multiple folders ... most "rom maintenance" tools aren't going to accomodate this special structure.

There are also other limitations to databased offline rom tools that I'm solving as well. That's part of the secret :)

Also, most tools require very rigid contraints on filenames, zip required, etc. What if you want to mix and match? Some ZIPPED files ... some unzipped files ... some untrimmed ... what about Text files? Music files? Your rom manager isn't going to handle this for you.

Letting you fully prep a deployment is the only way to get this flexibility. This is the flexibility *I* need. Sure - many people will NEVER use this. I think, though, once you get used to it - you won't want to do it any other way.

Yes, it's a different paradigm that EVERYONE is used to. But you can't progress by using the same old formula that everyone else does. :)

I can't wait for beta feedback soon!

Closer and closer ....

2008-10-01T20:08:00.002-07:00

Deploying to the card in the DEPLOY CENTER now works! What a pain in my ass. Syntax sucks.

In any event, I have to add the txt file wrapper to the process and clean up some stuff - but I expect a working build later tonight or tomorrow.

We're getting close.

Wow, some serious progress tonight ...

2008-09-30T22:10:00.002-07:00

Despite the fact I had practically NO time to work today, I still managed to get a LOT done.

The Deploy Center is rocking and rolling. All the work I've put in on the side has paid off. It was CAKE to integrate my "secret" code along with my rom trimmer right into CycloEdit Pro.

Trimming is now working along with the unzipping (and the secret code works too). Left? Text file reformatting and actual copying to the microSD card. Oh, and of course, ASSLOADS of unit testing, then a beta goes out.

Once the deploy center goes through beta, and we get a little cleanup work done, it's time for 1.0, and from there, we're ready to move forward with new and requested features.

I'm very excited ... this 1.0 release has taken seemingly forever. I want to put the final strokes on the canvas and move on.

Tonight's progress ...

2008-09-29T22:33:00.002-07:00

I began the primary code for the Deployment Center tonight.

The Deployment Center has 4 parts;

a) Unzipping all roms
b) Trimming Roms
c) Reformatting text files
d) Copying files to the microSD

Tonight, unzipping was done. Seems to work properly. I have my own code done for trimming roms and reformatting the text files, so that shouldn't be too hard to integrate.

Until the deploy center works, there will only be basic bug fix betas.

Another update ....

2008-09-28T17:21:00.002-07:00

Just a small fix to address an issue that creeped in with RUMBLE SETTINGS.

Get it using the updater tab.

V0.86b -> V0.87b
* Somthing was wrong with rumble Settings. This should be repaired.

Small update

2008-09-28T08:54:00.001-07:00

Those of you using SELECTIVE BACKUP vice FULL BACKUP might be experiencing errors. This is because of filename collisions (how many README.TXT files do you have on that microSD anyway?). Today's quick build will stop that by adding a random number to the end of the colliding file.

V0.85b -> V0.86b
* Added code to prevent filename collisions (and hence, crashes) when doing SELECTIVE BACKUPS. This isn't final, but it does the trick.

2008-09-26T22:44:00.001-07:00

For those of you with issues with the updater (it's working fine here - so I dunno what the issue is), you can get the latest build here:

http://www.monroeworld.com/cycloeditpro/update.zip

Unzip, rename, overwrite existing. But I'd appreciate any help with tracking down why your updater isn't working.

New Beta Build!

2008-09-26T17:02:00.001-07:00

Alright, a new beta is out! Just use the updater in your existing copy to get the latest! I've been busy. Here is the changelog ...

V0.8b -> V0.85b
* Fixed a bug where the microSD profiler counters didn't reset making the values accumulate each pass.
* The update center didn't reset after the update finished. Now, it does.
* Skins had a lot of issues. Delete didn't work if the skin was currently displayed. Double clicking RANDOM did crappy stuff. Added some error checking to avoid crashing out of the program.
* The Alternative Save checkbox now works.
* Rumble settings had a minor issue. Fixed.
+ Added threaded calls to file copying - app no longer hangs and offers an indicator during the copy process.
+ Along with the alt save checkbox comes file selectors for SAVE, TEXT and GBA SAVE locations! WHOO HOOO!

Once again STAY OUT OF THE DEPLOYMENT TAB ... nothing works, it's going to cause errors. Just DON'T DO IT. :)

End of night ...

2008-09-21T22:24:00.002-07:00

Okay, got a little more done - found several issues with the XML parsing that was keeping Alt Save Locations from staying checked. Found an issue with Rumble settings too. Interesting.

All I have left to do is replicate the threading across all the file copy operations and we're ready for another beta. Whoo hoo!

Tonight's work so far ...

2008-09-21T18:38:00.002-07:00

Squashing bugs ... Here is what we got so far ...

- Double clicking RANDOM on the skins no longer produces an error.
- Fixed the DELETE SKINS issues reported on the TC forms. This required a lot of little crap. Glad it's over. I've never been a big skins fan, but I had to get it working :)
- MicroSD profiler values reset between uses now.
- Fixed some verbage and messages.

Probably get more done tonight ...

Some work has been done ...

2008-09-20T22:50:00.002-07:00

Thanks to my good buddy Brien King, I have been able to successfully move the file copy operations to a threaded environment. Now, you actually GET UPDATES on what files are being copied, and the damn application doesn't lock up totally until it's done. This should allow me to offer up a CANCEL as well as provide you guys a MUCH richer experience.

So far, this is only working on ONE instance of the file copy routine - several to replace - but that's trivial at this point.

My next step is to insert some notes into my code (thank god for // TODO: ) outlining fixes for the issues already submitted to me via the Team Cyclops forum thread. They are pretty trivial as well.

Once I get those hammered out, and put the threading code into the other file copy routines - I'll release another public beta. At that point, the deployment center becomes my next goal (threaded deployment center) - and there will be another beta after that (at least one). Once we get some feedback, and remediation happens from that beta, I think we're ready for 1.0 and I can start adding some of the cool features I've been working on in stand alone code in my tiny glimpses of free time lately.

Damn, I'm excited now!!

I've been sick ...

2008-09-19T07:57:00.002-07:00

Well, I've been sitting on the edge of death (alright, that's a bit dramatic) the last few days, so I haven't done SQUAT on the code. I'm gonna go hit the doctor today and maybe get a phatty Z-Pak :)

Hopefully I'll be spanking on the code later on this weekend.

Let's try a beta!

2008-09-15T22:17:00.001-07:00

Alright gang ... I feel pretty comfortable with a short public beta on this.

Get the Beta here: http://monroeworld.com/cycloeditpro/cycloeditprov08b.zip

This is NOT a prime time product. I really recommend you wait at least ONE MORE beta build if you are at all squeamish about early betas.

Here is what I KNOW already is wrong:

PLEASE do not play in the Deployment Center. I didn't disable anything or lock it out, and while I don't think anything BAD can happen in there, as Scatman Crothers said in The Shining, "You ain't got no business in there anyway .. so STAY OUT .. you hear?"
If you select a drive from the drive drop down, and it isn't a CycloDS Evolution card (like a hard drive) - it will make a CYCLODS folder on it. Sorry about that. THAT will be fixed next build.
Don't double click RANDOM in the Skin Manager :)
There is no code to trap invalid XML in skin definitions.
Alternative SAVE and TEXT locations do not work as they should. I'd say out of that for now as well.

Otherwise, I think we're ok. I'm not officially set up to handle bug tracking yet. However, you can post stuff at the Team Cyclops forum for now, or reply to this entry here.

Thanks gang!

Side Tracked with features ...

2008-09-15T18:25:00.002-07:00

You ever have this problem? You copy a rom image over to your microSD and you don't rename it ... you just leave it the same goofy name your dumper called it? Like N____NUSA.NDS? Then you realize when you go to clean your card up, you have NO idea what the hell that game was? Sure, you see it right in the menu of your CycloDS Evo, but now you have to start guessing what the game really is?

The feature for CycloEdit Pro I'm drafting up will actually handle this for you soon ... :)

As for the beta, we're getting pretty close to being comfortable with it. I need to verify the application updater works properly, but I believe it does - then you can have the latest builds downloaded directly to you. I really want to be sure at LEAST this works before the beta heads out the door.

Weekend Update

2008-09-14T20:16:00.002-07:00

I'm afraid the weekend beta just isn't going to make it. I had my lead beta tester hit the app and it's in very good shape for a first pass - but I have a couple of loose ends still I must wrap up.

Today's effort DOES, however, give me a decent list of things to work on. Thanks to the tester's diligence, I was able to clean up some serious issues in the microSD Profiler and the backup tool.

The backup tool still locks the application up while it's working; I need to research threading more to get this issue cleaned up. However, I was able to use a delegate to keep the file copying list displaying during the copy -- of course, if you click off the application, it doesn't refresh the way it should. Sigh.

There are issues with custom SAVE and TEXT locations too.

Finally, there are a couple of glaring issues with the Skin Manager that I really want tidied up before the public gets it.

The good news is - there really isn't much horribly wrong - just a lot of little things that the evil anal perfectionist wants done. :)

Something we found during testing ... there are apparently skins out there that have malformed XML descriptor files. Apparently, if they work on the CycloDS, you won't have an issue here. However, I can see people downloading and installing skins through this tool and they will not know what's wrong. It would be nice if whatever tools are being used to make skins would be sure to validate XML or host sites that can check the validity when they are uploaded.

Well, that's enough of an update ... back to work.

When?

2008-09-12T10:54:00.002-07:00

I've been getting a lot of mail and posts asking the eternal question ... WHEN? When will it be ready?

I run a pretty full life and CycloEdit Pro isn't on the top of the priority lists at this time. HOWEVER, it's getting pretty close to a stable beta status and I'm hoping over the weekend to tie up a couple of loose ends and make it ready for a PUBLIC beta release.

If I do release it this weekend, it will be more like an alpha - as all functionality will NOT be present (namely the deployment tool) as I'm actively pursuing different methods and code to do what I want to do. So, I'll likely disable the tab for this release.

Keep an eye out here for the latest and greatest news and info.

The first update

2008-09-11T09:10:00.001-07:00

Time for a little update on progress of CycloEdit Professional.

Tonight I added compatibility for 1.5b3 - namely the batter saver XML option. This led me to realize that MANY new XML changes have occurred between 1.41 (the latest stable release - which I need to support). With XML changes come UI changes and lots of logic to determine what can be shown and when. The new features also lends to several customizable folders I'll need to account for.

Unfortunately, not much of this logic was present in CycloEdit 1.x so it's having to be all written from scratch. Instead of "hacking" this support in, I created a system to handle future upgrades as well as support 1.41 - the latest build (1.5b3).

I also realized while I was kicking around the code that the SAVE XML code hadn't been brought over and implemented with the new codebase. Fortunately, with the foundation I created for handling versions of the firmware, it went pretty quickly, and it appears to work.

All that is left after various bugs and clean up is the DEPLOYMENT CENTER, which still has some work to be done - however, I do believe I can get a beta out without having it done to completetion.

So, that all being said, by the end of the week, I should have an "advanced users" type beta - just to get it out there and have the bug hunting begin.

Welcome to the CycloEdit Professional developer journal

2008-09-11T08:20:00.000-07:00

I've had a lot of people ask for a dev journal for Cycloedit Professional so here it is. This will allow you to follow progress of the application even if Team Cyclops' forum is down (which it appears to be a lot these days). You will also be able to subscribe to this as a feed so you don't have to actually come and visit.