usebb-development Mailing List for UseBB (Page 2)
Light and Free PHP Forum Software
Brought to you by:
pc_freak
Menu
▾
▴
usebb-development — Development discussion
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
(28) |
Apr
(3) |
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
(3) |
Sep
(8) |
Oct
|
Nov
|
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Melissa <uns...@gm...> - 2007-12-28 00:09:46
|
Wow, good news! Thanks :). On Dec 27, 2007 3:32 PM, Dietrich Moerman <die...@us...> wrote: > Since today, the alpha UseBB 2 source code has been added into our > public Subversion repository. > > The website has not been updated yet, but you can find SVN connection > information over at https://sourceforge.net/svn/?group_id=93103. The web > interface can be found at http://usebb.svn.sourceforge.net/viewvc/usebb/. > > Note all code changes are also sent to the checkins mailing list. For > subscription information, see > https://lists.sourceforge.net/lists/listinfo/usebb-checkins. > > What's next is to compose coding guidelines for anyone wishing to > contribute code. As usual, all code is kept under the GNU General Public > License. > > -- > Dietrich Moerman -- http://dmoerman.be > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > UseBB-Development mailing list > https://lists.sourceforge.net/lists/listinfo/usebb-development > |
|
From: Canol G. <can...@ya...> - 2007-12-27 21:54:57
|
Hi Dietrich,=0A=0AI wish you good luck with the development of UseBB 2. I f= ind the decision to only support PHP5 as a good point. As I heared PHP6 wil= l include some significant features so I can even suggest only to support P= HP6 if it comes out before UseBB 2. It would probably be bad for marketing = but good for humanities future :)=0A=0A=0AI also wish good luck to find eno= ugh people to create a team. I know how hard it is to develop such a big pr= oject on your own. Not because of the hardness to code it but mostly becaus= e you get bored and tired to code everything, draw everything and test ever= ything, patch everything on your own after a few months of development, pro= ject slows down significantly and the only solution is to have a break for = a few months.=0A=0AAnyway, I liked UseBB 1 very much and am looking forward= for UseBB 2. Good luck, have fun...=0A=0A=0A=0A=0A =0ACanol Gokel=0A=0Aiyz= i Forum - Hacettepe Robot Toplulugu - Sineyorum=0A=0A=0A----- Original Mess= age ----=0AFrom: Dietrich Moerman <die...@us...>=0ATo: UseBB developm= ent mailing list <use...@li...>=0ASent: Wednesda= y, December 26, 2007 6:05:21 PM=0ASubject: [UseBB-Development] UseBB develo= pment inactivity=0A=0ARecently, some people have expressed their concerns a= bout the UseBB =0Aproject, especially 2.0 development (or, the lack thereof= ). Also, the =0Aidea about a development team has been brought up again.=0A= =0AAs you might know, UseBB 2.0 development already started previous =0Asum= mer, and a number of components have been completed (for the time =0Abeing)= . This mainly includes the language system (unexisting in 1.0)=0A and =0Ath= e first parts of the database layer. Around the end of September, =0Adevelo= pment turned inactive (for personal reasons). I am indeed the=0A sole =0Ade= veloper in this project, and thus there have been no code changes =0Asince = then. This situation may question some people about the need for =0Athe Use= BB project, especially 2.0. Aren't there more than enough PHP =0Aforum proj= ects around already? This is certainly a good question which=0A I =0Awill t= ry to answer as good as possible.=0A=0AWhen the project started, the main g= oal was to create a light and=0A usable =0Aforum package that suits the nee= ds of most small to medium sized web =0Asites which don't need the features= of the big commercial and =0Anon-commercial products. Even though UseBB 1.= 0 has been completed some =0Atime (nearly 1.5 years) ago and the actual pro= duct has mostly reached =0Aits goals, it is lacking a good and future-proof= PHP implementation and=0A =0Adeveloper features. This was the reason to st= art up the UseBB 2.0 =0Aproject and to rewrite everything in PHP 5. This ce= rtainly hasn't been=0A a =0Abad idea: continuing to maintain and extend the= 1.0 codebase would be =0Alike drudging through mud, continuously adding mo= re. PHP 4 is also =0Anearing its end of life and is getting replaced by PHP= 5 nearly=0A everywhere.=0A=0ASo, what is UseBB 2 exactly about? A flexible= forum package written in =0APHP 5, using object orientation as much as pos= sible and taking=0A advantage =0Aof the new components available in PHP 5 (= including SimpleXML, PDO, =0Aetc). The base system will remain "light", all= owing more functionality =0Ato be plugged in. It will also overcome the oth= er limitations UseBB 1.0=0A =0Ahad. Some new functionality that will be add= ed in core are threaded =0Atopics, topic tagging and UTF-8 support. If we t= ake all the currently =0Aavailable PHP forum packages, leave out those that= are not implemented =0Ain OO PHP 5, don't support threaded topics, don't h= ave topic tagging, =0Aetc... not many packages will remain, if any. As a fo= rum software =0Aenthusiast, the only ones I know of and that in some way ca= n be =0Aconsidered similar to the UseBB 2 idea are Phorum, Woltlab Burning= =0A Board =0A3 and bbPress. Though, Phorum and bbPress are not object-orien= ted. WBB=0A 3 =0Ais, but it is commercial software. So, is there a substitu= te for UseBB =0A2? I seems not. That's why the development of 2.0 should co= ntinue.=0A=0AWhat concerns myself, I will certainly continue to develop Use= BB 2 when=0A =0AI have the interest and time. This also certainly doesn't m= ean that =0Athere is no need for a team. Though, finding capable people wil= ling to =0Adedicate their free time and continue doing so isn't that easy. = Over=0A the =0Apast four years, I've had a number of people who were willin= g to help=0A in =0Athe development of UseBB 1.0. Not a single one actually = got to it. Some=0A =0Aof them just vanished and never returned, others sudd= enly left when=0A they =0Adiscovered that the project actually wasn't that = big as they expected=0A it =0Ato be. There are also thousands of people on = the Internet who are =0Awilling to help in the development and claim to be = good PHP developers,=0A =0Awhile they actually even never heard about PHP v= alue types. Does this =0Amean that there are no capable people out there? T= here sure are, but =0Afinding and attracting those people is hard. So, my f= irst concern was=0A to =0Acomplete 2.0.0, get some buzz airing and the pote= ntial developers will =0Aappear automatically.=0A=0ATo give you an idea of = the requirements for UseBB 2 development: next=0A to =0Athe obvious stuff y= ou should know(TM), including XHTML, CSS,=0A JavaScript, =0APHP and SQL, yo= u should be familiar with object-oriented design and =0Aprogramming, PHP 5 = (preferrably 5.2 and its new components such as =0ASimpleXML, PDO, etc.), c= ross-RDBMS SQL (this means, when necessary you =0Ashould be able to write M= SSQL or Oracle specific statements), XML, the =0Ausual web development secu= rity issues matter, GNU/Linux (UseBB mostly =0Aruns on GNU/Linux and all de= velopment upto now was performed on *NIX =0Aboxes), Subversion, etc. Next t= o the technical knowledge, you should be=0A =0Afamiliar with the idea behin= d Open Source, willing to dedicate your=0A free =0Atime (there is no "minim= um amount of commits per month", just pick up =0Asome work when you have th= e interest and time) and preferrably have an =0Ainterest in Internet conten= t management and forum software.=0A=0AA last item in this letter is the pre= vious decision of keeping the v2 =0Acode secret until there is a "decent co= debase" (called 1.99). The main =0Areason for this decision was the number = of GPL violations occuring in =0A2005 and 2006 (remember Revo Forum, XennoB= B, etc). This decision could =0Abe called obsolete at this point, so the co= de will most likely soon be =0Amade available in our public Subversion repo= sitory. As of then, you are=0A =0Aalso welcome to offer code changes and id= eas (instead of having to wait=0A =0Auntil 1.99 - which will thus never exi= st).=0A=0ASo, that's about it for now. An announcement will be made when th= e code=0A =0Ais available in SVN. Also be sure to watch the forums, develop= ment =0Amailing list and my blog for any updates. If you are willing to =0A= contribute in 2.0 development (and have read the requirements), feel =0Afre= e to contact me.=0A=0A(This message has been crossposted on the forums, mai= ling list and =0Adevelopment blog.)=0A=0A-- =0ADietrich Moerman -- http://d= moerman.be=0A=0A-----------------------------------------------------------= --------------=0AThis SF.net email is sponsored by: Microsoft=0ADefy all ch= allenges. Microsoft(R) Visual Studio 2005.=0Ahttp://clk.atdmt.com/MRT/go/vs= e0120000070mrt/direct/01/=0A_______________________________________________= =0AUseBB-Development mailing list=0Ahttps://lists.sourceforge.net/lists/lis= tinfo/usebb-development=0A=0A=0A=0A=0A=0A=0A=0A =0A___________________= ________________________________________________=0AYahoo! kullaniyor musunu= z? http://tr.mail.yahoo.com=0AIstenmeyen postadan biktiniz mi? Istenmeyen = postadan en iyi korunma =0AYahoo! Posta'da |
|
From: Dietrich M. <die...@us...> - 2007-12-27 19:32:52
|
Since today, the alpha UseBB 2 source code has been added into our public Subversion repository. The website has not been updated yet, but you can find SVN connection information over at https://sourceforge.net/svn/?group_id=93103. The web interface can be found at http://usebb.svn.sourceforge.net/viewvc/usebb/. Note all code changes are also sent to the checkins mailing list. For subscription information, see https://lists.sourceforge.net/lists/listinfo/usebb-checkins. What's next is to compose coding guidelines for anyone wishing to contribute code. As usual, all code is kept under the GNU General Public License. -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-12-26 16:05:32
|
Recently, some people have expressed their concerns about the UseBB project, especially 2.0 development (or, the lack thereof). Also, the idea about a development team has been brought up again. As you might know, UseBB 2.0 development already started previous summer, and a number of components have been completed (for the time being). This mainly includes the language system (unexisting in 1.0) and the first parts of the database layer. Around the end of September, development turned inactive (for personal reasons). I am indeed the sole developer in this project, and thus there have been no code changes since then. This situation may question some people about the need for the UseBB project, especially 2.0. Aren't there more than enough PHP forum projects around already? This is certainly a good question which I will try to answer as good as possible. When the project started, the main goal was to create a light and usable forum package that suits the needs of most small to medium sized web sites which don't need the features of the big commercial and non-commercial products. Even though UseBB 1.0 has been completed some time (nearly 1.5 years) ago and the actual product has mostly reached its goals, it is lacking a good and future-proof PHP implementation and developer features. This was the reason to start up the UseBB 2.0 project and to rewrite everything in PHP 5. This certainly hasn't been a bad idea: continuing to maintain and extend the 1.0 codebase would be like drudging through mud, continuously adding more. PHP 4 is also nearing its end of life and is getting replaced by PHP 5 nearly everywhere. So, what is UseBB 2 exactly about? A flexible forum package written in PHP 5, using object orientation as much as possible and taking advantage of the new components available in PHP 5 (including SimpleXML, PDO, etc). The base system will remain "light", allowing more functionality to be plugged in. It will also overcome the other limitations UseBB 1.0 had. Some new functionality that will be added in core are threaded topics, topic tagging and UTF-8 support. If we take all the currently available PHP forum packages, leave out those that are not implemented in OO PHP 5, don't support threaded topics, don't have topic tagging, etc... not many packages will remain, if any. As a forum software enthusiast, the only ones I know of and that in some way can be considered similar to the UseBB 2 idea are Phorum, Woltlab Burning Board 3 and bbPress. Though, Phorum and bbPress are not object-oriented. WBB 3 is, but it is commercial software. So, is there a substitute for UseBB 2? I seems not. That's why the development of 2.0 should continue. What concerns myself, I will certainly continue to develop UseBB 2 when I have the interest and time. This also certainly doesn't mean that there is no need for a team. Though, finding capable people willing to dedicate their free time and continue doing so isn't that easy. Over the past four years, I've had a number of people who were willing to help in the development of UseBB 1.0. Not a single one actually got to it. Some of them just vanished and never returned, others suddenly left when they discovered that the project actually wasn't that big as they expected it to be. There are also thousands of people on the Internet who are willing to help in the development and claim to be good PHP developers, while they actually even never heard about PHP value types. Does this mean that there are no capable people out there? There sure are, but finding and attracting those people is hard. So, my first concern was to complete 2.0.0, get some buzz airing and the potential developers will appear automatically. To give you an idea of the requirements for UseBB 2 development: next to the obvious stuff you should know(TM), including XHTML, CSS, JavaScript, PHP and SQL, you should be familiar with object-oriented design and programming, PHP 5 (preferrably 5.2 and its new components such as SimpleXML, PDO, etc.), cross-RDBMS SQL (this means, when necessary you should be able to write MSSQL or Oracle specific statements), XML, the usual web development security issues matter, GNU/Linux (UseBB mostly runs on GNU/Linux and all development upto now was performed on *NIX boxes), Subversion, etc. Next to the technical knowledge, you should be familiar with the idea behind Open Source, willing to dedicate your free time (there is no "minimum amount of commits per month", just pick up some work when you have the interest and time) and preferrably have an interest in Internet content management and forum software. A last item in this letter is the previous decision of keeping the v2 code secret until there is a "decent codebase" (called 1.99). The main reason for this decision was the number of GPL violations occuring in 2005 and 2006 (remember Revo Forum, XennoBB, etc). This decision could be called obsolete at this point, so the code will most likely soon be made available in our public Subversion repository. As of then, you are also welcome to offer code changes and ideas (instead of having to wait until 1.99 - which will thus never exist). So, that's about it for now. An announcement will be made when the code is available in SVN. Also be sure to watch the forums, development mailing list and my blog for any updates. If you are willing to contribute in 2.0 development (and have read the requirements), feel free to contact me. (This message has been crossposted on the forums, mailing list and development blog.) -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-09-19 10:38:51
|
The language system should be completed (for now). What still might be implemented later is splitting the messages over multiple XML files (per component). This depends on how the performance of SimpleXML and XPath is. Next is the database access layer. As said I will not use Doctrine or any other framework. I started with the connection management a few days ago. Expect more updates soon. At the end of the month, I will post a summary over at my blog (http://dmoerman.be). Dietrich Moerman schreef: > Hello all, > > The past couple of days I have been working on the UseBB 2 code base > (yes, finally). What has been completed (more or less, for the time > being) is the translation system discussed earlier here. > > As said back then, there will be two major static methods used for > translating strings in the source code. Examples: > > echo UseBB_Lang::t('Hello %browser.', array('browser' => > $_SERVER['HTTP_USER_AGENT'])); > > UseBB_Lang::t() takes an English string (including variables), an > associated array with variable key/value pairs and eventually a language > code (which is only used when we need a language different from the > user's - an example use case in v1 is sending topic notification emails). > > echo UseBB_Lang::plural(count($_GET), 'There is 1 GET variable.', 'There > are %count GET variables.'); > > UseBB_Lang::plural() does about the same, except for it takes a count as > first parameter, followed by the singular and plural English form. Of > course, you can also pass variables and a language code here. Though, > %count is automatically assigned and does not need to be passed separately. > > So, how does it all work? > > One of the big advantages is that there is no English translation file, > all English strings are in the code itself. For translations, a new XML > format is used similar to the Qt GUI toolkit's translation files. An > example Dutch file is attached. The file name and the value of the code > attribute of <language/> MUST be alike and be an official language or > language/country code (e.g. nl, nl-be, etc). This again in opposition to > UseBB 1 where the full name was used. A list of these codes can be found > at http://www.loc.gov/standards/iso639-2/php/code_list.php (second table > column). > > The XML file also contains the text direction (ltr in most cases), the > English and native name and a list of translators (name/email pairs). > Notice there is no character set given, ALL translations will be UTF-8 > encoded (which is also the default character set for XML). > > Another thing to note is plural form handling. This is in fact another > downside of the current translation system in v1. Several languages have > completely separate plural form rules compared to English. In some > languages, this is even very complicated. The current code base knows > these exceptions and chooses the right form. In most languages, there > will only be two forms (singular/plural), but some will require three. > > Lastly, one of the best new features is the system's ability to choose > the language based on the user's ACCEPT_LANGUAGE header. A Dutch browser > will for example automatically see the interface in Dutch. If a specific > language/country code is available (e.g. nl-be) this will be used, if > not, the system will fall back to "nl" (when available). > > So, for the time being this system is completed. > > What concerns the database/ORM framework, I will write our own system. > The fact we are using UTF-8 and most (if not all) of these frameworks > rely on core PHP functions makes them unreliable. Doctrine is one of > them. I have sent an e-mail to doctrine-dev about this but sadly did not > receive a response after several weeks. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > UseBB-Development mailing list > https://lists.sourceforge.net/lists/listinfo/usebb-development -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-09-11 08:56:48
|
I'm going to build my own (PHP based) though I still would like to
support more than one format (able people to use Smarty, etc).
Melissa schreef:
> Nice updates Dietrich :).
>
> Have you decided what template parser you will be using? Or building your
> own?
>
> On 9/10/07, Dietrich Moerman <die...@us...> wrote:
>> Small update, I changed the code so integer and float variables are
>> automatically formatted. Thus, you don't need to call
>> UseBB_Lang::number() separately.
>>
>> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
>> 5345.7894));
>>
>> If you don't want it to apply formatting, cast it to a string.
>>
>> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
>> (string) 5345.7894));
>>
>> This will save some type work in the future. :)
>>
>> Dietrich Moerman schreef:
>>> An update today.
>>>
>>> I changed the variables system so it supports three variable types (the
>>> same as in Drupal).
>>>
>>> %foo Escaped and highlighted variable.
>>> @foo Escaped variable.
>>> !foo Raw variable (for example in email messages).
>>>
>>> Using these escaped variables no longer requires the developer to
>>> manually escape data (using unhtml() in UseBB 1). Highlighted for the
>>> time being means the value is encapsulated in <em/>, this should depend
>>> on the used theme later on.
>>>
>>> What was also added is UseBB_Lang::number() which is used to format
>>> number values (integer and float) with the correct number of decimal
>>> places and separators for decimals and thousands. The separators can be
>>> different per language (for example, 1,000.12 in English is 1.000,12 in
>>> Dutch). plural() now automatically formats the @count variable using
>>> this method. Example:
>>>
>>> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
>>> UseBB_Lang::number(5345.7894, 1)));
>>>
>>> Which outputs: There are <em>5,345.8</em> posts per day.
>>>
>> --
>> Dietrich Moerman -- http://dmoerman.be
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> UseBB-Development mailing list
>> https://lists.sourceforge.net/lists/listinfo/usebb-development
>>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> UseBB-Development mailing list
> https://lists.sourceforge.net/lists/listinfo/usebb-development
>
--
Dietrich Moerman -- http://dmoerman.be
|
|
From: Melissa <uns...@gm...> - 2007-09-10 22:00:11
|
Nice updates Dietrich :).
Have you decided what template parser you will be using? Or building your
own?
On 9/10/07, Dietrich Moerman <die...@us...> wrote:
>
> Small update, I changed the code so integer and float variables are
> automatically formatted. Thus, you don't need to call
> UseBB_Lang::number() separately.
>
> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
> 5345.7894));
>
> If you don't want it to apply formatting, cast it to a string.
>
> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
> (string) 5345.7894));
>
> This will save some type work in the future. :)
>
> Dietrich Moerman schreef:
> > An update today.
> >
> > I changed the variables system so it supports three variable types (the
> > same as in Drupal).
> >
> > %foo Escaped and highlighted variable.
> > @foo Escaped variable.
> > !foo Raw variable (for example in email messages).
> >
> > Using these escaped variables no longer requires the developer to
> > manually escape data (using unhtml() in UseBB 1). Highlighted for the
> > time being means the value is encapsulated in <em/>, this should depend
> > on the used theme later on.
> >
> > What was also added is UseBB_Lang::number() which is used to format
> > number values (integer and float) with the correct number of decimal
> > places and separators for decimals and thousands. The separators can be
> > different per language (for example, 1,000.12 in English is 1.000,12 in
> > Dutch). plural() now automatically formats the @count variable using
> > this method. Example:
> >
> > echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
> > UseBB_Lang::number(5345.7894, 1)));
> >
> > Which outputs: There are <em>5,345.8</em> posts per day.
> >
>
> --
> Dietrich Moerman -- http://dmoerman.be
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> UseBB-Development mailing list
> https://lists.sourceforge.net/lists/listinfo/usebb-development
>
|
|
From: Dietrich M. <die...@us...> - 2007-09-10 20:30:36
|
Small update, I changed the code so integer and float variables are
automatically formatted. Thus, you don't need to call
UseBB_Lang::number() separately.
echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
5345.7894));
If you don't want it to apply formatting, cast it to a string.
echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
(string) 5345.7894));
This will save some type work in the future. :)
Dietrich Moerman schreef:
> An update today.
>
> I changed the variables system so it supports three variable types (the
> same as in Drupal).
>
> %foo Escaped and highlighted variable.
> @foo Escaped variable.
> !foo Raw variable (for example in email messages).
>
> Using these escaped variables no longer requires the developer to
> manually escape data (using unhtml() in UseBB 1). Highlighted for the
> time being means the value is encapsulated in <em/>, this should depend
> on the used theme later on.
>
> What was also added is UseBB_Lang::number() which is used to format
> number values (integer and float) with the correct number of decimal
> places and separators for decimals and thousands. The separators can be
> different per language (for example, 1,000.12 in English is 1.000,12 in
> Dutch). plural() now automatically formats the @count variable using
> this method. Example:
>
> echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
> UseBB_Lang::number(5345.7894, 1)));
>
> Which outputs: There are <em>5,345.8</em> posts per day.
>
--
Dietrich Moerman -- http://dmoerman.be
|
|
From: Dietrich M. <die...@us...> - 2007-09-10 16:42:06
|
An update today.
I changed the variables system so it supports three variable types (the
same as in Drupal).
%foo Escaped and highlighted variable.
@foo Escaped variable.
!foo Raw variable (for example in email messages).
Using these escaped variables no longer requires the developer to
manually escape data (using unhtml() in UseBB 1). Highlighted for the
time being means the value is encapsulated in <em/>, this should depend
on the used theme later on.
What was also added is UseBB_Lang::number() which is used to format
number values (integer and float) with the correct number of decimal
places and separators for decimals and thousands. The separators can be
different per language (for example, 1,000.12 in English is 1.000,12 in
Dutch). plural() now automatically formats the @count variable using
this method. Example:
echo UseBB_Lang::t('There are %num posts per day.', array('%num' =>
UseBB_Lang::number(5345.7894, 1)));
Which outputs: There are <em>5,345.8</em> posts per day.
Dietrich Moerman schreef:
> Hello all,
>
> The past couple of days I have been working on the UseBB 2 code base
> (yes, finally). What has been completed (more or less, for the time
> being) is the translation system discussed earlier here.
>
> As said back then, there will be two major static methods used for
> translating strings in the source code. Examples:
>
> echo UseBB_Lang::t('Hello %browser.', array('browser' =>
> $_SERVER['HTTP_USER_AGENT']));
>
> UseBB_Lang::t() takes an English string (including variables), an
> associated array with variable key/value pairs and eventually a language
> code (which is only used when we need a language different from the
> user's - an example use case in v1 is sending topic notification emails).
>
> echo UseBB_Lang::plural(count($_GET), 'There is 1 GET variable.', 'There
> are %count GET variables.');
>
> UseBB_Lang::plural() does about the same, except for it takes a count as
> first parameter, followed by the singular and plural English form. Of
> course, you can also pass variables and a language code here. Though,
> %count is automatically assigned and does not need to be passed separately.
>
> So, how does it all work?
>
> One of the big advantages is that there is no English translation file,
> all English strings are in the code itself. For translations, a new XML
> format is used similar to the Qt GUI toolkit's translation files. An
> example Dutch file is attached. The file name and the value of the code
> attribute of <language/> MUST be alike and be an official language or
> language/country code (e.g. nl, nl-be, etc). This again in opposition to
> UseBB 1 where the full name was used. A list of these codes can be found
> at http://www.loc.gov/standards/iso639-2/php/code_list.php (second table
> column).
>
> The XML file also contains the text direction (ltr in most cases), the
> English and native name and a list of translators (name/email pairs).
> Notice there is no character set given, ALL translations will be UTF-8
> encoded (which is also the default character set for XML).
>
> Another thing to note is plural form handling. This is in fact another
> downside of the current translation system in v1. Several languages have
> completely separate plural form rules compared to English. In some
> languages, this is even very complicated. The current code base knows
> these exceptions and chooses the right form. In most languages, there
> will only be two forms (singular/plural), but some will require three.
>
> Lastly, one of the best new features is the system's ability to choose
> the language based on the user's ACCEPT_LANGUAGE header. A Dutch browser
> will for example automatically see the interface in Dutch. If a specific
> language/country code is available (e.g. nl-be) this will be used, if
> not, the system will fall back to "nl" (when available).
>
> So, for the time being this system is completed.
>
> What concerns the database/ORM framework, I will write our own system.
> The fact we are using UTF-8 and most (if not all) of these frameworks
> rely on core PHP functions makes them unreliable. Doctrine is one of
> them. I have sent an e-mail to doctrine-dev about this but sadly did not
> receive a response after several weeks.
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> UseBB-Development mailing list
> https://lists.sourceforge.net/lists/listinfo/usebb-development
--
Dietrich Moerman -- http://dmoerman.be
|
|
From: Dietrich M. <die...@us...> - 2007-09-09 22:21:36
|
No, only the singular form is used to lookup the translations. English has only two forms (singular and plural) while some languages have three (see http://doc.trolltech.com/qq/qq19-plurals.html). The plural form passed to plural() is only used when English is the interface language. If all languages had only two forms and shared the same rules, we could have just left behind the form attribute and make separate <message/> elements for singular and plural. However, there is even one language (French) that has only two forms as in English but uses the singular for a count of 0 as well (again, see the above link). For the convenience of the translator, these rules (which you can see in the last table at the above link) are embedded in our code. The only thing the translator needs to do is use the right language code and correctly translate the different plural forms. Melissa schreef: > Question with the .xml format. > > I seen you had only 'form 1' in the English language ( non-plural ), but had > it had been translated 2 different times in Dutch (non-plural, plural). Is > there no origional needed for the second argument (plural) ? > > <message> > <original form="1">There is 1 GET variable.</original> > <translation form="1">Er is 1 GET-variabele.</translation> > </message> > <message> > <original form="2">There are 2 GET variables.</original> > <translation form="2">Er zijn %count GET-variabelen.</translation> > </message> -- Dietrich Moerman -- http://dmoerman.be |
|
From: Melissa <uns...@gm...> - 2007-09-09 21:22:41
|
Question with the .xml format.
I seen you had only 'form 1' in the English language ( non-plural ), but had
it had been translated 2 different times in Dutch (non-plural, plural). Is
there no origional needed for the second argument (plural) ?
<message>
<original form="1">There is 1 GET variable.</original>
<translation form="1">Er is 1 GET-variabele.</translation>
</message>
<message>
<original form="2">There are 2 GET variables.</original>
<translation form="2">Er zijn %count GET-variabelen.</translation>
</message>
On 9/9/07, Dietrich Moerman <die...@us...> wrote:
>
> Hello all,
>
> The past couple of days I have been working on the UseBB 2 code base
> (yes, finally). What has been completed (more or less, for the time
> being) is the translation system discussed earlier here.
>
> As said back then, there will be two major static methods used for
> translating strings in the source code. Examples:
>
> echo UseBB_Lang::t('Hello %browser.', array('browser' =>
> $_SERVER['HTTP_USER_AGENT']));
>
> UseBB_Lang::t() takes an English string (including variables), an
> associated array with variable key/value pairs and eventually a language
> code (which is only used when we need a language different from the
> user's - an example use case in v1 is sending topic notification emails).
>
> echo UseBB_Lang::plural(count($_GET), 'There is 1 GET variable.', 'There
> are %count GET variables.');
>
> UseBB_Lang::plural() does about the same, except for it takes a count as
> first parameter, followed by the singular and plural English form. Of
> course, you can also pass variables and a language code here. Though,
> %count is automatically assigned and does not need to be passed
> separately.
>
> So, how does it all work?
>
> One of the big advantages is that there is no English translation file,
> all English strings are in the code itself. For translations, a new XML
> format is used similar to the Qt GUI toolkit's translation files. An
> example Dutch file is attached. The file name and the value of the code
> attribute of <language/> MUST be alike and be an official language or
> language/country code (e.g. nl, nl-be, etc). This again in opposition to
> UseBB 1 where the full name was used. A list of these codes can be found
> at http://www.loc.gov/standards/iso639-2/php/code_list.php (second table
> column).
>
> The XML file also contains the text direction (ltr in most cases), the
> English and native name and a list of translators (name/email pairs).
> Notice there is no character set given, ALL translations will be UTF-8
> encoded (which is also the default character set for XML).
>
> Another thing to note is plural form handling. This is in fact another
> downside of the current translation system in v1. Several languages have
> completely separate plural form rules compared to English. In some
> languages, this is even very complicated. The current code base knows
> these exceptions and chooses the right form. In most languages, there
> will only be two forms (singular/plural), but some will require three.
>
> Lastly, one of the best new features is the system's ability to choose
> the language based on the user's ACCEPT_LANGUAGE header. A Dutch browser
> will for example automatically see the interface in Dutch. If a specific
> language/country code is available (e.g. nl-be) this will be used, if
> not, the system will fall back to "nl" (when available).
>
> So, for the time being this system is completed.
>
> What concerns the database/ORM framework, I will write our own system.
> The fact we are using UTF-8 and most (if not all) of these frameworks
> rely on core PHP functions makes them unreliable. Doctrine is one of
> them. I have sent an e-mail to doctrine-dev about this but sadly did not
> receive a response after several weeks.
>
> --
> Dietrich Moerman -- http://dmoerman.be
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> UseBB-Development mailing list
> https://lists.sourceforge.net/lists/listinfo/usebb-development
>
>
|
|
From: Dietrich M. <die...@us...> - 2007-09-09 16:55:27
|
Hello all,
The past couple of days I have been working on the UseBB 2 code base
(yes, finally). What has been completed (more or less, for the time
being) is the translation system discussed earlier here.
As said back then, there will be two major static methods used for
translating strings in the source code. Examples:
echo UseBB_Lang::t('Hello %browser.', array('browser' =>
$_SERVER['HTTP_USER_AGENT']));
UseBB_Lang::t() takes an English string (including variables), an
associated array with variable key/value pairs and eventually a language
code (which is only used when we need a language different from the
user's - an example use case in v1 is sending topic notification emails).
echo UseBB_Lang::plural(count($_GET), 'There is 1 GET variable.', 'There
are %count GET variables.');
UseBB_Lang::plural() does about the same, except for it takes a count as
first parameter, followed by the singular and plural English form. Of
course, you can also pass variables and a language code here. Though,
%count is automatically assigned and does not need to be passed separately.
So, how does it all work?
One of the big advantages is that there is no English translation file,
all English strings are in the code itself. For translations, a new XML
format is used similar to the Qt GUI toolkit's translation files. An
example Dutch file is attached. The file name and the value of the code
attribute of <language/> MUST be alike and be an official language or
language/country code (e.g. nl, nl-be, etc). This again in opposition to
UseBB 1 where the full name was used. A list of these codes can be found
at http://www.loc.gov/standards/iso639-2/php/code_list.php (second table
column).
The XML file also contains the text direction (ltr in most cases), the
English and native name and a list of translators (name/email pairs).
Notice there is no character set given, ALL translations will be UTF-8
encoded (which is also the default character set for XML).
Another thing to note is plural form handling. This is in fact another
downside of the current translation system in v1. Several languages have
completely separate plural form rules compared to English. In some
languages, this is even very complicated. The current code base knows
these exceptions and chooses the right form. In most languages, there
will only be two forms (singular/plural), but some will require three.
Lastly, one of the best new features is the system's ability to choose
the language based on the user's ACCEPT_LANGUAGE header. A Dutch browser
will for example automatically see the interface in Dutch. If a specific
language/country code is available (e.g. nl-be) this will be used, if
not, the system will fall back to "nl" (when available).
So, for the time being this system is completed.
What concerns the database/ORM framework, I will write our own system.
The fact we are using UTF-8 and most (if not all) of these frameworks
rely on core PHP functions makes them unreliable. Doctrine is one of
them. I have sent an e-mail to doctrine-dev about this but sadly did not
receive a response after several weeks.
--
Dietrich Moerman -- http://dmoerman.be
|
|
From: Dietrich M. <die...@us...> - 2007-08-15 12:41:56
|
Hello all, Sorry for the quietness and delays lately. A few recent UseBB (2.0) related posts I made on my blog: * http://dmoerman.be/web-application-i18n-and-l10n * http://dmoerman.be/development-updates As noted in the most recent post, Doctrine seems like a good solution for UseBB 2.0, apart from the fact that we will enforce UTF-8 which is not supported in PHP core nor Doctrine. I have posted a message to doctrine-dev with questions and a possible solution on their part (Doctrine_String and phputf8, as I plan to do in UseBB itself). Still awaiting a response... -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-08-12 17:40:44
|
Hello,
You cannot change & into &. As we are using XHTML, doing so will
break XML well-formedness and even show an error when using the
application/xhtml+xml content-type. What's even more, it *will* break
the RSS feed (which is server as XML).
I don't know why you would want to change it though.
谭冠鹏 schreef:
> the code below locate int the file functions.php. I do not know if I
> can replace "&" with "&".
> If I do,will there be differences?
>
>
> if ( $html ) {
>
> foreach ( $vars as $key => $val )
> $safe[] = urlencode($key).'='.urlencode($val);
> $url .= join('&', $safe);
>
> } else {
>
> foreach ( $vars as $key => $val )
> $safe[] = $key.'='.$val;
> $url .= join('&', $safe);
>
> }
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> UseBB-Development mailing list
> https://lists.sourceforge.net/lists/listinfo/usebb-development
>
--
Dietrich Moerman -- http://dmoerman.be
|
|
From: <s_...@st...> - 2007-08-11 16:16:36
|
the code below locate int the file functions.php. I do not know if I
can replace "&" with "&".
If I do,will there be differences?
if ( $html ) {
foreach ( $vars as $key => $val )
$safe[] = urlencode($key).'='.urlencode($val);
$url .= join('&', $safe);
} else {
foreach ( $vars as $key => $val )
$safe[] = $key.'='.$val;
$url .= join('&', $safe);
}
|
|
From: Dietrich M. <die...@us...> - 2007-07-07 15:50:33
|
Hello all, The next UseBB 1 maintenance release, 1.0.7, will be released most likely next Monday (July 9th). Changes include: - Added an (random math based or custom) anti-spam question feature against spam bots. - Added a security measure which generates a new session ID when logging in/out. - Fixed bug #1641: Global text color missing. - Fixed bug #1591: CSS for BBCode [code] blocks in IE and Safari. - Fixed faulty HTTP_HOST reassembling when running on port other than 80. - Fixed hexadecimal entities + smilies parsing problem. - Fixed fatal error for phpBB convertor using mysqli. - Admin accounts are no longer deactivated when e-mail address has changed. - Made the sendmail -f parameter for emails an on/off setting. - Now always stop when superglobals are (tried to be) defined via GET/POST/COOKIE. Translation files additions: Added in lang: - AntiSpamQuestion - AntiSpamQuestionInfo - Question - Answer - AntiSpamQuestionMathPlus - AntiSpamQuestionMathMinus - AntiSpamWrongAnswer Added in admin: - ConfigBoard-sendmail_sender_parameter - ConfigBoard-sendmail_sender_parameter-info - ConfigBoard-antispam_question_mode - ConfigBoard-antispam_question_mode-info - ConfigBoard-antispam_question_mode0 - ConfigBoard-antispam_question_mode1 - ConfigBoard-antispam_question_mode2 - ConfigBoard-antispam_question_questions - ConfigBoard-antispam_question_questions-info Changed in admin: - ConfigBoard-cookie_httponly-info -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-07-06 14:10:29
|
UseBB has expressed its support for the new Go PHP 5 initiative[1]. Go PHP 5 was started by a group of PHP based Open Source projects which will make new features PHP 5.2 only as of February 5th, 2008*. As UseBB has been working towards our rewritten PHP 5 forum package "UseBB 2", we have joined this group[2]. The website lists participating projects[3] and hosting providers[4] which will serve PHP 5.2 by default. Should you know more projects or hosts that can participate, please contact them or submit them at once. *February 5th, 2008 is not the final release date of UseBB 2.0.0 but the goal of the initiative for all projects to have migrated to PHP 5.2 only development. We will also still support and "bug fix" UseBB 1 after this date. [1] http://gophp5.org/ [2] http://www.usebb.net/gophp5/ [3] http://gophp5.org/projects [4] http://gophp5.org/hosts -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-06-08 22:19:46
|
Hello all, Just a "small" note to say that two third of my exams at university college are done now. This means I will be picking up UseBB 2 work as soon as I have the time. As said earlier I will continue analysis and design, complete the domain model (which has been posted before), the class diagram and database design. The question which database abstraction framework will be used remains for now, possible candidates are: - eZ Components Supports MySQL, PostgreSQL, Oracle and SQLite. - Zend Framework Supports MySQL, Microsoft SQL Server, Oracle, PostgreSQL and SQLite. - phpDoctrine Supports FrontBase, InterBase/Firebird, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, QuerySim (never heard of) and SQLite. All these are written in PHP 5. However, I guess phpDoctrine used to be written in PHP 4 (or I have been badly informed when posting in a previous thread). Checking SVN reveals that the code is in PHP 5. There is a big difference between Doctrine and the others, Doctrine is an ORM framework which maps database relational data to objects and vice versa, the other two are just regular database abstraction frameworks. All of them use PDO. I don't know how big all these frameworks are, AFAIK Zend Framework can be slimmed down to only the necessary components, but this is uncertain. Doctrine will most likely only contain what we need. I will test these packages and check what turns out best. Any suggestions are still welcome. ----- Another note, PHP Group's PHP 4 support will end at the beginning of 2008. Therefore I want to speed up things a bit so we can hopefully roll out 1.99 by the end of the year and 2.0 before the summer of 2008 (perhaps earlier). This means some planned things for 2.0 may be postponed to 2.1, 2.2, etc, among this are threaded topics, abstract template parser support and other more technical user and developer features. I will then stop supporting UseBB 1 about 6 months after UseBB 2.0.0 has been released. If I can continue UseBB 2 development at a good speed this will be between July and December 2008. -- Dietrich Moerman -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-05-09 20:09:43
|
Dietrich Moerman schreef: > Hello all, > > During a few hours of free time yesterday and today I implemented a > simple but effective anti-spam measure in UseBB 1. The anti-spam > question feature poses guests who access the register, reply and new > topic forms either a random and simple math question or a randomly > picked question out of a set of questions/answers defined by the admin. > Especially the custom ones are effective. > > The code (fully functional) is in CVS, apart from the ACP modifications > which will happen later this week. Then I will also apply the changes to > the public community forums. > Today, the code was completed. The math question mode now randomly poses plus and minus math questions with randomly chosen operands. Unlimited custom questions can be defined, the given answer is case insensitive. All this can be configured in the ACP. The code can be fetched from CVS. It is also enabled on the community forums now. A UseBB 1.0.7 release is not planned right now, I hope to wait for a few months (2, 3, perhaps more) unless security holes are found. The development of UseBB 2 will - as announced before - continue as of the end of June. -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-05-08 20:04:54
|
Hello all, During a few hours of free time yesterday and today I implemented a simple but effective anti-spam measure in UseBB 1. The anti-spam question feature poses guests who access the register, reply and new topic forms either a random and simple math question or a randomly picked question out of a set of questions/answers defined by the admin. Especially the custom ones are effective. The code (fully functional) is in CVS, apart from the ACP modifications which will happen later this week. Then I will also apply the changes to the public community forums. -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-04-21 21:50:35
|
Dietrich Moerman schreef: > Hello all, > > It has been a bit quiet here lately, due to a few hardware problems and > some other work that had to be done. > > Over the next week I will try to perform more tasks for the analysis and > design phase, investigate a few of the other PHP based web applications, > especially concerning the template system/forms/plugins integration > (this seems to be one of the hardest parts currently). Afterwards I need > to look into phpDoctrine which at first sight seems to be a good > candidate for database abstraction with ORM support (instead of eZ > Components). > > Any suggestions are still welcome. I will try to elaborate on the above > topics later on. > Haven't got any time this week due to course work assignments, and don't suspect to have much time available in the next month. As exams in June are getting closer, I guess the next big period of UseBB 2 work will be for as of the end of June 2007. I guess there won't be a change for a 1.99 release next summer, unless a miracle occurs. Let's see how it evolves and perhaps 1.99 could be released in SVN by the end of 2007. What concerns the website, as I plan to get into Drupal development, it could be a very good idea to base the new UseBB 2.0 website on Drupal 5 (or perhaps even 6 by then). A bridge could be made so no duplicate registrations are needed, and seen the flexibility of Drupal all website content could easily be housed in this system using custom content types (this also opens up the possibility to eventually get a resources database earlier than planned upto now). In the mean time any more ideas are still welcome on this list or the forum. -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-04-13 13:43:17
|
Hello, Until today, UseBB had a disused CVS module "UseBB-docs" that contained a few DocBook XML files that were once (in 2005) meant to be used for official documentation. Today, this module has been removed by SourceForge.net and this means the end of the CVS cleanup process that has been going on for some time. This also included removal of the "test" and old "UseBook" modules. UseBB is now the only module in our CVS repository, containing all UseBB sources from 0.2 upto today. UseBB 2 will be, as announced, kept in the Subversion repository. Greetings from sunny Belgium. :) -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-04-07 20:59:35
|
Hello all, It has been a bit quiet here lately, due to a few hardware problems and some other work that had to be done. Over the next week I will try to perform more tasks for the analysis and design phase, investigate a few of the other PHP based web applications, especially concerning the template system/forms/plugins integration (this seems to be one of the hardest parts currently). Afterwards I need to look into phpDoctrine which at first sight seems to be a good candidate for database abstraction with ORM support (instead of eZ Components). Any suggestions are still welcome. I will try to elaborate on the above topics later on. -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-03-31 13:58:13
|
Hello all, Attached is the first revision of the domain model. A domain model is a representation of the existing objects in an object-oriented system, their associations and (some) properties. The diagram shows the existing objects currently foreseen in UseBB 2.0. Note this design allows unlimited subforums, threaded topics, polls with unlimited options, private messages, etc. If anyone is familiar with OO analysis, feel free to comment. -- Dietrich -- http://dmoerman.be |
|
From: Dietrich M. <die...@us...> - 2007-03-30 13:21:11
|
An update of the summary document, a few sections were added, including threaded topics, groups, translation support, polls, private messages, form API, etc. -- Dietrich -- http://dmoerman.be |
