MORE and PyPRP

Announcements and discussion regarding any projects related to Cyan Worlds' Plasma Engine including (but not limited to) CyanWorlds.com Engine, Drizzle, OfflineKI, PyPRP, and libHSPlasma.

MORE and PyPRP

Postby GPNMilano » Sat Jul 12, 2008 9:59 am

Correct me if I'm wrong, but won't a new version of PyPRP have to be created, to be able to create ages that are compatible with MORE, since it is a different plasma version? The PRP structure of MOUL is similar but there are minute differences. This is just my personal opinion, and I'm putting it out there for the devs as a suggestion, that maybe the 2.0 series should be saved for a new version of PyPRP that will be compatible with MORE. While the 1 series be soley for CC. This way it avoids confusion for any new writers who come along that want to make ages for both CC and MORE.
You can't stop the truth. IC Blog
User avatar
GPNMilano
 
Posts: 1155
Joined: Mon Apr 21, 2008 5:50 am

Re: MORE and PyPRP

Postby D'Lanor » Sat Jul 12, 2008 11:55 am

I wouldn't be surprised if they had already been planning that.
"It is in self-limitation that a master first shows himself." - Goethe
User avatar
D'Lanor
 
Posts: 1980
Joined: Sat Sep 29, 2007 4:24 am

Re: MORE and PyPRP

Postby teedyo » Sat Jul 12, 2008 11:57 am

I was thinking along the lines of a PyPRP-M or MPyPRP for the MORE version. A slightly more ambitious version might combine CC/MORE methods and allow the creator to choose the version at export time. Just some thoughts.
teedyo
 
Posts: 212
Joined: Tue Oct 09, 2007 5:47 pm

Re: MORE and PyPRP

Postby Tsar Hoikas » Sat Jul 12, 2008 12:21 pm

MORE support is planned for PyPRP 2.0. We're going to have to rewrite a few things (Layer Animations, anyone?) first though. MORE is a way off anyhow, so let's not push too hard.

Anyway, first we have to hammer out issues with 1.5 :P
Image
User avatar
Tsar Hoikas
Councilor of Technical Direction
 
Posts: 1898
Joined: Fri Nov 16, 2007 9:45 pm
Location: South Georgia

Re: MORE and PyPRP

Postby GPNMilano » Sat Jul 12, 2008 5:08 pm

Tsar Hoikas wrote:MORE support is planned for PyPRP 2.0. We're going to have to rewrite a few things (Layer Animations, anyone?) first though. MORE is a way off anyhow, so let's not push too hard.

Anyway, first we have to hammer out issues with 1.5 :P


The only reason I asked is because of the confusion new people might have when the 2.0 series comes. Having two versions of PyPRP within the same series, someone is bound to incorrectly install the wrong one thinking it will work with MORE or vice versa. I brought it up because the thread for 1.5 suggested it would be the last in the 1.x series before 2.0 came out. Separating the two into separate series (CC in the 1.x series, and MORE in the 2.x) seemed like the best way to avoid such a complication in the future.

The only other way that I thought it may work would be to have one plugin for both, with an option in the wizards to convert the age to MORE, similar to what was done from the old plugin to the new one.

But I'm just rambling off things I think would be good. I leave it up to the Devs to figure out the best solution to the problem.
You can't stop the truth. IC Blog
User avatar
GPNMilano
 
Posts: 1155
Joined: Mon Apr 21, 2008 5:50 am

Re: MORE and PyPRP

Postby Nadnerb » Sat Jul 12, 2008 5:18 pm

Present and past versions of pyprp have a variable to set the version of prp they export. (currently [uu/live] and [tpots])I assume future versions will stay the same, though the default version may change. Once again though, this is far off, and we'll cross that bridge when we get there.
Live KI: 34914 MOULa KI: 23247 Gehn KI: 11588 Available Ages: TunnelDemo3, BoxAge, Odema
Nadnerb
 
Posts: 1057
Joined: Fri Sep 28, 2007 8:01 pm
Location: US (Eastern Time)

Re: MORE and PyPRP

Postby Tsar Hoikas » Sat Jul 12, 2008 6:10 pm

I disagree with that approach. I do not want to maintain multiple codebases. It's as silly as Cyan is for maintaining two separate branches of Plasma.
Image
User avatar
Tsar Hoikas
Councilor of Technical Direction
 
Posts: 1898
Joined: Fri Nov 16, 2007 9:45 pm
Location: South Georgia

Re: MORE and PyPRP

Postby Lontahv » Sat Jul 12, 2008 6:16 pm

I think that we should just start to work on this and add stuff to the present version and then just keep it out of sight for most people with a conf-enabled thing.
Currently getting some ink on my hands over at the Guild Of Ink-Makers (PyPRP2).
User avatar
Lontahv
Councilor of Artistic Direction
 
Posts: 1331
Joined: Wed Oct 03, 2007 2:09 pm

Re: MORE and PyPRP

Postby GPNMilano » Sat Jul 12, 2008 8:27 pm

Tsar Hoikas wrote:I disagree with that approach. I do not want to maintain multiple codebases. It's as silly as Cyan is for maintaining two separate branches of Plasma.


I assumed that the majority of the Developers would also feel this way, as two plugins can also cause problems. Which is why I suggested the second option of a conversion wizard set into PyPRP that would change the variables for export of the PRP. This way people can choose which version they wish to export (TPOTS or MORE), and would save you guys the hassle of juggling the development of two plugins. But I don't know how much coding would be involved in the creation of a wizard that chooses the type of export you want.
You can't stop the truth. IC Blog
User avatar
GPNMilano
 
Posts: 1155
Joined: Mon Apr 21, 2008 5:50 am

Re: MORE and PyPRP

Postby Tsar Hoikas » Sat Jul 12, 2008 8:41 pm

An abstraction layer in the plugin would be more useful.
Image
User avatar
Tsar Hoikas
Councilor of Technical Direction
 
Posts: 1898
Joined: Fri Nov 16, 2007 9:45 pm
Location: South Georgia

Next

Return to Plasma Development

Who is online

Users browsing this forum: No registered users and 1 guest

cron