You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(262) |
Jun
(381) |
Jul
(314) |
Aug
(277) |
Sep
(201) |
Oct
(156) |
Nov
(35) |
Dec
(23) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(21) |
Feb
(63) |
Mar
(30) |
Apr
(48) |
May
(59) |
Jun
(15) |
Jul
(10) |
Aug
(4) |
Sep
(16) |
Oct
|
Nov
|
Dec
(1) |
| 2005 |
Jan
|
Feb
(10) |
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
| 2007 |
Jan
|
Feb
(3) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2016 |
Jan
(2) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
|
From: Vargas, I. S. - I. <inf...@ya...> - 2009-04-23 18:18:26
|
Gentlemen *** English translate *** when running. /configure says: configure: WARNING: *** Unable to find the SDL_rtf development files! You can get them from: http://www.libsdl.org/projects/SDL_rtf Disabling aedStaticRTF in the meantime.. However, it was installed in /usr/local/include/SDL/SDL_rtf.h running ./make the following error: In file included from tinyxml/tinystr.cpp:26: tinyxml/tinyxml.h:993: error: extra qualification 'TiXmlDeclaration::' on member 'TiXmlDeclaration' make[2]: *** [tinystr.lo] Error 1 please help me to correct mistakes. Greetings Manuel. |
|
From: Rodrigo H. <rod...@ra...> - 2008-11-01 18:34:46
|
<html> <body> <blockquote type=cite class=cite cite><br> I think everyone on the list should make up their mind and vote (including<br> the people who aren't aedGUI developers). So, guys, what do you say?</blockquote><br> SDL to me is a proven library that provides a lot of the functionality we need, I dont mind being tied to SDL, I personally think that making things simpler for the user should not mean making things more complicated for developers (meaning avoiding SDL as much as posible), and in keeping with reinventing the wheel, I dont see why not make use of other libraries such as SDL_image and others, perhaps SDL_draw or SDL_gfx for primitives, the idea of GNU</body> </html> |
|
From: Rodrigo H. <rod...@ra...> - 2008-11-01 18:34:19
|
|
From: odgerkr9 <odg...@ho...> - 2007-04-14 09:58:04
|
Hillo0 cb4 |
|
From: Sue S. <eo...@ha...> - 2007-02-12 19:40:11
|
Hi, Economize 50% on Vaiagra Vaulium Ciualis http://www.tetrx-com Replace "-" with "." in the above link. sister were like potato-filled sacks dragging him back down... He fixed his eyes skyward, though he knew he must still be very deep, the water above him was so dark,... |
|
From: Everild L. <cr...@ca...> - 2007-02-01 16:37:38
|
Hi, Purchase your medication from our site because it costs less. http://www.vodrx*.com - Remove "*" to make the link working! -- A connection I could have made without assistance, Dumbledore sighed, but never mind. He peered over the top of his half-moon spectacles at Harry, who was gaping at Snapes face, which was continuing to swirl |
|
From: Praxiteles C. <del...@la...> - 2006-11-26 15:51:06
|
Hi, V t a g r a from $ 3 , 30 http://www.keruijinfunhadesunjasderuin.com =20 _____ =20 saved? |
|
From: Marica R. <jun...@da...> - 2006-11-22 17:05:04
|
Hi, V t a g r a from $ 3 , 30 http://www.fedrunjinbeirundaspo.com =20 _____ =20 That will do fine. |
|
From: alexander <bog...@xp...> - 2006-11-20 13:40:49
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2900.2963" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <div align="left"> <p><font face=Arial = >AE86 owners are at a disadvantage, because the solid rear-axel setup limits any rear toe or OK, enough, you're in Orlando not Vatican City</font><BR><IMG alt="" hspace=0 src="cid:CFAEXCM4HBGRLXHYPL9Z" align=baseline border=0><BR><font face=Arial = >Remember, an inertial dyno operates under controlled conditions and isn't subject to road The acceleration software utilizes the engine speed and vehicle speed signals from the OBD-II port to chart your zero to 60 mph, and eighth- and quarter-mile runsI don't watch that show too often</font><BR><BR><font face=Arial = >Using solid pillow-ball joints creates a more predictable setup as far as the movement of the car, but has potential for a rougher ride," said PfeifferHonda's i-VTEC continues to maintain an industry presenceThe AE86's factory design makes it difficult to stabilize and reinforce the shock towers and rear</font><BR><BR><font face=Arial = >What a great opportunity to get some dollars tucked in your shirt!I think I have a high metabolism, but Food Network doesn't help.</font><BR><BR><font face=Arial = >The Integra was well received, sending a message up the ladder to Honda Corporate that the You can check my Web site for updates</font><BR><BR><font face=Arial = >Eager to see what we could gain by uncorking the exhaust, we bolted on the first aftermarket</font><BR><BR><font face=Arial = >Because the core is 20mm thicker than stock, its capacity is bumped up to 3.1 liters</font></p> </div> </BODY></HTML> |
|
From: disk <ast...@xx...> - 2006-11-15 11:44:23
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2900.2963" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <div align="left"> <p><font face=Arial = >My brother has a shaved head and stands about 6 feet 2 inches and is over 200 poundsI like average, everyday, real guys</font><BR><IMG alt="" hspace=0 src="cid:XYFQGBDELH3YXCUQ6PQ9" align=baseline border=0><BR><font face=Arial = >Our most consistent figures were 241.4 hp at 6000 rpm and 212.1 lb-ft of torque at 5900 rpmnewer is OBD II and any car 1995 or older is OBD IHere we saw pulls of 239.6 hp and 210.2 lb-ft of torque</font><BR><BR><font face=Arial = >Therefore, dynos taken at the beach and the mountains cannot be compared without applying a More exhaust backpressure generally means less horsepower, and a stock catalytic converter is </font><BR><font face=Arial = >You could just say you are prepared for the next tripI like it because of the artistic valueVTEC innovations are evolving and constantly leaving their mark in the automotive world.</font><BR><font face=Arial = >Hell, if you are only looking for those kinds of gains, just loose 10 pounds -that alone will make The 5hp gained from losing the factory cat for the metallic one is substantialWhat is the best part of your body; the part that needs the most improvement, and your home phone number?</font><BR><font face=Arial = >I've seen your bikini pictures and your smile wasn't the first thing I noticed</font><BR><font face=Arial = >Some have even taken their love of the sport to a professional level, while others have moved on I want to get more into TV</font></p> </div> </BODY></HTML> |
|
From: Oluwayemisi R. <jac...@cc...> - 2006-11-08 10:40:23
|
Hi, Approved PHxxARMACYhttp://www.bdewunkondefunhase.com =20 right. His voice, sure enough, and his way of thinking. Some guy! |
|
From: Ernesto D. <er...@do...> - 2005-04-01 03:19:16
|
Great to know, this are very good news :-) Take care. Ernesto Eduardo B. Fonseca escribi=F3: > Hi Everyone, > > Just to announce that aedGUI is back! We have some new widgets and=20 > major revisions and bug fixes. I will commit them asap and release=20 > aedGUI 0.2.0. > > Cheers! > > -- > Eduardo B. Fonseca <eb...@ae...> > Account Manager > |
|
From: Eduardo B. F. <eb...@ae...> - 2005-03-30 15:37:28
|
Hi Everyone,
Just to announce that aedGUI is back! We have some new widgets and
major revisions and bug fixes. I will commit them asap and release
aedGUI 0.2.0.
Cheers!
--
Eduardo B. Fonseca <eb...@ae...>
Account Manager
|
|
From: Ivan S. <po...@fl...> - 2005-03-02 20:41:01
|
On Sun, Feb 27, 2005 at 06:04:22PM -0300, Eduardo B. Fonseca wrote: > Hi Rodrigo, > > I think it would be nice if aedGUI had two rendering subsystems: SDL > and SDL_opengl. This would be awesome, since opengl games are in the > rise nowadays. BUT, I think it should continue to support SDL 2D as > well. > I think we should abstract the drawing functions and develop both > subsystems in parallel. Well, Ivan, your worst nightmare is starting to > come baaack ;) <scared> Oh, please don't, please... </scared> :) Seriously, I'm not against opengl stuff, actually I'm glad to see aedGUI's coming back to life again. -- Ivan Stankovic, po...@fl... |
|
From: HERNANDEZ C. R. J. <rod...@ra...> - 2005-03-02 18:53:35
|
I believe there is already some work done by me on the OpenGL Path=2C check that out=2C however you need to create a clear separation between the core drawing engine and the higher level GUI logic=2C otherwise=2C yo= u will face the same frustration I encountered=2E You=27re welcome to take ideas and code from Glitch=2C the drawing and initialization functions in oglinterface=2Ecpp will surelly save you quit= e some time with the OpenGL core=2E = ----- Mensaje Original ----- De=3A potatoes =3Cbwilli03=40coin=2Eorg=3E Fecha=3A Miercoles=2C Marzo 2=2C 2005 4=3A04 am Asunto=3A Re=3A =5BaedGUI=5D project interest =3E So the problem we now face is how could aed support both simple 2d = =3E drawing and openGL while still being practical and useful in both=3F = =3E A = =3E plugin architecture could do this=2C but as Rodrigo mentioned that = =3E could = =3E be very difficult to implement=2E Any ideas=3F I=27ll screw around = =3E with the = =3E source a little and see what i can come up with but I can=27t be = =3E certain=2E =3E Eduardo B=2E Fonseca wrote=3A =3E = =3E =3E Hi potatoes=2C =3E =3E =3E =3E First of all=2C Welcome back! =3E =3E =3E =3E=3E aed is a partially complete=2C full function Gui toolkit t= hat = =3E =3E=3E renders under SDL=2E to me the most practical purpose for aed= is = =3E as an = =3E =3E=3E easy drop-in Gui system for games=2C or other openGL apps=2E = it in = =3E it=27s = =3E =3E=3E current form it is simply just another widget set=2C but becau= se = =3E it = =3E =3E=3E renders in SDL converting it to render to a openGL window = =3E wouldn=27t be = =3E =3E=3E very hard=2E a themeable Gui library capable of providing the= = =3E =3E=3E developer with already complete menu=2C hud=2C and console sys= tems = =3E right = =3E =3E=3E from the start of development would be a very useful tool=2E =3E =3E =3E =3E =3E =3E I agree=2E =3E =3E =3E =3E=3E our current openGL output simply gives a SDL=5Ftexture wit= h = =3E the = =3E =3E=3E window to be used as a texture in the developers own openGL = =3E setup=2C = =3E =3E=3E which is slow and limits lots of openGL functionality=2E thou= gh = =3E aed = =3E =3E=3E uses SDL=27s 2d drawing api=2C which means low level rendering= = =3E functions = =3E =3E=3E would need some rewriting to switch=2E but SDL=27s library is= = =3E similar to = =3E =3E=3E many basic openGL commands=2C so it is very plausible=2E =3E =3E =3E =3E =3E =3E Of course=2C but some of us still develop 2d software=2C so I= = =3E think = =3E =3E this functionality should be =22plugged-in=22=2E I dunno=2C maybe= a = =3E configure = =3E =3E switch=3F =3E =3E =3E =3E=3E we could provide an easy to use and simple to implement = =3E framework = =3E =3E=3E for game makers=2E not something so encompassing as a game = =3E engine = =3E =3E=3E framework but something that will provide=3A =3E =3E=3E =3E =3E=3E * a way to open an openGL window=2E =3E =3E=3E * forms capable of both simple and complex starting menus=2E= =3E =3E=3E * widgets to make a complete hud/in-game Gui=2E =3E =3E=3E * forms loadable from XML =3E =3E=3E * transparent client/server communication (easy with XML b= ased =3E =3E=3E forms) =3E =3E=3E =3E =3E =3E =3E Interesting=2C very interesting=2E =3E =3E =3E =3E=3E the differences between such a toolkit and aed=27s current= = =3E status = =3E =3E=3E really aren=27t very big=2E most game Gui=27s aren=27t very c= omplex=2E = =3E basic = =3E =3E=3E theming abilities and transparency are it=27s only aesthetic = =3E =3E=3E necessities=2C and a few widgets to help graphics programmers = =3E with = =3E =3E=3E commonly needed things(console=2C 3d functionality=2C etc=2E=2E= =2E)=2E = =3E unthemed = =3E =3E=3E aed would retain it=27s current non-flashy toolkit look=2C mak= ing = =3E it = =3E =3E=3E still very capable of normal program UIs=2E =3E =3E=3E how does everyone feel about this=3F does this seem usefu= l=2C = =3E =3E=3E practical=2C interesting=3F i=27d be glad to hear from both p= eople = =3E =3E=3E interested in it and people just reading=2E =3E =3E=3E =3E =3E =3E =3E I think it=27s a good idea=2C but we need to discuss ir furth= er=2E = =3E I = =3E =3E think aedGUI should stay as a multi-purpose gui toolkit (I=27m = =3E using it = =3E =3E this way nowadays) but I really think your idea is plausible and = =3E =3E feasible=2E =3E =3E =3E =3E Cheers! =3E =3E =3E =3E -- = =3E =3E Eduardo B=2E Fonseca =3Cebf=40aedsol=2Ecom =3C=3E=27)=22 =3Emailt= o=3Aebf=40aedsol=2Ecom=3E=3E =3E =3E A=26D Solu=E7=F5es =3E =3E =3E = =3E = =3E ------------------------------------------------------- =3E SF email is sponsored by - The IT Product Guide =3E Read honest =26 candid reviews on hundreds of IT Products from real = =3E users=2EDiscover which products truly live up to the hype=2E Start = =3E reading now=2E =3E http=3A//ads=2Eosdn=2Ecom/=3Fad=5Fide95=26alloc=5Fid=14396=26op=3Fck =3E =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F =3E aedGUI-developers mailing list =3E aedGUI-developers=40lists=2Esourceforge=2Enet =3E https=3A//lists=2Esourceforge=2Enet/lists/listinfo/aedgui-developers =3E |
|
From: potatoes <bwi...@co...> - 2005-03-02 18:16:07
|
So the problem we now face is how could aed support both simple 2d=20 drawing and openGL while still being practical and useful in both? A=20 plugin architecture could do this, but as Rodrigo mentioned that could=20 be very difficult to implement. Any ideas? I'll screw around with the=20 source a little and see what i can come up with but I can't be certain. Eduardo B. Fonseca wrote: > Hi potatoes, > > First of all, Welcome back! > >> aed is a partially complete, full function Gui toolkit that=20 >> renders under SDL. to me the most practical purpose for aed is as an=20 >> easy drop-in Gui system for games, or other openGL apps. it in it's=20 >> current form it is simply just another widget set, but because it=20 >> renders in SDL converting it to render to a openGL window wouldn't be=20 >> very hard. a themeable Gui library capable of providing the=20 >> developer with already complete menu, hud, and console systems right=20 >> from the start of development would be a very useful tool. > > > I agree. > >> our current openGL output simply gives a SDL_texture with the=20 >> window to be used as a texture in the developers own openGL setup,=20 >> which is slow and limits lots of openGL functionality. though aed=20 >> uses SDL's 2d drawing api, which means low level rendering functions=20 >> would need some rewriting to switch. but SDL's library is similar to=20 >> many basic openGL commands, so it is very plausible. > > > Of course, but some of us still develop 2d software, so I think=20 > this functionality should be "plugged-in". I dunno, maybe a configure=20 > switch? > >> we could provide an easy to use and simple to implement framework=20 >> for game makers. not something so encompassing as a game engine=20 >> framework but something that will provide: >> >> * a way to open an openGL window. >> * forms capable of both simple and complex starting menus. >> * widgets to make a complete hud/in-game Gui. >> * forms loadable from XML >> * transparent client/server communication (easy with XML based >> forms) >> > > Interesting, very interesting. > >> the differences between such a toolkit and aed's current status=20 >> really aren't very big. most game Gui's aren't very complex. basic=20 >> theming abilities and transparency are it's only aesthetic=20 >> necessities, and a few widgets to help graphics programmers with=20 >> commonly needed things(console, 3d functionality, etc...). unthemed=20 >> aed would retain it's current non-flashy toolkit look, making it=20 >> still very capable of normal program UIs. >> how does everyone feel about this? does this seem useful,=20 >> practical, interesting? i'd be glad to hear from both people=20 >> interested in it and people just reading. >> > > I think it's a good idea, but we need to discuss ir further. I=20 > think aedGUI should stay as a multi-purpose gui toolkit (I'm using it=20 > this way nowadays) but I really think your idea is plausible and=20 > feasible. > > Cheers! > > --=20 > Eduardo B. Fonseca <eb...@ae... <mailto:eb...@ae...>> > A&D Solu=C3=A7=C3=B5es > |
|
From: Eduardo B. F. <eb...@ae...> - 2005-03-02 14:57:54
|
Hi potatoes,
First of all, Welcome back!
> aed is a partially complete, full function Gui toolkit that
> renders under SDL. to me the most practical purpose for aed is as an
> easy drop-in Gui system for games, or other openGL apps. it in it's
> current form it is simply just another widget set, but because it
> renders in SDL converting it to render to a openGL window wouldn't be
> very hard. a themeable Gui library capable of providing the developer
> with already complete menu, hud, and console systems right from the
> start of development would be a very useful tool.
I agree.
> our current openGL output simply gives a SDL_texture with the
> window to be used as a texture in the developers own openGL setup,
> which is slow and limits lots of openGL functionality. though aed
> uses SDL's 2d drawing api, which means low level rendering functions
> would need some rewriting to switch. but SDL's library is similar to
> many basic openGL commands, so it is very plausible.
Of course, but some of us still develop 2d software, so I think this
functionality should be "plugged-in". I dunno, maybe a configure switch?
> we could provide an easy to use and simple to implement framework
> for game makers. not something so encompassing as a game engine
> framework but something that will provide:
> * a way to open an openGL window.
> * forms capable of both simple and complex starting menus.
> * widgets to make a complete hud/in-game Gui.
> * forms loadable from XML
> * transparent client/server communication (easy with XML based
> forms)
Interesting, very interesting.
> the differences between such a toolkit and aed's current status
> really aren't very big. most game Gui's aren't very complex. basic
> theming abilities and transparency are it's only aesthetic
> necessities, and a few widgets to help graphics programmers with
> commonly needed things(console, 3d functionality, etc...). unthemed
> aed would retain it's current non-flashy toolkit look, making it still
> very capable of normal program UIs.
> how does everyone feel about this? does this seem useful,
> practical, interesting? i'd be glad to hear from both people
> interested in it and people just reading.
>
I think it's a good idea, but we need to discuss ir further. I think
aedGUI should stay as a multi-purpose gui toolkit (I'm using it this way
nowadays) but I really think your idea is plausible and feasible.
Cheers!
--
Eduardo B. Fonseca <eb...@ae...>
A&D Soluções
|
|
From: Eduardo B. F. <eb...@ae...> - 2005-03-02 14:57:50
|
Hi Rodrigo,
I think it would be nice if aedGUI had two rendering subsystems: SDL
and SDL_opengl. This would be awesome, since opengl games are in the
rise nowadays. BUT, I think it should continue to support SDL 2D as
well.
I think we should abstract the drawing functions and develop both
subsystems in parallel. Well, Ivan, your worst nightmare is starting to
come baaack ;)
Cheers!
Eduardo.
On Sun, 2005-02-27 at 14:37 -0600, Rodrigo Hernandez wrote:
> Opps, sorry about that last email, I hit the wrong button :)
>
> I found that modifying the code in order to make it SDL independent to be
> actually harder than to start over as I stated on a previous email
> (http://sourceforge.net/mailarchive/message.php?msg_id=9402064), I still
> feel the same way, so I wont repeat myself, if you want to avoid headaches
> or re writing most of the code,
> it would be better if aedGUI stays SDL only.
>
> At 09:59 PM 26/02/2005, you wrote:
> > aed is a partially complete, full function Gui toolkit that renders
> > under SDL. to me the most practical purpose for aed is as an easy
> > drop-in Gui system for games, or other openGL apps. it in it's current
> > form it is simply just another widget set, but because it renders in SDL
> > converting it to render to a openGL window wouldn't be very hard. a
> > themeable Gui library capable of providing the developer with already
> > complete menu, hud, and console systems right from the start of
> > development would be a very useful tool.
> > our current openGL output simply gives a SDL_texture with the window
> > to be used as a texture in the developers own openGL setup, which is slow
> > and limits lots of openGL functionality. though aed uses SDL's 2d
> > drawing api, which means low level rendering functions would need some
> > rewriting to switch. but SDL's library is similar to many basic openGL
> > commands, so it is very plausible.
> > we could provide an easy to use and simple to implement framework for
> > game makers. not something so encompassing as a game engine framework
> > but something that will provide:
> > * a way to open an openGL window.
> > * forms capable of both simple and complex starting menus.
> > * widgets to make a complete hud/in-game Gui.
> > * forms loadable from XML
> > * transparent client/server communication (easy with XML based forms)
> > the differences between such a toolkit and aed's current status
> > really aren't very big. most game Gui's aren't very complex. basic
> > theming abilities and transparency are it's only aesthetic necessities,
> > and a few widgets to help graphics programmers with commonly needed
> > things(console, 3d functionality, etc...). unthemed aed would retain
> > it's current non-flashy toolkit look, making it still very capable of
> > normal program UIs.
> > how does everyone feel about this? does this seem useful, practical,
> > interesting? i'd be glad to hear from both people interested in it and
> > people just reading.
> >
> >potatoes
>
> Rodrigo Hernandez, lonewolf programmer
> Aeon Games
> http://www.aeongames.com
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> aedGUI-developers mailing list
> aed...@li...
> https://lists.sourceforge.net/lists/listinfo/aedgui-developers
--
Eduardo B. Fonseca <eb...@ae...>
A&D Soluções
|
|
From: Rodrigo H. <rod...@ra...> - 2005-02-27 20:40:59
|
Opps, sorry about that last email, I hit the wrong button :) I found that modifying the code in order to make it SDL independent to be actually harder than to start over as I stated on a previous email (http://sourceforge.net/mailarchive/message.php?msg_id=9402064), I still feel the same way, so I wont repeat myself, if you want to avoid headaches or re writing most of the code, it would be better if aedGUI stays SDL only. At 09:59 PM 26/02/2005, you wrote: > aed is a partially complete, full function Gui toolkit that renders > under SDL. to me the most practical purpose for aed is as an easy > drop-in Gui system for games, or other openGL apps. it in it's current > form it is simply just another widget set, but because it renders in SDL > converting it to render to a openGL window wouldn't be very hard. a > themeable Gui library capable of providing the developer with already > complete menu, hud, and console systems right from the start of > development would be a very useful tool. > our current openGL output simply gives a SDL_texture with the window > to be used as a texture in the developers own openGL setup, which is slow > and limits lots of openGL functionality. though aed uses SDL's 2d > drawing api, which means low level rendering functions would need some > rewriting to switch. but SDL's library is similar to many basic openGL > commands, so it is very plausible. > we could provide an easy to use and simple to implement framework for > game makers. not something so encompassing as a game engine framework > but something that will provide: > * a way to open an openGL window. > * forms capable of both simple and complex starting menus. > * widgets to make a complete hud/in-game Gui. > * forms loadable from XML > * transparent client/server communication (easy with XML based forms) > the differences between such a toolkit and aed's current status > really aren't very big. most game Gui's aren't very complex. basic > theming abilities and transparency are it's only aesthetic necessities, > and a few widgets to help graphics programmers with commonly needed > things(console, 3d functionality, etc...). unthemed aed would retain > it's current non-flashy toolkit look, making it still very capable of > normal program UIs. > how does everyone feel about this? does this seem useful, practical, > interesting? i'd be glad to hear from both people interested in it and > people just reading. > >potatoes Rodrigo Hernandez, lonewolf programmer Aeon Games http://www.aeongames.com |
|
From: Rodrigo H. <rod...@ra...> - 2005-02-27 20:23:29
|
At 09:59 PM 26/02/2005, you wrote: > aed is a partially complete, full function Gui toolkit that renders > under SDL. to me the most practical purpose for aed is as an easy > drop-in Gui system for games, or other openGL apps. it in it's current > form it is simply just another widget set, but because it renders in SDL > converting it to render to a openGL window wouldn't be very hard. a > themeable Gui library capable of providing the developer with already > complete menu, hud, and console systems right from the start of > development would be a very useful tool. > our current openGL output simply gives a SDL_texture with the window > to be used as a texture in the developers own openGL setup, which is slow > and limits lots of openGL functionality. though aed uses SDL's 2d > drawing api, which means low level rendering functions would need some > rewriting to switch. but SDL's library is similar to many basic openGL > commands, so it is very plausible. > we could provide an easy to use and simple to implement framework for > game makers. not something so encompassing as a game engine framework > but something that will provide: > * a way to open an openGL window. > * forms capable of both simple and complex starting menus. > * widgets to make a complete hud/in-game Gui. > * forms loadable from XML > * transparent client/server communication (easy with XML based forms) > the differences between such a toolkit and aed's current status > really aren't very big. most game Gui's aren't very complex. basic > theming abilities and transparency are it's only aesthetic necessities, > and a few widgets to help graphics programmers with commonly needed > things(console, 3d functionality, etc...). unthemed aed would retain > it's current non-flashy toolkit look, making it still very capable of > normal program UIs. > how does everyone feel about this? does this seem useful, practical, > interesting? i'd be glad to hear from both people interested in it and > people just reading. > >potatoes Rodrigo Hernandez, lonewolf programmer Aeon Games http://www.aeongames.com |
|
From: potatoes <bwi...@co...> - 2005-02-27 19:11:19
|
aed is a partially complete, full function Gui toolkit that renders
under SDL. to me the most practical purpose for aed is as an easy
drop-in Gui system for games, or other openGL apps. it in it's current
form it is simply just another widget set, but because it renders in SDL
converting it to render to a openGL window wouldn't be very hard. a
themeable Gui library capable of providing the developer with already
complete menu, hud, and console systems right from the start of
development would be a very useful tool.
our current openGL output simply gives a SDL_texture with the window
to be used as a texture in the developers own openGL setup, which is
slow and limits lots of openGL functionality. though aed uses SDL's 2d
drawing api, which means low level rendering functions would need some
rewriting to switch. but SDL's library is similar to many basic openGL
commands, so it is very plausible.
we could provide an easy to use and simple to implement framework
for game makers. not something so encompassing as a game engine
framework but something that will provide:
* a way to open an openGL window.
* forms capable of both simple and complex starting menus.
* widgets to make a complete hud/in-game Gui.
* forms loadable from XML
* transparent client/server communication (easy with XML based forms)
the differences between such a toolkit and aed's current status
really aren't very big. most game Gui's aren't very complex. basic
theming abilities and transparency are it's only aesthetic necessities,
and a few widgets to help graphics programmers with commonly needed
things(console, 3d functionality, etc...). unthemed aed would retain
it's current non-flashy toolkit look, making it still very capable of
normal program UIs.
how does everyone feel about this? does this seem useful,
practical, interesting? i'd be glad to hear from both people interested
in it and people just reading.
potatoes
|
|
From: potatoes <bwi...@co...> - 2005-02-26 05:46:55
|
perhaps i should ask, is there still interest? |
|
From: Rodrigo H. <rod...@ra...> - 2005-02-26 02:28:55
|
No, it was designed to work with the 2D portion of SDL, I used a trick to have the SDL surfaces translated into a OGL texture which was then rendered to the screen as a quad with ortho projection, this approach probed to be quite slow, so I do not recomend it, you can see how I got it to work on the gltest.cpp source file, but again, its better to avoid it. At 04:55 PM 25/02/2005, you wrote: >Please exuse this interuption of the list. I just have a quick question. >Was aedGUI designed to use the OpenGL portion of SDL? For instance, in the >main.cpp test program, could I add SDL_OPENGL to the flags and get a 3D >window? Just curious before I continue with aedGUI. > >Andrew Carroll >Carroll-Tech >720-273-6814 >an...@ca... > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >aedGUI-developers mailing list >aed...@li... >https://lists.sourceforge.net/lists/listinfo/aedgui-developers Rodrigo Hernandez, lonewolf programmer Aeon Games http://www.aeongames.com |
|
From: Andrew C. <an...@ca...> - 2005-02-26 02:15:11
|
Please exuse this interuption of the list. I just have a quick question. Was aedGUI designed to use the OpenGL portion of SDL? For instance, in the main.cpp test program, could I add SDL_OPENGL to the flags and get a 3D window? Just curious before I continue with aedGUI. Andrew Carroll Carroll-Tech 720-273-6814 an...@ca... |
|
From: HERNANDEZ C. R. J. <rod...@ra...> - 2005-02-25 19:21:39
|
I am here, I have answered a couple of posts on the SF forums, however, I've been working on my other GUI Idea (check the front page of my site for the CVSROOT if you want to check it out), so it's been a while since I last worked on aedGUI, I haven't seen any activity on CVS either. ----- Mensaje Original ----- De: Ivan Stankovic <po...@fl...> Fecha: Viernes, Febrero 25, 2005 11:36 am Asunto: Re: [aedGUI] help wanted? > On Thu, Feb 24, 2005 at 07:04:01PM -0600, potatoes wrote: > > sometime ago, i did some development with you guys and i was > wondering > > if you are interested in any help again. > > Hello there! > > This list has been silent for quite some time, it seems the > project is (almost?) dead. I wonder whether Eduardo and Rodrigo are > still subscribed... > > -- > Ivan Stankovic, po...@fl... > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users.Discover which products truly live up to the hype. Start > reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > aedGUI-developers mailing list > aed...@li... > https://lists.sourceforge.net/lists/listinfo/aedgui-developers > |