Is it time for a new PyPRP release?

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.

Re: Is it time for a new PyPRP release?

Postby Jojon » Fri Mar 13, 2009 3:22 pm

Christian Walther wrote:That's an interesting perspective, but it doesn't quite match my impression. Have you followed the development activity in SVN? Or even just the recent clashes between boblishman and GPNMilano? SVN activity is certainly not overwhelming, and obviously declining, but I do still see steady activity, well above the level of some of my own projects that I don't consider abandoned at all. And, more importantly, I see accumulation of work.


I came across the Bob/Chloe flood after it had taken place and it was quite a shock to me, I must say -- glad misunderstandings got more or less straightened out in the end. (I'll make another note around this at the end of this post)

Now, any coding (and I use the word in its lightest possible sense) that I myself has ever done, has been the equivalent of a huge mess of 'let's-see-what-this-does' post-it notes, tacked on top of and around eachother. From the wording I see used (on the forum, I have read no SVN comments), some developers seem to regard experimental parts of their contribs as pretty much that sort of thing and that they'd like to get any conclusions they may have derived from it properly reimplemented, within an overarching coordinated framework, before seeing it fit for public release. One might argue that 'then why do they bother with uploading them at all?' or that 'in that case someone should take the reins and clearly define that framework if it that is not already done', but this is the point at which I prefer to make the assumption that people do stuff for good reason, rather than any other guess. The guess I made is that while devs knows where they want to go, details of the framework is up in the air, until we get a glimpse of Cyan's material.


Christian Walther wrote:My third question that you're referring to was not meant as "Does anyone have any plans for PyPRP, or is it completely abandoned?", but rather as "Does anyone have any plans for coordinated public releases, or is everyone just working away on it according to their own agenda?"


Ok, I took it as "what is the planned direction for pyprp development?", but upon rereading, I notice the word "releases" at the end. As I said, my guess has been that the work we see done, has been for research purposes, more than implementation.


Christian Walther wrote:The (subjective and so far unfounded) impression I get is that a lot of cool things are being done, or have been done, but nobody uses them, because they're only being driven to the point of being useful to an intrepid few. While I can completely relate to that with my programmer hat on, it does seem a bit of a shame from the point of view of the users. I suspect that there could be a lot of people who think that if anything was wasted effort, it was developing all that in the first place, when a comparatively small bit of additional effort could bring it to a much greater audience. But I can't really judge that, since as a programmer myself (and probably even one with a rather extreme tendence in that direction) I know full well that programming, like any creative activity, is an end in itself and does not require any intention of making anything useful to outsiders.

The way I see it, throwing stuff away is what we're doing if we never shape the current PyPRP trunk into a release. Is the prospect of a new, libPlasma-based PyPRP really reason enough to leave everything we currently have behind in an almost-finished state? I admit I haven't bothered to check, but what I've passively heard so far has seemed a bit vaporware to me. Is there any actual development on it going on?


Don't get me wrong -- as a user, I would love to get a new reliable release and a fireworks display where there is nobody to see it, is indeed a bit of a waste -- I'm just trying to draw conclusions from limited information here, preferrably without conjuring conspiracy theories. :7


Christian Walther wrote:I wonder if more people think like you, Jojon. That would certainly explain the somewhat unimpressive response to this initiative.


It would certainly be good to see some more responses from those actually concerned. C'mon guys, let's have it all out here in one big group therapy session. ;)


I wrote that I'd say something about recent clashes on the forum. This is not about the case mentioned specifically, but just a little comment on such things in general. I have hung around this place since its early days and have from time to time noticed how admireably active people have suddenly stopped posting. A few times this has been preceeded by a tense exchange of words or two. I have at these times never discerned any apparent reason for such tension and can only guess that it has grown either out of general uncertainty (which has had even stalvarts like boblishman and Andy throwing their hands up in despair at different points), or something said in private. What I'm saying is that we have thoughout the existance of this place seemed to steadily lose good people. Does anybody have a decent perception of why this is, because I seem to be missing it. Other than becoming more transparent, what can we possibly do to stop this drift, if it's not just something I'm imagining?
Jojon
 
Posts: 1116
Joined: Sun Sep 30, 2007 5:49 am

Re: Is it time for a new PyPRP release?

Postby Grogyan » Fri Mar 13, 2009 4:22 pm

We are now at the stage where we were suppose to be 2 years ago, and we're still waiting on Cyan to fulfill its promises.

There is very likely to be a surge of activity again when servers are created, and players devoted to the game want more, in particular, features that are are deep within the SVN or havn't yet been done in a single tool (Blender), it is essential that we have a powerful tool set, with which to make Ages, and its no good for us that aren't in the know of merging branches by ourselves.

The other thing is LibPlasma, which I have no idea how it is going to work with Blender, or even if our current projects will be compatible with it.

I'm going out on a limb to say that i'm not going to be here for much longer, my life is moving, and I have strong interests in other games, more notably, how much easier they are to mod with.
Plasma is hideously designed, and has some powerful features, but more importantly, its so ancient and difficult to work with that even Second Life is a far better prospective to build a new Uru on.


What i'm saying is Christian, with hopefully your expertise and collaboration with the other plugin devs, we can get the game back on track and prepared for when the multiplayer environment code is released, we can all have fruitful future.
Better to have loved and lost than never to have loved at all
User avatar
Grogyan
 
Posts: 1203
Joined: Thu Oct 11, 2007 1:27 am

Re: Is it time for a new PyPRP release?

Postby Lontahv » Fri Mar 13, 2009 11:57 pm

Since the starting of the GoW site the PyPRP devs have been working very hard. The plugin has been rewritten and its capabilities have gone from rather simple and crude to very highly advanced.

When I started coding for the PyPRP project, there were many needs. You'd be making an age and find your tool-box was lacking something you needed to finish the job. Then, releasing new versions was much more than just fixing a few minor bugs, fiddling certain settings, adding a few niche features. It was about adding stuff that was the difference between your age looking like something 3d from the early 90's and and something comparable to Cyan's work.

For me to use I feel like for now it's done. I have the tools I need (PyPRP is advanced enough to export a decent age and libPlasma is great for if you want "that little rare feature" for your age).

Sure, PyPRP has room for improvement and PyPRP2 needs much more work. There's just not the urgency of before. Now, there's a way to do almost everything (either with PyPRP or libPlasma) without having to count bytes. All you need to battle now are the UI's for various tools. ;) IMO, in most cases, even this is a lot easier than hex editing Plasma-objects (however complex the interface may prove :P ).

Grogyan wrote:The other thing is LibPlasma, which I have no idea how it is going to work with Blender, or even if our current projects will be compatible with it.


The PyPRP2 plugin (for Blender) that is under development is taking advantage of libPlasma though its Python bindings.

Grogyan wrote:Plasma is hideously designed, and has some powerful features, but more importantly, its so ancient and difficult to work with that even Second Life is a far better prospective to build a new Uru on.


Some would argue that they've already built a new Uru in some large commercial MMO's. :P

Grogyan wrote:What i'm saying is Christian, with hopefully your expertise and collaboration with the other plugin devs, we can get the game back on track and prepared for when the multiplayer environment code is released, we can all have fruitful future.


I don't think the PyPRP development team is currently broken. I think expecting to have a full-function easy to use version of PyPRP that exports stuff for a game that's not even out yet is a little extreme.

The idea of PyPRP2 is to use the switch in PRP versions to reinvent PyPRP as a easy to use, fast and powerful (using Zrax's C++ Plasma library with Python bindings) plugin for Blender. Right now it consists of 5 or so Python modules and a big concept. For the "easy to use" part GUIs will play a large role. Support for GUIs in Blender's API (without having to use BGL) is on its way.

PyPRP has made a huge step. It's moved PRPs from almost exclusively the realm of hackers to the world of persevering Myst and Uru fans. Now, with libPlasma's capabilities letting developers focus on high-level stuff like UserInterface, I believe PyPRP can make another huge step and have its user-base expand from technologically skilled, persevering Myst and Uru fans to all fans who want to make ages. /me scowls at Blender, 3dMax and Maya for being so hard to learn

I think that when the summer comes along, development will be carried out at a faster pace than it is now.
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: Is it time for a new PyPRP release?

Postby Grogyan » Sat Mar 14, 2009 1:51 am

Max and Maya are terrible to me, Blender is like sandpaper on wood, eventually you'll find its smoother than you first though (the sandpaper)
Last edited by Grogyan on Sat Mar 14, 2009 3:58 am, edited 1 time in total.
Better to have loved and lost than never to have loved at all
User avatar
Grogyan
 
Posts: 1203
Joined: Thu Oct 11, 2007 1:27 am

Re: Is it time for a new PyPRP release?

Postby Christian Walther » Sat Mar 14, 2009 3:25 am

Jojon wrote:From the wording I see used (on the forum, I have read no SVN comments), some developers seem to regard experimental parts of their contribs as pretty much that sort of thing and that they'd like to get any conclusions they may have derived from it properly reimplemented, within an overarching coordinated framework, before seeing it fit for public release.

I don't disagree with that, but I have the feeling I'm being misunderstood (as usual when I try to deal with humans :?), or we're deviating from the topic. The project I'm trying to gauge support for is about taking the features and bugfixes that we have in a sufficiently finished state and bringing them out to the people, not about developing new features or finishing unfinished experimental features. It involves little to no coding effort, but a fair amount of documentation effort. (I have to admit that perhaps I mixed the two things up a bit in my previous posts.)

Lontahv wrote:Then, releasing new versions was much more than just fixing a few minor bugs, fiddling certain settings, adding a few niche features.

Do I have to read that, maliciously, as "Today, releasing new versions is just about fixing minor bugs and adding niche features, and therefore isn't worth the effort"? I would agree with the assessment, but not with the conclusion.

Lontahv wrote:For me to use I feel like for now it's done. I have the tools I need (PyPRP is advanced enough to export a decent age and libPlasma is great for if you want "that little rare feature" for your age).

Ah, I can understand that, but I'd hazard a guess that you're talking about the current trunk here, not about the last release (1.5). I think it might be a worthwile endeavour to enable more people to work with the PyPRP that you consider "done".

Lontahv wrote:There's just not the urgency of before.

I don't know. I do feel a certain sense of urgency, for two reasons: To fight against people walking away because they have the impression that development has stalled, and because in a few months, OSMO will be out, we will all be busy with lots of exciting new stuff, and it will never get done.

Lontahv wrote:I think expecting to have a full-function easy to use version of PyPRP that exports stuff for a game that's not even out yet is a little extreme.

As to the topic of Cyan and waiting for the game that's not out yet - my opinion is that what I'm talking about is completely independent of that. It may well be that OSMO is out by the time we finish this, but we shouldn't let ourselves be distracted by that, and concentrate on getting the current PyPRP for CC out before working on OSMO support (or switching to PyPRP 2 / libPlasma if it is decided that putting OSMO support into PyPRP 1 is a waste of time).
Christian Walther
 
Posts: 443
Joined: Sun Jun 08, 2008 3:10 am
Location: Switzerland

Re: Is it time for a new PyPRP release?

Postby D'Lanor » Sat Mar 14, 2009 3:36 am

Lontahv wrote:For me to use I feel like for now it's done. I have the tools I need (PyPRP is advanced enough to export a decent age and libPlasma is great for if you want "that little rare feature" for your age).

Sure, PyPRP has room for improvement and PyPRP2 needs much more work. There's just not the urgency of before. Now, there's a way to do almost everything (either with PyPRP or libPlasma) without having to count bytes. All you need to battle now are the UI's for various tools. ;) IMO, in most cases, even this is a lot easier than hex editing Plasma-objects (however complex the interface may prove :P ).

That accurately sums up the current stalemate. For you as a developer there is no urgency anymore but most writers have absolutely no use for libPlasma. And they too would like to be able to use new features. And rare features? I don't know. Particles for example are IMO essential.
Keep in mind that libPlasma only makes sense to those who have a basic knowledge of the Plasma engine. Many people are at a stage where they just about manage to copy/paste/change names in Alcscript without understanding the logic of it in terms of Plasma.
"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: Is it time for a new PyPRP release?

Postby Jojon » Sat Mar 14, 2009 3:53 am

It may be worth noting, that only a short while before the creation of this thread, Trylon himself did a little shoutout to the other devs, regarding an updated release. To me, inclusion of CW's bit that applies modifiers upon export, alone, would make it worth it.

Documentation is the grisliest bit, I think, though. It can be hard for people in the know, to fully empathise with those not yet initiated, especially when there may be need for prerequisite specialist skills, where the experts will often go "Huh, doesn't EVERYONE know that?!". :7


@CW:

Yes, we went slightly off tangent there, but only for strictly topic-bound analytical reasons. :9
Jojon
 
Posts: 1116
Joined: Sun Sep 30, 2007 5:49 am

Re: Is it time for a new PyPRP release?

Postby boblishman » Sat Mar 14, 2009 6:22 am

D'Lanor wrote:Keep in mind that libPlasma only makes sense to those who have a basic knowledge of the Plasma engine. Many people are at a stage where they just about manage to copy/paste/change names in Alcscript without understanding the logic of it in terms of Plasma.


it is SO nice to hear someone else say this ... this is exactly what my "run-ins" with Chloe have been about.

(Oh, and Chloe ... Andy's tutorial about changing waveset parameters in libPlasma is of no use to me when I want to be able to use libPlasma. This is NOT a criricism of Andy's tutorial, but, having looked at LibPlasma - and actually done the tutuorial - I still have NO idea how to impliment GUIs ... :? , mostly because there is zero documentaion anywhere ... *hint hint*)

I also would describe particles and (of course) GUI's as the main two final "essential" items that are "missing" from the current plugin ... (and it's why I get so frustrated when I see that some Dev's have them working (and even have Ages released with working examples) ... but there is no way that "ordinary" writers can use these features ... )
when it comes to Age creation ... "DOH" seems to be my middle name...
User avatar
boblishman
 
Posts: 882
Joined: Fri Oct 05, 2007 4:47 pm
Location: Spain

Re: Is it time for a new PyPRP release?

Postby Marcello » Sat Mar 14, 2009 10:23 am

In my opinion there is urgency. If the open source UrU has any chance of growing, then we need as much people as possible writing ages and let their imagination flow. Whether they already could do this by using the current tool is not what this discussion is about. What we want them to do (I imagine) is doing all their writing as fast and easy as possible. Simple said we need GUI's and tutorials that don't have you dig into Plasma.

I find it amazing what has been done by the dev's sofar and yes most features are available one way or the other. All their work will be obsolete though if future writers (and I hope the future is not far away) won't use the plugin because of the lack of GUI, tutorials for advanced features and it's usability in general. I find this very likely.

Again... I love the plugin and everything it does, but it's far from finished from a usability perspective. Which I find is a problem if we want UrU to grow.
User avatar
Marcello
 
Posts: 374
Joined: Sun Nov 04, 2007 8:59 am
Location: Haarlem, The Netherlands

Re: Is it time for a new PyPRP release?

Postby Tsar Hoikas » Sat Mar 14, 2009 12:43 pm

Okay, sorry for not posting in this topic sooner. It's practically been screaming my name, begging for attention... Almost like a child who found a toy he likes in Wal*Mart. I've had a very busy stint at school, but that should be over for the most part now.

Historically, PyPRP releases were just thrown together when the developers said "Okay, we have a good number of features. Let's release it." That was a time when the development was taking place in the trunk. Now, from what little I know, we have several different branches of PyPRP going on in contribs. I know that Nadnerb was merging some of the contribs; I don't know if he is still doing this. GPN just recently PMed me about merging some of her contrib stuff to the trunk and releasing a new version. I was (and still am) very much supportive of this.

CW, if you seriously do want to take on the responsibility of preparing releases, I suggest you talk to Nadnerb and Paradox. The best way to hammer that out would be over IRC (irc.justirc.net port 6667, channel #PyPRP) as they're really the developers at this point. I'm just the guy with the title around here. I'm willing to help you make releases. I'm working on revamping some of the stuff on the GoW Site, so this is a great time for this.

Sorry if my post is inadequate. Boogers are crowding my brain :(
Image
Tsar Hoikas
Councilor of Technical Direction
 
Posts: 2180
Joined: Fri Nov 16, 2007 9:45 pm
Location: South Georgia

PreviousNext

Return to Plasma Development

Who is online

Users browsing this forum: Google [Bot] and 16 guests