You are here:  » Version Announcement


Version Announcement

Submitted by support on Sun, 2006-02-26 13:23 in

Hi Everyone;

Just to let you know that I have now decided against developing the "Pro" version as a separate product. Instead, I will continue to develop Price Tapestry as per the original "Pro" version feature list, merging new features into the current distribution as they are completed. The script will remain free to all Magic Parser customers under the current "example source code only, no official support" basis.

I will of course make announcements to the forum as and when new features are released; with my first priority (now that full text indexing has been incorporated) being a better way to isolate the codebase from the presentation (HTML, CSS etc.) making the upgrade path easier for existing users wanting to benefit from new features.

Submitted by daviddoig on Sun, 2006-02-26 14:15

This is good news, I have only come across this yesterday and have been scouting the web for a while. It is good to see a product in development and now one that will in effect be opensource in some ways.

I am interested in the development so far and what will come.

Submitted by iman on Sun, 2006-02-26 17:49

Hi David,

I saw the "Pro version" tab disappear earlier this day and was quite puzzled, but *this* is just great news.

Does this mean we can begin "hacking" the free version?

I was hoping that you would find a way to keep the codebase from "user plugins" that we would develop. Lately, products have been improved in this regard. They provide "hook" mechanisms to let external code integrate nicely.

Thanks again, I.

Submitted by support on Sun, 2006-02-26 17:54

> was hoping that you would find a way to keep the codebase from "user plugins" that we would develop.

That's what I'm working on at the moment. I would appreciate any comments from those already hacking Price Tapestry with regards to what sort of changes you are making (I realise that they are mostly cosmetic at the moment) and therefore what work is required to incorporate a new feature from the distribution into your installation...

Submitted by henk on Sun, 2006-02-26 19:17

great m8

when you or others need help i will be there :)

( dutch translation np )

www.linkik.com

Thx Henk

Submitted by iman on Sun, 2006-02-26 20:32

Hi,

my first concern with hacking PT is localization, that is :
- messages translation
- date formating
- hour formating (am/pm or 24h)
- price and currency display

I am not expecting multiple languages/currencies support, but rather easy culture adaptation.

I would recommend either gettext or PEAR::Translation (http://pear.php.net/package/Translation)

Regards, I.

Submitted by support on Sun, 2006-02-26 20:36

Hi Iman,

I was thinking about exactly that today. I know that gettext() is an option; but the configuration of it looks quite complex for users who would like to run a translated version. I'll look into the options.

Note that currency is already localised through the config parameter $config_currencyHTML.

I take it with regards to date and time formatting you are referring to the admin interface?

Cheers,
David.

Submitted by searley on Sun, 2006-02-26 20:48

What many of the asp shopping carts have is a language text files, that can be eddited something like

langCategory="Category"
langBrand="Brand"
langProducts="Products"

and you would run doen the file and modify the words to suite what you want to be dispalyed

For example instead of 'Brand' i may want the word 'Make'

so i would simply edit the file to show:

langBrand="Make"

Submitted by support on Sun, 2006-02-26 20:53

That's more or less exactly what I was thinking of doing - an includes/phrases.php script that contains a simple associative array of all text (there isn't much) throughout the script, e.g:

includes/phrases.php:

<?php
  $phrases
["Brand"] = "Brand";
  
$phrases["Merchant"] = "Merchant";
  
$phrases["Price search results for"] = "Price search results for";
?>

Just thinking of the best way to manage this when it comes to upgrade - you don't want to spend ages on your translation only for it be overwritten when you upgrade.

Submitted by searley on Sun, 2006-02-26 20:58

As i have said before i do more in ASP and the routines are different, but yes thats what i was thining

you could have

includes/phrases_english.php
includes/phrases_german.php

etc, then through config you choose the base language you want, and modify as requires

Currently as you say there is only a few phrases, but as the script grows there will be more, like under Rate & Review etc

Submitted by iman on Mon, 2006-02-27 12:20

I agree with you. However, you could save yourself some typing by writing this way :

<?php
$phrases
=array(
  
"Brand" => "Brand",
  
"Merchant" => "Merchant",
  
"Price search results for" => "Price search results for"
);
?>

And what about variables nested in phrases like in: "Compare 5 prices in 3 merchants" ?

I would use printf() with placeholders in the original string like this one:

"Compare %s prices in %s merchants"