Why not to make the GUI more mighty?
Lol
You know that I didn't mean it that way...
In my opinion, the GUI isn't that high prior, as the Exporters do a great job in most parts.
Though, in interactivity there could surely be some additional stuff...
I guess, Pause and Resume buttons wouldn't be that hard to add or that much of a speed decrease...
A bigger problem might be the interactive tonemapping...
Besides those 2 1/2 and maybe a more intelligent way to put out especially large images (with auto-fit, i.e.), the GUI already is fine as it is.
The last of those 3 1/2 requests is low prior and maybe the most time consuming part...
(1 1/2 = stop and resume... one alone wouldn't make SOO much sense...)
You know that I didn't mean it that way...
In my opinion, the GUI isn't that high prior, as the Exporters do a great job in most parts.
Though, in interactivity there could surely be some additional stuff...
I guess, Pause and Resume buttons wouldn't be that hard to add or that much of a speed decrease...
A bigger problem might be the interactive tonemapping...
Besides those 2 1/2 and maybe a more intelligent way to put out especially large images (with auto-fit, i.e.), the GUI already is fine as it is.
The last of those 3 1/2 requests is low prior and maybe the most time consuming part...
(1 1/2 = stop and resume... one alone wouldn't make SOO much sense...)
Hehe, ... I take an educated guess, that Nik wanna optimize Indigo
and make it "working". This would make the SDK sell and the most
bigger companies would code "in house" software with the SDK
to have full control over the API.
So there would be no need for Nik to code a GUI and to fight against
those ugly GUI bugs and a usable design for it. So of course it would
be better to have someone to implement Indigo into some "other" GUI.
But from what I've read, the most ppl that do like to code, like to have
full access to the API, because it makes life easier. That would imply
to have access to the SDK and the SDK costs money .... *doh*
So in the end ppl will live with what Nik offers us, or will jump
on another train. It always depends on our needs and priorities.
nb: This is just pure guessing from me as an artist. I'm no
coder at all ... but I pay attention. *sfg*
edit: Kram, don't worry ... I was just playing with you too!

take care
psor
and make it "working". This would make the SDK sell and the most
bigger companies would code "in house" software with the SDK
to have full control over the API.
So there would be no need for Nik to code a GUI and to fight against
those ugly GUI bugs and a usable design for it. So of course it would
be better to have someone to implement Indigo into some "other" GUI.
But from what I've read, the most ppl that do like to code, like to have
full access to the API, because it makes life easier. That would imply
to have access to the SDK and the SDK costs money .... *doh*
So in the end ppl will live with what Nik offers us, or will jump
on another train. It always depends on our needs and priorities.
nb: This is just pure guessing from me as an artist. I'm no
coder at all ... but I pay attention. *sfg*
edit: Kram, don't worry ... I was just playing with you too!
take care
psor
Last edited by psor on Thu Jan 24, 2008 8:46 am, edited 1 time in total.
"The sleeper must awaken"
my guess is that Ono wants to make money with commercial licensing and he should. It would be smart for him to stay focused on the development of the 'rendering engine' and let others worry about the user end of it. ( especially since that end of it is dependent on the software it's being incorporated into )
I don't want to speak for him but that's where I would stand on it.
I don't want to speak for him but that's where I would stand on it.
Nope Kram, not bored - but I have to much spare time at my hands
right now and can share some thoughts. *LOOOOL*
I know about what Nik said. Non the less, this will be the last step.
First comes, and this is what I wish him very much, to make money
out of the SDK. If everything goes wrong and there is no success,
then it would be a shame to let Indigo die. So it's like a parents
and child story ... "normal" parents will keep the child alive if
it's healthy enough. And from my POV, Indigo is pretty healthy!
*smile*
take care
psor
right now and can share some thoughts. *LOOOOL*
I know about what Nik said. Non the less, this will be the last step.
First comes, and this is what I wish him very much, to make money
out of the SDK. If everything goes wrong and there is no success,
then it would be a shame to let Indigo die. So it's like a parents
and child story ... "normal" parents will keep the child alive if
it's healthy enough. And from my POV, Indigo is pretty healthy!
*smile*
take care
psor
"The sleeper must awaken"
- Kosmokrator
- Posts: 1141
- Joined: Sat Jul 29, 2006 11:52 am
- Location: Greece-Athens
- Kosmokrator
- Posts: 1141
- Joined: Sat Jul 29, 2006 11:52 am
- Location: Greece-Athens
Hm, features I would like to see is refresh when I want it, pausing the displaying of images, etc. I think all that is needed is a tool that can tell Indigo when to render the image, and then it needs to display the saved PNG. That would also improve performance since I don't have to display an image every 2 minutes. At the moment I have to resume all the time because of this.
And pause and resume are useful too. But I think only with the command line this can't be done without ugly side side effects like restarting the scene all the time.
And pause and resume are useful too. But I think only with the command line this can't be done without ugly side side effects like restarting the scene all the time.
@kadajawi
I guess for a coder this is easy to code in a 3rd party GUI. It would
access Indigo over the console and could load the image Indigo
saves. And offer all the stuff you like. Since I just learned AS 1.0
and PHP in the past this will not help here, especially it's about
four years ago that I touched some code.
*whispers*
Maybe we can convince dougal2 to go for it with Java ... hehe! ;o))
*plonk*
Or I just have to learn Java, ... but I don't think this will happen
anytime soon.

take care
psor
I guess for a coder this is easy to code in a 3rd party GUI. It would
access Indigo over the console and could load the image Indigo
saves. And offer all the stuff you like. Since I just learned AS 1.0
and PHP in the past this will not help here, especially it's about
four years ago that I touched some code.
*whispers*
Maybe we can convince dougal2 to go for it with Java ... hehe! ;o))
*plonk*
Or I just have to learn Java, ... but I don't think this will happen
anytime soon.
take care
psor
"The sleeper must awaken"
@psor
Java is easy
get stuck in
... http://www.netbeans.org/ full IDE and lots of "getting started" tutorials on this site.
@kadajawi
Sound like you should run the console version of indigo and use a separate PNG viewer.
Java is easy
@kadajawi
Sound like you should run the console version of indigo and use a separate PNG viewer.
@dougal2
Thanx mate! Already downloaded NB 6 some time ago, because I
was interested to start a material editor, but somehow I couldn't
get my head around to start with all the coding stuff ... *sigh*
And to be honest, I'm more a "hacker" then a coder. I love to
hack existing code ... never really had the head to write stuff
from scratch. Ya ok, ... during study, but that's some years ago.
Anyway, maybe I can collect some energy to finally do it again. *g*
@Kram
Be my guest!

take care
psor
Thanx mate! Already downloaded NB 6 some time ago, because I
was interested to start a material editor, but somehow I couldn't
get my head around to start with all the coding stuff ... *sigh*
And to be honest, I'm more a "hacker" then a coder. I love to
hack existing code ... never really had the head to write stuff
from scratch. Ya ok, ... during study, but that's some years ago.
Anyway, maybe I can collect some energy to finally do it again. *g*
@Kram
Be my guest!
take care
psor
"The sleeper must awaken"
Who is online
Users browsing this forum: No registered users and 12 guests


psor