Blogs

As I mentioned in my last blog post I am working on a new progress box for Toucan, so after getting Pre-release 2 out of the door earlier I have done some work on it.

The progress box is probably the part of Toucan I like the least as it currently just outputs text which can be hard to look through when you have copied a lot of files. So for the redesign one of the major priorities is to made it easier to use and to find errors.

Realize that this thing is only half coded. And the logic flow will likely change.
The idea is that a general launcher could be made, and then a config ini used to setup the application.

Configuration INI (Store in AppNamePortable\Data\):

#IF YOU DON"T USE A VARIABLE LEAVE IT AS FALSE!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Application]
ExeName=
ExecutableDirectory=
CheckRunning=True 
#Normally, you should leave "CheckRunning" set to true

[Settings]
HKCU=
HKLM=
Config_File=
Manipulate_Set_Out_Path=
#Utilize "True" or "False" for each settings storage place.
[RegistryBranch]

Yes, I know it is more than six months since I last posted, but I thought I would (once again) try to keep you all more informed with what is going on with Toucan, so here it goes

So clearly 2.0 has been released since my last post, along with 2.0.1. 2.0.2 Pre-release 1 is now in testing in the beta forum, you can grab it here. This should fix the majority of the bugs in the 2..0 platform.

K, I haven't actually written this yet, but what do you think of a generic launcher configured via a INI?

It would need to handle:
HKCU and HKLM (HKLM would require a check for admin, but that's easy)
PATH addition (again, only if needed)
%APPDATA% redirect
Command Line Switches

I'm not worried about a splash, if I did have a splash, it'd be something similar to PortaLuanch.

Any ideas?

Let's talk about the code SetOutPath.

Applications act funny. Some of them understand where they are and where to look, regardless of their location. some of them however, get confused. And some of them act really funny.

Now, this blog entry was brought about by this this post. Now, I'm not making this entry to insult the original poster, just bring about some better explanations.

SkipSplashScreen:
		;=== Check for data files
		IfFileExists "$PROGRAMDIRECTORY\config.conf" GetPassedParameters ;=== settings already in program directory
		IfFileExists "$SETTINGSDIRECTORY\config.conf" MoveSettings ;=== settings found in data directory
		
		;=== Copy the default settings files
		StrCmp $DEFAULTLOCATION "true" "" GetPassedParameters ;=== if not default location, user is on their own
		CreateDirectory "$SETTINGSDIRECTORY"
		CopyFiles /SILENT "$EXEDIR\App\DefaultData\settings\*.*" "$SETTINGSDIRECTORY\"

Okay, I don't really want to post this in the forums, but I figure I cn blog it here.

I am currently working on ATPad; VTi; Generator; and xVideoServiceThief

Actually, xVideoServiceTheif is done, I just haven't posted it yet. I talked to John about it, and he wasn't to enthused about the name. Also, its stuck in ALPHA. It works greet and all, but I think John would like for it to go into beta. Anyway, if you wants it, you can add a comment to the blog saying so, or just saying that the blog sucks, either way-it'd be nice to know someone's reading.

John gave me the developer permissions, so, now I has a blog.
So what do I write?
I doubt he'd appreciate me posting a rousing round of lora ipsum so . . .
Well, the first post on the blog has been blown.

I know! I'll post code examples here.

Cheerio!

After holding off on them for a while, I've finally decided to have a go at portablizing aTunes as well as Columba.

With 2.0 Alpha 1 now out I thought I would give out a rough timeline of future developments, in chronological order

Today/tomorrow: Spanish translation poll
In the next week: Assuming the poll comes up with an answer the next week should see the release of 1.2.2, which should be the last release in the 1.x series.
Two-three weeks: Alpha 2 released, this may come earlier, depending on when I get free time!