There is a reason Laravel supports localisation.. you doing it wrong m8
You must be registered to see links
, I know about it
Joopie.
But this isn't a Language system. I see you're little misunderstanding what I'm doing here. The thing it's that, HabboWEB has it's own language system in .json files. I'm justing replacing "Habbo" word by {{$chocolatey['name']}}, of course
this
Code:
echo __('messages.welcome');
or this
Code:
[USER=1333467003]Lang[/USER]('messages.welcome')
Seems be so much decent. Maybe I'll switch to Localization. It's a good idea. But, I'm basically doing the same.
Also in the HabboWEB templates I'll do the same. "Habbo" for Hotel Name. Anyways, next release I'll add localization.
One last thing:
Localization in Laravel it's for language system. Obviously if I had the control of the thing, and we don't have Angular in HabboWEB this would be pretty amazing to put.
But see, I'm not changing the localization strings. Maybe those languages are good for Internal Texts that aren't on HabboWEB Language Files.
But for
templating engine I don't think that this Is good. I mean, Chocolatey has some Blade Global Variables that makes everything easier. It's like on RevCMS. The
User Model, the
Settings Model.
You can access both Mail Settings, Chocolatey Settings and User Instance (if available). This is good for pro developers and newbies. They just need insert {{$user['my_user_attribute']}}. {{$chocolatey['my_setting_attribute']}}
I will change from Array to objects. Because it's more easier and pretty more decent.
I will use Localization feature for Internal texts.
I also need think on a way to make HabboWEB stuff easier to edit/patch/etc. Adding a new language isn't
easy since you need add the .json schema of the language and replace all Habbo words with safe.
Obviously if you don't want you don't
need change Habbo to {{$chocolatey->name}}. But you
may do it.
Regards,
Claudio
