Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account
Forum
Support forum
Coding inside your component
images.php and fork
  • Page:
  • 1

TOPIC:

images.php and fork 07 Oct 2013 07:54 #11308

Hi all,

I noticed one of the classes for which there is no fork yet is the images.php class. I tried to do it myself by adding the following lines in the images.php file:
JLoader::register('WpfImagesFork', JPATH_ADMIN_WPF .DS. 'fork' .DS. 'classes' .DS. 'images.php');
JLoader::load('WpfImagesFork');
// Fallback if no fork has been found
if (!class_exists('WpfImagesFork')){ class WpfImagesFork extends WpfImages{} }

This does load the forked class, but however when (in my case), I want to override the get() function, it does not seem to work. It will still call the get of the parent images.php class. I think in my case I can workaround this by calling my forked class in the forked class of the file.php, but just wondering why the first approach does not work.

FYI - what I am trying to accomplish is to override the define constant for 'allowed image sizes'. I want to merge this with a number of extra sizes which will be passed in from my component configuration parameters.

Any one any ideas?

Misha

Please Log in or Create an account to join the conversation.

images.php and fork 07 Oct 2013 10:38 #11309

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
For the moment not forkable.
Images.php will be rewrited and will work with JImages natives from (Joomla 3.0 native)
Coding is now a piece of cake
The following user(s) said Thank You: blue-canoe

Please Log in or Create an account to join the conversation.
  • Page:
  • 1
Forum
Support forum
Coding inside your component
images.php and fork
Time to create page: 0.180 seconds
“
”

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started

Log In Sign In