Author Topic: We need a new installer or we're in trouble.  (Read 15754 times)

0 Members and 1 Guest are viewing this topic.

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: We need a new installer or we're in trouble.
YAML is as bloated as XML.
And has some very ambiguous definitions of how it handles certain types of values, too. About the only thing YAML has going for it is that it's a lot easier for a human to read/edit than just about anything else, but that's it.

...So yeah, if you're comparing to XML, YAML, and INI files, JSON all the way.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline m!m

  • 211
Re: We need a new installer or we're in trouble.
I created a Java library which migrates the current installer data format to a proposed JSON format: https://github.com/asarium/fsoi2json
Here is the output when I run it with the current installer data: http://pastebin.com/7i71r8Kg
It already includes preliminary dependency tracking but we will have to improve that with proper version detection.

 
Re: We need a new installer or we're in trouble.
 :pimp:
I might be able to help you guys with this. I package applications as my regular job and work almost exclusively in AdminStudio/Installshield. I can build complex MSI packages to order and would be willing to make a nice professional install sequence for you if MSI format works for your needs?

Let me know/

 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: We need a new installer or we're in trouble.
I think the issue is that it needs to be an online installer, because so many of the individual components are updated so constantly.

  

Offline Goober5000

  • HLP Loremaster
  • Moderator
  • 214
    • Goober5000 Productions
Re: We need a new installer or we're in trouble.
I'm just going to close this, because there's no use having half a dozen people all duplicating each others' efforts.  Especially not when, as I said, the FSO Installer is nearly ready to go.

My intended date for release is January 19th and I'm going to stick to that.  We can also revisit Hellzed's and m!m's ideas for an online portal at that time.

And if it turns out I can't make that deadline for whatever reason, I'll reopen this thread.