Michael Herger;261978 Wrote: > > What I would like to see is a single place where I could look recent > > Subscribing to the checkins list comes close to this: every checkin is > > commented. It's what you would see in a complete change log. > > http://lists.slimdevices.com/lists/listinfo/checkins > Sorry, didn't know about that one, I will set up an e-mail adress for it and subscribe it, sounds like a reasonable repository. > > Get used to Subversion: updates will take 5 minutes. Updating is easily > > done and doesn't need a lot of knowledge about SVN. > http://tortoisesvn.tigris.org/ integrates nicely with Windows > explorer. > Can use that to checkout changes to the windows runtime system? I am used to svn on Linux and there I have to do my own build, don't I? Or does it only update the perl code then and the executables aren't changed? > > > > Wouldn't have changed anything in this case anyway, wouldn't it? > > You would have been aware of the issue when it was a "hot topic", when > the > code broke your skin. That's when it was discussed in the forums. > [color=blue] > I was referring to using the latest build. That wouldn't have changed anything since it's not a bug, but a change. Following the discussion, of course, would have helped. > > If you're not ready to test the fixed versions, you shouldn't complain > about the issues. If you assume yourself they've already been fixed, > then why bother at all? > I didn't complain, I made a suggestion. And I feel that working on this I am lacking documentation all over the place, which is probably normal for a beta system. But then it shouldn't be if there's more then one person working per task. I know people hate writing documentation (myself included) but it really can help a lot. One thing I did mention before is preferences. I can read those form the preferences file but then I don't always know what they do and especially I don't know i they are still used. > > Don't get me wrong, but I considered you and the way you're working > very professional and ambitious. You've come up with a really great and > slick skin, which does things we didn't are possible with a skin. That's > why I'm a bit surprised about your reaction. You expect plugin authors > to change > their plugins just to make them _accepted_ by your skin, whether > they're actually broken or not. But you're not ready to follow the > development which is done for the platform you're working on? > Well, I never claimed to be a professional developer, actually I claimed to be the opposite. But that's not the point: Following the whole development discussion here takes what, an hour a day? Two hours a day? I've got 12h of other stuff to do each day so that eats into my time budget for actually getting things done on this system. I try to follow stuff in the forums that I feel has to do with skins and plugins but I definitely cannot follow each and every development thread. And, again, I do find it difficult to find information. I'm rather new to SC, only using it for less than half a year and thus I don't know all the history and everything and I even find it hard to find stuff in the wiki that I found before, And another point is important: I don't always have a very professional dev. environment at hand, especially I'm not always on a broadband internet connection so assuming I have to download the full package on Windows that didn't look any attractive. Having to install active state perl, Windows Server Ressource Toolkit and whatever on already much too slow subnotebook didn't really look attractive either. And if I have to choose between being professional and getting things done I tend to prefer the latter, at least if it's about "fun" applications like a media center.
Regarding the request to adapt plugins for iPeng: I put that one up for discussion and I wrote down which my priorities are (don't break the usability and make it look good). The only (plugin) developer feedback I got was from Erland. And Erland was quite positive about my approach, maybe because he has run into these issues before. There must be some reason why some of his plugins ship with special code for each and every skin. I don't regard you a plugin developer since you have control over the main skin and can do any kind of changes to the overall system if it seems necessary. And as the start of this whole discussion shows this happens. There are lots of things I would love to change to the overall architecture (especially since I am thinking about the native iPhone app.) to better fit my needs, too, but I don't have that option. -- pippin --- see iPeng at penguinlovesmusic.com ------------------------------------------------------------------------ pippin's Profile: http://forums.slimdevices.com/member.php?userid=13777 View this thread: http://forums.slimdevices.com/showthread.php?t=42620 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta
