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-09-29 11:42:54
|
On Wed, 2004-09-29 at 12:31 +0100, Andrew Godwin wrote: > > Aah alright, :) maybe you can just load them, and if the resolution is > > too low just 'cut off' the right side. (that is possible right, in > > html ? ) > > Hmm, I'm not sure, although I wouldn't be surprised. I'll have ago. Alright, sounds good... We want to do a release upcoming monday, Do you think it's possible to have (atleast) a static version ready before then ? (if not, it's no problem). Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-09-29 11:34:55
|
Heya list, I finally finished the plugin library stuff in CVS. This means that the plugin system now actually looks at the multiple entries that it can get from the plugin. the CVS XMMS plugin needs to be recompiled since an 'index' entry has been added to the VisPluginRef structure. This field contains the index in the VisPluginInfo structure for a given .so. Cheers, Denins |
|
From: Andrew G. <and...@bl...> - 2004-09-29 11:31:20
|
On Wednesday 29 September 2004 09:29, Dennis Smit wrote: > On Wed, 2004-09-29 at 07:29 +0100, Andrew Godwin wrote: > > On Tuesday 28 September 2004 23:20, Dennis Smit wrote: > > > Heya, not sure if it's useful, but I made some banners that might be > > > used in the website it's banner rotation: > > > > > > http://www.plasser.nl/synap/libvisual/banners/ > > > > > > > > > Let me know what you think. > > > > Good; they're quite wide (I've been planning for 800x600 resolutions, > > too) but it doen't matter too much. Besides, it might be possible to find > > some way to detect and change according to resolution, although that's > > possibly going too far ;) > > Aah alright, :) maybe you can just load them, and if the resolution is > too low just 'cut off' the right side. (that is possible right, in > html ? ) Hmm, I'm not sure, although I wouldn't be surprised. I'll have ago. |
|
From: Dennis S. <sy...@yo...> - 2004-09-29 08:59:31
|
Heya Duilio I've got a suggestion for the config window: When double click on a plugin in the list, start a morph to that plugin. What do you think about it ? Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-09-29 08:45:48
|
Alright guys,
Since we're really not going to make the schedule anyway, I'd like
to do a bugfix release next week.
Goals:
* Loads of fixes.
* XMMS Plugin stable/usable (You think this is possible Duilio ?)
What needs to be done:
Globally:
* Look for issues, list them.
XMMS plugin:
crash op gl startup.
cleanup -> start, switching plugins kinda weird
sometimes.
QUIT WM -> start, crash. (can't reproduce anylonger..)
Completely working config dialog
Libvisual:
Finish plugin libraries (multiple plugin structures in
one plugin).
Log verboseness API.
Plugin flags (atleast integer flags).
Plugins:
Random seed infinite.
What do you guys think, can we do this together and roll out a quality
release before monday next week ?
I sure think we can, but I seem to be miscalculating schedules wrongly
anyway :)
Cheers,
Dennis
|
|
From: Dennis S. <sy...@yo...> - 2004-09-29 08:29:46
|
On Wed, 2004-09-29 at 07:29 +0100, Andrew Godwin wrote: > On Tuesday 28 September 2004 23:20, Dennis Smit wrote: > > Heya, not sure if it's useful, but I made some banners that might be > > used in the website it's banner rotation: > > > > http://www.plasser.nl/synap/libvisual/banners/ > > > > > > Let me know what you think. > > Good; they're quite wide (I've been planning for 800x600 resolutions, too) but > it doen't matter too much. Besides, it might be possible to find some way to > detect and change according to resolution, although that's possibly going too > far ;) Aah alright, :) maybe you can just load them, and if the resolution is too low just 'cut off' the right side. (that is possible right, in html ? ) Cheers and thanks, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-09-29 08:28:29
|
On Wed, 2004-09-29 at 03:13 -0300, Duilio Javier Protti wrote: > > I was thinking about something like this: > > VISUAL_LOG_VERBOSENESS_HIGH (for everything) > > VISUAL_LOG_VERBOSENESS_MEDIUM (for warnings/criticals/errors) > > VISUAL_LOG_VERBOSENESS_LOW (for critical/errors) > > and: > > VISUAL_LOG_VERBOSENESS_NONE (for disabling ALL the messages) > > I think is perfect Ok, care to implement it ? :) > > There is kinda one special case, that is VISUAL_LOG_INFO.. Not sure > > how we should handle this one in this case... > > Well, we must let the user some way to show a message >always< so > a good place to put that is on VISUAL_LOG_INFO messages I guess. Agree on that! Cheers, Dennis |
|
From: Andrew G. <and...@bl...> - 2004-09-29 06:29:39
|
On Tuesday 28 September 2004 23:20, Dennis Smit wrote: > Heya, not sure if it's useful, but I made some banners that might be > used in the website it's banner rotation: > > http://www.plasser.nl/synap/libvisual/banners/ > > > Let me know what you think. Good; they're quite wide (I've been planning for 800x600 resolutions, too) but it doen't matter too much. Besides, it might be possible to find some way to detect and change according to resolution, although that's possibly going too far ;) . |
|
From: Duilio J. P. <dp...@fc...> - 2004-09-29 06:01:42
|
> I was thinking about something like this: > VISUAL_LOG_VERBOSENESS_HIGH (for everything) > VISUAL_LOG_VERBOSENESS_MEDIUM (for warnings/criticals/errors) > VISUAL_LOG_VERBOSENESS_LOW (for critical/errors) > and: > VISUAL_LOG_VERBOSENESS_NONE (for disabling ALL the messages) I think is perfect > There is kinda one special case, that is VISUAL_LOG_INFO.. Not sure > how we should handle this one in this case... Well, we must let the user some way to show a message >always< so a good place to put that is on VISUAL_LOG_INFO messages I guess. Bye, Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 23:12:35
|
On Tue, 2004-09-28 at 20:05 -0300, Duilio Javier Protti wrote: > Cool!, I want for this from a time ago, but I don't have worked > on because it was for 0.1.8 on the ROADMAP. But I think will be > good to get it right now. Well, Don't take the roadmap too litteraly, it's a direction, not a final road, remember, where we go, we make the roads ;) > I was thinking on a simple system like: > > void visual_log_set_verbose (int yes_or_no); > > to enable/disable i.e. debug messages (but maybe other internal > things too). Also would be good to let the user set this through > visual_init() passing -v flag or something like that. Well, I wouldn't do that, and especially not something as common as '-v' An application that just passes on his argv/argc could errornously change the verboseness level. I personally don't think that just 'visual_log, on and off' is anough. I was thinking about something like this: VISUAL_LOG_VERBOSENESS_HIGH (for everything) VISUAL_LOG_VERBOSENESS_MEDIUM (for warnings/criticals/errors) VISUAL_LOG_VERBOSENESS_LOW (for critical/errors) and: VISUAL_LOG_VERBOSENESS_NONE (for disabling ALL the messages) There is kinda one special case, that is VISUAL_LOG_INFO.. Not sure how we should handle this one in this case... > I believe having different debug levels (i.e. from 0 to 9) is > a bad idea on a dynamic library like libvisual, and is in general > very confusing. I agree that over doing it is confusing, but there is a clear distinction between VISUAL_LOG_DEBUG and VISUAL_LOG_ERROR, I don't think you can treat them equaly as they are whole different message classes. Please give me your comments... Greets, Dennis |
|
From: Duilio J. P. <dp...@fc...> - 2004-09-28 22:54:01
|
> I've got a question, Since you did most of the visual_log system, > what do you think about having a method that sets the verboseness > of the log system, so you can make it shutup all together, both > through an API call and a environment variable... It would be very > nice if you could have a look at this. > > Thanks, > Dennis Cool!, I want for this from a time ago, but I don't have worked on because it was for 0.1.8 on the ROADMAP. But I think will be good to get it right now. I was thinking on a simple system like: void visual_log_set_verbose (int yes_or_no); to enable/disable i.e. debug messages (but maybe other internal things too). Also would be good to let the user set this through visual_init() passing -v flag or something like that. I believe having different debug levels (i.e. from 0 to 9) is a bad idea on a dynamic library like libvisual, and is in general very confusing. Bye, Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 22:20:57
|
Heya, not sure if it's useful, but I made some banners that might be used in the website it's banner rotation: http://www.plasser.nl/synap/libvisual/banners/ Let me know what you think. Cheers, Dennis |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 21:52:13
|
On Tue, 2004-09-28 at 22:42 +0100, Andrew Godwin wrote: > On Tuesday 28 September 2004 22:28, Dennis Smit wrote: > > Regarding the website, > > > > I think the big white space is a bit distracting, But I got another > > idea, maybe it's an idea to have multiple banners and rotate them. > > > > So we can make a few banners, with shots.. > > > > What do you think about that ? > > > Good idea, although I'd blend the shots into the white (sort of like the logo > on the left). > > The only reason it's large and white is the fact that that side of the logo > was... but it does need something there, I think. > > I'll add an example tomorrow, to show you what I mean. I've got a few shots > off amarok so far. > > Andrew Alright, I'm making some logos right now :) Cheers, Dennis |
|
From: Andrew G. <and...@bl...> - 2004-09-28 21:48:10
|
On Tuesday 28 September 2004 22:36, Jeroen wrote: > In message #1 on Tue, Sep 28, 2004 at 08:24:18PM +0100, Andrew Godwin mumbled: > > <snip> > > http://bytehoard.ath.cx/libvisualtest > > *Wow!* > I'm liking the reactions so far, for sure. > A few points though > > 1) sync the sequence of the icons on the left with those on the right? > (The icons are a really cool idea btw.) Yeah, this will be a feature; probably use the same code for both menus, just dropping the next. > 2) seperate 'about' and 'news'. Add icon/entry for each? Think > about getting back to 'main page', too. > 3) where to put documentation? > I's an example ;) I know very well you need more stuff; these were just five things I though of and used. However, I think having about & news on the main page is a good idea. And perhaps a wiki-style thing for docs? |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 21:47:01
|
On Tue, 2004-09-28 at 23:36 +0200, Jeroen wrote: > In message #1 on Tue, Sep 28, 2004 at 08:24:18PM +0100, Andrew Godwin mumbled: > > <snip> > > http://bytehoard.ath.cx/libvisualtest > > *Wow!* > > A few points though > > 1) sync the sequence of the icons on the left with those on the right? > (The icons are a really cool idea btw.) > 2) seperate 'about' and 'news'. Add icon/entry for each? Think > about getting back to 'main page', too. > 3) where to put documentation? Well we need some more links anyway, like 'team' and such, but I think that'll be in the CMS :) |
|
From: Andrew G. <and...@bl...> - 2004-09-28 21:42:12
|
On Tuesday 28 September 2004 22:28, Dennis Smit wrote: > Regarding the website, > > I think the big white space is a bit distracting, But I got another > idea, maybe it's an idea to have multiple banners and rotate them. > > So we can make a few banners, with shots.. > > What do you think about that ? > Good idea, although I'd blend the shots into the white (sort of like the logo on the left). The only reason it's large and white is the fact that that side of the logo was... but it does need something there, I think. I'll add an example tomorrow, to show you what I mean. I've got a few shots off amarok so far. Andrew |
|
From: Jeroen <dys...@xs...> - 2004-09-28 21:36:40
|
In message #1 on Tue, Sep 28, 2004 at 08:24:18PM +0100, Andrew Godwin mumbled: > <snip> > http://bytehoard.ath.cx/libvisualtest *Wow!* A few points though 1) sync the sequence of the icons on the left with those on the right? (The icons are a really cool idea btw.) 2) seperate 'about' and 'news'. Add icon/entry for each? Think about getting back to 'main page', too. 3) where to put documentation? Kind regards / met vriendelijke groet, Jeroen |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 21:28:12
|
Regarding the website, I think the big white space is a bit distracting, But I got another idea, maybe it's an idea to have multiple banners and rotate them. So we can make a few banners, with shots.. What do you think about that ? |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 21:11:08
|
On Tue, 2004-09-28 at 23:32 +0300, Vitaly V. Bursov wrote: > > Instead of flags, use char *indentifiers or ?, also with different > Not "instead" but "and". > > > applications, how do we make sure that indentifiers don't collide. > well, usually application names are different... I propose to add > char *optional_plugin_app_parameter_or_whatever; > to VisPluginInfo. PLugin can set flag, say, APPLICATION_SPECIFIC > and that char* string to "my_app_name iface 0.1". > Libvisual must be told that it can load and use that plugin. Ok, I kinda understand what you describe here, but as the dummy I'am I probably need an example scenario to understand the real usefulness of the approach... Thanks, Dennis |
|
From: Andrew G. <and...@bl...> - 2004-09-28 21:01:35
|
On Tuesday 28 September 2004 21:48, Dennis Smit wrote: > On Tue, 2004-09-28 at 21:17 +0100, Andrew Godwin wrote: > > 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. > > Assume you meant 'I can ...' :) > > Yeah news feed is important, maybe a screenshot manager is useful... Yes, of course I did. I'm still deciding what basic CMS to go with, or to use my build-your-own set of basic libraries. Gallery or something similar would be good for the screenshots, probably, should i need it. Andrew |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 20:48:17
|
On Tue, 2004-09-28 at 21:17 +0100, Andrew Godwin wrote: > 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. Assume you meant 'I can ...' :) Yeah news feed is important, maybe a screenshot manager is useful... Anyone else ideas ? Thanks, Dennis |
|
From: Vitaly V. B. <vit...@us...> - 2004-09-28 20:32:53
|
On Tue, 28 Sep 2004 21:52:39 +0200 Dennis Smit <sy...@yo...> wrote: > On Tue, 2004-09-28 at 22:14 +0300, Vitaly V. Bursov wrote: > > May be implement something like VISUAL_PLUGIN_FLAG_SPECIAL but > > in an opposite way. I.e. plugin must be used only with this > > application. This application simply provide some kind of > > special data/interfaces that can not be used with Libvisual. > > > > One nice way to implement this is to use const char* identifier > > to specify, say, application id. Numeric id's -- enums and > > #defines not very useful here, I think. > > > > We could place this id to VisPluginInfo. If so, we should add > > some void *dummys[5]; so we can extend functionality further > > without breaking plugin ABI. > Ok, this might sound a bit lame, but I kinda lost you here :) My fault... I'm trying to do few things at once. In different languages ;) > Instead of flags, use char *indentifiers or ?, also with different Not "instead" but "and". > applications, how do we make sure that indentifiers don't collide. well, usually application names are different... I propose to add char *optional_plugin_app_parameter_or_whatever; to VisPluginInfo. PLugin can set flag, say, APPLICATION_SPECIFIC and that char* string to "my_app_name iface 0.1". Libvisual must be told that it can load and use that plugin. > Let's keep in mind that libvisual will be very succesful and used > everywhere, even on the mobile phone (ehm.. alright I'm a bit :)) it will be REALLY slow! We'll need a mobile phone cluster! > dreamy today) but you got my point... Of course, it's just another to extend functionality with no pain. Plugin can use export'ed data inside of application itself. (i think) On ELF binaries only. he-he. -- Vitaly GPG Key ID: F95A23B9 |
|
From: Andrew G. <and...@bl...> - 2004-09-28 20:18:02
|
>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. Andrew |
|
From: Vitaly V. B. <vit...@us...> - 2004-09-28 20:03:18
|
On Tue, 28 Sep 2004 20:24:18 +0100 Andrew Godwin <and...@bl...> wrote: > http://bytehoard.ath.cx/libvisualtest 8-(_) WOW!! It's Great, Andrew! -- Vitaly GPG Key ID: F95A23B9 |
|
From: Dennis S. <sy...@yo...> - 2004-09-28 19:52:44
|
On Tue, 2004-09-28 at 22:14 +0300, Vitaly V. Bursov wrote: > May be implement something like VISUAL_PLUGIN_FLAG_SPECIAL but > in an opposite way. I.e. plugin must be used only with this > application. This application simply provide some kind of > special data/interfaces that can not be used with Libvisual. > > One nice way to implement this is to use const char* identifier > to specify, say, application id. Numeric id's -- enums and > #defines not very useful here, I think. > > We could place this id to VisPluginInfo. If so, we should add > some void *dummys[5]; so we can extend functionality further > without breaking plugin ABI. Ok, this might sound a bit lame, but I kinda lost you here :) Instead of flags, use char *indentifiers or ?, also with different applications, how do we make sure that indentifiers don't collide. Let's keep in mind that libvisual will be very succesful and used everywhere, even on the mobile phone (ehm.. alright I'm a bit dreamy today) but you got my point... About ABI compatibility, we surely need this at some point, but I rather wait till we're not in heavy development anylonger. Cheers, Dennis |
10 messages has been excluded from this view by a project administrator.
