Menu
▾
▴
libvisual-devel — libvisual mailinglist for developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(38) |
May
(22) |
Jun
(92) |
Jul
(101) |
Aug
(18) |
Sep
(286) |
Oct
(180) |
Nov
(73) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(18) |
Feb
(74) |
Mar
(56) |
Apr
(11) |
May
(5) |
Jun
(4) |
Jul
(20) |
Aug
(4) |
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
| 2006 |
Jan
(11) |
Feb
(2) |
Mar
(10) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(24) |
Aug
(11) |
Sep
(5) |
Oct
(16) |
Nov
(25) |
Dec
(8) |
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
(4) |
Nov
(12) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|
From: Dennis S. <sy...@yo...> - 2004-10-05 16:22:21
|
On Tue, 2004-10-05 at 02:50 -0300, Duilio Javier Protti wrote:
> Oh, I see now what are your plans for VisUI! But, how exactly we can
> give that hints. I remember you have mentioned something like libglade
> does.
There will be a VisUIContainer
kinda thing (don't take things to literally
btw, I'm just sketching).
You can pack other VisUIContainers in that
like a VisUIGroup.
(we will keep it very basic)
For example:
___
VisUIContainer *uicont = visual_plugin_get_ui_container (plugin);
VisUIGroup *uigroup = visual_ui_group_new ("Sexy configs");
VisUILabel *uilabel = visual_ui_label_new ("Something: ");
VisUIText *uitext = visual_ui_text_new (paramentry);
VisUIBox *uibox = visual_ui_box_new (VISUAL_UI_HBOX);
visual_ui_box_pack (uibox, uilabel);
visual_ui_box_pack (uibox, uitext);
visual_ui_group_add (uigroup, uibox);
visual_ui_container_add (uicont, uigroup);
___
And have some good API to get extract the userinterface data
so you can easily build it within your app.
I really think it's important to have a facility to describe
userinterfaces in, atleast to some degree... If people have comments,
thoughts, please comment now, so we can all think about it for a while.
> Doing with the thing we have now won't be difficult:
> - grouping of params could be done changing to a VisList of
> VisParamContainer's on VisPluginData structure.
Won't do that, it's hacky. It's working around the real problem.
> - lay restrictions on the input could be done adding a pointer to a
> 'validator' function, which returns TRUE if the given value for the
> VisParam a valid one (and probably also return a message string in
> case of error), and will be provided by the plugin writer.
This can be described on UI niveau, where I think this should
be handled.
>
> But well, VisUI still being a good idea, I suggest these easy changes
> just to concentrate on other things for a while, like VisFont and the
> actual libvisual-display.
Sorry, I won't change things, to be reverted at a later point. We are
still in development, we don't have to be production ready at this
moment. Rather solve the problems once and right, than solve
them twice. I rather call us stable, both API/ABI when we're done
than when we're not done, but just want people to use us. This is my
opinion. I think that, atleast in the beginning Vitaly will be working
mostly on the libvisual-display stuff. It's in good hands for sure...
I also agree that our ROADMAP has to be revised a bit, I like to give
VisThread a very low piority, but raise the piority of VisFont
and VisAudio rewrite.
The ROADMAP is still a very good overview about, what NEEDS to be done.
Not what needs to be done at which point. It's a nice guide, but it's
far from final. Till now we have mostly been working on our 'feelings'
and I think it's turning out very well.
I personally, will continue work on the core library, I will
need some help here and there, but generally, I can pull it off :)
I'm getting used to the stress introduced by my new school, so I'm able
to hack more again :) What we really could use is some anthousiastic
plugin porter!, now we have a website, it's time for a new
call for help 'Plugin porters required' :).. hehehe.
Cheers and thanks,
Dennis
|
|
From: Andrew G. <and...@bl...> - 2004-10-05 16:06:15
|
On Tuesday 05 October 2004 16:43, Dennis Smit wrote: > On Mon, 2004-10-04 at 22:14 +0100, Andrew Godwin wrote: > > An initial (actually dynamic, but it may as well be static) version of > > the libvisual website is now properly up at http://libvisual.sf.net/v2 > > Simply super! > > > It does run off a database, and the frontend seems to be working nicely. > > What's missing is the administration bit; currentely, any updates have to > > be done with phpmyadmin and some knowledge of how the whole damn thing > > works. > > > > I'm aiming to get the admin interface done soon; it's actually harder > > than the main site, since it needs users and extra functionality like > > that. > > Sounds like a challenge *grin* hehe :) Yeah, it's the boring stuff that's the hardest, with my motivation being enjoyment and all... however, I'm nearly there with that now. > > > If you want, I could redirect the main site there now (the content's > > exactly the same, I've just copied it over), but you won't be able to do > > anything to it (adding news?) without adding a row or two in the > > database. Or getting me to do it. > > Yeah, please redirect it, the old site is crap [tm]. Yours truly rocks. > OK, will do at some point. > Ok, now a few requests: > > 1. an: [older news] feature. Will add this after the admin interface; currentely, there's only three news items ;) > 2. an extra site: "Team". Will do via admin interface. Anyway, you need to write stuff in it. > 3. remove "Email" and rename it to contact and have a description how to > join the mailing lists. Will do that now. > > 4. Add an 'documentation' entry. We will put some docs there, both > user and devel docs. See 2) OK, back to coding... Andrew |
|
From: Dennis S. <sy...@yo...> - 2004-10-05 15:56:50
|
On Tue, 2004-10-05 at 07:30 +0100, Andrew Godwin wrote: > As you can see, it does point to the SF page for downloads... > > Dennis said he wanted to keep the two news feeds separate; I don't know his > specific reasons. I've done the SF RSS feed approach before, with MagpieRSS, > but he wanted a separate one, so there it is. I personally like the .sf.net for brief anouncements, like 'new release' and keep the website also for regular updates, semi off topic things. Often with development news, in the fashion like 'look Duilio made the xmms plugin rock harder!' and 'Vitaly is fixing our display target framework, look how good we are', besides 'We thank andrew for his great website work' as last 'Dystopia made docs!!!'... Ok I overdid that a bit, but the message is clear probably ;) > Gallery is definitely going in; I'll do that when the main admin stuff is > done. Then screenshots galore can be uploaded. Rocking for sure. Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-10-05 15:53:10
|
On Tue, 2004-10-05 at 01:56 +0300, Vitaly V. Bursov wrote: > Lvdisplay now supports framebuffer based plugins in GLX. Well, almost. :) > 8bit plugins rendered in 8bit RGB 3 3 2. no palette support now. It's also upside down :) > Dennis, why oinksie plugin resizes (almost) correctly while others > (mostly) not? What steps should be performed to notify everything that > dimensions have changed? is height also the screen scanline it's byte pitch ? I think it has to do with this. Oinksie is 32 bits, so it's already aligned, but lower depths probably have an alignment issue... > PS. lvdisplay is extremly unstable. It can crash itself, crash your > X Server or freeze your PC. Sorry. ;) That is alright, it's an extremely motivating piece of software, I really like lvdisplay to succeed very well. I think that depending on things like SDL won't ever suite our needs, in complete control, display targets, GL support and multihead support. I'm so sure that by making lvdisplay both very powerful and also easy, with lot's of capabilities/special capabilities for a given display target (but generalised under a set of drivers) we're going to deliver an awesome product. Together with libvisual, we will just make the freesoftware world rock on audio visualisation! Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-10-05 15:44:48
|
On Mon, 2004-10-04 at 22:14 +0100, Andrew Godwin wrote: > An initial (actually dynamic, but it may as well be static) version of the > libvisual website is now properly up at http://libvisual.sf.net/v2 Simply super! > It does run off a database, and the frontend seems to be working nicely. > What's missing is the administration bit; currentely, any updates have to be > done with phpmyadmin and some knowledge of how the whole damn thing works. > > I'm aiming to get the admin interface done soon; it's actually harder than the > main site, since it needs users and extra functionality like that. Sounds like a challenge *grin* hehe :) > If you want, I could redirect the main site there now (the content's exactly > the same, I've just copied it over), but you won't be able to do anything to > it (adding news?) without adding a row or two in the database. Or getting me > to do it. Yeah, please redirect it, the old site is crap [tm]. Yours truly rocks. Ok, now a few requests: 1. an: [older news] feature. 2. an extra site: "Team". 3. remove "Email" and rename it to contact and have a description how to join the mailing lists. 4. Add an 'documentation' entry. We will put some docs there, both user and devel docs. Thanks a lot, Dennis |
|
From: Andrew G. <and...@bl...> - 2004-10-05 06:30:47
|
On Tuesday 05 October 2004 01:03, Gustavo Sverzut Barbieri wrote: > On Monday 04 October 2004 18:14, Andrew Godwin wrote: > > An initial (actually dynamic, but it may as well be static) version of > > the libvisual website is now properly up at http://libvisual.sf.net/v2 > > > > It does run off a database, and the frontend seems to be working nicely. > > What's missing is the administration bit; currentely, any updates have to > > be done with phpmyadmin and some knowledge of how the whole damn thing > > works. > > > > I'm aiming to get the admin interface done soon; it's actually harder > > than the main site, since it needs users and extra functionality like > > that. > > > > If you want, I could redirect the main site there now (the content's > > exactly the same, I've just copied it over), but you won't be able to do > > anything to it (adding news?) without adding a row or two in the > > database. Or getting me to do it. > > > > Anyway, work will continue on the admin stuff tomorrow. > > The site rocks! > > About the admin stuff, try to keep with SF resources and people use that, > just things that are not available there you need to code. As you can see, it does point to the SF page for downloads... Dennis said he wanted to keep the two news feeds separate; I don't know his specific reasons. I've done the SF RSS feed approach before, with MagpieRSS, but he wanted a separate one, so there it is. Gallery is definitely going in; I'll do that when the main admin stuff is done. Then screenshots galore can be uploaded. Andrew |
|
From: Duilio J. P. <dp...@fc...> - 2004-10-05 05:38:00
|
> I think that parsing just the VisParamEntries won't provide a nice > user interface experience, especially when it comes to big > lists of VisParamEntries. The VisUI module could give some hints > to the UI builder like, grouping, what kind of input entry, lay > restrictions on the input. VisUI won't be complex, or big, it's just > a few extra hints so a way nicer UI can be build. > > My 2cents. > > Cheers, > Dennis Oh, I see now what are your plans for VisUI! But, how exactly we can give that hints. I remember you have mentioned something like libglade does. Doing with the thing we have now won't be difficult: - grouping of params could be done changing to a VisList of VisParamContainer's on VisPluginData structure. - lay restrictions on the input could be done adding a pointer to a 'validator' function, which returns TRUE if the given value for the VisParam a valid one (and probably also return a message string in case of error), and will be provided by the plugin writer. But well, VisUI still being a good idea, I suggest these easy changes just to concentrate on other things for a while, like VisFont and the actual libvisual-display. Bye, Duilio. |
|
From: Gustavo S. B. <gu...@gs...> - 2004-10-05 00:02:29
|
On Monday 04 October 2004 18:14, Andrew Godwin wrote: > An initial (actually dynamic, but it may as well be static) version of the > libvisual website is now properly up at http://libvisual.sf.net/v2 > > It does run off a database, and the frontend seems to be working nicely. > What's missing is the administration bit; currentely, any updates have to > be done with phpmyadmin and some knowledge of how the whole damn thing > works. > > I'm aiming to get the admin interface done soon; it's actually harder than > the main site, since it needs users and extra functionality like that. > > If you want, I could redirect the main site there now (the content's > exactly the same, I've just copied it over), but you won't be able to do > anything to it (adding news?) without adding a row or two in the database. > Or getting me to do it. > > Anyway, work will continue on the admin stuff tomorrow. The site rocks! About the admin stuff, try to keep with SF resources and people use that, just things that are not available there you need to code. -- Gustavo Sverzut Barbieri --------------------------------------- Engenharia de Computacao 2001 - UNICAMP GPSL - Grupo Pro Software Livre Cell..: +55 (19) 9165 8010 Jabber: gsb...@ja... ICQ#: 17249123 GPG: 0xB640E1A2 @ wwwkeys.pgp.net |
|
From: Gustavo S. B. <gu...@gs...> - 2004-10-04 23:53:41
|
On Tuesday 28 September 2004 17:17, Andrew Godwin wrote: > >8-(_) WOW!! > > > >It's Great, Andrew! > > > > > >I'm simply VERY VERY VERY happy with this design, it's exactly what I > >want. If you could throw an CMS around this, that would be just super. > > > >Thanks a lot! > > > >Dennis > > That's reassuring. I'll see if I can't get some sort of CMS around it; you > guys don't want too much, I presume, just a news feed and some static > content. I'll see what I come up with. Hi Andrew, Sorry for being late, the site is not up anymore so I can see... but since most liked it, I like it too :D About the CMS, it would be good to have http://gallery.sf.net and use news feed (RSS) from SF, so we can keep things centralized... There are many php scripts to format SF RSS into webpages, even the project releases and stuff like that... it would ROCK! -- Gustavo Sverzut Barbieri --------------------------------------- Engenharia de Computacao 2001 - UNICAMP GPSL - Grupo Pro Software Livre Cell..: +55 (19) 9165 8010 Jabber: gsb...@ja... ICQ#: 17249123 GPG: 0xB640E1A2 @ wwwkeys.pgp.net |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-04 22:56:28
|
On Mon, 04 Oct 2004 23:13:29 +0200 Dennis Smit <sy...@yo...> wrote: > Vitaly, could you update libvisual-display, I don't know how > xlib stuff works, regarding events, please fill in the 0, 0 with x, y > value. Great! I've updated lvdisplay. Lvdisplay now supports framebuffer based plugins in GLX. Well, almost. :) 8bit plugins rendered in 8bit RGB 3 3 2. no palette support now. Dennis, why oinksie plugin resizes (almost) correctly while others (mostly) not? What steps should be performed to notify everything that dimensions have changed? PS. lvdisplay is extremly unstable. It can crash itself, crash your X Server or freeze your PC. Sorry. ;) -- Vitaly GPG Key ID: F95A23B9 |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 21:25:06
|
Maybe something like this would work: 'Is there a depth close to my own depth, take that' if not, take the depth nearest, but lower than my (where my is display) depth. But I agree, the current 'depth' system is just suck. I want to a plugin to be able to say "I support these depths", "pick one that you'd like", but as well "I will now start with outputing THIS DEPTH", (for example for the gdkpixbuf plugin, you don't know what depth the image has, so the plugin has to be able to notify in realtime)... I'm undecided howto do this right, but now we're doing libvisual-display, this might be the right time to fix this... I must admit tho, that I'm really kinda undecided. There are a few steps in this: 1. Plugin requests depth. 2. If plugins ran within a VisActor the VisActor has to catch this notify, and resynchronise with the plugin. (and possibly revise the depth transformation environment). 3. The app needs to be notified, Maybe the app runs it in this depth itself. And then resync with the VisActor.. So actually, the app needs to know BEFORE the VisActor knows, but when it gets a request, it should handle it by resyncing the VisActor. Now we get at the point we need an event loop within the APP. This makes it harder to use libvisual, which kinda suck... I'm not sure, please think with me :) Cheers, Dennis On Mon, 2004-10-04 at 23:46 +0300, Vitaly V. Bursov wrote: > Some actor plugins support multiple depths... > How it should be choosed? It's a difficult to choose > the best depth - it's too plugin specific. > > I propose to add a function to actor plugin API which > gets available depths as its argument and returns only > one depth that plugin performs best. Anyway there must > be manual override. > > Not sure. Suggestions? > |
|
From: Andrew G. <and...@bl...> - 2004-10-04 21:14:54
|
An initial (actually dynamic, but it may as well be static) version of the libvisual website is now properly up at http://libvisual.sf.net/v2 It does run off a database, and the frontend seems to be working nicely. What's missing is the administration bit; currentely, any updates have to be done with phpmyadmin and some knowledge of how the whole damn thing works. I'm aiming to get the admin interface done soon; it's actually harder than the main site, since it needs users and extra functionality like that. If you want, I could redirect the main site there now (the content's exactly the same, I've just copied it over), but you won't be able to do anything to it (adding news?) without adding a row or two in the database. Or getting me to do it. Anyway, work will continue on the admin stuff tomorrow. Andrew |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 21:13:53
|
ABI/API incompat changes
Vitaly, could you update libvisual-display, I don't know how
xlib stuff works, regarding events, please fill in the 0, 0 with x, y
value.
case ButtonPress:
/* XXX Hm, how do i specify another parameters
like x,y? */
visual_event_queue_add_mousebutton (eventqueue,
ev.xbutton.button,
(ev.type == ButtonPress) ?
VISUAL_MOUSE_DOWN:VISUAL_MOUSE_UP, 0, 0);
break;
Thanks,
Dennis
|
|
From: Dennis S. <sy...@yo...> - 2004-10-04 20:53:30
|
On Mon, 2004-10-04 at 22:52 +0300, Vitaly V. Bursov wrote: > On Mon, 04 Oct 2004 19:13:27 +0200 > Dennis Smit <sy...@yo...> wrote: > > > It reads the x, y data from the last mouse move event. I'm not sure > > if it's a good idea to do it like this, what do you think ? > Hm, and how handled situation if there were no motion event? > For example plugin changes, mouse clicks. No motion. Mouse is > inside of plugin window. I agree, we should change this... Will fix it in CVS... Thanks, Dennis |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-04 20:46:43
|
Some actor plugins support multiple depths... How it should be choosed? It's a difficult to choose the best depth - it's too plugin specific. I propose to add a function to actor plugin API which gets available depths as its argument and returns only one depth that plugin performs best. Anyway there must be manual override. Not sure. Suggestions? -- Vitaly GPG Key ID: F95A23B9 |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 20:39:18
|
On Mon, 2004-10-04 at 22:53 +0300, Vitaly V. Bursov wrote: > On Mon, 04 Oct 2004 19:12:52 +0200 > Dennis Smit <sy...@yo...> wrote: > > > Nearly no code for a full functional visual + window + events. > Thanks to Libvisual :) Wouldn't have been possible with all the support and suggestions and code from all you guys, I'm so happy with the state we're in now. Cheers, Dennis |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-04 19:53:10
|
On Mon, 04 Oct 2004 19:12:52 +0200 Dennis Smit <sy...@yo...> wrote: > Nearly no code for a full functional visual + window + events. Thanks to Libvisual :) > Do you need extra things from libvisual to ease lvdisplay > development ? Not sure... Gonna find out soon. -- Vitaly GPG Key ID: F95A23B9 |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-04 19:52:11
|
On Mon, 04 Oct 2004 19:13:27 +0200 Dennis Smit <sy...@yo...> wrote: > It reads the x, y data from the last mouse move event. I'm not sure > if it's a good idea to do it like this, what do you think ? Hm, and how handled situation if there were no motion event? For example plugin changes, mouse clicks. No motion. Mouse is inside of plugin window. -- Vitaly GPG Key ID: F95A23B9 |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 17:15:03
|
On Mon, 2004-10-04 at 18:42 +0100, salsaman wrote: > Hi guys, > couple of quick questions. I understand you've added flags to the > actors, which flags should I check for to get actors suitable for LiVES ? > I think there was also a flag for non-reentrant inputs, how do I check > for this ? This issue will be resolved in livido by setting an error > condition. > > Think these should be the last updates for LiVES. > > Cheers, > Salsaman. We've got flags, yet, however I haven't yet tagged alsa as nonreentrant, because it's actually reentrant, it doesn't error on every sound card... I'm not yet decided how to solve this issue. It's not yet entirely done, I'll keep you posted.. Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 17:13:50
|
It reads the x, y data from the last mouse move event. I'm not sure if it's a good idea to do it like this, what do you think ? Cheers, Dennis On Mon, 2004-10-04 at 02:08 +0300, Vitaly V. Bursov wrote: > Shouldn't function visual_event_queue_add_mousebutton() take x, y parameters also? > VisEventMouseButton struct has x,y members. > |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 17:13:17
|
Had a look at it, I'm damn impressed!!! Nearly no code for a full functional visual + window + events. This is just so good! Do you need extra things from libvisual to ease lvdisplay development ? Cheers, Dennis On Mon, 2004-10-04 at 02:57 +0300, Vitaly V. Bursov wrote: > Lvdisplay test application can now load and play input&actor pair. > Window resize is supported. > > Only GL actors supported so far. > |
|
From: Dennis S. <sy...@yo...> - 2004-10-04 17:12:25
|
2004-10-04 Dennis Smit <ds...@ne...>
* libvisual/lv_random.*: A bit of a overhaul by
Vitaly V. Bursov, thanks Vitaly :) (owyeah
also added double, float)
Thanks a lot Vitaly, looks really good, I love how you've
solved the things with the #defines :)
I changed a few things, take a look at CVS.
Cheers,
Dennis
On Mon, 2004-10-04 at 01:37 +0300, Vitaly V. Bursov wrote:
> Here we go!...
>
> Dennis, do you have some app to test this random() stuff?
>
|
|
From: salsaman <sal...@xs...> - 2004-10-04 16:27:53
|
Hi guys, couple of quick questions. I understand you've added flags to the actors, which flags should I check for to get actors suitable for LiVES ? I think there was also a flag for non-reentrant inputs, how do I check for this ? This issue will be resolved in livido by setting an error condition. Think these should be the last updates for LiVES. Cheers, Salsaman. |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-03 23:57:03
|
Lvdisplay test application can now load and play input&actor pair. Window resize is supported. Only GL actors supported so far. -- Vitaly GPG Key ID: F95A23B9 |
|
From: Vitaly V. B. <vit...@us...> - 2004-10-03 23:09:31
|
Shouldn't function visual_event_queue_add_mousebutton() take x, y parameters also? VisEventMouseButton struct has x,y members. -- Vitaly GPG Key ID: F95A23B9 |
10 messages has been excluded from this view by a project administrator.
