Jump to content
Ketarin forum

jeff9315

Members
  • Posts

    7
  • Joined

  • Last visited

jeff9315's Achievements

Newbie

Newbie (1/14)

  1. I don't believe there is any way to get an Environment Variable into Ketarin. I would really like to be able to get access to the Computer Name that I'm on. I'd primarily want it so I can customize the download directory so that it would be something like H:\Ketarin\Downloads\Computer_Name\Category_Name Anybody have any workarounds you can suggest? Ideally, a future version of Ketarin would either allow access to all Environment Variables or there would be a way to create a Ketarin Global Variable through the commandline such as h:\ketarin /PARM="COMPUTERNAME:"Starfish" so that the Ketarin Global variable {COMPUTERNAME} would be "Starfish"
  2. I've had a similar situation in which I wanted to specify which computers an applciation gets installed on. My work-around is to create a per-application variable using the "Textual Content" variable. I then put a space-delimited list of computer names. In my case, I named this variable {JPG-PC}. I then created 2 custom columns ... one for {PC} and one for {Selected-App}. {Selected-App} contains the following regex: {JPG-PC:regex:Starfield} where Starfield is one of the computer names. This then shows all software to be installed on Starfield. The only thing I really need to figure out is how to remove Starfield as being a hard-coded global value buried in a regex so that I can base it on the name of the computer that Ketarin is actually being run from (i.e., %COMPUTERNAME%). Or even specifying it as a separate global variable would be better than what I have now. Hope this helps someone ... Jeff
  3. I wonder if a link to the Changelog could be put on the Wiki. Or maybe just keep the Changelog on the Wiki instead of in the forum. Thanks ... Jeff
  4. Being new to Ketarin, I am just starting to write my own app definitions and would really like to see some consistency to make it easier for everyone to adapt other people's work to their own needs and to develop standard templates. Since it's been almost 3 months since the last post on this topic, I hope that this subject gets resurrected and a consensus gets reached. I agree with CyberTekSol that no one should be forced. I also like andreone's suggestion that Flo develop a dropdown box of suggested variable names (and their definitions) which will "encourage" people to use them. CyberTekSol, FranciscoR, and Shawn all seem to prefer using short names while Stalker prefers long variable names. I can certainly live with anything, but I personally prefer long names. I'm a team lead of a few progerammers and I just checked with 5 programmers and 4 of them prefer longer names (FWIW). I'm too new to know which variables are commonly used (or even what some of the ones listed above are used for). Also, would it make sense to have 2 variables that can be used for each item ... a short name and a long name? That eliminates the likelihood of an infinite number of names without forcing anyone to be "left out" because they disagree on the subject of long vs. short. Anyway, since we've got conflicting viewpoints, does anyone have a suggestion as to how to break the logjam and begin adopting some guidelines for people to use? I'm deliberately saying guidelines not standards since we don't want to force anyone to use them, but we do want to encourage people to use them. Thanks ... Jeff
  5. I think the method that Tomorrow posted would work fine for you. Being a newbie, I had stumbled on a similar approach also. Basically, you would define Z:\Install\Software as a global variable (maybe named dldir} and put this string in the target path: {dldir}\{category}\{appname} v.{version}.{url:ext} and that would be used for all new entries. Everything else Tomorrow said was to just get your already existing apps to have {dldir}\{category}\{appname} v.{version}.{url:ext} in the target path field. Thanks ... Jeff
  6. Hi Shawn. Thanks for replying. I'm not using any other template ... just the "Default". Being a new user, I hadn't even realized that there were other types of templates. No, it is NOT applying it retroactively. What happens is that everytime I EDIT an application, it adds an additional {file} to the "Start Process". Even if I cancel the editing. Here's an example ... I create an application and save it. I then go back in to the same application to edit it and I see that there are 2 {file} commands. I cancel the edit without making any changes and I edit the same one again. There are now 3 {file} commands. I cancel again (or hit OK -- it doesn't seem to matter). I edit it again and there are now 4 {file} commands. I am using the current production version 1.5.0.400. Thanks ... Jeff
  7. FIrst ... I have just found Ketarin and I absolutely love it. It's going to help me ensure that when I upgrade my 3 home computers from Vista to Win 7, I can do a new install and be sure to get all my current software installed (and upgraded to the latest versions). My wife is going to love me for that :-) Now, for the bug ... I've searched through the forums and haven't seen anything related to this. I hope I didn't just miss it. I created a template for new applications (using the "Save As Default" button). This template contains a "Start Process" command -- {file} within the Setup tab. Because the template contains it, whenever I edit an application, {file} gets added to the "Start Process" section, so that my existing entries all contain mutiple {file} commands. When I remove {file} from the template, it no longer adds additional {file} commands in, hence my belief it's related to the template. Thanks ... Jeff
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.