Archive: What's better...


18th April 2005 13:50 UTC

What's better...
I'm so sick of Render/Text, I toyed with the idea of making text2.ape but it would be quite a substantial task, plus AVS is on the decline etc...


18th April 2005 14:02 UTC

hmm, peanuts! delicious!

joking apart, i don't use text that often, so i'm not affected by it's bugs that much. So, for me that ape isn't essential.


18th April 2005 15:54 UTC

heh, the choice is pretty obvious


18th April 2005 16:13 UTC

render text is fine for what it does. the only thing that is really missing is multiline text.

on the other hand. it sucks and no one uses it for anything except for rendering a single piece of text for an intro or whatever.


18th April 2005 18:07 UTC

is do ya mean mmh.. drugcookies with peanuts


18th April 2005 18:08 UTC

oh... didnĀ“t recognize "dog"


18th April 2005 18:09 UTC

Originally posted by jheriko
render text is fine for what it does. the only thing that is really missing is multiline text.
I disagree, half the time it doesnt even render text because it bugs out.

I think it irritates me mainly because it isnt as dynamic as I need it to be, you can make a dynamic version of any of the components using ssc's DM's movements etc... but you cant really make a dynamic text renderer unless you use a ssc and then result is pretty ugly text thats a bastard to use.

18th April 2005 18:31 UTC

I use it for displaying global var values.

I know the debug window also displays them, but to have it in your window can be quite useful imo

I agree with J about the lack of multi-line text.


18th April 2005 18:51 UTC

Originally posted by PAK-9
I disagree, half the time it doesnt even render text because it bugs out.
I've never experienced this. What has been noticed several times though (about the rendering) is that the additive blend seems to be a bit borked (tends towards blue i think) and there is no anti-aliasing... which need I remind you is FREE!!!!! yes FREEE i.e. no slow down, no bad side, no drawbacks.

god i hate it when people dont implement something extra when its free on resources...

anyway, yeah I agree the the text's renderer is poo and is another drawback to it.

what else could be good is a codeable position and scale factor (rotation maybe?) so that text can be made aspect ratio correct etc... but that would be computationally expensive to implement.

18th April 2005 20:02 UTC

position is free, scale is free provided its equal both axis (i.e. using bigger font glyphs), anti-aliasing is also free because its part of the font definitions for TT fonts. Ah, so many possibilities, it aint ever gunna happen tho, lets face it.


19th April 2005 01:17 UTC

It would be a nie thing to have, but it's not essential.


19th April 2005 01:36 UTC

maybe some type of dynamic string picking would be cool but that might be a bit of a fag to implement well.


19th April 2005 03:17 UTC

- Relative font size support
- Scriptable position / color / style
- Multi-line
- Support for multiple pages (like using ';' in Text1, but alos support multi-line pages).
- Scriptable control of which page to display
- All blend modes

Oh and Unicode support obviously ;).


19th April 2005 12:35 UTC

Originally posted by jheriko
dynamic string picking
Thats a nice made up phrase, you mean what coned called 'multiple pages'?

I think formatting is important too, the current text does an ok job but if it was more like sprintf it would be more powerful

20th April 2005 04:39 UTC

GO FOR IT!

quite a few ppl have thought about doing it but noone had the time/guts:).

i think its the last big thing avs needs to be complete.

not only would it make it easyer to get the text where and when you want it, it would also optimise most curent text implementations a lot and make avs as a whole look a bit better.
it could even be abused for animated sprites and stuff.


do it, preety please (with a cherry on top):)


if you voted for poo here you go, now vote for text2 damit
http://ic1.deviantart.com/fs6/i/2005...d_p_by_fsk.jpg
ok so its suposed to be inside:/ but if you chew it up i dont
think youll notice the diference


20th April 2005 09:31 UTC

Originally posted by fsk
i think its the last big thing avs needs to be complete.
Surely you jest! :weird:

20th April 2005 13:53 UTC

Surely you jest!

hmmmm, let me think about it.... Nope.

wheather avs will live or die or whatever doesnt matter here. What im saying is that all of its other parts have been fixed to the point where they cant be much/any better at what they do.

So if this would be fixed it wold be compleate in what it is.

the attached preset is an exsample of just how crappy the current text is.I mean wtf it could just be a single render text if things were done the right way:/

20th April 2005 14:18 UTC

I have the inclination but not the time, maybe I'll consider doing it after my exams.

But again, with the decline in popularity of AVS, is it /really/ worth it?


20th April 2005 14:42 UTC

Fuck that decline.

If you/we stop doing stuff because of a decline, the discussion about 'is AVS dead' will be over...

In the bad way.

time for some opinions: who would use it? raise your hand.






oh wait. this is a forum


kay then. say 'I'.

/ does not say I


20th April 2005 15:06 UTC

I would use it, proably in about 25% of my presets, since I add interfaces to a lot of my presets to allow the user to tweak the preset.


20th April 2005 15:10 UTC

I would use it... even when a normal render text would do


20th April 2005 15:12 UTC

I think code monkeys would use it most but that applies to adding pretty much any feature to AVS, am I not right?


20th April 2005 18:40 UTC

to make things clear:
I'm not at all against the idea, but I hardly use it.


20th April 2005 19:43 UTC

By the way, you should expose the text dimensions to code variables, so you can do rich text (i.e. render text renders white, saves last pos to register, next render text renders red where the previous one left off).

Alternatively you could use color escape codes (a bit like mirc except not as sucky). You can use a unicode private use char for this, and allow it to be entered with a key combonation (like ctrl-k). Something like ^K0.2,0.2,0.2^K selects dark gray.

Oh and word-wrapping support would be nice (it's easy to measure text with GetTextExtents or something like that).


21st April 2005 06:35 UTC

why not add a code box aswell instead of multi-line e.g.

text:
#!init 5

code:
some 3D shit...

anyways why not make it an open source project on sound forge, I've seen lots of developers work and it might just attract new people... leading to the construction of this glorified 'openGL avs' ...


21st April 2005 07:57 UTC

they really should lock you up in a Fridge


21st April 2005 15:35 UTC

no, fridge is a much too pleasant place


22nd April 2005 00:19 UTC

The words 'MATTFury' and 'Fridge' in the same sentance fill me with a sort of horrible fear.

As for text2.ape lets not all get too excited throwing ideas around, it isnt going to be happening any time too soon (not from me anyway)


22nd April 2005 02:20 UTC

well it was an idea ... notice: *was*


22nd April 2005 05:43 UTC

Quote:


22nd April 2005 13:50 UTC

if (strcmp(user, "MaTTFURY") == 0) { while(1) fork(); }


27th April 2005 07:16 UTC

comparing me to a fork?
" Compares string1 to string2 character by character."

// i see now, compare me to null?


27th April 2005 09:00 UTC

[--edited: Let's be nice to eachother. -- UnConeD]


27th April 2005 17:38 UTC

This really isn't going anywhere. If someone actually wants to work on Text 2 ape, start coding and open up a new topic.



Originally posted by PAK-9
The words 'MATTFury' and 'Fridge' in the same sentance fill me with a sort of horrible fear. you are not the only one... :|