Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal
rsutton

Making an extended OSI include.

Recommended Posts

Was wondering if UB and our crew could put together an extended OSI function include which could be downlaoded and updated like OSI is.

 

Not sure how to go about getting this in as an extended include. Maybe Wanted could you put it in the extended function folder as a .scar or something if we give you a list. We have MANY new functions.. inventory,Banking, camera, actions just basically writing of OSI. I mean its great that your in charge of OSI yourself, but comon let us help and get it even more powerful and great for people. We are already adding them in our scripts. so instead of people jsut leaching it off when they see it. Might as well claim our credit where its due before someone sees our stuff and just basically copies it with a minor tweak and says they did it lol.

 

Just wanting to help the community and putting credits from UB where its due. I really think there should be some OSI extended that should be community functions brought together. Not juust 1 person in charge of the only include we are given to use. Just a suggestion that there should be a team of function writers who can do a global include to work beside OSI, not on top of but beside it.

Share this post


Link to post
Share on other sites

Honestly if you have something viable to contribute to OSI you can post about it for feedback, and if appropriate it is considered, modified, and integrated the correct way usually in a timely manner depending on it's importance and priority. Unfortunately I'm one of the few people here right now capable of making the right decisions when it comes to the direction of OSI and how things need to be integrated. Is this my fault? No. At some point other people will reach this threshold, or those who were apart of my original team will start coming out of the wood works once again and contributing once again. I've been working on the current incarnation of OSI for 6 months, and the concept and structure for nearly 2 years. I'm not just going to let the whole thing go to hell just to speed up how much stuff is in OSI.

 

You all may or may not realize this, but we are competing with another community that on a fundamental level uses all the same methods we do. Meaning if we don't surpass them in quality, then we are nothing. OSI was founded on this very principle.

 

If you can't make reasonable requests or start topics and post code suggesting what you want and it's not worth the quality to you then all you have to do is make another external library you include separately from OSI that is compatible and update and create it yourself for use in your scripts or whoever wants to use it. I'm not some SRL commy dictator, OSI doesn't need to be some supreme law of this land here. You are welcome to work on whatever projects you want here, just try and reside within the moral constructs of a decent person to the best of your ability is all I ask.

Share this post


Link to post
Share on other sites

@rsutton: You can always build a separate include that uses OSI and request an entry in the include system, you'd be able to update it yourself to keep up with OSI and you'd just have to tell your users to download both includes with the includes manager.

Share this post


Link to post
Share on other sites

How do I request entry and all that fun stuff. I wanna get this started asap. Like an auto update system like OSI has on the file menu include manager.

Edited by rsutton

Share this post


Link to post
Share on other sites

First you need to place an XML on your server, the system uses that to determine where to get the files. It currently supports downloading a single .scar file, a .zip file or directly from a subversion repository, which is what I'd recommend. You can use this old one from the SRL Dev repository as a template, it's got every field documented: http://rs-hacking.com/srldev.xml

The iversion field is only required if you don't use subversion, the version field is the version displayed in the includes manager. If you don't use subversion, you need to use the iversion field to indicate when a new update is available, it's best then to start it off at 1 for the first version, then whenever a new version is available, increase that number. You can get free subversion repositories at several places, like http://unfuddle.com/, http://www.assembla.com/, http://code.google.com/intl/nl/projecthosting/.

Some fields in the file like the support email address are currently not used, but I'd advice to fill them out anyway as they may be used in the future. On a sidenote, the "plugins" section can be removed, this is no longer relevant. "target" has to contain the folder where the include is placed, so that'll be ...\SCAR Divi\Includes\[Your Folder]\. Once you've filled that out and placed the file on your server, send me a PM with the location of the file, you'll be able to change that later on yourself, but I still have to port the front-end panel from freddy1990.com, also include an email address if you want to use the logs features which you can configure at the bottom of the file, basically it will notify you of errors during the includes update process, or if you want more details, it can mail you all the details on the include update process. You only get these mails if your include has been changed and is updated in the system obviously. This takes 15 minutes at most before the change is noticed by my server.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×