From: Mark W. <ma...@rw...> - 2011-03-05 02:53:43
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Scott, <br> <br> I had a quick look and I committed back about three lines of changes to test-language-stuff.php.<br> <br> As long as you dont append .php to the page url , everything loads through the main site and the print_r stuff now prints out so that it is readable in a browser. :)<br> <br> How does one set the language to use?<br> <br> Mark<br> <pre class="moz-signature" cols="72">_____________________________________________ Mob: 07725 695178 Email: <a class="moz-txt-link-abbreviated" href="mailto:ma...@rw...">ma...@rw...</a></pre> <br> On 04/03/2011 22:25, Scott Miller wrote: <blockquote cite="mid:AAN...@ma..." type="cite">Hi guys,<br> <br> I just checked in the minimal amount of code I've sucked in from joomla to get the language stuff to work, and a test script that demonstrates how to load the classes and get the language files loaded. Currently the script just spits out a print_r of a couple classes and some debugging output. So, it's not sexy and pretty yet, but it works. Oh, please run the test language script on the command line, don't try to load it with a browser, I didn't html encode anything yet. And the one language fileset was copied straight from joomla 1.6 main en-GB files.<br> <br> So, some decisions I've struggled with this week:<br> <ul> <li>Do we want to leave these classes named J* (ie JLoader, JLanguage, JFolder, JPath, JFile, JObject, JFactory, etc) or do we come up with our own prefix? If we do, what prefix should we use? Do we want a prefix at all? (BTW: I'm pretty sure JFactory can probably go away when we load this stuff into our existing Factory class)<br> </li> <li>I am struggling to wrap my brain around the Error classes (ours and theirs). Can someone help me figure out how to get the commented out Error handling to actually function with our error handling classes? And give me a brief explaination of how the error handling classes work and what happens for the user?</li> </ul> As this is a first stab, I'm sure there are still things that can be eliminated or cleaned up yet. I'm thinking all the XML indirection methods maybe could be consolidated a bit :-)<br> <br> -Scott<br> <br> <div class="gmail_quote"> On Fri, Mar 4, 2011 at 7:45 AM, David Thompson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:tom...@us...">tom...@us...</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div> I agree with Scott here, Mark. I think if he can work in the same branch then you will automatically have some else who will test your work (and the other way round). Much better than another dead branch with no-one to test or integrate. Not that anything Scott does ends up being dead code ;-).<br> The translation work doesn't impact the architecture in itself, I hope.<br> Dave<br> <br> <hr> Date: Thu, 3 Mar 2011 15:07:13 +0000 <div class="im"><br> Subject: Re: [Tsheetx-developers] Proposal of contribution for a French version<br> </div> <div class="im">From: <a moz-do-not-send="true" href="mailto:sco...@gm..." target="_blank">sco...@gm...</a><br> </div> To: <a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a>; <a moz-do-not-send="true" href="mailto:tom...@us..." target="_blank">tom...@us...</a><br> CC: <a moz-do-not-send="true" href="mailto:tsh...@li..." target="_blank">tsh...@li...</a> <div class="im"> <br> <br> Yes, I saw the email come through about 5 hours after I'd sent it...<br> <br> Brutal is fine :-) I am under no illusions of "cooperation", but I'd thought that perhaps if we made minimal changes to the pieces we wanted we could nearly drop in replacements as Joomla made improvements. But, after starting to look at the work needed, the number of changes we will need to keep from sucking in the whole framework (which I totally agree, we don't want the entire framework) made this thought unrealistic.<br> <br> I understand the fear that perhaps adding internationalization now will hurt the overall progress, but I think this is an important piece, and I've now become familiar enough with the joomla libraries, that I'm not willing to just drop it at this point. I'm hopeful I can hammer out a decent "framework" borrowed and inspired by Joomla that will allow relatively easy translations within a week or two. Plus, the current state of the project says it's quite a long ways off from being released; 3 months or more would be my guess. If we were nearly ready for a release, I would be more easily swayed away :-)<br> <br> Thanks for providing the reality check, I'll start hacking, hammering, and reshaping things to work for us.<br> <br> -Scott<br> <br> <div>On Thu, Mar 3, 2011 at 1:41 PM, Mark Wrightson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a>></span> wrote:<br> <blockquote style="padding-left: 1ex;"> <div>Hi Scott, <br> <br> Your emails did come through, i've just been too busy to reply.<br> <br> I think the best idea is to take inspiration from Joomla and other source files you have seen and create your own that suits our requirements that as Dave says won't bloat the project with un-needed functions.<br> <br> I also think we should put translation on the todo list for a point after we have got txsheet fully working and reskinned. Ultimately my main concern is that there are so many changes being made at the moment, if we don't pool our resources and complete them first, we will get to a point where all we will have is a mess.<br> <br> Mark<br> <pre>_____________________________________________ Mob: 07725 695178 Email: <a moz-do-not-send="true" href="mailto:ma...@rw..." target="_blank">ma...@rw...</a></pre> <div> </div> </div> </blockquote> </div> <br> </div> </div> </blockquote> </div> <br> </blockquote> </body> </html> |