On Sunday 05 February 2006 22:31, you wrote: > On 2/6/06, Brian Mattern <[EMAIL PROTECTED]> wrote: > > the notebook API changed and examine hasn't been updated yet. > > This was obvious indeed! >
The last two lines of output are: ...:432:"undefined reference to `ewl_notebook_tabs_position_set'... and ...:433: undefined reference to `ewl_notebook_tabs_alignment_set'... This was just hours after an EWL commit that says: - rename notebook2 to notebook. - this is API breakage. you now use the normal container functions to append/prepend/insert widgets to the notebook So sure, not completely obvious if you don't have a lot of experience with compiler errors, but the commit log was fairly clear. Also, he explicitly asked "what has happened", so I let him know... > > I would highly recommend following CVS commits and updating when > > something is added that you want to try out rather than just blindly > > updating everything every day. > > Not many people have the time (or knowledge) to follow CVS commits > every day and on top of that patching what hasn't been updated. > There's a fine line between developer and enthusiastic user who wants > to get the latest E. Of course your recommendation is good but it's > easier to update blindly once you know that a certain number of > commits have been done without going into the details of particular > commits. I understand that it takes an extra amount of time to actually follow development, but then again, you might learn something about it. I definitely don't expect users to patch the things that haven't been updated. I do want encourage people to become either a bit more knowledgable or at least a bit more patient. I don't want to discourage people from using e17. I think the enthusiasm is great. However, at this time the user base VASTLY outnumbers the developer base, and we spend a LOT of time helping people compile things. > > > Keep in mind that this is CVS and not a release system, and as > > developers, we reserve the right to break things. > > Agreed. But bear in mind that as a user we reserve the right to inform > politely the developers that they broke things and if possible to fix > them at their convenient time. :-) > Sure, and polite bug reports are often helpful. But I just want to reiterate that this is development code. If we change an API it may take a few days to get everything using that updated. Also, its entirely possible someone will commit something that is incomplete, along with a message stating "don't use this yet, it will hose your box", and I'd prefer not to have dozens of reports the next day of people who hosed their boxes because they had to get their E fix that day. -- rephorm ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
