Blogs

Hookay, I've created binaries for you guys. Course, only certain people are going to read the blog So only a few are going to know.

Alright, I've tested most of the stuff. Registry is checked and config is checked. Now, I'll let you decimate what's left.

A long long time ago, in a galaxy far far away . . .
Okay, so you are asking yourself, "Just what the chicken finger is IntelliLaunch? Why the seashore do I care about it?"

IntelliLaunch was a couple of things. A challenge to myself to see if I could actually pull of something this complex.
Most importantly IntelliLaunch is a end-user program portabilzer. It is a no-compile, INI configured, PAM compatible shell(?) program.

By configuring the INI properly, you can portablize almost any program.

About PNotes and ATPad.
PNotes
The new development test is going to take a bit while I rework the launcher structure. I'm adding in the language support that was broken in 4.0 and then I am working on the new ini file structure. I've also fixed the misspelling. If you really want to test it via the PAF structure, you can just drop in the new PNotes 4.5 binaries. Old notes/settings will be okay.

I do plan on making a dev test available for the Release candidates. However, I can't guarantee that I'm going to make dev tests for the test releases.

Ok long story short I somehow screwed up the html encoding of my apps home page at http://portableapps.com/apps/music_video/dvdstyler_portable that was really my fault (thanks John for fixing it)

True story is the fact I need to take a refreshers course on html and possibly on Drupal functions XD as it was not the html but a drupal encoding function I accidently switched on (without knowing it too)

Anyways hopefully soon DVDStyler Portable will be fully released sometime today or the next.

Okay, I finished coding IntelliLaunch.

So, here's the deal- I'm posting this in code form for right now. You should use the standard portableapps format, in the following setup:

*App
---*AppName
---*AppInfo
------appinfo.ico
------appinfo.ini
*Data
---configuration.ini
---*Registry
---*SetOutPathDirectory
---*AppData
---*Config
*Source
---*Other
------Intelliluanch.nsi
------StrRep.nsh
------ReplaceinFile.nsh
------GetParameters.nsh
------IntellLaunch.jpg

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.

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\"