Show Likes
This section allows you to view all posts where this member received or gave a like to.
1
The Pub / Re: will there be a slideshow for zoomedia in the beta release?
Nao « on February 26th, 2014, 10:09 PM »
There won't. Although I'm currently in a JavaScript focusing phase, I have no plans yo further work on zoomedia during that time. If I work on media stuff I'll instead focus on adding mediaelement.js support and write a playlist system for it so I can get rid of jwplayer.
Anyone is free to offer to work on Zoomedia though... the code is short and simple. Adding a slideshow wouldn't be hard but I'd like for it to be better integrated with AeMe, unlike highslide's.
Anyone is free to offer to work on Zoomedia though... the code is short and simple. Adding a slideshow wouldn't be hard but I'd like for it to be better integrated with AeMe, unlike highslide's.
2
Then I think php will be easy for you. There are many websites offering free tutorial on php. Here is one I downloaded which I feel may be useful to you and other beginners. Attached
3
(Then it leaves us with only TE in the PHP < 5.3 list..? Thorsten, can you elaborate..?)
That's the thing with PHP: some (not all!) changes may be backwards-incompatible. For instance, SMF 2.0.7 is a (pretty underwhelming) patch to mostly improve PHP 5.5 support because the 'e' modifier in PCRE was deprecated, and SMF relied heavily on that. Wedge was patched to the same effect about six months ago (by the same person, I suspect :P). Without these patches, the software would still work, but you'd be getting warnings all over your page. Not cool.
Unfortunately, the reverse is also true... If you try using new PHP features, older versions will give you errors (which isn't a problem for Wedge, except *before* the install process begins, as I painfully noticed today.)
So, basically, whenever you're using software that hasn't been updated in a while (they don't always need to), you're better off staying on your current PHP. All hosts use different ways of allowing users to upgrade; some will force it on them (good luck for old software), and I'm fine with that but I understand it'd be upsetting for those. Some will provide a setting in their panel to choose your default PHP. And some will only enable it if you contact their support team.
So, no worries, it's all good.
That's the whole idea. Wedge forces users to upgrade their PHP to newer, safer versions. If you can update to PHP 5.5, then be my guest. I do all of my local testing on PHP 5.5 these days, so Wedge is fully compatible between PHP 5.3 and 5.5. (5.6 alpha was released recently, and it doesn't break any compatibility in Wedge, so you can add that to the list.)
That's the thing with PHP: some (not all!) changes may be backwards-incompatible. For instance, SMF 2.0.7 is a (pretty underwhelming) patch to mostly improve PHP 5.5 support because the 'e' modifier in PCRE was deprecated, and SMF relied heavily on that. Wedge was patched to the same effect about six months ago (by the same person, I suspect :P). Without these patches, the software would still work, but you'd be getting warnings all over your page. Not cool.
Unfortunately, the reverse is also true... If you try using new PHP features, older versions will give you errors (which isn't a problem for Wedge, except *before* the install process begins, as I painfully noticed today.)
So, basically, whenever you're using software that hasn't been updated in a while (they don't always need to), you're better off staying on your current PHP. All hosts use different ways of allowing users to upgrade; some will force it on them (good luck for old software), and I'm fine with that but I understand it'd be upsetting for those. Some will provide a setting in their panel to choose your default PHP. And some will only enable it if you contact their support team.
So, no worries, it's all good.
That's the whole idea. Wedge forces users to upgrade their PHP to newer, safer versions. If you can update to PHP 5.5, then be my guest. I do all of my local testing on PHP 5.5 these days, so Wedge is fully compatible between PHP 5.3 and 5.5. (5.6 alpha was released recently, and it doesn't break any compatibility in Wedge, so you can add that to the list.)
4
There's an easy solution: Install both forums (SMF and Wedge) in the same database. They use different prefixes (SMF tables start by default with smf_ and Wedge tables start with wedge_ by default.
5
Yes, there will be a way :)
Fixing the importer at this time. Estimated time: today :eheh:
Fixing the importer at this time. Estimated time: today :eheh:
6
Believe it or not, but... I'm currently uploading the repo.
So, in a few minutes (depending on my connection's speed, but it's a bit slow... and it's a big repo), you'll finally be able to download it. And maybe install it (if it works.) And maybe use it. And maybe enjoy it. ;)
So, in a few minutes (depending on my connection's speed, but it's a bit slow... and it's a big repo), you'll finally be able to download it. And maybe install it (if it works.) And maybe use it. And maybe enjoy it. ;)
7
I don't know. Maybe they'll jump ship if I remove Aeva Media from sm.org entirely... :P
I'm not planning to do it, though, for these reasons:
- I'm proud of the fact that 3 years after I gave up on it, it's still the best gallery system available for SMF. (Or, as Arantor so elegantly puts it, "the least worst". Go ahead, Pete, make my day and code your own! I'm sure it'll be better than the 2 years of my life I invested on it!)
- It's free advertising for Wedge.
- Wedge only adds a few features (those from the non-free Aeva Media 2.x) to Aeva Media, and as such, switching from SMF to Wedge *just* for the gallery upgrades wouldn't make sense.
I will not, however, update Aeva Media for SMF 2.1 or later, or port it to any other fork. I will let it die its glorious death, while it keeps on living in Wedge. :)
I'm not planning to do it, though, for these reasons:
- I'm proud of the fact that 3 years after I gave up on it, it's still the best gallery system available for SMF. (Or, as Arantor so elegantly puts it, "the least worst". Go ahead, Pete, make my day and code your own! I'm sure it'll be better than the 2 years of my life I invested on it!)
- It's free advertising for Wedge.
- Wedge only adds a few features (those from the non-free Aeva Media 2.x) to Aeva Media, and as such, switching from SMF to Wedge *just* for the gallery upgrades wouldn't make sense.
I will not, however, update Aeva Media for SMF 2.1 or later, or port it to any other fork. I will let it die its glorious death, while it keeps on living in Wedge. :)